Mod Baldur's Gate 3 with AI: six contributor reports

Six contributor reports cover personal single-player changes and troubleshooting. Every note is marked working, but each has its own verification limits. The versions below are historical reports, not a compatibility matrix or tests by this site.

Act 2 loading diagnosis

A heavily modded save could not enter Act 2. On Steam, Windows 10, Patch 8 hotfix, the recorded DX11 executable was 4.73.98.727; Many More Monsters 3.5.2.0 and 4.4.3.0 both reproduced the failure. The data route used LSLib Divine 1.20.4, Script Extender v32 logs, a Python minidump parser and capstone. Repacking progressively smaller sets of level entities identified one NPC whose layer could not resolve. Removing that entity from the personal pak let both a fresh character and the long save load Act 2. The reason the layer fails, and whether a later mod update fixes it, remain unverified. Source: act-2-load-hang-one-bad-level-layer.md.

Act 2 never loads (hang at 50% or crash)

Symptom → cause → reported fix: a frozen load bar or crash shared the same fault; one NPC in Many More Monsters had an unresolved level layer. Bisecting repacked copies isolated it, and a local copy without that entity loaded. Clean static scans did not establish that runtime loading was safe. Keep a pristine pak and use throwaway characters for removal tests; an existing save may require its recorded modules. Source: act-2-load-hang-one-bad-level-layer.md.

Generated wardrobe by body type

The wardrobe project classified installed clothing mods and generated containers summoned on demand, rather than filling one enormous chest. Its data route adds a small Script Extender Lua handler, using LSLib Divine 1.20.4, a PowerShell + bash generator pipeline, AV Item Shipment Framework (ISF) and Nexus Mods GraphQL API descriptions. The recorded environment is Steam on Windows, Patch 8 / Patch 8 hotfix, with Script Extender v32. Pilot and full builds worked in game; the largest containers and the exact cause of a control lock remain unresolved. Source: clothing-sorter-generated-wardrobe-by-body-type.md.

Scrolls became equippable and unusable.

Symptom → cause → reported fix: the generator made stubs for its own scrolls and gave them an armour type, shadowing the real definitions. Exclude local definitions from foreign-item stubs and reject duplicate entry names. Truncated names also collided; deterministic hash suffixes and uniqueness checks resolved those collisions. Keep generated UUIDs stable because saves reference them. Source: clothing-sorter-generated-wardrobe-by-body-type.md.

Custom outfits and visual assets

A personal outfit pak combined edited mod and vanilla meshes, materials, icons and cloth. This asset-only route did not require Script Extender. Work ran on Steam, Windows 10, from Patch 7 through Patch 8 hotfix, with LSLib Divine 1.18.7 / 1.20.4, Blender 4.0.2, Norbyte’s dos2de_collada_exporter (later v3.0.0), texconv and BG3 Modders Multitool. The human checked the items in game, including movement for cloth; some individual behaviors were only partly checked. Source: custom-outfits-visuals-materials-cloth-icons.md.

Missing MetaData

Symptom → cause → reported fix: the startup popup appeared when the icon registry was absent. Supply the registry entries corresponding to the icon files. Separately, copying another mod’s compiled shaders crashed startup; referencing the source material as a soft dependency fixed that case. Source: custom-outfits-visuals-materials-cloth-icons.md.

Device or resource busy

Symptom → cause → reported fix: deployment could not replace a loaded pak because the running game held it open. Check that the game has closed before replacing it. For garments disappearing at distance, the note instead corrected mismatched LOD distances and declared tiers; these are different symptoms. Source: custom-outfits-visuals-materials-cloth-icons.md.

Managing a large load order

The configuration-management report used LSLib Divine 1.20.4, Python, Script Extender and Native Mod Loader for a Steam, Windows 10 setup on Patch 8 / Patch 8 hotfix, with Script Extender v32. It edited backed-up XML and recovered a validated module order from save metadata. Install batches loaded and the save-based recovery became the working order; intermittent resets still had no isolated cause, and a photo-mode repair was not reported back from play. Source: managing-a-500-mod-load-order-by-hand.md.

Whole load order reset to one entry on launch, every time.

Symptom → cause → reported fix: malformed metadata in a self-made pak caused repeatable resets. Copy a working metadata structure and leave its dependency node empty rather than guessing values. This does not diagnose intermittent resets. Entries outside the correct Mods node were ignored, and renamed module folders required updating the Folder field as well as identity/version fields. Source: managing-a-500-mod-load-order-by-hand.md.

Gameplay and compatibility patches

Small data patches changed armour tiers, usable-item effects, spell behavior and starting equipment through stats, root templates, progressions and Osiris goals. The Windows Steam report spans Patch 7 to Patch 8 hotfix and names LSLib Divine 1.20.4, BG3 Modders Multitool and Python. Override patches had to load after their targets. Armour behavior, the feat item and class creation had human confirmation; several other shipped changes, including the revised Extra Attack patch and critical-hit immunity, were not reported back from play. Source: gameplay-and-compatibility-patches-stats-osiris.md.

Choices Pending

Symptom → cause → reported fix: a modded class inherited an equipment selector without the Null or Default options expected by Starting Equipment Selection. Replacing the affected progression rows under their original UUIDs with the compatible selector and default allowed class creation. For non-stacking damage reduction, the separate fix was bare reduction on separate armour-tier items rather than a condition-wrapped reduction. Source: gameplay-and-compatibility-patches-stats-osiris.md.

Personal weapon projects: Skyrim dagger, sheath and shields

The weapon report describes a personal port of Hravna - Dagger of the North by Danp, a scabbard using a belt from wesslen’s Modular Equipment, edits to the Deathwyrm sword from Falazure by onyx, naerys and mons, and generated visible-shield conversions. The asset-only route ran on Steam, Windows 10, in the Patch 7 era and Patch 8 hotfix. Named tools include Blender 3.6 LTS, niftools addon 0.1.1, Blender 4.0.2, Norbyte dos2de_collada_exporter, LSLib Divine 1.20.4, Blender Weapon Templates, texconv and Python. The human confirmed the dagger, scabbard, sword and shields from two source mods; the random-loot mod’s shields were not tried in play. Source: weapons-skyrim-dagger-port-sheath-bone-visible-shields.md.

STATUS_DLL_NOT_FOUND

Symptom → cause → reported fix: the portable Blender build used for NIF import lacked the VC++ runtime; the MSI installation worked. The report used the older Blender branch for that addon and a separate Blender setup for BG3 export. Source: weapons-skyrim-dagger-port-sheath-bone-visible-shields.md.

Scabbard and sheathed blade drift apart when walking.

Symptom → cause → reported fix: the scabbard followed the thigh while the sheathed blade followed the root. Weighting the scabbard to Root_M kept them aligned. The sword’s stowed position was corrected with a Dummy_Sheath bone rather than a change that moved its hand grip. Source: weapons-skyrim-dagger-port-sheath-bone-visible-shields.md.

These are reported personal asset projects. Game files and ripped assets must not be redistributed; this guide supplies no asset downloads or extraction instructions. Respect source creators’ permissions before sharing any original work. Source: CONTRIBUTING.md hard rules.

How to start your own mod

Install Universal Modder, then use the engine-research template with your owned Baldur’s Gate 3 installation and exact version. Back up saves and configuration before changes; keep gameplay work single-player and use a separate test save. Adapt the item or weapon template for one small slice, then ask for an observable in-game test and a record of what remains unverified. These are planning templates, not promises that the reported mod will work on another setup. Source: README rules and Try it.

Read merge games with AI before choosing a port or simulation, and use troubleshooting to compare the exact symptom with a named report.

Frequently asked questions

Are all six reports independently tested?

No. Their notes are marked working by the contributor, with individual checks and omissions described above. This site has not tested them.

Does the Act 2 fix apply to every load hang?

No. That report isolated one NPC and a level-layer failure in Many More Monsters. It leaves the reason for that layer failure unresolved.

Can I share the ported Skyrim dagger assets?

Do not redistribute game files or ripped assets. The report describes personal use and credits the source creators; it is not a download or sharing license.

Does every patch need Script Extender?

No. The outfit note says it is not required, the gameplay patches are data-based, and the wardrobe report uses a Script Extender handler. Follow the matching note.