Database · shell
Interactive Mortal Shell 2 tools: track quest routes, compare Shells, filter weapons and Seals by moves and effects, and browse upgrade materials.
Interactive utilities for route tracking, Shell comparison, equipment move filtering, and upgrade-material planning. Every tool links back to the routes and guides it depends on. Filter weapons, sidearms, and Seals by moves, effects, special abilities, and guides.
Mortal Shell 2 Tools — Route Checklist, Shell Comparator, Weapons Database is stored as a Shell or build claim from MortalShell2.org. The source snapshot was captured on 2026-08-18T08:19:57+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 Tools — Route Checklist, Shell Comparator, Weapons Database 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.
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 Tools — Route Checklist, Shell Comparator, Weapons Database, 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 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 Tools — Route Checklist, Shell Comparator, Weapons Database 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.
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 Tools — Route Checklist, Shell Comparator, Weapons Database.
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.
