BG3: Failed to write load order

[NalaGinny]

Hi,

I have been using Vortex to handle my BG3 mods for a few months and until now it worked fine. But now whenever I try to change something with my mods (was trying to remove some due to patch 7 adding mod support) it is giving the failed to write load order message.

When I check for more information it says Cannot set properties of undefined (setting 'node')

TypeError: Cannot set properties of undefined (setting 'node')
    at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\game-baldursgate3\loadOrder.js:365:37
    at Generator.next (<anonymous>)
    at fulfilled (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\game-baldursgate3\loadOrder.js:28:58)
    at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18)
    at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5)
    at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)

[jhinor]

Same. It happened to me the last small update as well. I tried changing things with no success, and then it just magically worked again. I think Vortex has to update their software after the game updates? I don't know, but I'm hoping for an answer from someone more knowledgeable than myself.  

[HaVeNII7]

Same issue. Ran the game without issue for months, once patch 7 dropped it stopped working entirely.

[Jgold]

same for me 

[kirant]

Same issue here - I suspect it may be because we're running LSLib manually.  I had to download it manually previously.

I think it's very specifically LSLib since the mod activation requests when opening up a modded save in BG3 asks for many, many instances of one of my mods (5E spells in my case), which is likely interpreted in its domain.  Similarly, any attempt to modify the load order is met with the same "Failed to write load order" error. 

[Floofed99]

So is there any known solution to this?

[ZarexJaeger]

Been happening to me as well. Reinstalled LSLib, got rid of the error, but mods do not load for the game. I guess we just need to wait for everything to transfer over to the official mod page in-game?

[NalaGinny]

Tried to reinstall LSLib as well but then the version is listed as 0.0.0 () and Vortex can't deploy any mods because it says LSLib is not installed. Set it back to 1.19.5 and then I can deploy mods again but the Failed to write load order persists.

[Zanderat]

1 hour ago, ZarexJaeger said:

Been happening to me as well. Reinstalled LSLib, got rid of the error, but mods do not load for the game. I guess we just need to wait for everything to transfer over to the official mod page in-game?

No.  Incompatible mods need to be updated.  Has nothing to do with the ingame mod manager, which I plan to avoid (unless I am proven wrong).  It was a disaster for Bethesda games.

[ZarexJaeger]

4 hours ago, Zanderat said:

No.  Incompatible mods need to be updated.  Has nothing to do with the ingame mod manager, which I plan to avoid (unless I am proven wrong).  It was a disaster for Bethesda games.

I don't believe so since even though I'm installing stuff that has been updated to patch 7, it's still coming up with this exact same error. Plus, that's fine, but not a lot of people are gonna wait for Vortex (I will) or don't want to touch it/know about it