Triggers slower than shift-queueing?

[MauranKilom]

In -wtf mode, I happen to buy a dagger most of the times. But if I order my hero to blink somewhere, and then shiftqueue another blink (both from dagger), my hero will stop after the first blink. (Any other shift-queued action won't be executed as well.) I suppose the cooldown-resetting is done by triggers.
I've also heard of things like crow being able to carry gem (if you don't know about it don't ask please, because bug discussion is not allowed ). This one must be triggered, too.
And the third thing, manta+metamorphosis also works. Though i'm not sure if this is triggered or hardcoded glitch/feature.


So, my question: Is shift-queueing faster than triggers?

[casab1anca]

Yes, in -wtf mode, the cooldown is reset by triggers. A shift-queued order is executed immediately after the previous order completes, but the trigger needs at least a small amount of time (however little) to execute, so the cooldown isn't reset yet.

Manta+metamorphosis is hardcoded, I believe.

[zxdragon12]

I don't see why you would shiftqueue it anyway. It's wtf mode, just spam that hotkey to your destination.

[MauranKilom]

That's actually irrelevant to my question. To answer you: because I might want to get somewhere after I perform an action, and if i was able to shift queue daggers, I would be able to get from A to B in a matter of frames.

[JaCKaSS_69]

Spam clicking works in -wtf too, but thats irrelevant.

Yes, triggers need some time to take place.

[MauranKilom]

I'm actially amazed now. I would've thought that whatever you do, first triggers register it, and then you do it (e.g. performing the second blink), and thus they could do everything in that time.
Thx!
Cáno fixed it...

[Cáno]

Nothing to thank for. Talking about triggers 'taking time to execute' is complete nonsense. It only means that casab1anca and JaCKaSS_69 don't know what they are talking about but still try.

Generally, if we are talking about triggers firing on events, talking about time or delay is completely irrelevant. It's all about in what order actions are performed and that depends on how things are coded. We obviously don't know that but we can tell by testing.
For example: Damage event fires after all the reductions are calculated, but before the check for invulnerablity and before the HP is deducted. And there's no real reason for that, it's just how it's programmed.

In this particular case, however, the Cooldowns are refreshed 0 seconds after the spell goes into effects.

Originally Posted by MauranKilom

Is shift-queueing faster than triggers?

This question doesn't even make any sense.

[casab1anca]

Sorry if I was wrong, but does that mean triggers are executed sequentially with the game flow, i.e. the trigger must finish execution before anything else can continue?

[MauranKilom]

Originally Posted by Cáno

In this particular case, however, the Cooldowns are refreshed 0 seconds after the spell goes into effects.

Ok, so in this interval the shift-queueing is executed. Could've thought of that myself...

Originally Posted by Cáno

This question doesn't even make any sense.

Just that the answer is no doesn't mean it is senseless. I just thought that triggers only fire after shift-action is executed. In this moment SK-ult comes into my mind, together with the fact that you will lose one pulse even with shift-queueing blink. So I could've seen myself that the answer was no. I was just confused by wtf-blinking, because I didn't realize the trigger must wait for the spell to begin it's effect, or it would refresh a spell that is not already casted.

Edit:

Originally Posted by casab1anca

Sorry if I was wrong, but does that mean triggers are executed sequentially with the game flow, i.e. the trigger must finish execution before anything else can continue?

yes, but you can make an event "Wait 0 seconds" in which the things you speak of can continue (including shift-queued actions), and then the trigger continues. This is the case we are talking about with the dagger: we have to wait till the spell is done for refreshing the cooldown.

[Cáno]

It just has no sense. A trigger isn't something that can be fast or slow. Triggers don't fire but are fired.

Actually, even if there was no delay it wouldn't work. The EVENT_UNIT_SPELL_EFFECT fires before the spell goes on cooldown so refreshing is pointless. The EVENT_PLAYER_UNIT_SPELL_FINISH should work since it's fired before the next order is given but it just doesn't. Ask Blizzard why.

[MauranKilom]

Originally Posted by Cáno

Actually, even if there was no delay it wouldn't work. The EVENT_UNIT_SPELL_EFFECT fires before the spell goes on cooldown so refreshing is pointless.

I already understood and mentioned that.

Originally Posted by Cáno

The EVENT_PLAYER_UNIT_SPELL_FINISH should work since it's fired before the next order is given but it just doesn't. Ask Blizzard why.

I've thought it would work, and so I wondered why the trigger is fired after the next order is given and not at the end of the spell (that's what i was referring to as "slower", though it is not the correct word for it). Just this sentence would've been enough to make it clear what's going on.

Thank you for your help

[DracoLich]

We have 200 hp and just killed Necronomicon Warrior 3rd lvl with Last Will, which deal 600 dmg to killer right after death.
Hero have 199/200 exp, so, after killing he will get exp, -> a lvlup stats, in our case - +50 str (or +1k hp, whatever u like)
So, question: will damage applied before lvlup OR damage trigger will be slower than lvlup?

[Cáno]

Level up will be first.

And please stop using expressions like 'damage trigger will be slower'. It's hard to read these...

It's not even a damage event, it's unit death event which fires after the damage event.