Stupid units

[Wayshan]

Hey, I have one problem with using a trigger called
"Unit - Issue order Targeting a point"
I want unit to go by the road. Problem is that the path isn't straight (it's zig zag), so I need more regions and multiple use of this trigger. The unit has to be neutral - passive. The unit stops sometimes or just turn in half way and goes back. Idk what to do with it. Can someone advice me?
My trigger is:
TriggerAB
"A unit enters region A"
"Triggering unis is Unit"
"Order unit to move to region B"
TriggerBC
"A unit enters region B"
"Triggering unis is Unit"
"Order unit to move to region C"

etc.

 

[Razwerd]

"Triggering unis is Unit"

What is that? You should probably use Order Entering Unit to Move to Region B.
Also units will take the shortest path, so if you want them to go by a specific way put path blockers or cliffs etc.

 

[Wietlol]

Show triggers?
That helps.

 

[Nichilus]

If I understand the problem correctly, then the answer to the zig-zag problem is that the problem is not with the trigger but with WC3's pathing system.
Computer controlled units by default return to the point they ran away from (or if they run too far away from the point). You could try to manually stop the unit once it reaches some destination. Also, I believe you need to increase the size for some constants in Gameplay Constants window in World Editor. I think Neutral Creep camps or something.

 

[Squiggy]

Try setting the owner of the units to a Player instead of Neutral Passive

 

[APproject]

As Nichilus said. Go to gameplay constants and set Creep - Guard values to very high, this way units will not go back, never going back even if you are being chased by hostile one. So this got nothing to do with triggers, because these units are forced to go back due to those values.

 

[Wayshan]

Ah thanks, guys I have a quite similar question - when I have one player controlling another player (fully), units of the controled player are coming back too. Can I change it somehow in gameplay constants too?

 

[APproject]

Try setting those values to the maximum value allowed and see if the same occurs. If it does, then something else is forcing units to go back, a trigger perhaps.