Guide

Game wall-run traversal systems explained

Harbor Rooftop's signature gap was a twelve-meter jump between two warehouse roofs — reachable only if players sprinted, jumped at the lip, and prayed. Completion sat at 41%. Designers widened the ledge, added coyote time, and still saw players slam into the far wall and fall. The fix was not a bigger jump buffer; it was a wall-run strip on the takeoff face: sprint into the wall, stick for 1.8 seconds of lateral speed, then jump off the end with preserved momentum onto the far roof. Completion rose to 89%, and speedrunners found a corner-transfer chain that cut ten seconds off the platinum route. Wall-running is not sliding on geometry — it is a timed movement state that trades downward pull for horizontal velocity until stamina, angle, or surface length says stop.

Wall-run systems appear in Mirror's Edge-style runners, Titanfall combat mobility, Assassin's Creed facade climbs, and open-world parkour verb stacks. They share surface validation, an attach finite-state machine (FSM), gravity compensation, and exit rules that feed the next verb — jump, mantle, slide, or another wall. This guide covers eligibility probes, speed and stamina curves, inside vs outside corners, camera and animation hooks, level authoring, the Harbor Rooftop refactor, a technique decision table vs grapple hooks and pure locomotion, pitfalls, and a production checklist.

What wall-run systems are

A wall-run system lets the player character temporarily adhere to a vertical or near-vertical surface while moving primarily along the wall plane. Core responsibilities:

Eligibility — decide which geometry counts as runnable (angle, material tag, minimum length, player speed gate).
Attach — snap or blend the character onto the wall plane with correct facing and initial lateral velocity.
Sustain — apply reduced gravity, speed caps, and optional stamina drain for the run duration.
Transfer — handle 90-degree corners, wall-to-wall hops, and ceiling transitions without popping the player off.
Exit — detach with jump impulse, fall, mantle assist, or chain into the next traversal verb.

Unlike always-on “sticky walls,” production wall-runs are gated verbs: the player must meet entry conditions, and the system must communicate remaining runway (stamina bar, footstep audio, camera tilt) before the run ends.

Surface detection and eligibility rules

Most failures trace to fuzzy eligibility. Ship explicit rules, not accidental mesh collisions:

Check	Typical rule	Why it matters
Surface normal	Wall angle 75°–100° from up (near-vertical)	Shallow ramps feel like ice; overhangs need climb, not run
Runnable tag	Layer or material: `RunnableWall`	Prevents brick vs glass vs enemy-body confusion
Approach speed	Min horizontal speed ~4–6 m/s at contact	Walking into a wall should slide, not stick
Clearance	0.4–0.6 m free space along wall plane	Protruding pipes cause instant detach and rage
Minimum length	≥ 2 m continuous runnable span	Teaches players not to waste the verb on slivers
Entry height	Feet between 0.5 m and 4 m off ground (genre-tuned)	Blocks silly ground-scrape runs on curbs

Use a short forward-and-down ray or capsule sweep from the shoulder at jump apex: if the hit normal qualifies and speed exceeds threshold, queue attach on the next frame. Debounce one-frame false positives on triangle seams.

Attach FSM and gravity compensation

Treat wall-run as its own locomotion mode with clean enter/update/exit:

Approach — airborne or sprinting toward wall; probes armed.
Attach blend — 80–150 ms snap: align body yaw to wall tangent, zero velocity into the wall, inherit tangent speed.
Run sustain — apply custom gravity (often 10–25% of world g along the wall normal), accelerate laterally to cap, play run cycle.
Warn — last 0.3 s: audio tick, camera roll, stamina flash when runway or meter ends.
Exit — jump (add outward + up impulse), fall, corner transfer, or forced detach on obstacle.

Gravity curve: constant low-g feels floaty; many games ramp downward pull over time so skilled players release early for distance jumps and novices get a forgiving first second. Titanfall-style combat runs use shorter windows (0.8–1.2 s) with higher lateral caps; exploration runners allow 2–3 s with gentler acceleration.

Pair with input buffering: if the player presses jump 100 ms before detach, honor it on exit for buttery chains.

Speed, stamina and chaining exits

Wall-run feel lives in the trade-off between how fast and how long:

Lateral speed cap — often 1.2–1.5× sprint speed; higher in pure runners, lower when wall-run is one verb among combat.
Stamina meter — drains per second on wall; regens on ground. Empty meter forces detach. Shows players the resource explicitly.
Distance limit — hard cap per attach regardless of stamina; prevents infinite loops on circular silos unless designed.
Exit jump bonus — release within 0.2 s of optimal point adds 10–15% horizontal carry; rewards reading wall length.
Chain rules — wall-run → jump → opposite wall-run within 0.5 s may skip speed gate on second attach (Mirror's Edge rhythm).

Document whether wall-run preserves momentum into dodge rolls or slides — ambiguous transitions are where speedrun tech and casual frustration diverge.

Corner transfers and wall-to-wall hops

Corners separate polished traversal from wall-hugging glue:

Outside corner — player wraps around convex edge; rotate tangent 90° over 6–10 frames while maintaining speed magnitude. Probe the new face before completing rotation.
Inside corner — concave 90°; often impossible without a small air gap. Either block with “non-runnable” trim or allow a auto-hop that spends stamina.
Wall-to-wall — parallel walls 3–5 m apart: zigzag runs with jump between faces. Author with symmetric runnable tags and mid-air attach forgiveness.
Wall-to-ceiling — rare; usually transitions to climb or vault. If supported, cap speed and switch animation root early.

Debug-draw tangent arrows on runnable meshes in editor; designers should see run direction without play mode.

Camera, animation and feedback

Players read wall-run readiness from presentation, not tooltip text:

Camera — slight roll into the wall (3°–8°), FOV bump +5° on attach, ease back on exit. First-person games may reduce roll and lean the view model instead.
Animation — three-beat foot cycle synced to lateral speed; blend upper body for aim in shooters. Root motion optional; many teams drive feet in code for predictable jump-off points.
VFX/SFX — dust streaks on brick, metal scrape on steel; pitch rises as stamina drains. Silence before detach is a classic bug.
UI — stamina pip or wall-run icon only while attached; hide on ground to reduce HUD noise.

Level authoring for readable wall-run lines

Geometry teaches the verb:

Paint runnable strips with contrasting trim players learn once, then read at speed.
Entry walls face the approach vector; avoid diagonal approaches that fail normal checks unless you widen forgiveness.
Place exit targets (ledges, beams) at 70–85% of max run distance so optimal jumps feel earned, not pixel-perfect.
First tutorial wall: long, flat, one exit jump to safe ground — no corners until attach success rate exceeds 80% in telemetry.
Gate advanced chains behind optional collectibles, not mandatory story beats.

Case study: Harbor Rooftop Run refactor

The warehouse gap shipped with a single runnable face on the takeoff wall:

Before — precision jump only; 41% completion; average six deaths per player in playtests.
Probe fix — seam at the wall lip failed attach 22% of the time; merged collision and added 0.15 s attach coyote after airborne contact.
Speed gate lowered — min speed from 6.2 to 5.0 m/s so sprint-jump entries qualified without frame-perfect timing.
Exit assist — jump-off added 12% horizontal carry toward nearest LedgeGrab volume on the far roof.
Platinum route — optional outside-corner transfer on the far wall added for speedrun layer; casual route ignores it.

Completion hit 89%; median deaths dropped to 0.4 per player. Telemetry showed 63% of successful crossings used wall-run, proving the verb carried the encounter instead of hiding bad jump tuning.

Technique decision table

Technique	Best for	Strength	Weakness
Wall-run	Gap crosses along parallel walls, rooftop lines	Readable flow, skill expression on release timing	Needs authored runnable surfaces; fails on organic terrain
Mantle / vault	Vertical ledges within 1–2 m height bands	Forgiving near-miss recovery	Not for horizontal speed; no momentum fantasy
Grapple hook	Large gaps, swing arcs, vertical pull	Spans arbitrary anchor distances	Aim friction; harder to network
Double jump	Simple platformers, low authoring cost	Universal, no surface tags	Flat feel; hard to gate difficulty
Zipline	Fixed downhill lines, one-way beats	Predictable pacing, cinematic	Rail-like; low player routing agency
Air dash	Combat mobility, dodge extensions	Omni-directional correction	Breaks realism; overlaps with dodge i-frames

Common pitfalls

Sticky every vertical face — players cling to enemies, crates, and doorframes; tag explicitly.
No speed gate — walking into walls attaches and looks broken; require sprint or airborne entry.
Instant detach on triangle seams — mesh cracks drop players mid-run; merge collision or grace 2–3 frames without valid wall.
Flat gravity on infinite runs — circular arenas become infinite loops; use distance or stamina caps.
Exit jump with no outward impulse — players slap back into the wall; add normal-component boost.
Camera fight on inside corners — nausea and disorientation; block or auto-hop with telegraph.
Networking raw transform snap — remote avatars slide; replicate attach state + phase, not just position.
Mandatory precision chains in story — accessibility and churn; always offer a slower ground route.

Production checklist

Define runnable material/layer tags and document angle limits in design wiki.
Implement attach probe with speed gate, clearance sweep, and seam debounce.
Build wall-run FSM: attach blend, sustain gravity curve, warn, exit branches.
Tune lateral cap, stamina drain, and max distance per genre target.
Buffer jump input on exit; verify carry into mantle and second-wall attach.
Author outside-corner transfer with new-face validation before rotation completes.
Hook camera roll, FOV, footstep VFX, and stamina UI to attach/detach events.
Place tutorial wall with telemetry on attach success and detach reason codes.
Playtest with gamepad and KB+M; confirm sprint entry is achievable on both.
Log detach reasons (stamina, distance, bad angle, obstacle) for tuning sprints.

Key takeaways

Wall-running is a gated locomotion verb, not default friction on vertical geometry.
Eligibility probes (angle, tag, speed, length) determine success more than jump tuning.
Gravity ramps, stamina meters, and exit jump bonuses create readable skill ceilings.
Corner transfers and wall-to-wall hops need explicit rotation and validation logic.
Harbor Rooftop turned a 41% precision jump into an 89% flow route by authoring one runnable face and fixing seam attaches.