Order Unit to stop via trigger does not stop them?

[aple]

Very simple:

• Untitled Trigger 002
  • Events
    • Unit - A unit Is issued an order targeting a point
  • Conditions
  • Actions
    • Unit - Order (Triggering unit) to Stop

This does not order the unit to stop. In the context, the point order is Move. If they're ordered to move, I want the unit to be immediately ordered to stop. That way, it's order is empty and it will acquire targets that come near it.

Removing the move ability will not work, because I still want the unit to be able to be ordered to move and hold position.

 

[Zeatherann]

It needs to be lowercase "stop", not "Stop" like you have it.

 

[aple]

I'm using GUI. You can only put Presets in the Order Units function. No strings, no variables.

 

[Tickles]

Order the unit to move to its current location. Turning the trigger off and then on after the actions prevents an infinite point order loop:

• Events
  • Unit - A unit Is issued an order targeting a point
• Conditions
• Actions
  • Trigger - Turn off (This trigger)
  • Set TempPoint = (Position of (Triggering unit))
  • Unit - Order (Triggering unit) to Move To TempPoint
  • Custom script: call RemoveLocation (udg_TempPoint)
  • Trigger - Turn on (This trigger)

 

[aple]

I tried that but it doesn't work with what I'm trying to do.

I'm using a knockback system that moves the units, and when they are knocked back they'll try to move to the location you order them to move to after they've been knocked back.

 

[Daffa]

The Knockback should use SetUnitX and Y, if I don't mistaken there they're keeping orders.

 

[aple]

Well, it's an old system. Probably horribly out-dated. But it doesn't keep the orders. Just try the first trigger I posted alone, without anything else in the map, or anything else in that trigger. It won't actually order the unit to stop.

(Or hell, maybe my Editor/WC3 is just horribly bugged...)

 

[Dr Super Good]

The problem is because the event fires before the order is actually issued to the unit. This is a timeline of what goes on.

You order unit to move -> Unit issued order targeting point event fires -> Unit ordered to stop -> Unit Ordered to move

You need a 0 timeout timer to create a new thread after the "Unit Ordered to move" stage in response to the "Unit issued order targeting point event fires" stage.

 

[Zeatherann]

Hmm, then why does this work in JASS in the trigger condition?

 

[Dr Super Good]

As far as I am aware it has never worked. It works in response to the "unit is attacked" event which is commonly part of an anti-TK system but that is because attacking is not an order and more a state.

 

[Zeatherann]

No, I've used it for stopping smart orders as well.

 

[Dr Super Good]

Well when I used it the stop order was always issued before the main order which was why it never worked and fits the problem the topic creator describes perfectly.

I do admit I might have run it as an action and not a condition however (if that makes a difference).