Guide

Game ring-out and stage KO systems explained

Harbor Siege shipped a tournament-legal cliff stage with narrow walkable platforms and instant ring-out past the ledge. Telemetry from 12,400 ranked duels showed a skewed win distribution: 38% of rounds ended in ring-outs at under 15% accumulated damage, often from a single back-throw or a light hit that barely moved the defender. Grapplers with command grabs dominated pick rate on that stage (+22% vs roster average) while zoners saw queue dodges spike 31%. Players described rounds as “decided by geometry, not reads.”

The stage team kept ring-outs as a win condition but retuned three coupled systems: blast-zone distance from the playable surface, kill-percent scaling on knockback, and a minimum-damage gate on throw ring-outs. Zero-damage cliff KOs fell to 9%; average round damage before a ring-out rose from 11% to 47%. Edge threat remained real — late-percent ring-outs still closed rounds — but neutral now had room to breathe. This guide covers ring-out geometry models, kill-percent curves, knockback coupling, corner and edge pressure, throw interactions, the Harbor Siege refactor, a technique decision table versus health-only KO rounds, pitfalls, and a production checklist.

What ring-out adds beyond health depletion

A ring-out (stage KO, blast-zone KO, out-of-bounds KO) ends the round when a character crosses a stage boundary — usually while in hitstun, throw state, or helpless aerial recovery. It is a spatial win condition layered on top of (or instead of) draining a health bar. The design levers differ from damage-only fighters:

Position becomes damage — standing near the edge multiplies threat even at low percent; center stage is defensive real estate.
Knockback direction matters more than magnitude — a weak horizontal push at the ledge beats a strong vertical launcher in center (see knockback systems).
Stage selection is balance — the same matchup shifts when blast zones tighten or platforms shrink; ban lists must account for geometry, not just visuals.
Time-to-kill variance widens — ring-outs enable early round swings that health-only systems rarely allow without one-touch kill bugs.

Ring-out systems pair naturally with round-based match formats where each game resets position. Stock-based platform fighters often use multiple lives per round; traditional 2D fighters typically treat one ring-out as an immediate round win.

Ring-out geometry models

Engines implement stage boundaries in a few recurring patterns. Pick one primary model per game; mixing without documentation confuses players and netcode auditors.

Blast zones (invisible kill planes)

Popular in platform fighters: axis-aligned rectangles beyond the camera frame. When the hurtbox center (or any hurtbox point — document which) crosses left/right/top/bottom blast zones, the stock is lost. Distance from the ledge defines how “small” a stage feels. Competitive rules often normalize blast-zone distance across legal stagelist entries.

Walk-off ledges (instant ring-out)

Common in 3D arena fighters: leaving the walkable polygon triggers immediate KO regardless of damage. Edge thickness matters — a one-pixel gap between visual cliff and collision mesh produces rage-quit clips. Add a short re-entry grace only if your game supports ledge climb mechanics; otherwise keep walk-off deterministic.

Damage-gated ring zones

A hybrid: crossing the boundary only KOs if accumulated damage exceeds a threshold (e.g. 150% in platform fighters, or a flat 40% in hybrid brawlers). Below threshold, the engine clamps position or plays a stumble animation at the edge. This separates “edge scare” from “edge kill.”

Hazard ring-outs

Spikes, lava, water, and trains apply ring-out on contact, sometimes ignoring percent gates. Treat hazards as authored exceptions in your data table — do not inherit default blast-zone rules silently.

Kill percent and knockback scaling

Most ring-out fighters do not kill at zero damage. Instead, kill percent (or damage percent) scales knockback on each hit so that the same move sends farther as percent rises. The curve shape defines when edge becomes lethal:

Base knockback — fixed launch vector per move at 0% (often negligible for light attacks).
Growth factor — multiplier per percent point; linear, piecewise-linear, or exponential segments.
Weight / fall speed — character constants shift the same formula; heavy characters need higher percent to die off top.
DI and momentum — player influence on angle; ring-out reads depend on holding toward stage vs away.
Rage or guts modifiers — if your game has comeback systems, document whether they affect knockback growth near the blast zone.

Tuning workflow: plot kill percent at each blast zone for every character against a reference move (e.g. neutral aerial). Stages with tighter side blast zones should not also use the steepest growth curves unless you want grappler-dominated metas.

Edge pressure, throws and corner carry

Ring-out metas emerge from how offense carries defenders toward boundaries:

Corner push — blockstring sequences with forward momentum on block; pairs with pushback on hurtbox displacement.
Throw ring-out — back throw at ledge is the classic low-damage KO; gate with minimum percent, reduced throw distance at low damage, or a one-per-round cliff throw limit. See grab and throw systems for wall-splat vs ring-out throw variants.
Spike and meteor — downward knockback off ledge; often requires higher percent than horizontal kills.
Wall bounce and splat — wall bounce routes convert center hits into edge situations; cap bounce damage when blast zones are close.
Edge-guard layer — off-stage intercepts; balance recovery tools (double jump, up-special invuln frames) against stage width.

Spectator clarity improves when the HUD shows percent color shift near kill range (e.g. white to red past 80% on small stages) — not hidden engine math.

Harbor Siege cliff stage refactor

Problem diagnosis on the legal cliff variant:

Side blast zones 12% closer than training stage average
Throw back distance constant — no percent scaling on throw KB
Walk-off polygon extended 0.4m past visible rock mesh (collision bug)
No minimum damage on ring-out throws

Changes shipped together:

Pushed side blast zones outward 9% (visual cliff unchanged — kill plane moved)
Aligned walk-off mesh to rendered ledge; added debug gizmo in lab builds
Throw ring-out requires defender at 25%+ OR third throw attempt in round (anti-loop)
Linear knockback growth +8% below 40%, unchanged above (keeps late KOs)
Replay filter tags “ring-out < 20%” for balance review

After 8,600 post-patch ranked games on the same stage:

Ring-out wins under 15% damage: 9% (was 38%)
Average damage at ring-out KO: 47%
Stage dodge rate: 11% (was 31%)
Grappler win rate vs roster mean: +6% (was +22%)
Average round length: +4% (acceptable — more neutral time)

Technique decision table

Your design goal	Prefer	Over
High-stakes edge reads in tournament play	Percent-scaled blast zones + normalized stagelist	Instant walk-off on every competitive map
Prevent throw-only cliff games	Minimum percent gate on throw ring-out	Removing throw KO entirely (kills grappler identity)
Casual-friendly low frustration	Wider blast zones in quick-play queue only	Random ring-out hazards in ranked ruleset
Readable spectator moments	HUD percent tint + slow-mo on final stock	Invisible kill planes with no camera cue
Zoner vs grappler stage fairness	Stage ban in Bo3+ sets; publish blast-zone specs	One cliff stage in all ranked pools
Health-bar-only round clarity	Flat arena variants in training mode	Mixing ring-out and health KO in same round without UI

Common pitfalls

Collision mesh wider than art — invisible walk-off produces clip-driven KOs; sync visual and physics ledges in CI screenshots.
Flat throw distance at all percents — back throw becomes the entire neutral game on small stages; scale throw knockback or gate low-percent cliff throws.
Tight blast zones + steep KB growth — double punishment stacks; tune one lever per patch.
Ignoring DI near ledge — if DI is strong, test survival at kill percent minus 10%; if weak, edge feels inevitable.
Ring-out without recovery tools — defenders need readable up-special or ledge grab; otherwise offense is pure chase.
Netcode desync on KO frame — authoritative position on blast-zone cross; replay must show same KO frame online.
Hazard ring-outs ignoring percent — accidental on legal stagelist; tag hazard stages casual-only.
Wall bounce into instant KO — undamped corner pinball deletes neutral; cap wall hits or widen zones on bounce-heavy stages.

Production checklist

Document blast-zone offsets per stage in data (left/right/top/bottom).
Publish kill-percent table for reference move vs each legal stage.
Define throw ring-out rules: min percent, distance curve, wall-splat variant.
Validate walk-off polygon against rendered mesh in lab build gizmos.
Simulate top 15 edge routes per character at 20%, 50%, 80% defender percent.
Telemetry: ring-out win rate, damage at KO, stage dodge rate, throw KO share.
Tag replays with ring-out damage bucket for balance review filters.
Stage ban policy for ranked Bo3+ documented in match format rules.
Rollback: blast-zone cross is authoritative; test 100ms latency KO frames.
HUD: percent tint or icon when within 15% of typical kill threshold.

Key takeaways

Ring-out makes position a win condition — blast-zone distance and kill percent must be tuned together.
Throw ring-outs need percent gates or scaling on small stages or grapplers dominate.
Walk-off collision must match visible ledges; invisible cliffs destroy trust.
Harbor Siege cut sub-15% ring-out wins from 38% to 9% by widening zones, fixing mesh, and gating throws.
Publish stage geometry specs so tournament bans and balance patches target real levers.