Quick answer: Drive music from a combat state that the music system listens to, crossfade between tracks, and add a cooldown so music does not flip rapidly.

Music not changing with combat is a state-tracking and transition issue. Here is how to fix it.

How to fix it

1. Drive music from combat state

Track a combat state (in combat, exploring) and have the music system respond to it, switching to combat music when combat starts. If the music does not listen to the state, it never changes.

2. Crossfade between tracks

Transition between exploration and combat music with a crossfade rather than a hard cut, so the change is smooth. An abrupt switch is jarring; a crossfade keeps the music flowing as the state changes.

3. Add a cooldown

Add a cooldown before reverting to exploration music after combat ends, so brief lulls do not flip the music back and forth. Without it, music rapidly toggling between states is distracting and feels broken.

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

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.