Mod folder structure (deploying contents vs parent folder)

[Toadby]

So I am using Vortex to manage mods for Rimworld. I have the game directory manually set. When I download mods, I drag the zip files in to Vortex to install them.

My problem is, unless the archive already contains a subfolder with the mod contents, Vortex will just drop the contents in to the mods folder - Instead of putting each mod in its own folder.

What I've been doing to manage this is set new mods to disabled, open the location (mod staging folder), and manually create a subfolder before enabling. So what my mods look like is Staging folder > Modname > Same Modname > contents. And that way the inner mod folder gets deployed and carries the contents with it.

 

Am I doing something wrong? Is there a mod type I should be selecting to get them to deploy how I want them to?

[Pickysaurus]

The Rimworld extension is quite basic at the moment. It will take the archive from Nexus Mods and simply extract it into your staging folder.

 

It would be possible to add some logic to create the folders automatically by enhancing this extension, provided there's a good way to programmatically work out when a parent folder is required.

 

e.g. If the mod has a manifest file on the top level, we need to nest it into a parent folder.

[Toadby]

Thank you for the response! I might look into modifying the extension if I can stop endlessly browsing mods :P