Mortal Shell II Retail vs Open Beta: Use the Correct Version
Published 2026-08-22 · Updated 2026-08-22
Separate Mortal Shell II retail information from Open Beta data, identify the correct Steam app, and avoid carrying obsolete storage, progression, or patch advice into the full game.
Sources
Checked on 2026-08-22. Store details and balance may change after patches.
The two Steam apps are not interchangeable
Mortal Shell II retail uses Steam App ID 2584270. The Open Beta uses App ID 4711740 and is identified by SteamDB as a demo whose parent is the retail game. That distinction matters whenever a guide cites requirements, files, branches, reviews, achievements, patches, or carry-over behavior. Before following a fix, open the Steam store or library entry and confirm which product is running. A search result that says Mortal Shell II can still lead to the Beta page, so the page title and App ID are stronger identifiers than a thumbnail.
Storage advice changed for retail
The official retail Steam page lists 70 GB available storage and requires an SSD. The Open Beta page lists 30 GB, while SteamDB recorded a larger installed Beta depot at one stage. These numbers describe different products and snapshots; they are not evidence that the retail installation should be forced into the Beta footprint. If an old performance article says 30 GB is enough, treat that as Beta-era guidance. Leave room for downloads, unpacking, shader data, saves, and future patches rather than filling the drive to the minimum free byte.
Do not import Beta balance into a retail build
The official pages describe the Beta as a limited opening slice and the retail game as the complete standalone sequel. Enemy placement, costs, Shell availability, upgrade behavior, options, and performance can change between them. A Beta video remains useful for identifying an interface or explaining historical context, but it cannot establish a current item location or universal build. Check the guide's date and source. If the claim depends on a number or position that the current official material does not confirm, verify it in the retail game before spending resources.
Use a four-field version check
Record four fields before reporting a problem: product name, App ID, game version or patch label, and platform. On Steam, also note whether a testing branch is selected. This turns a vague report into something another player or developer can reproduce. It also prevents a common support loop in which retail fixes are tested against an old Beta installation. When screenshots are shared, include the library product name or version display but remove personal account information.
Keep both installations from confusing troubleshooting
If both products appear in the library, verify the executable through the correct Steam entry instead of deleting folders manually. Check the install location, shortcut target, and the store page reached from the library. Back up saves before removing any game data. A clean retail verification should be performed through the retail App ID. Do not copy Beta configuration folders into retail unless an official support instruction explicitly requests it; even similarly named options may have different defaults or formats.
How this site labels older evidence
Pages on this site identify Beta-only evidence in the source label and restrict it to the symptom or historical fact it actually demonstrates. Retail requirements come from the full-game store page. SteamDB is used for app identity, dates, packages, and update history—not for invented combat facts. When an official retail update supersedes a Beta workaround, the retail source wins and the affected guide should receive a new updated date. This policy keeps useful historical reports without presenting them as current universal instructions.