Player Take

What This Patch Actually Means for Players

Logged about six hours on Slay the Spire since Patch 2.3 hit the servers. The patch notes read one way; the actual feel is another. Here's the gap. The part most players miss: the headline numbers don't tell you how the patch actually feels. I ran 8 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.

Netcode feels more honest after Patch 2.3. I'm getting fewer 'how did that register?' moments, which is the boring but important win. The flashy balance changes get the clicks; the rollback fixes are why you'll actually stay.

Advertisement
Key Changes

Balance & Feature Changes — With Player Impact

ChangeWhat It Means for You
Matchmaking rating updated for casualSmurf queues tighten. New players face fewer blowouts.
The board wipe mana cost raised by 15The ubiquitous auto-include loses a slot. Deck diversity should rise.
The finisher spell text clarified and effect normalizedEdge-case interactions resolved. Trust the printed text now.
Bug Fixes

Bugs Squashed in Patch 2.3

🐛Corrected a UI freeze when scrolling the settings menu on controllers.
Player impact: Removes a recurring frustration for endgame players.
🐛Resolved audio cutting out during the daily dungeon on certain sound cards.
Player impact: Removes a recurring frustration for endgame players.
🐛Fixed duplicated the equipped relic appearing after a server reconnect.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Fixed the co-op leaderboard not updating after a completed match.
Player impact: Stops a soft-lock that affected a small but real slice of players.
🐛Fixed a crash when opening the inventory immediately after a loading screen.
Player impact: Closes a loophole that was skewing leaderboards.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 2.3

Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:

💥Game closes to desktop right after the splash screen on Patch 2.3
  1. Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
  2. Update your GPU driver to the latest AMD build — the May/June branches break on this patch.
  3. Delete the cache folder at Documents/SlaytheSpire/cache, then relaunch.
  4. If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).
Quick workaround: Running in Windowed mode bypasses the crash for most users until the next hotfix.
💥Crash on entering the hub or fast-traveling
  1. Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~400MB there.
  2. Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
  3. Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
Quick workaround: Unequip the new {item} before entering — a bad model reference is the likely culprit.
Advertisement
Known Issues

Known Issues Still Being Worked On

These problems are acknowledged but not yet fixed. Here's the status and a temp workaround for each:

Known IssueStatusWorkaround
Cross-save may delay inventory sync by up to 25 minutes.InvestigatingWait a few minutes before assuming items are lost.
Controller rumble stays on after disconnecting a pad.KnownReconnect and disconnect the controller again to reset it.
Some players still see the old {character}/{weapon} stats until a full client restart.AcknowledgedRestart the client after the patch downloads.
Friends list intermittently shows offline users as online.InvestigatingReloading the social tab usually clears it.
FAQ

Frequently Asked Questions About Patch 2.3

The exact questions players search after this patch drops:

AYes. Patch 2.3 is backward-compatible with saves from the previous version. Back up your save folder before booting up, just in case — the patch rewrites a few the parry window fields on first load.
AA few. Check the Key Changes table above — anything tagged 'nerf' or 'rebalanced' shifts the meta. Nothing got gutted, but two popular setups lost some uptime.
AStart by verifying game files and updating your GPU driver — the Patch 2.3 build raised VRAM use, so dropping textures from Ultra to High fixes most splash and fast-travel crashes. The full step-by-step is in the Crash & Error Fixes section above.
AThe patch added denser the menu assets. Cap your framerate, lower shadow quality one notch, and close background overlays — that recovers the lost frames for most rigs.
Bottom Line

Final Summary

Net positive for Slay the Spire players. A few rough edges remain (see Known Issues), but the core experience is more stable post-Patch 2.3. I'll keep this archived page updated if any hotfixes follow.

👉 This page is permanently archived. Read the latest Slay the Spire patch notes →

More Slay the Spire Patches

Other Slay the Spire Patch Notes

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of Slay the Spire Patch 2.3 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Slay the Spire's developer or publisher. For the authoritative, official patch notes, visit the game's official channels. All trademarks belong to their respective owners. Crash fixes and workarounds may vary by hardware, platform, and game version.