War in the North Legacy Edition Quests

Quest planning in The Lord of the Rings: War in the North™ - Legacy Edition begins in town and ends only after the reward or conversation is confirmed. Accept optional work before travel, inspect branches before major transitions, track collectibles in the current campaign cycle, and return time-sensitive items before Siege. This hub uses Legacy Edition AppID 2523770 as the authority when older route descriptions and the live quest log differ.

Establish a town routine before travel

Walk through the stable hub before selecting the next destination. Speak to characters with new dialogue, accept side work, turn in completed objectives, and inspect merchants. Open the quest log after each acceptance. A remembered title is not enough; the live log confirms that AppID 2523770 attached the task to this save.

In Bree, current Legacy Edition routing highlights Forewarned is Forearmed, Rowlie’s Gift, and Otto’s Arsenal before Fornost. Use those names as prompts to inspect the town rather than as substitutes for the in-game objective. Check all three heroes’ equipment and supplies while the party is safe.

Take a screenshot or short note before departure. Record destination, unfinished quest, special-item count, and last checkpoint. This creates a useful recovery reference without editing saves or assuming that Steam Cloud can reverse every mistake.

Read objective changes at the moment they occur

When a named enemy falls, inspect the ground and quest state before leaving. Some objectives depend on a dropped item or a follow-up prompt, not merely the kill. When a secret trail or breakable route appears, complete the interaction and confirm its effect rather than walking into the area and assuming discovery credit.

After dialogue, pause long enough for the log and autosave to settle. Do not quit during the transition or force Steam Cloud operations. If the objective did not change, replay the conversation through normal options or return from the nearest checkpoint before trying broad technical changes.

In co-op, have the host and guests inspect their logs when progress matters. The official listing confirms online co-op and Steam Cloud, but it does not document every field of guest quest ownership. A short early test is safer than learning after a long chapter that one player’s state differs.

Separate story travel from optional work

The main objective often points directly toward the next fight or exit. Search nearby branches before committing. In Fornost, the right-side room and underground route at Main Gate, the Battlements sorcerer, and the left fork in Outer Wards reward this habit. Move as a fellowship so an explorer does not trigger a second group outside revive range.

Optional quests can also require returning to the character who assigned them. A completed combat condition is not necessarily a completed quest. At the next hub, check the log, find the named NPC, finish the conversation, and confirm the reward or completion state.

Avoid treating the game as an open-world cleanup map. Campaign transitions can change which conversations and locations remain available. If a route warns about a pre-Siege hand-in, resolve it before starting Siege rather than planning to return after the finale.

Track the Cult of the Lidless Eye across seven regions

The current Legacy Edition completion route identifies seven scroll sources: the Battlements sorcerer in Fornost, a gilded chest in the Coldfells, a sorcerer in the High Moors, a chest in the interior of Mount Gundabad, Wulfrun in Mirkwood’s Shadowed Paths, a dead sorcerer in the Grey Mountains, and a captain in Carn Dûm. Loot and verify each scroll in the live quest state.

Record the count by region instead of only writing “scroll found.” If the total is short later, the regional note narrows the search. Keep the item and quest active; do not sell, discard, or move save files based on an old version’s inventory behavior.

Return all seven to Elrond in Rivendell before Siege according to the current AppID 2523770 route. Complete the conversation and confirm the outcome before traveling onward. The Lidless Eye scroll guide lays out this sequence in a compact table.

Protect conversation-based objectives

Current completion routing calls out Frodo and Glorihirin conversations as opportunities that should not be postponed. When either character becomes available, exhaust the relevant dialogue and verify any achievement or quest response before advancing. Do not assume the character will remain accessible after the next chapter.

Conversation objectives can fail silently if a player leaves early, skips through a transition, or expects another co-op participant’s interaction to count. Let the dialogue finish, then have each player inspect their own state where applicable. Avoid disconnecting while the host is completing a turn-in.

If an expected result is absent, return through the game’s ordinary hub navigation and retry the exact dialogue. Record host or guest role and chapter. A clean reproducible report is more useful to Aspyr support than an unverified save replacement.

Coordinate quests in cooperative sessions

Before loading a chapter, name the active side objectives and who is watching each collectible. Keep the host’s intended campaign save clear, and use the same AppID 2523770 public build and difficulty. A friend launching retired AppID 32800 is not a compatible lobby plan unless Aspyr explicitly documents cross-AppID play.

At an important pickup, regroup before the interaction. Confirm the item or quest update, then cross the checkpoint together. Guests should reconnect after an early low-risk test to see what inventory and progression persist. Steam Cloud availability does not define host-versus-guest ownership by itself.

For a three-person achievement condition, coordinate the action rather than relying on AI. Strength of Our Alliance is described by the current route as a three-human cooperative kill, which belongs in the Coop hub as well as the achievement plan.

Recover when a quest appears stuck

First read the exact objective and inspect the relevant item or counter. Return to the last normal checkpoint, repeat only the triggering interaction, and wait for the state change. Restart Steam and the game cleanly if the problem persists. Do not change compatibility flags, delete files, or import a retired-app save before confirming a simple quest-state issue.

Record game name, AppID 2523770, current chapter, objective wording, host or guest role, the last successful step, and the repeatable failure. Legacy Edition has no public semantic version label, so include the date and public-branch state rather than inventing a patch number.

Use the Walkthrough hub when the route context is the real problem, and the Achievements hub when an objective has a Steam unlock condition beyond the quest completion itself.

Quest route sources

• Current Legacy Edition 100% route
• Official Legacy Edition Steam listing