Modding & Tooling Starter

A stable mod stack starts with a clean baseline: clear saves you care about, verify your game files, and decide how you’ll back out if something breaks. This starter walks through a conservative setup that keeps achievements intact on vanilla saves while still giving you QoL upgrades.

Pre-flight checklist

• Verify files in Steam/GOG and launch once unmodded.

• Back up saves + Configs before adding anything. Keep a second copy in cloud or a separate drive.

• Disable overlays (Rivatuner/Discord) if you see injector conflicts. Add Bannerlord to AV allowlists.

• Read the current patch notes so you know which branch your mods target. See Patch Notes & Version Differences.

Pick your manager (and profiles)

• Bannerlord launcher: fine for a handful of mods; limited profile support.

• Vortex: profiles, deployment, and conflict flags. Great once you understand staging folders.

• Manual: only if you track every file. Use for tiny testing pairs.

• Create a vanilla profile and a modded profile. If an update lands, you can flip back to vanilla instantly to keep playing.

• Load order starter: Native → language packs → Harmony → ButterLib → UIExtenderEx → Mod Configuration Menu → UI/QoL → content/gameplay.

Links to dig deeper: Modding Basics, Mods & Tools Overview, Modding & Best Mods.

Essential frameworks (don’t skip)

• Harmony: patching backbone; keep it first under Native.

• ButterLib: shared library for UI/gameplay mods.

• UIExtenderEx: required for most interface tweaks.

• Mod Configuration Menu: unified settings page inside the Options menu.

• If a mod bundles an outdated version, prefer the latest standalone release to avoid crashes.

Safe starter pack (achievements-friendly)

Focus on QoL over overhaul:

• Camera/Gamepad tweaks; banner/party sorting utilities.

• Troop sorting and encyclopedia filters for recruitment runs (pairs well with Troop Recruitment and Development).

• UI performance fixes paired with Performance & Stability Tips and Performance & Optimization.

• Non-cheaty info panels (battle terrain preview, perk tooltips). Test in a custom battle before career saves.

Handling patches and branches

• Stick to the release branch unless a mod specifically supports beta. If mods lag behind, consider rolling back via Steam Betas until authors catch up.

• Keep a small CHANGELOG.md noting mod names, versions, and install date. Helps pinpoint breakage.

• After updates, launch with only frameworks enabled. If stable, re-enable QoL in batches.

Troubleshooting & rollback

• Crashing on load? Remove the last added mod first; delete its config files in Documents\Mount and Blade II Bannerlord\Configs if they remain.

• Use a short stress test: 500v500 custom battle, then a town enter/exit loop. If you pass, your campaign is likely safe.

• Keep a clean saves folder copied before each major mod change.

• Crash logs mention missing dependencies? Reinstall frameworks in order and verify game files again.

• If you’re totally stuck, revert to the vanilla profile and play while waiting for fixes; use Cheats & Console Commands only on disposable saves.

Quick checklist before adding more

• Vanilla profile launches? ✅

• Frameworks present and updated? ✅

• Backup of saves/configs? ✅

• Mods enabled in small batches with notes? ✅

• Passed a 30-minute stability run? ✅

Next stops: Controls & UI Setup, Beginner's Guide, Wiki Navigation Hub.