GCD Hack?

[glalizas]

I found some GCD hacks but they are not supporting 4.1 . Is there any for 4.1?

[DrakeFish]

Wasn't GCD 'hack' included into WoW in patch 4.0 or something? They made an option for it so you could reduce your client-side GCD (which does the same thing that GCD 'hack' was doing).

[Anonie]

No. GCD hack back in 3.3.x was to bypass the client side GCD counter so that you effectively had like a .5 second GCD instead of the normal wow enforced fastest GCD that geared toons with tons of haste lowering GCD down to 1 second. Now, 4.0.x, server side does the GCD processing as well as the client side. The GCD function that is in settings lets you kind of queue up the moves if it is within the whatever time setting that you have in the options.

For example, it is set to 250 ms (which is kinda normal), so within the 250 ms time just before you finish casting a spell or GCD cooldown (like nourish, fireball, crusader strike, etc..), you press your next spell, (like lifebloom, pyroblast, judgement) and your wow client will send the msg that you want to cast lifebloom or pyroblast, and it'll queue it up to cast as soon the gcd or cast timer is finished according to server side. However, if you press the button to cast the spell 300 ms before the end of the cast, the wow client/server will ignore the cast message and not queue it up.

There's a slight variation of what happens when there's sudden burst lag and everything freezes for a good few seconds, but under normal conditions, this is what happens.

Edit: TLDR: the GCD hack from ICC era has been forever fixed and GCD is monitored both server side and client side.