WoW Classic macros, the hub

Classic runs the same macro system it shipped with in 2004. Here is the era-correct syntax, plus a macro page for every classic class that matters.

Era-correct syntax in one paragraph

Classic macros are the same macro system the game shipped with in vanilla, and the rules on this site's guide,command list, andconditionals page apply unchanged. Two era notes: conditionals that gate on a unit use the [target=unit,condition] spelling in classic-era documentation (the modern [@unit,condition] sort reads the same and works on current clients), and spell ranks are addressable by name:/cast Polymorph(Rank 1) is a real line in classic macros.

The class pages

  • Warrior: stances, charge, intercept, and the dead-health execute bind.
  • Hunter: the auto-shot weaver, pet control, and aspect habits.
  • Rogue: stealth openers, the sap-then-garrote key, and vanish discipline.
  • Druid: form toggles, the auto-bear, and mouseover heals without breaking form.
  • Mage: rank-1 polymorph, the focus counterspell, and the frost armor bind.

The conditionals that matter in classic

Three families do most of the era's macro work. All appear on theconditionals reference, and the class pages use them constantly:

  • Stances ([stance:1..3], [nostance:n]): warrior-only, and the backbone of every warrior bind. 1 battle, 2 defensive, 3 berserker.
  • Forms ([form], [noform], [form:n]): druid shapeshift state.[noform] means out of every form.
  • Stealth ([stealth], [nostealth]): rogue opener gates.

Mechanic pages that carry straight across

Everything on the technique pages works in classic: mouseoverheals, lazy chains, castsequence reset, and modifiers. The classic class pages take the strongest of those patterns and rewrite them in era syntax.

A warning that applies to every era

Stance and form numbering has never been officially documented, and classic re-releases shift it. The macros here use the widely-known numbering and mark where it matters; if a bind does nothing in your client, the first thing to check is the stance or form number, not the spell name.

Questions people ask

Do modern macro guides work in Classic?+
Mostly, with two syntax differences. Classic-era macro wikis write unit gates as [target=mouseover,help] while modern guides write [@mouseover,help]; both resolve on current classic clients. And classic-era spell ranks are real: Polymorph(Rank 1) is a legitimate cast line in classic macros.
Is the macro cap the same in Classic?+
Yes. The classic client keeps the 255-character macro limit and the same macro window. The techniques on the modern pages (conditionals, modifiers, castsequence) all work unchanged in classic.
Do Turtle WoW and other vanilla servers take these macros?+
Generally yes. Private servers run the vanilla-era client, so the classic-era syntax on this hub and its class pages transfers. If a custom server changes an ability name, that one macro needs a rename, nothing deeper.