Disabling mods deletes original files

[RyanBurnsRed]

What I mean by the title is if I install this mod and enable then disable it, Vortex completely removes the Translate_ENGLISH file it modifies and doesn't give me back my original or anything of the sort.

I came to this realization when I switched to a vanilla profile yesterday and didn't have a HUD when I loaded a save near the start. I had to verify the game files in Steam. Is this intended? I can't recall ever having a problem like this with NMM or MO so I'm not sure if I'm just being dumb.

[rmm200]

First question I would have is did you install that mod from within Vortex or manually?

Second question would be what is the Translate_ENGLISH file part of? Vanilla Skyrim, SkyUI, or something else?

Just trying to help you get more responsive answers.

[Tannin42]

Are you certain? Could you try to reproduce this and document it step by step (ideally with screenshots)?

 

When vortex has to overwrite a file in data to install a mod it's supposed to backup the original file to <original filename>.vortex_backup. Then, when the mod gets disabled the vortex_backup file will be restored.

[RyanBurnsRed]

Thanks for the replies. I'm going to try to be as descriptive as possible and provide screenshots.

 

So first is Translate_ENGLISH.txt is part of vanilla Skyrim. Without this file the text in the UI of the game all have $ before them. So like on the main menu it'll say $Continue and $New and so on. Also I linked to the wrong mod in my OP...it's actually this one I was using, the older version with the loose files. If you check the file contents you'll see this mod has its own Translate_ENGLISH.txt file.

 

Here is a brand new vanilla Interface folder right after installing from Steam. Note the date and time. It's the only file in this folder.

 

Next I'm going to install and enable the mod I linked above. Here's how the folder looks afterwards. Keep noting the date and time on Translate_ENGLISH

 

Now at this point nothing has happened in Vortex. See the mod is enabled and is the only mod enabled on this fresh install....until I install something else or restart Vortex. Here I'll install and enable iHUD since it has no loose files and won't conflict.

 

As soon as I enable iHUD this pops up. With show individual files ticked. It's Translate_ENGLISH! But at this point it's too late. If I choose Undo the file is overwritten anyway.

 

And now when I disable the mod. The original files from the mod are gone but kept the folder structure, which is fine...but now my Translate_ENGLISH file is gone too. At this point I have to either verify files in Steam or reinstall the mod if I didn't make a backup.

 

Also while testing this I decided to see what would happen between two mods that overwrite each other.

I tried testing with ApachiiSkyHair and a separate retexture of it. The thing with this is that as soon as I install the retexture, those files overwrite the original.

 

Here's ApachiiSkyHair installed only. Notice the date on LongCurly_blonde.dds. Here's when I install the retexture. At this point Vortex is telling me these two mods conflict. But choosing whether one loads before the other has no effect on the actual files in the folder.

I'm not sure if this is supposed to happen. Starting up the game and the retextured mods are the ones that are being loaded even when set to load before in Vortex.

 

However if I disable the retexture then the original files are put back in place, so that works as it should.

 

I'm using Votex 0.15.2 and here are my settings

[Tannin42]

Thank you so much for taking the time to document this in detail.

 

This is definitively a bug in Vortex, it probably snuck its way in a few updates ago when I fixed a performance issue with deployment.

[RyanBurnsRed]

You're very welcome! Regarding the second part with the textures, is it also a bug?

I would think that telling Vortex to load one texture mod before or after another regardless of install order would switch out the files, but that doesn't seem to be the case.

[Tannin42]

Vortex doesn't automatically re-deploy when you change load order because that could be very annoying if you did more than one conflict. So you have to run deploy manually before you see the effect of changing the install order.

If it doesn't work then, that's probably a bug, but I followed your steps and it works for me.

[Grestorn]

Tannin, that's news to me.

 

So if I activate multiple mods with loose files and they're conflicting with other mods or each other. I'll get the red lighting symbol on them, I click them and resolve all conflicts.

 

Do I have to un/reddeploy them manually after this? I always presumed that changing the "load after" or "load before" will automatically do as I requiested. If that's not the case, you should display a popup message with the option to redeploy all afftected mods.

[Tannin42]

Yeah, I realise it's less then ideal and I already have a todo scheduled to improve this.

 

In general it doesn't hurt to press deploy once too often than not enough, when there is nothing to do on a deploy it should take only a second anyway. (unless you purge first, deploy is an incremental update so it only has to deploy stuff that changed)

[Grestorn]

Ah, that's good to know. So if I press 'deploy all mods' now, it will only correct the files which are currently taken from the wrong mod due to changes in the conflict load order? I don't actually have to disable them first?