Guide

Game kill cam and death camera systems explained

Harbor Crest's tactical shooter beta locked the death camera on the victim's ragdoll for four seconds while a static death recap panel listed damage sources. Ranked telemetry showed 64% of deaths followed by an immediate queue dodge or session exit tagged “unfair death.” Players could read that a sniper killed them but never saw the angle, peek timing, or whether lag compensation rewound their position into an open window. Support volume clustered on “I was behind cover” — unverifiable without a replay POV.

The refactor shipped a server-rewound kill cam: three to five seconds from the killer's perspective, skippable after 0.5 s, paired with a compact recap overlay. Unfair-death churn fell from 64% to 13%; repeat-death reports against the same camper dropped once victims could see off-angle holds. A kill cam is the death camera that answers “what did they see when they shot me?” This guide covers the death-camera FSM, replay camera modes, rewind authority, duration and skip UX, ranked disclosure policy, spawn integration, the Harbor Crest refactor, a technique decision table, pitfalls, and a production checklist alongside replay systems and spawn protection.

Death camera FSM: from elimination to respawn

Treat the post-death camera as a finite-state machine, not a single animation. Typical states:

Impact freeze (0–200 ms) — brief hit-stop on final damage; optional directional damage indicator
Ragdoll or collapse (200–800 ms) — body physics; camera may orbit corpse
Kill cam replay (3–5 s) — rewind segment from killer POV or chase cam
Recap hold (until skip or respawn) — static panel with damage breakdown
Respawn transition — fade to spawn point with protection window

States 2 and 3 are often merged in fast-paced modes: skip ragdoll entirely and cut straight to kill cam on competitive playlists. Casual modes may linger on ragdoll for spectacle. The FSM must accept skip input in every non-respawn state — forced watch time is a top quit trigger in FPS playtests.

Parallel vs sequential recap

Sequential: kill cam plays, then recap panel appears. Cleaner visually; adds total downtime.
Parallel: semi-transparent recap overlays the kill cam corner. Harbor Crest used parallel so players could read damage percentages while watching the angle. Keep overlay opacity below 40% so crosshair and peek lines stay readable.

Camera modes and when to use each

Mode	What player sees	Best for	Risk
Killer POV	Exact aim reticle, ADS state, recoil	Teaching angles; verifying peek fairness	Reveals killer position to victim
Third-person chase	Camera behind killer at offset	Melee and ability kills; readability	Less precise for hitbox disputes
Neutral cinematic	Midpoint between combatants	Environmental kills, multi-kill trades	May obscure who shot first
Victim corpse orbit	Spin around dead body	Battle royale looting context	Does not explain off-angle deaths
Damage timeline scrub	Pause frame on each hit with arrow	High-TTK RPG shooters	Higher implementation cost

Most tactical shooters default to killer POV for gunfights and chase cam for explosives and melee finishers where first-person view is disorienting. Document mode selection in server kill events so QA can assert the correct camera path per weapon class.

Field of view and ADS matching

Replay FOV must match the killer's hip-fire and ADS FOV at each frame. Showing a wider FOV than the killer had makes peeks look easier than they were; narrower FOV makes fair shots look like snap cheats. Sync weapon sway and recoil animation on the replay rig so victims can evaluate spray control.

Server rewind and replay authority

Client-side kill cams built from local state lie. The victim's machine does not have the killer's true aim history, and without server rewind the replay cannot show whether lag compensation opened a window that felt unfair locally. Production pattern:

Server records a ring buffer of compact snapshots per player (position, rotation, stance, weapon state) for the last 8–12 seconds
On confirmed kill, server tags rewind start time (usually 3–5 s before fatal hit) and killer entity id
Death payload to victim includes rewind token, snapshot slice, and hit event list validated by hit registration
Client interpolates snapshots into a smooth camera path; server does not stream video

For trades (simultaneous deaths), pick a deterministic rule: show the cam of whoever the server adjudicated as dying second, or show neutral cinematic. Ambiguous trade cams are a major fairness complaint in dual-kill scenarios.

Bandwidth and cheat surface

Send only the killer's snapshot slice to the victim, not full lobby state. Validate rewind tokens expire after one use and bind to victim session id so replay data cannot be scraped for wallhack-style intel mid-round. In ranked modes, some teams delay killer POV until round end while still sending damage recap immediately — a compromise between fairness education and competitive integrity.

Duration, skip, and respawn coupling

Kill cam length trades learning against pace. Rules of thumb from shipped FPS titles:

Casual / team deathmatch: 4–5 s cam, skip after 0.5 s
Ranked / bomb defusal: 3 s cam or recap-only; skip after 0.25 s
Battle royale: optional full death recap; spectator handoff instead of cam
High player count: shorten cam when respawn queue is long

Tie cam end to respawn timer, not the reverse. If respawn is instant, cap cam at 2 s or allow cam to continue in a corner overlay during spawn protection. Harbor Crest aligned cam end with respawn button readiness so players never waited idle after skipping.

Input during death

Accept skip on any button (not only Space). Allow loadout and tactic menu access during recap hold so players can plan the next life. Block movement and fire input. In spectator-enabled modes, offer “Spectate killer” only after cam ends to prevent ghosting through cam data.

Ranked disclosure and streamer privacy

Killer POV cams leak live position. Policies by tier:

Casual: full killer POV; show killer name and clan tag
Ranked: full POV but hide killer name until round end; optional delay cam in finals
Streamer mode: anonymize killer skin and name; generic weapon silhouette
Custom / league: admin toggle per match; VOD delay alignment

Distance readouts on cam HUD help victims judge sniper legitimacy but enable stream-sniping in small lobbies. Gate distance behind a “competitive integrity” setting defaulting off in ranked. Never show enemy minimap pings or teammate positions in kill cam renders.

Harbor Crest refactor walkthrough

Harbor's combat UX team replaced corpse-orbit death with a rewind pipeline:

Snapshot buffer — 10 s per player at 20 Hz compact keys; weapon fire events stored separately for muzzle flash sync
Kill event payload — victim receives 4 s rewind + hit list with body zone, damage type, penetration flag
Camera rig — killer POV for hitscan; 2 m chase offset for grenades and melee; FOV lerps on ADS transitions
Skip UX — any input after 500 ms; progress bar shows remaining cam time without blocking center reticle
Ranked policy — killer name masked; cam unchanged so angle disputes remain resolvable
Spawn handoff — cam ends 200 ms before spawn protection activates; no overlap where victim sees live round through protection bubble

Outcomes: unfair-death churn 64% to 13%; average deaths per session rose 18%; “behind cover” tickets fell 71% once rewind showed peek timing; cam skip rate stabilized at 42% (players watch when learning, skip when respawn matters).

Technique decision table

Approach	Best for	Weak when
Corpse orbit only	BR looting, stylized arcade	Off-angle disputes; tactical learning
Recap panel only	Fast respawn, low dev cost	Players cannot verify peek or netcode
Server-rewound killer POV	Tactical shooters, ranked fairness	Snapshot storage; privacy in small lobbies
Chase cam only	Melee, abilities, third-person titles	Hitscan angle disputes stay opaque
Full round VOD replay	Esports, anti-cheat review	Overkill for casual death UX
Delayed ranked cam	Competitive integrity	Frustrates immediate learning

Common pitfalls

Client-only replay — angles do not match server truth; fuels “cheater” reports.
Forced full watch — Harbor pre-refactor quit spikes; always allow early skip.
FOV mismatch — makes fair peeks look illegal or vice versa.
Ignoring trade kills — dual-death cams need deterministic rules.
Showing live killer after cam — free wallhack if cam ends while killer holds angle on corpse.
Cam longer than respawn — players idle angry; sync timers.
No penetration flags in overlay — wallbang deaths feel random without recap context.
Environmental kills with killer POV — disorienting; use neutral cam.
Snapshot gaps on packet loss — stuttering cam reads as bug; interpolate or shorten window.

Production checklist

Define death-camera FSM states and skip behavior per playlist.
Record server snapshot ring buffer with weapon and stance keys.
On kill, package rewind slice + validated hit list to victim only.
Match replay FOV to killer hip and ADS at each frame.
Select camera mode by weapon class (POV vs chase vs neutral).
Cap cam duration; enable skip after 250–500 ms.
Align cam end with respawn timer and spawn protection start.
Pair with death recap overlay (parallel or sequential).
Apply ranked name masking and streamer anonymization presets.
Handle trade kills, environmental kills, and team kills explicitly.
Telemetry: skip rate, watch duration, unfair-death survey, ticket tags.

Key takeaways

Kill cam answers what the killer saw — recap alone lists damage but not angle.
Server rewind is mandatory for hitscan fairness and lag-comp verification.
Skip early, always — learning and pace coexist only with player control.
Match FOV and ADS on replay — or peeks look wrong.
Harbor Crest cut unfair-death churn 64% to 13% with rewind POV plus instant skip.