Printable View
All fair enough.
Even with Macaroon going away, however, Jamba seems to be going strong and provides the same benefit of extra macro length.
I do like the concept of using /click for organization. Especially since Jamba allows you to "name" the button so you can call:
/click JMB_TargetBlizzardsSpecialCaseStuff
which then is simply:
/target frost tomb
/target chaotic rift
/target guardian
/target TotemOfDeath1
I just discovered after some testing a potentially useful function for /click
/stopmacro
Here's what I just tried:
/click MacaroonButton96
/click MacaroonButton97
On MacaroonButton96:
/stopmacro [harm]
/cast Spell1
On MacaroonButton97:
/cast Spell2
If I don't have something hostile targeted, Spell1 will cast and Spell2 will fail because of GCD. If I do have something hostile targeted the "sub-macro" will fail at /stopmacro and then the "master-macro" will cast spell2.
This has potential because it means you can almost form a logic branch with a macro. Not exactly ... but it is better than just having a single hardstop.
Thoughts? Impressions?
It is not a whole lot different from using [help] and [harm] or [nohelp] and [noharm] logic in macros.
But having it in two sequences, lets you mix and match the pieces.
IE, it is still modular, so you don't have to have help/harm logic in a single macro.
The most important reason is to remove the "time lag" between casts that you get in a /castsequence. There is a lot of information floating around about this. Unless it has been changed? Not to my knowledge though.
Unless of course your /castsequence macros contain a single spell and some spacer commas. It won't make a difference in DPS with these. Wasn't sure if this is what you inferred in your post. If so, then the benefits of /click is basically what everyone else has already said :P
It won't make any difference in DPS if you're using instant cast spells either.