Changing mods in game directory gets them deleted

[omena007]

Hi all, I wonder if anyone else has this problem that appeared to me at recently. Sometimes, it seems to happen randomly, if I edit mod files directly in game directory like edit a texture file etc. then when I deploy new files in Vortex it doesn't recognize the change in normal deployable way but gives me option to either delete or restore the file. This is turning my hair grey since both options basically delete all the chances I have made and making mods from Vortex directory is bothersome since you have to deploy with every change you make.

Edited January 3, 2023 by omena007

[Pickysaurus]

The two options you are given either:

 

• Revert the change and use the unedited mod file from the staging folder.
• Save the change, overwriting the one in the staging folder with your new one.

 

Neither of these options will delete the file.

[omena007]

The two options you are given either:

 

• Revert the change and use the unedited mod file from the staging folder.
• Save the change, overwriting the one in the staging folder with your new one.

 

Neither of these options will delete the file.

That's exactly the problem Vortex doesn't give the normal option to save the change/overwrite, instead it gives option to "save change and delete the file" or "revert change restore file" as if I had deleted the file in the game directory. Thank you for the quick reply in any case.

Edited January 3, 2023 by omena007

[Pickysaurus]

If it's giving you that option then you've either moved or deleted the file and it's no longer where Vortex expects it to be.

 

While a human can quite easily work out if a file has been moved or renamed that's hard to do programmatically. Functionally as far as the file system goes deleting and moving/renaming a file are basically the same action.

[omena007]

 

The two options you are given either:

 

• Revert the change and use the unedited mod file from the staging folder.
• Save the change, overwriting the one in the staging folder with your new one.

 

Neither of these options will delete the file.

That's exactly the problem Vortex doesn't give the normal option to save the change/overwrite, instead it gives option to "save change and delete the file" or "revert change restore file" as if I had deleted the file in the game directory. Thank you for the quick reply in any case.

 

I understand this, thank you for your reply. I guess when a file is edited the Vortex can randomly act as if I have deleted or renamed the file instead. It would make more sense if I had changed a format or a name, but I guess this is a mystery. Thank you in any case.

[Guest deleted34304850]

my question would be why are you manually editing files that are controlled by your mod manager? that would provoke the manager to say this has changed in a way i don't know about, so i am going to restore it back to how i know it should be.

can you make edits to your file outside of the folder, then add your changed file into vortex to allow it to deploy your changed file to the game directory? this would, i think, stop the issue you're seeing, because it would control the file with your edits in place, replacing the unedited file?

[Zanderat]

The only changes I have made to files outside of Vortex would be if I used xEDIT or the CK on them. My experience is that Vortex handles those changes correctly (save or revert). No issues.

[omena007]

my question would be why are you manually editing files that are controlled by your mod manager? that would provoke the manager to say this has changed in a way i don't know about, so i am going to restore it back to how i know it should be.

can you make edits to your file outside of the folder, then add your changed file into vortex to allow it to deploy your changed file to the game directory? this would, i think, stop the issue you're seeing, because it would control the file with your edits in place, replacing the unedited file?

As I explained earlier, when I make mods and edits to mods I use direct files because it's a lot quicker bc i don't have to run "deploy" Every Single Time I make a change to the texture to see the change when I preview the file in nifskope, simple as that. It's just not realistic to manually move files and deploy Everything with every step and the thing is usually Vortex handles it very well. If edit is made in game directory Vortex asks if I want to use the newer file, it's that simple.This is issue has only started to happen lately and it only happens randomly or at least seems to. So the point here for me is not "what if I should do mods in the most inconvenient way" but is Vortex doing this randomly and why, like is it a bug or something. But if you do have a method of editing textures that's more convenient I would be happy to hear it out.

Edited January 4, 2023 by omena007

[Guest deleted34304850]

if you're editing in the game folder - are you then deploying, and if so, why, given that the mod manager will try to revert changes it sees made to files it controls?

[showler]

It's not supposed to revert the changes. It's supposed to ask if you want to revert or save the changes. The problem appears to be that it is not doing so.