My theory is: because it's a unit-order it can't compute directly the desired unit-order, it needs some time (wait) inbetween the orders, otherwise it will just take the first-order, which in your case is "Route 1".
BUT: It's not the ideal solution to just add wait. What you really should do is split all Events and Actions into several Triggers, so they don't bother each other.
Trigger 1:
Event: Unit Enters Region X
Action Order Unit to move to Region Y
Trigger 2:
Event: Unit Enters Region Y
Action Order Unit to move to Region Z
and so on. If you have a look at Blizzard maps they rarely have huge triggers, they split them into several triggers (for performance and other reasons). The best example are the cinematics you can find on all maps. Blizzard uses Queues.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
My theory is: because it's a unit-order it can't compute directly the desired unit-order, it needs some time (wait) inbetween the orders, otherwise it will just take the first-order, which in your case is "Route 1".
BUT: It's not the ideal solution to just add wait. What you really should do is split all Events and Actions into several Triggers, so they don't bother each other.
Trigger 1:
Event: Unit Enters Region X
Action Order Unit to move to Region Y
Trigger 2:
Event: Unit Enters Region Y
Action Order Unit to move to Region Z
and so on. If you have a look at Blizzard maps they rarely have huge triggers, they split them into several triggers (for performance and other reasons). The best example are the cinematics you can find on all maps. Blizzard uses Queues.