Delete overridden files option?

[daneyuleb]

It would be nice if there was a way (other than manually comparing and manually deleting lots of files) to have Vortex automatically delete files within a mod that are being overridden by other mods. Those overridden files are just wasting space and texture files can be awfully big. For instance, many of my "2017 texture pack" files are being overridden by Noble and other mods textures, but not all of them (so I can't just delete the 2017 mods. In the manage mod conflicts area, why not have a "delete" option for the overridden file? Unless there's some way to do it that I'm missing.

[Guest deleted34304850]

.

[AugustaCalidia]

It would be nice if there was a way (other than manually comparing and manually deleting lots of files) to have Vortex automatically delete files within a mod that are being overridden by other mods. Those overridden files are just wasting space and texture files can be awfully big. For instance, many of my "2017 texture pack" files are being overridden by Noble and other mods textures, but not all of them (so I can't just delete the 2017 mods. In the manage mod conflicts area, why not have a "delete" option for the overridden file? Unless there's some way to do it that I'm missing.

 

Your overridden files are not taking up space. Vortex places hard links and not the actual mods in the game data folder. The mods themselves are located in your Mods Staging Folder. The hard links mirror what's in that folder. The file size of any given mod in your game data folder is actually the file size of the mod in the Mod Staging Folder, not the file size of something residing in your game data folder.

[Tannin42]

No, this isn't actually an unreasonable request.

The idea is to remove the files in the staging folder that don't get deployed anyway because they are overridden by another mod.

 

However this would essentially break Vortex's ability to change the order of mods, disable mods or switch profiles without reinstalling the mod that was being overwritten.

Let's say you have the 2017 texture pack and "noble" installed, deployed in that order, you let Vortex remove the files from the texture pack.

Now if you disable Noble you get vanilla textures where the 2017tp was supposed to cover textures, if you switch the order you get textures from noble that are supposed to be provided by the 2017tp.

 

Or to rephrase: You would be locking down the deployment order, basically like NMM did - and across all profiles.

To make this usable we'd have to provide a warning if a mod won't work in the current deployment order without being reinstalled.

 

If you really care about this functionality please create a feature request through the feedback page in Vortex or directly on github.

[rmm200]

Thinking of the problems we would see come in because of this feature - tread carefully...

[Guest deleted34304850]

.

[AugustaCalidia]

Tannin42, please don't ever, ever, ever, ever (to the 1000th power) include such a feature in Vortex.

[HadToRegister]

Going to add a +1 to 1ae0bfb8's and Augusta's requests of "DON'T"

"Vortank deleted all my FiLES!!!"

[AugustaCalidia]

"Cortex deleted all my stuff!"

[Guest deleted34304850]

.