Next action
Start with the two prologue missables
The route opens with Marigold's crown and the Tar Golem check because neither returns in NG+.
Source-backed release data, still marked for recheck.
100% completion · local-first
Finish Mortal Shell II with one 100% completion route.
A version-aware route, interactive map and linked checklists for story, trophies, collectibles and exploration.
Four tracks
Storynot started
Trophiesnot started
Collectiblesnot started
Explorationnot started
145source-indexed guides
1,893cleaned map markers
66map categories
4linked completion tracks
One record, four views
Four completion lines, counted once.
A boss can matter to story, trophies and exploration, but it still contributes one target to overall progress. Every surface reads the same local state.
Open tracker
Default 100% routeThe dangerous checks come first.
Choose your goal
One safe order, focused by what you care about.
Start from the same low-rework route, then filter it for Platinum, collectibles or exploration. There is no free-form editor and no duplicate progress tree.
- Tutorial missables appear before everything else.
- Every mappable target deep-links to the same marker state.
- NG+ copies only known carryover and explains every reset.
Database
Every captured guide, with its source attached.
Evidence boundary
What this completion companion can prove
The site can prove which source was captured for a record, when that capture entered the dataset, which local target state you selected, and how supported targets connect across the roadmap, map, tracker, and trophy views. It cannot read a Mortal Shell II save, inspect inventory, confirm a platform achievement, or establish that an old coordinate still matches the current release. A local check therefore means “confirmed for this companion profile,” not “automatically verified by the game.”
Read the evidence strip before acting on a guide. Official identifies first-party material; cross-checked means more than one captured source supports the conclusion; single-source means the statement remains attributable to one source. Records marked “Needs recheck” stay visible for investigation but should not be converted into current fact without comparing the source date and the build you are playing. When the game disagrees, leave the target open and preserve the source link for review.
Progress stays in browser storage unless you export a companion profile. That JSON export restores the site's route and target states; it is not a game-save backup. Use the platform's own save tools separately before missable encounters or cycle transitions. The distinction keeps recovery predictable and prevents a checklist file from being described as protection for gameplay data it never contains.
Start with the roadmap when order matters, use the walkthrough for step-level work, open the map only for a spatial question, and use the database to inspect the attributed record behind a conclusion. The tracker is the final reconciliation view because it de-duplicates shared objectives across story, trophies, collectibles, and exploration. This tool order keeps the completion claim limited to decisions that can be traced and reviewed.
Search is the fallback when a name is known but its route is not. It indexes published guides and custom map records, then sends the reader back to the owning page; a result is a discovery link, not a new source or an automatic completion signal.