Steam scope: Windows PC.
The Mortal Shell II update record is intentionally chronological. It answers what changed in the official product record, what announcement established the current release state, and which observations belong only to the separate Open Beta. The base game uses Steam AppID 2584270; the Open Beta uses AppID 4711740. These products can share a name while having different content, dates, and entitlements, so every entry begins with the correct identity.
Current release checkpoint
At the 2026-08-09 checkpoint, the base Steam page shows Mortal Shell II as an upcoming, pre-purchasable Windows product with an expected release date of August 20, 2026. That is a dated store state, not a guarantee that the date can never move. If the page changes, the update entry should preserve the old date and record the new one rather than silently overwriting history.
The current page identifies Cold Symmetry as developer and Playstack as publisher. It also presents the sequel as an action RPG with an open-world direction, more than 60 dungeons, Shell possession, and a no-stamina combat concept. Those are product-description facts. They should not be rewritten as a patch note or expanded into an unverified enemy and item list.
How official entries are selected
An entry needs a publication date, a source URL, a short description of the change or announcement, and a product scope. Official Steam News and the developer or publisher’s own announcement pages are preferred. A community post can point to a change, but it should not be the only evidence for a release date, price, platform, or patch behavior.
Do not merge an announcement with an observation simply because they were published close together. A trailer can confirm that a feature is shown; it may not confirm that the feature is available at launch. An Open Beta note can confirm what the test exposed; it cannot confirm that a full-game reward, map, or progression rule is unchanged.
Beta entries
Beta entries use the separate AppID 4711740 in their label or source note. They are useful when they answer a narrow player question such as “what does the opening test cover?” or “what control language appears in the test?” They are not a substitute for the base-game release notes. If a Beta item is removed, that is an update to the Beta record, not automatically a change to the full product.
Keep the date visible next to a Beta observation. A limited build can be updated without changing the base store page, and a video can remain online after the test has changed. The correct phrasing is “observed in the Beta on [date]” until a full-game source confirms the same behavior.
What needs rechecking after release
On August 20, or after a changed launch date, recheck the store identity, price and edition labels, release status, requirements, supported language columns, and the first official patch. Then recheck all pages that mention combat input, Shell names, weapon routes, dungeons, save behavior, controller prompts, Steam Deck, or performance. These claims are version-sensitive and should carry the date of their evidence.
The update log should link to a revised article when a change affects a player decision. It should not repeat the full article. A short note such as “the requirements block changed; see Technical” keeps the timeline useful and avoids duplicate prose across update entries.
What counts as a correction
A correction is warranted when an old article used the wrong AppID, treated Beta evidence as launch evidence, copied a fact from the first Mortal Shell, or reported a date without a source. Preserve the reason for the correction and the new evidence. A correction history increases trust because it shows why a sentence changed.
Do not use the update hub for ordinary speculation, code lists, tier rankings, or a collection of unverified social posts. Those entries create the appearance of activity without helping a player decide what to do. When evidence is weak, the useful update may be “not confirmed” plus the exact check that would resolve it.
An update entry should make its time boundary visible. Use the publication date for an announcement, the observation date for a Beta test, and the check date for a store-state capture. If a later source corrects the earlier one, keep both dates and state the reason. Readers can then tell whether a changed sentence reflects a new patch, a corrected product scope, or a more reliable interpretation of the same announcement.
The update hub also acts as a maintenance queue. When a new official post changes a release date, language table, requirement, or edition, link the affected Guide, Systems, or Technical page and schedule a focused reread. Do not refresh every article merely because a news item exists; update the pages whose player decisions are actually affected.
FAQ
What is the current base-game release date?
The Steam base-game listing currently shows August 20, 2026, checked on 2026-08-09. Recheck the official page when publishing a new entry.
Why is the Open Beta in a separate timeline?
Because it has AppID 4711740 and is a distinct product. Its observations must not silently become base-game facts.
Where should a technical fix go?
The timeline records that the official change happened; the Technical hub explains the player action. Keep the two links connected but do not duplicate the troubleshooting steps.
Sources: Mortal Shell II on Steam, Mortal Shell II Open Beta, official Steam News, and Playstack. Checked 2026-08-09.