War in the North Legacy Edition Coop

The Lord of the Rings: War in the North™ - Legacy Edition supports online co-op and shared or split-screen play for a fellowship of up to three players. Steam also lists Remote Play Together. Start with matching AppID 2523770 builds, decide who controls Eradan, Andriel, and Farin, test one low-risk checkpoint, and learn what persists for host and guests before committing a group to a long campaign chapter.

Choose the cooperative mode deliberately

Online co-op is the right starting point when each player owns Legacy Edition on Steam and will run the game independently. Check the store page or library properties for AppID 2523770. The retired original uses AppID 32800, and Aspyr has not published cross-AppID lobby compatibility. Matching names in a library are not enough; use the product identity.

Shared or split-screen play runs multiple local players through one host system. Connect controllers before starting and confirm which device controls which hero. Steam lists full controller support and recommends a gamepad. Test pause, camera, menu navigation, and character input so one device does not control two participants.

Remote Play Together streams the host’s local cooperative session to remote friends. It can be useful when not every participant runs a separate copy, but it inherits the host’s performance and upload constraints. It is not evidence of console crossplay or mixed-AppID networking.

Create a matching online lobby baseline

Have everyone restart Steam and launch the same public Legacy Edition build. Avoid one participant using an old beta or modified installation. Agree on difficulty and the host’s intended save before inviting. If a player cannot join, compare product AppID and build state before changing routers, ports, or save files.

Run the first connection in a stable hub or early checkpoint. Verify movement, target response, voice or text communication, and normal enemy behavior. A clean lobby baseline makes later disconnects easier to separate from chapter scripts or local performance.

The official listing does not promise cross-platform play. Do not schedule a Windows Steam campaign around PlayStation, Xbox, or Switch players joining the same lobby. Console gyro or network features also should not be transferred into the PC setup unless the current Windows build exposes them.

Assign Eradan, Andriel, and Farin responsibilities

Eradan should watch distant archers, sorcerers, explosive targets, and safe firing lanes. Andriel should monitor fellowship health and use healing or area magic before pressure becomes unrecoverable. Farin should meet close enemies and prevent them from freely reaching the other two. These jobs are simple enough to communicate during a crowded room.

Everyone still revives, avoids damage, and calls threats. Use short location-based calls such as “left archer,” “rear sorcerer,” or “revive Farin.” Do not assume another player understands a specialized skill build from its name. Explain the one action or resource that must be protected.

Agree on loot etiquette after reading the item requirements. A hero-compatible item may be clearly useful to one player, but the group should verify how trading, pickups, and guest inventory behave in the current session. Do not rely on old AppID instructions for an action that might be irreversible.

Test host and guest persistence early

Use a low-value, unmistakable item as the test. Have a guest collect it, cross a checkpoint with the host, exit through the normal menu, and reconnect. Inspect the guest’s inventory, hero state, quest state, and any progression that matters. Repeat once with a host pickup if the ownership model remains unclear.

Steam Cloud availability does not itself define which campaign fields belong to the host or guest. Avoid replacing, copying, or editing saves while synchronization is active. A successful Continue on the host does not prove the guest retained equipment.

Record host, guest, chapter, difficulty, collected item, checkpoint, and result. If a later session behaves differently, this small baseline helps identify whether the cause is connection, campaign state, or a changed public build.

Coordinate revives, quests, and checkpoints

Stay close enough that a downed player can be reached without pulling another group. Before a risky revive, one player should control the dangerous enemy while another performs the action. Calling “reviving” prevents all three people from abandoning pressure at once.

At quest drops and collectible interactions, regroup and verify the state before moving. The seven Lidless Eye scrolls and time-sensitive conversations deserve explicit confirmation. Avoid host travel or guest disconnects while a turn-in or autosave is processing.

For Strength of Our Alliance, current Legacy Edition completion routing describes a kill performed by three human players together. Schedule a full trio, choose an unmistakable target, coordinate contribution, and let each player inspect their Steam achievement state afterward. AI companions should not be assumed to satisfy the human-player condition.

Diagnose connection or input failures safely

For online trouble, confirm AppID 2523770, public branch, host save, difficulty, Steam online status, and whether a fresh hub lobby works. Restart Steam and the game cleanly. Test without changing several network settings at once. Record the exact error and whether the failure happens before lobby entry, during loading, or at a checkpoint.

For split-screen or Remote Play input, disconnect extra devices, reconnect in a known order, and inspect Steam Input assignments. Watch for doubled actions or a keyboard controlling the wrong participant. Change one mapping and retest the menu before returning to combat.

Escalate a repeatable Legacy Edition problem with hardware, Windows version, host or guest role, chapter, connection mode, and steps. The public build has no semantic version label, so provide the test date rather than inventing one. Continue to the Online Coop guide for a focused session checklist.

Cooperative feature sources

• Official Legacy Edition Steam features
• Current Legacy Edition completion route