Skip to content

Editorial policy

How our fan guide distinguishes documented facts, player reports and editorial advice, handles automated assistance, and corrects unsupported claims.

Last updated

Editorial identity and responsibility

Our collective byline, Mortal Shell 2 Wiki editorial team, identifies the publisher of the site text. It does not claim employment by Cold Symmetry or Playstack, and it is not a fictional individual author. The site operator is responsible for publication and receives accuracy concerns through our contact page.

Automated assistance is used for drafting and organising material. A fluent draft is not a hands-on test, and neither an automated tool nor a source category establishes that a statement is correct. We do not invent a writer's biography, recorded playtime or review credentials to make a guide appear authoritative.

Different kinds of evidence answer different questions

Developer and publisher announcements can document named features or patch changes. Storefront listings can document the version, platform requirements and price displayed for a particular region and date. A storefront price is not automatically a worldwide console price, and a patch note describing a fix is not proof that every player's problem has disappeared.

Player discussions help identify practical questions and reported symptoms. A dated discussion can show that someone asked about an issue; it cannot, by itself, prove its cause, its prevalence or that a proposed workaround works. We distinguish a player's account from a developer-confirmed change and avoid presenting one report as a measured community-wide trend.

Advice such as learning an attack opening before committing a long combo is an editorial recommendation. It should explain its purpose and limits rather than invent an in-game reward, a hidden modifier or a universal optimal build. If the evidence does not establish an exact value or an unlock condition, the article should say so or omit that claim.

What qualifies as a first-hand test

A first-hand performance or gameplay claim needs a record of what was actually done. For a PC comparison, that means the game build, test date, hardware, driver, display settings, resolution and relevant quality or upscaling choices, plus a repeatable route or workload. A frame-rate number without the test conditions cannot support a general performance promise.

For gameplay results, a useful record identifies the area, Shell, equipment, game build, conditions, number of attempts and what was measured. A single success is not a win-rate dataset. Official screenshots illustrate the game; they do not prove the editorial team captured a benchmark or completed an event. Unless a page supplies an actual test record, do not interpret its recommendations as a claim of personal testing.

Badges, dates and revisions

Guide labels describe editorial content types. They do not indicate developer endorsement, official affiliation or personal testing. Evidence and its limits belong with the relevant claim rather than being implied by a page-wide badge.

“Last updated” records an editorial revision to that page. It does not mean that every sentence was freshly verified or every workaround repeated that day. We do not advance all article dates solely because the site is rebuilt, a footer changes or a calendar day passes. Where an original publication date is not established, we leave it out rather than derive it from the latest edit.

When related short pages are consolidated, the retained guide should address the combined topic coherently and the old route should lead to the relevant section. A longer word count alone is not an improvement. Repetition, unsupported details and paragraphs unrelated to the reader's task should be removed.

Corrections and commercial separation

Send the page URL, disputed wording and relevant evidence to [email protected]. For a bug or changed mechanic, include the platform and build if known. We review whether the claim needs correction, a clearer limit, removal or an explanation that evidence is inconclusive. A report does not require the sender to reveal an account password or upload a full save.

The current site does not run advertising, affiliate checkout links or paid placements. A link to a store is a route to another service, not a promise of support or an endorsement of every claim on that service. If a commercial relationship is introduced, it must be disclosed near the affected content. Payment must not be represented as independent testing or official confirmation.