Quick answer: Axis locks zero physics-driven velocity along the locked axis each step. Direct position or linear_velocity assignment from script bypasses the lock — use apply_central_force or honor the lock manually.

A 3D side-scroller pins the player’s movement to the XY plane by locking the Z axis on the RigidBody3D. The character starts on Z=0, but over time drifts to Z=-3.2. The lock is on; the body still moves.

What Axis Lock Actually Does

For RigidBody3D, axis lock zeroes linear_velocity.z (or other axes) after each physics step. Forces applied along the locked axis still produce zero net motion because the solver clamps velocity each tick.

What it doesn’t do:

Fix 1: Use Forces, Not Direct Velocity

# RIGHT: respects axis lock
body.apply_central_force(Vector3(input_x * 100, 0, 0))

# WRONG: bypasses lock
body.linear_velocity = Vector3(10, 0, 5)   # Z component sneaks through

Forces are integrated through the solver each tick, and the lock clamps the resulting velocity. Direct velocity writes are taken at face value.

Fix 2: Honor Lock Manually

If you must write velocity directly:

var v = Vector3(10, 0, 5)
if body.axis_lock_linear_z: v.z = 0
body.linear_velocity = v

Explicit. Clear. Future you sees the constraint in the code path.

Fix 3: Use _integrate_forces

For complex motion that should respect locks fully:

func _integrate_forces(state: PhysicsDirectBodyState3D):
    var v = state.linear_velocity
    if axis_lock_linear_z: v.z = 0
    state.linear_velocity = v

_integrate_forces runs inside the physics step. The solver applies its own lock after this; combining the explicit zero with the lock guarantees no drift.

Char Controller Special Case

CharacterBody3D doesn’t have axis_lock_* in the same way. Implement manually:

func _physics_process(_delta):
    var v = velocity
    v.z = 0   # 2.5D constraint
    velocity = v
    move_and_slide()

Zero the velocity component each frame. The character can’t accumulate Z motion regardless of input or collisions.

Verifying

Print body.global_position.z over time while applying forces. With proper lock + forces, the value should stay constant (within ~0.0001 floating-point noise). If it drifts, you have a write-site bypassing the lock.

Understanding the issue

The challenge with physics-related bugs is reproducibility. A symptom you see in a 30 fps build may vanish at 60 fps because the integrator's step size changed. Reproducing reliably means controlling both your inputs and the engine's tick rate.

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

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

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

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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.

“Axis locks constrain physics integration. Direct velocity/position assignments aren’t physics integration — they bypass.”

For 2.5D games, prefer CharacterBody3D + manual axis zeroing — cleaner than fighting RigidBody’s direct-write loopholes.