Dirty plugin clean through Vortex with SSEDIT

[Darkf0rge]

Been tearing my hair out over this for a couple of hours.

Can anyone tell me the steps to do this properly? It worked one time permanently for some reason but now it seems anytime I purge and deploy mods it writes back the dirty Plugins all over again. I really don't want to do this over and over again.

 

Had the same issue with some form 43 Plugins but I ended up being able to get around that by copying the fixed plugin from the games folder and zipped up into another mod for a reinstall.

 

In the case of these ones I really do not want to reinstall.

This seems like one big problem with a virtual system. But it looks like it must be possible because one of the ones I've cleaned has remained so.

After I do the clean, and deploy I get a message that it's been changed from outside and do I want to apply it permanent. and I confirm but it does not work.

 

Anyone know? can't seem to find any tutorial on it.

[LawrenceFB]

 

 

Been tearing my hair out over this for a couple of hours.

Can anyone tell me the steps to do this properly? It worked one time permanently for some reason but now it seems anytime I purge and deploy mods it writes back the dirty Plugins all over again. I really don't want to do this over and over again.

 

Had the same issue with some form 43 Plugins but I ended up being able to get around that by copying the fixed plugin from the games folder and zipped up into another mod for a reinstall.

 

In the case of these ones I really do not want to reinstall.

This seems like one big problem with a virtual system. But it looks like it must be possible because one of the ones I've cleaned has remained so.

After I do the clean, and deploy I get a message that it's been changed from outside and do I want to apply it permanent. and I confirm but it does not work.

 

Anyone know? can't seem to find any tutorial on it.

 

 

 

Only a suggestion, but try just 'deploy', as that should notice the binary has changed and offer you the option to apply or undo. Apply means keep your changes. Only click the 'apply' button if you want to change it to 'undo/override/overwrite'. Do click the 'confirm' button as this is the one that does the work. Purge may be, and this only a guess, deleting you changed file before Vortex notices the change.

[Tannin42]

When you clean one of the vanilla/dlc files, vortex shouldn't make any difference.

When you clean a mod esp/esm you should do so in the game directory as you usually would if you were using any other tool. Then the next time you deploy vortex will tell you that there was an external change to the esp. Click apply there and it should copy the modified file over to the mod directory.

If after you confirmed the "external changes" dialog you still have different files between mod directory and game directory that would be a bug.

[Darkf0rge]

Thanks for the response Tannin42, much appreciated.

 

I understand this is an alpha obviously but I am already finding it way better to use than the alternatives, so nice work on that front.

Unfortunately I had already cleaned my vanilla dlc files, so not sure there but I definitely cleaned one where it worked fine. I am a bit nervous about using another tool to do it at this stage.

 

Example plugin is the BSHeartland.esm from Beyond Skyrim Bruma that comes back, as long as I do not purge mods it stays cleaned.

 

With the form 43 plugins I was simply able to do the upgrade in the CK then take the file from the game folder and manually paste it into the relevant mods folder to resolve.

Can't seem to do a similar thing with SSEEdit though. One thing I noticed is properties of those files doesn't seem to change at all which is odd, I guess it's because often they are just empty records, but the timestamp doesn't change either.

 

I definitely get that confirmation about external changes but they don't seem to stick. If I just deploy it's not an issue yes, only when I need to use purge and redeploy for whatever reason, seems like it might be a bug. Just sing out if there is anything I can do too assist.

 

*Edit*

 

Well after playing around and switching to a different profile and reloading it seems the problem has gone away, so now I am confused what I have done to make it work.

I stopped trying to troubleshoot it yesterday assuming its a bug after a clean, and continued building my profile so things are muddy. So Ill keep this in mind next time a dirty plugin comes along that needs cleaning and see how it goes.

 

Cheers