Online co-op in The Lord of the Rings: War in the North™ - Legacy Edition supports a host and up to two friends. Every independent Steam player should launch AppID 2523770 on the same public build. Establish a clean lobby, test one item and checkpoint for persistence, then divide Eradan, Andriel, and Farin duties before starting a long chapter.
Verify all three copies before inviting
Open the Steam library or store identity and confirm Legacy Edition AppID 2523770. The original 2011 Steam app is 32800 and is not a documented cross-version multiplayer partner. If one person owns only the retired app, do not troubleshoot the network as though the products were already compatible.
Use the same public branch. Let Steam finish ordinary updates and restart the client if one machine has stale state. Legacy Edition does not publish a semantic version number, so compare branch and update completion rather than inventing a version label.
Agree on who hosts, which campaign save will load, and the difficulty. A player joining the wrong cycle may see equipment, quests, or enemy behavior different from the planned session. Keep mods and manual file changes out of the baseline.
Run a low-risk persistence trial
Meet in an early or stable area and have one guest pick up a recognizable low-value item. Cross a normal checkpoint, exit through the game menu, allow Steam synchronization to finish, and reconnect. The guest should inspect inventory, hero progression, quest state, and any other field the group expects to retain.
Have the host verify the campaign state independently. Steam Cloud being listed does not explain every host and guest ownership rule. A controlled trial turns an undocumented assumption into evidence for this group without risking important gear.
Do not copy save folders between accounts or AppIDs. Do not pause or force Cloud synchronization while the game is writing. If the result is unexpected, repeat once from a fresh low-risk checkpoint and record the roles and sequence.
Coordinate the fellowship during combat
Assign Eradan to distant priority targets, Andriel to healing and area support, and Farin to front-line contact. Call threats by location and type. When a player is downed, name who controls the enemy and who revives so the entire party does not abandon its position.
Stay within a recoverable distance. A fast player who enters another room can create separate encounters and place the revive outside safe reach. Wait before doors, drops, quest interactions, and travel prompts until everyone is present.
Discuss loot after reading hero and attribute requirements. If the game’s sharing or trading behavior is unclear, test with a low-value item. Do not make an irreversible transfer based on instructions for AppID 32800.
Protect collectible and achievement credit
At a Lidless Eye scroll, named quest drop, or important conversation, secure the area and let the interaction finish. Each player should inspect the relevant state before the host travels. Avoid disconnecting during quest turn-ins or autosave.
For Strength of Our Alliance, current AppID 2523770 routing specifies a three-human coordinated kill. Use a full trio, select an unmistakable target, and have all three contribute according to the live Steam wording. Then check each account; host credit does not prove guest credit.
If an achievement does not unlock for one member, repeat cleanly before changing anything. Record target, character, host role, connection stability, and which accounts received credit. Keep AI companions outside the assumption for a human-player condition.
Isolate lobby, loading, and disconnect problems
If an invite fails, confirm Steam online state, product AppID, public branch, and that the host can create a fresh lobby in a stable hub. If loading fails, try the same players with an early save to distinguish campaign state from connection state. If a disconnect occurs mid-chapter, note the last checkpoint and whether only one guest or the entire lobby dropped.
Restart Steam and the game before changing router or firewall settings. Change one variable per retest. Do not disable broad security controls or expose ports without an official requirement. A reproducible failure at the same transition points toward a different cause than random network loss.
When contacting Aspyr, provide Windows version, connection type, host or guest role, chapter, public-branch date, exact error, and repeatable steps. This is more actionable than a generic “co-op broken” report.
End a session cleanly
Finish at a known checkpoint, inspect quest and inventory state, and have the host exit normally. Guests should also leave through the intended menu instead of terminating the process. Allow Steam Cloud to finish before shutting down or switching accounts.
At the next session, verify Continue and guest state before beginning another long chapter. Keep the prior checkpoint record until the group confirms persistence. This habit is especially valuable before Siege, the final approach, or a high-difficulty cycle.
Return to the Coop hub for split-screen and Remote Play distinctions, or the Achievement guide when planning the three-human requirement alongside campaign completion.