omena007

Amazing! I was getting really paranoid I would accidentally destroy all my mods with the bug.

I'm just making sure I understood correctly: in your example do the files have same names but totally different folder paths? Does the injected mod type mean a mod that is deployed currently? In my case the files have same names and same folder paths except of course for the Mods root folder and they were all nif files. So both mods targeted the exact same files.

After the new update Vortex replaced incorrect files of a one mod with files from another mod within Vortex mod folders. this is pretty hard to explain and English is not my first. When Mod X loads after Mod Y (conflicting files), Vortex will actually try replace the files of the Mod Y with the files of Mod X within the vortex mod folder of the Y. The result is that you have identical files in the both mod folders X and Y. Normally Vortex doesn't touch the files, just changes which files are deployed to the game folder. So when I had the Mod X being deployed, Vortex asks if i want to deploy the changes in the Mod Y, but there were no changes being made, just Mod X that loads after Mod Y. In a hurry I didn't realize this and clicked deploy. The files that were in a totally different vortex mod folders were now replaced with the files from a totally different mod folder. And this actually happened to all of the mod folders the Mod X had conflict with. In other words: Vortex replaced/destroyed the Mod Y files in the vortex mod folder. Vortex should have not made changes into those files. I just lost a punch of mods/files made by me due to this bc I didn't realize what Vortex was doing before it was too late. Also if you think of commenting to this topic "Yeah right you just dum" (like someone already did) or in the lines of like I made this up for laughs bc I totally have no better things to do like consider: a. maybe you are not a software dev b. maybe your need of attention is not my problem. I have 600+ mods in use, made a few, I'm not making stuff up. I'm just letting people who actually develop the program know and warning others to watch out for this.

Hi! I wonder if there's an easy way to disable deleted items from an esp that is a patch to a master esp? I know that you can easily ignore the deletion of the items in the patch's details section (it just brings them back) but is there a way to just change these deleted items to disabled? Or is there a way to delete a file from the master in the patch esp so that it actually doesn't show up in the game? Bc making a patch and wanting to delete items from the master while manually disabling every single item and moving them to the side so they don't block your view in the creationkit is absolutely tedious. //edit. i got it to work but I don't know how.

My additional info for this bug is that using Wrye Bash esl-fication with Vortex gets esp's deleted but not always. Not sure if related.

Here's a screenshot. The situation with this case was that I checked the first mentioned Nithi's esp was not deleted, it was still in the game directory. with other esp's they were in fact deleted from game directory but I don't know how since I didn't do it myself. a) I'm the admin. b) My game folder is under my username's folder "Games". c)All files are on my internal c drive. I'm using windows. I also checked the deployment method is the default. When I replace a file or when creationkit or xedit replaces the file it should always have the very same name. The problems have only occured in these last 2 months and I have used vortex many years actively. I hope I understood these questions correctly, I'm not a native speaker. Thank you for the help in any case.

Thank you for your reply! I can give an example of one case that happened. I edited a player home esp file in creationkit which always edits the files directly in game directory. When the Vortex started to deploy files it gave me option to delete the edited esp file or restore the old version of it. there were other unrelated dds files I had also edited and with each of the files Vortex asked me to "accept" they had been deleted (they had not I checked the game directory) or restore the old one. I have tried to close and reopen Vortex after it does this but it won't deploy normally unless I choose delete or restore. there are no other options. I can put a screenshot here next time it happens but it will just show you the same options you get when you delete a file in the game directory. No errors, nothing weird. Does creationkit or photoshop do the backup files you mentioned? bc it seems weird when it happens rarely and not all of the time. I wanted to make this topic just in case it's a bug and also because it's really bothersome when there's many files in question when it does this.

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. The vortex normally deploys the changes made in either game or vortex directory, like said before.

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.

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.

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.

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.