Lost in Random: The Eternal Die / GAME HISTORY
Lost in Random Eternal Die Save Menu Freeze: The Cancel-and-Reopen Report
Stormteller acknowledged a reported Save and Exit freeze after a controller user canceled the prompt and quickly reopened it. The developer promised a later patch; that reply alone does not establish which shipped version fixed it.
Short answer
Stormteller acknowledged a reported Save and Exit freeze after a controller user canceled the prompt and quickly reopened it. The developer promised a later patch; that reply alone does not establish which shipped version fixed it.
Scope: Lost in Random: The Eternal Die, September 2025 Steam report using an Xbox controller. No final repair version was verified from the checked exchange.

The canceled prompt mattered
Foulax’s report on September 23, 2025 describes a short menu sequence rather than a failure while actually writing a save. Developer Antti of Stormteller replied on September 25 that the issue had been identified and should be fixed in the next patch. A planned fix and a published patch are different evidence.
The actions in the report
The player described the following controller interaction.
- Open Save and Exit.
- Select No, which is highlighted by default.
- Quickly open Save and Exit again.
- The controls stop responding, leaving the player unable to continue through the normal menu.
The report says clicking Continue with a mouse briefly affected the interface but did not restore useful control. The player then had to close the application manually. That is a self-report, not a test performed by Patchlo.
What to avoid without inventing a timer
Do not deliberately repeat the rapid cancel-and-reopen sequence while investigating. Let the menu close before making another selection. There is no verified number of seconds that guarantees safety, and this account does not establish save-data corruption. The demonstrated cost is losing control of the active session and having to shut it down.
What the historical reply leaves open
The checked exchange does not identify a final patch number. It cannot justify saying every current build remains affected, or that every existing session is safe after an unspecified update. Install available updates and include the platform, controller and menu sequence in any new report. Keep the original report’s narrow symptom separate from general controller-detection or loading-screen failures.
Join the conversation
Have a question, correction or a different take? Share it below. Comments appear immediately after submission.
Reader comments
Loading comments…