Post#8 » Sun Nov 26, 2017 9:52 pm
I believe it's common knowledge that GCD is meant to limit burst damage by limiting the number of instant cast spells you can fire in a given time window. It was never meant to limit your ability to move.
I believe also that it's common knowledge that instant cast abilities should be able to be cast on the move. (by the way, non instant cast abilities that are meant to be cast on the move, like Healing Energy are interrupted while moving on the Z axis, i.e. flying/falling, but that's another issue)
If for instant cast abilities you were meant to stop moving for a GCD, then why this ain't true for all instant cast abilities which don't need 5 points into the AM/Shaman mechanic to become instant? For example, Radiant Gaze, doesn't gets interrupted while moving.
So we have instant abilities and "instant" abilities.
In my book, this is a bug. And it doesn't make it any less of a bug if we call it "Basic class mechanic" or if it has been around from Live. Otherwise we should be flagging as bugs all other instant abilities that can be cast on the move, without explicitly saying so.
ps: And i am 100% sure that technical wise, it's not the GCD that is causing this interruption, cause you only need to stop moving for like 0.1 second if you are talented enough, or like 0.5 if you are not, in order to fire any of those 5points AM/Shaman instants without getting interrupted, and not a whole 1.5sec which is what the GCD is equal to.
What is going wrong here is that the original spell is marked non instant, and the AM/Shaman mechanic implementation instead of doing it really instant like the other spells, it just reduces its casting time to 0. But on the client it's hardcoded that if a spell is non instant (ignoring the mechanic) and you cast it while moving, it sends a "interruption" message to the server. And the server blindly follows this interruption message, ignoring on his side as well, that your mechanic is at 5 points.
