Short answer
Save still will not load? Back it up and check the 0.8.0 public save fix. World sections missing? Check 0.7.2. Stash refusing to open? Check 0.7.1. A disabled repair item, an empty container or missing quest equipment needs the matching branch below; these are not all the same bug. A patch-listed fix does not prove every affected save has recovered.
Find the next step for your symptom
| What you see | Evidence | What to do next |
|---|---|---|
| Enemy footsteps seem absent or hard to locate | 0.8.0 lists a fix for off-screen AI footsteps | Compare scoped and nearby observations before changing settings. |
| Cliffs seem to block the Inhuman crash site | Developer describes ordinary access | Check the search area and approach; no special key is established. |
| World sections do not load | 0.7.2: fix listed | Update, then report the exact location if it remains. An unrevealed map label is not missing world terrain. |
| Stash interaction does nothing | 0.7.1: fix listed | Check opening, camp and tab separately. |
| Gun repair item cannot be applied | 0.7.0: revised item rules | Match the exact maintenance item, not an old universal condition cutoff. |
| Ordinary containers remain empty | Developer reply: one real-world hour | Check the container timer; sleeping through a game hour is not equivalent. |
| Bunker still appears cleared | 0.7.0: reset fix listed | Use bunker-specific return checks; the developer specifies three real-world hours. |
| Catching Current says a magazine is missing | September 10 community solution, acknowledged by the original poster | Check the detector and its signal; missing the detector entirely is a separate branch. |
| Items are present but Bogdan dialogue will not advance | Separate community reports | Compare dialogue failure with missing lime. |
| Backpack loss after trader input and reload | September 4 report; exact final fix not established | Preserve your recovery point and read the dated incident. Do not repeatedly save over the affected state. |
Source: Hotfix 0.7.2 ↗
Source: Hotfix 0.7.1 ↗
Source: Update 0.7.0 — repairs, UI and save/load changes ↗
Save will not load: public 0.8.0 fix
Back up the save, update the public game and try loading it again. Update 0.8.0 says previously experimental fixes for several corrupted-save and file-lock cases were included in the public release. This does not establish that every damaged save can be recovered.
- Copy the affected save folder.Keep a separate untouched backup and note your current game version and branch.
- Update and load the existing save.The developer states existing saves are compatible and recommends, but does not require, starting again to experience changes.
- Verify progress and inventory.If loading still fails, preserve logs and the backup, then report the build and precise error through Feedback.
Source: Update 0.8.0 — corrupted saves, file locks and compatibility ↗
Before retrying or reporting
CrossOver: all save slots disappear after saving
Back up the save folder before further tests; try the public 0.8.0-or-later save fix first. The original report is for Scavland 0.7.1 running through CrossOver on macOS. FailNot's developer-marked reply, checked October 8, says the issue was fixed on the experimental branch. This is not a guarantee of recovery or evidence of a native macOS release.
- Stop saving and close the game.Copy the full Scavland save folder from the affected CrossOver bottle to a separate backup. Keep the original files and logs; do not delete your only recovery point.
- Match the error, not only the empty slot list.The report names a .checkpoint-* directory and a manifest.json failure inside SaveCheckpoint.RecoverStaging. Record your build, CrossOver version and whether your log has the same error.
- Consider the developer's branch test.Follow the public-build instructions above, retaining the untouched backup. Verify inventory and progress after loading, then check whether a new test save remains visible after restarting.
The player reported that removing a checkpoint directory temporarily restored the slots, but the problem returned after saving again. That is not a permanent fix, and this guide does not recommend blindly deleting checkpoint folders. If the public-build test fails, preserve the logs and report the exact branch and error to the developer.
- Keep the current recovery point.If items or saves are affected, stop irreversible changes. Do not test by deleting saves or selling the equipment.
- Check the relevant condition.Read the actual item, Job, camp or mode. For death-screen choices use the recovery guide.
- Send an actionable Feedback report.Include version, mode, location, steps, expected result and observed result. Mention mods if present; leave account information out of public screenshots.
Source: Update 0.8.0 — off-screen AI footsteps fix ↗
Enemy footsteps: missing audio or a scoped-view mismatch?
Update 0.8.0 lists a fix for AI footsteps outside the screen. Update first; if the problem remains, record the circumstances and report it. Players disagree about missing and directional footsteps. One proposes that hearing stays centered on the character while aiming farther away, but this is a player explanation, not a developer-confirmed radius or measured distance.
- Check the immediate surroundings safely.If you hear a nearby threat while looking through a scope, leave the distant aiming view and inspect around your character. Do not interpret a clear distant view as proof the area around you is safe.
- Compare like-for-like observations.If safe, note whether sound differs between normal view and distant aiming at the same location. Record the audio device, build and mods; change only one setting at a time and retain its original value.
- Record a reproducible failure.A short clip showing your position, view and the audible or missing cue is more useful than a claimed hearing distance. If the problem also occurs nearby without aiming, say so explicitly in Feedback.
These are diagnostic checks, not a tested repair. The discussion does not establish a universal silent-enemy bug, an exact hearing radius, or that reloading fixes it. Keep a recovery point and avoid repeatedly recreating an ambush just to test sound.
Source: Footstep discussion — conflicting player explanations, checked October 10 ↗
Source: Sudden Growling sound — player account of a nearby threat while scoped, not a mechanics test ↗
Historical reports are not current diagnoses
The launch trader-input report was acknowledged by a developer. Later 0.7.0 notes describe UI and save fixes, but do not explicitly identify that thread as resolved. The exact incident status remains unconfirmed; it does not mean every player still has the bug.
Source: Original trader-input incident and developer reply ↗
Known-issues FAQ
Is everything here a confirmed current bug?
No. The table distinguishes fixes listed by the developer, changed game rules and dated community reports. Your save still needs its own version and context.
Should I wait an in-game hour for ordinary loot containers?
The developer reply cited by the loot guide specifies one real-world hour, not one hour skipped through sleeping. Bunker resets have a separate rule.
Where should I report a remaining problem?
Use in-game Feedback with the version, mode, exact steps and affected location or item. Protect your save before repeating a loss-related problem.