Formatting Macros Edit

Note: Commands for some of the older macros have been modified significantly. Where possible, please validate and mark with last working patch or version number.

When editing a macro on the Wiki please:

  • name it, describe what it does, and use a 'space' before each command for the 'code box'
  • note the version of WoW that you tested it in
  • if moving from another page, remove it from the old page
  • follow this Macro formatting example:
==== Macro Name ====
 /y Hooray, I made a macro!
* Use: This yells, "Hooray, I made a macro!"
* Works in 5.4.2
which creates:

Macro Name Edit

/y Hooray, I made a macro!
  • Use: This yells, "Hooray, I made a macro!"
  • Works in 5.4.2

Dull Axe ApplicationEdit

Okay, I started here because I understood most of the language already in place, even if it was nonstandardised. I'm doing some dinking with some of the deleted macros, and will be adding back in the ones I can make work in the appropriate places. Remember, none of this information is gone - it's just there in the history, so feel free to check back and see if there's something you can salvage in the older stuff. If you had something in the deleted section that you can explain better and bring up to snuff for the current patch, please feel free to add it back in - if you need help with the language, send me a message on my talk page.

The 'Macroformat' template seems unnecessary and cluttering to put on the page itself, and I think is better served here on the talk page, where people who are looking for help on how to edit the page will have the information presented to them. --TalenLee (talk) 22:48, November 2, 2009 (UTC)

Other maintenanceEdit

I deleted the ranks in the macros since the new system will cast the highest rank if you leave out the rank numbers

Ghost Wolf/Mount Macro Edit

The current one doesn't make much sense to me, I'm a newbie to macros, but wouldn't it be better laid out like this:

#showtooltip [combat,nomounted] [Stance:1] Ghost Wolf
#showtooltip [nostance,nocombat] Standard Mount
/cast [Stance:1] [combat,nomounted] Ghost Wolf
/use [nostance,nocombat] Standard Mount

It sort of works even without the dismount, but I'm waiting for response from the Macro Gurus out there.

--TheMadness 00:03, 8 September 2007 (UTC)

After a quick raid in #wowwiki-lounge, thanks to the help of Mr_Rabies2 and cogwheel I fixed it. --TheMadness 20:10, 8 September 2007 (UTC)
Fixed again for Redflaregraf (talk) 11:12, March 2, 2011 (UTC)

I got a macro for my shammy, and added /Cast [running] Ghost Wolf in it, so that if I am moving it will cast GW otherwise mount up. What is weird is that it works but I get an error message saying "unknown macro option 'running'". Is there a way to script in "running" as a dependency and I am just doing it wrong? As I said, it does work as is, so it is not a huge deal, but was more curious why I was getting an error message though it was working....and would rather have it written right and not have to see that error message. Thank you in advance for any help.

First off, remember to sign enteries ;). Second, running isn't a macro option, and that why you're getting an error. You can keep the macro with out the [running] part, and it will still work as it will try to cast the mount, fail, and then try to cast GW. If you're standing still it will cast the mount instead, and fail on GW as the GCD isn't up yet. Hope that helps! Decibal (T / C / [Wowhead]) 05:08, 20 March 2009 (UTC)

Windfury application for dual wielding Edit

Two clicks/button presses on this macro will apply different ranks of Windfury to your main hand and off-hand, however if you are wearing a shield or using a two-handed weapon it will be buffed with highest rank, regardless.

#showtooltip Windfury Weapon
/cast [equipped:shields/two-hand] Windfury Weapon(Rank 5)
/stopmacro [equipped:shields/two-hand]
/castsequence Windfury Weapon(Rank 5), Windfury Weapon(Rank 4)

A word of explanation: applying different Windfury ranks is essential since same ranks cannot proc off both weapons at the same time. This macro makes buffing your weapons easier.

WoW Icon 16x16 Patch 2.1.0 (2007-05-22): Mixing two different ranks of "Windfury Weapon" while dual-wielding will no longer increase the number of "Windfury Weapon" procs.

-- I deleted this macro because it is no longer useful. I put it here for reference. - routine error.

Enhancement T5 2-piece macro Edit

I just got 2 pieces of T5 enhancement set, and came up with nice macro to help managing those procs:

/cast [button:2] [target=player] Lesser Healing Wave
/cast [button:1] [target=targettarget] Lesser Healing Wave

This will cast LHW on yourself when clicked with left button (as you are on left side of the mob you are targetting on default UI) and to the player that the target is attacking (normally the tank) when clicked with right button. I found this really useful, though i dont know if thats something that should be on wowwiki page, not everyone have that set :P

Swithu 00:36, 13 December 2007 (UTC)

Lightning or any shield macro Edit

Just wondering if there is anyway to only cast a shield buff, if there is not already one present?

Also, is there a command for "Heal on mouseover of a player's unitframe"? I have a simple "Heal on mouseover" but it does not work on unitframes.

/stopcasting change Edit

Maybe it's just me, but I seem to recall in the patch notes that /stopcasting is no longer required in macros due to the client/server spell queue change. I can't site my source as I don't remember what patch, does anyone know for sure one way or the other?

Decibal (T / C / [Wowhead]) 21:47, 25 May 2008 (UTC)

That's right - you no longer need to start a spell-spamming macro with /stopcast - there's a short period - about 1/4 to 1/2 a second as far as I can see - before the end of a spellcast when you can hit the next one and it'll queue up. Djnw (talk) 08:26, 26 May 2008 (UTC)

Several macros use the mouseover feature, after some experimenting it seems that the mouseover can target your totems (when focussed on the main screen) resulting in an unfortunate immune message at the end of e.g. the heal. If the "raid" modifier is added then this prevents targeting your totems, so

  1. showtooltip

/target [modifier:ctrl] player /cast [exists,nodead,help] [target=mouseover,nodead,help] [target=focus,help] [] Lesser Healing Wave; /targetlasttarget [modifier:ctrl]

would become:

  1. showtooltip

/target [modifier:ctrl] player /cast [exists,nodead,help] [target=mouseover,nodead,help,raid] [target=focus,help] [] Lesser Healing Wave; /targetlasttarget [modifier:ctrl]

this issue seems to apply to several macros mentioned here.

Macros.. Where are they now? Edit

Good Day..

A couple days ago, I was in the Macro > Shaman article. There were large numbers of Macros for v3.2. For non-macro writers that page was VERY useful, even if they had to be tweaked. Were they simply moved to another location? I checked History, but didnt see the Macros. Did see a lot of article by other people. Please, how do I get to the old macro page?

Much Thanks Lynlee

--Lynlee (talk) 17:16, November 4, 2009 (UTC)

Click on the 'History' tab, then go back to the version of the page before 'Dull Axe Application.' --TalenLee (talk) 21:48, November 4, 2009 (UTC)

/* Shock Cycling */ Edit

I moved Shock Cycling from ele to gen as its good for all specs.

Remember to sign your posts. I agree with your decision on it though and I just edited the writing. I'll test the macro in soon. Redflaregraf (talk) 11:53, March 2, 2011 (UTC)
I verified that the macro still works fine and added a small addition to the section --Redflaregraf (talk) 06:49, March 3, 2011 (UTC)

Instant Crit Heal Edit

Removed this macro today because Tidal Force hasn't been available since 4.0.1 according to wowwiki. One more down.. Redflaregraf (talk) 11:30, March 2, 2011 (UTC)

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.