This is the dated status page for MARVEL Tōkon: Fighting Souls on Steam. The official base-game page for AppID 3787240 reports a release date of 2026-08-06 and exposes links to update history and related news. As of the 2026-08-09 check, this handoff establishes the release milestone and the store-defined feature scope, but it does not establish a complete public patch-note corpus, a semantic version, a BuildID, or a second branch. A careful update log says what was checked and what was not found.
Current release record
The current official store page lists MARVEL Tōkon: Fighting Souls as released on 2026-08-06. The base product is the Steam PC identity used throughout this wiki. The PC system panel lists Windows 11, 64-bit requirements, 16 GB RAM, and 27 GB storage, while the feature panel lists modes, online requirements, DualSense support, Steam Cloud, and 39 achievements. Those are the baseline product facts checked on 2026-08-09, not a patch number.
Use the Modes, Systems, Combat, and Editions hubs for evergreen explanations. Add an update entry only when a release notice materially changes one of them. Do not copy the entire store description into every update card.
What the official update source should contain
An official patch entry should answer five questions: what date was it posted or released, what version or branch does it name, which product or DLC does it affect, which platform is in scope, and what player-facing behavior changed? A balance adjustment belongs near Combat or Characters. A mode fix belongs near Modes. A requirement or account change belongs near Systems. A delivery notice belongs near Editions.
If an announcement has no version label, write “version not publicly stated” rather than guessing from a timestamp or a SteamDB BuildID. If it describes a planned character or stage, use a future-content label. If it announces availability, record the actual release date and update the related index only after verifying the live product.
Release milestone versus patch note
The 2026-08-06 release date is a release milestone. It is not itself evidence of a balance patch, hotfix, or launch-day server change. Keep those event types separate so players can tell whether a page describes when the game became available or what changed after availability.
The store page also says the Year 1 pass includes four characters and one stage post-launch and that the remainder is expected by 31 December 2027. That is a product-delivery statement. It should be tracked under Editions until a dated official announcement identifies a character, stage, or availability event. Do not fill the update feed with placeholder names or a made-up schedule.
Check before publishing a new entry
Start with the official Steam update-history or announcement link from the base page. Confirm the URL still resolves to AppID 3787240 or to a directly related DLC AppID. Read the entire notice, not just its headline. Compare the stated platform and branch with this site’s scope. Then search the source corpus for the affected claim so the evergreen page can receive a short dated note rather than a duplicated patch article.
For a character update, verify whether the character is launch or Year 1 content. For a stage update, verify whether the stage is base game or pass content. For an online update, distinguish account access from matchmaking behavior. For a system update, capture the published requirement and the player’s observed result separately.
What this page does not claim
This page does not claim a regular patch cadence, active support level, future roadmap completion, or abandonment. It does not infer a public version from the release date. It does not use review totals as a patch signal. It does not turn a store edit into a gameplay change without an official explanation.
It also does not merge other Steam products into the base game. The Year 1 Characters and Stage Pass is AppID 4848500; Standard–Ultimate and Deluxe–Ultimate upgrades are 5030920 and 5030930. A related product can receive an update entry, but the entry must identify its own scope.
A useful update record for players
Each entry should have a short summary, a dated source link, a scope badge, and one “check this next” link. A balance note can link to Combat. A new roster entry can link to Characters. An online change can link to Modes and Systems. A pass delivery note can link to Editions. This keeps the feed useful even when it is sparse.
When no official patch notes are found, say so as of the check date. That is more informative than repeating a generic “no news” paragraph. The maintenance task is to check again after a named official announcement, a store update, a product delivery date, or a player question that points to a first-party source.
Update FAQ
What is the latest verified milestone?
The official Steam page reports release on 2026-08-06, checked here on 2026-08-09 UTC.
Is a semantic version known?
Not from the public store evidence used in this audit. Record a version only when an official note or authoritative build source names it.
Does the Year 1 date mean all content is released?
No. The store describes expected future availability; track delivery separately and update only when an official notice confirms a release.
Where should a balance change be explained?
Put the dated change in Updates and the durable player explanation in Combat, Characters, Teams, or Modes, depending on what changed.