Quick answer: Keep editor code in Editor folders or behind editor-only compilation, do not reference UnityEditor from runtime scripts, and guard play-mode state-change callbacks.

An editor script breaking play mode is editor code leaking into runtime. Separating them fixes it. Here is how.

How to fix it

1. Keep editor code in Editor folders

Code using the UnityEditor namespace must live in an Editor folder or an editor-only assembly. Referenced from runtime, it fails to build and can break play mode. Separate it.

2. Guard with compilation symbols

Where runtime code must include editor-only bits, wrap them in UNITY_EDITOR conditional compilation so they exist only in the editor and are stripped from builds.

3. Guard play-mode callbacks

Editor callbacks for play-mode state changes can throw during the transition and break entering play. Guard them, check the state, and handle exceptions so a faulty callback does not block play mode.

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.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.