A tower is a fixed zone with a required headcount. At resolution, count distinct living players whose full bodies fit inside its radius. A correct soak may hurt occupants; an underfilled tower may punish the group. The demo compares one required player with two. Other games use sustained occupancy or orb collection instead of exact counts.
At 0.70 seconds Kern reveals a fixed rune at x405, y710. Its outer radius is 66 units; Tavi's 24-unit body must fit within 42 units of the center. The ally stays outside. The warning lasts to 2.20 seconds and the readout reaches 1/1.
Reduced motion disables autoplay. Scrub through 0.70, 1.30, 2.10, 2.30, 3.10, 3.75, 4.20, 4.45, and 5.45 seconds.
Define a stable tower ID and center, required headcount, full-body boundary, live roster, snapshot instant, occupant and raidwide damage, duplicate prevention, travel budget, failure readability, and retry behavior.
Store the tower center in world space, not on a target. At contact, snapshot unique living player IDs whose complete collision bodies fit inside the effective radius. Here the painted radius is 66 and the body radius is 24, so a center more than 42 units away does not count. Decide explicitly whether a production tower allows partial overlap, exactly N, or at least N; never let the graphic decide by accident.
Compare the snapshot count with the signaled requirement once per tower hit ID. This demo uses exact equality: 1/1 succeeds and deals 15 only to its occupant; 1/2 fails and deals 90 to every living party member. Keep occupied IDs, recipients, and health deltas in one ledger so replay or network callbacks cannot apply damage twice.
Budget warning time against the farthest assigned player's path, obstacles, movement speed, and latency. Signal two required players before anyone commits to a solo soak. Test both reachable and unreachable assignments, a player on the exact boundary, a downed teammate, and a retry that restores roster and health without reusing an old hit ID.
If the rule requires full occupancy, center-in-circle and full-body-in-circle produce different results. Use the same collision body for the count, indicator, and hit logic, and specify which boundary convention the encounter uses.
A correct count may prevent a raidwide failure while still costing the occupants health. Show both outcomes separately; otherwise players cannot distinguish a deliberate soak cost from an underfilled-tower penalty.
A two-person requirement in a two-person party gives no spare body. Recompute assignments for downed members, party size, and simultaneous towers; make an impossible roster state explicit instead of silently failing it.
A headcount snapshot, a sustained occupancy test, and an orb that one player collects all use a fixed location but create different decisions. Label the chosen rule, contact time, and whether extra players help or invalidate it.
Log tower ID, hit ID, center, radius, body radius, required count, living roster, occupied IDs, positions at contact, success, each damage recipient, and retry reset. Reproduce exact-edge, excess-player, missing-player, duplicate-callback, and narrow-screen cases.
Kern lights a single-person rune. Tavi steps inside and holds it, absorbing the small pulse. The next rune asks for two bodies, but Tavi arrives alone. Its unfilled mark flashes across the arena and the whole group pays for the missed check.
Keep the tower fixed while characters move. Use one or two pips and a numeric 1/1 or 1/2 readout, retain results when paused, show both health bars, and identify raidwide failure by shape as well as color. At reduced motion, the same timeline checkpoints must reveal the complete rule.
A shared-damage stack follows a marked player and divides one hit among nearby bodies. A tower checks who occupies a fixed world point and can punish everyone when its count is missed. A personal spread instead asks marked players to separate.
Will's first-phase moonlight barrier forms at a world location after the pupil is redirected. Occupying that barrier in the relevant dimension advances the screen-break test. It is a sustained safe-area variant, not this demo's exact one- or two-person headcount.
Words of Entrapment places four corner towers with light or dark aspects. Assigned players must occupy towers of the opposite aspect before they resolve. This is an occupancy-and-assignment variant with one suitable player per tower, not a two-player tower.
Remnants of Forgotten Torments create fixed orbs that designated players collect so the group avoids the unclaimed effect. Their number and debuffs change who should take each orb. This is a collection-and-transfer variant, not an exact-count tower; the video shows the live raid context.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub