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.Originally Posted by 'Taliesin',index.php?page=Thread&postID=178459#pos t178459
As do I, but if this technique could be expanded to cast priorities... that would interest me a great dealOriginally Posted by 'Taliesin',index.php?page=Thread&postID=178459#pos t178459
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...Originally Posted by 'Taliesin',index.php?page=Thread&postID=178459#pos t178459
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.
Connect With Us