# Hunter macro test cases — unperformed plan 31 canonical records: 31 current and 0 historical. Every case state is NOT_RUN. No client execution or successful result is represented by this document. Canonical source: macros/hunter/pack.json. Exact body hashes identify content, not a game build. Requirements, targeting order, modifiers and limitations below are copied from the canonical records. Their source qualifications remain intact. Authored command clauses are planning prompts, not a certified game parser or a promise a spell succeeds. ## hunter-auto-shot — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 59c099e184a85b7de40733a9df82557d1e1811b8958ffa4890a02de38ef57a52 Exact canonical body (plain text): ```text #showtooltip Auto Shot /cast [harm,nodead] !Auto Shot ``` ### Requirements - Learned Auto Shot; the current source records the first rank at level 1. Confirm each required rank in your own spellbook. - Usable ranged weapon and compatible ammunition; living enemy 8–35 yards away. ### Target order - Current living hostile target - No living hostile target: no cast ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Does not select an enemy, send the pet, stop for crowd control or maintain safe distance. Confirm non-toggle behaviour in Forever. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [harm,nodead] !Auto Shot. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] The ! prefix requests non-toggle behavior. Compare initial and repeated presses with the relevant aura/attack state already active; exact client behavior remains to be observed. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-raptor-strike — 1.1.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 0a98110c17c7e1d41ed7c5bb57685c133a0fb14fdf54f4bf824f043942b2dc5a Exact canonical body (plain text): ```text #showtooltip Raptor Strike /cast [harm,nodead] Raptor Strike ``` ### Requirements - Learned Raptor Strike; the current source records the first rank at level 1. Confirm each required rank in your own spellbook. - A usable melee weapon and a living enemy in melee range. ### Target order - Current living hostile target - No living hostile target: no cast ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Raptor Strike queues the next melee swing. It is not an instant ranged attack. - No separate attack-start command is included. Automatic attack behavior, including when the ability cannot be cast, still needs testing in the Forever client. Avoid pressing this key while preserving crowd control. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [harm,nodead] Raptor Strike. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-arcane-shot — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 6342e98260ee7878020feb669866a4e870988299d2c21a80dfa66c352b952355 Exact canonical body (plain text): ```text #showtooltip Arcane Shot /cast [@mouseover,harm,nodead][harm,nodead] Arcane Shot ``` ### Requirements - Learned Arcane Shot; the current source records the first rank at level 6. Confirm each required rank in your own spellbook. - Usable ranged weapon and ammunition; target 8–35 yards away. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no action ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Does not start Auto Shot or send your pet to the mouseover enemy. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Arcane Shot. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-hunters-mark — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: a0ee984996cbcd504d43ee62d49f9aeca0d18e2e8bab33d8af7115a93a5fc188 Exact canonical body (plain text): ```text #showtooltip Hunter's Mark /cast [@mouseover,harm,nodead][harm,nodead] Hunter's Mark ``` ### Requirements - Learned Hunter's Mark; the current source records the first rank at level 6. Confirm each required rank in your own spellbook. - Enemy within 100 yards. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no action ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Marking does not order a pet attack or begin Auto Shot. HARM identifies its enemy target, not direct damage. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Hunter's Mark. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-concussive-shot — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 7b93b02b946deb5d916f71fa9e1ffaf7c6a14732db4b82845945e649787ed56c Exact canonical body (plain text): ```text #showtooltip Concussive Shot /cast [@mouseover,harm,nodead][harm,nodead] Concussive Shot ``` ### Requirements - Learned Concussive Shot; the current source records the first rank at level 8. Confirm each required rank in your own spellbook. - Usable ranged weapon and ammunition; enemy 8–35 yards away. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no action ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Does not add Auto Shot or a pet attack that could defeat a control plan. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Concussive Shot. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-wing-clip — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: d8d5e33219f9e9e98213820fe8bdd49e026648d76e2c3819bdc4d69c40b027c6 Exact canonical body (plain text): ```text #showtooltip Wing Clip /cast [@mouseover,harm,nodead][harm,nodead] Wing Clip ``` ### Requirements - Learned Wing Clip; the current source records the first rank at level 12. Confirm each required rank in your own spellbook. - Enemy in melee range. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no action ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Wing Clip. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-stings — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 22aea81716d846f8955e9808d7f06d763860e33b4d2b76080d0b775aa0e07155 Exact canonical body (plain text): ```text #showtooltip [mod:ctrl] Viper Sting; [mod:shift] Scorpid Sting; Serpent Sting /cast [mod:ctrl,harm,nodead] Viper Sting; [mod:shift,harm,nodead] Scorpid Sting; [harm,nodead] Serpent Sting ``` ### Requirements - Learned Serpent Sting; the current source records the first rank at level 4. Confirm each required rank in your own spellbook. - Learned Scorpid Sting; the current source records the first rank at level 22. Confirm each required rank in your own spellbook. - Learned Viper Sting; the current source records the first rank at level 36. Confirm each required rank in your own spellbook. - Usable ranged weapon and ammunition; selected enemy 8–35 yards away. Viper Sting needs an enemy with Mana to drain. ### Target order - Control: Viper Sting on current enemy - Otherwise Shift: Scorpid Sting on current enemy - Otherwise: Serpent Sting on current enemy ### Modifiers - Control: Viper Sting - Shift: Scorpid Sting ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Only one Sting from you can remain on a given target in this source. A chosen unlearned or unusable Sting does not fall through to another. - Serpent damage can break crowd control. Scorpid is a hit-chance reduction here, not its Classic Strength/Agility effect. - Keep the listed modifier combination free of conflicting action-bar bindings. Each chosen spell requires its own keypress; this is not a sequence. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [mod:ctrl,harm,nodead] Viper Sting. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 2, cast clause 2: [mod:shift,harm,nodead] Scorpid Sting. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 2, cast clause 3: [harm,nodead] Serpent Sting. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise modifier held/released states and combined key chords exactly as written, including competing modifiers. Check binding interception and first-clause priority; an unavailable selected action is not a readiness-based alternative selector. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-aimed-multi — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 58ebd2f27037acf97388e25f605ff59eae2d8bccc15a0fddc1453d2aa70f75a3 Exact canonical body (plain text): ```text #showtooltip [mod:shift] Multi-Shot; Aimed Shot /cast [mod:shift,nochanneling,harm,nodead] Multi-Shot; [nomod:shift,nochanneling,harm,nodead] Aimed Shot ``` ### Requirements - Learned Aimed Shot; the current source records the first rank at level 20. Confirm each required rank in your own spellbook. - Learned Multi-Shot; the current source records the first rank at level 18. Confirm each required rank in your own spellbook. - Usable ranged weapon and ammunition; selected enemy 8–35 yards away. ### Target order - Current living hostile target - No living hostile target: no cast ### Modifiers - Shift: Multi-Shot ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Aimed Shot is a trained baseline ability from level 20, not a Marksmanship talent. The two shots share a cooldown in this snapshot. - Multi-Shot may hit nearby controlled enemies. Existing Auto Shot is not stopped; the macro does not schedule shots or cancel a channel to fire. - Keep the listed modifier combination free of conflicting action-bar bindings. Each chosen spell requires its own keypress; this is not a sequence. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [mod:shift,nochanneling,harm,nodead] Multi-Shot. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 2, cast clause 2: [nomod:shift,nochanneling,harm,nodead] Aimed Shot. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise modifier held/released states and combined key chords exactly as written, including competing modifiers. Check binding interception and first-clause priority; an unavailable selected action is not a readiness-based alternative selector. - [ ] Exercise the broad nochanneling guard with a legitimate active player channel and with none; compare ordinary casts and repeated presses. Do not infer that it protects a pet channel or every other command line. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-distracting-shot — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: ee18103a1356baddad76f12f715efaac8f52570723d97a4142d295e694adcd6d Exact canonical body (plain text): ```text #showtooltip Distracting Shot /cast [@mouseover,harm,nodead][harm,nodead] Distracting Shot ``` ### Requirements - Learned Distracting Shot; the current source records the first rank at level 12. Confirm each required rank in your own spellbook. - Usable ranged weapon and ammunition; enemy 8–35 yards away. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no action ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - This source describes additional threat, not a modern forced-target taunt. It may fail to pull the enemy off another player. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Distracting Shot. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-tranquilizing-shot — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 1204f397612e6abaa754907cfec818a3cd2fb0b1474f09177f24ec3d05a90903 Exact canonical body (plain text): ```text #showtooltip Tranquilizing Shot /cast [@mouseover,harm,nodead][harm,nodead] Tranquilizing Shot ``` ### Requirements - Learned Tranquilizing Shot; the current source records the first rank at level 60. Confirm each required rank in your own spellbook. - Usable ranged weapon and ammunition; enemy 8–35 yards away with an eligible Frenzy effect. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no action ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - The source records level 60 but does not establish its complete acquisition route. Confirm it is learned, not merely level-eligible. - This is a Frenzy removal attempt, not a generic interrupt or removal of every buff. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Tranquilizing Shot. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-pet-care — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 50e6db229cb20ac65d422845c95ed83862b865ffb2638ac126dcb91ebd73e1e2 Exact canonical body (plain text): ```text #showtooltip [mod:shift] Revive Pet; [nopet] Call Pet; Mend Pet /cast [nochanneling,mod:shift] Revive Pet; [nochanneling,nopet] Call Pet; [nochanneling,@pet,exists,nodead] Mend Pet ``` ### Requirements - Learned Call Pet; the current source records the first rank at level 10. Confirm each required rank in your own spellbook. - Learned Mend Pet; the current source records the first rank at level 12. Confirm each required rank in your own spellbook. - Learned Revive Pet; the current source records the first rank at level 10. Confirm each required rank in your own spellbook. - An acquired tame pet. Revive Pet requires a dead pet; Mend Pet requires a living pet within 20 yards. ### Target order - Shift: attempt Revive Pet - Otherwise no summoned pet: Call Pet - Otherwise living pet and no existing channel: Mend Pet ### Modifiers - Shift: Revive Pet ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - A dead pet may report absent: use Shift explicitly if the ordinary key cannot call it. The macro does not inspect stable slots. - All branches preserve an existing player channel. Stop a channel manually before choosing another pet-care action; do not spam during the separate Revive Pet cast. - Call Pet may display a pet-specific name in the beta. Confirm the canonical English cast name against your client. - Keep the listed modifier combination free of conflicting action-bar bindings. Each chosen spell requires its own keypress; this is not a sequence. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [nochanneling,mod:shift] Revive Pet. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 2, cast clause 2: [nochanneling,nopet] Call Pet. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 2, cast clause 3: [nochanneling,@pet,exists,nodead] Mend Pet. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise modifier held/released states and combined key chords exactly as written, including competing modifiers. Check binding interception and first-clause priority; an unavailable selected action is not a readiness-based alternative selector. - [ ] Test relevant absent/dead/living and required/wrong-family pet states, actual training and the acting unit's resources/range/line of sight. A pet-family or existence condition does not prove the pet can act or protect its channel. - [ ] Exercise the broad nochanneling guard with a legitimate active player channel and with none; compare ordinary casts and repeated presses. Do not infer that it protects a pet channel or every other command line. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-scare-beast — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: b7e9e1985d3dd29c675457557652690a09ae85f76f398d2bfd1f6c570d01e536 Exact canonical body (plain text): ```text #showtooltip Scare Beast /stopattack /petpassive /petfollow /cast [@mouseover,harm,nodead][harm,nodead] Scare Beast ``` ### Requirements - Learned Scare Beast; the current source records the first rank at level 14. Confirm each required rank in your own spellbook. - A fear-susceptible Beast in the learned rank range; rank 1 records 10 yards. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no Scare Beast ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Attack stopping and pet recall happen even with no valid Beast. Damage already in flight, damage-over-time effects and allies can still break fear. - Pet commands require a controllable pet; this key leaves it Passive until you deliberately change its behaviour. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2: /stopattack. Observe attack stopping independently of the later cast, including an unavailable/no-match cast. Existing periodic damage, projectiles, allies or pet behavior are not cleared by this command. - [ ] Line 3: /petpassive. Test its written guards with an actual controllable pet and observe the order/mode independently of later spell success. Record the resulting pet state; do not assume a failed cast undoes this order. - [ ] Line 4: /petfollow. Test its written guards with an actual controllable pet and observe the order/mode independently of later spell success. Record the resulting pet state; do not assume a failed cast undoes this order. - [ ] Line 5, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Scare Beast. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Test relevant absent/dead/living and required/wrong-family pet states, actual training and the acting unit's resources/range/line of sight. A pet-family or existence condition does not prove the pet can act or protect its channel. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-freezing-frost — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: a996d1fd79efcb70ae722bd65c37dc48c9053a23a70461cc0d941ee995056a33 Exact canonical body (plain text): ```text #showtooltip [mod:shift] Frost Trap; Freezing Trap /stopattack /petpassive /petfollow /cast [mod:shift] Frost Trap; Freezing Trap ``` ### Requirements - Learned Freezing Trap; the current source records the first rank at level 20. Confirm each required rank in your own spellbook. - Learned Frost Trap; the current source records the first rank at level 28. Confirm each required rank in your own spellbook. ### Target order - Shift: place Frost Trap at your feet - Otherwise: place Freezing Trap at your feet ### Modifiers - Shift: Frost Trap ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - These are feet-placed traps, not Trap Launcher or @cursor casts. No combat-placement permission is inferred; check the current client. - One Frost trap can be active. The macro does not wait for arming, choose a target or clear existing damage that may break Freezing Trap. - Pet is left Passive; return it to the desired mode deliberately. - Keep the listed modifier combination free of conflicting action-bar bindings. Each chosen spell requires its own keypress; this is not a sequence. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2: /stopattack. Observe attack stopping independently of the later cast, including an unavailable/no-match cast. Existing periodic damage, projectiles, allies or pet behavior are not cleared by this command. - [ ] Line 3: /petpassive. Test its written guards with an actual controllable pet and observe the order/mode independently of later spell success. Record the resulting pet state; do not assume a failed cast undoes this order. - [ ] Line 4: /petfollow. Test its written guards with an actual controllable pet and observe the order/mode independently of later spell success. Record the resulting pet state; do not assume a failed cast undoes this order. - [ ] Line 5, cast clause 1: [mod:shift] Frost Trap. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 5, cast clause 2: Freezing Trap. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise modifier held/released states and combined key chords exactly as written, including competing modifiers. Check binding interception and first-clause priority; an unavailable selected action is not a readiness-based alternative selector. - [ ] Test relevant absent/dead/living and required/wrong-family pet states, actual training and the acting unit's resources/range/line of sight. A pet-family or existence condition does not prove the pet can act or protect its channel. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-fire-traps — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 6dea0a65061688632c6046a2745d07f27d90eff293c56c418de6d4de515708e4 Exact canonical body (plain text): ```text #showtooltip [mod:shift] Explosive Trap; Immolation Trap /cast [mod:shift] Explosive Trap; Immolation Trap ``` ### Requirements - Learned Immolation Trap; the current source records the first rank at level 16. Confirm each required rank in your own spellbook. - Learned Explosive Trap; the current source records the first rank at level 34. Confirm each required rank in your own spellbook. ### Target order - Shift: place Explosive Trap at your feet - Otherwise: place Immolation Trap at your feet ### Modifiers - Shift: Explosive Trap ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - One Fire trap can be active. Area damage can break crowd control; this macro does not control which enemy triggers the trap. - Feet placement only. It does not establish whether the beta permits combat placement. - Keep the listed modifier combination free of conflicting action-bar bindings. Each chosen spell requires its own keypress; this is not a sequence. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [mod:shift] Explosive Trap. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 2, cast clause 2: Immolation Trap. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise modifier held/released states and combined key chords exactly as written, including competing modifiers. Check binding interception and first-clause priority; an unavailable selected action is not a readiness-based alternative selector. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-feign-death — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: affc66e2a817f68afcf66eef8eab6f882ae8826308995910569392719d5dd8e9 Exact canonical body (plain text): ```text #showtooltip Feign Death /stopattack /stopcasting /petpassive /petfollow /cast Feign Death ``` ### Requirements - Learned Feign Death; the current source records the first rank at level 30. Confirm each required rank in your own spellbook. ### Target order - Yourself; pet ordered back separately ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Attack/cast cancellation and pet orders occur even if Feign Death is unavailable. Resist, incoming effects or a pet still in combat can defeat an escape. - Pet is left Passive. The source warns that remaining feigned for the full six-minute duration kills the Hunter; end it deliberately. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2: /stopattack. Observe attack stopping independently of the later cast, including an unavailable/no-match cast. Existing periodic damage, projectiles, allies or pet behavior are not cleared by this command. - [ ] Line 3 has unconditional /stopcasting. Observe cancellation of an active cast/channel even when the later spell is unavailable; record the resulting failed attempt separately. - [ ] Line 4: /petpassive. Test its written guards with an actual controllable pet and observe the order/mode independently of later spell success. Record the resulting pet state; do not assume a failed cast undoes this order. - [ ] Line 5: /petfollow. Test its written guards with an actual controllable pet and observe the order/mode independently of later spell success. Record the resulting pet state; do not assume a failed cast undoes this order. - [ ] Line 6, cast clause 1: Feign Death. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Test relevant absent/dead/living and required/wrong-family pet states, actual training and the acting unit's resources/range/line of sight. A pet-family or existence condition does not prove the pet can act or protect its channel. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-disengage — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: c7dce1b37fb2c1c6831ee4e192b8b9446033282562879096ba1e2b2a5d57407b Exact canonical body (plain text): ```text #showtooltip Disengage /stopattack /cast [harm,nodead] Disengage ``` ### Requirements - Learned Disengage; the current source records the first rank at level 20. Confirm each required rank in your own spellbook. - Enemy in melee range. ### Target order - Current living hostile target - No living hostile target: no cast ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - This is not the Retail backward leap. It does not move the Hunter, guarantee a target switch or recall the pet. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2: /stopattack. Observe attack stopping independently of the later cast, including an unavailable/no-match cast. Existing periodic damage, projectiles, allies or pet behavior are not cleared by this command. - [ ] Line 3, cast clause 1: [harm,nodead] Disengage. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-combat-aspects — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: a402e03e76ba5e50985794ff404ae4e129240e03933491838e0825a4e62b18d8 Exact canonical body (plain text): ```text #showtooltip [mod:shift] Aspect of the Monkey; Aspect of the Hawk /cast [mod:shift] !Aspect of the Monkey; !Aspect of the Hawk ``` ### Requirements - Learned Aspect of the Hawk; the current source records the first rank at level 10. Confirm each required rank in your own spellbook. - Learned Aspect of the Monkey; the current source records the first rank at level 4. Confirm each required rank in your own spellbook. ### Target order - Shift: Aspect of the Monkey on yourself - Otherwise: Aspect of the Hawk on yourself ### Modifiers - Shift: Aspect of the Monkey ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Only one Aspect can be active. This does not choose an Aspect from range, weapons or combat events; verify non-toggle behaviour in Forever. - Keep the listed modifier combination free of conflicting action-bar bindings. Each chosen spell requires its own keypress; this is not a sequence. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [mod:shift] !Aspect of the Monkey. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 2, cast clause 2: !Aspect of the Hawk. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise modifier held/released states and combined key chords exactly as written, including competing modifiers. Check binding interception and first-clause priority; an unavailable selected action is not a readiness-based alternative selector. - [ ] The ! prefix requests non-toggle behavior. Compare initial and repeated presses with the relevant aura/attack state already active; exact client behavior remains to be observed. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-cheetah — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: d7b88f395af84f055716601ee4d04993ec985bf4ee933c0b0ce16bbad1a4ad0d Exact canonical body (plain text): ```text #showtooltip Aspect of the Cheetah /cancelaura [mod:shift] Aspect of the Cheetah /cast [nomod:shift] !Aspect of the Cheetah ``` ### Requirements - Learned Aspect of the Cheetah; the current source records the first rank at level 20. Confirm each required rank in your own spellbook. - Aspect of the Cheetah must already be active on you; removing it does not require learning or casting the spell. ### Target order - Shift: cancel your Cheetah aura - Otherwise: activate Cheetah ### Modifiers - Shift: cancel Cheetah ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Taking damage while Cheetah is active can daze you. Cancelling the Aspect does not remove a daze already applied. - Keep the listed modifier combination free of conflicting action-bar bindings. Each chosen spell requires its own keypress; this is not a sequence. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2: /cancelaura [mod:shift] Aspect of the Cheetah. Test the named own aura present/absent and any literal modifier guards held/released. Observe that cancellation is separate from learning/casting the spell, other units' auras and any later cast; do not infer restored cooldowns or removed restrictions. - [ ] Line 3, cast clause 1: [nomod:shift] !Aspect of the Cheetah. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise modifier held/released states and combined key chords exactly as written, including competing modifiers. Check binding interception and first-clause priority; an unavailable selected action is not a readiness-based alternative selector. - [ ] The ! prefix requests non-toggle behavior. Compare initial and repeated presses with the relevant aura/attack state already active; exact client behavior remains to be observed. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-tracking — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 048526d846c3db66abdc097e82f76e8a0e6ad015b2794f73209aff3adcb33b0c Exact canonical body (plain text): ```text #showtooltip [mod:shift] Track Humanoids; Track Beasts /cast [mod:shift] Track Humanoids; Track Beasts ``` ### Requirements - Learned Track Beasts; the current source records the first rank at level 1. Confirm each required rank in your own spellbook. - Learned Track Humanoids; the current source records the first rank at level 10. Confirm each required rank in your own spellbook. ### Target order - Shift: Track Humanoids - Otherwise: Track Beasts ### Modifiers - Shift: Track Humanoids ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Only one tracking mode can be active; this does not detect the best creature type or automatically swap tracking. - Keep the listed modifier combination free of conflicting action-bar bindings. Each chosen spell requires its own keypress; this is not a sequence. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [mod:shift] Track Humanoids. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 2, cast clause 2: Track Beasts. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise modifier held/released states and combined key chords exactly as written, including competing modifiers. Check binding interception and first-clause priority; an unavailable selected action is not a readiness-based alternative selector. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-flare — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 1a7582289c160fe84cc0ed5ba6ad2fe070f85d9df150b1c8805707358d5b68b3 Exact canonical body (plain text): ```text #showtooltip Flare /cast [nochanneling] Flare ``` ### Requirements - Learned Flare; the current source records the first rank at level 32. Confirm each required rank in your own spellbook. ### Target order - Ground area selected with the client reticle ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Does not cancel an existing channel. Confirm the ground location with the client reticle; no @cursor support is assumed. - The source also contains Enchanted Flare with overlapping purpose but a different cooldown. Their acquisition relationship is unresolved; this key addresses Flare only. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [nochanneling] Flare. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise the broad nochanneling guard with a legitimate active player channel and with none; compare ordinary casts and repeated presses. Do not infer that it protects a pet channel or every other command line. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-volley — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: f645760e86704b347aa48022dce2e847134e00d1dee3617a033a672d6937f512 Exact canonical body (plain text): ```text #showtooltip Volley /cast [nochanneling:Volley] Volley ``` ### Requirements - Learned Volley; the current source records the first rank at level 40. Confirm each required rank in your own spellbook. - Usable ranged weapon and ammunition; valid area within 35 yards. ### Target order - Ground area selected with the client reticle ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Existing Volley is protected from this key, but other channels are not. Confirm the reticle manually. - Area damage can break crowd control. This does not move, retarget or restart the channel automatically. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [nochanneling:Volley] Volley. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise the literal nochanneling:Volley guard with its named channel and a different legitimate player channel. Do not assume this spell-specific guard protects every channel. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-summon-hawk — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 05bc7cc9bea6941f2c1517e5a2c1a9d4f20ccf2b40f5e3ffa1c5539c6abf4f5c Exact canonical body (plain text): ```text #showtooltip Summon Hawk /cast [@mouseover,harm,nodead][harm,nodead] Summon Hawk ``` ### Requirements - Learned Summon Hawk; the current source records the first rank at level 25. Confirm each required rank in your own spellbook. - Select Summon Hawk at rank 1 in Beast Mastery, row 4, with a legal allocation requiring at least 16 tree points under the source calculator model. A spec label does not grant the talent; point eligibility does not prove early spell learning. - Enemy within 35 yards. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no action ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Shares cooldown with Arcane Shot. The source permits at most two summoned hawks; the macro does not count hawks or choose a cooldown. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Summon Hawk. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-intimidation — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: d6e253e1801d03f779a48c43f4d6c81b6bd79e42e236069e15853b26ed8c8c27 Exact canonical body (plain text): ```text #showtooltip Intimidation /petattack [harm,nodead] /cast [harm,nodead] Intimidation ``` ### Requirements - Learned Intimidation; the current source records the first rank at level 30. Confirm each required rank in your own spellbook. - Select Intimidation at rank 1 in Beast Mastery, row 5, with a legal allocation requiring at least 21 tree points under the source calculator model. A spec label does not grant the talent; point eligibility does not prove early spell learning. - Fully rank Bestial Swiftness, the current named prerequisite for Intimidation. - A living controllable pet able to reach your selected enemy; the pet must land its next attack for the stun. ### Target order - Current living hostile target - No living hostile target: no cast ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Pet attack is ordered even if Intimidation is unavailable, on cooldown or out of range. Do not press on crowd-controlled enemies. - This is not an instant ranged interrupt. Pathing, successful attack, pet state and stun immunity matter. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2: /petattack [harm,nodead]. Test its written guards with an actual controllable pet and observe the order/mode independently of later spell success. Record the resulting pet state; do not assume a failed cast undoes this order. - [ ] Line 3, cast clause 1: [harm,nodead] Intimidation. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Test relevant absent/dead/living and required/wrong-family pet states, actual training and the acting unit's resources/range/line of sight. A pet-family or existence condition does not prove the pet can act or protect its channel. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-bestial-wrath — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 0e34f6b9d6f094318e8b157cf651730c38cdd22fba274ef2be30e3496bc4b01a Exact canonical body (plain text): ```text #showtooltip Bestial Wrath /cast [@pet,exists,nodead] Bestial Wrath ``` ### Requirements - Learned Bestial Wrath; the current source records the first rank at level 40. Confirm each required rank in your own spellbook. - Select Bestial Wrath at rank 1 in Beast Mastery, row 7, with a legal allocation requiring at least 31 tree points under the source calculator model. A spec label does not grant the talent; point eligibility does not prove early spell learning. - Fully rank Intimidation, the current named prerequisite for Bestial Wrath. - Living controllable pet within the recorded 100-yard range. ### Target order - Your living pet - No living pet: no cast ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Does not summon, revive or order the pet to attack. The pet must already have an appropriate target if you want offensive benefit. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [@pet,exists,nodead] Bestial Wrath. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Test relevant absent/dead/living and required/wrong-family pet states, actual training and the acting unit's resources/range/line of sight. A pet-family or existence condition does not prove the pet can act or protect its channel. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-scatter-shot — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: e201f5e8243c530fb59b5151a3914832ac47a95438fd3f2bda18ac403abfab14 Exact canonical body (plain text): ```text #showtooltip Scatter Shot /stopattack /petpassive /petfollow /cast [@mouseover,harm,nodead][harm,nodead] Scatter Shot ``` ### Requirements - Learned Scatter Shot; the current source records the first rank at level 30. Confirm each required rank in your own spellbook. - Select Scatter Shot at rank 1 in Marksmanship, row 5, with a legal allocation requiring at least 21 tree points under the source calculator model. A spec label does not grant the talent; point eligibility does not prove early spell learning. - Usable ranged weapon and ammunition; enemy within 15 yards. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no Scatter Shot ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Existing damage and projectiles can still break the effect. Pet recall and attack stopping occur even if the cast fails; pet is left Passive. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2: /stopattack. Observe attack stopping independently of the later cast, including an unavailable/no-match cast. Existing periodic damage, projectiles, allies or pet behavior are not cleared by this command. - [ ] Line 3: /petpassive. Test its written guards with an actual controllable pet and observe the order/mode independently of later spell success. Record the resulting pet state; do not assume a failed cast undoes this order. - [ ] Line 4: /petfollow. Test its written guards with an actual controllable pet and observe the order/mode independently of later spell success. Record the resulting pet state; do not assume a failed cast undoes this order. - [ ] Line 5, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Scatter Shot. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Test relevant absent/dead/living and required/wrong-family pet states, actual training and the acting unit's resources/range/line of sight. A pet-family or existence condition does not prove the pet can act or protect its channel. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-sniper-shot — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 4c2e63092ac03366852920083daf7cd7d144b15380cd5ca61793beb1845bc9ee Exact canonical body (plain text): ```text #showtooltip Sniper Shot /cast [nochanneling,harm,nodead] Sniper Shot ``` ### Requirements - Learned Sniper Shot; the current source records the first rank at level 40. Confirm each required rank in your own spellbook. - Select Sniper Shot at rank 1 in Marksmanship, row 7, with a legal allocation requiring at least 31 tree points under the source calculator model. A spec label does not grant the talent; point eligibility does not prove early spell learning. - Fully rank Trueshot Aura, the current named prerequisite for Sniper Shot. - Usable ranged weapon and ammunition; enemy 8–35 yards away. ### Target order - Current living hostile target - No living hostile target: no cast ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - The source records a four-second cast. This does not aim automatically, cancel a channel, stop Auto Shot or align a shot rotation. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [nochanneling,harm,nodead] Sniper Shot. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise the broad nochanneling guard with a legitimate active player channel and with none; compare ordinary casts and repeated presses. Do not infer that it protects a pet channel or every other command line. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-trueshot-rapid — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: d841b167d95b85133c3b904d760b01dee1dfd9518b5a17a6cfb4003dcdee0507 Exact canonical body (plain text): ```text #showtooltip [mod:shift] Rapid Fire; Trueshot Aura /cast [mod:shift] Rapid Fire; Trueshot Aura ``` ### Requirements - Learned Trueshot Aura; the current source records the first rank at level 25. Confirm each required rank in your own spellbook. - Select Trueshot Aura at rank 1 in Marksmanship, row 4, with a legal allocation requiring at least 16 tree points under the source calculator model. A spec label does not grant the talent; point eligibility does not prove early spell learning. - Learned Rapid Fire; the current source records the first rank at level 26. Confirm each required rank in your own spellbook. ### Target order - Shift: Rapid Fire on yourself - Otherwise: Trueshot Aura for nearby party ### Modifiers - Shift: Rapid Fire ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Rapid Fire benefits melee and ranged attack speed in this source. The key does not detect buff expiry, stack both spells or send a pet. - Keep the listed modifier combination free of conflicting action-bar bindings. Each chosen spell requires its own keypress; this is not a sequence. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [mod:shift] Rapid Fire. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Line 2, cast clause 2: Trueshot Aura. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise modifier held/released states and combined key chords exactly as written, including competing modifiers. Check binding interception and first-clause priority; an unavailable selected action is not a readiness-based alternative selector. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-deterrence — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 708fe86771b9b2422db298c4b5d4d2c6cd75349c41f82a21528e053d36a12480 Exact canonical body (plain text): ```text #showtooltip Deterrence /stopcasting /cast Deterrence ``` ### Requirements - Learned Deterrence; the current source records the first rank at level 20. Confirm each required rank in your own spellbook. - Select Deterrence at rank 1 in Survival, row 3, with a legal allocation requiring at least 11 tree points under the source calculator model. A spec label does not grant the talent; point eligibility does not prove early spell learning. ### Target order - Yourself ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Cancels the current cast even if Deterrence is unavailable. The source grants Dodge and Parry, not modern total damage immunity. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2 has unconditional /stopcasting. Observe cancellation of an active cast/channel even when the later spell is unavailable; record the resulting failed attempt separately. - [ ] Line 3, cast clause 1: Deterrence. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-counterattack — 1.1.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: cde90681465fe7ac8a6cc3e131d0211e26968a5acd3d5d8a3c40cbee1639733d Exact canonical body (plain text): ```text #showtooltip Counterattack /cast [harm,nodead] Counterattack ``` ### Requirements - Learned Counterattack; the current source records the first rank at level 25. Confirm each required rank in your own spellbook. - Select Counterattack at rank 1 in Survival, row 4, with a legal allocation requiring at least 16 tree points under the source calculator model. A spec label does not grant the talent; point eligibility does not prove early spell learning. - Fully rank Deterrence, the current named prerequisite for Counterattack. - A recent parry must have enabled Counterattack. The current source records its first spell rank at 25; actual talent selection, known-spell acquisition and the reactive opportunity still apply separately. - A usable melee weapon and a living enemy in melee range. ### Target order - Current living hostile target - No living hostile target: no cast ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - Does not create or detect the reactive opportunity. Root immunity still applies. - No separate attack-start command is included. Automatic attack behavior, including when the ability cannot be cast, still needs testing in the Forever client. Avoid pressing this key while preserving crowd control. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [harm,nodead] Counterattack. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-strider-kick — 1.1.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: 083f97537dd40f8851f5f525190376437451550d0158e0c7cd6ee5f19604c0fc Exact canonical body (plain text): ```text #showtooltip Strider Kick /cast [harm,nodead] Strider Kick ``` ### Requirements - Learned Strider Kick; the current source records the first rank at level 30. Confirm each required rank in your own spellbook. - Select Strider Kick at rank 1 in Survival, row 5, with a legal allocation requiring at least 21 tree points under the source calculator model. A spec label does not grant the talent; point eligibility does not prove early spell learning. ### Target order - Current living hostile target - No living hostile target: no cast ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - The source describes damage and a movement-speed buff, not a spell interrupt. - No separate attack-start command is included. Automatic attack behavior, including when the ability cannot be cast, still needs testing in the Forever client. Avoid pressing this key while preserving crowd control. - Later official development notes permit Strider Kick while disarmed or without a main-hand weapon. Range, actual talent ownership and other cast restrictions still apply; client acceptance remains unverified. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [harm,nodead] Strider Kick. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use a different mouseover as a control. This body has no @mouseover option; verify its actual selected-target/self/ground action instead of borrowing another macro's mouseover policy. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status. ## hunter-lacerate — 1.0.2 State: NOT_RUN Scope: Current design; actual client tests still required Body SHA-256: ffd2bc05e4a71ec3c0afda78d9a900d76dc396dd2e7f5948742909a82dc97b38 Exact canonical body (plain text): ```text #showtooltip Lacerate /cast [@mouseover,harm,nodead][harm,nodead] Lacerate ``` ### Requirements - Learned Lacerate; the current source records the first rank at level 30. Confirm each required rank in your own spellbook. - Enemy in melee range. Lacerate is baseline trained at level 30 in this source, not the passive Lacerating Strikes talent. ### Target order - Living hostile mouseover - Living hostile target - No valid enemy: no action ### Modifiers No entries declared; absence is not proof of unrestricted behavior. ### Known limitations - Source-reviewed on 7 November 2026 against the 4 November Talents Forever export, base client 1.60.1.70755 with separately reported server-hotfix overlays. Some values follow announced development notes ahead of game data; exact class source statements distinguish these from extracted records and reported hotfixes. Source records are provisional and no in-client macro test is recorded. - English spell names; check your spellbook and actual learned rank. Source IDs identify reference ranks, not a forced rank-1 cast. - Range, line of sight, resources, cooldowns and the global cooldown still apply. A macro does not detect readiness or choose your next combat action. - The bleed can break damage-sensitive crowd control. - The first matching unit wins. An out-of-range, obstructed, immune or otherwise unusable mouseover does not fall through to your target. ### Cases to observe — all NOT_RUN - [ ] Compare this exact ID, version, body SHA-256 and native macro-editor readback before testing. Personal edits are a different test subject. - [ ] Record actual client/build/channel, locale, learned ranks, talents, equipment and settings. Observe an intended action with required conditions met and compare the ordinary spellbook control; do not infer success from the tooltip. - [ ] Run the listed targeting order and modifier choices with distinct conflicting recipients. Distinguish an invalid condition from a matching but unusable recipient; range, line of sight, cooldown, resource or eligibility failure must not be assumed to fall through. - [ ] Line 2, cast clause 1: [@mouseover,harm,nodead][harm,nodead] Lacerate. Exercise each literal bracket group and the written clause order; record the actual action, recipient, rank and error. This is a case inventory, not a simulation of the game parser. - [ ] Use different mouseover A and current target B. Exercise the friendly/hostile/dead/absent states actually referenced by the body, then a matching but unusable A; observe the recipient without assuming target acquisition or target changes. - [ ] Exercise the exact requirements and limitations printed below, including relevant form/stance, equipment, party, reagent, creature, reactive and ground-placement questions. Source descriptions are not observations or permission to invent a missing rule. - [ ] Make two observations after resetting each required case under the plan's maintainer rule; read back/retest after reload. Record PASS, EXPECTED_FAILURE, FAIL, BLOCKED, NOT_RUN or justified NA with evidence references; no form or checkbox promotes the library status.