A player-controlled boss combines authored encounter structure with an opponent who can improvise. The boss role needs an explicit assignment flow, a bounded move set, readable telegraphs, encounter-owned health and rewards, and an AI fallback that preserves the same contract when matchmaking fails or the controller disconnects.
The encounter opens in a matching state. At 0.70 s an eligible remote controller appears; at 1.20 s the crown token moves onto Kern and the role becomes authoritative. Tavi remains outside danger until the assignment is visible and complete.
Autoplay is disabled by reduced motion. Scrub across 0.70, 1.20, 1.55, 2.05, 2.18, 2.68, 3.08, 3.55, 3.95, 4.45, and 5.20 seconds to inspect matching, assignment, input, telegraph, attack, recovery, disconnect, AI takeover, continuation, and reset.
Define eligibility, consent, matchmaking timeout, role handoff, boss loadout normalization, legal actions, telegraph floors, health and resource authority, challenger scaling, latency compensation, disconnect and AFK detection, AI takeover, rematch rules, grief prevention, rewards, accessibility, privacy-safe telemetry, and deterministic tests for every transition.
Define opt-in, region, latency, progression, party, rank, repeat-opponent, and platform rules before searching. Time out into a known AI rather than holding the challenger at a door. Make one server-authoritative transition assign the controller, normalize their boss package, close late joins, announce the role to both sides, and start danger only after clients acknowledge the same state.
Give the controller meaningful choices inside authored constraints: select moves, aim within bounds, vary spacing, manage a boss resource, or coordinate limbs. Keep minimum startups, collision shapes, active windows, recovery, arena limits, health, phase gates, and forbidden exploits encounter-owned. Normalize imported builds or replace them with a role kit so matchmaking does not become an invisible difficulty roll.
Track heartbeat, input age, AFK duration, packet loss, illegal commands, surrender, and disconnect. On failure, stop accepting remote commands, freeze into a safe non-damaging beat, transfer the same state to AI, then resume without healing, repeating the intro, or duplicating rewards. Test reconnect policy, co-op scaling, host migration, rollback, grief stalls, intentional disconnects, and both victory orders.
Unbounded cancel timing, animation swaps, status stacks, or imported equipment turn the authored fight into ordinary PvP with a boss health bar. Route every command through an encounter action graph, enforce startup and recovery on the authority, normalize stats, and reject commands that cannot be represented by the visible state.
A rare controller must not become a required external dependency. Set a short, communicated search budget, preload the fallback, preserve boss health and phase state during takeover, and make reward ownership idempotent. Simulate no candidate, late candidate, AFK, high latency, disconnect during startup and active frames, and both clients leaving.
Write two lists. Expression includes move choice, target selection, spacing, feints that still pay their startup, and resource timing. Invariants include telegraph floors, hit geometry, recovery, arena bounds, phase progression, health, and reward authority. The controller can surprise through choices, not by hiding the rules.
Compare experienced and novice controllers, solo and co-op challengers, latency bands, controller input rates, and AI fallback. Prefer a bounded role kit, cooldown economy, poise or resistance budget, and challenger-count modifiers over copying a player's full build. Cap stall tools and healing so survival cannot replace engagement.
Use a crown, aura shape, nameplate label, arrival animation, announcer line, caption, and HUD state to show that another player has the boss role. When AI takes over, change the ownership marker without changing the boss silhouette or response vocabulary. Do not reveal private account data beyond the game's normal multiplayer identity.
Log search time, assignment source, normalized kit, command acceptance, telegraph start, authoritative hit, heartbeat age, takeover cause, transferred health and cooldowns, outcome, rematch, and reward grant. Automated tests should prove that one controller owns Kern at a time, illegal inputs do nothing, every damaging action was visibly announced, and each result pays once.
The quarry's crown searches the old rune network and finds another challenger. Its sigil settles above Kern, whose familiar stone body now waits, baits, and commits with a human rhythm—but every rune still lights before danger. When the link breaks, the crown dims to an amber machine-glyph and the elemental continues from the same cracked core.
Use opt-in matchmaking, a visible search timeout, input buffering, generous but fixed telegraph floors, captions for ownership and connection state, non-color icons, an AI fallback, and a complete offline path. Let players hide remote names, reduce social signals, or choose AI-only play without changing progression rewards.
An invasion adds a hostile player to the world under general PvP rules. A player-controlled boss assigns that person the encounter's boss slot, health, move constraints, arena, phase gates, and rewards. A mimic or adaptive AI only imitates player behavior; here a real participant supplies decisions, while AI exists as a contract-compatible fallback.
At the final portal, the human challenger fights a multi-part boss whose limbs are controlled cooperatively by the other local players; empty roles can be filled by bots. Splitting the boss action set across controllers creates coordinated expression while the arena, shared body, attack packages, health, and victory condition remain authored.
The Old Monk can summon an actual network player as the Black Phantom boss. If the host is offline or no suitable participant is found, an NPC fills the role. The encounter demonstrates explicit role substitution: a human supplies combat decisions, while the arena, boss objective, health framing, reward, and fallback remain system-owned.
Online, the ritual can summon another player into the boss role instead of the NPC Halflight. The summoned Spear receives encounter-specific support and constraints rather than merely invading an open level; offline or failed matchmaking restores Halflight. The swap preserves progression while producing a distinct human cadence.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub