Larian Studios Forums Baldur's Gate III Baldur's Gate III - Modding Mods won't stay deleted

I feel like I've tried everything I can think of. I've disabled them all, deleted them one-by-one in the in game mm, deleted them in the files, used a bg3mm to delete them, nothing seems to work. Every time I start up the game again all the mods reinstall and enable themselves. Also, half of the mods say something along the lines of it not being able to be deleted because it's being used in another process, which to my knowledge, it's not. Does anyone have any ideas or suggestions on how I can solve this issue?

if you're on windows, try hitting windows key + R, and type %LocalAppData%. Scroll and find Larian Studios, then Baldur's Gate, then player profiles, then Public, then delete modsettings.lsx file. it'll make all your mods inactive, but I'm not entirely sure if it'll fix the problem. in that same menu under %LocalAppData% - Larian Studios - Baldur's Gate, you can open the mods folder from there and try deleting them. After you delete either modsettings.lsx and/or the mods, try reverifying mods through steam and see if that fixes it!

Unfortunately, I've tried that a few times. It doesn't fix it.

I'm having the exact same issue, Ive kinda narrowed it down to the game having issues with actually unsubscribing from the mods you've downloaded in BG3 to the subscriptions on mod.io, I've checked the actual website for me to find that I wasnt subscribed to anything, and to test I subscribed to one on the website, relaunched the game after nuking my mods list and BAM there it was along with every single other mod I've downloaded in game. Hopefully someone has more insight to this

I'll have to keep that in mind if it happens again. I ended up logging out of my larian account in the mm (not sure if that does anything but it was worth a shot), deleted what it would let me, started a new game, went back to the main menu, deleted what it would let me again, repeated that one more time. The mods haven't come back after that.

I'm not real sure what you're talking about here, but I've been having a problem that I think has to do with Vortex itself.
I had a set of mods I was using and was experimenting. Started having trouble, so I deleted all the mods, then uninstalled Vortex.

Then reinstalled it and, the mods I had deleted showed up. I was trying for a clean slate.
This must have to do with Vortex itself.

I'm having the same issue and I'm using bg3 Mod manager. I want to use an older version of a head I like because the new version no longer supports Unique Tav but every time I start up the game the newest version will be installed. I deleted it & then replaced it with the old version several times, deleted it out of the mods folder & tried deleting it after I logged out of my Larian account but it keeps coming back. It's just annoying and somewhat tedious to replace it every time I try to load up the game.

Have you tried to set the modsetting.lsx to read-only, so that this can't be overwritten? But be careful, every time you want to install a new mod, you have to take care to uncheck it first and put it back in again after saving/exporting, as long as this problem has not been solved. If the problem is solved, be sure to uncheck it completely.

I'm not sure how to set modsetting.lsx to read-only, if possible do you think you can explain how?

Im truly at the point of just accepting that I need to import the old head every time I load up the game lmfao

My modsetting.lsx is constantly being overwritten and that's why my mods didn't work. I have marked this file as read-only so it cannot be overwritten by BG3MM. I ignore all error messages when starting the game because my mods are all there and working.


Users\Username\AppData\Local\Larian Studios\Baldur's Gate 3\PlayerProfiles\Public

rightclick the modsetting.lsx > preferences > read-only

As long as there is a problem with this file being overwritten, you must always deactivate this if you want to install new mods and activate it when they are installed.

This may also help with this problem.