Skip to content

Baldur's Gate 3 Modding

I'm learning Larian's official Baldur's Gate 3 Toolkit, focused on gameplay scripting. I first opened it in September 2026, so alongside building encounters I built myself an offline reference to learn faster.

My role
Solo modder, learning the Toolkit from scratch
Built with
BG3 Toolkit, Osiris, Dialog and Timeline editors, Stats editor, Python
Focus
Gameplay scripting: dialogue, flags, skill checks and story goals
Status
Ongoing since September 2026

What I can build so far

  • Dialogue with consequences

    Branching conversations where choices set flags, so the world remembers what happened, and branches gated by Persuasion or Intimidation checks.

  • Osiris story goals

    Event-driven scripts that react to triggers, item use and dialogue flags, request rolls, then change the world: unlock, open, grant items and XP once.

  • Characters and stats

    Placed characters with their own stats entries (level, ability scores, armor) instead of base-game defaults.

  • Cinematics

    First dialogue timelines: camera shots and a speaker-framed greeting. My least practised area so far.

An offline reference I built

BG3 modding knowledge is spread across a wiki, community spreadsheets, a search engine and videos. I pulled what I needed into one searchable set of notes, every entry linked back to its source.

  • Osiris function index

    A script pulls the official modding wiki through its API and builds an offline index of 1,149 Osiris entries (269 events, 387 queries, 493 calls), each with its signature and a link to the source page.

  • Curated essentials

    A short guide to the functions behind flags, dialogue, doors, rolls and rewards, with the wiki's examples beside each signature.

  • Toolkit cheat sheet

    Shortcuts, debug-console commands and testing tricks merged from the community sheet and Larian's official guide, such as forcing every roll to pass or fail to test both branches.

  • Tutorial notes

    Toolkit tutorials transcribed locally with Whisper and turned into step-by-step notes for scripting, timelines and the stats editor.

What the Toolkit taught me

  • One dialogue, two IDs

    Starting a dialogue from Osiris needs the dialogue's resource ID, not the ID stored inside the file. The wrong one fails with a misleading “doesn't exist” error.

  • Reloads can keep stale data

    After changing a dialogue's timeline setting, reloading the level kept the old version. Only a full Toolkit restart picked up the change.

  • Log what you actually saw

    My work log separates what I watched work in game mode from what is still untested: both outcomes of a roll, save and load, repeat interactions.

Baldur's Gate 3 and the BG3 Toolkit belong to Larian Studios. This is personal modding work, not affiliated with Larian.