Classic druid macros

Every button already needs to work in every form. Druid macros are how the forms stop being a tax.

The travel bind that respects the moment

The form toggle that never fights you: no form means bear, in a form means travel. Built on the two form-agnostic gates, so it is immune to form-numbering drift:

#showtooltip/cast [noform] Dire Bear Form/cast [form] Travel Form

Walking you go bear (or cat, if you prefer and swap the name). Shaped, you travel. One key, both halves of the classic druid commute.

The auto-bear

The leveling legend: the moment combat starts and you are unshaped, the bind drops you into bear form. It is the macro version of a leveling druid's kneejerk:

#showtooltip/cast [combat,noform] Dire Bear Form

The gates do precisely the work: in combat and out of form. Not fighting, no-op. Fighting and shaped, no-op (you are already safe). It is the cleanest state macro on the classic pages.

Mouseover heals without breaking form

The healer bind: cradle the mouseover, fall back to self, and never leave your shape to do it. Classic-era unit syntax applies:

#showtooltip/cast [target=mouseover,help,nodead] Healing Touch; Healing Touch

Full treatment of the pattern is on the mouseover page; the classic-era [target=mouseover,...] spelling is the era-correct one.

The swiftmend chain

A healer's best friend needs a gate, because it eats a charge: swiftmend when the fight is on, rolling heal otherwise:

#showtooltip/cast [mod:shift] Swiftmend; [@player,combat] Rejuvenation; [@player] Regrowth

Shift pops the swiftmend charge. In combat, rejuve. Out of it, regrowth. All on the player unit, none of it form-dependent. This is thelazy macro structure doing exactly what it is for.

Forms are a state machine, so encode the state

Every druid bind earns its keep by gating on form state, which is why theconditionals page is the druid macro's real home. Numbered form gates exist ([form:1] and friends) but the numbering has never been documented and re-releases shift it; prefer the agnostic pair on this page and sleep sounder in every era.

Questions people ask

What do [form] and [noform] check, exactly?+
[form] is true while you are in ANY formshift; [noform] is true in caster form. The pair is form-agnostic, so form toggle macros built on them survive every client's quiet renumbering of the numbered form conditionals.
Is the auto-bear macro safe in a raid?+
No, and that is the point of its design: the version here gates on [combat,noform], so it drops you into bear form only when combat starts and you are not already shaped. In a raid where you want caster form, take it off the bar rather than re-gating it.
Do these macros work in TBC and WotLK Classic?+
Yes, with one tweak: later classic eras add Travel Form and Aquatic Form, so extend the travel bind's fallback chain with your era's forms. The [form]/[noform] gates are unchanged across eras.