How This Field Guide Verifies Mortal Shell II Information

The promise

Every important answer is labeled by version, platform, source quality, and last verification date. A page can be useful without pretending to be complete. When reliable evidence stops, our directions stop.

Confidence labels

Label	Meaning
Official	The claim is explicitly stated by the developer, publisher, platform store, or a clearly identified team representative.
Verified	Complete game footage with a usable timestamp, direct editorial testing, or deterministic calculation from verified inputs supports the claim.
Multi-source	Two genuinely independent sources agree on the same scoped fact. A post and the article it links to count as one source, not two.
Community reported	One or more player reports are useful for discovery, but the claim is not independently confirmed.
Unverified	Evidence is missing, contradictory, or too weak to support publication.

What qualifies as verified

An important claim can receive a Verified label when at least one of these conditions is met:

1. A first-party source states it directly.
2. Complete gameplay footage shows it with a clear timestamp.
3. Two independent player sources agree and describe the same version and scope.
4. The result follows deterministically from already verified inputs.

Single anonymous comments never justify save editing, file deletion, configuration changes, exact statistics, or a definitive route.

Page publication states

• Ready: enough evidence exists for the page’s stated scope. It may be indexed unless explicitly noindex.
• Needs verification: the topic is tracked, but no public detail page is generated.
• Blocked: a conflict or missing primary artifact prevents responsible publication.
• Draft: a private content file or template exists; it is excluded from public route generation and search indexing.

Unverified and outdated detail pages must use noindex. Draft articles are not generated as public routes.

Version and platform rules

Patch names are stored per platform. A PC fix does not automatically become an Xbox or PS5 fix. When no numeric build is published, we use the developer’s label and tell readers where to find their exact in-game build string.

Safe issue guidance

Troubleshooting is ordered from low-risk checks to any destructive step. File deletion appears only when a developer source names the exact files. Even then, the guide requires a backup first and explicitly prohibits deleting neighboring saves.

Route rules

A location route needs a reliable starting Beacon, stable landmarks, an arrival confirmation, and version scope. A map marker alone is not a walking route. We do not convert vague source prose into invented “left, right, straight ahead” steps.

Fact and editorial advice

Objective facts use evidence labels. Advice must state its test conditions or supporting reasoning and is visually separated from factual claims. The site does not publish authoritative tier lists or exact DPS rankings without reproducible data.

Source independence and copyright

Competitor sites are discovery and cross-checking tools. We do not copy their prose, page structures, screenshots, maps, databases, or distinctive phrasing. Public access does not grant republication rights. Field Guide text is original and links back to the evidence used.

Corrections

Use the correction link in the footer. Include the page URL, platform, complete build string, the exact sentence you believe is wrong, and a source or reproducible test when available.