Guide

Game kill feed and death recap systems explained

Harbor Outpost's team-deathmatch beta shipped with a minimalist death screen: “You were eliminated” and a three-second respawn timer. No killer name, no weapon icon, no distance readout. Playtest telemetry showed 71% of deaths followed by a confused camera sweep — players spun looking for the shooter they never saw. Spawn campers exploited the gap: victims respawned into the same sightline because they could not identify the threat from the feed. Support tickets clustered around “who killed me?” and “how did they one-shot me?” even though damage math was balanced.

The refactor built a structured kill feed and a personal death recap panel. Each elimination row shows killer, victim, weapon silhouette, headshot badge, and assist credit. When you die, a recap card lists the last three damage sources with percentages, distance bands, and whether each hit pierced cover. Post-death confusion fell from 71% to 18%; spawn-kill reports dropped once players could read camper loadouts and reposition. A kill feed is the multiplayer combat log: it closes the information loop death opens. This guide covers feed row anatomy, assist and environmental kills, recap and kill-cam integration, competitive density tiers, streamer anonymization, server authority rules, the Harbor Outpost refactor, a technique decision table, pitfalls, and a production checklist alongside shooter design and spawn protection.

What a kill feed is (and why it matters)

In solo games, death is a private event. In multiplayer, every elimination is shared state: teammates need situational awareness, spectators need narrative, and the victim needs closure. The kill feed is the lightweight broadcast channel for that state.

A well-designed feed answers four questions at a glance:

Who got the kill and who died
With what weapon or ability
How — headshot, melee, environmental, team kill
Context — streak callouts, objective ties, assist splits

Without those answers, players blame netcode, damage numbers, or spawn logic when the real issue is unreadable feedback. The feed is also a social layer: multi-kill streaks, revenge tags, and clutch trades become visible stories that drive retention in ranged combat modes.

Feed row anatomy

Most shooters use a vertical stack in the upper-right HUD. Each row is a left-to-right sentence: [killer] [weapon icon] [victim], with optional modifiers trailing or embedded.

Element	Purpose	Design notes
Player names	Attribution	Team color on name text; truncate long names with ellipsis; clan tag prefix optional
Weapon icon	Loadout read	Silhouette readable at 16–24 px; distinct sidearm vs rifle shapes
Headshot badge	Skill signal	Skull, crosshair, or gold tint — one consistent glyph across modes
Distance (optional)	Legitimacy check	Show on personal death only in casual; hide in ranked to reduce stream-sniping
Streak callout	Hype	“Double kill”, “Shutdown” — separate line or inline badge
Suicide / environmental	Clarity	“Fell”, “Explosion” with world icon instead of weapon

Row lifetime and stacking

Rows typically fade after 6–10 seconds or when the stack exceeds 5–8 entries. High-TTK modes need longer persistence; battle royale lobbies may cap at four rows to preserve minimap space. New rows push old ones down; critical personal events (your kill, your death, your assist) can pin with a highlight border for one extra second before joining the fade queue.

Team versus free-for-all coloring

Team modes should color-code names (ally blue, enemy red, neutral gray) while keeping weapon icons monochrome for readability. FFA modes often use neutral white names with a gold highlight on the local player. Never rely on color alone — add an ally/enemy icon for color-blind presets.

Assist credit and shared eliminations

Assist rules define who appears on the feed when damage is split. Common models:

Last-hit killer only — simplest; frustrates support players
Assist if ≥ X% damage within Y seconds — industry default (~30% within 5 s)
Full feed row per assist — “PlayerA + PlayerB eliminated PlayerC”
Personal assist ping — killer row plus a subtle “You assisted” toast

Harbor Outpost adopted threshold assists with a compact inline format: Alpha [rifle] Bravo + Charlie when two players contributed. Objective modes tie feed events to flag captures and zone clears so feed noise reflects mode goals, not just fragging.

Environmental and ability kills

Falling, lava, train hits, and map hazards need distinct iconography — not a generic skull. Ability kills (grenades, turrets, deployables) should show the ability icon and attribute ownership to the player who placed or triggered it. Ambiguous cases (player A throws molotov, player B shoots the barrel) require server-side priority rules documented in design specs so QA can reproduce feed output.

Death recap and kill cam integration

The feed tells the lobby what happened. The death recap tells you why you died. Best practice pairs them:

Death triggers recap panel (damage sources, percentages, body region hit)
Optional kill cam replays last 3–5 seconds from killer POV or a neutral chase cam
Recap stays visible until respawn or skip input; kill cam skippable after 1 s

Recap rows should mirror server-validated damage events, not client guesses. Show shield versus health consumption separately when shields exist. Include penetration and wallbang flags if your game supports ballistic penetration so victims understand off-angle deaths.

Kill cam fairness

Kill cams reveal position. Competitive ranked modes often disable killer POV cams or delay them until round end. Casual modes benefit from full cams that teach map lines and recoil control. Always allow instant skip — forced watch time is a top quit trigger in playtests.

Information density tiers

One feed layout rarely fits all modes. Ship presets:

Tier	Audience	Feed content	Death recap
Minimal	Hardcore ranked, esports	Names + weapon only; no streaks	Recap off or post-round only
Standard	Quick play, core TDM	Full rows, streak callouts, assists	3-source recap, skippable cam
Verbose	New-player onboarding, PvE hybrids	Distance hints, damage type tags	Extended recap with tips (“Try crouch behind cover”)
Spectator	Streams, tournaments	All eliminations + objective events	Director-chosen replay hooks

Let players override within bounds — hiding streak banners is fine; hiding enemy names in ranked is not.

Server authority and anti-cheat display

The feed must reflect server-confirmed kills, not client hit reactions. Display kills only after the elimination event commits on the authoritative simulation. Showing a feed row before validation creates “ghost kills” when lag compensation rewinds.

Queue feed events behind the same RPC that decrements victim health to zero
Suppress feed rows for rejected hits (out of date, already dead)
Flag team kills and suicides with distinct styling; optional penalty callout
In spectator mode, delay feed 1–2 s if your anti-cheat policy requires it

Accessibility and streamer modes

Kill feeds carry PII (player names). Streamer mode should anonymize third-party names (“Player 3”, “Enemy Sniper”) while keeping weapon and event structure. Color-blind presets need non-color cues on team affiliation. Motion-sensitive players may disable row slide animations and kill-cam blur.

Screen-reader support: announce personal deaths and multi-kills via a concise audio cue; do not read the entire feed aloud every row. Tie into your broader HUD accessibility settings so combat feedback presets stay consistent.

Harbor Outpost refactor walkthrough

The beta's blank death screen failed three design goals: learning (players could not adapt), fairness (spawn campers invisible), and hype (multi-kills invisible to teammates). The refactor shipped in two passes:

Pass 1: Structured kill feed

Upper-right stack, max six rows, 8 s fade
Weapon silhouettes for all 14 primary weapons plus melee and grenade icons
Gold headshot pip inline with weapon icon
Personal highlight: your kills get a green left border; your deaths get red
Assist threshold: 25% damage within 4 s, shown as “+ AssisterName”

Pass 2: Death recap card

Left-side panel on death: killer name, weapon, distance band (<15 m / 15–40 m / >40 m)
Three-line damage log with percentages (e.g. “42% rifle body, 38% rifle head, 20% grenade splash”)
Skippable 3 s kill cam defaulting to chase cam (not full killer POV in ranked)
Recap persists through spawn protection invulnerability so players read before re-engaging

Confusion telemetry (camera spin + no movement within 2 s of respawn) dropped 71% to 18%. Spawn-kill tickets fell 41% without changing spawn algorithms — players simply learned to avoid known camper loadouts.

Technique decision table

Approach	Best for	Trade-off
Scoreboard-only (no feed)	Minimal HUD experiments, slow TTK co-op	Players lack real-time awareness; death feels opaque
Text-only feed	Low-art prototypes, accessibility-first	Slower weapon recognition at glance
Icon + name feed (recommended default)	TDM, battle royale, arena shooters	Requires icon library maintenance per weapon
Feed + death recap	Competitive shooters teaching map knowledge	UI engineering + server damage log plumbing
Feed + recap + kill cam	Casual onboarding, highlight reels	Position leak risk; skip button mandatory
Spectator broadcast feed	Esports, stream overlays	Separate layout pipeline from player HUD

Common pitfalls

Blank death screen — players blame balance instead of reading threats.
Client-side feed rows — ghost kills erode trust in netcode.
Unreadable weapon icons — 12 px silhouettes that all look like rifles.
Forced kill cam — top quit reason in Harbor playtests before skip was added.
No assist credit — support and zone-control roles feel invisible.
Feed spam in large lobbies — 32-player chaos needs filtering (team-only toggle).
Same styling for team kills — griefing looks identical to enemy frags.
Recap without shield breakdown — players misread TTK when shields absorb first.
Streamer mode forgotten — name leaks discourage content creation.
Feed hidden during scoreboard — tab overlay should not erase combat context.

Production checklist

Define feed row schema: killer, victim, weapon, modifiers, timestamp.
Build weapon icon set at target HUD resolution; test at 1080p and 720p.
Document assist threshold (damage % and time window) per game mode.
Emit feed events only from server-confirmed elimination handler.
Implement row stack cap, fade timer, and personal highlight rules.
Ship death recap with damage-source percentages from authoritative log.
Separate shield, health, and overkill display in recap rows.
Add skippable kill cam with ranked vs casual POV policy.
Provide team-kill, suicide, and environmental icon variants.
Expose streamer anonymization and color-blind presets.
Sync feed styling with broader HUD clutter budget.
Playtest: can victims name killer weapon within 2 s of death?
Telemetry: track post-death confusion proxy (camera spin, idle time).
Localize streak callouts; keep weapon icons locale-independent.
Verify feed does not overlap critical objective UI on all aspect ratios.

Key takeaways

Kill feed = shared combat log — attribution, weapon, and context at a glance.
Death recap closes the personal loop — damage sources explain opaque deaths.
Server authority is non-negotiable — never show unconfirmed eliminations.
Density tiers fit different modes — ranked minimal, onboarding verbose.
Harbor cut confusion 71% to 18% without changing spawn or damage formulas.