War in the North Legacy Multiplayer Not Working
A reversible launch-week checklist for failed lobbies, missing invites, connection errors, and unstable Legacy Edition co-op sessions on each platform.
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.
Find the failure stage
| Failure stage | First test | What the result tells you |
|---|---|---|
| No multiplayer option | Confirm the exact Legacy Edition product and update | You may be in the wrong application or an incomplete install |
| Lobby creates but friend sees nothing | Reverse the invite direction | Distinguishes host/session state from the joining account |
| Friend sees lobby but cannot join | Test same-platform, same-store pair | Separates a platform boundary from a general session failure |
| Join succeeds, then drops | Cross one checkpoint in a private lobby | Identifies session stability rather than discovery |
| Co-op works but progress disappears | Run the short persistence test | Move to the dedicated progress page instead of repeating network resets |
Reversible checklist
- Confirm the build. Every player should launch The Lord of the Rings: War in the North — Legacy Edition, not the old 2011 Steam application or a shortcut pointing at it.
- Check service status. Look at the platform’s own network status page and sign in again if the service reports a problem.
- Close the game fully. End the process, relaunch, and recreate a private lobby. Do not stack a reinstall or save deletion on top of this test.
- Swap host and invite direction. Have the other player host the same short test. Record which direction worked.
- Use one controlled network comparison. A phone hotspot or a known-good connection can show whether the home network is the leading variable. Stop after one comparison and restore the original setup.
- Test a short session. Load into a safe area, cross one checkpoint, and exit normally. This catches a drop that happens only after the lobby starts.
- Capture evidence. Save the exact error text, platform, store, region, version, host, time, and whether the lobby was public or private.
Avoid these early “fixes”
Do not delete local or cloud saves, disable console security, forward ports, or rebuild a database because a forum comment suggested it. Those actions can destroy recovery evidence and still do not prove the cause. Change one variable at a time and keep the last known-good configuration.
If a same-platform test works but a mixed-platform pair fails, read the crossplay guide. If a player can join but loses levels or gear, use multiplayer progress not saving.
Sources
Recommended guide route