Mortal Shell II - Interactive Map Beacons

Mortal Shell 2 Interactive Map

View the current world map and use the route checklist for known Beacons, Tarstones, Shell locations, bosses, and key route anchors. Exact map pins will be added once each location is confirmed.

Detailed pins are being charted.

The world map is available now. Exact collectible pins, dungeon entrances, and route markers will be added after each location is matched to a reliable in-game position. Use the route checklist below for known Shells, Beacons, Tarstones, bosses, and route objectives while the full pin layer is prepared. Checked entries stay in this browser so you can keep a route list open while playing.

Tiel, the Acolyte

Near Tiel's corpse in the beta village route.

Emberseed Stone

Inside the dungeon within the Mushroom Village Beacon.

Deadman's Stone

Chest in the Mushroom Village entrance area.

Shattering Stone

Chest in Mushroom Village, near Tiel's corpse.

Trial left of Mushroom Village Gate

Trial to the left of the Mushroom Village Gate; associated with Marksman's Stone.

Volatile Fragment

Defeat The Grand Illusionist within the Mushroom Village Gate Beacon.

Parasitic Stone

Inside the church dungeon, behind the Arbiter of Flesh.

Arbiter's Prize

Reward for defeating the Great Arbiter of Flesh.

Sunken Village Beacon

Beacon reached near the later beta swamp/village route.

Siegebreaker's Stone

Clear the first Sunken Village arena, light three candles, and open the chest.

Corroded Stone

Inside the Sunken Village Beacon.

Magdalena

Sunken Village Swamp encounter; drops Magdalena's Momento in beta notes.

Evidence boundary for Mortal Shell 2 Interactive Map — Beacons, Tarstones, Shells & Bosses

Mortal Shell 2 Interactive Map — Beacons, Tarstones, Shells & Bosses is stored as a Shell or build claim from MortalShell2.org. The source snapshot was captured on 2026-08-18T08:19:56+00:00 and last checked on 2026-08-18; its dataset label is Launch 1.0. Read the summary at the top as the captured conclusion, not as independent gameplay testing by this companion. The single source evidence label describes how many source layers support the record, while needs recheck describes whether its version still needs review. Neither label silently upgrades an unverified detail into current fact.

Keep the record attached to its attributed source URL, source identifier mortalshell2_org, platform scope, and review date. The page may help define a question or route lead even when the normalized source body did not pass the publishing gate. In that case, the missing body must remain missing: do not expand Mortal Shell 2 Interactive Map — Beacons, Tarstones, Shells & Bosses with locations, rewards, statistics, steps, or compatibility claims inferred from the title. A short source conclusion plus a precise verification plan is safer than fabricated completeness.

Verify the Shell or build claim in the current build

Separate Shell identity, unlock path, ability evidence, equipment recommendation, and personal play-style preference. A source-backed acquisition route does not prove an unlisted stat value, universal tier, or compatibility with every weapon and patch.

For Mortal Shell 2 Interactive Map — Beacons, Tarstones, Shells & Bosses, write the exact question being answered before using the captured conclusion. Confirm the named subject and current game state, then record the observed result and any mismatch. Keep facts supplied by the source separate from player preference, route convenience, and details inferred only from the page title.

Before acting, record the application branch and platform actually launched, then compare them with the stored platform list and Launch 1.0 label. Use the smallest test that can confirm the page's central question without spending scarce resources or crossing an irreversible route point. Note the starting state, action, expected result, and observed result. If any one of those is unknown, keep that part unresolved instead of converting absence of evidence into a negative answer.

Use Mortal Shell 2 Interactive Map — Beacons, Tarstones, Shells & Bosses with the companion tools

Use search for the named Shell record, the map for a matched acquisition lead, and the tracker for confirmed ownership. Build selection remains a local decision rather than measured performance proof.

Search results, map favorites, route checks, and tracker completion all belong to this local companion profile. They do not query the game's inventory, quest flags, platform achievements, cloud save, or storefront entitlements. Mark only the exact Mortal Shell 2 Interactive Map — Beacons, Tarstones, Shells & Bosses decision or supported target that the game confirmed. A related result can remain a useful lead without being checked, and an exported JSON profile preserves companion state only; gameplay recovery requires the platform's separate save system.

Reconcile and close the Mortal Shell 2 Interactive Map — Beacons, Tarstones, Shells & Bosses record

When the current build disagrees with MortalShell2.org, preserve both observations. Record the dated source claim, the release build tested, the exact mismatch, and whether the difference affects only a route step or the central conclusion. Look for a current official or independently attributed source before changing the record. A similar noun in patch notes is not enough; the update must address the same subject, condition, and result represented by Mortal Shell 2 Interactive Map — Beacons, Tarstones, Shells & Bosses.

Close the review with a compact receipt: question tested, source and date checked, platform and build used, action performed, observation made, and local target changed. Keep unknown, skipped, failed, and completed states separate. If the page remains marked needs recheck, retain that warning even after one successful personal test; one run can confirm a local outcome without proving universal behavior. This receipt makes later updates auditable and prevents stale guidance from being silently presented as release-wide fact.