How to read this tracker
CONTROL Resonant is currently an unreleased base-game Steam product with a listed 24 September 2026 release date. This page is the controlled home for official announcements, dated Steam news, launch-state changes, and later patch notes. It is not a placeholder changelog and it will not invent entries to make the timeline look full. Each update must state its date, source, scope, and practical effect on a player or guide.
The strongest source order is the official Steam product/news feed and Remedy’s official game and news pages. A reputable preview can help explain why a topic is worth watching, but it is not a patch note. Community reports can be useful leads, yet they remain unconfirmed until an official post or reproducible live-build evidence supports them. This distinction protects the page from turning a preview detail into a permanent mechanic.
Current release-state record
The Steam page identifies AppID 3669870, Remedy Entertainment as developer and publisher, a single-player scope, and a Windows 10/11 64-bit PC target. It currently presents the product as coming soon and available for pre-purchase. The official Remedy page repeats the 24 September 2026 date and lists the wider platform context. If either store page changes its date, edition wording, or platform scope, record the date of the change and link the updated source.
The page should keep one current status sentence near the top, followed by a dated timeline. Avoid a second competing release date in a card, metadata field, or translation. When a locale receives a different store message, quote the locale source and explain whether the difference is wording or an actual regional release change.
What belongs in a dated entry
Use a compact entry with a human-readable date, an official source label, a short type such as release, gameplay, language, or patch, and two or three player-facing bullets. Explain what a player can do with the information. A gameplay announcement can point to Combat or Systems. A language announcement can link to Technical or accessibility research. A patch note can list affected pages and the version boundary.
Do not add a title that only says “news.” The title should identify the event: a launch announcement, a named gameplay presentation, an official language note, or a versioned patch. If the source is a video, include the official video page and describe only visible or stated information. Do not manufacture a transcript or claim that a trailer proves a mechanic outside the shown context.
Pre-release topics worth monitoring
Current official wording supports monitoring combat, supernatural powers, the Aberrant weapon, exploration, side content, anomalies, puzzles, bosses, player choices, and the PC requirements. The Steam page also contains dated news material around gameplay and supported languages, while current announcements mention launch and world details. These are monitoring categories, not a fabricated history. A new entry should be added only when an official source provides a date and a change in the public record.
When a topic changes, update the nearest canonical guide and add a cross-link here. For example, if Remedy publishes a confirmed weapon-form explanation, update Arsenal and record the source date. If the Steam requirements change, update Technical and preserve the previous table under its version label. If a story trailer reveals a new name, update Story with a spoiler marker instead of adding an unconnected glossary stub.
Launch-day maintenance
On release day, verify the Steam title, AppID, base-game scope, store requirements, supported languages, and the first official patch. Check the site’s homepage, primary navigation, canonical URLs, sitemap, and language switcher after content updates. The release is a state change, so every page that says “pre-release,” “coming soon,” or “not yet confirmed” should be reviewed before it remains indexable.
The first live update should prioritise player safety: installation requirements, save and accessibility notes, known issues from official support, and a clear distinction between launch content and future announcements. Do not fill the page with unverified day-one rumours. A short, sourced tracker is more useful than a long timeline that cannot be audited.
Version labels and corrections
Every guide change should have a reason. Use the Steam build or patch label when the official source provides one; otherwise use the publication date and state that the build label is unavailable. If an earlier page was based on preview wording, preserve the correction note and explain the change. Never silently overwrite a confirmed value with a newer guess.
This tracker is deliberately hub-only while official dated entries remain limited. It becomes more useful when it records real changes, not when it adds empty child pages. Readers should be able to open an entry, inspect the source, understand the scope, and know which guide has been refreshed. That is the standard for every future CONTROL Resonant release note.
For translations, keep the source date, product name, AppID, version label, and source URL aligned with English. Translate the explanation naturally, but do not translate a build identifier or silently localise a quoted in-game term. If a translated store page omits a field, link back to the canonical source and state that the English listing supplied the value. That prevents a language switch from creating four conflicting release records.
That discipline also makes future audits reproducible: every entry can be checked against a dated page rather than memory.
Sources: Steam store page, Remedy news, Remedy official game page.
Use this tracker as a dated change log, then return to the affected hub for context and the released build for final confirmation.