New GCD Changes

[HPAVC]

Button mashing a spell even though it doesn't cast because of (not ready yet, not even rage, not enough energy, etc) will trigger a GCD. Drastically effecting chaining spells together (mashing mortal strike so you trigger it as the cooldown occurs, arcane explosion spamming will actually have delays betwene explosions if you press the keys to fast, prayer of healing.

http://www.wowinsider.com/2007/11/05/dont-mash-in-2-3/

I wonder if this means the world is going to move to hardware macroing tools and there will be a backlash crackdown on people that server up multiple perfectly timed spells.

[Xzin]

Ick that makes things a bit harder... especially as you get desynced spamming IAE due to stuns, etc.

[Ellay]

I guess we'll see how this one pans out on live.

[Xzin]

If you thought Thaddius was bad....

What happens if you click it and you are out of casting but you lag and are not actually? Forget trying to time spells. This is going to be a nightmare with constantly shifting latency times.

[Djarid]

it is intended as an improvement... to replace the endemic /stopcasting in macros... but we will have to see how it plays out.

[Xzin]

Consider if you mash 1 button, there is a good chance that at LEAST 1 guys is going to be desynched..... it might be an issue.

I will refrain from jumping to conclusions here though.

[Gallo]

I think this is a simple misreading of the patchnotes (this is common with Blizzard).

This is a good thing, not bad, for button mashers.

Basically it's the same as a /stopcasting macro for latency but with no stopcasting. It will send the signal to cast to the server no matter what your client says is going on.

Yes your GCD will trigger when you press the button to early. But it will get to the server and if the server says you you can't cast yet it will come back to you and cancel the early GCD. So the unused GCD will be twice your latency.

But if you hit the button while the unused GCD is active it will send another message to the server until the server says there is no cast and no GCD so button mash away my friends. Button mash away.

What this may do is melt there servers as their I/Os go through the roof.

[Stealthy]

I think this is a simple misreading of the patchnotes (this is common with Blizzard).

This is a good thing, not bad, for button mashers.

Basically it's the same as a /stopcasting macro for latency but with no stopcasting. It will send the signal to cast to the server no matter what your client says is going on.

Yes your GCD will trigger when you press the button to early. But it will get to the server and if the server says you you can't cast yet it will come back to you and cancel the early GCD. So the unused GCD will be twice your latency.

But if you hit the button while the unused GCD is active it will send another message to the server until the server says there is no cast and no GCD so button mash away my friends. Button mash away.

What this may do is melt there servers as their I/Os go through the roof.

As someone who lives outside the US (Australia) but has to play on US servers, this is bad bad bad!
The 'spell not ready yet', 'item not ready yet',' 'need more rage', 'need more energy', 'cannot do that yet' will all trigger the GCD, and I will have to wait for the server to confirm that there is no GCD - twice my latency, which is about 400ms. Double that is 800ms, close to 1 sec where I can't do jack.

I'm sure Blizz mean this as a fix, but how does that old saying go - "the road to hell is paved with good intentions"

Cheers,
Stealthy

[kadaan]

People are crying wolf with no facts imo.

Client spell cast requests are now sent to the server even if your player is already casting another spell. This eliminates the need for /stopcasting in macros to compensate for latency.

Where in there does it say it triggers the GCD?

[Xzin]

Seems based on that wording to not impact anything.....