Mortal Shell II SteamDB Update Tracker: Builds, Apps and Patches
Published 2026-08-22 · Updated 2026-08-22
Read Mortal Shell II SteamDB App IDs, update history, packages and Beta relationships without mistaking a database change for an official gameplay patch note.
Sources
Checked on 2026-08-22. Store details and balance may change after patches.
Start with the retail App ID
SteamDB identifies Mortal Shell II retail as App 2584270, developed by Cold Symmetry and published by Playstack. It separately links Beta and Playtest products to the parent game. Use the App ID to avoid reading the wrong depot or history page. A matching title is not sufficient because store search results and community hubs can continue to surface Beta material after launch.
A changenumber is not a gameplay explanation
SteamDB records database and package changes, including a last changenumber and record-update time. These values show that Steam metadata changed; they do not explain balance, enemy behavior, or bug fixes. Only call a change a gameplay patch when an official developer note says so. If no official note exists, describe it as a build, depot, package, or metadata update and leave the gameplay effect unresolved.
Packages describe purchase relationships
SteamDB package pages can show the retail app, price history, included apps, release date, and depot relationships. This helps distinguish the standard product from associated content, but package data is not a complete edition-benefit explanation. Use the official store comparison for cosmetics, access timing, and purchase promises. Prices also vary by currency and can change, so attach a checked date rather than preserving a number as permanent.
Depots and download size require careful wording
A depot is a Steam content container. A manifest change proves that files changed, not why they changed. Download size, disk size, unpacking space, and store-listed required storage can all differ. For troubleshooting, record the Steam download shown to the player and the free disk space; for requirements, cite the official 70 GB retail listing. Do not use a Beta depot size as a retail installation promise.
Use update history to trigger guide reviews
When SteamDB shows a new retail build or record change, treat it as a signal to check official announcements and retest patch-sensitive pages. Review performance workarounds, targeting instructions, costs, locations, and build claims. If the official notes show no relevant change, the guide may only need a checked date. If behavior changed, update the body, schema dateModified, and links from the patch index.
A safe tracker workflow
Monitor App 2584270, record the observed SteamDB time and identifier, then look for a matching official Steam or developer post. Summarize only the official explanation and link both sources when useful. If no note exists, publish no speculative fix. This workflow makes SteamDB a freshness detector while keeping Cold Symmetry and Playstack material as the authority for player-facing meaning.
Fields to preserve in a patch index
A durable patch record should keep the observed date, retail App ID, SteamDB build or changenumber when visible, official patch label, platforms named by the developer, official URL, and the guide pages that may be affected. Keep an additional status field: review required, reviewed with no change, updated, or awaiting official explanation. This prevents every database event from becoming a thin news post. Publish a player-facing entry only when the official information changes a decision, fixes a recurring problem, or tells players to retest an existing guide; otherwise update the internal ledger and wait. Preserve the checked time so readers can distinguish a current review from an abandoned tracker.