[Snippet] Stun Event

[Nestharus]

This resource has moved here.

--

gone

 

[Magtheridon96]

Did you have to call the unit unit? =P

 

[Troll-Brain]

Unfortunately it won't fire if the unit is already stunned/paused, which makes it quite pointless (in most cases), in fact only make every stun abilities with triggers is the best solution.

 

[Nestharus]

Unfortunately it won't fire if the unit is already stunned/paused, which makes it quite pointless (in most cases), in fact only make every stun abilities with triggers is the best solution.

Awww, that's true : (

 

[Bribe]

A stun is a point-order event, and what you have is a target-order event.

 

[Nestharus]

A stun is a point-order event, and what you have is a target-order event.

Nop, you're wrong.

It sounds like you just assumed this because that's what you would think a stunned order would be. Don't just assume things, test them first >.>.

 

[Troll-Brain]

A stun is a point-order event, and what you have is a target-order event.

When you pause an unit or stun it, the unit get the same order, but it's a point-order when you pause it (don't remember if the target point was null or not but the coordinates are 0,0 : the center of the map).
And when the unit get stunned it's a widget-order event, if i remember correctly the target is the widget which has directly stunned the unit (like an orc ward made with a shaman spell, or the caster if the spell is direct like the ones with the human hero : moutain king)

But this special order is cool when you want to forbid an order an keep the previous no-target one (like holdposition) :

http://www.hiveworkshop.com/forums/1866690-post358.html

 

[Nestharus]

I actually think stun event is still useful.

For example, you could easily argue that only detecting the first stun on a unit is smart since the unit is already stunned, thus can't respond to further stuns =).


However, this wouldn't be useful for like passive abilities that do something when a unit is stunned =(.

 

[Troll-Brain]

I actually think stun event is still useful.

I disagree.

For example, you could easily argue that only detecting the first stun on a unit is smart since the unit is already stunned, thus can't respond to further stuns =).

Again, any concrete example ?
The only use i can see is to do something when a stun ability occurs, so it's not enough, plus if the event fired each time that wouldn't be a problem, that's not like you can't easily link a boolean or an integer to an unit.
In fact that's why i've never submitted a such thing, the only valid way is to make all stun abilities with triggers.

However, this wouldn't be useful for like passive abilities that do something when a unit is stunned =(.

Yep and actually that would be the only one useful case.

 

[Bribe]

Its uses are limited but this system does its purpose as it should.

I might recommend coupling this with detecting when a unit is paused, which
is the same issued order as was already discussed but with a point-order event
(yeah point order .... when it's paused, doesn't make any sense I know)

~ Approved