How to Set Up Stance Macros as a Warrior in WoW Classic

In WoW Classic Era, put Battle Stance, Defensive Stance, and Berserker Stance on keys you can reach in combat. Use a macro with a stance condition when you want a single button to prepare an ability and then cast it on another press. Test the transition and the follow-up separately before relying on it in a dungeon.

Establish stance keys you can reach

1. Open the Spellbook and confirm which stances your Warrior has learned.
2. Put the stance spells or the existing stance bar bindings where you can reach them while moving.
3. Switch through the stances outside combat. Watch which action bar page appears after each change.
4. Confirm that the controls you need remain reachable on the new page. Place a shared utility macro on a bar that doesn't change if you want the same key in every stance.

Start with a dependable way to enter Defensive Stance if you tank. If you mainly deal damage, make sure you can enter the stance your next ability requires. Use clear icons or a consistent key arrangement. The goal is to know what your character will do before you press the button.

Check the stance after each test. If a key seems to have stopped working, the action bar may have switched to a page containing a different ability. Test the key from each stance rather than assuming that a working key on one page is bound to the same action elsewhere.

Add a guarded follow-up

This example changes to Berserker Stance when needed and uses Berserker Rage when you're already in the required stance:

#showtooltip Berserker Rage
/cast [nostance:3] Berserker Stance; Berserker Rage

Create a character macro with /macro. Copy the English example or replace the spell names with the ones shown in your client. The stance condition checks whether you are outside stance 3. When that condition matches, the first action is the stance change. Once you're in Berserker Stance, the next press can choose Berserker Rage. Check availability and timing before assuming it will fire immediately.

The two branches make it easy to test what happened. From Battle Stance, press once and verify the stance icon changed. Press again when the ability is available and check its result. Start in Berserker Stance next time and verify that the button goes directly to the ability instead of repeating the stance change.

Consider the cost of changing stance

Switching stance can affect the rage you retain. Your talents can change how much you keep. Watch the rage bar while practicing instead of relying on a number that may belong to another build. If you need rage for the next action, check how much will be available after the switch.

For example, suppose you are tanking and preparing an ability in a different stance. Make the switch at a safe time and check your resources before pressing the follow-up. Keep a clear way to return to Defensive Stance afterward if the pack still needs your attention. Changing stance is a tactical decision with consequences for the next action.

Avoid combining several unrelated actions while learning. A macro that changes stance, swaps a weapon, and tries an ability can fail at different points. Add only the behavior you can verify, and use separate buttons when you need to control timing or resources.

Fix a macro that stalls after the switch

Check which stance the character is actually in and whether the required stance has been learned. If the stance changed but the ability didn't fire, check the second press, any active cooldown, and the ability's own requirements. Verify that you still have the macro on the active bar page.

If the condition chooses the wrong branch, test the simple example without extra modifiers. Once it works, add other behavior one step at a time. Use a nearby easy fight to check timing after the out-of-combat test.

Keep the direct stance buttons even after you make a combined macro. They let you recover from a wrong state and choose a stance for a different ability. A good setup makes the transition and the follow-up predictable under pressure.

If you bind a different stance-dependent ability later, verify its requirements in the Spellbook first. Reuse the same pattern only after you identify which stance enables that ability.