Skip to content

Beacons: separate cleansing, travel and an unavailable upgrade

Check Mortal Shell II beacon progress, distinguish cleansing from travel and upgrade failures, and investigate a missing checkpoint without an invented location map.

By Mortal Shell 2 Wiki editorial team · Last updated

Mortal Shell II Beacons: Cleansing, Travel and Missing Progress

A beacon can be involved in three different problems: establishing a checkpoint, completing its cleansing encounter, and using a menu feature after a progression unlock. Identify which action is failing before repeating a dungeon or spending materials. This guide separates those actions rather than claiming a personally recorded route to every beacon.

A hooded villager among barrels in Mortal Shell II

What the 49 and 46 numbers describe

A Steam player discussion reports 49 beacons overall and distinguishes 46 that require cleansing from three additional entries. That distinction explains why a world total and a cleansing target can differ. It is a community description, not a developer-published coordinate list. It does not independently establish every location name, reward or the conditions recorded by your current achievement progress.

Use those numbers as context for a progress check. Do not count a beacon merely because you saw its structure from a distance. Compare the location you actually visited with the completion or interaction state displayed by the game. A matching personal count is useful evidence, but is not proof that every required action was recorded.

This reference does not assign unverified coordinates or guarantee that every checkpoint remains available after every story choice. A route compiled for another campaign state may not explain your current map. Preserve the save and identify the unmet requirement before making another major progression choice.

Separate arrival from cleansing

At a new beacon, first check whether you can interact normally. A hostile approach, an interaction prompt, an entered encounter and a completed encounter are different states. Record the location name and the exact state you reach. A report that an exit did not appear after an encounter is more useful than simply saying the beacon is broken.

If entering places you in a separate encounter, complete the objective actually shown there. Do not substitute a remembered route from another beacon or assume that defeating the largest enemy completes every requirement. Inspect the result and available exit before deciding that the checkpoint has been cleansed.

After returning, inspect the menu and map again. The question is whether the relevant entry changed, not whether the scene looked brighter. If you received completion feedback, retain a screenshot. That record helps distinguish an unfinished encounter from a failure to display or preserve its completion.

Travel access is a separate progression check

Mether’s Breath and beacon travel are related progression systems. Access to a checkpoint alone does not establish that every travel function has unlocked. Inspect your current ability description and available menu before treating a missing destination as an interface defect.

If travel is available but you cannot find a location, compare the list with places you actually completed. A familiar region name is not necessarily the specific beacon you intended to reach. Confirm the displayed destination rather than selecting a similar label and assuming the journey was wrong.

Read confirmation prompts before travelling. If the game warns about consequences, this guide does not override that warning with a promise of a reversible test. Cancel normally when you only need to check menu responsiveness. Do not confirm a consequential transition to investigate a highlight or input issue.

An unavailable upgrade is another problem

An unavailable Mether’s Pulse row does not prove that a beacon was never cleansed. Inspect the requirement beside the action and the inventory count in the same save. An item with a similar name may support a different upgrade; another displayed balance may refer to a different currency.

If the requirement appears satisfied, note whether the row highlights, whether confirmation responds and whether other entries work. Use the Pulse upgrade selection guide for that particular symptom. It describes controlled comparisons without promising that a reload, another beacon or additional farming universally repairs the report.

Do not spend rare materials on an unrelated purchase merely to refresh the menu. A change elsewhere can obscure the original conditions without repairing your intended action. Preserve the owned count, required count, platform and input device so another person can understand the same starting state.

Build a missing-progress log

Record each exact beacon label, whether you entered its encounter, whether completion feedback appeared and whether the expected state remained after loading. Give travel availability its own column. Otherwise it is easy to count one interaction twice or treat a travel unlock as evidence of cleansing.

Prioritize uncertain entries rather than replaying the world from memory. A location where you remember arriving but not finishing deserves attention before one with a clear completion record. If a path is inaccessible, record its visible obstacle. Do not invent the missing ability or assume that the next boss opens it without information establishing that connection.

For a difficult Mammon return, use the second-visit survival plan. Preparation and checkpoint completion are related, but a dangerous return does not prove a hidden enemy-scaling formula. Keep the observed route problem separate from speculation about its cause.

Preserve the save when completion does not persist

Compare the same location before and after one normal load, allowing any save indication to finish. Repeatedly closing during a save, editing undocumented values or resolving a cloud conflict by guesswork can damage the progress you are investigating.

A useful report states the build, location, action, completion feedback and result after loading. Separate observations from proposed causes. If no reliable repair is established, retain the evidence rather than starting New Game Plus as an experiment. This guide makes no guarantee that a new cycle restores missing completion. A small, reproducible description is more useful than replaying uncertain routes until the original conditions are lost.