Locations

This index contains 28 Locations records. It organizes source captures so a player can find a named question, inspect its evidence label, and decide what to verify next. Examples in the current set include All Beacons Locations | Mortal Shell 2; All Dungeons Locations | Mortal Shell 2; All Gate Locations | Mortal Shell 2. A card is an attributed lead, not proof that its conclusion, location, value, or route still matches the release build. Open the dedicated page before acting, then keep the title, summary, source, version, and review date together as one evidence record.

The current Locations set cites Game8, PowerPyx, InteractiveMap.app. Source names describe provenance, not automatic authority, and multiple pages from one publisher do not become independent corroboration merely because their URLs differ. 28 records carry a needs-recheck version state. Use that label to prioritize current-build review; never remove it because a card looks complete or because another page repeats the same captured conclusion.

Start with the exact decision blocking the run: identify an object, reach a place, answer a platform question, prepare a route transition, or reconcile a changed build. Search for that subject and compare the returned hub, type, source, and date. Open one primary record instead of reading every card as a combined guide. If two pages answer different questions, keep both; if they make the same claim from the same source family, do not count them as independent confirmation.

Read list, location, how-to, ranking, and yes-or-no titles according to their intent. A list needs a defined snapshot before it can claim completeness. A location needs a current route confirmation. A how-to needs a start state and observable stop condition. A ranking needs criteria and alternatives. A time-sensitive answer needs the same platform, edition, branch, and date. These checks prevent the Locations index from turning titles into facts the captured body never supplied.

Use the map only for a matched spatial lead, the roadmap only for an ordered route decision, and the tracker only for a supported local target. None of those tools reads the game save, inventory, quest flags, achievements, or storefront entitlements. Confirm the named result in the game before checking it. An imported marker, search result, or completed card can help organize work without becoming evidence that the underlying objective is finished.

When a record disagrees with the current release, retain the attributed source and capture date, record the application build and platform tested, and describe the exact mismatch. Seek a current official or independent source that addresses the same condition and result before editing the conclusion. Close the review with a receipt containing the question, evidence, test, observation, and local state change. This keeps the Locations index useful without hiding unknowns or manufacturing release facts.

Before leaving the Locations index, compare the open work with all 28 visible records and remove only true duplicates from the review queue. Keep two similarly named pages when their intents, platforms, versions, or source conditions differ. Record why a page was selected, deferred, or rejected so another session can resume the same evidence question without rereading every card or mistaking an unreviewed record for a negative result.