War in the North Multiplayer Progress Not Saving
Understand the launch report about guest levels, loot, equipment, and XP not persisting in Legacy Edition multiplayer, then run a safe host-client test.
Patch 2: separate three kinds of lost progress
The November 3 update repairs mission-summary statistics disappearing when returning to town mid-mission. It separately repairs equipment loss from respec tokens and Scroll 7 not counting toward The Cult of the Lidless Eye. Match the symptom to the relevant system before replaying a chapter.
| What is missing | Relevant Patch 2 change | Check next |
|---|---|---|
| Mid-mission totals after a town visit | Summary statistics are retained | Reopen the mission summary |
| Gear after spending a respec token | Specific respec equipment-loss repair | Equipped items and spare inventory |
| The seventh scroll’s quest credit | Scroll 7 counting repair | Current quest counter and hand-in |
| Guest level, loot or a missing save file | A separate persistence problem | Character state in the guest’s own game |
Patch 2 does not describe a new host/guest save-ownership rule or a way to rebuild an empty save. Keep the last usable copy, update before a short checkpoint test and compare story, character, equipment and quest counters independently. Do not interpret a fixed summary screen as proof that every persistence issue has the same repair.
Quick answer
Story checkpoints, character growth, equipment and mission-summary statistics are different states. If one disappears, preserve the last usable save and compare that state before replaying a long section.
For now, use one consistent host, run a short persistence test, and do not overwrite the last known-good save while investigating.
Separate the kinds of progress
The phrase “progress not saving” can describe different systems:
| Progress type | What to compare |
|---|---|
| Story/campaign | Chapter, checkpoint, quest state, host save |
| Character state | Level, skill points, respec changes |
| Equipment | Weapon, armour, elf stones, visual customisation |
| Session rewards | XP, loot, coins, consumables |
| Local/cloud file | Timestamp and file size before and after the session |
Do not assume a host’s campaign save explains a guest’s character reset. Test each row separately and record the result.
Safe 15-minute persistence test
- Choose one host and write down the host and client platform, store, region, and game version.
- Photograph or record the client’s level, equipment, skill points, and visible customisation before joining.
- Start a private session in a low-risk section. Avoid a boss, a chapter transition, or a long achievement run.
- Cross one checkpoint and earn a small amount of XP or one ordinary item.
- Exit through the normal menu. Do not force-close the game.
- Reopen the client’s own game and compare the four progress types above.
- Repeat once with the other player hosting. Stop if a save warning appears.
If the guest sees Saving Disabled, treat the session as a test only. Do not spend rare items or grind levels in that lobby until the behavior is understood.
What the original manual can and cannot tell us
The Warner Bros. manual describes host-controlled story conversations, co-op party roles, and a recommendation to let the player with the oldest save host. It also describes character, weapon, item, skill, and level carry-over between replayed campaigns in the original release. Those details are useful context, but they are not a Legacy Edition save contract.
If a guest sees Saving Disabled, stop the progression run and compare their level, equipped items and quest log after returning to their own game. Keep the last usable copy and record which host and checkpoint produced the warning.
Recovery and escalation
If progress is already missing, preserve every surviving local and cloud copy before trying a workaround. Record the last session that saved correctly, host/client direction, chapter, level, gear, and the first moment the red warning appeared. Send that timeline to Aspyr support.
Sources
Recommended guide route