how many handlers are registered, across every event
runs every handler registered for event, in registration order
Runs the pre-damage seam and clamps the resulting amount at zero.
removes one specific handler; offSource is the usual way, this is for a one-off
removes every hook registered with this source - a fainted creature's ability leaving
Optionalsource: unknown
Generic combat lifecycle hooks; the game owns HP, formulas, and when each event fires.
The registry is
core.HookRegistry, the same onebattle.BattleHooksuses - these were two copies of one class for a while. What is combat-specific is that a handler receives a single mutableDamageContext, and themodifyDamageseam below built on it.Example