Systems are explained directly. Story outcomes and late-game events are omitted unless clearly marked.
Do three things before the opening mission
- 1
Read the platform list
Launch trackers agree on 53 achievements/trophies, but platform presentation and trophy grades differ. Use the list on the platform where you play.
- 2
Lock the difficulty plan
Cross-checked guidance warns that changing difficulty can forfeit difficulty-related progress. Decide whether the first campaign is casual, high-difficulty, or Beskar.
- 3
Create a recovery point
Keep a clean pre-campaign or early-campaign backup where the platform allows it. Never test a launch workaround on the only copy of a long run.
Players are actively asking whether 100% is possible in a single campaign. Treat that as unresolved launch-week demand, not a guaranteed route, until requirements and mutually exclusive states are fully cross-checked.
Campaign and difficulty progress
This phase favors a stable, broad roster over experimental speed. If a named companion dies under permadeath, their bond and side-story opportunities may disappear with them.
Bonds, companions, and roster breadth
Named operators gain bond progress through use and conversation. Rotate companions deliberately, but do not send an underbuilt operator into a mission solely for progress.
After every return
Walk The Den, talk to the named roster, and note who presents new dialogue or a side quest.
Before every deployment
Balance bond targets against injury, mission role, and the chance that the story requires a specific operator.
Between missions
Use custom recruits for Operations and coverage so story companions are not forced into every risk.
Cleanup after the campaign state is safe
| Cleanup cluster | Best time | Risk control |
|---|---|---|
| Class / talent actions | After the roster can respec freely | Record a proven build first. |
| Operations and resources | Between story deployments | Do not strand the main squad without support. |
| Companion bonds | Before a final story lock | Keep relevant named operators alive. |
| Difficulty / Beskar | Dedicated campaign if needed | Do not lower the setting mid-run. |
| Platform-specific trophy cleanup | After comparing the local list | Check sync before deleting saves. |
Use a campaign-state tracker
Difficulty: ________
Permadeath: on / off
Beskar: on / off
Alive: ___ / 7
Bond targets: ________
Open side quests: ________
Pre-campaign backup: □
Pre-finale backup: □
Platform sync checked: □
Unlocked: ___ / 53
Difficulty: ___
Cleanup: ___
What this roadmap does—and does not—claim
Verified: launch trackers list 53; difficulty, permadeath, and Beskar materially affect campaign planning; named operators have bonds and unique story roles.
Not presented as settled: that every achievement is obtainable in one playthrough, that a difficulty change can never be recovered, or that a community workaround safely restores a missed unlock. Those are patch- and platform-sensitive claims.
Why there is no copied trophy dump: the useful decision is when an unlock becomes missable or risky. This page links the live platform lists and keeps the route focused on campaign state rather than duplicating copyrighted database text.
Sources used on this page
Community reports show that a question recurs; they do not prove a cause or fix. Patch-sensitive details were checked on 2026-08-31.