Confirmed for this version
Know the constraints before you commit
Official game imageOperational sequence
What to do in a live run
- 01Step 1
Record the symptom and the current build
Write down platform, build, mode and the exact message. For a trophy, keep the challenge condition and match result; for squad formation, keep the invitation sequence. This lets you distinguish a new occurrence from a similar older report.
Field advice - 02Step 2
Compare one squad network condition at a time
The official preview relays player reports of improvement after changing Ethernet versus Wi-Fi, checking NAT type or disabling a VPN. These are reported workarounds, not a universal fix. Change one condition, retry the same invite and record the result before changing another.
Official notes + field adviceS2 - 03Step 3
Get clear of the helicopter edge
When the extraction task permits boarding, move into the usable boarding area and check that your character is aboard. Do not intentionally wait at the side or edge, the position named in the known issue. Keep this as risk reduction rather than a guaranteed workaround.
Official notes + field adviceS1 - 04Step 4
Report the shortest repeatable sequence
Include what you expected, what happened and the few actions leading to it. Use the official support link from the release notes and attach the version and platform context. For a missing PS5 trophy, verify the listed condition before spending another run on the same attempt.
Field advice
Brief 01
What to recheck after a missing achievement
For General Contractor, use all six tools listed by Steam in one match, including the Crowbar. The 1.1 fix closes an incorrect unlock case without a Crowbar. Check the condition and platform first: a correct attempt on PS5 can still be affected by the trophy issue listed at release.
Brief 02
A fix note should match your actual symptom
Resupply fixes cases of medkits failing to be consumed when healing another Responder and perks failing to apply after switching Responders. These statements should not be rewritten as a different healing bug or a promise that all related symptoms are solved. Record what happened in your run before choosing which note applies.
Brief 03
Use the current Normal respawn rule
Plan around the Normal extraction-start respawn added in 1.1. The 1.0.4 dossier remains useful for its earlier Survival changes, but its future-tense Objective statement should not guide a current run. A respawn window also does not protect every later extraction death.
Before commitment
Run checklist
- Capture platform, build and exact symptom.
- Check the task or trophy condition.
- Retry one changed condition at a time.
- Save a short sequence for official support.
Decision support
Situation → action
| Situation | Action | Why |
|---|---|---|
| Cannot form a squad | Compare a network change using the same invitation sequence | The issue is known under some network conditions; reported workarounds vary.S1S2 |
| PS5 condition completed, trophy missing | Keep the match evidence and check the relevant condition before retrying | Some PS5 unlocks were still flagged at the 1.1 release.S1 |
| Boarding during final extraction | Enter the usable boarding area and avoid the edge | The helicopter edge or side is the location named in the published issue.S1 |
FAQ / practical answers
Questions players ask before the next run
Does Normal Objective now have a final respawn?
Resupply 1.1 adds a final respawn window at the start of the extraction sequence on Normal. The 1.0.4 note that Objective support was planned for a later update describes the older state, not the current 1.1 rule.S1S3
Are PS5 trophy failures fixed in the 1.1 notes?
Some PS5 unlock failures remain in the known-issues list at release, with a fix being prepared. Check your challenge condition and preserve the result before repeating a demanding attempt; do not read the PC Steam checklist as a guarantee for every platform.S1
Does disabling a VPN guarantee squad invitations work?
No. The official preview describes it as one player-reported workaround alongside network and NAT changes. Compare one condition at a time and record whether the same invite succeeds before trying another change.S2
Why was I left behind near the helicopter?
The 1.1 notes flag a boarding problem near the helicopter’s edge or sides. Move into the usable boarding area and verify boarding during your run. A matching symptom is useful for a report, but does not establish the cause of every missed extraction.S1
Release notes and official preview reviewed 2026-10-08. Known-issue status is dated to the 1.1 publication; the suggested checks reduce ambiguity and are not guaranteed fixes.
Updates linked to this page
These updates may change the route, value or rule described on this page. Open a patch to see the affected area.