Game corner carry systems explained

What corner carry adds beyond midscreen damage

Midscreen pressure trades health for advantage. Corner carry trades position for a multiplied payoff: reduced escape vectors, tighter okizeme, deadlier throw loops, and higher scaling on wall interactions. Without deliberate carry design, rushdown characters become damage dealers who never access their strongest tools.

Four properties distinguish carry systems from incidental pushback:

• Carry budget — each string or route documents how many stage units it moves the defender toward the nearest wall.
• Proximity scaling — pushback or knockback increases as the defender nears the boundary, preventing “almost corner” dead zones.
• Route orthogonality — multiple carry paths (block push, launch knockback, side-switch, throw reposition) so defenders cannot solve carry with one escape habit.
• Trap conversion gate — carry strings end in a documented knockdown distance or plus frame that enables corner traps, not just closer spacing.

Carry is the offensive half of corner design; escape tools are the defensive half. Tune them together or matches swing between unstoppable traps and meaningless midscreen wins.

Carry mechanics taxonomy

Pushback on block and hit

The workhorse carry tool: each blocked or hit frame advances the defender along the X axis. Designers track push_per_hit and blockstun_push_multiplier separately — block push often carries more because the defender cannot counter-hit out. Document cumulative push per string, not per move in isolation.

Knockback velocity vectors

Launchers, sweeps, and wall-splat moves apply horizontal velocity toward the nearest stage edge. Vector carry is burstier than block push: one good launcher can skip three hits of string push. Pair with hurtbox displacement so juggle drift does not accidentally carry midscreen.

Side-switch and crossup carry

Crossups that end with the defender's back to the wall carry regardless of approach direction. Side-switch carries are essential when the attacker approached from the wrong side — without them, winning neutral on the “open” side feels wasted.

Throw and command grab repositioning

Throws teleport spacing: tick throw into corner, command grab with forward knockdown at wall. Grab carry bypasses block entirely but costs startup risk. Document throw knockdown distance to wall in pixels, not “corner throw.”

Stage walk and micro-adjustment

Between string gaps, the attacker walks forward to maintain throw range while the defender is pushed. Walk speed during plus frames is a hidden carry stat: a +2 string with fast forward walk carries more than +4 with slow walk.

Carry math and design knobs

Treat stage width as a resource bar. Midscreen center to corner might be 800 units; a standard rushdown route should carry 200–280 units per neutral win without meter.

• corner_push_per_hit — base units moved per contact frame.
• wall_proximity_multiplier — scales push from 1.0 at center to 1.4–1.8 within 120 units of wall; eliminates three-pixel dead zones.
• carry_budget_per_string — cap total push per blockstring before forced reset or scaling decay; prevents infinite corner inching.
• knockback_wall_bias — fraction of horizontal velocity aimed at nearest boundary on launch moves.
• carry_decay_on_escape — if defender backdashes out, how much carry progress resets (full, half, or none).

Build a spreadsheet: character, string ID, hits to corner from center, meter cost, knockdown type at wall. If two characters reach corner in the same hits but one spends meter, the meterless character needs weaker corner payoff or slower carry — otherwise roster feels uneven before anyone tests damage.

Effective corner spacing

“In the corner” is not binary. Define tiers:

Carry strings should target deep corner or flush wall on knockdown, not approach corner — approach tier is where Harbor Brawl's three-pixel frustration lived.

Carry routes and string design

Midscreen-to-corner paths

Standard route: neutral poke confirm into blockstring (120 units push) into special cancel forward knockdown (180 units knockback) = flush wall. Alternate route: jump-in overhead (80 units) into low string (100 units) into throw (reposition). Routes should differ in risk and meter so players choose based on reads, not one optimal carry line.

Wall-splat and bounce carry

Wall-splat sticks the defender; the attacker walks forward for free during splat frames, then detonates into bounce or extended combo. Splat carry is high reward but character-specific — document which moves trigger splat and whether carry continues after splat ends.

Drive rush and gap-closer carry

Drive rush and dash cancels close distance without pushback on the defender — they are carry accelerators, not carry themselves. Cap drive-rush carry extensions per round or opponents feel snapped to the wall from fullscreen.

Reset without losing carry progress

Plus-on-block string enders that do not knock down should not push the defender out of corner. Audit minus-to-plus frame traps at the wall: a +2 standing medium that pushes backward on block is a carry bug at flush spacing.

Integration with pressure and stage systems

Corner carry sits between several systems:

• Blockstring pressure — carry-per-hit on blocked normals is the primary inching tool; see plus-on-block tables in frame advantage docs.
• Rushdown archetypes — gap closers get the attacker into carry range; carry strings finish the job.
• Wall bounce and break — carry sets up splat; splat sets up break meter or extended juggle; break resets to midscreen as escape valve.
• Anti-air and air-to-air — launching an opponent from midscreen toward the wall they are facing is a carry route; wrong-side launch carries the wrong direction.

Telemetry tag carry events separately from damage events. Designers need “neutral win to deep corner within N seconds” not just combo damage histograms.

Harbor Brawl carry refactor

Harbor Brawl's carry pass targeted the three-pixel dead zone without buffing damage.

1. Pushback table rebuild — 47 normals retuned; average push_per_hit on block +18% within 150 units of wall.
2. Wall proximity multiplier — linear 1.0–1.6 scale from center to 100 units; eliminated approach-corner dead zone.
3. Carry budget caps — blockstrings capped at 320 units total push before forced knockdown or minus reset; stops infinite inching.
4. Route documentation — each character gained two documented meterless carry lines in the movelist with unit totals.
5. Training overlay — shows carry progress bar and tier (midscreen / approach / deep / flush) during blockstring practice.

Results after five weeks: neutral-win-to-corner-trap 22% to 38%; average damage per corner sequence +31%; “can't keep people in corner” tickets −64%; backdash escape rate from approach tier 41% to 19%. No character exceeded target corner time without a documented counter-route in playtests.

Technique decision table

Common pitfalls

• Pushback without carry budget — infinite corner inching on safe strings; cap push per string or round.
• Approach-corner dead zone — defender can backdash between throw and reversal ranges; use proximity multiplier.
• Minus string pushback at wall — block push that moves defender out of corner on gap; audit minus endpoints at flush spacing.
• Carry without trap payoff — reaching corner but knockdown minus on wakeup wastes the route; pair carry with oki tiers.
• Ignoring wrong-side wins — no side-switch route makes half of neutral wins feel empty.
• Flat pushback all stage — same pixels midscreen and at wall; proximity scaling fixes most “almost there” frustration.
• Conflating carry with damage scaling — corner damage bonuses are separate knobs; carry is position, not DPS.

Production checklist

• Define corner distance tiers (midscreen, approach, deep, flush) in design wiki.
• Add push_per_hit, block_push, and knockback_wall_bias to movelist schema.
• Build carry spreadsheet: string ID, units moved, hits from center, meter cost.
• Implement wall_proximity_multiplier on pushback resolver.
• Cap carry_budget_per_string with telemetry on cap hits.
• Document two meterless carry routes per rushdown character.
• Audit minus-on-block push at flush wall for all strings.
• Tag carry events in combat telemetry (tier reached, time from neutral win).
• Training mode: carry progress bar and tier overlay during blockstring practice.
• Playtest neutral-win-to-flush-wall rate weekly; target 30–45% for rushdown archetypes.

Key takeaways

• Corner carry is spatial routing, not raw damage — document carry budgets per string.
• Proximity multipliers eliminate approach-corner dead zones where backdash escapes.
• Pushback on block, knockback vectors, side-switch, and throws are orthogonal carry tools.
• Harbor Brawl raised neutral-win-to-corner-trap from 22% to 38% with pushback tables, not damage buffs.
• Carry and corner escape must be tuned as a pair — carry without trap payoff wastes player wins.
• Telemetry carry tier separately from combo damage to see if neutral wins convert to position.

Related reading

• Game corner escape and pressure systems explained — trap layers, reversals and defender routes at the wall
• Game blockstring pressure systems explained — plus frames, gaps and reset points that inch toward corner
• Game pushback and hurtbox displacement systems explained — spacing geometry and knockback vectors
• Game wall bounce systems explained — splat, bounce and wall break after carry lands