Repository navigation
Ability Mechanics
This page documents Hunter ability interactions that are not obvious from the tooltip.
Straightforward spell changes such as altered cast times, cooldowns, damage values, ranks, or target caps belong on Forever Hunter Patch Notes rather than being repeated here.
The focus here is:
- hidden interactions
- unusual combat behavior
- dynamic scaling
- proc behavior
- range or timing quirks
- mechanics that materially affect testing or rotation design
- Hunter periodic damage can Crit
- Periodic damage uses the Hunter's ranged Crit chance
- Periodic effects are dynamic rather than fully snapshotted
- Auto Shot can continue firing while casting compatible ranged abilities
- Raptor Strike, Mongoose Bite, Strider Kick, and Wing Clip can trigger normal melee on-hit effects
- Feign Death resets both the ranged and melee swing timers
- Feign Death can be resisted independently by nearby enemies
- Trap activation is checked in batches of approximately 800 ms
- Trap trigger radius is approximately 5 yd
- Fast movement can cross a trap before the next trigger check
- Scorpid Sting's hit reduction does not stack with Insect Swarm
- Fire and Frost traps are intended to operate independently, but current Forever behavior may prevent both from being active together
Periodic Hunter damage behaves differently from original Classic expectations.
Hunter DoTs can:
- Crit
- dynamically update with the Hunter's current stats
- respond to damage modifiers while already active
This affects effects such as:
- Serpent Sting
- Immolation Trap
- other Hunter periodic effects where applicable
Hunter periodic damage can Crit.
The Crit chance used is the Hunter's:
Ranged or Melee Crit Chance, whichever is higher
rather than spell Crit.
This means increases to ranged or melee Crit can also increase the expected damage of eligible Hunter periodic effects.
A periodic Crit uses the effect's applicable Crit multiplier.
See Attack Formulas for Crit-damage modeling.
Hunter periodic effects are not fully snapshotted when first applied.
Instead, later ticks can respond to the Hunter's current stats.
For example:
- Apply Serpent Sting
- Increase RAP
- Allow the Sting to continue ticking
- Later ticks increase in damage
Conceptually:
Tick Damage = Current Stats at Tick Time
rather than:
Tick Damage = Stats When Effect Was Applied
This means stat changes during an active DoT can affect the remaining ticks.
A clean dynamic-scaling test is:
- apply the DoT with a known RAP value
- record several ticks
- change RAP without refreshing the DoT
- record the remaining ticks
- compare the two groups
If the damage changes without reapplying the effect, the effect is dynamically recalculating.
See Hunter Testing Methodology.
Auto Shot can continue firing while the Hunter is casting certain ranged abilities.
Confirmed compatible casts include:
- Aimed Shot
- Multi-Shot
- Sniper Shot
The Hunter does not need to finish the cast before Auto Shot can fire.
This means the ranged weapon cycle and the spell cast can overlap.
Conceptually:
Cast-Time Ability ≠ Automatic Auto Shot Pause
This is an important departure from simply treating every cast-time ability as occupied ranged downtime.
Because Auto Shot can continue during compatible casts, the actual opportunity cost of a cast depends on more than the cast time itself.
A cast can consume player action time without necessarily removing the Auto Shot that occurs during that window.
This is especially important when comparing:
- Aimed Shot
- Multi-Shot
- Sniper Shot
- melee-weaving windows
See Shot Mechanics for Auto Shot timing and retry behavior.
Hunter melee abilities can trigger normal melee on-hit effects.
Confirmed examples include:
- Raptor Strike
- Mongoose Bite
- Strider Kick
- Wing Clip
These attacks can trigger effects such as:
- Windfury
- Fiery Weapon
- Dragonbreath Chili
- other generic melee on-hit effects
This applies even when the ability's primary purpose is not direct weapon damage.
Applicable Hunter melee attacks can trigger Windfury.
The Windfury extra attack occurs immediately on the same server tick as the triggering attack.
It does not wait for the Hunter's next normal melee swing.
This makes a single woven melee ability capable of producing multiple weapon events immediately.
See Melee Weaving for rotational implications.
Feign Death has several important hidden behaviors beyond its tooltip.
Feign Death resets both:
- ranged swing timer
- melee swing timer
This means Feign Death should not be treated as rotationally free.
Using it can destroy progress already accumulated on both weapon timers.
For a Hunter using slow ranged or melee weapons, this can represent a small damage loss.
Feign Death can be resisted.
The approximate resist chance increases with the target's level relative to the Hunter. This can be reduced by the players hit chance now that hit is universal physical and spell hit.
| Target Level | Approximate Resist Chance |
|---|---|
| Equal level | 4% |
| +1 | 5% |
| +2 | 6% |
| +3 | 17% |
| +4 | 28% |
| +5 | 39% |
| +6 | 50% |
Beyond this point, the pattern continues at approximately:
+11 percentage points per additional target level
The large jump begins once the target reaches +3 levels.
Feign Death can perform independent resist checks against multiple nearby enemies.
Enemies within approximately:
~40 yd
may receive their own check.
One enemy resisting Feign Death does not imply that every nearby enemy also resisted it.
This means a large pull can produce mixed results where some enemies drop the Hunter while others continue attacking.
Feign Death reliability decreases sharply against higher-level enemies.
Against a +3 target:
~17% resist
is already significant enough that Feign Death should not be assumed to succeed every time.
Against enemies substantially above the Hunter's level, failure becomes increasingly likely.
Hunter traps use several mechanics that are not obvious from their tooltips.
The practical trigger radius is approximately:
~5 yd
A valid enemy entering this radius becomes eligible to activate the trap.
However, entering the radius does not necessarily mean the trap triggers immediately.
Trap activation is checked in batches of approximately:
~800 ms
This means trap detection is not perfectly continuous.
Conceptually:
Enter Trigger Radius → Wait for Trap Check → Trap Activates
If a target crosses the trigger area between checks and leaves before the next check occurs, it can pass through without activating the trap.
This batching makes traps vulnerable to sufficiently fast movement.
Examples include:
- Charge-style movement
- mounted targets
- high movement-speed effects
- rapidly crossing the edge of the trigger area
A target can physically pass over or through the trap before the next activation check.
This does not necessarily mean the target was outside the trigger radius.
It may simply have entered and exited between trap checks.
The trap trigger radius is large enough that placing a trap directly beneath or very near the Hunter can force a normal melee attacker to enter the trigger area while approaching.
However, batching still matters.
A rapidly moving target can potentially cross the trigger area before the trap performs its next check.
Forever allows traps to be placed during combat.
Fire and Frost traps also use separate cooldown categories.
The intended behavior allows the categories to operate independently.
However, current Forever behavior has shown cases where a Fire and Frost trap cannot both remain placed simultaneously.
This should be treated as a current implementation issue, not as the intended trap-category mechanic.
See Forever Hunter Patch Notes or the current bug tracker for implementation status.
Scorpid Sting reduces the target's chance to hit.
Its hit-reduction effect does not stack with Insect Swarm.
If both effects are present, they should not be modeled as additive hit reduction.
This matters when evaluating raid debuff combinations or tank mitigation.
When testing hidden ability behavior, isolate the interaction being tested.
Useful questions include:
- Does the effect use ranged, melee, or spell Crit?
- Does changing AP after application change later damage?
- Does the ability trigger weapon procs?
- Does it reset either swing timer?
- Does the ability interact with the GCD?
- Does another effect stack with it?
- Is activation immediate or batched?
- Does behavior change against multiple targets?
A hidden mechanic should ideally be confirmed through repeated tests rather than a single combat-log event.
See Hunter Testing Methodology for the full testing framework.