airbreather
commented
7 years ago Looks like what's happening is Wrye Bash is saving its own config stuff (which should be profile-specific) in steamapps\common\Skyrim Mods\Bash Mod Data\Table.dat. For example, if I rebuild the Bashed Patch for STEP Extended, close Wrye Bash, switch profiles to STEP Core, and list the patch config for the Bashed Patch, it'll still tell me that the patch was configured with STEP Extended Patch.esp (along with other Extended-specific stuff, not with any Core-specific stuff like the STEP Core Patch).
So when I go to rebuild the patch, it thinks it needs to newly import names and stats from the STEP Core Patch.
This feels like it should be relatively benign, but regardless, it does in fact seem to be at least tangentially related to the rebuilt patch getting blown up.
Wrye Bash doesn't seem to have any command-line arguments that will help in this case. However, it does look like I can override sBashModData in bash.ini, so I think I can work around this by creating separate bash.ini files for each profile and replacing the Wrye Bash executable in MO with multiple batch files (one per profile) that copies the profile-specific bash.ini file (given by a command-line argument to the batch file) into the Wrye Bash directory and overrides sBashModData with the path to a folder under the profile-specific directory.
What just happened? I rebuilt the Bashed Patch for STEP Core after updating BSW to 2.0.08, and it ballooned to 7x the size it was before? It also all of a sudden started importing a bunch of stuff from STEP Core Patch.esp.
Does it have anything to do with rebuilding the STEP Extended and STEP Extended (My Tweaks) versions and not clearing the Overwrite folder in between those and rebuilding the STEP Core version?
I don't have the time to look into this right now.