Guide

Game simultaneous knockdown and double KO systems explained

Harbor Brawl's ranked season opened with a viral clip: both players traded heavies on the last sliver of life, both characters fell, and only one woke up with oki pressure. The loser filed a dispute; replay showed both knockdown animations starting on the same frame. The engine had applied attack priority to damage but not to knockdown state — the higher-priority side kept knockdown ownership and received full hard knockdown floor time while the other character snapped to standing via a fallback idle state. Disputed-round tickets spiked to 23 per week; casters could not explain the outcome on stream.

The simultaneous-KO patch defined a single resolution path: when both fighters enter knockdown on the same frame (or within the trade-KO grace window), the round applies a neutral reset at midscreen unless life totals differ after damage application — in which case the surviving player wins. Double KOs at exactly zero life award the round to whoever dealt more damage that round, then falls back to match-format tie rules. Disputed-round reports fell 54%; trade-KO situations became teachable instead of arbitrary. This guide explains simultaneous knockdown vs double KO, resolution policies, interaction with priority and supers, netcode requirements, the Harbor Brawl refactor, a technique decision table, pitfalls, and a production checklist.

Three outcomes players confuse

Designers often lump “we both fell over” into one bucket. Players, spectators, and netcode disagree unless you separate three distinct cases:

Trade knockdown (mid-round). Both characters enter knockdown while at least one still has life remaining. Neither player has won the round yet. The design question is who gets oki, whether neutral resets, or whether both stand after a shared downed state.
Double KO (round end). Both characters reach zero (or ring-out threshold) on the same frame or within the same damage-resolution batch. The round must declare a winner, declare a draw, or trigger overtime per match format.
Clash without knockdown. Both attacks connect under trade rules but neither move carries knockdown — handled entirely by priority and hitstun, not covered here except where knockdown flags fire late.

Simultaneous knockdown policy must be documented beside your priority table. Resolving damage trades without resolving knockdown ownership creates the exact Harbor Brawl bug: fair-looking trades with unfair wake-up asymmetry.

Trade knockdown resolution policies

When both sides should plausibly hit the floor together, pick one primary policy and apply it consistently across normals, specials, and throws (if your game allows throw trades).

Neutral reset (both down, both recover)

Both characters enter the same knockdown type with identical floor time, then wake up at neutral spacing (often midscreen or at trade point). No oki advantage is granted to either side. This is the clearest policy for spectators and the easiest to keep deterministic online. Harbor Brawl adopted this for same-frame trade knockdowns when life remains on both sides.

Priority-owned knockdown

The win-out side of a trade is treated as the attacker for knockdown purposes: they remain standing or get a short advantage state; the loser takes knockdown and faces oki. This rewards reads in neutral but must be visible — if priority is opaque, players perceive randomness. Only use when your priority system is already published and VFX-distinct.

Shared downed state with simultaneous tech

Both fighters enter a brief shared knockdown animation (e.g., both crumple) and rise on the same frame unless a tech roll or delayed wake-up input differentiates them. Creates skill expression but increases UI burden; document input windows precisely.

Trade grace window

Knockdowns within N frames of each other (commonly 1–3) count as simultaneous even if animations start on adjacent frames. Without a grace window, one-frame network jitter online produces different outcomes offline vs online. Harbor Brawl uses a 2-frame grace window aligned with its trade damage batching.

Double KO and round tie resolution

When both life bars empty in the same resolution step, the round needs explicit rules beyond “who hit first.” Common tournament-grade policies:

Policy	Behavior	Best for
Damage dealt tiebreak	Round to whoever dealt more damage this round; if tied, sudden-death overtime or full round replay	Traditional fighters, Bo3 sets
Shared round draw	Both players receive round win credit (rare) or neither does; match continues	Team battles, casual modes
Initiator wins	Last active attacker ID wins on simultaneous KO	Arcade flow; poor for esports clarity
Super > normal	If one KO was a super and the other was not, super wins even on same frame	Meter-heavy fighters
Ring-out priority	Stage KO beats health KO when both trigger together	Platform fighters

Harbor Brawl ranked uses damage-dealt tiebreak, then a 15-second overtime round with 50% life if still tied — mirroring its timeout policy in the match format guide. Casters can read the tiebreak from the post-round stats panel without opening a rulebook.

Pipeline order: where simultaneous KO fits

Knockdown resolution must run in a fixed combat pipeline slot so rollback netcode can replay matches identically:

Detect hitbox overlap and apply trade/priority rules.
Apply damage, chip, and guard effects per side.
Evaluate knockdown flags for each connected move.
If both sides flagged knockdown within grace window, run simultaneous-KO policy (neutral reset or priority-owned).
If either life ≤ 0, evaluate double-KO policy before spawning oki states.
Commit animation states and pushback only after policy resolves.

Applying knockdown animations before step 5 causes the Harbor Brawl bug: one character enters oki-eligible down state while the other silently stands. Unit tests should include same-frame trade heavies, trade supers, and throw-plus-strike edge cases.

Interaction with supers, assists, and ring-outs

Supers and cinematic freeze. If a super carries invulnerable recovery while the opponent crumples, simultaneous KO rules must define whether the super player wins the round when both die to projectile-aftermath damage. Document whether damage applied during super freeze counts toward tiebreak totals.

Tag and assist overlap. In team fighters, an assist hit and a point-character trade can produce three knockdown candidates. Policy options: point-only resolution, assist ignored for simultaneous KO, or full neutral reset if any two active hurtboxes trade into knockdown. Harbor Siege 3v3 uses point-only with assist hits treated as projectile-tier for priority but not knockdown ownership.

Ring-out double KO. When both characters cross the blast zone same frame, award the round by lower damage percent (platform style) or by last-off-stage frame. Mixed health-and-ring-out games need a precedence table published in the movelist FAQ.

Harbor Brawl refactor: from silent priority to published rules

Before refactor:

Knockdown ownership followed animation start order, not combat policy.
Double KO at zero life awarded the round to player 1 in versus mode.
Replay files did not log simultaneous-KO branch taken.

After refactor:

Same-frame trade knockdown with life remaining triggers neutral reset at trade point; both get soft knockdown with 18 frames floor time, no OTG.
Double KO uses round damage tiebreak; overtime at 50% life if tied.
UI banner: “Trade reset” or “Double KO — damage tiebreak” with winner highlighted.
Combat trace exports sim_ko_policy enum for tournament admins.

Disputed-round tickets fell from 23/week to 11/week; stream chat “rigged trade” messages dropped sharply once the banner shipped.

Technique decision table

Design goal	Prefer simultaneous-KO policy	Prefer alternative
Esports clarity and dispute reduction	Neutral reset + damage tiebreak double KO	Hidden priority-owned knockdown
Reward aggressive trade reads	Priority-owned knockdown with clear VFX	Always neutral reset (flattens risk/reward)
High oki skill ceiling	Shared downed state + tech timing	Automatic neutral reset
Online rollback consistency	2-frame grace + deterministic policy enum	Animation-order knockdown ownership
Casual fun over fairness	Initiator wins double KO	Overtime tiebreak (can feel anticlimactic)
Team fighters with assists	Point-only knockdown ownership table	Global simultaneous reset on any assist trade

Common pitfalls

Resolving damage trades without knockdown policy. Priority tables must include a knockdown column, not only hit confirmation.
Player 1 wins double KO. Legacy versus-mode hacks destroy ranked trust; always use published tiebreaks.
No grace window online. One-frame jitter should not flip oki vs neutral outcomes.
Supers exempt from simultaneous rules. Players will find same-frame super trades; policy must cover them.
OTG after trade reset. If both sides down, neither should face on-the-ground follow-ups unless your policy explicitly grants advantage.
Silent outcomes. Without UI copy, even correct rules feel arbitrary.
Replay gaps. Tournament admins need sim_ko_policy in combat logs to resolve disputes without frame-stepping blind.

Production checklist

Document trade knockdown vs double KO vs clash-without-KD in the combat bible.
Pick primary trade-knockdown policy (neutral reset, priority-owned, or shared down).
Define double-KO tiebreak aligned with match format (damage, overtime, draw).
Set trade grace window (frames) and match it to damage batching.
Insert simultaneous-KO resolution after damage, before oki state spawn.
Cover supers, throws, assists, and ring-out in the same policy table.
Add UI banner or SFX for trade reset and double-KO outcomes.
Export policy enum in replay and combat trace.
Unit-test same-frame trade heavies, trade supers, and zero-life double KOs.
Rollback fuzz test with ±2 frame input offset on trade-KO setups.
Publish rules in movelist FAQ and training mode glossary.
Monitor disputed-round tickets after launch; adjust tiebreak only with season notice.

Key takeaways

Trade knockdown and double KO are different problems — mid-round reset policy vs round-end tiebreak.
Attack priority alone is insufficient; knockdown ownership needs an explicit simultaneous-KO branch.
Harbor Brawl cut disputed-round reports 54% with neutral trade reset and damage tiebreak double KOs.
A 1–3 frame grace window keeps online rollback aligned with offline same-frame trades.
Visible UI and logged policy enums turn opaque engine behavior into teachable, dispute-resistant rules.