Quote Originally Posted by kadaan
People are crying wolf with no facts imo.

Quote Originally Posted by 2.3 Patch Notes
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?
No, people are not crying wolf. Here's a link to blue posts about it:
http://forums.worldofwarcraft.com/th...id=1&pageNo=11

The posts that highlight the problem:

Post from Pjamin, note - he's quoting Slouken (blue)
* The client can't initiate casts more often than the global cooldown, so it's only a problems for spells with longer cast times than the global cooldown.
So my 1.5 sec Flash of Light Spell is always penalized by latency?

Edit: With 500ms latency I might as well down rank my HL as it would heal for more and be more mana efficient or am I missing something obvious?

* in 2.2 you couldn't initiate a cast on the client before the client received notification from the server that the previous cast had completed.
But I could circumvent that with quartz and stop casting.

* This discussion doesn't really involve people using /stopcasting, because they aren't the ones spam casting. In 2.2 they would interrupt their previous cast, losing the time already spent casting, and in 2.3 they wait the round trip latency for the error message from the server, both of which are less efficient than getting the timing right.
But a click 1ms too quick triggers a penalty of GCD + latency, yes? Does it cancel my previous spell?


Post from Slouken (blue)

So my 1.5 sec Flash of Light Spell is always penalized by latency?
Nope, assuming constant latency your 1.5 second Flash of Light can be cast back to back.
0.0s: Client starts casting Flash of Light, starts 1.5 second global cooldown
0.25s: Server starts casting Flash of Light
0.5s: Client sees Flash of Light start casting
1.5s: Client finishes global cooldown, starts casting Flash of Light, starts global cooldown
1.75s: Server completes casting Flash of Light, starts casting new Flash of Light
2.0s: Client sees Flash of Light complete and new cast start

But I could circumvent that with quartz and stop casting.
Yep, now you don't need stop casting.

But a click 1ms too quick triggers a penalty of GCD + latency, yes?
Yes.

Does it cancel my previous spell?
No.

Cheers,
Stealthy