Proximity damage scales a hit by distance from its announced source. Unlike a binary circle, moving farther can reduce damage even when no point in the arena is completely safe. This demo compares a timely retreat with standing near the same rune; both pulses hit once, but with different severity.
At 0.68 seconds Kern marks one fixed rune. Tavi walks from 220 to 410 units away before the first pulse. Concentric bands preview relative severity rather than a binary safe border.
Reduced motion disables autoplay. Scrub through 0.68, 1.50, 2.30, 3.10, 3.50, 4.40, and 5.50 seconds.
Define the source, distance metric, inner and outer clamps, minimum and maximum damage, sampling instant, hit identity, reachable retreat, and visible health change.
Lock one source at the warning. Measure from that point to the target's chosen sample point, not from the boss's later position or the camera. This version clamps damage to 90 at 140 units or less and 10 at 420 units or more, interpolating between; it never claims an outer safe edge.
Keep the source visible through the warning and sample each target once at 2.20 and 4.30 seconds with distinct hit IDs. A target moving after the pulse does not retroactively alter that hit. Reject duplicate callbacks and document whether cover, mitigation, and group effects modify the result.
Test ordinary walking from the nearest likely starting position, with the full character inside the arena. Compare health changes near, between, and beyond the clamps; test exact boundaries, invalid coordinates, duplicate IDs, and retry. Keep bands and numeric feedback legible without color.
A standard AoE outline suggests zero damage beyond it. When the attack has a nonzero floor, use graded rings, a source marker, and health feedback instead of a false safe boundary.
If the boss moves after the warning, a live boss-centered measurement can contradict the telegraph. Snapshot the source or visibly track it, and use that same position in the damage calculation.
Tune warning time, run speed, arena depth, and damage floor together. Reaching the low-damage band should not require an unannounced dash, immunity, or a camera trick.
First calculate distance-based damage, then apply shielding, resistance, or group rules in a documented order. Log both raw and final damage so tests can distinguish bad geometry from balance values.
Record encounter, source, target, hit ID, sampled distance, unclamped fraction, clamped dose, health before and after, and reset. Rewind through both pulses to confirm identical results without a second application.
Kern charges a rune. Tavi backs away and survives its first pulse with modest damage. On the next warning Tavi stands closer; the same rune strikes much harder.
Combine the source glyph, concentric bands, distance-and-damage readout, pulse, health number, and clear hit reaction. Leave the timeline seekable with autoplay disabled.
An ordinary radial AoE asks whether a target is inside a radius. Here distance sets the amount even at the outer edge. Wakfu's Hark Saniss is a related but different proximity rule: nearby players add a permanent boss damage bonus on scheduled turns, rather than receiving a continuously graded pulse.
The Decisive Battle places a proximity marker at the arena center; players move toward the edge to reduce the damage before a new arena threat appears. The encounter combines distance with a follow-up, unlike the isolated pulse in this demo.
After a weapon is destroyed, Eradication deals raid-wide damage that decreases with distance from the boss. The raid can retreat, while one tank may stay closer to prevent Carnage: the range response creates a second positioning constraint.
Hark Saniss counts players within four cells on scheduled turns and gains a permanent damage bonus for each. This grid-based proximity threshold changes future boss damage; it is a contrast to the demo's per-target radial falloff, not an example of the same formula.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub