Moonfrost launched into Steam Early Access on October 12, 2026. This page tracks official announcements that change what a player can access, whether a Demo save transfers, which content is currently in scope, and what has actually shipped. Roadmap plans stay separate from released changes, and a third-party Steam BuildID is never presented as a public semantic version.
The latest first-party entry available on October 15 is the Early Access launch announcement. No separate public semantic version label or post-launch base-game patch note was found in the official feed at this checkpoint. That does not prove there were no backend builds; it means players do not yet have a developer-authored numbered patch record to cite.
Current release snapshot
Release state
Early Access, released October 12, 2026.
AppID 2561630Public version
No semantic version is stated on the store or latest official announcement.
Not publicly statedNative platform
Windows. Steam lists Windows 11 in the minimum requirements.
Steam public branchDemo transfer
October 12 updated-Demo progress can carry to Early Access; older Demo saves are incompatible with the updated Demo.
AppID 4684100 boundaryCurrent content
First half of the story, opening Temple scope, 11 villagers, friendship to level 3, restoration, housing, and hundreds of blueprints.
Launch scopeRoadmap
More story, characters, relationships, Temple levels, locations, and features are planned, but timing can evolve with feedback.
Plan, not patch noteWhat counts as an update here
An entry needs a date, an official Steam, Moonfrost, Oxalis Games, or clearly authored developer source, an exact product scope, and a player-facing change. A launch announcement, Demo compatibility notice, patch note, hotfix, or shipped content milestone qualifies. A roadmap image is stored as a plan. A Steam event that contains no game change is not converted into a patch.
Community reports can identify a problem that players are seeing, but they do not establish a fix. SteamDB can record a BuildID or metadata change, but a BuildID is not a developer version such as 1.0.0 and does not explain the patch contents by itself. Every update-sensitive guide should point back to a dated official entry when one exists.
Timeline
2026-10-12 - Moonfrost enters Early Access
Type: Early Access launch
Oxalis Games announced that Moonfrost was available in Early Access on Steam. The post invites players to farm, fish, cook, craft, explore, meet friends, and rebuild the village. It also presents the roadmap as a look at what may come next and explicitly warns that plans can evolve during development.
- Base game: Steam AppID 2561630.
- Platform: Steam on Windows PC.
- Current roadmap items remain plans until a later announcement says they shipped.
- Bug reports and feedback are directed to Steam Discussions or the official Discord.
Source: Official Early Access launch announcement
2026-10-11 - Updated Demo save rules announced
Type: Demo compatibility
The team announced an updated Moonfrost Demo for October 12, five hours before the paid Early Access launch. Saves from the previous Demo generation are not compatible with the updated Demo and require a new start. Progress created in the updated October Demo can carry over to Early Access.
- Previous Demo save to updated Demo: incompatible.
- Updated October Demo to Early Access: carry-over supported.
- Demo identity: AppID 4684100, separate from base-game AppID 2561630.
- Diagnose a missing transfer by Demo generation before treating it as general cloud-save failure.
Source: Official one-day-to-launch and Demo notice
2026-09-29 - Early Access content scope detailed
Type: Release scope
The release-date announcement describes around half of the main story, Temple access through Level 19 with puzzles, 11 NPCs, relationships up to level 3, village cleanup and street repair, an in-game map, updated tasks, and decoration crafting puzzles. The current store later describes the Temple as the first 20 rooms; both official counting labels are retained.
- Story: around 50 percent at launch.
- Temple: through Level 19 in this announcement; first 20 rooms on the store.
- Villagers: 11, with relationships capped at level 3.
- Village: cleanup, repairs, and restoration are current activities.
Source: Official Early Access date and scope announcement
2026-07-10 - Olunari Temple changes previewed
Type: Development diary
An official Temple development diary previewed a revised exploration space with puzzles, hazards, symbols, hidden routes, teleporters, and shortcuts. Treat this as first-party design context for the Early Access Temple, while using the released game for exact room solutions, damage, timing, and route availability.
- Symbol and mechanism concepts are supported by official development material.
- A preview is not a complete solution list or proof of every data-recorded room.
- Current access still follows the Early Access launch boundary.
Source: Official Moonfrost Steam news archive
Current known issues versus confirmed fixes
Steam Discussions at launch include questions about rooms, workbenches, save data, resolution, controller and fishing prompts, Copper Wire, Quartz, Silver, storage, and tools. Those topics show where players need help; they are not an official known-issues list. A developer-tagged reply can clarify one context, but the issue remains open until a dated post or current build observation confirms the change.
Before applying a workaround, identify the AppID, current build date, operating system, input device, quest stage, and whether the report came from the old Demo, updated Demo, or paid Early Access game. Back up saves before any file operation. Prefer reversible setting or route checks over deleting data.
How to act on the next patch
Read the official note first and identify whether it targets the base game or Demo, public or other branch, Windows or Deck-specific behavior, and a named system. Load a stable save, test one affected action, and only then update your route, settings, or resource plan. If the note changes a room check, recipe, spawn, relationship cap, Temple depth, or save rule, the relevant guide and database entry should receive the same date and scope.
If no authored note exists, describe only the observed behavior and the Steam BuildID as third-party metadata when needed. Do not call the build number a version. Continue to Early Access Content for current boundaries or Tech for reproducible platform troubleshooting.