Fix: Godot GDScript Await Blocking Physics Tick

An enemy is supposed to telegraph its attack with a half-second windup, then strike. The first version of the code looked clean — await get_tree().create_timer(0.5).timeout in the middle of _physics_process. The result on screen: the enemy stutters, attacks fire twice, the player’s collision response feels laggy, and the physics step occasionally skips a frame entirely.

What Await Does to a Per-Tick Callback

When GDScript encounters await, it transforms the surrounding function into a coroutine. Execution suspends at the await; control returns to the engine; the engine resumes the coroutine when the awaited signal fires.

For _physics_process, this is catastrophic:

1. Tick 1: _physics_process is called. It runs to the await and suspends.
2. Tick 2: the engine calls _physics_process again — a fresh entry on a new stack — while the previous coroutine is still suspended.
3. Now two coroutines are racing to mutate velocity, state, and the same position.

The visible result is non-deterministic: jitter, duplicated attacks, state machine corruption, occasional silent state freezes when one coroutine clobbers the other’s changes.

The Wrong Code

# anti-pattern
func _physics_process(delta):
    if state == ATTACKING:
        await get_tree().create_timer(0.5).timeout   # suspends
        do_strike()
        state = IDLE

Fix 1: Manual Tick Counter

Replace the timer with a counter you decrement each tick:

var windup_timer: float = 0.0
var state = IDLE

func _physics_process(delta):
    match state:
        WINDUP:
            windup_timer -= delta
            if windup_timer <= 0.0:
                do_strike()
                state = RECOVER

func start_attack():
    state = WINDUP
    windup_timer = 0.5

This is the standard finite-state machine approach for physics-driven entities. No coroutines, no allocations per tick, fully deterministic.

Fix 2: Timer Node with Signal

For a one-shot delay that triggers an action, a Timer node and signal connection is also fine — the callback is dispatched between physics ticks, not inside one:

@onready var windup_timer: Timer = $WindupTimer

func _ready():
    windup_timer.timeout.connect(_on_windup_done)

func start_attack():
    state = WINDUP
    windup_timer.start(0.5)

func _on_windup_done():
    do_strike()
    state = IDLE

Fix 3: Await in a Coroutine Off the Per-Tick Path

If you really want async syntax, isolate the await in a function called from a signal handler — never from _physics_process. The coroutine runs once per attack rather than re-entering on every tick:

func _ready():
    self.attack_requested.connect(_run_attack)

func _run_attack():
    state = WINDUP
    await get_tree().create_timer(0.5).timeout
    do_strike()
    state = IDLE

Because _run_attack is called once per attack — not 60 times per second — the await suspends one coroutine, not a flood of them.

Diagnosing Existing Code

Grep your scripts for await inside callback bodies:

grep -rn -B 5 "await" --include="*.gd" | grep -E "_physics_process|_process|_input"

Any match is a candidate for one of the three fixes above. If the await is for RenderingServer.frame_post_draw, that’s the rare legitimate use; otherwise refactor.

Verifying

Add a print(Engine.get_physics_frames(), state) at the top of _physics_process. Before the fix, you’ll see overlapping states or skipped frames during action windups. After the fix, state transitions are clean and tied to the counter or signal.

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

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

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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

“Await is a coroutine in disguise. Don’t spawn one every tick — spawn one per action and let the rest of physics stay synchronous.”

If a coworker says “we’re using await for a delay,” check whether the await is in a per-tick callback. 9 times out of 10 it is.