Fix: Godot CollisionShape Disabled Not Re-Enabling

Here is how to fix Godot CollisionShape disabled not re-enabling. You implement an invincibility frame system — disable the hitbox collision shape, wait briefly, re-enable it. You call set_deferred("disabled", true) then later set_deferred("disabled", false). The shape stays disabled permanently. Or it never disables at all. The timing of deferred calls relative to physics steps is the root cause.

The Symptom

A CollisionShape2D or CollisionShape3D that was disabled via set_deferred("disabled", true) does not respond to set_deferred("disabled", false). The shape remains disabled indefinitely. The node’s disabled property reads false in the debugger, but collisions do not register.

Alternative symptom: the shape flickers — it disables and re-enables so fast that it never actually stops detecting collisions, making your invincibility frames useless.

What Causes This

Same-frame disable and enable. If both set_deferred("disabled", true) and set_deferred("disabled", false) are queued in the same physics frame, the physics server may process them both before the next collision check. The net result is no change.

Process mode preventing deferred execution. If the parent node’s process_mode is set to PROCESS_MODE_DISABLED, deferred calls on children do not execute. The call is queued but never processed.

Node freed before deferred call executes. If the node owning the CollisionShape is freed between queueing the deferred call and its execution, the call is silently dropped.

Multiple scripts competing. Two scripts both controlling the same shape’s disabled state. One disables, the other enables on the same frame. The final state is unpredictable.

The Fix

Step 1: Use a timer between disable and enable.

extends CharacterBody2D

@onready var hitbox: CollisionShape2D = $HitboxArea/CollisionShape2D

func take_damage():
    # Disable collision for invincibility frames
    hitbox.set_deferred("disabled", true)

    # Wait for actual time to pass
    await get_tree().create_timer(1.0).timeout

    # Re-enable after the timer
    hitbox.set_deferred("disabled", false)

The await ensures at least one physics frame passes between disable and enable. The physics server has time to process the disabled state before the enable arrives.

Step 2: Use physics_frame signal for frame-precise timing.

func disable_for_frames(frames: int):
    hitbox.set_deferred("disabled", true)

    for i in range(frames):
        await get_tree().physics_frame

    hitbox.set_deferred("disabled", false)

This guarantees the shape is disabled for exactly N physics frames before re-enabling. Each await get_tree().physics_frame yields until the next physics step completes.

Step 3: Verify the node is still valid before re-enabling.

func safe_reenable():
    await get_tree().create_timer(0.5).timeout

    if is_instance_valid(hitbox) and is_inside_tree():
        hitbox.set_deferred("disabled", false)

If the player dies or the scene changes during invincibility, the hitbox node may be freed. Always check validity after an await.

Step 4: Use a single authority for shape state. Avoid multiple scripts toggling the same shape. Centralize control:

var _invincible: bool = false

func set_invincible(value: bool):
    _invincible = value
    hitbox.set_deferred("disabled", value)

func take_damage():
    if _invincible:
        return
    set_invincible(true)
    await get_tree().create_timer(1.0).timeout
    set_invincible(false)

When set_deferred Is Not Needed

You only need set_deferred when changing collision shapes during physics callbacks (_physics_process, body_entered, area_entered). Outside these contexts, direct assignment is safe:

# Safe in _process, _input, or custom functions not called from physics
func _input(event):
    if event.is_action_pressed("toggle_shield"):
        hitbox.disabled = !hitbox.disabled  # Direct is fine here

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

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

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

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

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.

“Deferred calls queue for end-of-frame. Two deferred calls in one frame both execute before the next physics step sees either. Add real time between them.”

Related Issues

For physics material problems on the same shapes, see PhysicsMaterial Bounce Not Working. For character body physics, see CharacterBody2D Floor Snap.

Timer between disable and enable. Check validity after await. One script owns the shape state.