Fix: CharacterBody2D Wall Jump Not Working in Godot

Wall jumping is a staple mechanic in 2D platformers, but getting it to work reliably with Godot’s CharacterBody2D is surprisingly tricky. The most common issue is that is_on_wall() returns false even when the player visually touches a wall, or the jump fires but sends the character in the wrong direction. Here’s how to fix it.

Why is_on_wall() Is Unreliable for Wall Jumps

The is_on_wall() method only returns true after move_and_slide() has processed a collision with a surface whose angle exceeds floor_max_angle. This means two things must be true simultaneously: the character must be moving into the wall, and the collision normal must be steep enough to qualify as a “wall” rather than a slope.

In practice, this breaks wall jumping in several ways. If the player releases the horizontal movement key before pressing jump, is_on_wall() returns false because there’s no collision happening. If the wall has even a slight angle (common with hand-drawn or tile-based levels), it might register as a slope instead. And if the character is falling too fast, the collision may be classified differently based on the velocity vector.

The fix is to stop relying on is_on_wall() and use dedicated raycasts instead.

Setting Up Raycast-Based Wall Detection

Add two RayCast2D nodes as children of your CharacterBody2D. One points left, one points right. Set their target_position to extend just past the edge of your collision shape — typically 2–4 pixels beyond the character’s width.

# Scene tree:
# CharacterBody2D
#   CollisionShape2D
#   RayCast2D (WallCheckLeft)  - target_position = Vector2(-12, 0)
#   RayCast2D (WallCheckRight) - target_position = Vector2(12, 0)

@onready var wall_check_left: RayCast2D = $WallCheckLeft
@onready var wall_check_right: RayCast2D = $WallCheckRight

func is_touching_wall() -> bool:
    return wall_check_left.is_colliding() or wall_check_right.is_colliding()

func get_wall_normal() -> Vector2:
    if wall_check_left.is_colliding():
        return wall_check_left.get_collision_normal()
    if wall_check_right.is_colliding():
        return wall_check_right.get_collision_normal()
    return Vector2.ZERO

Make sure both raycasts are enabled and set to collide with your wall collision layer. If your walls are on a different layer than your floors, configure the raycast’s collision_mask accordingly.

Implementing the Wall Jump

With reliable wall detection in place, the wall jump itself is straightforward. When the player presses jump while touching a wall and not on the floor, apply both vertical and horizontal velocity:

const WALL_JUMP_VELOCITY_Y: float = -300.0
const WALL_JUMP_VELOCITY_X: float = 200.0
const WALL_JUMP_INPUT_LOCKOUT: float = 0.15

var input_locked: bool = false
var input_lock_timer: float = 0.0
var last_wall_normal: Vector2 = Vector2.ZERO

func _physics_process(delta: float) -> void:
    # Handle input lockout timer
    if input_locked:
        input_lock_timer -= delta
        if input_lock_timer <= 0.0:
            input_locked = false

    # Apply gravity
    if not is_on_floor():
        velocity.y += gravity * delta

    # Ground jump
    if is_on_floor() and Input.is_action_just_pressed("jump"):
        velocity.y = JUMP_VELOCITY
        last_wall_normal = Vector2.ZERO

    # Wall jump
    elif not is_on_floor() and is_touching_wall() and Input.is_action_just_pressed("jump"):
        var wall_normal = get_wall_normal()
        if wall_normal != last_wall_normal:
            velocity.y = WALL_JUMP_VELOCITY_Y
            velocity.x = wall_normal.x * WALL_JUMP_VELOCITY_X
            last_wall_normal = wall_normal
            input_locked = true
            input_lock_timer = WALL_JUMP_INPUT_LOCKOUT

    # Horizontal movement (skip if input locked)
    if not input_locked:
        var direction = Input.get_axis("move_left", "move_right")
        velocity.x = direction * SPEED

    move_and_slide()

The input_lock_timer is crucial. Without it, the player can hold the opposite direction and immediately cancel the horizontal push from the wall jump, making the character slide straight up the wall. A lockout of 100–200 milliseconds feels responsive without being sluggish.

Preventing Infinite Wall Climbing

Without a check, players can repeatedly jump off the same wall to climb infinitely. The last_wall_normal variable prevents this — it stores the normal from the most recent wall jump and blocks another jump in the same direction until the player either lands on the floor (which resets it to Vector2.ZERO) or touches a wall on the opposite side.

Reset the tracking when the player lands:

if is_on_floor():
    last_wall_normal = Vector2.ZERO

If you want to allow multiple jumps on the same wall (like climbing a shaft by alternating between two walls), you can skip the normal check entirely and instead limit wall jumps with a counter or a short cooldown timer. The right approach depends on your game’s design — Celeste-style wall climbing is very different from Mega Man X-style wall jumps.

Test your wall jump with different wall materials, angles, and character speeds. Edge cases like jumping at the top edge of a wall, hitting a corner where two walls meet, or wall-jumping during a wall slide all need specific attention. Build a test level with various wall configurations and iterate until every case feels right.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Godot Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

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

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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.

Wall jumps are 90% about feel — get the physics right, then tweak the numbers until it’s fun.