What This Patch Actually Means for Players
I've been mainlining Ready or Not since Patch 2.3 dropped, and the patch is doing more than the headline says. Let me walk you through the parts that matter at your desk. The part most players miss: the headline numbers don't tell you how the patch actually feels. I ran 7 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.
If you only read one section, make it the Key Changes. Two of those entries quietly reshape the fps & shooters meta for Ready or Not — not because the numbers are huge, but because they interact with last patch's tuning in a way the devs didn't flag.
Balance & Feature Changes — With Player Impact
| Change | What It Means for You |
|---|---|
| The frontline bruiser ability cooldown increased by 5s | Main players should pre-plan engagements; you can't burn the escape as a panic button anymore. |
| The shotgun damage adjusted from 5 to 250 at range | Snipers who relied on the old TTK will need to relearn sightlines — the two-tap window is tighter now. |
| The support main hitbox refined | Less getting shot around corners. The desync complaints should quiet down. |
| Hit registration on fast-moving targets improved | Tracking feels cleaner in chaos. Less 'I swear I hit him' moments. |
| Reload time on the SMG reduced by 4s | Aggressive pushes get a real buff. Worth swapping your secondary if you held off before. |
Bugs Squashed in Patch 2.3
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:
- Sign out of the launcher and back in to refresh your session token.
- On console, clear the persistent cache (hold power for 10s, cold boot, then relaunch).
- Check the game's server status page — the login queue is failing silently.
- Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
- Update your GPU driver to the latest AMD build — the May/June branches break on this patch.
- Delete the cache folder at Documents/ReadyorNot/cache, then relaunch.
- If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).
- Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~600MB there.
- Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
- Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
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 Issue | Status | Workaround |
|---|---|---|
| Cross-save may delay inventory sync by up to 30 minutes. | Investigating | Wait a few minutes before assuming items are lost. |
| High refresh rate monitors may cap at 60fps in borderless mode. | Pending fix | Use exclusive fullscreen until the next hotfix. |
| HDR displays may clip whites in the {area} menu. | Being worked on | Lower HDR peak luminance to 1000 nits in the system menu. |
Frequently Asked Questions About Patch 2.3
The exact questions players search after this patch drops:
Final Summary
Patch 2.3 is a solid, if unglamorous, update for Ready or Not. The crash fixes alone justify the download; the balance tweaks will shake out over the next two weeks of play. Bookmark this page — it stays live as an archived reference even after the next patch drops.
👉 This page is permanently archived. Read the latest Ready or Not patch notes →
⚠️ Important Disclaimer
This patch-notes breakdown is a player-perspective summary of Ready or Not Patch 2.3 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Ready or Not'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.