Quick answer: Make edits outside play mode, save the scene explicitly, and never expect play-mode changes to persist.

Scene changes not saving is usually play-mode edits or an unsaved scene. Here is how to fix it.

How to fix it

1. Do not edit in play mode

Changes made while in play mode are discarded when you stop playing. This is the most common cause of lost edits. Make changes outside play mode, or copy values to reapply after stopping.

2. Save the scene explicitly

Save the scene after editing (and before closing or switching scenes). Unsaved changes are lost when the editor closes or the scene changes. Watch for the unsaved-changes indicator and save.

3. Mark changes dirty if scripting

If you change a scene object from an editor script, mark the object and scene dirty (SetDirty, MarkSceneDirty) so Unity knows there are unsaved changes to save. Changes not marked dirty may not be saved.

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.

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