-
Here's how I would do it:
MacroSequence
Code:
FrostNova = { [[
/stopcasting
/cast Frost Nova
]] },
NovaSequence1 = {
reset = { seconds = 25 },
"/click FrostNova", "", "", ""
},
NovaSequence2 = {
reset = { seconds = 25 },
"", "/click FrostNova", "", ""
},
NovaSequence3 = {
reset = { seconds = 25 },
"", "", "/click FrostNova", ""
},
NovaSequence4 = {
reset = { seconds = 25 },
"", "", "", "/click FrostNova"
},
Normal Macro (Mage 1)
Code:
/click NovaSequence1
Normal Macro (Mage 2)
Code:
/click NovaSequence2
etc.
All the normal macros should be bound to the same key.
@legality :) - MacroSequence has been around for quite a while without issue, and it is from Cogwheel who is one of the UI & Macro forum MVPs (whatever Blizzard calls them -- green posters). It's all in-game code, and it's not doing anything that violates the spirit of the TOS either. IMO it is fine, but you should decide for yourself.
@wowphreak - Thanks for the AHK tip! It is a bizarre little language... :)
-
thanks for the examples, that is pretty slick.
-
Thanks for the examples. Now my 2nd team rushing to 59, then one more team i will level before RAF is out and then i'll sit and think through my setup for outland instance grinding.
One question though. What is "/click" command? Never seen it in solo-play macro (i'm rather new to multiboxing)
-
/click simulates a button press. The WoW APIs let mod authors create virtual buttons and attach macros to them. When you do "/click SomeSequence" in a normal macro you are simulating a L-click of the invisible button named "SomeSequence", which MacroSequence has created with the sequence macro you specified.
More info on /click here:
http://www.wowwiki.com/Making_a_macr..._button_clicks
