Database · location

Mortal Shell 2 All Beacon Locations

Guide for all Beacon Locations in Mortal Shell 2. Find and cleanse all Beacons for the So Fresh, So Clean trophy & achievement in Mortal Shell II.

Mortal Shell 2 All Beacon Locations

August 17, 2026 by Gage Leave a Comment Mortal Shell 2 contains 49 Beacon Locations. Cleansing all Beacons is required for the trophy/achievement So Fresh, So Clean , along with Bring My Ova Back to Me as all Ova are obtained by cleansing Beacons. Note that the trophy tracker will only track 46 beacons, because only 46 of 49 Beacons can be cleansed. 3 of 49 are already cleansed when you find them (Marrow Keep, Widow’s Overlook, Outskirts of Mammon). None of the Beacons are missable, you can find and cleanse any missed Beacons after the final boss in free-roam before choosing to enter New Game+. Beacons are listed in the order that they appear in the Mether’s Breath (fast travel) menu when at any Beacon. Cleansing the Beacons requires entering them and progressing through a mini dungeon with enemies and sometimes minibosses, then claiming an Ova at the end. The Beacons that appear after each of the 6 main bosses always give the most Ova, containing 26 Ova in each Beacon.

Marrow Keep

#1 – Marrow Keep

Fainweald

#2 – Stonebled Gate #3 – Mushroom Village Gate #4 – Nochtean Gate #5 – Mushroom Village #6 – Outskirts of Nochte #7 – Blackridge Pass #8 – Widow’s Overlook #9 – Gloomshade Grove #10 – Citadel of Penance #11 – One Legged Wolf

Ruins of Mammon

#12 – Outskirts of Mammon #13 – Sester’s Gate #14 – Gate of Infinity #15 – Castigator’s Keep #16 – Abbey Entrance #17 – Abandoned Outpost #18 – Gate of Mammon #19 – The Silent Steps #20 – High Lord’s Courtyard

Glutted Mire

#21 – Seeping Mire #22 – Sunken Village #23 – Magdalena’s Glade

Prisoners’ Domain

#24 – Hangman’s Scaffold #25 – Executioner’s Pulpit #26 – Slumwater Drain #27 – Captive’s End

Sanguine Caverns

#28 – Pulsing Caves #29 – Sanguine Shoreline #30 – Child’s Feeding Grounds

Conquered Temple

#31 – Ovate’s Chamber #32 – Winterglass Lake #33 – Conqueror’s Hoard

Faded Citadel

#34 – Citadel Annex #35 – Citadel Atrium #36 – Scholar-Prince’s Chamber

Withered Shoals

#37 – Nameless Pass #38 – Ossinite Falls #39 – Hexapod’s Burrow

The Unfound Path

#40 – The Hidden Nave #41 – Receiving Hall #42 – Faithful’s Shelter #43 – Brether’s Court #44 – Obsidian Vault #45 – Bridge of Procession #46 – Empty Cradle #47 – Chamber of the Forsaken

Disciple’s Pass

#48 – Disciple’s Grotto #49 – Village Outskirts That’s all of the Beacons in Mortal Shell II. More Mortal Shell 2 Guides: Shell Locations Tarstone Locations Beacon Locations Weapon Locations Sidearm Locations How to Summon Night (Increase Difficulty)

Turn the Beacon list into a route check

Use the numbered source list as a reconciliation sheet rather than as forty-nine isolated trips. Compare the current area in the fast-travel menu with the matching group on this page, then open the map only for the Beacon you are actively checking. Keep a record incomplete until the game confirms the cleanse or shows that the Beacon was already clean when discovered. That distinction matters because the cited guide explains why its total location count and the trophy tracker's cleanse count are different.

Before leaving an area, filter the companion tracker to incomplete exploration and trophy targets. A checked Beacon state belongs to the local companion profile; it is not read from the game and does not prove that an Ova, trophy counter, or fast-travel entry updated. If the current release uses a different menu order or a marker does not match the source description, leave the target open and follow the attributed guide for the captured ordering instead of guessing a replacement coordinate.

Close the collection with evidence still attached

After the regional sweep, compare the remaining names against the source sections and revisit only unresolved groups. Preserve the page's source date when recording a discrepancy, because a patch can change a location or interaction without making the original capture fraudulent. The final completion claim should reflect Beacons you confirmed in the game, while any unresolved count mismatch remains visible as a recheck task. This approach keeps the list useful for routing without presenting a third-party checklist or imported map snapshot as independent verification.

Editorial verification source: open attributed reference · reviewed 2026-08-21

Evidence boundary for Mortal Shell 2 All Beacon Locations

Mortal Shell 2 All Beacon Locations is stored as a location or route point from PowerPyx. The source snapshot was captured on 2026-08-18T08:19:42+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 powerpyx, 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 All Beacon Locations 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 location or route point in the current build

Separate the named place, the entity expected there, the route used to reach it, any encounter condition, and the result. Captured coordinates or directions are a lead until the same release build confirms that the target and access path still match.

Treat Mortal Shell 2 All Beacon Locations as a completeness claim rather than a loose collection of examples. Define the source snapshot, count the named entries it actually supplies, check for duplicates, and label unknown release additions. Do not call the list complete merely because every imported row has a local check; source coverage and player completion are different questions.

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 All Beacon Locations with the companion tools

Use a map marker to investigate one named objective, not to mark every nearby object complete. Update the tracker only after the game confirms the location-specific target.

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 All Beacon Locations 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 All Beacon Locations record

When the current build disagrees with PowerPyx, 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 All Beacon Locations.

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.