Fix: GameMaker Tilemap Collision Shape Mismatch

Here is how to fix GameMaker GMS2 tilemap collision checks that report wrong values. Your character walks through walls because tile_meeting says no collision. Or your wall-detection script stops working when a tile is rotated. The cause is the bit-packed tile data format and the requirement that source sprites have collision masks.

The Symptom

tile_meeting returns false on tiles you can see. Or comparing tilemap_get(layer, cx, cy) == TILE_GROUND fails when the tile in question is flipped or rotated, because the data includes those flags.

What Causes This

Raw tile data includes flip/rotation bits. tilemap_get returns a 32-bit value where the index is the lower bits and rotation/flip are upper bits. Direct comparison fails when those upper bits are non-zero.

Sprite has no collision mask. tile_meeting checks the source sprite’s collision shape. If the sprite’s mask is not configured, the function returns false even on tiles with visible art.

Layer ID wrong. tilemap_get_at_pixel needs a specific tilemap layer ID, not a layer name. Use layer_tilemap_get_id(layer_get_id("Walls")).

World vs screen coordinates. Functions like tilemap_get_at_pixel expect world coordinates, not view-relative.

The Fix

Step 1: Strip flag bits before comparing.

var _data = tilemap_get_at_pixel(layer_walls, x, y);
var _idx  = tile_get_index(_data);

if (_idx == TILE_GROUND) {
    // solid floor
}

tile_get_index extracts the lower bits cleanly. Use this for any comparison.

Step 2: Configure source sprite collision mask. Open the sprite that the tilemap uses (often called something like spr_tileset_walls). Set Collision Kind to Rectangle or Precise. tile_meeting now uses this mask.

Step 3: Cache the layer ID.

// Create event of oController
layer_walls = layer_tilemap_get_id(layer_get_id("Walls"));

Cache once. Looking up by name every frame is wasteful.

Step 4: Use world coordinates.

// In a player object's Step event - x and y are world coordinates
if (tile_meeting(layer_walls, x, y + 2)) {
    // player is on solid ground 2px below
}

If you need to convert from a mouse or device position, use device_mouse_x_to_gui conversions or just mouse_x which is already world.

Step 5: Read flag bits if you need them.

var _data = tilemap_get_at_pixel(layer_walls, x, y);
var _idx = tile_get_index(_data);
var _rot = tile_get_rotate(_data);
var _flipx = tile_get_flip(_data);
var _flipy = tile_get_mirror(_data);

Useful for tile-aware behaviors like reading slope direction from the rotation flag.

Common Patterns

Floor check: if (tile_meeting(layer_walls, x, y + 1)) just below the player.

Wall check: if (tile_meeting(layer_walls, x + sign(hspeed), y)) in front.

Hazard tile: if (tile_get_index(tilemap_get_at_pixel(layer_hazard, x, y)) == TILE_LAVA).

Performance Note

tile_meeting is fast (sprite collision check); tilemap_get_at_pixel is also cheap. Both can be called multiple times per Step without measurable impact for typical hundreds of objects. For thousands, consider precomputing solid grid arrays at level start.

Understanding the issue

Tilemaps are dense data structures. A single tile change touches several other systems: rendering, collision, possibly navigation. Bugs at the intersection often look like 'I changed one tile, why did three other things break'.

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

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

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

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For GameMaker-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 GameMaker, 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.

“Tile data is packed. Strip flags before comparing. Source sprites need masks. World coordinates only.”

Related Issues

For surface lifecycle, see Surface Lost After Resize. For shader uniforms, see Shader Uniform Per Frame.

tile_get_index strips flags. Sprite mask enables tile_meeting. World x/y. Solid checks work.