The sources we reviewed includes older demo reports of a freeze on the moon screen while crops update and a severe frame-rate drop after a moon cutscene. It does not prove that a midnight crash is reproducible in the Steam v1.0.0 release.
Source-limited · checked
Evidence boundary
What is not confirmed yet
This page states only what the sources checked for it support. The following details are still open:
- Need a reproducible v1.0.0 transition, exact error/log and confirmed developer or patch status.
Source-limited · checked
Sources checked and their limits are listed under Sources checked below.
Safe diagnostic order
- Exit the game and copy your save folder before changing files. The sources we reviewed do not establish the save path, so locate it through Steam support or the developer community instead of deleting guessed folders.
- Restart Windows and Steam.
- In Steam Library, open the game's Properties → Installed Files → Verify integrity of game files.
- Retry once with non-essential overlays, recording tools, and monitoring utilities closed.
- Note whether the failure occurs before the moon result, during “updating crops,” or after the next day begins.
- Record game version, Windows version, GPU/driver, save age, in-game date, moon/event text, and the exact error or log.
- Submit the report through the official Steam Community or Discord linked from the game's Steam page.
Do not delete the save, registry entries, or runtime folders as an opening step. Do not treat a demo-era workaround as a v1.0 fix.
If the problem is low frame rate without a crash, use low FPS. If the game never reaches the menu, use splash-screen crash.
Not confirmed yet: at least one reproducible v1.0.0 report with an exact transition, error/log, and confirmed developer response or patch status.
← Swipe wide tables to compare all columns →