I had a general question about Wrye Bash (and possibly OBMM) functionality.
Say I download a texture replacer/ some other sort of "replacer" mod, that is supposed to overwrite Oblivion's original files - if I install that mod using WB or OBMM, does it overwrite the existing files, or does it hide/rename/backup the original files and put the new files from the mod in their place?
I ask because if I uninstall the mod, will the original files also be lost, or will they be restored by Wrye Bash? Or is this handled in another way?
Well...
the
vanilla files are in BSAs so how could they be overwritten ?
Now if mods are installed in this order :
modA
modB (overwrites content from modA)
files from modA will be overwritten
If both mods are installed with BAIN you can use anneal upon uninstalling modB (or auto anneal if you uninstall modB with BAIN) to restore modA files
Now I have a
request :hubbahubba:
I have already talked about this.
packageA
packageB
packageC (overwrites content from packageA)
It would be great
if files would be actually backed up with BAIN. So upon installing packageC above a dialogue would pop up :
"You are about to overwrite content from packageA" "Proceed" "Back it up first" "Cancel"
If "Back it up first" were chosen the to-be-overwritten files would be transferred to a folder Conflicts\packageC\packageA (titles of packages could be too long - a check should run to truncate filenames accordingly or \\?\ used - at own risk)
A choice should be available in the ini - whether this dialogue would be displayed in all cases, on CRC mismatch or never.
Why ?
It is not about installation so much as about
mod anatomy - I was always doing this kind of thing myself with tools like teracopy and beyond compare, backing up the files manually - but, believe me, it is a hassle and one ends up with folders "Conflict" all over the place and mistakes are made etc etc. This feature would be very useful if one wanted to examine conflicts - or examine which meshes got PyFFi'ed to find a problematic one - or archive/examine differences in versions of his/other people's mods. Right from bash - with no other tools and in an orderly fashion (details to be worked out - like probably backing also up the meshes from packageC at the same time, labeling the folders according to if CRCs match or not (default choice) etc). Including conflicts where CRCs match is probably too much - but it can be informative (this info could just be retrieved from the installers tab anyway).
Installation-wise there is some use of the above procedure also - one could open the conflicts folder, zip the conflicts and create an override package. One could simply change the install order you'd say - yes - but what if one would want only some of those packageA files and the rest from C (could be done manually but
it is a hassle) ? And though install order is more flexible than load order there are cases that moving packages around could break things.
This would be great for testing one's various versions of one's mods also.
Anyway this was something I was missing sorely in OBMM - which only warned and only for omod children IIRC. I hoped to find it in BAIN - half found it but only for install purposes not for general mod use/packaging/comparing/whatnot.
I'd say that initially an implementation only for CRCs mismatch, with minimal choices - and the conflicts dir in Oblivion Mods\Bash Mod Data - would be 99% of what needed. The bottom line of remarks is that Bash has got already the info in its hands - a pity not to use it, no ? I have spent countless hours archiving conflicts for one reason or the other and it is a rather frustrating hobby lol
I really hope I am not asking too much, I have no clue how all this is implemented
Thanks
:bow: