Start with the matching symptom
The tinyBuild known-issues page is read alongside the official Steam patch announcements, checked October 8. A patch note is a developer fix claim for the named update, not proof that your save recovered or that the same update reached every console. If your symptom is not listed, that does not prove it is unique or already fixed. For a crash or lost items, preserve the save and evidence before experimenting; do not delete a save to test a workaround.
Check the patch before retrying
- Note your platform and installed version. Compare Steam notes with your Steam build; console version numbers and rollout dates may differ.
- If an update is available, preserve the save and any PC log needed for a report before closing the game, then install the update.
- Return to the affected action once. If it still fails, report the version and exact state instead of repeatedly spending materials or starting a new save.
Steam 1.007 (September 28) names pier-stair collisions and Central Districts Purge Parts I and II among its fixes. For a character stuck on the pier or a blocked battle quest, check that update before trying save edits. The notes do not give a universal unstuck command or a manual repair for every affected save.
Slowdown, tearing and console saves
| What you see | What is actually known | Next step |
|---|---|---|
| Performance worsens during a long session | Publisher-listed issue with a specific temporary step. | Save by resting in bed, preserve the PC log if reporting, then close and relaunch. Follow the platform troubleshooting steps if it recurs. |
| Screen tearing on a console | Listed; no console-specific fix is published on the issue page. | Record platform, display settings and a short clip. Do not assume a PC graphics setting applies. |
| NPCs freeze and time stops on PS5 or Xbox | The publisher marks this save-breaking exception as fixed and asks players to update. Its page still says a PS4 patch is being worked on. | Check for the latest update on your own console. Preserve progress and report a remaining freeze; this status does not guarantee every affected save recovers. |
Newer Steam symptoms: match the action, not just “stuck”
- 1.008, October 2: addresses a conveyor-related endless loading screen, a crash when going to bed, and progression blocked by completing Linda’s Ball before the Plague Doctor’s Beautiful Dream. A loading fault, bed crash and quest-order fault need different report details.
- 1.009, October 6: addresses load-time crashes, getting trapped after the nun’s base upgrade, and collisions around several stations. Record where and when the character gets stuck if it persists after updating.
- A worker stops after returning resources: compare the station with the current worker patch checks.
- Fish bait is present but not recognized: see the bag-specific fishing check before changing your catch technique.
These Steam notes describe developer fixes, not a repair we have tested in your save. A community report after 1.009 describes resurrection-zone gates becoming inaccessible. That is a separate, unconfirmed regression; the tower-gate interaction fix in the notes does not prove a remedy. Keep the save and report the gate, quest state and build. No verified official recovery route is established here.
Stuck stations, quests and rewards
The support page groups the symptoms below, together with missing pickups, corpse-count errors and partial-stack chest loss, as addressed by patch 1.007 on most platforms. It explicitly says they remain on Switch 1 and 2 while that patch is pending. Check your platform’s installed update; matching numbers alone do not establish identical rollouts.
| What you see | What is actually known | Safe next step |
|---|---|---|
| Garden well upgrade can be crafted again | Included in the publisher’s 1.007 fix group; still listed for Switch 1 and 2. | Avoid the repeat craft. If it already crashed, note the console and build rather than trying it repeatedly. |
| Corpse stuck on the crematorium table | Steam 1.005 (September 24) announces a fix. The support page now limits the outstanding 1.007 group to Switch 1 and 2. | Check the installed update before retrying. If it persists, report the corpse and station state; no separate manual recovery is documented. |
| Study Table stops responding or gives no Science | Steam 1.005 addresses the locked table; 1.007 addresses missing Science and items that could not be studied. | Match the symptom to the update. If it recurs, record the item and sequence; avoid sacrificing more valuable items to test. |
| Town Warehouse will not accept iron delivery | Steam 1.007 announces an iron-delivery quest fix; the support page limits the outstanding warning to Switch 1 and 2. | Check the patch, then the same quest state. If still blocked, record counts and turn-in steps rather than repeatedly handing over supplies. |
| Soldiers receive beer or pie but you receive no reward | Included in the publisher’s 1.007 fix group; pending on Switch 1 and 2. | Record the item and dialogue; avoid spending more items solely to retest until the status changes. |
“Record” is a precaution for a reproducible report, not an official repair. A problem being on this list does not establish when a patch will ship.
Missing points, corpse counts or items
| What you see | What is actually known | Safe next step |
|---|---|---|
| Research pickup is visible outside reach | Out-of-bounds pickups are in the 1.007 fix group; pending on Switch 1 and 2. | Check the pickup and counter before repeating the action. See the point-loss checks; no recovery method is published. |
| Morgue capacity counter goes negative after cremation | This corpse-count fault is in the 1.007 fix group; pending on Switch 1 and 2. | Record the displayed capacity before and after cremation. Do not assume the negative number represents extra usable capacity. |
| Only part of a stack fits in a full chest | Partial-fit item loss is in the 1.007 fix group; pending on Switch 1 and 2. | Leave enough room for the whole stack before moving valuable items. This avoids the reported partial-fit situation; it is not a recovery method for already lost items. |
When the issue is still happening
- Write down your platform, game build, location, the exact action and the visible result.
- On PC, copy
Player.logbefore launching again if you plan to report a bug; the publisher says a new launch resets it. Keep save files private and send them only through official support. - Steam PC update 1.006 added in-game bug reporting. Use that option if available in your build, or use tinyBuild's bug-report instructions. For performance alone, the existing troubleshooting guide has platform-specific checks.
This is an independent symptom index, not the publisher's live status feed. Recheck the official list after a patch and match its platform before assuming an older entry still applies.