Crimson Moon patch notes - Updates | Crimson Moon Wiki

This crimson moon patch notes page separates an official PC announcement from a later secondary hotfix snapshot. Patch 1.0.0.1 is supported by captured Steam News text that identifies its PC build and explains the first key-remapping release. Hotfix 1.0.1 is described in a detailed creator breakdown and a dated third-party update tracker, but the complete official 1.0.1 body was not recovered in this collection. The distinction matters because a secondary summary can describe a real update without replacing the final platform notes.

The collection was reviewed on September 13, 2026, shortly after the game's launch period. A page captured from a community update describes Hotfix 1.0.1 as planned for that week, while another dated tracker describes it as live shortly afterward. Those records show the sequence of communication, but only a fresh official platform check can establish the current build for every reader. Future revisions should preserve the publication date and platform scope of each entry instead of presenting the archive as one undated list.

The official Steam announcement says Patch 1.0.0.1 passed testing and shipped to PC as build 162350. Its central feature was an Alpha version of keyboard-and-mouse binding support released before the team considered the system fully polished. Players could rebind available actions, restore default bindings, and adjust mouse sensitivity through the keyboard settings and a custom keyboard profile. The announcement framed this as an early response to player feedback rather than the finished form of control customization.

The same official note names three advanced behaviors that were not part of that Alpha release. It did not include assigning multiple keys to one action, double-tap inputs, or hold inputs. The developers said they intended to continue improving and expanding keybinding support, without attaching a final completion date to those features. A current guide should therefore describe what the captured patch added and avoid claiming that every requested binding option is now available.

The secondary Hotfix 1.0.1 breakdown reports rolling backup saves intended to provide another recovery layer when a save becomes corrupted or cannot load. It also describes fixes for situations in which player progression could reset unexpectedly. The same report says save synchronization between Steam Deck and PC was addressed for players using the same Steam account. These are material claims, but they should remain tied to the dated hotfix snapshot until the complete official notes are available in the source archive.

The hotfix report does not state that every possible save or progression problem is eliminated. It explicitly says additional reports were still under investigation, which is important for a run-based game built around permanent equipment and character progress. Players encountering a new issue should avoid treating an old fix category as proof that their specific case cannot occur. A patch archive should record both resolved cases and outstanding investigation language without turning either into an unsupported reliability percentage.

The secondary breakdown groups several fixes around two-player online co-op. It reports that a host option could remain unavailable after reconnecting to online services and that accepting a platform invite could leave a player stuck at the title screen. It also describes a case where a downed player could fail to revive at an activated Nexus Gate. These entries concern distinct points in the session flow, so they should not be compressed into a broad claim that all co-op problems were fixed.

The report further says in-run progress can persist for the client, allowing the joining player to continue after the shared session ends. It also mentions work on synchronization issues that could make a cooperative session unreliable. The captured roadmap still lists further co-op and crossplay work after 1.0.1, showing that the hotfix was not presented as the last multiplayer update. Current matchmaking, reconnection, and client-progression behavior should be checked on the live build before troubleshooting advice is made absolute.

Camera behavior was already listed as an urgent concern in the official 1.0.0.1 follow-up section. The later secondary hotfix report describes lock-on changes for large stationary bosses and further adjustments around large or elite enemies. Its stated aim is to reduce unwanted movement and make attacks easier to read without changing the underlying encounter. The report also says this work lays groundwork for later improvements involving large enemies, interiors, occlusion, and collision.

Boss names in automatic captions are not reliable enough to serve as a canonical encounter list. One secondary description names Tyrigon and the Dry Rot King, while the automatic transcript renders at least one name differently. The patch page can accurately describe the category of camera work without guessing at a misspelled proper noun. Detailed boss-specific notes should wait for an official text source or a direct in-game verification of the exact name and affected behavior.

The secondary 1.0.1 report describes crash fixes across Steam, Epic Games Store, PlayStation 5, Xbox Series X and S, and Steam Deck. It also names a specific crash during an Egregore encounter, although the precise boss spelling should be checked against official text. Steam Deck received a reported fix for losing menu controls as well as the save-sync change shared with PC. These entries show broad platform coverage, but they do not guarantee identical performance or eliminate every hardware-specific crash.

The secondary hotfix summary reports that interaction prompts and HUD button icons were updated to reflect custom keybindings more consistently. It also describes separate left and right Shift icons, a cancel option in keyboard remapping screens, and a correction for assigning Escape to a custom action. Those points extend the Alpha foundation introduced in Patch 1.0.0.1. They should not be interpreted as confirmation that multiple bindings, double-tap inputs, or hold inputs were added unless newer official notes say so.

The same snapshot includes HUD scaling options, improved interface scaling for high-resolution displays, status-effect icon fixes, and corrections to several results or mission screens. These are interface-level changes rather than evidence of new combat rules. A corrected display may reveal existing information more clearly without changing the value behind it. When a patch page describes a UI correction, it should avoid inferring a hidden balance adjustment that the captured notes never mention.

The captured development update originally targeted Hotfix 1.0.1 for the week of its announcement, with a fallback to early the following week if final testing or platform approval caused a delay. It placed Hotfix 1.0.2 later in September and Update 1.1 later in October. A developer reply characterized the first two hotfixes as issue-focused and 1.1 as the point where larger quality-of-life changes could begin. Those are announced targets rather than guaranteed release receipts, so the archive must preserve their planned status until official publication is checked.

The launch-day Steam discussion identifies Team Metal as actively monitoring player reports and links to the current Known Issues page. It also directs unresolved bugs and technical problems to the ProbablyMonsters support site, where reports can reach the development team with useful diagnostic information. Individual discussion replies mention controls, camera behavior, co-op symptoms, progression, and performance, but those comments are not a measured incident database. The official post should remain the authority for where to report a problem, while comments serve only as dated examples.

Patch notes are most useful when each entry records the version, platform scope, evidence date, and whether the change is confirmed or merely planned. Readers should compare their displayed game build with the relevant platform notice before applying old troubleshooting advice. A fix shipped for one reproducible case may not cover a new symptom with a different cause. This page therefore reports the captured change history without promising that an update guarantees stability, restores every lost save, or resolves all co-op configurations.