There is one indispensable tool within my arsenal of abilities in World of Warcraft: the macro.

I utilize key bindings that call macros to perform actions on my target for practically every healing ability, but there is one in particular that I would be extremely lost without. Quoted below is the macro, with an explanation of the functions following:

---

TEMPLATE

#showtooltip spell name
/script UIErrorsFrame:Hide()
/use trinket slot
/script UIErrorsFrame:Clear(); UIErrorsFrame:Show()
/cast [help][target=mouseover,help,nodead][target=player] spell name

EXAMPLE

#showtooltip Regrowth
/script UIErrorsFrame:Hide()
/use 14
/script UIErrorsFrame:Clear(); UIErrorsFrame:Show()
/cast [help][target=mouseover,help,nodead][target=player] Regrowth

---

Basic Explanations

• #showtooltip spell name
  This line is merely used to show the tooltip of the specified spell when hovering over the button with the mouse. In addition, if using the question mark icon when creating the macro this will change that icon to be the icon of the spell specified. very helpful if you want to ensure you know the icons of the spells you want to cast in the event you ever have to do so with a completely unmodified user interface, though not nearly as much of an issue now that macros are stored server-side.
• /script UIErrorsFrame:Hide()
  This handy little line of code simply suppresses errors relating to the next line. Basically, there will still be a warning if the trinket is not available for use yet, but no annoying boxes to become distracting.
• /use trinket slot
  The trinket slots are slots 13 and 14. Be certain you have trinkets where you want them and tied to the spells you want them tied to if using these macros. My personal preference is to “pop” trinkets that increase spellpower as often as I can, thus tying that trinket to whatever spell is cast most often (on my Druid I actually tie it to Rejuvenation, and on the Priest to Prayer of Mending).
• /script UIErrorsFrame:Clear(); UIErrorsFrame:Show()
  This section clears the error “boxes” and turns them back on, ensuring any pertinent errors you may need to see are shown. To be honest, it has been so long since I’ve seen any errors other than lua errors related to addons I’m not even sure this script is still needed. I’ll continue to keep it in every macro I make that calls trinkets anyway though.
• /cast [help][target=mouseover,help,nodead][target=player] spell name
  This is the “meat” of the macro, and the most important part. As such, the components are broken down a little further:
  • [help]
    This portion merely means the recipient has to be friendly in order to cast the spell, and the ordering of these sections is important. Having this section first means that if I have a friendly target actually targeted then the spell will go to them, regardless of where my mouse is on the screen. Further, if I have an unfriendly target actually targeted, it will proceed to the next portion of the macro (very useful for keeping a boss targeted and still healing without any issue, reducing the number of additional unit frames I need on the screen to be effective).
  • [target=mouseover,help,nodead]
    This portion means that the target under my mouse, if friendly and alive, will be the recipient of the spell called upon in the macro. The beauty of using a mouseover macro is that there is no need to click on the target first, they simply have to be highlighted under the mouse.
  • [target=player]
    Closing out the macro, this portion casts the called action on me if neither of the first two conditions are met.

Quick and dirty, but hopefully beneficial. This post was unplanned, but after having mention made from a guildmate about wanting to talk to me about the macros I used I figured I would add a post also, giving a good place to reference while explaining macros used. Enjoy!

UPDATE:

The original post had a couple of errors, which may have caused some frustrations. The editor I use converted some characters when I sent it to the blog. This was caught by a guildie attempting to use the macro, and subsequently any post I place macros in I will ensure I proofread the post from the website instead of just my editor from this point forward.