» Thu Oct 14, 2010 4:19 am
By default, you have the default profile, which is just the My Games\Oblivion\Saves folder. With Wrye Bash, you can right-click on the "Saves" tab, and create a new profile. Let's say you create profile "Test" and profile "Beautified." After creating the new profiles, you right-click on "saves" again, and switch to profile "Test". Back in the mods tab, you uncheck everything but the Oblivion.esm (and DLCShiveringIsles.esp, if you have it) and a plugin you want to test. You then launch the game, save and exit. Now profile "test" is associated with those two (or three) plugins. Reopen Wrye Bash, click on the "saves" tab, and switch to rhe "Beautified" profile. Back in the mods tab, you uncheck the plugin you were testing and check all of your regular plugins. Again, you launch the game, save and exit. Now, "Beautified" is associated with your regular mod. When you switch back to "Test," Bash unchecks all of your regular mods and rechecks the all of the plugins associated with "Test" (Oblivion.esm, possible the SI esp, and the plugin you were testing.) If you, again, switch back to "Beautified", Bash loads all of those other plugins, and unchecks the plugin you were testing.
That is Bash's save association in a nutshell. If you remove plugins associated with a save file, Bash pops up a message about it when you switch to or load that profile. Remember to switch to an associated profile before (un)checking plugins in your load order; otherwise, you will find yourself having to make the changes all over again. Bash associates the set of plugins made with the most recent save. The plugin lists of other saves do not matter.
Edit: I was not going to mention this, but, anyway, if you use the bashed patch for multiple profiles, make a bashed patch for each profile. BOSS recognizes "bashed patch, #.esp", for #s 1-9. I think it also recognizes "bashed patch, FCOM.esp"...