Fix: Godot Input Action Double-Firing on Keyboard

The player presses Jump once and the character jumps twice or jumps to twice the height. You add a log, see two consecutive just_pressed calls in the same press, and wonder how Godot can detect two key downs from a single physical press. It can’t. The duplication is in your callback wiring.

Cause 1: Checked in Two Places

The most common cause: Input.is_action_just_pressed is checked in both _process and _physics_process in the same frame. The flag stays true for a full frame, so both callbacks see it as true and both jump.

# Anti-pattern: both callbacks consume the same press
func _process(delta):
    if Input.is_action_just_pressed("jump"):
        queue_jump_animation()

func _physics_process(delta):
    if Input.is_action_just_pressed("jump"):
        velocity.y = jump_force   # also fires this frame

If the press is registered between a physics tick and the following render frame, both callbacks observe the rising edge. The animation queues twice, or two physics frames apply jump_force back-to-back.

The fix is to read the press in one place and store a one-frame queued action:

var jump_queued: bool = false

func _process(delta):
    if Input.is_action_just_pressed("jump"):
        jump_queued = true

func _physics_process(delta):
    if jump_queued:
        velocity.y = jump_force
        queue_jump_animation()
        jump_queued = false

The press is captured once in _process (rising-edge accuracy) and consumed once in _physics_process (deterministic physics timing).

Cause 2: Unfiltered Key Echoes

If you handle keys in _input directly:

func _input(event):
    if event is InputEventKey and event.pressed and event.keycode == KEY_SPACE:
        jump()   # fires repeatedly while space is held

The OS sends key-repeat events while a key is held. The InputEventKey has is_echo() == true for those repeats. Filter them out:

func _input(event):
    if event is InputEventKey and event.pressed and not event.is_echo() and event.keycode == KEY_SPACE:
        jump()

Better: use the InputMap and check event.is_action_pressed("jump"), which has an optional allow_echo argument defaulting to false:

func _input(event):
    if event.is_action_pressed("jump"):   # ignores echoes by default
        jump()

Cause 3: Both _input and _unhandled_input Handling the Same Event

Godot dispatches input events to _input first, then to _unhandled_input if nothing called get_viewport().set_input_as_handled(). If you implement jump handling in both, a single key press fires both callbacks. Pick one:

# Use _unhandled_input for gameplay so UI takes priority
func _unhandled_input(event):
    if event.is_action_pressed("jump"):
        jump()
        get_viewport().set_input_as_handled()

Verifying

Add a print with frame number:

func _unhandled_input(event):
    if event.is_action_pressed("jump"):
        print("jump on frame ", Engine.get_process_frames())

One print per physical press means the fix is in. Two prints on the same frame — you’re still double-binding.

Understanding the issue

Input handling sits between hardware and gameplay. Hardware has its own protocol; gameplay has its own model. When these don't agree, the player perceives unresponsiveness even though every layer is technically functional.

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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

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

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.

“Pick one callback. Filter one echo. Set input as handled. The whole class of input double-fire bugs disappears.”

Almost all “double-jump on one press” reports trace back to _process+_physics_process both checking is_action_just_pressed.