Nivalis Nights is planned for a full Steam release on September 29, 2026. This Updates page is a trust layer: it tracks only information tied to Steam AppID 1488490 and clearly separates release announcements, development communication, and actual patch notes. At the audit date the game is not yet available, so there are no verified post-launch patch notes or live-build balance changes to report.
Release status
The canonical Steam store page currently lists September 29, 2026 and says the game is not yet available. The official Steam Community FAQ says Nivalis Nights will launch as a full release and will not have an Early Access period. Keep both the date and the release-state wording together because readers ask both “when” and “what kind of launch.”
Release dates can move. The page should show the last checked date and link to the current source instead of embedding an unverified countdown or guaranteeing that the date cannot change. If Steam changes the date, update this hub first, then review the homepage, beginner guide, and Systems page.
Official development communication
The Steam Community hub contains official events, announcements, and development updates. Use the Events and Announcements page as the collection point for official posts. A community blog title can be listed as communication history, but its title alone is not a patch note and should not be summarized as a mechanic change.
For each entry, record the post date, exact title, publisher or developer identity, source URL, and a short summary of what is actually stated. Keep announcements about trailers, release dates, optimization, languages, and platform plans separate from changes that players can reproduce in a build.
What counts as a patch note
A patch note needs a public game version, build context, or official changelog that describes a change to the playable product. “New trailer” is a release communication. “The store requirements changed” is a store-data update. “Fishing now accepts a new item in build X” is a patch-level mechanic claim. If the source does not state the build or change, label it as an announcement and do not translate it into an update table.
After launch, route changes to Businesses, Fishing, City, Relationships, Activities, or Systems with a dated note. Leave the timeline as the history and keep each guide’s current procedure concise.
Pre-release checklist
Before release, recheck the Steam title, AppID, date, availability, languages, requirements, controller support, Steam Cloud, and platform status. Watch for an official demo or playtest announcement, but do not add a separate product page until a public AppID and scope are verified. Check the official ION LANDS and 505 Games channels when Steam links to them.
Do not infer abandonment from a quiet period. Do not invent a roadmap cadence or a future feature. If an expected announcement has not appeared, say “not publicly confirmed as of the check date.” That is more useful than a speculative schedule.
Source and scope rules
Every timeline entry belongs to base game AppID 1488490. Historical posts that use the earlier Nivalis name can be included when the post clearly concerns the same product, but Cloudpunk updates, 505 Games collection news, unrelated DLC, and fan speculation stay out. The site is an independent guide, not an official news feed.
Editorial status labels
Use Planned release for the current date on the Steam store, Official announcement for a developer or publisher post, Store data for requirements or language changes, and Patch note only when a public game build has a stated change. Add Unresolved when a field such as BuildID, branch, or demo AppID cannot be checked. These labels keep a reader from confusing a trailer, a community answer, and a playable patch.
How to handle a date change
If the official date moves, update the release card, record the old date in the timeline, and review the beginner and Systems pages for stale wording. Do not rewrite an older announcement so that it appears to have predicted the new date. If the store and a community post disagree, link both and identify which one is current. The current store page controls the canonical availability claim until an official post supersedes it.
Post-launch maintenance
After release, maintain a short timeline entry for each verified patch and use the affected guide as the detailed home for the mechanic. A business balance change belongs in Businesses; a catch-table change belongs in Fishing; a controller fix belongs in Systems. This division makes the history readable and avoids a single Updates article becoming an unsearchable dump of copied patch text.
What is not yet known
As of this audit, no public base-game BuildID, default branch identifier, separate demo AppID, or playtest AppID was safely established. No verified patch notes exist because the product is not yet available. This is a scope boundary, not a statement that development has stopped. A future editor should replace each unresolved field only with a public Steam or publisher source and record the check date beside it. Until then, the unresolved label remains the correct answer for readers asking for a build number. That keeps launch coverage honest while leaving editors a precise field to fill later.
Sources
- Nivalis Nights on Steam, checked 2026-08-09.
- Official How to / FAQs, checked 2026-08-09.
- Official Steam Community Events and Announcements, checked 2026-08-09.