Read the location ledger as a set of labels

A location record answers a different question from a chapter record. The campaign table tells you which guide routes were observed and keeps a missing chapter boundary visible. The warfront table tells you which named places are present in the bound source set. Those two dimensions should be read together, not collapsed into a single guessed order. If a walkthrough uses a place as a heading, the matching row here gives you a stable spelling and a source note for comparison.

Bree, Rivendell, the Misty Mountains, Mirkwood, Gundabad and Carn Dûm come from the official Touchpoints description captured for the project. That is a useful first-party place-name record, but it is not a complete catalogue of every encounter or location. Fornost is included as a separate detail page because it is an explicit planned page in the content plan and a location record with its own fields. The difference in page depth is intentional and source-bound.

The player-facing benefit is quick orientation. A new player can scan the table before opening a guide, a returning player can check whether two spellings refer to the same captured label, and a co-op group can use the rows as a shared place-name vocabulary. When a source makes a broader story claim, follow its link and keep the page’s boundary note in mind.

Seven named fronts

Bree is a place-name label in the official video description and a useful lookup for a player placing the northern story. Rivendell is a recognisable fellowship-facing name. The Misty Mountains and Mirkwood add mountain and woodland settings to the same vocabulary. These labels are not accompanied by a fabricated difficulty scale here; the record’s value is that it lets a player identify the named front in a guide or video description.

Gundabad and Carn Dûm provide additional northern names in the same official description. They are especially useful when a search result uses only a place name and drops the game title. The row links to the campaign and the broader foe record, so the player can move from setting to enemy lookup without relying on an unsourced summary. The exact enemy list is kept on Foes and Bosses, where its eight structured entries can be read together.

Fornost has the dedicated detail page. That page repeats the captured fields, source time and current still treatment, while this table remains the hub for the complete seven-name set. Giving Fornost a detail page does not imply that the other six locations are less important; it reflects the planned page set and gives the location family one concrete detail example.

Turn a place name into a player task

When a player reaches a location in a walkthrough, the first useful action is to confirm the name, not to assume the guide’s whole context. Use the table row to check the captured spelling, then use the Campaign page to compare any chapter number. If the guide is historical, move to Editions and Platforms and confirm whether it is speaking about the 2011 PC release or the current 2026 Legacy Edition. This small check prevents a common search problem: a useful old route being mistaken for a current product statement.

The combat guide can sit beside the location table when the question is tactical. It explains how to read War Cry, Sanctuary, Evasion and elfstones in the source boundary. The Foes and Bosses page can sit beside it when an enemy name appears in a location heading. The page architecture keeps place, system and enemy as separate ledgers because those are separate lookup questions for a player.

The official video stills on the media page add a visual memory aid without replacing the table. Each still has a manifest identity and a caption, and the video facades wait for a deliberate click. On a phone, the location names and the direct links remain above the media treatment. The image is useful context; the structured row is the durable reference.

Source boundary and expansion

The current location set is complete for the bound inventory because it contains the seven planned names, not because it claims to list every place that could appear in the game. That distinction gives the page a safe expansion point. If a future sealed capture adds a named front, it can be added with its own source and timestamp. Until then, adding an invented eighth place would make the table look richer while weakening its provenance.

The missing chapter seven boundary on the campaign page is a useful reminder here. A location list and a chapter list can have different edges. The player should be able to see both edges rather than receiving a smooth narrative that hides where the records stop. The cross-links make that comparison quick and keep the external guide link in its proper role as observed navigation.

For an initial lookup, search Bree or Rivendell as a name check, then choose the campaign or Fellowship page. For a return visit, use the location row as a hub into Fornost, Foes and Bosses or the stills gallery. The page is built to shorten those transitions without claiming a guide authority that the source set does not provide.