Jump to content


  • Posts

  • Joined

  • Last visited

Hexalan's Achievements

Wolf Bait

Wolf Bait (1/9)



  1. Just need to add that I had to make the same change to serversettings.json as well. The client side only mods were loading the others were marked as disabled per the log file even though they indicated being enabled in the GUI.
  2. Environment: VS 1.14.5 on Windows 10 Problem: Due to disk space issues I moved my AppData/Roaming directory to another drive using Win10's folder location setting and let Windows move all the data. While all of my save data and other settings are fine the mod path setting is not updated to the new location (see ModManger-pre-edit.png). Clicking on the "Open Mods Folder" in Mod Manager does open the correct folder and the mods are present (modsfolder.png). I looked at clientsettings.json and found that the modPath is not updated and still points to the old directory: "modPaths": [ "Mods", "C:\\Users\\XXXXX\\AppData\\Roaming\\VintagestoryData\\Mods" ], Work around performed: Shut down VS. Edited the clientsettings.json file and changed the value of modPaths to the correct location under the moved AppData/Roaming location: "modPaths": [ "Mods", "D:\\XXXXX\\AppData\\Roaming\\VintagestoryData\\Mods" ], Restarted VS. The game client then picked up the mods correctly and seems to be working fine. Desired behavior: Provide the user with an editable save data location and make modPaths follow that setting. This would be my preference but that may break Windows' conformance crap. or Change the way modPaths is set to use the system location for %AppData%\\Roaming so that a move of the folder are followed correctly. *I'm not a coder and these are just my thoughts, there are probably better ways to fix it!* Thanks for creating such a great game!
  3. /*drops off hand torch on ground/* No, nothing in my hands! Seems to be working fine!
  4. Ok, went ahead and did the update with the item juggle. On version 1.7.2 with CarryCapacity-0.4.0-rc.2 installed. From your repo notes it seems we need to install Carry Capacity separately now? I have a new issue, breaking chests destroys the chest and returns nothing (MP server environment, not tested in SP). Contained items do drop though. Is this intended? There isn't anything in the server logs about it. MP Server / Windows clients VS 1.9.6 Neolithic 1.7.2 CarryCapacity 0.4.0-rc.2 Graveyard 1.1.3 WaypointUtils 1.0.17
  5. I have this installed with latest version (1.7.2) of Neolithic on VS 1.9.6 and the carry action will not work on anything. This is on an MP server, all players are seeing the issue. Also, some things show multiple lines of the action hint:
  6. Do you want bug reports here? It doesn't look lit your Git repo is set up for them. Updating from ver. 1.6.9 to 1.6.12 broke all of the Neolithic chests. All of them turned into the unknown "?" block. Vanilla reed baskets were fine. VS 1.9.6 (updated from 1.9.3) OS: Linux with Mono Other mods: 1.9.6-WaypointUtils-1.0.17 Graveyard-1.1.3
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.