[Solved] This somehow crashes the game.

[Yours Truly]

• Uncontrollable Footman
  • Events
    • Unit - A unit Is issued an order targeting an object
    • Unit - A unit Is issued an order targeting a point
    • Unit - A unit Is issued an order with no target
  • Conditions
    • (Unit-type of (Triggering unit)) Equal to (==) Man of Foot
  • Actions
    • Unit - Order (Triggering unit) to Stop

 

[IcemanBo]

It probably fires itself again. But if you turn the trigger off, order stop, then turn it on again, it probably won't crash.

 

[Yours Truly]

Well that kinda works. Game doesn't crash anymore but neither does the footman stop. What am I doing wrong here ._.

PS:This footman is ward-classified.

 

[HappyTauren]

Always post your trigger, chances are you do not understand instructions. So let us see.

 

[Yours Truly]

If you say so.

• Uncontrollable Footman
  • Events
    • Unit - A unit Is issued an order targeting an object
    • Unit - A unit Is issued an order targeting a point
    • Unit - A unit Is issued an order with no target
  • Conditions
    • (Unit-type of (Triggering unit)) Equal to (==) Man of Foot
  • Actions
    • Trigger - Turn off (This trigger)
    • Unit - Order (Triggering unit) to Stop
    • Trigger - Turn on (This trigger)

 

[IcemanBo]

Try to pause unit before ordering stop, and after stop it can be unpaused again. So:

Trigger off
Pause Unit
Stop
Unpause Unit
Trigger on

 

[Yours Truly]

At first it looked like it works. But then i tested the footman while he's in combat. All it takes is one player command and he's paused for eternity.

Hidden

• Uncontrollable Footman
  • Events
    • Unit - A unit Is issued an order targeting an object
    • Unit - A unit Is issued an order targeting a point
    • Unit - A unit Is issued an order with no target
  • Conditions
    • (Unit-type of (Triggering unit)) Equal to (==) Man of Foot
  • Actions
    • Trigger - Turn off (This trigger)
    • Unit - Pause (Triggering unit)
    • Unit - Order (Triggering unit) to Stop
    • Unit - Unpause (Triggering unit)
    • Trigger - Turn on (This trigger)

 

[IcemanBo]

All it takes is one player command and he's paused for eternity.

What does it mean with player command?

But hm, maybe.. what's the exact goal? It looks like you want prevent all units of type "Man of Foot" from making any orders, and just always stop. So they will never be able to move.

 

[HappyTauren]

Maybe add a condition Order is not "Stop". If you add that condition then you do not even have to turn off the trigger.

 

[Yours Truly]

What does it mean with player command?

But hm, maybe.. what's the exact goal? It looks like you want prevent all units of type "Man of Foot" from making any orders, and just always stop. So they will never be able to move.

Player command = any orders such as move,patrol,attack,stop and cast spells made by the unit's player

I'm actually trying to make a unit that is selectable, owned by their player but cannot be directly controlled.

Maybe add a condition Order is not "Stop". If you add that condition then you do not even have to turn off the trigger.

That works

 

[IcemanBo]

If unit has Ward classification it has no patrol buttons anymore etc, then the only order we need to filter is "smart" (right-click).

 

[Yours Truly]

So, the reason why the footman's not stopping is because it's classified as a Ward?

EDIT: OK, Nevermind guys. I got it working now. Thanks for trying to help anyway

Hidden

• Uncontrollable Footman
  • Events
    • Unit - A unit Is issued an order targeting an object
    • Unit - A unit Is issued an order targeting a point
  • Conditions
    • Multiple ConditionsAnd - All (Conditions) are true
      • Conditions
        • (Unit-type of (Triggering unit)) Equal to (==) Man of Foot
        • ((Triggering unit) is paused) Equal to (==) False
  • Actions
    • Unit - Pause (Triggering unit)
    • Unit - Order (Triggering unit) to Stop
    • Unit - Unpause (Triggering unit)

 

[Dr Super Good]

The order events fire before the order is actually issued. Hence the event response order overwrites the order issued in response to it after the trigger thread finishes. I think the pause/unpause work because pausing flushes the event response order so it is no longer scheduled to be issued.