BG3 Mods

BG3 Mods / Fixes

Troubleshooting · Every common failure

BG3 mods not working: match the symptom, then fix it

Load-order overrides, missing frameworks, saves that hang on load, and the post-patch failures that look like corruption but are not.

Start with the symptom, not the theory

Most mod failures look unique and are not. Four of them account for almost everything, and each has a different fix. Find your symptom, then read the section for it.

Symptom Usual cause First move
Mod shows in the manager and does nothing Load order: something below it overwrites the change Move it lower, find the mod it conflicts with
Game will not launch at all Missing dependency, or a mod built for an older patch Disable the newest mod, reinstall the framework it needs
Save hangs on load A mod that wrote the save is gone or changed version Reinstall that mod at the same version
Crash in character creation Two cosmetic or race mods fighting for one slot Keep one per category, add back one at a time
Fine yesterday, broken after a patch Script mods waiting on their authors Load without updating, then update one at a time

"Installed but nothing happened"

Nine times out of ten this is load order, not a broken mod. The list is read top to bottom and later entries win, so a mod can be installed correctly, enabled correctly, and still do nothing, because something further down is overwriting it. Reinstalling, verifying files or blaming the mod changes none of that.

What to do: move it below the mod it conflicts with, keep compatibility patches at the bottom, then confirm it shows a version number in the manager rather than a blank entry. A blank entry means the game never read the file at all, which is a different failure.

The full sequence, including the export step people skip, is in the mod manager and load order guide.

The game will not launch

A modded game that dies before the main menu almost always has a missing dependency. Frameworks are the usual culprit, because they are the one download people treat as optional: a mod page lists them under Requirements, the user installs the feature mod and skips the framework, and the game closes on launch with no message.

What to do, in order:

  1. Disable the mod you added most recently.
  2. Re-read its Requirements box and install every entry, in the order listed.
  3. If the framework is installed, check that it matches your game patch. Script extenders are rebuilt after patches, and an extension built for the previous patch will fail quietly.
  4. Start the game from the mod manager, not from Steam. The Steam launch skips the manager's order on some setups.

If the game reaches the menu but dies when you load a save, that is the next section.

The save hangs on load

A save records which mods wrote it. Remove one of those mods and the save waits for data that will never arrive: the loading bar stops at a fixed point, or the screen goes black after the narrator finishes.

There are only two honest fixes:

  • Put the mod back, at the exact version the save was written with. An older or newer version may load, but it can also change internal IDs and leave you with a save that reads as corrupted.
  • Accept the save as written off and start a new run. This is the real cost of removing a mod mid-campaign, and it is why the ordering advice on this site keeps pushing profiles: a profile that stays stable per run is cheaper than a repair.

What does not work: loading an earlier save from the same run. The mod list is stored per save, but the content changes upstream, so the earlier save hangs the same way.

It worked yesterday: what a patch breaks

When the base game patches, it changes code that script mods hook into. Data-only mods (items, cosmetics, classes that only add rows) usually survive. Anything that patches game logic needs its author to rebuild it.

The order that avoids a lost evening:

  1. Load the game first, without updating anything. You want to see what still works, not what the newest mod versions promise.
  2. Update the framework first, then class and UI mods, then the rest, starting the game between batches.
  3. Check the mod pages before you update. A mod that has not been updated since the patch is a known risk; a mod whose author has announced a rewrite is a bigger one.
  4. Keep a copy of the save folder before experimenting. If a run matters to you, that copy is the only thing that makes experimenting safe.

What console players can and cannot fix

On PS5 and Xbox everything comes from the in-game manager, which means no manual load order files, no external frameworks and no custom campaigns. Most failures on console are simpler: a mod was removed from the catalogue, or it has not been uploaded for the current patch. You cannot fix either from your side — you wait, or you play without it. What the console catalogue does and does not contain.

When to stop fixing and rebuild

Rebuild when the save needs three or more mods you cannot restore, or when the game launches and immediately crashes in the same place twice in a row. At that point the time cost of another fix attempt is higher than a fresh install.

Rebuilding is not reinstalling: the game files are fine. What you rebuild is the mod list.

  1. Create a new profile with only the frameworks.
  2. Add mods in batches of five, starting the game and saving after each batch.
  3. When a batch breaks something, the culprit is one of those five, and you found it in ten minutes instead of an evening.
  4. Once the list is stable, export the order and stop changing it mid-run.

A 60-second triage you can run every time

  1. Did the problem start within one hour of a change? Undo that change.
  2. Does the mod show a version in the manager? If not, the game never read the file.
  3. Do two enabled mods touch the same system? Move the one you want to win lower.
  4. Did the base game patch since it last worked? Then it is the patch, not your install.
  5. Does the save load with only the frameworks enabled? If not, the save is the problem, not the mods.
Ⅰ

Common questions

Why do my BG3 mods stop working after an update?

A game patch changes code the mods hook into. Script mods need an update from their author before they work again; cosmetic and data-only mods are usually less affected.

Can I fix a save that needs a removed mod?

Usually not cleanly. The save records which mods wrote it, so the practical choices are reinstalling the mod or starting a new run.

Does load order matter if I only use a few mods?

Yes, as soon as two of them touch the same system. Two mods editing the same spell or class table conflict regardless of how small your list is.

Why does my game crash in character creation?

Usually two cosmetic or race mods competing for the same slot. Disable all but one per category and add them back one at a time.

Ⅱ

Keep reading