Known issues and how to report bugs
Report bugs through the developers' form or their Discord, with your Player.log attached — the file lives in AppData\LocalLow\Oxalis\Moonfrost. Three demo hotfixes fixed stucks, the temple door and tool balance.
The fastest route out of a stuck save is the developers' own report channel, with the right file attached. This page collects where to send a report, how the team's response looked during the demo period, and which problems were already on their list.

How to report a bug
The developers' pinned thread asks for two things:
- The bug report form — linked from the "How to report bugs (please read)" thread in the Steam discussions.
- Your Player.log file, which they say helps them investigate much faster. You can find it at
C:\Users\<user>\AppData\LocalLow\Oxalis\Moonfrost\Player.log.
For anything urgent — a progression blocker or a save that will not load — the team asks players to go to their Discord and open a support ticket. Screenshots, videos and steps to reproduce are all useful to them.
What their turnaround looked like
While the demo was live the team shipped three hotfixes in quick succession, each with a public list of what was fixed and what was still open. That is a useful signal for what to expect during Early Access: fixes come in small, documented batches.
| Patch | Fixed | Still open after it |
|---|---|---|
| 1.0.1 | Input sticking during cutscenes; cursor disappearing in dialogue and UI; character name now required | — |
| 1.0.2 | Language auto-selection; stuck after a conversation; disappearing bed; tutorial dialogue polish; typos; storage chest added as a task reward | Door costs not visible; music looping; workbench deleted in build mode; stuck tool use; door collisions |
| 1.0.3 | Music looping and transitions; pickaxe and axe damage and stamina balance; dialogue fixes; temple door issue; walking up certain terrain | Infinite salad creation; stuck after certain cutscenes; walking through a building in the village |
Two notes on reading that table. The terrain walk-up fix only applies to a new game or new save, so an old save will still show the problem. And the hotfixes are demo-era: the Early Access build followed them, so treat this as the team's working style rather than a live status board.
The issues players talk about most
- A save that will not load. Older demo saves are not compatible with the 12 October demo update and need a fresh start. That is a format change, not data loss. Progress made in the updated demo is intended to carry into the full game.
- Rooms that will not register. Door placement is the usual cause: cost visibility and door collisions were both listed as known issues.
- Getting stuck. Cutscene stucks, tool stucks and being unable to walk up certain terrain were all tracked publicly, and the specific fixes are in the table above.
- Lost workbenches. Deleting a workbench in build mode loses it. Move it instead.
What we can help with
If a page on this site is wrong, use the contact page — that reaches us. Anything happening inside the game belongs with the developers' channels above, where the log file and a screenshot actually help.