Guide

Game knockback systems explained

Harbor Ruins' second boss arena sits on a narrow stone bridge above a kill plane. Playtest telemetry showed a spike in abandonments at 38% boss health: every overhead slam launched players backward off the edge with no recovery option. The combat team did not shrink the arena. They rebuilt knockback as a layered system — poise-gated launches, ledge-guard friction, and attack-specific displacement curves — so heavy hits still felt brutal without turning positioning into pure frustration. Boss clear rate rose 22% with no damage nerf. Knockback is how hits move bodies: a shove on the ground, a launch into the air, a slide into a wall, or a bounce that opens a juggle. It is one of the fastest ways combat communicates weight, threat, and mastery. Done poorly, knockback feels random, unfair, or exploitable in PvP. This guide covers impulse models, stagger versus launch, poise and weight classes, wall interactions, juggle limits, networking, the Harbor refactor, a genre decision table, pitfalls, and a practitioner checklist alongside our melee combat guide, health and damage systems guide, and game physics overview.

What knockback is (and what it is not)

Knockback is displacement caused by a hit, separate from damage numbers. A light jab might deal 8 damage and push a target 0.3 meters; a charged uppercut might deal 40 damage and launch them 2 meters vertically. Players read knockback before they read HP bars: it tells them whether they can recover, whether a combo is possible, and whether the next hit will kill by ring-out.

Knockback is not the same as hitstun (the window where input is locked) or hitstop (the brief freeze on impact). All three stack: hitstop sells contact, hitstun prevents immediate counterplay, knockback changes spatial state. See our hitstop guide for freeze-frame tuning; this guide focuses on where the body goes after contact.

Some games fake knockback with root motion on animations; others drive it with physics impulses on a capsule or rigidbody. Both are valid. The design question is whether displacement is deterministic and readable every time the same attack lands under the same conditions.

Impulse models: how engines apply force

Under the hood, knockback usually resolves through one of these patterns:

Velocity override: on hit, set horizontal and vertical velocity to fixed values derived from the attack data table. Predictable, fighting-game friendly, easy to netcode.
Impulse add: add a force vector to current velocity. Preserves momentum from movement and other hits; common in platform fighters and brawlers.
Position snap / kinematic tween: move the target along a curve over N frames regardless of physics. Soulslike bosses often use this for guaranteed spacing on grab attacks.
Ragdoll blend: switch to physics on heavy hits, then blend back to animation. High spectacle, harder to balance and sync online.

Harbor Ruins standardized on velocity override with additive falloff: each attack defines base knockback (kx, ky), a poise damage value, and a launch flag. If the defender's poise breaks, apply full values; otherwise apply 35% horizontal shove only. That single rule fixed the bridge boss without touching arena geometry.

Stagger, launch, and juggle tiers

Designers usually bucket knockback into tiers so players learn a vocabulary:

Flinch / micro-stagger: tiny displacement, animation interrupt only. Pistols, quick slashes.
Stagger / knockdown: target enters a grounded or crumple state. Opens okizeme (pressure on wakeup) in fighters.
Launch: target becomes airborne; gravity and air control rules apply. Opens juggles in action games and platform fighters.
Blowback / ring-out: extreme horizontal displacement aimed at stage edges or hazards. Common in arena brawlers; must be telegraphed.

Each tier needs paired recovery options: ukemi, air dodge, tech roll, burst, or super armor. Without escape valves, launch-heavy enemies feel oppressive. Without consequences, light attacks feel mushy. Tune tier thresholds against stamina and poise pools so resource management gates displacement, not hidden RNG.

Poise, weight classes, and knockback scaling

Poise (sometimes hyper armor or super armor) is a hidden or visible meter that absorbs hit flinch before full knockback applies. A boss at 80% poise might barely budge on light hits but stagger on a charged heavy. Player builds that stack poise trade mobility for stability — a classic RPG tank fantasy.

Weight classes multiply incoming knockback: a “heavy” character might take 0.7× launch distance but move slower; a “light” character takes 1.3× but recovers faster. Fighting games expose weight in character select; action RPGs hide it behind armor stats. Either way, document multipliers in a central table so a balance pass does not require hunting scattered constants.

Direction matters: knockback along the attack vector reads as physical cause; knockback always away from attacker center is easier to read in top-down games. Diagonal launches need consistent elevation angles or players misjudge air dodge timing.

Wall bounce, ground bounce, and chain displacement

Wall bounce reflects velocity when a launched body hits geometry, often with a damage multiplier and extended hitstun. It extends combos and sells arena tension. Cap chain bounces: infinite wall loops in PvP breed degenerate strategies and desync in lag.

Ground bounce ( OTG — off the ground) pops a downed enemy back into the air for juggle continuation. Fighting games gate OTG behind meter or character-specific moves. Action games use it sparingly on elite enemies to avoid infinite lock.

Juggle decay: each successive launch applies a dampening factor (e.g. 0.92× per hit) until the target reaches a terminal float state and falls out. Decay prevents 100-hit infinites while still rewarding skilled strings. Log juggle count per combo in telemetry to find broken loops early.

Multiplayer validation and feel

Authoritative server models should own knockback resolution: client predicts displacement for responsiveness, server sends correction if delta exceeds threshold. Large launches are where rollback fighters and action RPGs diverge — a 200 ms correction on a ring-out feels like theft.

Snap thresholds: if server position differs from client by more than half a body width after knockback, interpolate over 2–4 frames rather than teleporting. Log knockback events with attack ID, poise state, and surface normal for dispute debugging. Our netcode guide covers rollback versus delay-based sync; knockback is one of the first systems to stress-test either model.

Pair knockback with combat text and camera shake at tier boundaries so online spectators read impact severity even when particles are culled.

Accessibility and difficulty knobs

Not every player can react to rapid launch chains. Offer options that preserve challenge without removing weight:

Reduced launch distance (slider 50–100%) — keeps hitstun timing intact.
Ledge guard / infinite ledge in story mode — prevents environmental kills while keeping boss knockback scary on the floor.
Auto-recovery burst on repeated juggles — one free air escape per combo for assist modes.
Color-coded knockback tier on enemy windups — helps cognitive accessibility without slowing combat.

Competitive modes should disable or normalize these assists. Document which flags affect knockback in your difficulty preset matrix so QA can regression-test each combination.

Harbor Ruins refactor (worked example)

Before the refactor, knockback was a single formula: force = damage × 0.15 along hit normal. Heavy attacks on the bridge boss one-shot players off the stage because damage scaled with enrage phase but force scaled with it too.

The fix shipped in four parts:

Attack-authored knockback: every move lists fixed kb_x, kb_y, tier independent of damage roll crits.
Poise gate on launches: launch tier only applies when poise ≤ 0; otherwise downgrade to stagger tier.
Ledge friction zone: within 1.5 m of kill-plane edges, horizontal knockback multiplied by 0.4 for players (not enemies).
Telemetry overlay: heatmap of death positions per attack ID validated tuning in one sprint.

Enrage phase now increases attack speed and poise damage, not raw launch distance — pressure rises without unfair ring-outs.

Genre decision table

Genre	Knockback role	Typical model	Watch for
Fighting game	Combo routing, stage control	Fixed velocity, hurtbox pushback	Corner carry infinites, inconsistent pushback on trade
Platform fighter	Ring-out win condition	Impulse add + blast zones	Early kills at low %, DI degeneracy
Soulslike / action RPG	Threat readability, stamina wars	Poise + animation root	Camera obscuring launch direction
Beat-em-up	Juggle spectacle, crowd control	Launch + juggle decay	Infinite juggle on large enemies
Twin-stick shooter	Minimal displacement	Micro-flinch only	Knockback into bullet patterns feels cheap
MOBA / ARPG	Skill expression, peel	Skill-authored vectors	CC chain duration versus tenacity stats

Common pitfalls

Scaling knockback with damage: crits and buffs accidentally double displacement; players die to geometry instead of HP.
No poise on heavies: every tap launches; light attacks become useless.
Ignoring slope normals: knockback along flat X on a ramp sends bodies underground or into orbit.
Unbounded wall bounce: PvP degeneracy and netcode correction spikes.
Mismatched hitstun and travel time: target recovers mid-air before landing, breaking combo logic.
Enemy-only knockback immunity: players feel inputs do nothing on bosses without visible armor feedback.
Ragdoll without recovery state: characters flop until manual reset; softlocks in single-player.

Practitioner checklist

Central knockback table: attack ID, tier, kb_x, kb_y, poise damage, launch flag.
Weight / armor multipliers documented per character class.
Poise regen rate and break VFX readable in combat.
Juggle decay and wall-bounce caps defined per game mode.
Ledge / hazard policy for story versus ranked play.
Hitstun durations match displacement time to landing.
Server authoritative resolution with client prediction tests under 150 ms RTT.
Death heatmaps per attack ID on stages with kill planes.
Accessibility sliders wired to knockback distance, not hidden.
Regression replays: same seed produces identical knockback vectors.

Key takeaways

Knockback communicates weight and threat faster than damage numbers; tune it as its own system, not a damage side effect.
Tier knockback (flinch, stagger, launch, blowback) and pair each tier with recovery options.
Poise and weight classes gate displacement so light hits and heavy hits occupy distinct roles.
Wall bounce and juggle decay need hard caps to keep PvP and netcode stable.
Harbor-style fixes separate launch distance from enrage damage scaling and add ledge friction instead of shrinking arenas.