Quote Originally Posted by 'Taliesin',index.php?page=Thread&postID=178459#pos t178459
Using macros with the sequential /click method will work so long as each macro has a chance of trying to do nothing. Your first example will not work because once it hits your shock macro, it will ALWAYS be trying to cast one or the other.
I was under this impression too; but some of the sxamples in this post would seem to be suboptimal if there weren't some sort of scoping benefit involved with breaking the macro's up into their own macros. Otherwise, this technique is really only beneficial in that it provides a workaround for the macro length limit, since you can have multiple sequences in a single macro.

Quote Originally Posted by 'Taliesin',index.php?page=Thread&postID=178459#pos t178459
I personally shy away from rhythm tapping out of preference, but can be very effective. I'm a pure /castsequence button masher.
As do I, but if this technique could be expanded to cast priorities... that would interest me a great deal

Quote Originally Posted by 'Taliesin',index.php?page=Thread&postID=178459#pos t178459
EDIT: Just noticed that you put /use 13 and /use 14 at the end. I would recommend putting those after the Purge macro so that all your damage spells gain the advantage of the spellpower boost. Having them at the end means that you never use your trinkets because Lightning Bolt will always fire off.
The timing would be identical. The Purge is first, but we are assuming that in most cases it won't fire. The trinkets are fired at the end because we anticipate that Flame Shock will be the first cast, and Lava Burst the second.. Ideally, we would be able to test to see if Lava Burst is off cooldown... and if it was, we would fire the trinkets right before Lava Burst...


I'm at work, so I can't test these out. I had read Vyndree's writeup on /click, but didn't see a great deal of use for it in my seup at the time. I suppose it can also be very helpful for script branching using /stopmacro [] within the macros on the clicked actionbuttons.