How to Fix Unity Save-on-Quit Not Firing When You Stop Play in the Editor

OnApplicationQuit behaves differently between a real build exit and stopping Play mode, so save-on-quit can look broken or look fine misleadingly. Hook the editor event too.

How to fix it

1. Hook the editor play-state event

Inside #if UNITY_EDITOR, subscribe to EditorApplication.playModeStateChanged and save when the state becomes ExitingPlayMode.

2. Save on pause as well

Persist in OnApplicationPause(true) so the save path is exercised consistently across editor, mobile, and desktop builds.

3. Do not depend only on quit

Treat OnApplicationQuit as best-effort. The authoritative save should happen at meaningful checkpoints, not only at the final exit callback.

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