What causes Construct 3 touches passing through the pause menu?

Touch events are evaluated against gameplay objects regardless of the pause overlay, so a tap meant for a menu button also triggers actions on the world beneath it.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Construct 3 Game Where Touches Pass Through the Pause Menu

Quick answer: Put the menu on its own layer, check that the menu was not touched before running gameplay touch logic, or use a fullscreen blocker sprite to absorb stray taps.

Opening your Construct 3 pause menu and tapping Resume sometimes also fires a shot or moves the player. Touch is hitting both layers. Gate gameplay input on whether the game is paused so the menu absorbs the tap.

How to fix it

1. Gate gameplay input on pause

Wrap gameplay touch events in a condition like Is paused = false so taps are ignored by the world while the menu is open.

2. Use a blocker sprite

Place a transparent fullscreen sprite under the menu buttons and put it above gameplay so any tap not on a button is consumed by the overlay.

3. Order touch checks

Evaluate menu button touches first and use Else or a flag so a tap that lands on a button cannot also fall through to the world behind it.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Construct 3 error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.