The Lord of the Rings: War in the North™ - Legacy Edition is a separate Steam product, not an update applied to the retired 2011 app. Legacy Edition uses AppID 2523770 and is developed and published by Aspyr Media; the old release uses AppID 32800 and was published by Warner Bros. Interactive Entertainment. Buy, install, invite friends, and discuss saves using the AppID as the deciding identity.
What the new Steam listing confirms
The Legacy Edition store description names three immediately useful changes. You can hot-swap among Eradan, Andriel, and Farin; the game supports a fellowship with up to two friends online or in split-screen; and progression still centers on skills, abilities, weapons, armor, and distinct hero roles. The app is a Windows-only 64-bit release with DirectX 12 requirements, Steam achievements, Steam Cloud, full controller support, and Remote Play Together.
Launch coverage based on Aspyr’s release material also describes refined enemy-target locking, an interface that adds party Health, Mana, and EXP bars, autosave, and bug fixes. Treat those as Legacy Edition features, but not as a claim that every historical bug is gone. A general “bug fixes” statement does not establish the status of a specific Mirkwood trigger, multiplayer save issue, boss script, performance problem, or old workaround.
Gyro support mentioned for PlayStation 5 and Nintendo Switch belongs to those platforms. The Steam listing confirms DualSense controller support but does not turn a console gyro feature into a PC guarantee. On Windows, use only the options that appear in the current control menu.
What remains the same enough to recognize
The central campaign is still the northern fellowship’s fight against Agandaûr. Eradan remains the Dúnedain Ranger built around stealth and precise bows and swords; Andriel remains the Elven Loremaster with healing and area magic; Farin remains the durable Dwarven Champion for powerful melee combat. Fornost, Rivendell, Mirkwood, the Grey Mountains, Nordinbad, and Carn Dûm remain part of the route.
Steam lists 46 achievements, matching the established campaign-shaped list. Current Legacy Edition players report the familiar quest, secret, skill, equipment, difficulty, and cooperative objectives. That makes older route names useful as a map for questions, but the new app must decide the answer whenever behavior can depend on save format, hot-swap, network code, UI, item packaging, or a fixed trigger.
Ownership is not an upgrade entitlement
Owning AppID 32800 does not place AppID 2523770 in the same license automatically. The current store sells Legacy Edition as its own base game and package. Steam has no general rule that an owner of a retired app receives a separately published replacement, and the Legacy Edition page does not announce a free entitlement or owner discount.
Before buying, open the signed-in Steam page and inspect the purchase button. That is the reliable account-specific answer. Do not purchase a third-party key advertised for “War in the North” without seeing which AppID it activates. A key for the retired original is not interchangeable with a license for the active Legacy Edition.
Multiplayer compatibility needs matching products
Legacy Edition advertises online co-op, but Aspyr has not published cross-AppID compatibility with 32800. Separate Steam applications normally have distinct matchmaking, build, and ownership contexts. The safe setup is three players launching 2523770 on the same public build. If one friend owns only 32800, treat that group as incompatible until the games themselves or an Aspyr statement demonstrate otherwise.
Cross-platform play is also absent from the Steam feature list. The existence of PlayStation, Xbox, or Switch versions does not establish mixed-platform lobbies. Do not confuse Remote Play Together with crossplay: Remote Play streams a host’s local cooperative session through Steam; it does not connect independent console builds.
Saves and progression should start inside 2523770
No official migration path from the retired original app has been announced. Avoid copying an old save into a guessed Legacy Edition directory. File names and campaign structure may look familiar while serialization, account identifiers, Cloud synchronization, or checkpoint state differs. A failed import can be harder to diagnose after Steam Cloud uploads the changed files.
Create a new Legacy Edition save, reach a checkpoint, close the game normally, and confirm that Continue returns to the expected state. If Aspyr later publishes an import utility or documented directory, follow that procedure with backups and Cloud synchronization paused only as directed. Until then, an old save is archival data rather than a supported starting point.
Co-op progress deserves a separate test even with a new save. Have a guest collect an item, cross a checkpoint, disconnect normally, and return. Record what persists for the host and guest before committing to a full chapter. New autosave does not by itself define ownership of guest equipment or character progression.
Old DLC and bonus equipment are outside the confirmed package
The original AppID had Human Pack, Elf Pack, Dwarf Pack, Film Pack, and Orc Champion Sword DLC applications. They are typed as DLC for 32800, not 2523770. The Legacy Edition store API lists no DLC for the target app at launch. Therefore, an old DLC license does not prove transfer, and a familiar item appearing in the game does not prove that the corresponding old DLC app is bundled.
This distinction does not change the 46-achievement plan: the current Steam list contains the base campaign objectives, and the old equipment packs did not add a second achievement list. It does change gear documentation. Any bonus-looking weapon or armor should be identified from the Legacy Edition inventory and acquisition path rather than assigned an old DLC source by name alone.
A practical decision before buying or reinstalling
Choose Legacy Edition when you want the active store product, current Windows baseline, current online population, hot-swap flow, revised interface, autosave, and Aspyr support path. Keep the original installed only when you deliberately want the retired build, an archived save, or a historical comparison. Do not overwrite one installation’s files with the other.
For a co-op purchase, confirm every player’s product page shows AppID 2523770. For an old owner, assume a fresh license and fresh campaign unless the account or Aspyr explicitly says otherwise. For controller and performance questions, use the Tech hub because requirements and compatibility observations belong to the new executable. For the first campaign, return to the Guides hub and build a route around Legacy Edition behavior.