Global cooldown rework in Cataclysm

On Monday, we got this:
Quote:
There appears to be some system where the game will pre-queue your ability if you hit the button 1s-.7s before the GCD is complete. Once the GCD is up, the ability will auto fire. [...] The problem is that it locks in your ability and you can't switch what you want to do. This affects classes that rely on procs or chaining instant cast abilities in quick succession in a very negative way. You can't react to procs or switch to a CC ability on demand. You're "locked in" 1s before the GCD is even up.
There appears to be some system where the game will pre-queue your ability if you hit the button 1s-.7s before the GCD is complete. Once the GCD is up, the ability will auto fire. [...] The problem is that it locks in your ability and you can't switch what you want to do. This affects classes that rely on procs or chaining instant cast abilities in quick succession in a very negative way. You can't react to procs or switch to a CC ability on demand. You're "locked in" 1s before the GCD is even up.
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.
Today, Kalgan added:
As an update to this, the next beta build will include a slider bar (labeled "Custom Latency Tolerance") that lets you tune how sensitive the ability queue is (including sliding it all the way to zero if you choose). This value allows you to control (in milliseconds) how long before the GCD finishes the client will let you queue your next ability.
The optimal setting will probably be right around what your ping time is. So, if your ping is 100 for example, you'd probably want to set it at 100 or slightly higher.
The optimal setting will probably be right around what your ping time is. So, if your ping is 100 for example, you'd probably want to set it at 100 or slightly higher.
Let's talk about this. In Cataclysm, the way things are now in beta, if you hit an ability while the global cooldown is still counting down, the server will accept the command and hold it for you until the cooldown (on the server side) is finished. What this means is that if you have to cram as many abilities into a minute as you can, you will be able to chain them together one after another, no matter how bad your latency is. This is awesome, because right now, it doesn't always work out that way. You currently have to press a key as fast as you can and hope that the second the server starts accepting commands for your next cooldown, one of them landed. If your latency changes, or if you don't spam as fast as someone else, they could land more abilities in the same period of time.
The downside with this new ability chaining system is that if you send a command that's received half a second before the server is ready to execute your next ability, you can't change it. There are many reasons you'd want to do this, including procs, buffs, debuffs, boss mechanics or even better abilities coming off cooldown. Ghostcrawler's post indicates that Blizzard is planning on letting us change our command after it's been queued, though.
In addition, Blizzard will be implementing a new feature that lets you configure how early the server should start listening for the next command. It will eventually default to your average latency, and the closer it is to your latency, the better. Setting it high would be a perfectly fine option if we are indeed able to change our minds at the last minute; otherwise, it's better to stick to having it set at your average latency.
World of Warcraft: Cataclysm will destroy Azeroth as we know it; nothing will be the same! In WoW Insider's Guide to Cataclysm, you can find out everything you need to know about WoW's third expansion (available Dec. 7, 2010), from brand new races to revamped quests and zones. Visit our Cataclysm news category for the most recent posts having to do with the Cataclysm expansion.Filed under: Bugs, News items, Cataclysm






Reader Comments (Page 1 of 4)
Ally Oct 8th 2010 6:07PM
This'll be brilliant I hope. Hopefully it'll work well in PvP and PvE
Neofox Oct 9th 2010 4:51AM
For everyone who reads this; it seems that Blizzard is trying to make the system work exactly like the City of Heroes/Villains combat system. Basically, you have your abilities out on your action bar (like WoW), and rather than a GCD, the system waits for as long as it takes to animate your character doing the attack before it uses the next one (so right after the previous attack is finished).
That would work just fine in WoW with the GCD, and I've always wanted them to implement it, but there are two distinct differences getting in the way. First, all powers in CoH/V activate instantly--there are no casting abilities (and all abilities have a cooldown, no spamming). That, however, is not the real problem (because in WoW the next ability would start right after the last cast, simple).
The real difference causing a problem is that CoH/V has no proc abilities, or other variables that cause certain abilities to be used only at certain times. WoW on the other hand is abundant with talent/item procs and other abilities that are circumstantial (like a rogue's finishing moves, a paladin's hammer of wrath, or a mage's missile barrage). In WoW, the ability to change your order of attacks would be necessary.
Also, in WoW, some classes tend to spam the same button more often than others, whereas in CoH/V, each ability has a cooldown and therefore a different ability must be placed next in the queue. Because of this, in CoH it is easy to remove an ability from the queue by simply clicking it again, and the queued attack becomes unhighlighted and is no longer queued. WoW wouldn't be so simple because people will be queuing the same ability on top of itself.
Considering all this, I'd rather the queue system be left out of the game entirely, and I probably won't use it myself unless it becomes proven that it is, indeed, more efficient than the current system. I hope I've helped explain for those who were having trouble, or perhaps I've confused you more. In which case, apologies.
DracMonster Oct 9th 2010 9:05AM
If I'm understanding this correctly, if you set the slider all the way to 0 you won't have a queue, so it is basically optional.
If the system lets you change your queued command on the fly, that seems like it addresses your main concern, though.
Zalvi24 Oct 8th 2010 6:06PM
sounds pretty interesting
Dalrand Oct 8th 2010 6:13PM
I'd like to point out this ability queuing system is already working in live for cast time abilitys and has been for some time.
Zaros Oct 8th 2010 6:43PM
Thats latency
Noyou Oct 8th 2010 6:51PM
I would have to agree to an extent. I use default UI and your spell doesn't go through until you release your button. I have heard you can go in and make it fire as soon as you press which would be optimal for PvP. I have noticed that most times I can press my button before the GCD cools and my spell is 'queued' up so to speak a fraction of a second or two ahead. Only time it really helps the way it is - is on a boss fight. If you miss time it however you end up double clicking and that takes time away :(
Pyromelter Oct 8th 2010 7:01PM
It's not latency, there is a queuing system.
And the thing that creates the action on button press instead of release is an addon, call snowfallkeypress
http://www.wowinterface.com/downloads/info15078-SnowfallKeyPress.html
Enjoy :)
Narshe Oct 8th 2010 9:31PM
@pyromelter
That mods broken and hasnt been worked on since February.
Nucrus Oct 9th 2010 4:17AM
@Narshe
Snowfallkeypress is still working fine, have you even tried it?
Hih Oct 8th 2010 6:13PM
Sounds very cool. Lotro has a similar function where you can queue up your next instant which takes a little getting used to, but is really nice. Can't wait for this to get implemented in WoW.
Jorsh Oct 8th 2010 7:01PM
Wait... what?
Matthew Oct 8th 2010 11:15PM
/agree
Iirdan Oct 8th 2010 6:15PM
The short end of this, however, is in leveling. I'll be happily killing away, spamming some Arcane Shots on my lowbie hunter, and then the mob dies. Yay! But wait! I hit Arcane Shot again during the GCD! Oh no! It fired and pulled that nearby elite!
Dead.
It has ups and downs. Either way, it is an interesting feature that will take some getting used to.
(cutaia) Oct 8th 2010 6:26PM
I'm guessing a queued ability is only going to fire on the targeted mob, or at the very most it might still fire if you retarget in that last second of your previous global cooldown.
I don't see it picking a new target, retargeting, and firing your queued ability, though.
Artificial Oct 8th 2010 6:31PM
I don't think it works that way. The queued shot will just generate an "invalid target" error.
Artificial Oct 8th 2010 6:32PM
...and cutaia beat me...
Saeadame Oct 8th 2010 6:40PM
@(cutaia) - this actually happened to me just a few minutes ago while leveling. I killed a mob, but before it had completely uh... died, I pressed an attack again (Earth Shock). The system auto-targeted a nearby mob and used Earth Shock on it, causing me to accidentally pull a neutral mob that otherwise wouldn't have attacked me.
I didn't press tab, or anything except the Earth Shock button
Balgus Oct 8th 2010 6:43PM
or if it doesnt....use your mouse and turn around. cant shoot what isnt infront of you.
Iirdan Oct 8th 2010 6:44PM
Uh, not sure why I'm being downrated for sharing my experiences. This is exactly what has been happening to me in the beta.