BG3 Mods / Mod Manager
Setup · Load order · ProfilesBG3 Mod Manager and the load order that survives patches
The manager has one important job: writing the order into the game. Get that step right and most mod problems stop happening; skip it and nothing loads at all.
What the manager actually does
BG3 Mod Manager does one job that matters: it writes the load order into the game so the game reads mods in the sequence you chose. Everything else it offers, from profiles to archive importing, exists to make that job repeatable.
This is why "I copied the files into the mods folder and nothing happened" is the most common manual-install failure. The files are present, but the game has no instruction about what to load or in which order.
First-time setup
- Install the manager outside the game folder.
- Point it at your game install so it can find the data directory.
- Set the game data path and the mods path in the manager's preferences.
- Close the game. The manager cannot write the order while the game is running.
- Import your archives, enable them, then export the load order to the game.
That last step is the one people skip. Enabling a mod in the manager does nothing until the order is exported.
How load order is read
The list is read top to bottom and later entries win. If two mods both change the same record, the lower one replaces the other's change rather than merging with it. That is the whole mechanic, and it explains almost every "installed but no effect" report.
If you came here from a troubleshooting page, this is the answer nine times out of ten: the mod is not broken and does not need reinstalling, it is sitting above something that overwrites it.
A default order that works for most installs, top to bottom:
- Frameworks and libraries (the mods others depend on).
- UI overhauls.
- Class, subclass and spell additions.
- Item and equipment mods.
- Cosmetic mods.
- Compatibility patches, at the very bottom, so they get the last word on conflicts.
Custom campaigns are a special case: run them in their own profile with as few other mods as possible, so a conflict cannot be blamed on the campaign.
Profiles: the feature worth using
A profile is a saved mod list. Keep at least two: one for a modded main-story run, one for a custom campaign. Switching profiles is then a single action instead of enabling and disabling twenty mods and hoping you remembered the order.
When an update lands
A game patch invalidates script mods until their authors update them. After a patch:
- Load the game without updating mods first, and see what still works.
- Update mods one at a time, loading in between.
- If a save refuses to load, do not save over it; copy it aside before experimenting.
The manager will happily load mods built for an older patch. It has no way to know they are incompatible, and that is precisely the failure that looks like a corrupt save.
Common questions
Do I need BG3 Mod Manager or can I use Vortex?
Either works, since both write a load order for the game. BG3 Mod Manager is the more common choice for this game specifically, and most guides assume it.
Why does my mod show up but do nothing?
Almost always load order: a later mod is overwriting the change. Move it lower in its group, or below the mod it conflicts with.
Do I have to export the load order every time?
Every time you change the list, yes. The game reads the exported file, not the manager's screen.
Can I switch mod lists between saves?
Yes, with profiles. Keep a separate profile per kind of run so you are not rebuilding the list by hand.