Why does Pygame miss key presses when the mouse moves?

The event queue has a 128-event capacity. Mouse motion at high refresh rates can fill it, dropping later events. Block MOUSEMOTION via pygame.event.set_blocked and read motion via pygame.mouse.get_rel each frame instead.

How do I block specific event types in Pygame?

Call pygame.event.set_blocked([pygame.MOUSEMOTION]) to stop those events from being queued. Use pygame.mouse.get_pos and pygame.mouse.get_rel to poll position and delta in your main loop.

Should I use set_allowed or set_blocked?

set_allowed is the inverse of set_blocked - it whitelists. Use set_allowed when you want only specific events; set_blocked when you want most events except a few. Either works for the same effect.

Fix: Pygame Event Queue Overflowing With Mouse Motion

Quick answer: Pygame queues max 128 events. Mouse motion at 1000Hz pollers can flood it and drop key events. Block MOUSEMOTION via pygame.event.set_blocked and read mouse position/delta via pygame.mouse.get_pos/get_rel each frame.

Here is how to fix Pygame games where moving the mouse during gameplay causes key presses to be dropped or laggy. The event queue is bounded; high-frequency motion events can crowd out everything else.

The Symptom

Player swings mouse and presses keys. Some key events never reach your code. Or input feels laggy when the mouse moves a lot.

What Causes This

Bounded queue. 128-event default capacity. Overflow drops oldest events.

High mouse poll rate. 1000Hz mice generate ~16 motion events per frame at 60 FPS.

Per-frame consumption insufficient. If pygame.event.get is called less than once per frame, the queue fills.

The Fix

Step 1: Block MOUSEMOTION events.

import pygame
pygame.init()
pygame.event.set_blocked([pygame.MOUSEMOTION])

Stops motion events from queuing. Other events get full queue capacity.

Step 2: Poll mouse state directly.

while running:
    for event in pygame.event.get():
        if event.type == pygame.QUIT: running = False
        # handle KEYDOWN, MOUSEBUTTONDOWN, etc.

    # Mouse state via polling, not events
    mx, my = pygame.mouse.get_pos()
    dx, dy = pygame.mouse.get_rel()   # delta since last call
    handle_mouse(mx, my, dx, dy)

get_rel reports cumulative delta since the previous call — equivalent to summing all dropped MOUSEMOTION events.

Step 3: Always drain the queue each frame. Call pygame.event.get exactly once per frame at the top of your loop. Skipping frames lets the queue fill.

Step 4: For raw mouse delta in FPS games, use mouse.get_rel after pygame.event.set_grab.

pygame.event.set_grab(True)
pygame.mouse.set_visible(False)
# In loop:
dx, dy = pygame.mouse.get_rel()
# Use dx/dy for camera rotation

Step 5: Verify queue health with peek.

n = len(pygame.event.peek())
if n > 100: print(f"Queue near full: {n}")

If consistently high, there is a queue consumption problem.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Pygame, 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

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 Pygame. 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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

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 Pygame-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 Pygame, 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.

“Block MOUSEMOTION. Poll position via get_pos/get_rel. Drain every frame. Keys never drop.”

Related Issues

For Pygame multi-monitor tearing, see Display Flip Tearing. For mixer end events, see mixer.music End Event.

set_blocked MOUSEMOTION. get_pos/get_rel. Drain queue. Inputs reliable.