Crimson Moon Known Issues — Official List and Hotfix Status

What issues has the team officially confirmed?

The developers maintain an official Known Issues page, which lists what it calls “some of the key issues we’re currently working to address” after launch. As of that page’s September 1 content update — unchanged when last checked October 19 — the confirmed list covers five areas. The right-hand column shows where each area stands after Hotfix 1.0.1 (September 11); the section below adds what Hotfix 1.0.2 (October 1) changed on top:

Area	Confirmed issues (Sept 1 list)	After Hotfix 1.0.1
Stability & performance	Crashes during combat and general gameplay (some tied to ray tracing and specific encounters); a host-side crash entering the second arena of Ramshorn Keep; shader-compilation stuttering on the Epic Games Store version	“a number of crashes” fixed across all platforms, including the Egregore boss-fight crash; the Ramshorn Keep arena crash and ray-tracing crashes are not explicitly named
Multiplayer & co-op	An incorrect “Player has left the session” message; clients freezing or disconnecting in Moore Manor; accepting a co-op invite can leave the joining player stuck on the title screen; mission progress not always awarded to the host	Title-screen lock after invites fixed; Nexus Gate revives fixed; various co-op desyncs fixed; the false “left the session” message, Moore Manor freezes and host mission progress are not explicitly named
Saves & accounts	An account issue that can block the Main Menu from loading; saves not always syncing between Steam and Steam Deck; existing save data can be lost when updating the game	Rolling backup saves added plus fixes for progression being unintentionally reset; Steam Deck/PC sync fixed; the team “continue[s] to investigate further reports of save and progression loss”; the Main Menu account issue is not explicitly named
UI & HUD	Duplicate boss health bars; XP values showing decimal places; HUD notifications repeating; Mission Failed screen problems; Friends List elements missing on PS5 and the Epic Games Store; oversized loot interaction areas	Duplicate Tyrigon health bar fixed; XP decimals fixed; quest-notification spam fixed; Mission Failed difficulty skulls fixed; item pickup range reduced; the PS5/EGS Friends List issue is not explicitly named
Bosses & enemies	Felwyl’s death sequence can sometimes be skipped; an extra health bar can appear during the Tyrigon encounter	Both fixed — see below

Is the save data loss bug being fixed?

It was the one issue the team explicitly labeled high-priority — “This is a high-priority issue and a fix is being prepared for the upcoming hotfix” — and the fix work has now shipped in two waves.

Until that rework lands, the 1.0.2 announcement asks players to meet it halfway. Many of the remaining issues, it says, “occur when moving between devices”, so the recommendations are to play “on a single device where possible”, avoid “switching devices when playing the same save” — and PC players “may also want to create a local backup of your save as an additional precaution.” Full patch-by-patch detail: patch notes guide.

What did Hotfix 1.0.1 fix?

Hotfix 1.0.1 is the team’s first major post-launch hotfix, with official patch notes published September 11, 2026. Its fix list spans Steam, the Epic Games Store, PS5, Xbox Series X|S and Steam Deck, and it explicitly names many issues from the list above — the table maps fix by fix. The full ten-section list (camera, HUD scaling, keybinding cleanup, store fixes and more) is covered in the patch notes guide.

Notably, the official Known Issues page itself has not been edited since September 1 — its “preparing Hotfix 1.0.1” wording is now behind the shipped patch notes, which are the newer authoritative source.

What did Hotfix 1.0.2 fix from this list?

Hotfix 1.0.2 went live October 1, 2026, and delivered the key areas the September 25 announcement promised — with notes that name fixes well beyond 1.0.1’s list:

• Saves — progress and unlock information no longer carries between save files; the Save Overwrite screen now identifies the affected save and defaults to the safer “No”; the Xbox “Save upload failed” warning loop is fixed (full outlook above).
• Co-op — Quickplay works; the “Game Not Open to Join” join error is fixed; Lore Scrolls can now be collected in co-op, the exact gap the September 25 announcement called out; the downed-and-revive flow improved.
• Run-blocking — Clear the Area objectives are more reliable, with enemies now spawning and making their way towards you as intended; a Clear All Enemies objective can no longer complete with the final enemy alive.
• Boons & Weapon Arts — Angelic Bulwark’s shield functions; Avenging Pestilence no longer double-deals damage; Ground Slam arts no longer hit twice without Aftershock Technique; many more named in the patch notes.
• Stability — multiple crashes fixed per platform, including the Cardinal Mathias flask crash and the death-cinematic fall-through.

Still not explicitly named in either hotfix’s notes: the false “Player has left the session” message, the Moore Manor client freezes, host mission progress not always being awarded, and the Main Menu account issue. Treat those as open.

Which boss fights had confirmed issues?

Three bosses are now named across the official list and the hotfix notes — and all three named issues are fixed as of 1.0.1:

• Felwyl — “Felwyl’s death sequence can sometimes be skipped when defeated with certain attacks”; 1.0.1 fixed it being skipped “when defeating him during his lightning attack.” See the Felwyl boss guide.
• Tyrigon — “An additional health bar can appear during the Tyrigon encounter”; 1.0.1 fixed “a duplicate health bar appearing when locking onto Tyrigon at the beginning of the fight”, and also improved the lock-on camera against him. The host-side crash list also included the second arena of Ramshorn Keep, Tyrigon’s keep — that specific crash is not explicitly named in the 1.0.1 notes. See the Tyrigon boss guide.
• The Flesh-Wrought Egregore — not on the September 1 issue list, but the 1.0.1 notes fixed “a crash that could occur during the Egregore boss fight.” See the Egregore boss guide.

How does co-op run while issues persist?

Better than at launch, officially. Hotfix 1.0.1 fixed players getting stuck on the title screen after accepting a platform invite, downed players sometimes not being revived at activated Nexus Gates, the Host option staying unavailable after reconnecting, and various desyncs. It also changed a rule: “Co-op run progress will now also persist for clients, allowing them to continue the run solo.”

Hotfix 1.0.2 then shipped the largest co-op fix wave yet — Quickplay, the “Game Not Open to Join” join error, clients dealing reduced damage, stuck players, the downed-and-revive flow and Lore Scroll collection among them (list above). What remains not explicitly named in either hotfix: the false “Player has left the session” message, the Moore Manor client freezes and host mission progress not always being awarded. For how the shared-life co-op system itself works, see the co-op guide.

Is your “bug” actually a game system?

Maybe. In a launch-week post, the team noted that “some things being reported as bugs are actually game systems” that are not yet explained clearly enough in-game, and pointed players to an official wiki for guidance on systems and mechanics. Before reporting a bug, it is worth checking whether a run, build or Ward mechanic explains what you are seeing. Hotfix 1.0.2 (October 1) delivered part of that clarity — clearer Status Effect text for Tempo, Poisoned, Freeze, Marked and Sundered, plus more readable Boon descriptions — with further Boon information work aimed at Patch 1.1.