Guide

Game down-state and revive systems explained

Harbor Outpost's four-player raid shipped with instant death: one stray grenade and a teammate watched a loading screen for ninety seconds while the squad fought understaffed. Wipes felt random, not earned. The refactor replaced hard death with a down-state: incapacitated players collapsed in place, crawled slowly toward cover, and displayed a bleed-out ring teammates could interrupt with a three-second revive channel. Self-revive kits dropped rarely from elites gave solo recovery options without making every down trivial. Squad wipes only triggered when all four bleed-out timers expired or the team ran out of shared lives on higher difficulties. Co-op sessions lengthened, communication spiked, and failure became a recoverable drama beat instead of a menu trip. A down-state system sits between health reaching zero and permanent elimination — it defines how long a player stays in the fight as a liability, what teammates must do to recover them, and when the run actually ends. This guide covers incapacitation versus instant death, bleed-out timers and crawl verbs, revive channels and interrupts, self-revive economy, shared lives and squad wipe rules, finisher and stomp interactions, PvP down-but-not-out variants, multiplayer authority, UI feedback, the Harbor Outpost raid refactor, genre and technique decision tables, pitfalls, and a production checklist. For sustain after revival, see healing and lifesteal systems; for mitigation before the down-state triggers, see shield and barrier systems.

Down-state versus instant death

When HP hits zero, you choose what zero means:

Instant elimination

Instant death removes the player from combat immediately — respawn at checkpoint, spectate, or wait for round end. It keeps pacing tight in round-based PvP, roguelikes, and single-player action where retry loops are cheap. The cost: co-op feels punitive; one mistake sidelines a friend; and clutch recovery stories never happen.

Incapacitated down-state

Down-state keeps the entity in the world as incapacitated: prone, ragdolled, or in a wounded crawl animation. The player retains limited agency (ping enemies, call for help, slow crawl) while teammates or systems decide survival. Down-state creates a window — tension between bleed-out expiry and rescue — that instant death skips entirely.

Hybrid triggers

Many games use both: first down enters bleed-out; second down while already injured causes instant death; or boss fights disable revives to spike stakes. Document hybrid rules in UI tutorials — players assume consistency across modes.

Bleed-out timers and crawl mechanics

The bleed-out timer is the countdown from incapacitation to permanent death. It is your primary tension dial.

Timer length by context

Co-op PvE raids often use 30–60 seconds — long enough to finish a wave and reach the body. Fast PvP modes use 5–15 seconds so downed enemies do not stall rounds. Battle royale titles stretch timers when a teammate is actively reviving (dynamic extension) to reward commitment. Tune against average teammate travel time in your largest arenas.

Crawl and limited agency

Letting downed players crawl toward cover turns passive waiting into micro-decisions: reach a revive beacon, hide behind a crate, or bait enemies away from the medic. Cap crawl speed well below walk speed; disable sprint and weapons unless your genre demands “last stand” pistol fantasy. Ping and voice-call shortcuts matter more than movement when crawl is disabled (common in military sims).

Timer visibility

Show bleed-out as a radial ring on the body, a skull icon on teammates' HUD, and audio ticks in the final five seconds. Hidden timers feel like arbitrary deaths; overly loud timers train players to ignore them.

Revive channels: hold, progress, and interrupts

Revive is the action that exits down-state and restores a playable fraction of health.

Hold-to-revive channels

The rescuer stands near the body and holds an interact key for N seconds while a progress bar fills. Standard channel lengths: 2–4 s in action co-op, 6–10 s in tactical shooters where revives are high stakes. The reviver is vulnerable during the channel — that vulnerability is the gameplay. If taking damage cancels the channel, document whether partial progress persists.

Skill and item revives

Healer classes may cast faster revives at range with cooldown gates. Consumable syringes or defibrillators trade inventory slots for instant or boosted recovery. Tie item revives to your healing economy so medics stay distinct from DPS carrying one emergency pick.

Interrupt rules

Enemies can interrupt revives by meleeing the rescuer, applying suppression, or executing a finisher on the downed body. Finishers should telegraph (wind-up animation, UI prompt) so counterplay exists. Silent instant executions frustrate co-op groups.

Self-revive, second chance, and shared lives

Self-revive kits

Self-revive items let a downed player recover without a teammate — critical for solo play in co-op-tuned titles and for duos when both go down. Limit charges per mission or long cooldowns; otherwise squad wipes never happen and tension flatlines. Common pattern: one self-revive per run, consumed on use, not refillable from vendors mid-raid.

Second-chance perks and passives

Roguelike “phoenix” passives, battle royale self-revive stations, and class traits that auto-stabilize at 1 HP once per life are variations on the same knob. Treat them as loadout choices with visible UI charges so opponents and teammates can plan around them.

Shared lives and squad wipe

Shared lives pools (e.g. four deaths per mission across the squad) convert individual downs into team resource management. A squad wipe occurs when all players are simultaneously down with no revives remaining, all bleed-out timers expire, or the shared life pool hits zero. Clarify whether a successful revive refunds a life or only delays the pool decrement until bleed-out completes.

Post-revive state and combat re-entry

Revival is not resurrection at full power. Standard patterns:

Fractional HP — revive at 30–50% max health so re-entry is risky.
Brief invulnerability — 1–2 s i-frames to stand up; prevents spawn camping the body.
Revive sickness — reduced damage or movement for 5–10 s; discourages revive-tanking in open fields.
Ammo and ability reset — some titles refill magazines; others preserve state for continuity.

Align post-revive HP with your damage pipeline so enemies cannot immediately re-down revived players in one bullet unless that is an explicit hard-mode rule.

PvP down-but-not-out variants

Competitive modes adapt down-state differently than co-op:

Execution prompts — downed enemies can be finished for bonus points or denied self-revive.
Revive beacons — battle royale teammates place a slow channel at a fixed pad; third-party teams contest the site.
Gulag and 1v1 redeploy — death sends players to a side arena; win returns you to the match. No bleed-out, but same recovery fantasy.
No revives in ranked — down-state exists only as a short bleed for confirm kills.

PvP revive rules must be symmetric and server-authoritative. Client-side revive exploits are common attack surfaces in BR and extraction shooters.

Multiplayer authority and edge cases

Server (or host) must own down-state transitions:

Who is down, bleed-out start time, and whether revive channel is active.
Simultaneous downs — process in tick order; both can enter down-state same frame.
Revive during squad wipe resolution — cancel wipe if any revive completes before timers expire.
Disconnect while down — pause timer, convert to bot corpse, or instant bleed-out per policy.
Level transitions — auto-revive at checkpoint vs fail mission if anyone was down.
Environmental deaths (falling off map) — often skip down-state; document exceptions.

Log down, revive, and bleed-out events in combat telemetry. Spikes in unrevived deaths indicate tuning problems or unclear UI.

UI and feedback

Downed player: desaturate screen edges, show bleed-out ring, display “hold for self-revive” if kit available.
Teammates: world marker on body, distance callout, revive prompt when in range.
Enemies: distinct downed silhouette or icon so finishers target correctly.
Audio: heartbeat that accelerates, distinct revive channel loop, squad wipe sting.
Accessibility: optional extended bleed-out, single-press revive toggle for hold fatigue.

Harbor Outpost squad raid refactor (worked example)

Before: zero HP triggered instant death and a 90 s respawn timer at zone entrance. Understaffed fights cascaded into wipes; players skipped mechanics to babysit respawns.

Changes:

45 s bleed-out with 25% crawl speed toward nearest cover normal.
3 s hold-to-revive; damage cancels channel but retains 50% progress.
Revive at 40% HP + 2 s i-frames + 8 s “wounded” debuff (−20% damage).
One self-revive kit per player per raid, dropped from second elite kill if unused.
Shared pool of six squad deaths on heroic; bleed-out expiry decrements pool.
Boss phase 3 disables revives — announced 10 s prior via VO and UI banner.

Result: average encounter length rose 18%; wipe rate on first heroic clear dropped; voice comms usage measured in playtests doubled during bleed-out windows. Players reported deaths felt “fair if we choked the revive.”

Genre decision table

Genre	Typical down-state	Revive pattern
Co-op PvE shooter	30–60 s bleed, crawl enabled	Hold-to-revive, shared lives
Tactical / SWAT sim	Instant death or no revive	Mission fail on incapacitation
Battle royale	Timed bleed, beacon revive	Channel at pad, self-revive rare
Action RPG	Short down or shared ghost realm	Class skill / resurrection spell
Roguelike	Usually instant death	Meta unlock second chance
MMO raid	Death release spirit, combat rez	Healer cast with cooldown
Fighting game	Round KO only	N/A until next round

Technique decision table

Design goal	Prefer	Avoid
Co-op teamwork	Visible bleed-out, interruptible revive	Instant death with long respawn
High stakes tension	Short bleed, finisher telegraphs	Infinite self-revive charges
Solo-friendly co-op	Self-revive kit per mission	Hard gate requiring two alive players
Competitive integrity	Server-owned revive state	Client progress bars only
Boss climax	Revive-disabled phase callout	Silent no-revive surprise
Accessibility	Extended bleed toggle, tap revive	Pixel-perfect crawl required

Common pitfalls

Bleed-out shorter than travel time — revives mathematically impossible in large maps.
Revive without vulnerability — no risk to rescuer removes co-op tension.
Full HP on revive — down-state becomes a brief animation, not a setback.
Hidden shared life pool — players do not understand why the mission ended.
Self-revive spam — unlimited kits erase squad wipe threat.
Unclear finisher rules — players blame netcode when executions fail.
Boss no-revive without warning — feels like a rule change, not drama.
Down-state in solo with no self-revive — forces restart with no counterplay.

Implementation checklist

Define down-state entry: HP ≤ 0, fall damage exception list, boss phase flags.
Author bleed-out duration per difficulty; optional dynamic extension during active revive.
Implement crawl speed, allowed actions, and ping/call-for-help inputs.
Build hold-to-revive with progress, cancel-on-damage, and partial progress policy.
Set post-revive HP, i-frames, and wounded debuff magnitudes in data tables.
Configure self-revive kit drop rates, charges, and UI prompts.
Wire shared life pool and squad wipe resolution order on server.
Add finisher/interrupt animations with telegraph windows.
Handle disconnect, level transition, and reconnect while down.
Ship HUD markers, audio heartbeat, and accessibility toggles.
Playtest solo, duo, and full squad bleed-out travel times per map.
Log down, revive success, bleed-out expiry, and squad wipe in telemetry.

Key takeaways

Down-state is a time window — bleed-out length defines co-op drama.
Revive channels need vulnerability — rescuers must expose themselves.
Post-revive weakness prevents down-state from being a free reset.
Self-revive is a scarce safety valve for solo and duo edge cases.
Shared lives convert individual mistakes into team resources.
Server authority on revive state is non-negotiable in multiplayer.