DEV Community

Andy Wu
Andy Wu

Posted on

How Baldur's Gate 3 Script Extender Works — Install, Auto-Update, and After a Patch

A lot of Baldur's Gate 3 "this mod does nothing" reports are not about the .pak at all. They are about a Windows DLL that has to sit next to the game executable, and about whether that DLL still matches the game after a hotfix.

Norbyte's Script Extender (usually shortened to SE) adds Lua and Osiris scripting support to the game. Many class packs, spell frameworks, and other "deep" PC mods list it as a requirement. It is not a .pak, it is not installed by the in-game Mod Manager, and it has no official support on consoles or on macOS.

What it actually is

On Windows, the installer is a file named DWrite.dll. You place it in the game's bin folder, the same folder as the game executables. On a typical Steam install that is:

C:\Program Files (x86)\Steam\steamapps\common\Baldurs Gate 3\bin

The first launch after that downloads or applies the current extender. If it loaded, a Script Extender version string appears on the main menu.

That GitHub file is an updater. Norbyte's release notes say a new GitHub release means the updater changed, not that you must re-download after every Script Extender revision. When the game can reach GitHub, the extender updates itself on launch. Trust the version on the main menu, not a release page you bookmarked last month.

As of 12 October 2026, the latest updater package on GitHub is tagged v33. The last public Larian hotfix I could confirm (29 September 2026, per bg3.wiki's patch notes) is game version 4.1.1.7631656. Those numbers move independently. After any game or extender update, check the main menu and the requirement line on each Script Extender-dependent mod. This article does not claim any specific mod was verified against that build.

Official sources only

Download the extender from Norbyte's GitHub releases, or use BG3 Mod Manager's Tools → Download & Extract Script Extender command, which pulls from the same official source. The BG3 Modding Community Wiki is explicit: do not take Script Extender from Nexus Mods or from any other re-upload.

After the manager reports that it extracted the file, close the manager, launch the game once, then refresh the manager. It may still warn that Script Extender is missing until that first launch has happened.

Antivirus tools sometimes quarantine DWrite.dll because it loads into the game process. If the file vanishes from bin between sessions, check quarantine before you reinstall anything else.

Linux and Steam Deck

Script Extender is a Windows DLL. It works on Linux and on Steam Deck only under Proton, not under the native Linux build. Official instructions are: put DWrite.dll in the game bin folder and set Steam launch options to:

WINEDLLOVERRIDES="DWrite.dll=n,b" %command%
Enter fullscreen mode Exit fullscreen mode

Community guides sometimes also add PROTON_NO_ESYNC=1 if the override alone is not enough. The community wiki notes that BG3 Mod Manager may still show a warning on Linux even when the main menu already shows the extender version. Trust the main menu.

Config and logs, if you need to debug

Optional settings live in a ScriptExtenderSettings.json file in the bin folder. BG3 Mod Manager can create this under Settings → Preferences. Official defaults include CreateConsole (a separate debug window, off by default) and LogRuntime / EnableLogging (file logging, also off by default). The official default log directory is My Documents\OsirisLogs. If you turned logging on through the manager, the community wiki also points at %LocalAppData%\Larian Studios\Baldur's Gate 3\Script Extender Logs. Check both before you assume nothing was written.

EnableAchievements defaults to true in the official config, which is why many guides say the extender restores achievements in a modded game. The community wiki warns not to stack that with a separate Achievement Enabler native plugin.

After a Larian hotfix

Treat Script Extender and every mod that depends on it as volatile. A game hotfix can land before the extender, or before a Lua-based mod, has been updated.

A conservative sequence:

  1. Back up the save folder under %LocalAppData%\Larian Studios\Baldur's Gate 3\PlayerProfiles\Public\Savegames\Story before you experiment.
  2. Launch the game once so the extender can update itself. Confirm the version on the main menu.
  3. Only then update Script Extender-dependent mods, one at a time, from each author's current files tab — not from a screenshot taken on an older patch.
  4. If a save will not load, copy it aside before you disable mods or export a new order. Do not overwrite the only copy.

.pak mods still belong in %LocalAppData%\Larian Studios\Baldur's Gate 3\Mods. Script Extender does not change that path, and it does not replace exporting a load order from your mod manager.

For the rest of a first-time Nexus-route setup, including the manager export step, this step-by-step install guide for BG3 mods covers the two install routes. If a required extender or .pak still fails after a patch, this symptom-first mods-not-working guide is a better next stop than reinstalling at random.

Short version

Script Extender is a bin-folder DLL from one official GitHub project, it auto-updates when it can, and it is the part of a PC loadout most likely to go quiet after a hotfix. Confirm it on the main menu before you blame the mods that depend on it.

Top comments (0)