Hugslib + Deep Storage results in unplayable game state

[Drexl]

Mod List: Harmony [https://steamcommunity.com/sharedfiles/filedetails/?id=2009463077] Core Royalty Ideology HugsLib [https://steamcommunity.com/sharedfiles/filedetails/?id=818773962] LWM's Deep Storage [https://steamcommunity.com/sharedfiles/filedetails/?id=1617282896]

Issue: With HugsLib and Deep Storage installed the following issues occur:

• Inability to interract with any game objects or pan the map.
• Immediately after crash-landing the game keeps spawning steel slag chunks until they reach the end of the map.
• Mod options page is blank.

Log: log.txt

[LamkasDev]

+1

[lilwhitemouse]

Some mod or another has failed. Your best bet is to force Steam to redownload or check the integrity of the mod and if that doesn't help....do that for all other mods.

It's a weird thing, and I have yet to figure out how to cause it deliberately, but resetting the downloaded mods usually helps!

[Xetaxheb]

EDIT: see the bottom if you are a rimpy user

---

So update on this, I don't know what mod does it, but the only difference besides rimpy optimized textures I can find between my broken copy and a fresh one (workshop or github) is a "Languages\English\Keyed.LWM.DeepStorage.Keys.xml.swp" file, a LoadFolders.xml at the base level, and an empty Common directory at the base level.

LWM.DeepStorage.Keys.xml.swp.zip LoadFolders.zip

With my broken copy I cannot move the camera and some other brokenness, and drop pod (brutality, cass strive/reload, random spot on map) spits out a million scrap.

Deleting the LoadFolders xml fixes it for me. Some kind of loading outdated versions issue since 1.4 isn't specified in the xml? I don't know how it got there, though. It's in a ton of my mods so maybe part of RimPY's download or management process? But I tried deleting it and redownloading it and it wasn't there. So maybe another random 'optimization' mod like rocketman, rim73, yadda yadda yadda there's a lot that could maybe have done it. edit: well obviously some kind of updating from 1.3 issue without a fresh reinstall? leaving old files behind... could maybe fix with an included loadfolders in 1.4 idk

At any rate TL;DR remove the LoadFolders.xml file if it doesn't list 1.4.

Edit: I am not 100% completely confirming this but it's almost certain that updating with SteamCMD (or RimPY which uses it) does not remove outdated/removed files from existing folders.**

Here is my solution if you are a local files user;

• your best bet is to save your rimpy list with export list, then put active any mods you want fresh copies of and save another exported list as 'updated.xml' or similar.
• Rename the Mods folder (for backup) and open rimpy which should automatically ask you if you want to download missing mods or when you try to import the list it will.
• You will then get a list of every mod it's going to add to the downloader list as confirmation.
• Some of these will probably be wrong; but not to fear because the process is easy.
• Sort by the "Variants" column by clicking it. Variant: 1 means it only found 1 variant of a mod id on the workshop. These are probably fine.
• Variant 2 or more means it found multiple versions, and put them in the workshop number dropdown... these are the ones you'll need to pay close attention to. Many are probably wrong like russian translations or etc. It also updates the name to the right of that depending on the workshop number you select. It also shows compatible version. You can probably find what you want with that dropdown. Careful because scroll wheel on them WILL change the dropdowns.
• Variant 0 will need manual workshop number input, google them and copy the number from the url, for example 761421485 is Allow Tool.
• Put those number in the boxes.
• When all is said and done and you click download, it will populate the Downloader tab's to-be-downloaded list so you'll need to click download with steamcmd.
• It will warn you before it fills that list if there are any workshop mods it couldn't resolve, like a removed one; including the url. I recommend copying this and then you can go grab the folder from your backed up mods or at least see what it was... but keep in mind removed mods are probably removed because they're incompatible.

Depending on your number of mods to redownload, steamcmd can take awhile. I recommend leaving the datestamping on as well. Remember that any mod you did not have set as active or in the exported list will not have been redownloaded, so your inactive list will be emptied. You'll also need to copy back in any non-workshop folders from mods you had, like performance-fish or etc. And any Variant 1 mods are not 'guaranteed' to be the right ones, just what rimpy could find.

[Drexl]

@Xetaxheb that was incredibly helpful. Thank you!

[lilwhitemouse]

Dear archotechy gods! That's a subtle thing that could very well be is almost certainly causing the problem! I removed the LoadFolders at some point because it was a real pain to keep up to date, and because with 1.4 it was no longer useful, and if it's still around, it could f--- things up. You might bring this up with the rimpy people! I will look into whether an empty LoadFolders file causes problems, and can put one back if that would help.