A WoW macro is a list of slash commands activated from a button. It is not a scheduler that waits for one combat spell to finish before casting the next. If your macro contains several ordinary cast commands and only one spell works, the global cooldown may be the explanation rather than a missing punctuation mark.
For a first Retail macro, create the smallest useful button, prove that it works, and add complexity afterward. This guide addresses in-game commands, not external automation. The setup and limitations come from documented references; no current-client testing is claimed.
Create the macro in the right scope
Open the macro window with /macro or /m. Choose General if the macro should be shared across characters on the account, or choose the character-specific area if it belongs to this character. Select New, give it a recognizable name and icon, enter the commands, save, and drag its icon onto an action button.
Write each command on its own line. Naming a macro does not place it on your action bar automatically, so include that final drag in your setup check. A correctly written macro hidden in the macro window is not the same thing as the button you are currently pressing.
General scope shares the macro definition, not the abilities it references. A character without the named spell cannot acquire it by using another character’s saved command. Check the spellbook before treating a shared button as universally usable.
Start with one known spell
The source’s minimal example is /cast Shadow Word: Pain. Use that example only on a character that actually knows the spell. Otherwise choose a known ability and enter its correct name. The initial goal is behavior comparable to putting that ability directly on the action bar.
Warcraft Wiki’s macro-making guide documents setup, feedback, and casting behavior. Its question-mark icon can derive an icon from spell or item commands, while #show and #showtooltip provide feedback controls. Good feedback helps identify a button; it does not prove the ability is learned, in range, or currently usable.
Keep your original spell button available while checking the macro. If the ordinary spell button also fails under the same conditions, adding more macro lines is unlikely to solve the underlying cast requirement.
Understand why several cast lines fail
Commands are processed during the button activation, not spaced into a timed combat sequence. Most spells and some items trigger the global cooldown. A later ordinary /cast line cannot simply wait through that cooldown and resume when the first spell is finished.
| Button contents | What to expect | What not to infer |
|---|---|---|
| One known spell | A minimal cast attempt | It bypasses range or resource rules |
| Several ordinary combat spells | Global-cooldown restrictions still apply | One click schedules the rotation |
| Text and an emote | Multiple harmless commands can execute | Multiple combat casts are unrestricted |
| A limited off-GCD combination | May work if the actions permit it | Any arbitrary pair can be combined |
The guide explicitly identifies old multi-cast fallback examples involving Overpower, Execute, Mortal Strike, and Sunder Armor as nonfunctional. Do not revive an old combat example just because it looks more sophisticated than your single-spell button. Historical examples are not current Retail recommendations.
There are limited combinations involving instant, off-global-cooldown actions. That exception requires checking the particular actions; it is not permission to assume every spell and item pair works together. Nor does it provide a way to automate combat decisions.
Use a harmless multiline check
For a separate interface test, the documented example places /y Everybody, dance now! on one line and /dance on the next. It demonstrates that a macro can contain multiple slash commands without claiming that multiple combat abilities can ignore their normal restrictions.
Run any text example considerately, away from repeated group-chat spam. Its diagnostic purpose is narrow: confirm that the button you placed is executing the text you saved. After that, return to the one-spell example rather than repeatedly adding unrelated commands.
The general Macro reference helps distinguish the command-list concept from an external program. You do not need input automation, loops, or a timer to make an ordinary action-bar macro. Those are not repairs for a global-cooldown limitation.
Repair the button one layer at a time
Suppose a copied macro shows the expected icon but fails to cast. Remove everything except the one /cast line, confirm the exact spell name, check that this character knows it, and compare it with the normal ability button under ordinary valid casting conditions. Then verify you dragged the edited macro, rather than a different similarly named button, onto the bar.
Restore optional feedback, text, and item commands individually. For items, distinguish an item-use intention from a spell-cast intention; do not expect an item name after a spell command to solve the mismatch. If failure begins after a particular addition, you have isolated the next thing to inspect.
Do not mix this troubleshooting with build allocation. The talent-loadout guide concerns selecting talents, not executing slash commands. If another character cannot use the spell because its role or specialization differs, consult the class and specialization explanation before rewriting the macro.
FAQ
Can a macro wait for the global cooldown?
Not as a timed rotation scheduler. Listing more ordinary casts does not create pauses between them. Do not attempt to fix that limitation with game-freezing loops or external input automation.
Why does the icon look correct when casting fails?
Feedback can identify the intended spell without satisfying its requirements. Check spell ownership, range, and ordinary usability separately, then compare the minimal macro with the direct spell button.
Does General scope teach the spell to my alts?
No. It shares the macro definition across characters on the account. Each character still needs the underlying ability and valid conditions for using it.
Related guides
- How to Import, Save, and Share a Talent Loadout in WoW Retail
- WoW Classes vs. Specializations: How to Choose Your First Character
- Tank, Healer, or DPS? What Each WoW Group Role Actually Does
Explore the World of Warcraft Guides collection.
Sources and editorial notes
This is a source-based editorial guide, not a personal gameplay test, current-season ranking or guarantee of results. Version-sensitive mechanics, access requirements and item rules should be checked against the current client and developer information. Historical and preview material is not certification of current live behavior.
This guide covers World of Warcraft Retail within the stated source scope, not interchangeable Classic, progression or regional client rules.
Cover: an original LootGo editorial diagram, not an official game image, gameplay screenshot or exact interface.