Ok, I found a way to make it work. This very much feels like it's leaning on the border of exploits and ToS breaking though.
See this thread for an explanation of the method used (the original post is linked a few posts down).
I made one macro that does this and placed it in MacaroonButton101:
Code:
/run u=nil w=nil
/run a={"Aspect of the Viper","Aspect of the Hawk"} if UnitPower("player")/UnitPowerMax("player")*100<=15 then u=a[1] w=a[2] end
/run a={"Aspect of the Viper","Aspect of the Hawk"} if UnitPower("player")/UnitPowerMax("player")*100>=90 then u=a[2] w=a[1] end
/run if UnitAura("player",w) then EditMacro(GetMacroIndexByName("Manatest"),"Manatest",1,"/cast "..u,1,1) else EditMacro(GetMacroIndexByName("Manatest"),"Manatest",1,"",1,1)end
then dragged a macro called Manatest to MacaroonButton99 (using original macro interface),
then added the following two lines to the top of my dps macro
Code:
/click [nocombat] MacaroonButton101
/click [nocombat] MacaroonButton99
Testing on some target dummies, this seems to work (only out of combat, which is what I want).
Edit: Tested out in the real world, changed macro a tiny bit, works like a charm.
Connect With Us