Quick answer: Profile an exported release build for real performance, disable editor debugging features when testing, and do not judge frame rate from editor playback alone.
Lag in the editor only is editor overhead. Testing the export shows real performance. Here is how.
How to fix it
1. Profile an exported build
Editor playback carries debugging and editor overhead that an exported build does not. Profile a release export to judge real performance, since the editor can be significantly slower than the shipped game.
2. Disable editor debugging when testing
Features like the remote scene tree and debug collision shapes add cost during editor playback. Disable or account for them when assessing performance, so you measure the game and not the editor's tooling.
3. Do not judge from editor frame rate
A lower frame rate in the editor does not necessarily mean the game is slow. Confirm with an export before optimizing, so you do not chase a slowdown that only exists because of editor overhead.
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 Godot 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 errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.