Skip to main content

BG3 Toolkit creates a new mod page instead of updating my existing mod

Updated

If you publish an update to an existing Baldur's Gate 3 mod through the BG3 Toolkit and it creates a new mod page instead of updating your existing one, the most common cause is a missing or incorrect PublishHandle value in your mod's meta.lsx file. This article explains how to fix it so your update goes to your existing page and keeps its subscribers and download history.

The BG3 Toolkit is developed by Larian Studios. This article covers a common cause we've seen, but for issues with the Toolkit itself, please contact Larian support.

 

Why this happens

The Toolkit uses the PublishHandle attribute in your meta.lsx file to decide which mod.io page to publish to. The value should match the ID of your mod on mod.io.

If the PublishHandle is missing or set to 0, the Toolkit treats your project as a new mod and creates a new page. This often happens when you build your mod outside the Toolkit (for example with BG3 Modder's Multitool) and then import the .pak, because the meta.lsx in your source project may not include the PublishHandle.

 

Before you start

  • Make a backup copy of your mod project folder.
  • Make sure you're signed in to the Toolkit with the same mod.io account that owns the existing mod.

 

Find your mod ID

Open your mod's page on mod.io. Your mod ID is listed next to ID in the details panel, below the download and subscriber counts. You can use the copy button beside it to copy the ID to your clipboard.

 

Add the PublishHandle to your source project

  1. Open the meta.lsx file in your source project, found at Mods/[YourModFolder]/meta.lsx.

  2. In the ModuleInfo section, add or update the PublishHandle line alongside the other attributes, replacing 1234567 with your mod ID:

    <attribute id="PublishHandle" type="uint64" value="1234567" />
  3. Save the file and rebuild your .pak.

Once the line is in your source meta.lsx, every future build will include it.

 

Check the project after importing

After importing your .pak into the Toolkit, open the imported project's meta.lsx before publishing and confirm the PublishHandle still matches your mod ID. If it's missing or set to 0, correct it there before you publish.

Also check that the mod's UUID matches the one in your published version. A different UUID causes the mod to be treated as a separate mod.

 

Still creating a new page?

If the Toolkit still creates a new mod page with the correct PublishHandle in place, please contact Larian support, as this would point to an issue with the Toolkit.

If any duplicate mod pages were created along the way, you can hide or delete them from your mod.io account. If you need help with this, contact us with links to the pages and we'll sort it out.