Use an evidence ladder
An official fix note proves that Pocketpair shipped an intended correction; it does not prove every save is repaired. A community report is a reproduction lead, not proof of a widespread current defect. Several reports in this August review predate v1.0.3 or omit the exact build, and the locally captured official news now extends through v1.0.5.
Sort symptoms before changing a save
| Symptom family | First diagnostic |
|---|---|
| Cannot join a world | Compare full client and server versions and storefront update state |
| Accessory effect after a swap | Record equipment before/after; a re-equip is a community suggestion, not a verified repair |
| Controller or missing cursor | Record input devices; test a single-input setup |
| Long-session stutter | Record elapsed play time, hardware, settings and logs; do not label it a memory leak without evidence |
| Natural trees not worked | Check task settings, respawn timing and the later 1.0.4 logging fix |
| Steam delivery stalled | Diagnose Steam download state separately from game/save corruption |
Create a report another person can reproduce
- Give platform, storefront, full build, server type and whether the world predates the patch.
- State expected result, exact actions, actual result and repetition rate.
- Disclose current and previously installed loaders/mods; preserve a separate world backup.
- Attach a short clip or relevant log with private account information removed.
- Avoid deleting saves or reinstalling a console game to force an unavailable update. Recheck later official notes before claiming an August report still applies.