Printable View
I've seen a macro command for casting a sequence of spells. What if you wanted to cast the same one spell on a sequence of targets? I have my Priest who has the Stamina buff and now the Shadow Resist buff. I want to use the same macro to cast one of these buffs on different target each time. Is their a way to do this?
Sentack
Not with macros. Get the addon SmartBuff. You can set group buffs, and bind the "buff all" command to a key.
Yeah, SmartBuff makes buffing largely automatic. If that somehow doesn't work for you another way would be to use the addon MacroSequence. It lets you construct sequences out of any macro-able command (even other whole macros), not just spells.
Which is technically automation and a bannable offense? I might be mistaken. :P Or is that MacroSequence just changing the contents of a legit macro so the next time you press the button something else happens?Quote:
Originally Posted by 'Chorizotarian',index.php?page=Thread&postID=54288 #post54288
No, MacroSequence is fine. It provides an alternative macro system where you prewrite "sequences" in a separate LUA file that is loaded by MacroSequence. You can then run any of the sequences with a /click command as you would a normal macro.Quote:
Originally Posted by 'Kaynin',index.php?page=Thread&postID=54290#post54 290
Why isn't MacroSequence automation?
1) It's entrirely in-game using Blizzard's APIs
2) The specific purpose being discussed here is readily achievable by normal addons and within the scope of what addons / macros are intended to do
3) It comes from Cogwheel, a macro forum MVP
No. SmartBuff uses protected functions that are NOT accessible duringQuote:
Originally Posted by 'Kaynin',index.php?page=Thread&postID=54290#post54 290
combat. Blizz still allows smart targeting in addons out of combat.
Ah alright. Makes sense too I suppose.
Yeah, this all happened during the 2.0 patch timeframe when they broke the hell out of everything including Decursive and eePanels, two of the most used raid mods around. What you'll notice in some of those is that they can one-button buff/decurse but only after the combat has ended. They don't figure it's a big deal out of combat as that's just tedium time anyway. ;) Here's the skinny (direct link to the WoW 2.0 UI change list ) with the relevant portion highlighted:
Quote:
The protected code mechanism introduced in 1.10 has been extended to cover more functions. Blizzard code is considered secure, all other code is untrusted. The following function types are restricted for AddOns:
* Movement is never allowed.
* Spell casting and targetting (including focus) are only allowed using secure templates or special slash commands (not /script).
* Programatic modification of macros, key bindings, and the action bar page only allowed outside of combat.
* Trading, placing auction bids, querying LFG, crafting, and reloading the UI are only allowed interactively.
* Action buttons and targeting frames are now "protected". Protected frames cannot be programmatically moved, shown or hidden, or have their attributes (unit, action, etc) changed during combat.