Quick answer: Write the new high score to persistent storage the moment it is beaten, not at quit, and flush the write so it survives an abrupt close.
If a player sets a record then force-closes, the score vanishes because it was only meant to save on quit. Persist it the instant it is beaten. Here is the fix.
How to fix it
1. Save when the record is set
Write the new best score to persistent storage immediately when it surpasses the stored value, rather than deferring all persistence to a quit handler that may never run.
2. Flush the write
After writing, flush or commit so the value is actually on disk. A buffered write that is still in memory at a force-close is as good as lost.
3. Keep quit-time save as a backup
Leave the on-quit save in place too, but treat it as a safety net rather than the primary path, since clean shutdown is not guaranteed.
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 Unreal Engine 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.