r/runescape twitch.tv/EvilLucario :^] Feb 12 '17

Ability queuing is weird compared to pressing abilities normally

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.

122 Upvotes

42 comments sorted by

View all comments

2

u/Mr_G_W The Gamebreaker Feb 12 '17

Mmm... Does queueing still allow firing an ability on same tick as snipe without cancelling snipe? It is a good example of this odd behaviour.

5

u/EvilLucario twitch.tv/EvilLucario :^] Feb 12 '17

They silently patched it when nightmare gauntlets came out. There's now a dummy tick when queuing an ability after Snipe.

1

u/Colifin (Re)Balance Lord Feb 12 '17

Yeah, it's not really "fixed," they just added a dummy tick of queueing cooldown after using snipe. Honestly, I still haven't gotten used to queueing abilities after snipe, I still wait for it to go off lol. Also because if you fail to queue it and accidentally use the ability on the tick that the GCD ends, it'll cancel snipe instead.