Manor Lords Patch 3.1 Notes | Bug Fixes & Changes

Player Take

What This Patch Actually Means for Players

Pulled the patch notes apart so you don't have to. Here's what Manor Lords's Patch 3.1 actually changes the moment you boot it up. Reading between the lines: the headline numbers don't tell you how the patch actually feels. I ran 9 hours across 3 sessions on PC and a couple of these changes ripple further than the notes suggest.

Netcode feels more honest after Patch 3.1. 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.

Key Changes

Balance & Feature Changes — With Player Impact

Change	What It Means for You
Pathfinding on sieges fixed	Units stop dancing at the gate. Sieges are finally playable.
Multiplayer desync on simultaneous turns fixed	Cross-play lobbies should stop falling apart mid-match.
AI diplomacy logic improved — fewer irrational declarations	Alliances feel less random. Backstabbing is telegraphed better.
The island coalition late-game tech tree rebalanced	The doomed-to-lose-until-minute-40 faction has a fighting chance earlier.
The siege unit cost raised by 12	Spam builds get checked. You have to commit to a real army comp.

Bug Fixes

Bugs Squashed in Patch 3.1

🐛Corrected a camera glitch triggered when entering the hub on a mount.

Player impact: Quality-of-life win the community has wanted for weeks.

🐛Fixed an achievement not unlocking when the condition was met offline.

Player impact: Closes a loophole that was skewing leaderboards.

🐛Resolved an issue where keybindings reset after every restart.

Player impact: Removes a recurring frustration for endgame players.

🐛Resolved an issue where the stamina system would silently fail under high ping.

Player impact: Quality-of-life win the community has wanted for weeks.

Crash & Error Fixes

How to Fix Crashes & Errors After Patch 3.1

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 3.1

Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
Update your GPU driver to the latest Intel build — the May/June branches break on this patch.
Delete the cache folder at Documents/ManorLords/cache, then relaunch.
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.

💥Infinite loading screen after the patch

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.

Quick workaround: Switching to a wired connection and avoiding VPNs clears the hang for most players.

💥Blue screen / driver timeout (amdkmdag / nvlddmkm) mid-match

Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 3.1.
Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
Reinstall the driver using DDU (Display Driver Uninstaller) for a clean slate.

Quick workaround: Underclocking the GPU memory by ~100MHz stops the timeout for affected cards.

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 Issue	Status	Workaround
Friends list intermittently shows offline users as online.	Investigating	Reloading the social tab usually clears it.
Controller rumble stays on after disconnecting a pad.	Known	Reconnect and disconnect the controller again to reset it.
Voice chat volume resets between matches.	Known	Re-check your voice settings each session for now.
HDR displays may clip whites in the {area} menu.	Being worked on	Lower HDR peak luminance to 1000 nits in the system menu.

Server Maintenance

Downtime & Schedule

Scheduled: 2026-03-14 from 07:00 UTC for approximately 5 hours.

Details: Matchmaking disabled during the window. Manor Lords ranks will not decay for missed placement games during downtime.

Compensation: A small login bonus will be mailed after the window closes.

FAQ

Frequently Asked Questions About Patch 3.1

The exact questions players search after this patch drops:

QHow do I fix the crash after the Patch 3.1 update?−

AStart by verifying game files and updating your GPU driver — the Patch 3.1 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.

QWhen is the next patch after Patch 3.1?+

ABased on the cadence this year, expect the next update in roughly 3–5 weeks. Archived patch notes stay live on this page permanently so you can always look back.

QIs my save file compatible with Patch 3.1?+

AYes. Patch 3.1 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.

QWhy is my FPS lower after Patch 3.1?+

AThe patch added denser the new zone assets. Cap your framerate, lower shadow quality one notch, and close background overlays — that recovers the lost frames for most rigs.

QWere any the parry window nerfed in Patch 3.1?+

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.

Bottom Line

Final Summary

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

👉 This page is permanently archived. Read the latest Manor Lords patch notes →

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of Manor Lords Patch 3.1 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Manor Lords'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.