War in the North Legacy Edition vs Original
Compare War in the North Legacy Edition with the original campaign: hero switching, co-op features, Steam Deck support and the latest Patch 2 repairs.
Where Patch 2 changes the Legacy Edition comparison
Patch 2, released November 3, 2026 UTC, changes several practical differences from launch: co-op joining/loading/hub stability, restored ranged headshot hitboxes, steady health-potion fill, companion movement around Secret Stashes, and equipment retained when using respec tokens. It also repairs Scroll 7 quest credit and makes War-Mechanist count fellowship-wide kills.
These are repairs to the Legacy Edition, not a new campaign or a replacement hero system. Use the campaign route for the Fornost, Luin, Grey Mountains and Urgost changes, and the co-op checklist for joining problems. Patch 1 already announced Steam Deck Verified; Patch 2 adds Steam/Deck controller glyphs.
Keep the exact platform and installed patch alongside any original-release advice. The patch does not announce a new crossplay matrix, a universal guest-save policy or fixed performance numbers for the consoles.
Quick answer
Legacy Edition brings the northern campaign to its modern release, with three-hero solo switching and the multiplayer features listed for your platform. Compare the exact edition and patch before applying original-release advice.
The release reporting describes hot-swappable heroes, refined enemy targeting, a revised interface, autosave, and other fixes. Steam metadata also lists online co-op, shared/split-screen co-op, Remote Play Together, Steam Cloud, achievements, and full controller support. The exact implementation can still vary by platform.
Comparison at a glance
| Area | Original reference | Legacy Edition | What this means for players |
|---|---|---|---|
| Story | The Fornost and Agandaûr campaign | The northern campaign | Old chapter routes remain useful starting points |
| Solo control | One hero with companion AI | Release reports describe switching heroes during solo play | Keep all three characters equipped instead of building only the opening hero |
| Combat feel | Original target and lock-on behavior | Use the target-lock controls in the current settings | Do not copy old “the lock-on always behaves this way” advice blindly |
| Interface | Older HUD and menu assumptions | Health, mana, and EXP bars for party members are reported | Re-check screenshots and button prompts on the current platform |
| Saves | Original guide and manual describe campaign saves | New autosave is reported; modern cloud features are listed on Steam | Protect saves during launch-week testing rather than deleting them |
| Co-op | Original console/PC co-op rules | Steam lists online, local split-screen, and Remote Play Together | These listings do not prove console-to-PC crossplay |
| Achievements | Old platform lists and route guides | Steam achievements are listed for Legacy Edition | Verify the live list on the platform where you play |
The release-enhancement details come from contemporary reporting by PC Gamer and GamesRadar+. The current Steam feature list is recorded by SteamDB, which is a third-party metadata tracker rather than the publisher.
What still carries over from the original design
The original online manual remains useful for the underlying systems. Eradan is the mobile ranger with bow, stealth, and evasive options. Andriel is the support and control specialist who can protect the party. Farin is the durable frontline fighter with heavy weapons and a crossbow option.
Weapon eligibility is not universal: all three heroes can use one-handed weapons, while bows belong to Eradan, staves to Andriel, and the largest axe, hammer, and crossbow options to Farin. The manual also describes three distinct skill-tree identities per hero, level-up skill points, respec tokens, party-wide experience from kills, and replayable challenge maps.
That makes old build logic useful as a role map, not as a current numeric spreadsheet. It tells you why a Farin/Andriel/Eradan party works; it does not prove that a 2011 damage value, input prompt, exploit, or save rule is unchanged.
What not to assume
- A Legacy purchase automatically upgrades or connects to an original copy.
- A Steam feature label means PlayStation, Xbox, Nintendo, and every PC store share one matchmaking pool.
- A chapter walkthrough proves that current autosave, co-op persistence, or achievements trigger identically.
- A community post describing a smooth frame rate or a bug fix applies to every hardware revision.
- “Remaster” means every old bug has been removed.
Best way to use old guides
Use the old guide for chapter order, side-quest names, item categories, and achievement route ideas. Before following a mechanical instruction, run a small current-build check:
- Confirm the exact edition, platform, and patch number.
- Test the action in a safe area, ideally before a boss or a long co-op session.
- Record whether the current UI, save state, and character level match the old advice.
- Keep the result as a note for the party instead of silently treating one test as a universal rule.
Sources
Recommended guide route