How to Fix Construct 3 Bus Volume Not Affecting Sounds on a Tag

You lower an SFX bus but the effects stay loud. In Construct 3 a sound only obeys a bus once it's actually routed there.

How to fix it

1. Route the tag to the bus

Use Audio > Add tag to bus (or specify the bus when calling Play) so the sound flows through your custom bus rather than Master.

2. Set bus volume after routing

Call Set bus volume on the same bus name; volume changes only affect sounds currently routed there.

3. Check bus name spelling

Bus names must match exactly between the route and the volume action, or the change applies to a bus with no sounds.

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.