I think Bash would best serve the future of Nehrim modding if it were either able to handle multiple installs of Oblivion via ini swapping, save game profile swapping, and swapping of all the settings it has.
What you talk about practically falls under the purview of what I previously said. However, please bear in mind that the implementation of these things may differ from what you think.
For instance, we have INIzer, which tells Oblivion to load different ini files. Save game "profiles" are set in the INI - as is the path for the Data folder. The problem here is getting Bash to read the right INI. How would we get what INI the user wants to read? Do we just say "Please select the INI file you wish to read preferences from?" and hope they have it set up right?
Make it so that one could have multiple Wrye Bash installs each with their own settings, BAIN folders, and and be based on whatever data folder they are installed in.
Well, thanks to the magic of copying your Oblivion folder - as prescribed in the Nehrim installation guidelines - this is quite possible! Even right now! Just plop this version of Bash into your Nehrim folder, and use the good ol' original flavour Bash in your Oblivion one. However, this spreads stuff out a fair bit.
I may try your version but I'm not looking for what makes bash work with Nehrim and damn the Oblivion game - I want Bash with both at the same time.
This version should fix the crashing bugs from before, assuming the problems were caused by it loading the normal Bash settings file and getting stuffed up.
Right now, my setup works rather well - but I don't play Oblivion as well as Nehrim (yet), so it might be that it's something I haven't stumbled upon. Time will tell!
As an aside - if INIzer changes the INI file read, and the OBSE plugins folder is in the Data folder,
is it reasonable to assume that changing the Data folder in the INI is a bad idea for this sorta thing? If the plugins are always loaded from "Data/OBSE/Plugins/", then it's a rather "chicken-and-egg" situation - after all, plugins would still be loaded from the normal Data directory no matter what INIzer says! In other words, using two different
Data folders might be implausible.
EDIT: Oops. Fixed.