Mortasi

Seems the culprit was the Tales of Arise extension. Tried installing a couple of mods after disabling it and now it works as it should without adding any extra folders. Thanks for the help/solution @ChemBoy1! And thanks @Zanderat for your help as well

Ah, thanks for the info @ChemBoy1 ! The extensions I have are the ones Vortex gets automatically I think (could be I did something I don't remember). I assume the culprit can't be the bundled ones (guess everyone has those?) so here is the list when "bundled" are hidden. I'll try disabling them later and do a test.

The mods are fine and do not have subfolders. As I said Vortex creates these subfolders. Weird that it happens for me but not for you. Are we using the same version? Mine is 1.12.2 (8/14/2024) Example with Better Hotbar mod The zip contents look like this: But Vortex staging folder will look like this after I install it (notice the dir structure): Mods folder same as expected: I then manually move the files to top level (remove the \content\\paks\~mods\ folders, purge and deploy, and it works fine after that:

Hi, Spent a good bit of time trying to get Vortex to work for BG3. Found Vortex would not edit modsettings.lsx. Tried using BG3 Mod Manager to just set the load order for the mods already deployed by Vortex, and that wrote modsettings.lsx correctly, but it kept getting reset when I started the game. Was about to give up and try BG3ModManager or manual installs, but then I came over this tip on BG3ModManager page: Went to the Vortex deploy dir and moved the files for the 4 mods I had to top level within its own mod folder (\VortexMods\{modname}\Content\Paks\~mods to \VortexMods\{modname}\), and after a redeploy everything works perfectly. Vortex starts it process and modifies modsettings.lsx as expected, and when game is launched it is not reset anymore. Why does Vortex add these \Content\Paks\~mods\ folders under each mod when it (for me at least) makes modding not work at all for BG3? Is there any other way to fix this so I don't have to manually remove the folders Vortex automatically adds on all future mod installs?

For me the issue was that the staging folder set to a different drive/partition than the game files. Should work fine (even says so in the settings description for symlinks in Vortex), but apparently gives this reading-pak-files-forever issue.