Quote Originally Posted by 'Sam DeathWalker',index.php?page=Thread&postID=176233#p ost176233
You use castsequence in many of your macros also ...
Ok, I shouldn't have to be explaining this AGAIN. This is another fact about macros that should be stickied. But since we're here, let me explain about castsequence lag. Again.

ok, there is a difference between

/cast lightning Bolt

and

/castsequence Lightning Bolt, Lightning Bolt

In the case of the first ,by spamming that command you are constantly issuing a command to the sever to cast a spell. As soon as the server recognizes that spell is done being cast, it immediately starts to cast the next.

In the case of the second, you spam the macro, but it doesn't send a command to cast the next spell until the cient gets a message that the first one has gone off. What this means is that the first lightning bolt casts, and before the macro sends the command to fire the second, it has to get a confirmation that the first fired off successfuly. In 0 latency world, its not an issue. Out here wher people play with 100-200ms latency, using /castsequence ends up tagging on .1-.2 seconds to your effective cast time, reducing the number of casts per minute from say 30 to 27.

Now there are a few exceptions where this doesn't apply, namely, using /castsequence to induce artificial cooldowns ala my method (because you're not casting anything) and instant cast spells, which still require a confirmation from the server for a success, but that confirimation falls within the GCD anyway, (hence why the 9/6/9 paladin macro works).