Start with the symptom—not a random file fix
| What you observe | Relevant official note | Safe conclusion |
|---|---|---|
| A house with stacked clay blocks used to freeze during loading | October 27 hotfix | A known case was fixed for some saves; update before assuming the same issue remains |
| Loading progresses extremely slowly on a large house | Hotfix 2 notes slow PCs and big houses | Slow loading is not proof that the file is corrupted; record progress and hardware |
| Loading stops progressing | Hotfix 2 uses new no-progress/total time limits | The timeout behavior is detection, not a tool that reconstructs the save |
| You get “could not load save” | Normal failure/reporting route | Preserve the exact message and version; no universal repair is announced |
| You end up in an incomplete world without an error | Hotfix 2 aims to return players to main menu instead | Check current build; the old half-loaded behavior is a separate defect |
| The loaded location no longer has a village after completing a trial | October 27 completed-trial map fix | This is a map-state case, not necessarily a loading hang |
A version-safe troubleshooting sequence
- Identify the game build first. The release was October 26. The first relevant patch is October 27; Hotfix 2 is dated October 29 and labels itself
1.0.25.afc5b3. Let Steam complete its normal update before attributing symptoms to the newest version. - Protect the only save. If your progress matters, keep an unchanged backup using a method you already trust before attempting further gameplay or file operations. Neither patch instructs players to delete local files, replace a Steam Cloud save or edit the internal save format. We do not provide guessed file paths.
- Note whether the world contains stacked clay blocks. This detail is relevant only because October 27 specifically named that construction pattern. It does not prove every loading freeze has the same cause.
- Watch the progress state rather than repeatedly force-quitting at arbitrary intervals. In Hotfix 2, the developers describe an abort after four minutes with no progress, or twenty minutes total. A four-minute no-progress interval is not a promise of load completion. Preserve the exact failure dialog if one appears.
- If it fails, record the distinction. Did the game return to the menu, show a save error, crash to desktop or remain on screen? Those outcomes lead to different support reports. Collect the current build and a description of the house/last action; do not declare the save permanently lost from a single loading failure.
- Separate performance from save corruption. Hotfix 2 reduces logging overhead and fixes two listener leaks, which the developer says may help loading large houses. It does not identify the size at which every house should load, or mandate a graphics setting that repairs saves.
- Use the developer’s support/bug report route for a persistent failure. Keep the diagnostic details and do not submit private files or account credentials to third-party guide sites.
What the two October hotfixes did—and did not do
October 27: fixed certain save-load freezes involving stacked clay blocks and corrected an issue where a completed trial could restore the wrong map state. Neither line says all failed save files are automatically repaired.
October 29: improved error handling when loading makes no progress; specified four-minute/no-progress and twenty-minute/overall limits; added a fallback to the main menu when the expected error popup does not display; included load-related performance improvements. A fallback to the menu is not a successful load.
The same October 29 release also adds Stay here / Roam free to the walking hut’s chair and changes fullscreen/DX11 handling. Those other features are covered in the REKA Hub; changing hut behavior or graphics settings is not documented as a universal fix for a broken save.
November 3–6: identify the NEW save failure type before trying an October workaround
Hotfix 3 (November 3) reduced RAM and VRAM load demands, fixed memory leaks during travel/loading and improved a few very old tutorial-save cases. That helps distinguish a game running out of hardware memory from the October 29 four-minutes-without-progress / twenty-minutes-total timeout — a timeout by itself doesn’t restore any data.
Hotfix 4 (November 6) fixed save freezes with clay walls, saving while a world was still loading, two specific corrupted-save scenarios involving bludnik shelf variants together or buying an item from Bogdan at Dziady, and improved loading robustness. Do not assume every older save is automatically repaired. For a matching case: record which construction/quest action preceded the failure, preserve the only working copy and update to a build containing Hotfix 4 before testing a normal load. Success: that same save reaches the fully interactive world and retains the expected quest/build state, not merely a successful main-menu return. For other symptoms, provide the exact build and log via official support rather than modifying proprietary save data without a documented recovery method.
If a save still cannot load
Preserve what exists, note your last known working build, whether the save predates 1.0, whether the world had a large clay-block structure, and exactly what happened after the timeout. Submit that context to the developers through their official channels. Do not download a third-party “save fixer,” replace the only file with another player’s save, or present the October 29 timeout as data restoration.
FAQ
Will Hotfix 2 recover my deleted save? No developer source reviewed here promises recovery of a file that has already been deleted or overwritten.
Why does REKA return me to the main menu? Hotfix 2 documents this fallback after an aborted load when the normal failure popup does not appear. It is a controlled failure response, not proof the file was repaired.
Is the four-minute rule the maximum load time? No. Four minutes is the limit for no progress; the total cap is twenty minutes. These are separate conditions.
Should I remove stacked clay blocks from a save I cannot open? The developer did not publish a safe external editing procedure. Do not delete or manipulate an inaccessible save based on an unsupported guide.
Does this fix REKA’s fullscreen black screen? No. Hotfix 2 also has display fixes, but they address a different symptom. See the REKA task hub.
Official evidence
- Developer Hotfix October 27 — named stacked-clay loading fix.
- Developer Hotfix 2, October 29, build
1.0.25.afc5b3— no-progress/total timeout and main-menu fallback. - REKA developer news — authoritative update chronology.
Editorial source review: November 11, 2026 (Hotfixes 2–4 kept separate). No hands-on game client or player save was examined, no screenshot is bundled, and no universal save recovery is claimed.