Quote Originally Posted by 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.
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