Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Guides/Workflow Guide: Difference between revisions

From MoonGlasses Wiki
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
test2
<blockquote>This is mostly based on Fetish's workflow guide in the MoonGlasses Discord</blockquote>When you create a mod project using the '''Toolkit Editor''', it automatically saves the project in the following path:<syntaxhighlight lang="text">
Baldurs Gate 3\Data\Mods
</syntaxhighlight>This makes it available for the game to load directly. This is convenient, but can also lead to some problems if you publish your mod as a <code>.pak</code> file to the following path:<syntaxhighlight lang="text">
AppData\Local\Larian Studios\Baldur's Gate 3\Mods
</syntaxhighlight>Having both the mod project '''and''' the <code>.pak</code> file will cause conflicts. This can lead to issues when playing your mod in the game, such as the mod failing to work correctly or at all, even if it works perfectly in the editor.
 
== Quick Fix for Conflicts ==
If your mod works fine in the '''Toolkit Editor''', but starts causing problems once exported to the game, the above issue is likely the reason. The simple solution is to:
 
* '''Delete any <code>.pak</code> files''' that were created by the editor from your <code>Appdata...\Mods</code> folder.
 
This will usually resolve the issue, and your mod should work as expected in the game

Latest revision as of 17:20, 16 January 2025

This is mostly based on Fetish's workflow guide in the MoonGlasses Discord

When you create a mod project using the Toolkit Editor, it automatically saves the project in the following path:

Baldurs Gate 3\Data\Mods

This makes it available for the game to load directly. This is convenient, but can also lead to some problems if you publish your mod as a .pak file to the following path:

AppData\Local\Larian Studios\Baldur's Gate 3\Mods

Having both the mod project and the .pak file will cause conflicts. This can lead to issues when playing your mod in the game, such as the mod failing to work correctly or at all, even if it works perfectly in the editor.

Quick Fix for Conflicts

If your mod works fine in the Toolkit Editor, but starts causing problems once exported to the game, the above issue is likely the reason. The simple solution is to:

  • Delete any .pak files that were created by the editor from your Appdata...\Mods folder.

This will usually resolve the issue, and your mod should work as expected in the game

MediaWiki Appliance - Powered by TurnKey Linux