Quick answer: Pygame Rect uses half-open ranges — the right and bottom edges are outside the rect. For inclusive edge tests, inflate the rect by 1 pixel or write the comparison manually with <=.

A UI button at (100, 100) sized 80×30 is supposed to accept clicks anywhere inside its bounds. Players report clicks near the right edge fail. You log mouse coordinates — click at (180, 115) returns False from button.collidepoint((180, 115)). The point looks “inside” visually, but Pygame considers it outside.

Half-Open Interval Convention

Pygame Rect’s containment is defined as:

x ≤ p_x < x + width AND y ≤ p_y < y + height

For a rect (100, 100, 80, 30):

This is mathematically tidy — a 80-pixel-wide rect contains exactly 80 distinct x coordinates (100..179). But it surprises developers who expect (180, *) to count as “the right edge”.

Fix 1: Inflate by 1

def click_in_button(button_rect, pos):
    return button_rect.inflate(1, 1).collidepoint(pos)

inflate(1, 1) grows the rect by 0.5 pixels on each side (Pygame inflates symmetrically). The new effective bounds include the original right and bottom edges. Visually: a clickable area exactly matching the drawn button.

Fix 2: Manual Comparison

For full control, write the test yourself:

def point_in_rect_inclusive(rect, p):
    return rect.left <= p[0] <= rect.right and rect.top <= p[1] <= rect.bottom

Note <= on both bounds. Pygame Rect properties:

So p[0] <= rect.right includes the exclusive edge by intent.

For Rect-Rect Collision

The same convention applies to colliderect. Two rects touching at an edge don’t collide:

a = pygame.Rect(0, 0, 10, 10)
b = pygame.Rect(10, 0, 10, 10)   # a.right == b.left
a.colliderect(b)   # False

For most game purposes — tilemaps with non-overlapping tiles, separated entities — this is correct. It only surprises you when you intended adjacency to count as overlap.

For Grid-Aligned Tilemaps

If tiles are 16 pixels and tile (0,0) occupies (0,0)–(16,16) and tile (1,0) occupies (16,0)–(32,16), the half-open convention means a body at exactly x=16 is in tile (1,0), not (0,0). This is the right answer — otherwise the body would belong to two tiles simultaneously. Don’t change this for tilemaps.

Verifying

Print collidepoint results around the rect’s edges:

r = pygame.Rect(10, 10, 20, 20)
for p in [(10,10), (29,29), (30,30), (30,29)]:
    print(p, r.collidepoint(p))

Output: (10,10) True; (29,29) True; (30,30) False; (30,29) False. Confirms the right and bottom edges (x=30, y=30) are outside. With r.inflate(1,1).collidepoint(p), the (30, 29) and similar edge points are True.

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

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

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

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

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.

“Half-open intervals are correct. Whether they’re what you want depends on the context. Buttons want inclusive; tiles want half-open.”

Wrap UI hit-tests in a single hit(rect, pos) helper that does the inflate, so the convention is centralized.