This is the GRAIN ROT update record for the base Steam game, AppID 4450620. It is intentionally a direct hub with no empty child menu: a small launch site should not manufacture one page for every rumor, bundle, or community thread. Each entry belongs to a dated official Store history or a developer/publisher announcement. Community posts can point the wiki toward a question, but they are labeled as community evidence rather than silently merged into an official changelog.
Launch is a boundary, not a permanent version label
GRAIN ROT released on Steam on August 7, 2026 according to the Store page. That date is useful for release history, launch guides, and the distinction between pre-release demo evidence and the base game. It is not a version number. When a page says “launch build,” it should also carry a check date and explain which fact is tied to that state. Do not turn a depot BuildID, beta branch, or a screenshot timestamp into a public semantic version.
The Store description also distinguishes the full game’s persistent Outpost, shifting Deep Layers, Corrupted threats, and Living Spark loop. A demo or a pre-launch video may show the same concept with different rooms, items, or balance. The update hub should preserve the distinction so a player does not follow a launch article using a demo-only route.
Store metadata, developer/publisher statements, and dated Steam announcements for the exact AppID.
Player reports and questions that identify a topic to verify; never present them as a patch note.
Time-limited items such as launch-week Twitch Drops belong here with start/end dates and event scope.
Link the affected evergreen hub only when an update changes the answer players need.
Patch 1.01 and performance follow-up
The current Community Hub exposes a Patch 1.01 entry that mentions fixes for picking up coins or a fuse from some boxes in the Deep Layers, a furniture-category display for tables in the build menu, and a performance issue related to light invalidation. These are useful update leads because they map directly to Systems and Support. The final article should link the exact official post or Store history entry and carry its real timestamp; this hub records the current observation without inventing a broader changelog.
When a patch changes a page, state the impact. A box interaction fix may change a troubleshooting step. A menu-category correction may change how the Outpost page tells players to find furniture. A performance fix may reduce one cause of poor frame time without guaranteeing that every PC now performs the same. Keep the old guidance dated if it remains useful, and write the new guidance with the current build boundary.
Launch-week events are not permanent systems
The Community Hub also exposes launch-week Twitch Drops with two cosmetics and an August 14 end date. An event reward is not a GRAIN ROT code, a permanent item table, or a guarantee that the same reward will return. Record the event source, eligibility, watch-time requirement, start/end window, and whether the developer says it is exclusive. Remove or archive it when the window closes instead of leaving a stale “active” claim in a general guide.
The same rule applies to discounts, bundles, demos, and promotional posts. The Store page shows commercial bundles and an introductory offer, but those are not base-game mechanics. Keep price and promotion facts dated, separate from the evergreen Guides and Systems pages, and never use them to infer the value of an Outpost upgrade.
How to consume a Steam announcement
Start with the exact AppID and the post author. Read the title, date, affected build or branch, platform, and the actual change. Then compare the change with the current page. If the post says a bug was fixed, do not rewrite the whole mechanic unless the fix changes the player action. If a player report contradicts the post, record the disagreement and ask for a current reproduction rather than choosing a side.
For volatile claims, put the date beside the sentence, not only in a footer. A player searching “GRAIN ROT performance” needs to know whether a workaround predates Patch 1.01. A player searching “GRAIN ROT Grinder” needs to know whether the conversion value was checked after an economy patch. This is why Updates exists separately from Systems and Support.
What this hub will not claim
It will not infer abandonment from a quiet week, call every Steam event a patch, invent future roadmap features, or convert a community guide into official documentation. It will not create a Codes section for Steam keys, launch options, puzzle codes, or Twitch Drops. It will not mix demo, bundle, DLC, soundtrack, or another AppID into the base-game timeline. When evidence is missing, the entry says “not publicly stated” or “needs live/version testing.”
Follow the impact
Use Support for Patch 1.01 performance and hardware questions, Systems for Grinder or furniture changes, Outpost for base-building changes, and Guides for player-facing route updates. The update hub remains one direct link in the primary navigation exactly once.