November 2 Spell Vocabulary

The checker excludes removed spells and passive Venom. It recognizes Totemic Call, Shank, Death Mark, Oath of Light and Reckless Swings. Names confirmed by the notes can be checked while their exact current ranks and global cooldown remain unreconciled; those cases carry a warning.Blizzard: November 2 beta development notes, post 9, post 30732723, published November 3 UTC, retained source checked November 3, 2026.

The eighteen example patterns keep their existing syntax and evidence. A successful text check does not verify that your character has learned an ability or that its client behavior works in game.

Create and Edit a Macro

Type /macro in chat to open the macro window. Choose the general/account tab for a button you want on multiple characters, or the character-specific tab for a class button. Choose New, enter a short name, select an icon, and confirm. Paste the copied code into the text field, then choose Save. Drag the macro’s icon onto an action bar and bind that slot to a key.Reported, press or datamine, not confirmedSource: Forever beta 1.60.1.70205 MacroUI XML/Lua and command handlers, client locators, checked October 3, 2026.

To edit a macro, reopen the window and select it. Change the text and save again. The name/icon button changes those parts, so you don't need a new macro. The text field in the current client holds 255 characters and counts invisible characters, so keep the line breaks and avoid extra spaces when you're near the limit.Reported, press or datamine, not confirmedSource: Current macro UI locators, MacroFrameText and SaveMacro, checked October 3, 2026.

The copied spell names are English. On another client language, insert the spell from your own spellbook. The built-in macro help says to Shift-click a spell with the macro window open. Keep the conditions and replace the spell name in each /cast option. A spell named in the client data doesn't mean your character has learned it.Reported, press or datamine, not confirmedSource: Forever beta 1.60.1.70205 GlobalStrings, MACROHELPTEXT_LINE5; client source index, checked October 3, 2026.

Technical Notes
  • The name/icon button changes those parts without requiring a new macro, and the current client’s text field allows 255 characters.
  • Preserve the conditions and replace the spell name in each /cast option. A named spell in the client data does not establish that your character has learned it.

How to Read the Examples

These patterns use the familiar Classic macro form. In beta build 1.60.1.70205, the Forever client still sent /cast, /startattack, and /petattack arguments through its secure option parser. The conditions and composed patterns follow the linked community documentation, and a beta player’s pet report adds a mouseover /petattack example. The versioned dataset keeps client definitions, documentation patterns, and that player report apart as separate evidence types.Reported, press or datamine, not confirmedSource: Client command locators; Useful Macro Templates; beta pet report, checked October 3, 2026.

SyntaxIntended job
#showtooltip Spell NameShow the named spell’s tooltip; a bare #showtooltip follows the selected option.
/cast Spell NameAttempt a spell you have learned.
@mouseoverUse the unit under your pointer, including a unit frame.
help / harmRequire a friendly / hostile unit.
nodeadRequire a living unit.
@playerUse your own character.
mod:shiftChoose an option while Shift is held.
;Separate alternative spell options, read from left to right.

The table shows the documented macro grammar, not a new combat system. The first matching condition picks the option, and it does not check whether the spell is affordable, in range, off cooldown, or appropriate for the encounter. So a matching mouseover that is out of range can block the fallback cast.Reported, press or datamine, not confirmedSource: Macro question, post 2 and the current single-cast handler in client locators, checked October 3, 2026.

The friendly examples try a living friendly mouseover, then a living friendly target, then yourself. The hostile examples try a living hostile mouseover, then a living hostile target, and do nothing if neither matches. Bind mouseover buttons to a key so clicking an action-bar button does not move the pointer away from the intended unit.Reported, press or datamine, not confirmedSource: Community mouseover explanation, post 2, checked October 3, 2026.

Technical Notes
  • The conditions and composed patterns follow the linked community documentation; a beta player’s pet report also includes a mouseover /petattack example.
  • The first matching condition selects an option. A matching mouseover that is out of range can therefore block the fallback cast.

Check a New Button Before Relying on It

Read the example’s Prerequisites, limits, and evidence first. Confirm you have learned the spell and meet its normal resource, weapon, form, target, range, and line-of-sight rules. For friendly macros, try a friendly frame, a friendly target, and the self fallback in a safe situation. For hostile or pet macros, choose a safe target, because an auto-attack or pet command can begin even when the accompanying cast fails.

If a Shift macro fires another action, check the modified keybind. Community documentation notes that a keybinding can take priority over the macro modifier, so remove the conflicting binding or choose a different key. If the macro window cannot save or move a button, check the in-game interface and your action-bar addons. The beta discussion has a player report of that problem and later working macros, not a universal fix.Reported, press or datamine, not confirmedSource: Useful Macro Templates, modifier section; beta macro UI discussion, checked October 3, 2026.

The site’s syntax checks cover the listed command shapes, conditions, exact English spell names, and text length. They do not run the game parser and cannot confirm that a cast succeeds. Normal cast times, global cooldowns, spell restrictions, and pet behavior still apply. Use the class guides for class context and the addons guide when a replacement action bar affects the setup. For a gamepad setup, check the gamepad support guide for binding and interface caveats.

Technical Notes
  • Confirm the spell is learned and that its normal resource, weapon, form, target, range, and line-of-sight rules are satisfied.
  • The retained beta discussion contains a player report of the macro window problem and later working macros, rather than a universal fix.
  • The site’s syntax checks do not run the game parser or establish successful casts.

Macros by Class

Use the References

Check your character's learned ranks in the ability reference, and read the class and spec guides for role context before adapting a pattern.