How to Create Mods in Baldur's Gate 3: Customizing, Testing, and Publishing with the Official Toolkit

This guide covers making a practice melee fire spell using the Stats Editor and UUID Object Editor in the official Baldur’s Gate 3 Toolkit. You will learn data handling, localization, and spell list integration without needing 3D models. Distinguish between the Windows PC authoring environment and the in-game mod usage environment, and work in accordance with game builds that support the official mod manager.

1. Installing the Toolkit and Empty Project

Check Larian's Installing the Toolkit documentation for the installation order of the Toolkit and Toolkit Data for your store platform. For Steam, this involves checking the tools section in your library and the Toolkit Data game DLC. Record your existing game/toolkit version and saves, and create a new project following the Creating a New Mod documentation. Choose a unique name like TroubleMakerPracticeSpell and keep the default dependency settings as outlined in the official docs. Loading the entire game data may take some time during your initial work.

2. Creating Target Spell Data in the Stats Editor

1. Open the Stats Editor at the top of the editor.
2. Expand your own project rather than the Shared original.
3. Select + in SpellData and add Target data.
4. Create a row in the new Target table and assign the Name TMPracticeFlame. This is an internal name without spaces.
5. The technical identifier name will be Target_TMPracticeFlame. Do not confuse this display name with this internal ID.
6. Refer to the required columns in the official Basic Spell documentation to fill in the values and animation items below.

3. Filling Required Values for a Small Spell

Below is a bundle of practice values. Rather than pasting this block into a file, find each corresponding column in the Stats Editor and enter them individually. Configure it simply as Level 1, 1.5m melee, Dexterity saving throw, and 1d6 fire damage. Test a single effect before adding area-of-effect or healing all at once.

Name: TMPracticeFlame
Level: 1
SpellSchool: Evocation
TargetRadius: 1.5
SpellRoll: not SavingThrow(Ability.Dexterity, SourceSpellDC())
SpellSuccess: DealDamage(1d6,Fire,Magical)
SpellFail: DealDamage(1d6/2,Fire,Magical)
TargetConditions: Character() and not Dead()
CastTextEvent: Cast
UseCosts: ActionPoint:1;SpellSlotsGroup:1:1:1
Icon: Spell_Evocation_Fireball

The official documentation explains that spells require a Spell Animation to actually cast. Find an original Touch-type spell in Shared → SpellData → Target, copy its Spell Animation value, and paste it into your row. Row numbers vary depending on the game data version, so use search to find them. Select the required PrepareEffect, CastEffect, and HitEffect using the corresponding suffix items listed in the official documentation. For SpellFlags, check IsSpell, IsHarmful, IsMelee, and the appropriate casting conditions.

4. Player-Facing Names and Descriptions

In DisplayName, enter a custom name such as Practice Fire Touch, and in Description, enter a description like Deals [1] to the target. Localization input windows and string handles are managed using the Adding Localisation documentation method. Use DealDamage(1d6,Fire) for DescriptionParams and TooltipDamageList, and Dexterity for TooltipAttackSave to ensure actual numbers match the tooltips. Translating internal IDs can break spell list connections, so only translate display strings.

5. Adding to Spell Lists and Verifying in Game Mode

1. Create your project's Lists → SpellLists table in the UUID Object Editor.
2. Write a developer-friendly description in the Name field of the new entry.
3. Add Target_TMPracticeFlame to Spells. This value requires the spell type prefix.
4. Select the existing class spell list for that level in MergedInto. Since this example is Level 1, select the appropriate list such as Cleric SLevel 1.
5. Save all changes and load the Basic_Level_A test level.
6. Enter Game Mode and select the class and spell during character creation or level up. You can use the Ctrl+Shift+L level-up feature over portraits mentioned in official guides.
7. Check the target distance, damage on save success/failure, spell slot/action costs, and name, description, and animation respectively.

6. Local .pak and Public Distribution

Fill in the name, description, and thumbnail in Project → Project Settings. Publish Local is a feature that creates a .pak without public uploading, allowing you to choose the generation location. Enable the local pack using the official mod manager in a separate game profile and re-verify in a new test save. Public distribution on mod.io additionally requires Larian and mod.io account linking and authentication, file scanning, and description, tag, and dependency settings. Also note the original instruction that editor dependencies and mod.io dependencies must be set separately.

7. Troubleshooting Missing Spells and Removal

If the spell is not visible, check the Target_ prefix in the internal name, MergedInto in SpellLists, and the spell level and class level in order. If it fails to cast, check Spell Animation, CastTextEvent, and UseCosts. If tooltip values differ, compare DescriptionParams with the actual SpellSuccess. Removing a mod from a save may affect loading and behavior, so use a copy rather than your original save for comparison. In your distribution description, note supported builds, tested classes, required dependencies, and multiplayer conditions, and check official platform-specific reviews for console availability.

Original Documents and Verification Criteria

This introductory guide was written by the TroubleMaker operations team based on creator and official tool documentation verified on October 7, 2026. Code and diagrams are custom examples for explanatory purposes and do not represent actual gameplay verification of the game on this server. Verify and distribute using a separate test save with the versions specified in the text. Cross-reference the latest versions and dependencies for each tool from the originals below.

Larian Toolkit 설치

Larian 새 모드 생성

Larian 주문 데이터와 테스트

Larian 현지화 문자열

Larian 모드 배포