War in the North Legacy Edition Co-op Explained
A practical guide to online co-op, local split screen, Remote Play, host responsibilities, three-hero roles, and launch-week persistence risks.
Patch 2: retry joining and loading on the updated build
Patch 2 addresses crashes during matchmaking, loading screens and returns to hubs such as Bree and Fornost. It also repairs guests becoming stuck at map selection and a loading-screen freeze when a player with a slow connection joins. First update every player, close the game normally and recreate the group before repeating the step that failed.
Use a short sequence: form the party, select the map, load into a safe section, cross a checkpoint, then return to town. Record the first step that still fails. The repaired cases give a better starting point than repeating an old router workaround; they do not mean every disconnect has the same cause.
During a revive, the prompt now disappears when another player is already helping the fallen hero. Let one player handle the revive while the others keep the approach clear. Summary statistics are retained on a mid-mission town return, but keep character progress, quest state and inventory checks separate.
Quick answer
Update every player, form a short private session and identify the first failed step: lobby creation, invitation, map selection, loading or a checkpoint transition.
Choose the mode before choosing a build
| Mode | Best use | Main thing to verify |
|---|---|---|
| Solo | Learn chapters and test builds | Whether hero switching and AI positioning behave as expected |
| Online co-op | Three friends on separate systems | Invite direction, platform pairing, and save ownership |
| Local split screen | Couch play on one supported setup | Controller assignment, display readability, and performance |
| Remote Play Together | A Steam-hosted remote couch session | Host connection quality and input ownership |
SteamDB records these categories for the Steam product, while the Steam store page is the first-party listing. Neither is a crossplay matrix.
The three roles that make co-op work
The original manual describes a clear party triangle:
- Farin creates a safe front, interrupts pressure, and gives the group room to revive.
- Eradan handles ranged targets, mobility, and evasive repositioning.
- Andriel protects, restores, and controls when the group cannot win a damage race.
The best opening call is not “everyone pick damage.” Decide who will hold enemies, who will remove archers or exposed targets, and who will save a defensive or recovery action for the revive window.
Host rules to agree before starting
The original manual says the host controls story dialogue and recommends the player with the oldest save host. Legacy Edition reports about guest levels and equipment not persisting make a short test even more important.
- Choose one host for the campaign.
- Load into a safe area and photograph each player’s level and gear.
- Cross one checkpoint, earn a small reward, exit normally, and compare the files.
- Only then commit to a long chapter or achievement run.
If a client sees Saving Disabled, stop treating that lobby as a progression farm. Use multiplayer progress not saving for the save checklist.
Local and online are separate questions
Local co-op can succeed while an online session fails. An online lobby can also work on one platform pair while a mixed-platform group cannot connect. Diagnose the exact mode and platform pair; do not write “co-op works” or “co-op is broken” from a single test.
If the group cannot see an invite, follow the multiplayer not working checklist and then the crossplay page. Keep the platform, store, version, host, and result in a small table so the next test changes only one variable.
Sources
Recommended guide route