Mortal Shell II Interactive Map — Every Marker & Location

The source describes its own marker count, category set, interface, and Open Beta update status. Those figures establish what that third-party map claimed at capture time; they are not an official total for the released game and do not need to match this companion's cleaned marker model. Different deduplication rules, categories, and source dates can produce different totals without proving either interface complete.

Use a marker as a navigation lead. Search for one named objective, compare its category and surrounding description, then confirm the result in the game before changing completion state. A local favorite, collected flag, or share link belongs to the map tool and does not query the game save. When the source marker and current build disagree, preserve the link and capture date instead of guessing a replacement coordinate.

Review rights and provenance before reusing map material. This companion links to the attributed source and maintains its own generated paths; it does not claim ownership of the third-party interface or convert its marketing statements into verified gameplay. The useful SEO record explains what the source offers, where its version boundary sits, and which user decision still requires direct confirmation.

If a marker is valuable but unconfirmed, save the source URL and category instead of copying its coordinates into a current guide. The review queue can then test the lead without publishing an unsupported release location.

Remove the recheck label only after that release-location test succeeds.

Record the tested release build beside the marker before closing the review.

Mortal Shell II Interactive Map — Every Marker & Location is stored as a location or route point from InteractiveMap.app. The source snapshot was captured on 2026-08-18T08:20:03+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 interactive_map, 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 II Interactive Map — Every Marker & Location 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 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.

For Mortal Shell II Interactive Map — Every Marker & Location, 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 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 II Interactive Map — Every Marker & Location 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 InteractiveMap.app, 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 II Interactive Map — Every Marker & Location.

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.