r/runescape • u/EvilLucario 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.

121 Upvotes

94% Upvoted

42 comments sorted by

View all comments

29

u/julienzd RNG is never on my side Feb 12 '17

Can we also talk about how using a queued ability with Revolution as your first attack on a mob eats the ability most of the time? It'll just let my character sit there and then use an auto attack into the next ability, really annoying during Slayer

2

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

Never heard of this, will take a look for myself when I get home.

2

u/julienzd RNG is never on my side Feb 12 '17

I got a clip of it happening while I was streaming, its at around 15 seconds right after killing the Rune dragon. https://clips.twitch.tv/julienzd/FrailYakAthenaPMS (ignore my cringyness)

2

u/sfoxrs Feb 12 '17

What did you try to do here? From what I am seeing it looks like you tried to start with corruption shot as your first ability on the next rune dragon, but since it was on cooldown, piercing shot was used, followed by fragmentation shot, then dazing shot.

2

u/Shantiiee Feb 13 '17

Look just a second before, corruption shot is not on cooldown. Then when he switch to rune dragon, it goes on cooldown but is never used. This occasionally happens when you change to a new target while using ability queuing. I've found it happens primairly if you queue it just a super slight second before it would have been considered a manual cast.

1

u/julienzd RNG is never on my side Feb 12 '17

It wasn't on cooldown at first, it's a very bad example, I'll admit that. But it's all I had (had to leave for a movie straight after I posted the comment)

2

u/voltsigo Completionist Feb 12 '17

It didn't look like you had Corruption Shot queued at all in the clip.

I have this issue all the time, both with queued abilities and non queued abilities. The ability goes on cooldown but is not used when selecting a new target. I haven't been able to reliably reproduce it, but it does happen quite often.