Converging threats are two visible danger fronts advancing toward the same space. Their combined loss of clearance is the rule: reveal both origins and closing direction, commit the timing before movement, and leave an ordinary route out. Two side fields close below Tavi while the upper exit remains open.
Kern lights two broad side fields at the same height. Inward arrows show that their visible edges will meet below Tavi, while the upper route remains open.
Autoplay is disabled by reduced-motion settings. Use the timeline to inspect the two fronts and the full-body escape.
Design the two fronts, their meeting time, and a reachable full-body escape as one spatial promise.
Show two distinct origins, direction, footprint, and a shared arrival time. The reader should predict where the safe corridor closes without mistaking an arrow or preview line for active collision.
Test the player's whole body against both current fields. Measure the route to an upper or lateral exit at ordinary movement speed, including acceleration and arena boundaries; a point-sized gap is not sufficient.
Lock the fronts before they move, make the closing rate readable, and remove both hitboxes when their visible fields fade. Reserve a useful recovery interval after the corridor is clear.
A surprise second source changes the route after commitment. Reveal both edges before activation, or introduce the second as a separately announced escalation.
A gap can look open while the player's body collides with either field. Include radius, travel time, wall clearance, and camera framing in every sampled safe route.
The viewer cannot trust a closing diagram when hitboxes outrun their edges or remain after they fade. Drive motion, damage, and cleanup from the same clock.
Store each front's origin, width, height, timing, and current edge. A player is unsafe if either visible field overlaps their full collision body; their meeting does not add a hidden third attack.
Sample the remaining corridor width and the time needed to clear its threatened strip. Sweep each moving edge between frames so a fast front cannot cross the player unnoticed.
Crossfire is about trajectories from distinct origins crossing. Here two broad fronts progressively remove the corridor even if no discrete projectiles intersect. A persistent shrinking safe zone instead constricts a region from all sides.
Change one front's timing, angle, size, or the exit's location only after the base two-source pattern is learned. Keep at least one reachable route under every combination.
Kern charges runes along two flanking walls. Their paired stone fronts close a lower passage, but Tavi can step into the open upper lane before the runes meet.
Basic walking must reach the exit before the fronts arrive. A jump or dash may offer an alternate crossing only when its collision and invulnerability rules explicitly support it; neither should silently become mandatory.
Convergence makes the safe corridor narrower through two announced approaching sources. Moving hazard carries one footprint across the arena, crossfire intersects discrete paths, and shrinking safe area reduces a bounded sanctuary rather than combining two fields.
In the second phase, two Mantis Lords can dash from opposite arena edges at once. Their separate bodies and opposing origins make the shared lower route unsafe, while an airborne response differs from the atlas's walking exit.
In Saltbaker's last phase, the two salt cyclones flank the vertical platform space and slowly close inward. The danger is the narrowing span between large fronts, not a single projectile, with a different vertical response from the atlas diagram.
Halone's Lochos announces two edge-sourced spear rows whose half-arena attacks combine to leave one quarter safe. This is simultaneous convergence of coverage rather than literal moving walls, so the player reads the union of two sources before they resolve.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub