I run a few different executables through MO which can create files. Generally, any such file created will always go to Overwrite. I often wish that there was a way to tell MO to always put certain files back into specific mods, so I don't need to keep manually deleting them from Overwrite, or run Overwrite->Sync all the time.
But I'm confused about what the exact rule is, because I know of at least one instance where a file that is created/updated by a process run from MO does not go to Overwrite, and instead goes into its original mod directory.
Specifically, I use the ReProccer, provided by T3nd0 for Skyrim Redone (SkyRe). This is a Java SkyProccer, which writes to the file ReProccer.esp.
ReProccer.esp itself was provided as part of the SkyRe mod. Every time I run ReProccer, it updates ReProccer.esp and the resulting, new/changed file does not go in Overwrite (although a bunch of other files created by ReProccer do - such as log files and backup files.) After running ReProccer, I can go check my "T3nd0s Skyrim Redone" folder, and see the ReProccer.esp with an updated Modified timestamp.
So what's different about ReProccer.esp? Why does this get written back to its originating mod when, for example, the Bashed Patch does not?
I thought that maybe the difference was that ReProccer.esp was provided originally by an installed mod - whereas the Bashed Patch I created new the first time I ran Bash. So I took my "Bashed Patch, 0.esp" file, and made a new mod out of it - putting it in an archive, and installing that archive into MO like a mod. I then ran Wrye Bash to update the patch, but it made no difference: the new "Bashed Patch, 0.esp" ended up in Overwrite again, and my own "Bash Mod" got the little lightning symbol against it to indicate its version of the file was redundant.
So every time I run Bash to make a new Bashed Patch, I need to go to Overwrite and choose "Sync to Mods.." and choose to sync it to my own "Bash Patch" mod. Until I've done that, I get the MO warning triangle.
Oh, and regarding those other files created by ReProccer - log and backup files. I once tried moving all those from Overwrite into the ReProccer mod, hoping that once they were in there, future updates to them would sync back there and not keep going to Overwrite; i.e., that they would behave the same was as ReProccer.esp does. But no luck; like most other files, besides ReProccer.esp, all those files always go to Overwrite.
This is certainly not the end of the world. But I'm really confused as to why I never have to do this with ReProccer.esp, when I do with seemingly all other files - even other files created by the same ReProccer process, at the same time.
Is there some change I can make that could result in other files - in particular the Bashed Patch ESP file - also auto-syncing to a mod, like ReProccer.esp does? Or is there some fundamental difference in how ReProccer is creating ReProccer.esp that results in this difference, and is outside of my control for other files?
For the future, as a feature enhancement, it would be great it if it were possible to set up "Overwrite auto-sync rules", to handle files like the Bashed Patch which are regularly written to Overwrite but which the user wants to reside in a specific mod. I'll raise a Feature Enhancement for that soon. Of course t's not that important or urgent, just a nice to have.
Question
TheBloke
I run a few different executables through MO which can create files. Generally, any such file created will always go to Overwrite. I often wish that there was a way to tell MO to always put certain files back into specific mods, so I don't need to keep manually deleting them from Overwrite, or run Overwrite->Sync all the time.
But I'm confused about what the exact rule is, because I know of at least one instance where a file that is created/updated by a process run from MO does not go to Overwrite, and instead goes into its original mod directory.
Specifically, I use the ReProccer, provided by T3nd0 for Skyrim Redone (SkyRe). This is a Java SkyProccer, which writes to the file ReProccer.esp.
ReProccer.esp itself was provided as part of the SkyRe mod. Every time I run ReProccer, it updates ReProccer.esp and the resulting, new/changed file does not go in Overwrite (although a bunch of other files created by ReProccer do - such as log files and backup files.) After running ReProccer, I can go check my "T3nd0s Skyrim Redone" folder, and see the ReProccer.esp with an updated Modified timestamp.
So what's different about ReProccer.esp? Why does this get written back to its originating mod when, for example, the Bashed Patch does not?
I thought that maybe the difference was that ReProccer.esp was provided originally by an installed mod - whereas the Bashed Patch I created new the first time I ran Bash. So I took my "Bashed Patch, 0.esp" file, and made a new mod out of it - putting it in an archive, and installing that archive into MO like a mod. I then ran Wrye Bash to update the patch, but it made no difference: the new "Bashed Patch, 0.esp" ended up in Overwrite again, and my own "Bash Mod" got the little lightning symbol against it to indicate its version of the file was redundant.
So every time I run Bash to make a new Bashed Patch, I need to go to Overwrite and choose "Sync to Mods.." and choose to sync it to my own "Bash Patch" mod. Until I've done that, I get the MO warning triangle.
Oh, and regarding those other files created by ReProccer - log and backup files. I once tried moving all those from Overwrite into the ReProccer mod, hoping that once they were in there, future updates to them would sync back there and not keep going to Overwrite; i.e., that they would behave the same was as ReProccer.esp does. But no luck; like most other files, besides ReProccer.esp, all those files always go to Overwrite.
This is certainly not the end of the world. But I'm really confused as to why I never have to do this with ReProccer.esp, when I do with seemingly all other files - even other files created by the same ReProccer process, at the same time.
Is there some change I can make that could result in other files - in particular the Bashed Patch ESP file - also auto-syncing to a mod, like ReProccer.esp does? Or is there some fundamental difference in how ReProccer is creating ReProccer.esp that results in this difference, and is outside of my control for other files?
For the future, as a feature enhancement, it would be great it if it were possible to set up "Overwrite auto-sync rules", to handle files like the Bashed Patch which are regularly written to Overwrite but which the user wants to reside in a specific mod. I'll raise a Feature Enhancement for that soon. Of course t's not that important or urgent, just a nice to have.
Edited by TheBlokeLink to comment
Share on other sites
3 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now