Vortex does a atrocious job of deleting files

[Zanderat]

@showler is right. The OP correctly wants the data folder cleaned when uninstalling but the authors of said tools need to make them work with Vortex not the other way around. A good example of a tool that works well with Vortex integration is EasyNpc.

[Guest deleted34304850]

I think its a bad design choice. Considering that these folders vortex is symlinking into the data dir all have a hierarchy with data as the root, it would be trivial to have these extraneous files created by tools and such simply be placed into the staging folders. Vortex might not know a file belongs to bodyslide if its outside the folders already present in the staging dir but it's easy to assume anything inside those subfolders belong to the mod. Either way, these folders should no longer be "managed by vortex" after purge is done if they are safe to delete, as far as not being part of the deployment.

 

Vortex should have a better way of handling these extraneous files. Mods and their configuration/output should be stored together, its only good sense. Even if its just manually assigning folders and files to be tracked and moved to a mod's staging folder.

 

Common area folders like meshes, plugins, scripts could be assumed ignored by default unless giving the user the option to 'factory reset' them and clear them out.

 

Its wild vortex can't remove the Nemesis folder because there's a cache folder inside it or the bodyslide folder because you made a custom preset, which should be stored with the mod files anyway

 

Or MCM settings which again, should stay with MCM staging.

 

One Idea I have off the top of my head: sandbox tools added to vortex such that they can read anything in the skyrim install folder but can only write to their own mod staging folder. Than when you run bodyslide it outputs to the staging folder and deploys the output to the skyrim folder with hard links or whatever.

i think you're a homophobic coward who doesn't understand the simple basics of modding or how vortex works. because you lack this understanding, you project your own failings onto vortex and people who you don't know, but you know you disagree with on a variety of issues.

i'd ask why you're so scared of learning new and different things, but honestly, i don't care. your failings are yours and yours alone.

be better in your understanding and tolerance and try to be the best version of you at all times.

[showler]

Even if Vortex could override the file locations of various tools to put them in the staging folder (and I doubt it could considering how the links it uses misbehave when you get to write to the link rather than to the real file) it probably would be a nightmare for the tool authors trying to offer support to their users.

[vortexposer]

Right now, any old mod that generates random files in root or data can be easily side-stepped by making a template file for it to write to but tools should also provide an option for output folder path to redirect to (bodyslide settings). https://i.imgur.com/WTGzkm0.png

I think only Nemesis doesn't (fnis does though) but that's its own deficiency vs vortex issue. It's also easy enough to purge and import yourself, so its output can be managed

[Guest deleted34304850]

as far as I can tell, the OP never came back and showed what - if any - files vortex didn't clean up. i'm very curious to see if it genuinely doesn't clean up files for mods it manages. in my experience vortex has ALWAYS cleaned up everything it manages, and anything left over have been files placed by mods that vortex doesnt know about, so, based on my own experience, vortex does a great job of cleaning up everything it manages in my environment which includes fallout3, fallout nv, fallout 4 and skyrim.

[showler]

"The OP never came back" is practically the theme song of these forums.

[vortexposer]

Not having an overwrite folder, like in MO is mostly what they're referring to. Which 95% of what it "captures" is sloppy file generation that wouldn't even be necessary if author just shipped a template so Vortex would technically know file on its deployment (and subsequently purge once mod initializes it and updates after launch). As for the tools output, its just not well-known how to set up proper redirection. Plus it is rare to find any mod list guides to follow adv modding steps that would discuss it regarding Vortex.

Collections is realistically the perfect solution for most of this bc it forces you to build and bundle all output files and customized configs that get generated and "dropped". This alone has made it more than capable of maintaining clean environments. Including import of edited game files that user can set up themselves to swap out from its root, etc.

Like try explaining how to not alter FalloutNV.exe with 4Gb patcher to VNV users to use edited copy to deploy instead (replacing unedited original), while watching their brains melt.

Edited July 8, 2023 by vortexposer