Sovereign Tower released on Steam on August 6, 2026, and its public news is still changing quickly. This direct update hub follows the official base-game listing and Steam Community news rather than creating an empty dropdown of guessed patch pages. The purpose is simple: tell players which source was checked, separate release facts from community observations, and give corrections a dated place to land. The site does not treat the Demo, a preview, or a related soundtrack product as a base-game patch.
Official release identity
The base product is Steam AppID 4113940. The official store page credits WILD WITS GAMES as developer and Curve Games as publisher, lists the release date as August 6, 2026, and describes the game as a single-player Round Table management RPG. It also lists Windows and SteamOS+Linux support, Steam Achievements, Steam Cloud, Family Sharing, and 75 achievements. These are identity and scope facts; they should not be rewritten as a promise that every menu or value remains unchanged after a hotfix.
The Demo uses AppID 4422320. It is useful for understanding how the project was presented before launch, but its content, progression boundary, and menus are not automatically the full game. Every update entry on this site should state which AppID it covers so that a reader can tell a Demo note from a base-game correction.
How to read official news
The Steam Community news feed is the primary maintenance source for developer announcements, feature explanations, and new content. A post may describe a system in broad language rather than publish a complete table. Quote only the minimum wording needed for identification, link the original post, and summarize the player-facing consequence in new language. Record the publication date and the date the site checked it.
Official news can also reveal that a system is broader than the store summary suggests. Recent posts discuss the Demon, retained knowledge, an Omniscience response, new pathways, and new characters. Those observations justify a Time hub and spoiler-aware route notes; they do not justify inventing the price, limit, or unlock order of every rewind.
What counts as a correction
A correction changes a statement that was wrong or too broad for the released base game. Examples include confusing AppID 4113940 with the Demo, describing a preview behavior as a release guarantee, assigning an unofficial Quest count the status of official data, or presenting a community Knight trait as developer-confirmed. Corrections should name the affected page, the old statement in a short paraphrase, the new boundary, and the source that supports the change.
Do not delete a useful historical note merely because the game moved on. Mark it with a date and explain that it applies to an earlier build. Remove it from current metadata and navigation when it would mislead searchers. Protected ad frames, analytics code, and third-party scripts are not game-content sources; any old labels inside them should be recorded as protected residue rather than used to delay a guide correction.
Community evidence has a role
Launch-week players are already documenting a large Quest set, Knight traits, favorite meals, recruitment, and unexpected outcomes. These reports help identify what people search for, especially when the store page only summarizes the mechanic. They remain fallback evidence. A community table should state how it was collected, whether the author tested it in the public release, and which claims are still uncertain.
When a community report conflicts with official news, use the official source for product identity and intended feature scope. For a specific gameplay observation that official material does not enumerate, label the community source clearly and add the platform, date, and version boundary. Invite corrections with reproducible details rather than treating popularity as proof.
Maintenance rhythm
At each maintenance pass, check the store page, official Community news, and the exact pages linked from this site. Search for the AppID, Demo confusion, release-state changes, and new names that affect the Knights, Quests, Kingdom, Time, or Achievements hubs. Rebuild the sitemap after route changes and confirm that localized links point to the same intent. Do not create a child update route merely to display a date; use this direct hub until a distinct update has enough evidence and player intent to stand alone.
For a reported issue, capture the page URL, statement, source URL, date, platform, and whether the issue reproduces in the current public release. Keep the report free of private save files or account identifiers. A small evidence packet makes future edits faster and makes uncertainty visible to the reader.
Current boundary
As of August 10, 2026, this tracker records the public release identity and the available official feature/news context. It does not claim a particular patch number, branch, hotfix, Quest total, Knight roster total, achievement unlock list, or current balance value. Those details belong here only after the source is public, the product is confirmed, and the statement is dated. Until then, the other hubs should use the same transparent wording.
The same boundary applies to screenshots, videos, and search snippets. A thumbnail can identify a scene without proving its current behavior, and a search result can surface an old preview after launch. Link readers to the canonical page, show the checked date, and refresh the summary when the official wording changes. This keeps the tracker useful to players who arrive during the noisy first weeks of release.
Sources and scope
- Sovereign Tower on Steam is the base-game identity and release source.
- Official Steam Community news is the maintenance source for developer updates.
- Sovereign Tower Demo on Steam is tracked only to prevent product-scope confusion.