Originally Posted by Poromu
This is close to truth, but the way spell queueing works is that if you have no haste or NG and a cast time of 1.5, your casting-interval will be 1.5 because you can place the spell in queue before your last one finishes casting.
|
There is no spell queuing mechanics in WoW. If you press a spell button while it is on cooldown (global or regular), you instantly get the error message "Spell not ready" (or something like that - I'm using a German client). If the global cooldown is over but the spell still casting, then there's a brief delay in which the client sends the action to the server. The server now either accepts it, because he processes it right after the spell's duration on its end or it will send a SPELL_CAST_FAILED back with the error message "Another action in progress" (or something like that).
Lastly, the client also blocks additional cooldown-effective actions when it has already sent one action to the server and is still waiting for a reply. That's when it plays that annoying sound that you often get when spamming your buttons too quickly.
I'm willing to accomodate that perhaps Blizzard might have added some tolerance either to the GCD-lock client-side (maybe making it 1.4 seconds un-hasted) or a server-side tolerance of 0.1-0.2 seconds, which might result in players with very good pings to chain short spells near perfectly (although that could really only be achieved by means like G15 macros - noone is that perfect at timing). However, if near-perfect Wrath spam would be possible, those Moonkins should have discovered that solar eclipse beats lunar in DPS. Most players have found the opposite to be true by practical experimentation.