War in the North Legacy Edition Co-op Explained

Quick answer

The Steam listing describes a three-hero action RPG with online co-op, shared/split-screen co-op, Remote Play Together, and single-player support. That gives you several ways to play, but the modes are not interchangeable: local split screen is not the same as online matchmaking, and a feature label is not proof of cross-platform play.

Status — checked 14 August 2026: Steam’s feature set is listed; exact platform pairing and guest persistence remain partial.

Choose the mode before choosing a build

Mode	Best use	Main thing to verify
Solo	Learn chapters and test builds	Whether hero switching and AI positioning behave as expected
Online co-op	Three friends on separate systems	Invite direction, platform pairing, and save ownership
Local split screen	Couch play on one supported setup	Controller assignment, display readability, and performance
Remote Play Together	A Steam-hosted remote couch session	Host connection quality and input ownership

SteamDB records these categories for the Steam product, while the Steam store page is the first-party listing. Neither is a crossplay matrix.

The three roles that make co-op work

The original manual describes a clear party triangle:

• Farin creates a safe front, interrupts pressure, and gives the group room to revive.
• Eradan handles ranged targets, mobility, and evasive repositioning.
• Andriel protects, restores, and controls when the group cannot win a damage race.

The best opening call is not “everyone pick damage.” Decide who will hold enemies, who will remove archers or exposed targets, and who will save a defensive or recovery action for the revive window.

Host rules to agree before starting

The original manual says the host controls story dialogue and recommends the player with the oldest save host. Legacy Edition reports about guest levels and equipment not persisting make a short test even more important.

1. Choose one host for the campaign.
2. Load into a safe area and photograph each player’s level and gear.
3. Cross one checkpoint, earn a small reward, exit normally, and compare the files.
4. Only then commit to a long chapter or achievement run.

If a client sees Saving Disabled, stop treating that lobby as a progression farm. Use multiplayer progress not saving for the evidence checklist.

Local and online are separate questions

Local co-op can succeed while an online session fails. An online lobby can also work on one platform pair while a mixed-platform group cannot connect. Diagnose the exact mode and platform pair; do not write “co-op works” or “co-op is broken” from a single test.

If the group cannot see an invite, follow the multiplayer not working checklist and then the crossplay page. Keep the platform, store, version, host, and result in a small table so the next test changes only one variable.

Sources and evidence boundary

• SteamDB feature metadata — listed modes and controller support.
• Warner Bros. original manual — three-player roles, host dialogue, original save context.
• Current client progression report — reported launch behavior.

The page intentionally treats host/client persistence and crossplay as open questions until current-build evidence resolves them.