Ability queue system issues

We had to change the ability queue system you are describing to fix an exploit that was threatening to become pretty widespread. It is unfortunately one of those cases where a few bad apples ruin things for everyone. :(
We are working on an improvement where the most recent command will override the previous one. If for example you are spamming Hamstring, and then succeed in snaring someone, you can switch to Mortal Strike which will clear out the Hamstring queue instead of wasting more GCDs on Hamstring.
We are working on an improvement where the most recent command will override the previous one. If for example you are spamming Hamstring, and then succeed in snaring someone, you can switch to Mortal Strike which will clear out the Hamstring queue instead of wasting more GCDs on Hamstring.
The issue here is not the queue system itself but rather being locked into a choice when you rely on proc abilities that you can't predict. In the absence of a Sword and Board proc, for instance, or Revenge lighting up, you're going to want to use an ability like Devastate or Heroic Strike to generate threat, since some threat is always better than no threat. But when a higher-priority attack like Shield Slam or Revenge lights up, the last thing you want is to be locked into Devastate, unable to use the greater threat ability not only until Devastate fires but until the global cooldown -- which could end up costing you over 2 seconds on a proc that has a limited duration, as well as costing you that threat. There's a similar issue for DPS or PvP players, of course. A high-damage proc ability like Bloodsurge could very well fall away entirely while you're waiting for your ability queue to clear.
Hopefully that override will be in place soon. At any rate, this is something to be aware of for the immediate future.
Filed under: Analysis / Opinion, News items, Cataclysm






Reader Comments (Page 1 of 3)
Jadfer Oct 6th 2010 9:06AM
What was the exploit?
Moofius Oct 6th 2010 9:42AM
I'm guessing the "exploit" was being able to spam buttans (either manually or using a spam program) to get spells to cast instantly after the last spell instead of latency+reaction time.
In the end when they fix their fix it will bring everyone better dps, but right now it's annoying as hell.
Ice Oct 6th 2010 9:48AM
From what I recall it was the
-Cast 1.x sec cast then instantly spam instant spell landing both at same time. This also goes to some extent for melee even tho I dont know how much.
Correct me if Im wrong, of course.
Even tho I had no idea it was "exploit" I just thought it was lag.. but hey, devs seem to label stuff as "exploit" that people dont even realize that arent meant to be like that (not just blizz fyi)
Rawr Oct 6th 2010 10:03AM
The exploit was that you could somehow lower you GCD, thereby spamming abilities. Big problem in competitive gameplay like arenas.
Snuzzle Oct 6th 2010 12:10PM
@Ice
If that is the exploit they were trying to fix, they're many years too late. It's already become massively widespread. It's called a Shatter combo.
Resident Horrible Oct 6th 2010 12:49PM
I think I'm misunderstanding this. I have an add-on that tells me what my "Actual" casting baar/time is instead of the lag-induced wow ui casting bar. As soon as the bar hits the end, I immediately cast another spell, sometime an instant spell (this from a mage pov, btw) like Fireblast which lands at the same time as my Fireball. Are they saying not to chain these together?
This has been possible for years, so I'm assuming that I've got it completely wrong. Sorry if I'm an idiot, just curious about what's going on.
Munitions Oct 6th 2010 1:05PM
Rawr was right. The exploit they're referring to is one which allows you to remove the GCD on abilities. The GCD's still checked server-side, but removing it client-side gives you the smallest possible value, which is exactly 1 second. It's just an MPQ file that you place in the Data folder.
Also, as a warrior tank, I never knew there was an ability queue system. At all. The way I'm reading it, when you press a spell and it fails, the game queues it and does it later, but I know that isn't actually the case. Or is it?
... Link, anyone?
Pyromelter Oct 6th 2010 1:32PM
I thought it might have been something that had to do with that guy that made that macro that would crash servers. With a longer ability queue, that type of thing would not be able to occur.
That's what I got out of the "bad apples" situation, although I could be wrong. The shatter combo thing is not what they are referring to; that's a different bug entirely that is now fixed on the beta server the last I heard.
Darky Oct 6th 2010 9:10AM
Damn 'locks always ruining everything: First GCDs and now this; why can't they just hellfire themselves away?
Finnicks Oct 6th 2010 2:20PM
Oh sure. Blame the Warlocks. It's so easy.
You're a mage aren't you? DID BELT SEND YOU!?
WE'RE ONTO YOU MAGE. WE KNOW ABOUT YOUR OGRE ARMY.
Mr. Tastix Oct 6th 2010 2:36PM
Butthurt mage is obvious.
MikeLive Oct 6th 2010 9:11AM
Honestly, I only ever noticed this queue system when I'm experiencing really bad lag. Vast majority of the time, I'm hitting buttons when I can, never while the GCD is still ticking.
Noyou Oct 6th 2010 9:29AM
Go Blizzard!
Stilhelm Oct 6th 2010 9:31AM
I believe this only affects 4.0. In 4.0, if you hit an ability with 1 sec or less left on the GCD, it will queue that ability. On live, it doesn't appear that abilities are queued for melee classes. There was a definite difference in playing my warrior on live and on the PTR, and the queueing system did kind of suck for someone who's used to playing a prot warrior, made things feel sluggish.
nieboh Oct 6th 2010 9:39AM
So, I guess I'm wondering what they're doing. Are they fixing an exploit or fixing the system to make if feel less sluggish or both? Or will it become worse? Will fixing the exploit make it feel more sluggish? And as Jadfer said...just what was the exploit that they feel they need to fix?
Not saying you necessarily know the answers to these, Stilhelm, it's just that your post raises the questions in my mind.
Moofius Oct 6th 2010 9:49AM
They are fixing the "exploit" for now, but as said it will make things feel sluggish and annoying. I'm guessing they will soon (tm) fix their fix so things will be better than what it is currently on live. The "exploit" is manually spamming your ability button to get abilities after a gcd away faster, which leads to more stress for blizzards servers.
sherekhan88 Oct 6th 2010 9:50AM
I think it's that the initial ability queue system was exploitable, the current system was created to prevent that exploit, but was not refined and has issues of its own. It seems that the current iteration of the system is meant to be a stop-gap measure.
Quinto Oct 6th 2010 9:57AM
The exploit is a way to change your game files to give you the shortest possible global cooldown.
This new que system is supposed to fix the exploit for good, but I suspect it is also meant to allow people to get their abilities off without constand hand-damaging spam. Right now on beta it feels terrible for melee classes with random procs, but for casters I suspect its an improvement.
krko Oct 6th 2010 9:48AM
Accursed Fury Warriors and their Heroic Strike Exploit...
Mayhew Oct 6th 2010 12:11PM
I can assure you that this is not due to the Heroic Strike "exploit". That doesn't even exist on the PTR or beta servers. In making HS an instant attack on a separate cooldown, Blizzard has removed this bug/exploit from the game.