Operational priority
Know what optional Permadeath changes in solo and shared co-op runs, what the developer says is preserved, and why every group should agree before launch.
Start with one clear objective: enable the mode only after every player understands that one confirmed permanent co-op death ends the shared run. 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 optional Permadeath, revive-before-confirmed-death behavior, run-save deletion and preservation of settings described by the developer.
The developer was still validating fresh-run reset behavior; release behavior should be rechecked after unlock.
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.
- Agree on the session objective
- Confirm pings and map markers
- Separate personal and shared progression
- Assign transport and supply roles
- Agree on Permadeath before launch
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: Assuming all progress is shared.
- Avoid: Enabling Permadeath without group consent.
- Avoid: Treating an isolated disconnect report as universal.
Decision board
| Signal | Check | Field response |
|---|---|---|
| Goals differ | Which progress is personal? | Coordinate objectives without forcing identical quest states. |
| High-risk trip | Who owns transport, healing and extraction? | Assign roles and use pings before contact. |
| Permadeath considered | Does everyone accept the shared-run consequence? | Leave it off unless the group explicitly agrees. |
Common mistakes
- Assuming all progress is shared
- Enabling Permadeath without group consent
- Treating an isolated disconnect report as universal
Current patch note
The developer was still validating fresh-run reset behavior; release behavior should be rechecked after unlock.
Frequently asked questions
What should I do first for Permadeath Guide?
Start by deciding how you will enable the mode only after every player understands that one confirmed permanent co-op death ends the shared run. Use the checklist before committing scarce supplies or valuable equipment.
Is every exact detail verified for the release build?
The developer was still validating fresh-run reset behavior; release behavior should be rechecked after unlock.
Which guide should I open next?
Continue with /beginner-guide, /factions, /coop based on the next system blocking your current objective.
Sources & verification
- Major Development Update — Infestations, Co-op Pings, Permadeath & MoreDeveloper describes persistent weapon upgrades, Infestations, co-op pings and map markers, and optional shared Permadeath behavior.
- Not Quite Dead — What to Expect in Early AccessDeveloper launch overview covers progression, equipment, U1–U6 upgrades, vehicles, radiation, factions, bunkers, co-op and the map state.
Community reports are never promoted to official facts without corroboration.