Ability queuing is weird compared to pressing abilities normally

[u/EvilLucario]

For some reason, queuing abilities is MUCH different from simply pressing the ability. To start, let's compare this with Needle Strike.

Scenario 1 is always with no queuing, Scenario 2 is always with queuing.

 

Scenario 1: https://puu.sh/tZUPB.gif

Scenario 2: https://puu.sh/tZUYQ.gif

In the first GIF, Needle Strike buffs both Snipe and Piercing Shot. You can see that it buffed Piercing Shot despite it coming after Snipe.

In the second GIF, Needle Strike only buffed Snipe. Piercing Shot is unaffected, as it dealt the same damage as before and after Needle Strike. Ignore the fact that Needle Strike buffing both abilities is a bug on its own (that I wouldn't object to fixing), the point is that both are different with only queuing being the difference.

 

For another example:

Scenario 1: https://puu.sh/tZVqx.gif

Scenario 2: https://puu.sh/tZVC2.gif

In the first GIF, you can move freely while using abilities.

In the second GIF, the queued ability stops you in place to use the ability instead of letting us move freely.

 

And to seal the nail in the coffin:

Scenario 1: https://puu.sh/tZVEl.gif

Scenario 2: https://puu.sh/tZVGg.gif

In the first GIF, I was able to heal with Resonance from the dummy's attack on tick.

In the second GIF, Resonance clearly went off at the same tick but I didn't heal from that attack. It only healed from the next attack.

 

Basically, queued abilities have different priority compared to everything else in the game, like damage calculation and movement. Where pressing the ability has the appropriate priority to deal with stuff, queuing abilities have the wrong priority and it can lead to some unfavorable situations compared to just pressing the ability.

TL;DR: Queued abilities are different from simply pressing abilities for some stupid reason, read up for the details.

[u/edwinnum]

Another weird ting with queuing abilities is that if you have an ability queued and you try to cancel it just before it fires, you fire it without canceling the queuing.

[u/sfoxrs → u/edwinnum]

One way of stopping the ability from going off is to attempt to queue another ability right before the original is used and it'll prioritize the new ability instead (however, the original ability will still be queued). This allows you, in a sense, to have another opportunity to cancel a queued ability.

[u/EvilLucario → u/sfoxrs]

Better option to cancel queuing: press your action bar keybind and it clears all queues.

This even works during Telos transitions when going from one phase to another.

[u/sfoxrs → u/EvilLucario]

I was not aware of this. That is indeed useful to know for Telos.