Not reading from relocated Mods folder

[Josyph]

Greetings all. I was recently experiencing the disk space error (possibly due to the new version (1.19.x) or mods resulting in the taking up of more space for the time being, I'm not sure). Because my computer was poorly designed with not a lot of excess storage on my main drive which VS defaults to keeping saves on, I followed the advice on this thread: 

I successfully moved my VintageStoryData folder and was able to load my game up and find my saves and everything loading from my second hard drive right where I want it to be (in my case it's my D:\ drive). The problem is that even though the mods folder within the VintageStoryData folder successfully transferred my mods to its new location, the game doesn't seem to be reading the mods from that location. It's loading saves from that location but not mods. Did I do something wrong and/or is there a way to force the game to read mods from the new folder in my D:\ drive? 

The mods themselves don't appear in the ingame Mod manager but DO show up when I click on "show mod folder" 

Thanks, especially to @Streetwind for giving me a good solution to my problem as noted above.

Edited January 30, 2024 by Joseph Glazebrook

[Streetwind]

You can tell the game to look for mods in additional folders either by editing clientsettings.json, or by providing the --addModPath your:\path\here startup parameter.

[Josyph]

Fantastic. Thank you so much @Streetwind !  Once again, you have assisted another player. 

For those following this, I found the clientsettings.json file in the VintageStoryData folder after I moved it. I opened it and went to the very end, locating the entry entitled ""modPaths" and changed what had been there to the accurate drive, in my case, "D:\\Vintagestory\\VintageStoryData\\Mods"

[GerMilitaryLoli]

On 1/31/2024 at 11:50 AM, Streetwind said:

You can tell the game to look for mods in additional folders either by editing clientsettings.json, or by providing the --addModPath your:\path\here startup parameter.

God bless you! I had this problem, and didn't think that mods folder variable stored in string like absolute path and not created based on current login user, changing path on json file fixed it

[psychedelic]

Ohh! This is very late but I want to say it in case anyone else has this issue, my mods haven't been working for a long time now, not because I changed where my mods folder was, but because a few months ago I changed my windows user name. Very confusing because the "opens mods folder" still worked properly, but the clientsettings.json was not updated with the new name! Thank you!! 

[Campanella]

you've saved me........ thank you so much.........................