Mortal Shell II - Wiki Verified Open Beta

Mortal Shell 2 Wiki

Use this hub for information that can be checked against the public build, the official game site, Steam, or Playstack announcements. We removed standalone pages built only from names, icons, or incomplete fields. Install the official Steam demo and understand exactly which part of the game is playable. Separate the launch rewards and prologue-skip unlock from the inventory and currency reset. A task-first route through the prologue, first region, Beacons, Shells, and optional encounters. See the playable Shell information we can verify without publishing name-only profile pages. Filter the current map notes for Beacons, Tarstones, Shells, dungeons, and route anchors. Compare the Open Beta and full-game Steam requirements before downloading.

Release

Mortal Shell II launches digitally on August 20, 2026 for Steam, PlayStation 5, and Xbox Series X|S.

Open Beta

The free Steam build covers roughly the opening three hours, from the prologue into the first explorable region.

Progress transfer

Currency, weapons, Shells, collectibles, and other items reset at launch. The beta reward and a prologue-skip option are the documented exceptions.

Full-game structure

The official site describes an interconnected open world, eight playable Shells, stamina-free combat, sidearms, and extensive weapon upgrades.

What becomes a public page

A guide needs a clear player task, a direct answer, actionable steps, a stated game version, and a source. Client data can confirm names and assets, but a name alone does not prove an effect, location, drop, quest step, or build recommendation.

What stays out of search

We do not publish entity pages whose main value is “unknown,” “not confirmed,” or a repeated template. Community reports can identify questions worth testing, but structured facts require the game, an official statement, or another source that can be independently checked. Primary sources: official game site , Steam Open Beta page , and Playstack release announcement .

Evidence boundary for Mortal Shell 2 Wiki — Verified Open Beta Guides

Mortal Shell 2 Wiki — Verified Open Beta Guides is stored as a walkthrough decision from MortalShell2.org. The source snapshot was captured on 2026-08-18T08:19:59+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 Wiki — Verified Open Beta Guides 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.

Verify the walkthrough decision in the current build

Separate required progression, optional cleanup, missable preparation, irreversible transitions, and source-version assumptions. A captured order can organize a run without proving that every release build requires the same sequence.

For Mortal Shell 2 Wiki — Verified Open Beta Guides, 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 Mortal Shell 2 Wiki — Verified Open Beta Guides with the companion tools

Use the roadmap for ordered decisions, the map for one named acquisition lead, and the tracker for confirmed local progress. Keep optional skips, unknown states, and completed objectives distinct.

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 Wiki — Verified Open Beta Guides 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.

Reconcile and close the Mortal Shell 2 Wiki — Verified Open Beta Guides record

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 Wiki — Verified Open Beta Guides.

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.