@SonOfCronus: Sorry, currently I can't offer Wyre Bash compatibility. Obmm does contain a save file viewer and it will work with omo. I don't know of any other tool for that.
@SonOfCronus: Sorry, currently I can't offer Wyre Bash compatibility. Obmm does contain a save file viewer and it will work with omo. I don't know of any other tool for that.
This sounds really great, when I get the time I'll see if I can use this to get a few mods I've been wanting to try but have never been able to because they work at cross purposes to certain mods I don't want to play without.
Hey there, works great for me! Quite nice tool, easy to use and very handy if you want to keep a clean folder structure - especially if you have a larger selection of mods starting to clutter your Oblivion installation
Okay thats all I can think of for now, you have more than enough to chomp through already - I would add another note to your description though, for the inevitable recurring problems new users have with the games default installation folder and clashes with UAC, otherwise this comments section will just go around in circles with the same answer to the same old question.
Take care. Alt
Edit: Popped back in to give kudos, you deserve it for even contemplating taking this idea on
You can control which files are seen by the order of entries in the modlist file, similar to how the load order of esps work.
Also, omods are already supported, there is a hack in place. When obmm installs an omod, it extracts the relevant file to a temporary directory and then tries to move them to "data". At that point omo pops up a dialog and asks for a directory to redirect to. I installed mbp, ooo and darnified ui through this mechanism, all work fine.
The only problem I can see with your unified data and mods folder is that if you can re-direct Wrye Bash to look at the folder, where one mod has different choices of esps not yet installed (for example a non-cobl version and a cobl version, or an animated windows and lights version vs not AWLS) which esp is Wrye bash going to look at. Which set of anims for Surazals Sensual walks (out of the multitude he provides), and which individual vwalk.esps to import anims from ... just a few examples I can think of.
You will also need to provide some method of scripted installs too for the thousands of mods with choices before installation, as in Scripted OMODS or BAIN Wizards. Heres AWLS Wizard asking me if I have RAEVWD installed before it makes selections from its 235 sub-package options.
Its a huge task to undertake. Otherwise the user will have to extract omods or bains beforehand, determine how they eventually get installed, and only put esps esms bsas and all the relevant textures meshes sounds in your mods folder which they want in game. Theres no doubt that this will not be competing, but to say the least its one heck of an ambitious project.
@Mirelurk: Thanks for the report. I'm sorry to hear it doesn't work for you (mostly because that means I have to fix a bug. ). Did the omod-installer place anything in either Obliviondata or Oblivionmods? Did it change Oblivionmodsmodlist.txt? Did omo create the file Oblivionomo.log and if so, does it contain anything interesting? Finally: What is your windows version?
@alt3rn1ty: I haven't looked at bashed patches, so I will indeed add a disclaimer until I checked it out. What I do not want to do is create an equivalent to existing functionality. I want my tool to make life easier for users and mod developers, not more confusing by creating "competition" to wrye bash. My hope is that I'll be able to properly integrate my tool with wrye bash the same way it integrates with obmm so that wrye too will only see the "unified" data+mods directory and just continues to work as before.
Give Feedback
24 comments
Comments locked
The author has locked this comment topic for the time beingDidn't know it had one. Thanks
Obmm does contain a save file viewer and it will work with omo. I don't know of any other tool for that.
If I can't make it work with Wyre Bash, is there another Save File Viewer I can make it work with?
Thanks
Okay thats all I can think of for now, you have more than enough to chomp through already - I would add another note to your description though, for the inevitable recurring problems new users have with the games default installation folder and clashes with UAC, otherwise this comments section will just go around in circles with the same answer to the same old question.
Take care.
Alt
Edit: Popped back in to give kudos, you deserve it for even contemplating taking this idea on
Also, omods are already supported, there is a hack in place. When obmm installs an omod, it extracts the relevant file to a temporary directory and then tries to move them to "data". At that point omo pops up a dialog and asks for a directory to redirect to.
I installed mbp, ooo and darnified ui through this mechanism, all work fine.
You will also need to provide some method of scripted installs too for the thousands of mods with choices before installation, as in Scripted OMODS or BAIN Wizards.
Heres AWLS Wizard asking me if I have RAEVWD installed before it makes selections from its 235 sub-package options.
Its a huge task to undertake. Otherwise the user will have to extract omods or bains beforehand, determine how they eventually get installed, and only put esps esms bsas and all the relevant textures meshes sounds in your mods folder which they want in game.
Theres no doubt that this will not be competing, but to say the least its one heck of an ambitious project.
Did the omod-installer place anything in either Obliviondata or Oblivionmods? Did it change Oblivionmodsmodlist.txt?
Did omo create the file Oblivionomo.log and if so, does it contain anything interesting? Finally: What is your windows version?
@alt3rn1ty: I haven't looked at bashed patches, so I will indeed add a disclaimer until I checked it out. What I do not want to do is create an equivalent to existing functionality. I want my tool to make life easier for users and mod developers, not more confusing by creating "competition" to wrye bash. My hope is that I'll be able to properly integrate my tool with wrye bash the same way it integrates with obmm so that wrye too will only see the "unified" data+mods directory and just continues to work as before.