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 Construct 3 Audio Not Muting When the Browser Tab Is Backgrounded

Q: What causes Construct 3 audio not muting when the browser tab is backgrounded?

Your project does not react to the page becoming hidden, so when the player switches tabs the Web Audio context keeps running and the game plays sound from a tab they cannot see.

Quick answer: Use the On window 'hidden' / 'shown' (visibility) conditions to set master volume to silence when hidden and restore it when shown, optionally pausing music too.

Browsers keep audio running in background tabs unless you act. Construct 3 exposes visibility events; muting the master on hidden and restoring on shown stops the unwanted background noise.

How to fix it

1. React to visibility change

Add Browser conditions for the page becoming hidden and visible (or use the Audio object's tab-visibility handling) so you have a hook the moment the tab is backgrounded.

2. Silence the master volume

On hidden, set the Audio master volume to a very low dB (effective mute); on shown, restore it. This keeps state intact without stopping every individual sound.

3. Optionally pause music

For long music tracks, also pause playback on hidden so the track does not advance while the player is away and resume it when the tab returns.

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.

A crash you can name from its stack trace is a crash you can usually fix in minutes.