Operational priority
Use the developer-published local save path only for applicable old Playtest black-screen or load failures, with a clear warning that deletion resets progress.
Start with one clear objective: use the newer in-game legacy migration first when offered and reserve manual folder deletion for the developer-described old-save scenario. A smaller, recoverable trip is usually more useful than an ambitious route that consumes the equipment needed for the next attempt.
What current evidence supports
Current official or developer evidence supports the `%LOCALAPPDATA%\NotQuiteDead` baseline, old Playtest incompatibility warning and later legacy migration flow.
The August 25 release-candidate update introduced an in-game legacy-save prompt, so older manual guidance is a conditional fallback.
Decision sequence
Read the current signal, make one readiness check, and choose a response before committing resources. The decision board below keeps that sequence visible during play.
- Match the symptom exactly
- Check source date and status
- Prefer developer evidence over discussion titles
- Back up data before destructive workarounds
- Record the build when monitoring a report
Risk controls
Keep evidence confidence separate from personal observation. Mark what you saw in the current build, preserve an exit margin, and do not let an old screenshot or discussion title become a permanent game rule.
- Avoid: Promoting one report into a confirmed game-wide bug.
- Avoid: Calling a fix current without rechecking.
- Avoid: Deleting local data without a progress-loss warning.
Decision board
| Signal | Check | Field response |
|---|---|---|
| Developer says fixed | Is the note newer than the report? | Label FIXED BY DEVELOPER with the source date. |
| Community report | Is it repeated or acknowledged? | Keep COMMUNITY REPORTED or MONITORING. |
| Destructive workaround | Does the exact scenario apply? | Warn, back up, and prefer the newer in-game flow first. |
Common mistakes
- Promoting one report into a confirmed game-wide bug
- Calling a fix current without rechecking
- Deleting local data without a progress-loss warning
Current patch note
The August 25 release-candidate update introduced an in-game legacy-save prompt, so older manual guidance is a conditional fallback.
Frequently asked questions
What should I do first for Save File Location & Old Playtest Save Fix?
Start by deciding how you will use the newer in-game legacy migration first when offered and reserve manual folder deletion for the developer-described old-save scenario. Use the checklist before committing scarce supplies or valuable equipment.
Is every exact detail verified for the release build?
The August 25 release-candidate update introduced an in-game legacy-save prompt, so older manual guidance is a conditional fallback.
Which guide should I open next?
Continue with /known-issues, /permadeath, /beginner-guide based on the next system blocking your current objective.
Sources & verification
- Black Screen / Previous Playtest Players: Save File ResetDeveloper links incompatible old Playtest saves to some black screens and documents the destructive local reset path and warning.
- HUGE UPDATE Road to Release: Multiplayer, Zombies, Trader, Localization, SaveDeveloper reports release-candidate fixes and a legacy-save migration flow while continuing stability and performance work.
Community reports are never promoted to official facts without corroboration.