War in the North Multiplayer Progress Not Saving

Quick answer

A current Steam player reports a red “Saving Disabled” message when joining as a client, with levels, equipment, customisation, and session loot not carrying back to the client’s own game. That is a serious report, but it does not yet tell us whether the behavior is an intended host rule, a launch bug, or platform-specific.

For now, use one consistent host, run a short persistence test, and do not overwrite the last known-good save while investigating.

Status — reported 13–14 August 2026: one detailed community report with replies. No official clarification of guest progression was found in the sources checked.

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

1. Choose one host and write down the host and client platform, store, region, and game version.
2. Photograph or record the client’s level, equipment, skill points, and visible customisation before joining.
3. Start a private session in a low-risk section. Avoid a boss, a chapter transition, or a long achievement run.
4. Cross one checkpoint and earn a small amount of XP or one ordinary item.
5. Exit through the normal menu. Do not force-close the game.
6. Reopen the client’s own game and compare the four progress types above.
7. 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.

The current client report says the player’s own characters were reset, downscaled, or replaced by a host-provided “ghost” state. That wording is a report from one session, not a verified reproduction across platforms. Read the original manual alongside the current report and keep the evidence states separate.

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. There is no verified recovery tool in the sources checked here.

Sources and evidence boundary

• Current client progression report — reported behavior.
• Warner Bros. original online manual — original host/save context.
• Steam feature metadata — co-op and Steam Cloud listings, not a guest-save policy.

Patch 1 fixed part of this (September 15, 2026)

Patch 1 resolves two multiplayer problems that sat behind a lot of the reports on this page:

• Fornost gate: a multiplayer progression blocker where a gate in Fornost failed to release progression-critical enemies after the party respawned — the run could stall permanently. That is fixed.
• Gear desync: several cases where a character’s visible gear state was out of sync between host and client were fixed, along with cinematics aborting and asset loading when characters are swapped at checkpoints.

What Patch 1 still does not answer is the guest-save rule — whether a client keeps levels, equipment and session loot in their own game. Until Aspyr states that explicitly or independent tests reproduce it across more than one setup, this page will not promise that a host swap or reinstall fixes lost progress.