Fix: Godot 3D CharacterBody3D Falling Through Stairs

Here is how to fix Godot 4 CharacterBody3D characters that walk into stairs and refuse to climb. Godot does not include Unity-style Step Offset; you either model stairs as ramps under the hood or write the stepping logic yourself.

The Symptom

Character runs into a flight of stairs. Stops dead at the first step. Walking on flat ground works fine.

What Causes This

No built-in step support. CharacterBody3D treats steps as walls.

Slope angle too steep. An imaginary ramp through stair tops may exceed floor_max_angle.

Capsule shape catches lip. Even with a low slope, the capsule’s lower curve catches.

The Fix

Step 1: Add an invisible ramp collider over stairs. Create a StaticBody3D shaped as a ramp matching the stair slope. Disable the visual stairs’ collision (or set their CollisionShape3D disabled). The character glides up the ramp; players see steps.

Step 2: Or implement step-up logic.

extends CharacterBody3D

const MAX_STEP_HEIGHT := 0.4

func _physics_process(delta):
    # normal movement first
    move_and_slide()

    # detect blocked horizontal motion
    if get_slide_collision_count() > 0:
        var col = get_slide_collision(0)
        if col.get_normal().y < 0.5:   # nearly vertical wall
            try_step_up()

func try_step_up():
    var origin = global_position + Vector3.UP * MAX_STEP_HEIGHT
    var ahead = origin + transform.basis.z * 0.5
    var ray = PhysicsRayQueryParameters3D.create(ahead, ahead - Vector3.UP * MAX_STEP_HEIGHT * 2)
    var hit = get_world_3d().direct_space_state.intersect_ray(ray)
    if hit:
        global_position.y = hit.position.y + 0.01   # snap to step top

Step 3: Tune floor_max_angle.

floor_max_angle = deg_to_rad(50)   # default 45

Higher allows steeper ramps but also makes walls walkable; balance carefully.

Step 4: Use capsule collision shape. Sphere-bottom capsule rolls over stair lips better than a box.

Step 5: For competitive games, prefer ramp colliders. Ramp approach is deterministic and frame-rate independent. Scripted stepping can produce micro-pops between physics steps.

Understanding the issue

Game physics is a contract between authoring (the body, mass, collision shapes you set) and the solver (how the engine integrates them per tick). Bugs at this boundary usually surface as 'the values look right but the behavior is wrong' - a sign that one side of the contract isn't honoring the other.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Godot. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Godot-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Godot, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Ramp under stairs for visual + physics separation. Or step-up raycast for arbitrary geometry. Pick by complexity.”

Related Issues

For 2D ghost collisions, see CharacterBody2D Ghost. For 3D velocity Y, see Velocity Y Zeroed.

Hide a ramp under the stairs. Or raycast and snap. Climbing works.