Quick answer: Increase floor_snap_length to 4–8 pixels, raise the safe_margin to 0.08, and cap your fall velocity so the character cannot travel farther than the collision margin in a single physics frame.

You build a platformer in Godot 4. One-way platforms work when you walk onto them from the side, but when the character falls from above, they pass straight through like the platform is not there. The collision shape is correct, one-way is enabled, and it works at low speeds. The problem is that at high fall velocities, the physics solver steps over the platform entirely.

Why It Happens

Godot’s physics runs at a fixed tick rate (default 60 Hz). Each tick, the CharacterBody2D moves by velocity * delta. If the character is falling at 800 px/s and delta is 0.0167s, the character moves 13.3 pixels per tick. A one-way platform with a 2-pixel collision margin can be completely skipped — the character was above it on one tick and below it on the next.

This is the classic “tunneling” problem, made worse by one-way collisions because the solver only blocks motion from one direction. From below, the platform is invisible, so once the character overshoots, it stays below.

The Fix

Step 1: Increase floor_snap_length.

extends CharacterBody2D

func _ready():
    floor_snap_length = 8.0  # default is 1.0, too small for fast falls
    safe_margin = 0.08       # default is 0.001

floor_snap_length controls how far down the character will “snap” to maintain floor contact after move_and_slide. A value of 1 means the character loses contact after a 1-pixel gap. Bumps, slopes, and fast falls all create gaps larger than 1 pixel. Set it to 4–8 for reliable platform behavior.

Step 2: Cap fall velocity.

const MAX_FALL_SPEED = 600.0
const GRAVITY = 980.0

func _physics_process(delta):
    if not is_on_floor():
        velocity.y += GRAVITY * delta
        velocity.y = min(velocity.y, MAX_FALL_SPEED)

    move_and_slide()

At 60 Hz physics, a MAX_FALL_SPEED of 600 means the character moves 10 pixels per tick. With a safe_margin of 0.08 and a platform collision shape of at least 4 pixels tall, the solver will always catch it. Without the cap, gravity accelerates the character past any reasonable margin.

Step 3: Make the platform collision shape thick enough.

A one-way platform with a 1-pixel-tall RectangleShape2D is almost impossible to land on at speed. Make the collision shape at least 4–8 pixels tall, even if the visual sprite is a thin line. The visual and physical shapes do not need to match exactly.

Dropping Through One-Way Platforms

The reverse problem: letting the player press Down to fall through. The cleanest approach is to temporarily disable the platform’s collision:

func _physics_process(delta):
    if Input.is_action_just_pressed("move_down") and is_on_floor():
        # Find the platform we are standing on
        for i in get_slide_collision_count():
            var col = get_slide_collision(i)
            var collider = col.get_collider()
            if collider.is_in_group("one_way_platform"):
                collider.get_node("CollisionShape2D").disabled = true
                get_tree().create_timer(0.2).timeout.connect(
                    func(): collider.get_node("CollisionShape2D").disabled = false
                )
                position.y += 1  # nudge through the one-way threshold
                break

The 0.2s timer gives the character time to clear the platform before the collision re-enables. Adjust the duration based on your character’s fall speed.

Verifying the Fix

Build a test scene with platforms at varying heights: 100px, 200px, 400px, and 800px above the character. Drop the character from each height and confirm it lands on the platform every time. If it falls through from the highest drop, your MAX_FALL_SPEED is still too high for your collision margin.

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

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

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

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

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

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.

“One-way platforms are the most fragile collision type in any engine. They work at low speeds and break at high speeds. Cap your velocity, thicken the collision, and increase the snap length — the three-part fix is mechanical.”

Related Issues

For CharacterBody2D snapping issues on regular ground, see Godot CharacterBody2D snapping ground after jumping. For wall-jump collision bugs, see Godot CharacterBody2D wall jump not working.

Always cap fall velocity. Unlimited gravity acceleration will eventually break any collision system, not just one-way platforms.