A party split turns one boss arena into parallel spaces. Here four living players divide 2+2, complete different left and right objectives, and reopen a shared gate only after both tasks finish. The mechanic is not merely standing far apart: each side has independent progress and the slower side controls the whole group's release.
At 0.65 seconds Kern marks two distinct lanes. Four players travel in assigned pairs, with their whole bodies clear of the central divider by 1.70 seconds.
Reduced motion disables autoplay. Scrub to 0.65, 1.70, 2.60, 3.25, 3.45, and 4.85 seconds.
Define assignment, full-body divider clearance, two independent completion events, a shared deadline, gate logic, reunion, and reset.
Snapshot four distinct living players and assign exactly two to each side. At separation, include each player's 24-unit body radius when checking the central divider; a center on the correct side is insufficient. Lock the roster through the task window so a disconnect or duplicate ID does not silently satisfy both sides.
Give the left and right sides separate objectives and completion events. In the demo, left finishes at 2.60 seconds and right at 3.25. Keep both progress signals visible; do not substitute one aggregate bar, because players must know which side is holding the gate. Test both completion orders and a side that never finishes.
Open the shared gate exactly once after both valid sides finish before 3.60 seconds. A missing player, divider overlap, late task, or duplicate callback must not produce a second opening. Reserve a separate reunion route and log assignments, each task event, gate event ID, deadline result, and reset.
Distance alone does not create parallel work. Both sides need distinct, visible tasks whose completion affects the same gate.
If the faster side finishes and sees only a locked gate, waiting feels arbitrary. Show each side's completion state and the remaining deadline.
Use a physical divider, separate objective shapes, Roman I and II labels, and two progress bars. Hue reinforces the split but cannot be its sole signal.
Measure travel to both lanes, objective interaction, and movement back to the gate at ordinary speed. A group should fail because a task was missed, not because the path is geometrically impossible.
Record an encounter ID and per-side completion times. Resolve the shared gate once after checking both, then reject duplicate callbacks and clear only encounter-local state on retry.
Kern raises a stone wall through the arena. One pair charges a crystal, the other pulls a rune lever; the lower gate lifts only when both circuits answer.
The sides may defeat different enemies, hold switches, or solve asymmetric hazards. You can add a third room, but then recalculate roster size, independent progress, and reunion timing. Preserve the common dependency: no side alone can release the whole group.
Pairing polarity checks who shares a receiving zone at one pulse. Party split checks whether separated teams complete distinct objectives before a shared release. Stack damage asks several players to overlap; here the two teams cannot occupy the same lane while working.
Kaling's first phase separates the party among three Peril rooms, with a small team handling each room. The guide's first-room footage begins here; the two-lane demo deliberately simplifies the three-room version while retaining separate progress before the group proceeds.
Will's first phase divides players between the real and mirror dimensions, each with its own health bar. A team that finishes its side may need to switch or wait for the other side before the phase advances; the clip starts at the phase-one guide chapter.
At Castrum Lacus Litore, the raid splits between upper and lower routes to fight different bosses. Both groups must complete their encounters close together or the delayed side faces an enrage; the guide introduces the first split at this timestamp.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub