War in the North Legacy Edition Guides

The Lord of the Rings: War in the North™ - Legacy Edition is a separate Steam base game under AppID 2523770. Begin by choosing the hero whose job you understand, deciding whether the first campaign will be solo or cooperative, and keeping the 2011 AppID 32800 outside your save, DLC, and multiplayer assumptions. Legacy Edition supports instant switching among Eradan, Andriel, and Farin in solo play, while the Steam listing also confirms online and split-screen co-op for a fellowship of up to three players.

Set the right expectations before the first campaign

War in the North is a party action RPG, not a lone-character adventure with optional companions attached afterward. All three heroes travel together, revive one another, collect class-relevant equipment, and solve different tactical problems. In solo play you control one hero while the others are AI companions, and Legacy Edition lets you hot-swap rather than returning to the main menu. In co-op, agree on roles before loading a long chapter so healing, ranged pressure, and close control are all covered.

The campaign follows a northern fellowship opposing Agandaûr while the Ring-bearer’s journey unfolds elsewhere. The first major operation leads through Bree and the ruins of Fornost. Later chapters move through the Barrow-downs, Ettenmoors, Mount Gundabad, Mirkwood, the Grey Mountains, Nordinbad, and Carn Dûm. That structure matters because quests, secrets, scrolls, counters, and achievement conditions can be tied to a campaign cycle rather than a free-roaming endgame.

Choose a difficulty that leaves enough room to read attacks, revive companions, and learn the inventory. Current Legacy Edition community routes describe Normal, Heroic, and Legendary as a progression sequence on one save, but the difficulty unlock and carryover rules deserve a dedicated same-build confirmation before you plan a perfect run around them. For a first campaign, Normal is the safest planning baseline when achievements matter; Easy should not be chosen on the assumption that every completion milestone will unlock.

Build a dependable first-hour routine

Open the graphics, audio, controls, and gameplay menus before entering combat. Confirm the displayed bindings, camera speed, target-lock behavior, subtitle settings, and controller prompts. The Steam build lists full controller support and recommends a gamepad, but keyboard and mouse remain a valid choice if the prompts and camera feel correct. Change one setting at a time so a control problem is not confused with a frame-rate problem.

During the first encounters, practice a short loop: identify the most dangerous ranged or spell-casting enemy, keep the party inside your camera, avoid committing to long attacks when another enemy is active, and revive promptly. Use hot-swap to move to the hero whose kit answers the immediate problem. Eradan can remove distant pressure, Andriel can stabilize the group, and Farin can occupy clustered melee enemies. This is more reliable than forcing every room with one favorite character.

Open every equipment comparison with the hero requirement in mind. A larger displayed number is useless when the intended hero cannot equip the item or lacks the required attribute. Keep one functional weapon for each hero, retain elf-stones until their effect and socket are clear, and compare armor by both protection and the attribute needed to wear it. Named armor sets should be stored carefully because the Well-arrayed achievement requires a complete matching set worn by one compatible hero.

Route chapters without losing optional work

Treat towns as preparation checkpoints. Speak to named NPCs, accept available work, sell only items you are sure you do not need, inspect merchants, and read the quest log before choosing the next destination. Several player objectives are easier when handled in the chapter where they appear. Returning later may be possible in some cases, but it should not be the plan for a missable conversation or a collectible that precedes a major transition.

Use a compact campaign note with four fields: destination, unfinished quest, collectible count, and the last safe travel hub. Record only values the game exposes. For example, the current achievement route tracks secrets, Cult of the Lidless Eye scrolls, headshots, Beleram summons, crafted potions, quests, war-machine kills, and total kills inside the active campaign cycle. A screenshot of Gameplay Stats at each town is more useful than trying to remember which counter advanced.

Fornost is the first place to establish the habit. Prepare in Bree, clear Main Gate side rooms before following the obvious objective, inspect paths revealed by Eradan, use mounted war machines when their lanes are active, and loot the Battlements sorcerer who begins the Lidless Eye investigation. The Fornost walkthrough gives a spoiler-controlled route through those decisions.

Choose solo, online, or split-screen deliberately

The official Steam listing confirms single-player, multiplayer, online co-op, shared or split-screen co-op, and Remote Play Together. It also says you can play with up to two friends. For online sessions, every participant should own and launch AppID 2523770, use the same public build, and choose the same difficulty before joining. Compatibility with retired AppID 32800 has not been documented, so do not buy or schedule a session around cross-AppID play.

Before a long cooperative chapter, run a short save test. Join, collect an unmistakable low-value item, cross a checkpoint, leave normally, and inspect each player’s state after reconnecting. Steam Cloud being available does not prove that every guest progression field follows the guest rather than the host. Keep backup expectations modest and avoid experimenting with file replacement while Steam is synchronizing.

For couch play or Remote Play Together, connect and assign input devices before loading the campaign. Watch for doubled input, two controllers mapped to one player, or keyboard focus entering the wrong Steam overlay. The Coop hub separates online, local, and save-safety decisions without claiming unconfirmed cross-platform support.

Plan hero growth instead of chasing one universal build

Skills, attributes, and equipment work together. First meet the attribute requirement for the armor and weapon you actually use. Then invest toward the hero’s job: precision and ranged output for Eradan, support and area control for Andriel, or strength and durability for Farin. Do not copy an endgame point spread into an early character who lacks its gear, tier access, or difficulty context.

A useful build must name the campaign point, difficulty, weapon family, armor requirement, important skills, and failure condition. If a ranged build repeatedly leaves allies downed, it needs faster recovery or more attention to positioning. If a durable build survives but cannot stop archers and sappers, the party needs ranged or area coverage. The Builds hub starts with role-specific frameworks, while the Heroes hub explains what each character contributes before points are assigned.

Keep Legacy Edition boundaries visible

Legacy Edition is not a branch, DLC, or package for the retired original Steam app. The product has a new AppID, a new Aspyr listing, a Windows 64-bit requirement, DirectX 12, modern UI work, autosave, refined target locking, and hot-swapping described in launch material. The story, locations, three heroes, and achievement list draw from the earlier game, but shared names do not prove save import, lobby compatibility, entitlement transfer, or inclusion of the original app’s five DLC entries.

Use the Legacy Edition differences guide before buying a second copy for an old owner or organizing a mixed-version group. It separates confirmed changes from ownership and compatibility questions that Aspyr has not answered. Keep console-specific features, especially gyro controls, out of a Steam Windows setup unless the PC build itself exposes them.

Recover from a bad start without compounding it

If combat feels chaotic, lower the number of simultaneous decisions. Lock the camera on a priority enemy, shorten attack strings, and use the hero switch only after the controlled character is safe. If the party is under-geared, revisit merchants and recent replayable areas before spending every coin on a single item. If an achievement counter looks wrong, compare Gameplay Stats before and after one reproducible action instead of grinding blindly.

For crashes, input loss, online disconnects, or progress that does not persist, record AppID 2523770, the visible build state, Windows version, hardware or controller, host or guest role, chapter, and the last checkpoint. Restart Steam and the game cleanly before changing files. Aspyr’s support portal is the correct escalation point when a problem survives a reversible setup test.

Official and current references

• Steam store for AppID 2523770
• Aspyr support
• Current Legacy Edition 100% route