Your next step
The 15 October patch fixes staff that could not be unassigned from fire-damaged equipment and clears assignments to missing equipment when older saves load.
Separate the assignment from the fire
Before rebuilding a damaged station, identify which employee and equipment are involved. Write down whether the problem is an active fire, an assignment that cannot be removed, or a sale that will not complete. These are different symptoms. A screenshot of the assignment screen gives support a concrete starting point; a picture of the damaged room alone may not show the blocking relationship.
Try the current assignment controls
After confirming the installed build, revisit the affected employee and station using the game’s normal controls. Our suggested sequence is to inspect the assignment, attempt to remove it, and then check the equipment’s sale action. Record which step still fails. This sequence is a diagnostic checklist, not a promise that selling every damaged station is necessary or that staff automatically resume their old jobs.
Report an older-save mismatch precisely
If this began after loading an older world, keep that detail in the report. Compare the employee’s displayed assignment with equipment that actually exists in the shop. Preserve a copy of the save before experimenting with replacement furniture. Do not repeatedly overwrite your only recovery point while testing. Include the visible build and whether you are host or guest; those details help distinguish a persistent reference from a new incident.
Your reference sheet
| Check | What to record | What it tells you |
|---|---|---|
| Build | Record the installed version | Compare with the dated patch |
| Symptom | Write the exact screen or failed action | Keep observation separate from explanation |
| Comparison | Change one thing and record the result | Preserve a reproducible report |
The sheet stays in the open page. Download saves a text copy on your device; it does not change your game or send us a report.
Before your next shift
Is this a newly released 20 October feature?
No. This reference was published on 20 October and explains the linked 15 October patch.
Has this procedure been playtested here?
No. The developer-reported change is sourced; the diagnostic and planning checklist is editorial guidance.
Source and scope
Wild Dog — 15 October v0.1.57.18549 notes ↗. Reviewed 20 October 2026. Mechanic descriptions come from Wild Dog’s released notes. Our worksheet is an editorial aid; no timed playtest or numerical benchmark is claimed.