Little triggery problem with orders.

[CoLd Bon3]

Yo, wazzup, hivers! It's a simple question : why this doesn't work?

• CreepsStopAttack
  • Events
    • Unit - A unit Is issued an order targeting an object
  • Conditions
    • (Unit-type of (Target unit of issued order)) Equal to Wolf (Level 1)
  • Actions
    • Unit - Order (Ordered unit) to Stop

I want when a unit tries to attack this Wolf unit, the attacking unit to stop. I want this to stop both intentional and unintentional attack orders. I mean, both when you right click and when the unit attacks by it's self.

 

[69stehend]

"issued order" event only triggers when the player tells a unit to do something
autoattack doesnt trigger it
use the event "unit is being attacked"

 

[CoLd Bon3]

"issued order" event only triggers when the player tells a unit to do something
autoattack doesnt trigger it
use the event "unit is being attacked"

Unit is attacked event will stop the attacking unit right after it deals damage... i want to stop it before it deals damage.

 

[baassee]

Unit is attacked event will stop the attacking unit right after it deals damage... i want to stop it before it deals damage.

Nope. Unit is attacked fires when the attacking unit finishes his/her animation thus it can easily be abused by using stop.

 

[69stehend]

Nope. Unit is attacked fires when the attacking unit finishes his/her animation thus it can easily be abused by using stop.

it fires when it BEGINS the animation, not when it finishes

Unit is attacked event will stop the attacking unit right after it deals damage... i want to stop it before it deals damage.

it fires before it deals damage, even if animaton damagepoint is set to 0.00

 

[baassee]

it fires when it BEGINS the animation, not when it finishes

Ah makes sense.

 

[69stehend]

so just do it like this:

• Events:
• A unit is being attacked
• Conditions:
• Unittype of (Triggering Unit) is equal Wolf level 1
• Actions:
• Order (Attacking Unit) to stop

 

[defskull]

• Unit - Order (Attacking Unit) to Stop

Sometimes this function works too fast, perhaps adding a Wait or Timer of 0.00 second would work.
If it doesn't, well, it has to do with your Condition/Event.