Operational priority
Separate developer-fixed items, acknowledged behavior, community reports, monitoring and safe workarounds with source dates instead of inflating isolated posts into universal bugs.
Start with one clear objective: act only on source-backed status labels and match any workaround to the exact symptom and build context. 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 developer-reported fixes for Trader multiplayer, Prison collision, Faction markers, Infestations, zombies and legacy-save migration.
Movement, controller, graphics and isolated load reports remain COMMUNITY REPORTED or MONITORING unless official evidence changes their status.
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
Movement, controller, graphics and isolated load reports remain COMMUNITY REPORTED or MONITORING unless official evidence changes their status.
Frequently asked questions
What should I do first for Known Issues & Workarounds?
Start by deciding how you will act only on source-backed status labels and match any workaround to the exact symptom and build context. Use the checklist before committing scarce supplies or valuable equipment.
Is every exact detail verified for the release build?
Movement, controller, graphics and isolated load reports remain COMMUNITY REPORTED or MONITORING unless official evidence changes their status.
Which guide should I open next?
Continue with /save-file-location, /coop, /prison based on the next system blocking your current objective.
Sources & verification
- Development Update: New Trader UI, Multiplayer Fixes, Infestations & MoreDeveloper reports trader multiplayer, Infestation, zombie, Prison collision and Faction Safe Zone marker fixes.
- 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.
- Not Quite Dead General DiscussionsCurrent discussion titles include isolated movement, controller, graphics, invisible-barrier and launch/load reports; none are promoted to universal bugs.
Community reports are never promoted to official facts without corroboration.