At 0.55 seconds cracks and a lower-room outline announce the destination. From 1.15–2.15 seconds the marked floor gives way and both actors make one collision-free transfer. The encounter state resumes below, but narrower walls and a central rune create a new spatial problem before a visible lift returns the deterministic demonstration.

Open boss builder
Preview and open the floorAt 0.55 s the quarry floor cracks and outlines the lower rune chamber, landing marks, and tighter walls. At 1.15 s the floor opens and both actors begin collision-free authored fall paths while boss progress stays visible.
Show the next arena before taking control away Two stacked rooms show an upper quarry floor cracking above a narrower rune chamber. Kern and Tavi fall along separate fixed paths, land on marked points with encounter progress preserved, resume combat below, and later ride a visible lift back for the loop. Boss Player

At 0.55 s the quarry floor cracks and outlines the lower rune chamber, landing marks, and tighter walls. At 1.15 s the floor opens and both actors begin collision-free authored fall paths while boss progress stays visible.

Implementation checklist

Implement the relocation trigger, destination preview, transfer ownership, state handoff, spawn validation, new geometry, camera behavior, multiplayer policy, and reset as one encounter transition.

Core checks

Three questions for the mechanic

  • What state crosses the boundary?

    List health, phase counters, broken parts, spawned entities, status effects, cooldowns, resources, music position, and objective progress. Choose what persists, converts, pauses, or clears, then make that handoff atomic. A relocated arena should feel like one authored encounter; it should not duplicate the boss, restore a hidden default, or discard a costly player decision.

  • Where can every participant safely arrive?

    Preview the destination before forced movement, validate full-body clearance at each landing point, and reserve space for summons, companions, cameras, and multiplayer groups. Decide who owns the transfer if someone is dead, airborne, grabbed, disconnected, outside the trigger volume, or already inside the destination. Never resolve the move inside active damage or blocked navigation.

  • What new decision justifies the move?

    Change a meaningful spatial rule: width, height, cover, traversal, hazards, line of sight, gravity, footing, or access to the boss. Reframe the camera and reintroduce control before danger resumes. If the second room plays identically, the transition adds spectacle and loading risk without adding a useful phase.

Design mistakes

  • The cut hides a reset or unavoidable hit

    A black frame that restores boss state, moves projectiles onto the player, or resumes an attack before control returns breaks trust. Freeze or resolve live threats explicitly, expose retained progress, and add a protected landing beat whose end is visibly signaled.

  • The new room is only a different backdrop

    If ranges, routes, sight lines, and response verbs are unchanged, relocation becomes production cost without design return. Give the destination one legible geometry change and retune the boss package around it instead of importing every old attack unchanged.

Tuning

Tune the attack

  • Model relocation as a transaction

    Capture encounter state, suspend simulation, assign destination space, validate spawns, move actors, rebuild navigation and camera bounds, restore retained state, then resume. Log failures at each boundary so a partial transfer cannot leave duplicate bosses, missing players, or divergent multiplayer authority.

  • Budget transition time separately from downtime

    Measure signal, forced motion, camera settle, input restoration, and first danger. Skip or accelerate repeated cinematics while preserving the decision-relevant preview. The first visit may carry drama; retries need a stable, readable route back into play.

  • Retune attacks against the new topology

    Recalculate full-body clearances, projectile lifetimes, navigation reachability, off-screen tells, leash distances, and recovery routes in the destination. A pattern that was fair in a broad plaza may become a wall in a narrow chamber, while cover can trivialize a beam authored for open ground.

  • Test joins, deaths, checkpoints, and camera ownership

    Exercise solo and full parties, late joins, revives, split players, summons, photo modes, lock-on, and every checkpoint on both sides of the boundary. Define whether retreat is possible, where a wipe restarts, and how the game recovers if destination streaming or navigation fails.

Arena

  • Kern breaks into the sealed rune chamber

    The upper quarry is a shell over an older chamber that feeds Kern's core. Cracks preview the drop, and the lower room's tighter walls and central conduit explain why the same elemental changes its spatial pressure without becoming a new creature.

Player upgrades

  • Keep Tavi's position and sword legible through the fall

    Tavi loses control only while the floor transfers both actors. A marked landing preserves facing and distance, then ordinary movement and the familiar sword resume before Kern's next rule becomes dangerous. No transition-only verb is required.

Do not confuse this with

  • A new playable space, not a teleport or escape

    Teleport changes an actor's position inside the current spatial rule. Escape phase asks whether the boss reaches an exit and applies a consequence. Relocated arena moves the continuing encounter across a boundary, hands state to a different geometry set, and restores control there.

Bosses that use this mechanic

Learn more

Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub