Jump to content
  • 0

Having WB use MO's mod directory


Question

Posted

Hi,

 

I'm trying to use Mod Organizer on a different hard drive from my skyrim install and having trouble getting Wrye Bash to use the directory.  I've removed the semi and changed the value of sOblivionMods in bash.ini to the complete directory of the MO mods directory and it's not recognizing it.  Is there something else I must set to have this work?

 

Thanks

  • Answers 39
  • Created
  • Last Reply

Top Posters For This Question

Recommended Posts

  • 0
Posted
  Quote

You have to have MO running and launch WB from MO.

Where within MO is that launched from?

 

I've added Wrye Bash.exe to the executable list in MO.  Selecting that and running it still does not find mods.

 

For bash.ini the only line not semicolon'd out is sOblivionMods=G:\Games\Skyrim\ModOrganizer\mods

 

Any thoughts?

  • 0
Posted

Are you using MO to organize the mods and then WB to make the patch?

 

Or are you trying to use MO to just download the mods and want WB to install them?

 

If the former then you just have to start WB from MO and you'll be able to rebuild the patch no problem, go back to MO and start the game as usual, since the bashed patch won't change.

 

If the latter, you might as well take MO out of the equation.

  • 0
Posted

I'd like to use MO for downloading and easy updating and use WB for the clean installs/uninstalls.  From what I read in the step guide and on the step wiki, this seems like the best layout.  What would be the correct setup for that?

  • 0
Posted

Ok I understand now, you failed to account for the fact that WB appends \Bash Installers. What you need to do is adjust the download directory in MO to G:\Games\Skyrim\ModOrganizer\mods\Bash Installers and everything will work fine. You will need to move anything already downloaded to the new folder.

 

From SIG

  Quote

Copy then rename the file "bash_default.ini" to "bash.ini," and place this alongside the former. The INI lets you define many useful things including where Wrye looks for installers. Edit bash.ini and replace the "\Oblivion Mods" directory references with "\Skyrim Mods", set bSkipResetTimeNotifications=True and bResetBSATimestamps=False. Now just update any other paths or settings as necessary for your system. Many users prefer to keep Skyrim Mods\ directory on a different harddrive particularly if running skyrim from SSD. Do not try to change the "\Bash Installers" directory reference, as that is hardcoded, and Bash will create it inside Skyrim Mods\.

  • 0
Posted

The problem with that is that using MO for downloading is fine, but updating wont work unless the mod is installed through MO. It checks the installed mod's version against the version on the nexus. Your best bet is to use NMM for downloading/updating and WB for clean installs and such. You'll still have to get NMM to download to the bash installers folder, but it can check the nexus for updates without the mod having to be installed through it, so then you can freely install with WB

  • 0
Posted
  Quote

The missing /Bash Installers was the issue, thank you.

 

Are there any other directories I will need to set via .ini?

Yes, you need to follow the Skyrim Installation Guide replacing the examples with your own directory structure.  Also make sure to set the other listed parameters for proper functionality.
  • 0
Posted

Ok, I'll look at this in the morning but just out of curiosity can Wrye Bash, etc be installed to program files with UAC disabled? Trying to move skyrim somewhere else with the mover just created more headaches for me when I don't need UAC anyways (though I do have it on the lowest setting).

  • 0
Posted

I'm not sure why you think you don't need uac, you have another better security system running?

 

There is really nothing to moving it, you can just literally cut and past the steam directory wherever you want then reinstall steam overtop where you just moved it too and validate skyrim if you want to go the manual way.

  • 0
Posted

I have, however I think there may have been registry settings leftover which caused the issue. I'm going to Revo it and terminate everything with extreme prejudice. I really hate windows, if the performance hit wouldn't be horrendous I'd just assume run all of my 'essential' Winblows programs in WINE. I'll post again if I run into anymore problems, which knowing me and Wrye Bash is more than likely.

  • 0
Posted

Ok, so I installed everything, followed SIG to the letter again. Now I'm trying to run Wyre Bash from Mod Organizer and as before Wyre Bash won't open. Skyrim is installed to C:\Games\Steam\steamapps\common\skyrim

 

I'm posting the Wyre Bash bash.ini that was generated at install (I did not have to rename anything though it says Wyre Bash 299 instead of 300, I did customize it though I know I must have something wrong)

 

 

  Reveal hidden contents

 

 

 

Edit: Seeing it here makes it look different than either Notepad or Notepad++ I assume all of the following instances of Wyre need to be replaced with my username?

 

  Reveal hidden contents

 

 

Also I almost forgot but here is a screenshot of my Mod Organizer Settings

 

  Reveal hidden contents

 

Also I cannot get BOSS(BOSS.exe) to run correctly the cmd box comes up and says I have the latest version installed and then it closes, I tried switching the target to the BOSS GUI.exe but it worked even less.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.