Baldurs Gate 3 After Adding Mods Can’t Create Story | Fix

Quick context: You add a few mods to Baldur’s Gate 3, try to start a new run, and the game throws an “unable to create a working story” message or bounces you back to the main menu. Sometimes it even hints that your add-on setup is invalid. This feels like the game has bricked itself, especially when reinstalling or turning mods off does nothing.

This guide walks through why this happens and the safest path to fix it without wrecking your saves. You’ll see how to clean leftover mod files, repair the story scripts the game relies on, and rebuild a stable mod list so your next character can actually step out of the nautiloid.

What The Unable To Create A Working Story Error Means

Short answer in plain terms: the story system in BG3 can’t find the right scripts to run because something in your mod setup broke the data it expects. When that happens, the engine blocks character creation and refuses to load into the game world.

You’ll often see messages like “Unable to create a working story. Your add-on setup might be invalid,” or a warning that mods prevented the game from starting. This points straight at a mismatch between the base game files and whatever your mod manager is telling the game to load.

BG3’s story data needs a clean, consistent list of modules and scripts. Mods that touch spells, classes, races, UI, or campaign logic can alter that list. When a patch lands or a mod updates, those files can fall out of sync. The result is a story that can’t compile, so the game stops at the safest point it can: before you even leave character creation.

Steam, GOG, and other platforms all use the same core data. So if you see this story error across multiple attempts, assume the problem lives in your mod folders, your modsettings file, or the cache the game builds from them, not in your account or hardware.

Why Baldurs Gate 3 After Adding Mods Can’t Create Story Error Happens

Root cause overview: almost every “unable to create a working story” report traces back to one or more of these mod problems. Understanding them helps you pick the right fix instead of reinstalling the game in circles.

• Outdated mods — Mods built for older patches can reference scripts or assets that no longer exist, so the game chokes when it tries to load them at story compile time.
• Broken load order — A mod that should load before another ends up later in the list, so required data is missing when downstream mods run.
• Missing requirements — A content mod depends on a core library or framework you never installed, which leaves gaps in the story setup.
• Half-removed mods — Files remain in the Generated or Story folders even after you disable or delete a mod in your manager, so the game still sees traces of it.
• Corrupt cache files — BG3 stores compiled data; when this cache goes bad after crashes or patch updates, story creation can fail even with clean mods.
• Old saves with heavy mods — A save tied to missing mods can break when you try to continue that run or reuse the profile for a new story.

When you run into the baldurs gate 3 after adding mods can’t create story message, you are looking at one or more of those issues stacked together. The game is telling you that the add-on story layout no longer matches what its engine expects, so it refuses to move forward instead of letting you play a broken campaign.

Baldurs Gate 3 After Adding Mods Can’t Create Story Fix Steps

Game-saving plan: walk through these steps in order. Start with checks that cost you nothing, then move toward deeper file cleanup. Stop as soon as the game can start a new story cleanly.

Step 1: Back Up Saves And Mod Profile

• Copy your saves — Copy the Saves folder for BG3 to a safe spot on your drive so you can restore campaigns later even if you reset your mod setup.
• Archive the Mods folder — Zip up your current Mods folder and keep it on your desktop; this gives you a record of what you were running.
• Export load order — If your mod manager can export a load-order file or profile, save it now for reference.

Step 2: Test A Completely Vanilla Launch

• Disable all mods — In BG3 Mod Manager or the in-game mod menu, untick or remove every mod so the list is empty.
• Switch to story only — Make sure only the base game and official DLC entries stay active; no community add-ons should remain in the order.
• Start a fresh profile — Create a new profile, then try to start a new game. If the story loads, the base installation is fine and the issue sits in your mods.

Step 3: Clear Cache And Generated Files

Deeper fix: cleaning cached data can solve the error even when the vanilla test fails. BG3 keeps story and mod data in Generated and cache folders that can survive simple uninstall attempts.

• Close the game and manager — Exit BG3, your mod manager, and the launcher so no process keeps files locked.
• Delete Generated content — Open the BG3 profile directory and remove the Generated folder so the game rebuilds it on next launch.
• Remove cache folders — Delete the cache and temp folders for BG3 under your user AppData directory to flush old compiled data.
• Restart your PC — Reboot once to clear file locks and restart any services your launcher needs.

Step 4: Refresh modsettings.lsx

File reset: the modsettings.lsx file tells BG3 which add-ons to load and in what order. When this file references mods that no longer exist, story creation can fail.

• Locate modsettings — In your BG3 profile folder, find the modsettings.lsx file and copy it to a backup location.
• Delete the active file — Remove modsettings.lsx from the profile so the game or your mod manager can generate a new one.
• Launch without mods — Start BG3 with no external mods and let it rebuild a clean modsettings file based on base content only.

Step 5: Verify Game Files In Your Launcher

• Run file verification — On Steam, use the Verify integrity option; on GOG or other launchers use the matching repair feature.
• Wait for replacement downloads — Let the launcher redownload any missing or corrupt files from the servers.
• Test another new game — Try a fresh story with no mods again. If this works, the core game files and story data are healthy.

Step 6: Add A Known-Compatible Story Fix Mod (If Needed)

Targeted fix: some players only move past the story error once they install a small “mod fixer” style add-on built to help BG3 compile story data with mods present. Use this only from trusted mod hubs and match it to your current game patch.

• Check patch compatibility — Make sure the story fix mod you choose is listed as compatible with your current BG3 patch and platform.
• Place it at the top — In your load order, keep the fixer near the top, just after base entries, so other mods can use it.
• Test with only the fixer — Enable just that one mod and try a new game; if it works, the fixer and base game now agree on story data.

If you still see the baldurs gate 3 after adding mods can’t create story pop-up after all these steps, the safest move is to strip everything back to a clean profile and rebuild your mod list with stricter rules, which the next sections cover.

How To Clean BG3 Mods Safely Without Breaking Saves

Safe cleanup plan: cleaning mod data works best when you know which folders matter. BG3 spreads mod information across user folders and the game install directory, so you want to target the right spots instead of deleting random files.

Folder	Typical Path Hint	Main Action
Mods	User profile Documents BG3 folder	Remove disabled mods and keep only current ones
Generated	Same user profile BG3 directory	Delete to let the game rebuild story and cache data
Game Install	Steam or GOG library Baldur’s Gate 3 folder	Leave alone and use file verification for repairs

Folder-by-folder sweep: start with your user profile BG3 directory. Remove old mods that you no longer plan to use, then clear the Generated folder as described earlier. This cuts ties to half-removed add-ons that still lurk in compiled data.

Next, open your mod manager and refresh its view of active mods. Some tools have a “purge” or “clean” option that removes references to missing files. Use that before you enable anything again. This reduces the chance that a broken manifest will recreate the same bad story layout.

Let your launcher handle the game install folder. Manual edits there can cause fresh problems. Stick to the built-in repair or verify features when you need to replace base game files.

Rebuilding Your Mod List After Fixing The Error

Fresh start rule: once you can start a vanilla story again, rebuild your load order in small batches instead of throwing your entire old list back at the game. This keeps failures easy to trace.

• Group mods by type — Sort your mods into buckets such as visuals, UI, classes, spells, companions, or QoL tweaks.
• Install core tools first — Add mod manager support files, script extenders, or required frameworks before cosmetic content.
• Add a few at a time — Enable a small group, test a new game through the tutorial, then move on to the next batch.
• Skip known problem mods — Check recent comments on each mod page; leave out anything with fresh reports of story errors or patch issues.
• Keep a stable profile — Once you find a combo that works, save that load order separately and avoid changing it mid-playthrough.

When you see the error return after adding a specific batch, you know the culprit lives in that small set. Remove those mods, clean Generated again, and add them back one by one until you find the exact source. It takes time, but it saves you from wiping everything repeatedly.

Preventing Story Errors On New Playthroughs

Long-term plan: the best fix is not needing another emergency cleanup. A few simple habits make story errors far less likely on your next run.

• Match mods to patches — Before every big BG3 patch, read the mod descriptions and disable anything that has not been updated yet.
• Limit heavy script mods — Use only a few mods that rewrite story logic or core systems at a time; stack cosmetic ones on top instead.
• Dedicate profiles — Keep a separate profile for modded runs and another for near-vanilla, so saves stay tied to stable load orders.
• Back up before changes — Copy your Saves and Mods folders before installing a new batch so you can roll back if something breaks.
• Test on short sessions — Start a small throwaway campaign with new mods, reach the first camp, and see if anything behaves oddly.

If you treat mod changes like updates to a live project rather than small tweaks, you can keep Baldur’s Gate 3 fun and stable at the same time. The baldurs gate 3 after adding mods can’t create story problem almost always reflects a mismatch you can avoid with slower, more careful changes.

When A Full Reset Makes Sense

Last resort: sometimes months of experiments leave your BG3 folders packed with old data. If story errors keep coming back even after cleanups and careful load-order rebuilds, a full reset is worth the effort.

• Archive everything — Move Saves, Mods, and configuration files to an external folder so you can bring pieces back later if needed.
• Uninstall through the launcher — Remove BG3 from Steam, GOG, or your platform instead of deleting files by hand.
• Delete leftover folders — After uninstalling, manually remove any remaining BG3 user folders under Documents and AppData.
• Reinstall and test vanilla — Install BG3 again, launch with no mods, and confirm that a new story loads without any errors.
• Reintroduce only trusted mods — Bring back a small set of well-maintained mods, starting with the ones you rely on the most.

This reset takes time, yet it gives you back control. You get a known-good base game, a lean set of mods, and a far smaller chance of running into another story error right when you are ready to roll new characters.