5

Essential Macros

Posted February 16th, 2010. Filed under Macro
No Gravatar


Maintenance Tuesday… since I can’t login I figured I’d share some favorite macros.

Space Cadet Rune Strikes

In the heat of the moment, I’m guilty of not always seeing abilities that proc.  What this macro does is fires Rune Strike on each cast of Obliterate.  If Rune Strike’s not active, the error messages are suppressed. This is good; Rune Strikes add threat… threat is good… My example is for my Obliterate ability, but I have the same macro (substituting Blood Strike, Frost Strike, etc).  Your mileage may vary with runic power, so adjust to your own playstyle.

#showtooltip Obliterate
/cast Obliterate
/script UIErrorsFrame:UnregisterEvent("UI_ERROR_MESSAGE");
/cast !Rune Strike
/script UIErrorsFrame:RegisterEvent("UI_ERROR_MESSAGE");

Oooomph to Howling Blast

I love this one, especially on an AoE pull. It activates Deathchill and then casts Howling Blast. The crit damage really helps seal on aggro at the start of an AoE pack encounter. Note, you could apply the same to Frost Strike, but I like having Deathchill available for the next pack and I’d rather not burn on a single target.

#showtooltip Howling Blast
/script UIErrorsFrame:UnregisterEvent("UI_ERROR_MESSAGE");
/cast Deathchill
/cast Howling Blast
/script UIErrorsFrame:RegisterEvent("UI_ERROR_MESSAGE");

Summon Dead DPSer… or my Pet

I have this one keybound to CTRL-P…. If I am targeting a dead group member, they are revived with Raise Ally.  That, my friends, is pure fun. If not,  I call my ghoul with Raise Dead (gotta get more Corpse Dust!)

#showtooltip Raise Dead
/cast [target=dead,help] Raise Ally; Raise Dead

One Button Hearthstone

Saves some space on the action bars…  Allows for mouse-button control to Hearthstone (using the regular left-click or button 1), Death Gate with a right-click (button 2) or my lovely Argent Crusder’s Tabard (using the thumb button or button 4).  Rich toons can substitute the Ring of Kirin Tor or add to button 5.

#showtooltip [button:2] Death Gate; [button:4] item:46874; Hearthstone
/script UIErrorsFrame:UnregisterEvent("UI_ERROR_MESSAGE");
/cast [button:2] Death Gate; [button:1] Hearthstone
/use [button:4] item:46874
/script UIErrorsFrame:RegisterEvent("UI_ERROR_MESSAGE");

Tech Notes

Most of the above should be pretty self-explanatory.  There are a few notes and options to consider…

The exclamation point in front of Rune Strike prevents the ability from being toggled off if it was already active — that should never happen, but a single character is worth the error check.

The /script UIErrorsFrame:UnregisterEvent("UI_ERROR_MESSAGE"); and /script UIErrorsFrame:RegisterEvent("UI_ERROR_MESSAGE"); commands suppress those annoying “I can’t do that yet” messages. Anything nested between the Unregister and Register is error-reporting-free.

You can add conditionals for secondary spec checking. For example, with Engineering, I have Hyperspeed Accelerators on my gloves. I also like to toss in Rune Strikes while DPSing for the extra damage, so I use the same macros in my second spec. I just add a line after the /cast !Rune Strike like /use [spec:2] Gauntlets of the Stouthearted Crusader to use my haste trinket only in my secondary talent spec… Pretty nifty, eh?

If you have enjoyed this entry. Please feel free to bookmark it using your favorite social bookmarking site

5 Responses so far

  1. NeedineNo Gravatar says:

    I whould urge you to do one minor change to your macros

    instead of “/cast Rune Strike”

    use “/cast !Rune Strike”

    also you can exchange

    /cast with /use if your getting near the max line nr

    /use !Rune Strike

    basicly you can cut down your first macro to

    #showtooltip Obliterate
    /use Obliterate
    /use !Rune Strike

  2. antituxNo Gravatar says:

    Hey, actually your “Rune strike” macro should look like this:

    #showtooltip Obliterate
    /cast Obliterate
    /script UIErrorsFrame:UnregisterEvent(“UI_ERROR_MESSAGE”);
    /cast !Rune Strike
    /script UIErrorsFrame:RegisterEvent(“UI_ERROR_MESSAGE”);

    That way, you don’t un-check rune strike every time you hit obliterate.

  3. ArtieNo Gravatar says:

    Fixed rune strike — was there on deathchill but omitted on runes… thanks for the catch!

  4. Just found this post and although I’m more into rogues than DKs I find it very useful! Just checking the possible options of using the macros for different skills/classes.

    @Needine – didn’t know the /cast = /use thing, thanks for sharing! :)
    rogue leveling guide´s last blog ..Horde Rogue Leveling Guide – Start Leveling Your Horde Rogue My ComLuv Profile

  5. Thats such a clever macro I have been looking for this everywhere. thanks for sharing, im off to cast a few strikes. LOL at ‘Rune Strikes add threat… threat is good…’.

Leave a Comment





CommentLuv Enabled
This site is using OpenAvatar based on

Blade Barrier is using WP-Gravatar