WryeBash not seeing my mods

[Thick8]

I recently added a 2nd hard drive and moved my MO files to the new drive. MO2 and Skyrim work fine but when I open WryeBash through MO2, WryeBash opens without seeing my mods and creates a bashed patch, 0.esp in the skyrim data folder. I feel the issue may lie in the bash_default.ini file but am unable to make it work.

Here are my paths:

Skyrim:    C:\Steam\steamapps\common\Skyrim\skse_loader.exe

MO2:    C:\ModOrganizer\ModOrganizer.exe

MO2 user files:    E:\Users\John\ModOrganizer\Skyrim

WryeBash:    C:\Steam\steamapps\common\Skyrim\Mopy\Wrye Bash.exe

 

Any help would be appreciated.

Thanks.

John

Edited September 30, 2017 by Thick8

[Greg]

You should use Mod Organizer 1.3.11 for Skyrim Legendary Edition. Mod Organizer 2 is for Skyrim Special Edition and Fallout 4.

[Thick8]

I use MO2 for all of the Bethesda games. WryeBash was working properly prior to moving folders to the E drive. I'll play with the Bash.ini file I guess and see if I can figure it out.

[Mertz]

I recently added a 2nd hard drive and moved my MO files to the new drive. MO2 and Skyrim work fine but when I open WryeBash through MO2, WryeBash opens without seeing my mods and creates a bashed patch, 0.esp in the skyrim data folder. I feel the issue may lie in the bash_default.ini file but am unable to make it work.

Here are my paths:

Skyrim:    C:\Steam\steamapps\common\Skyrim\skse_loader.exe

MO2:    C:\ModOrganizer\ModOrganizer.exe

MO2 user files:    E:\Users\John\ModOrganizer\Skyrim

WryeBash:    C:\Steam\steamapps\common\Skyrim\Mopy\Wrye Bash.exe

 

Any help would be appreciated.

Thanks.

John

Some people have experienced trouble using the Standalone executable version of Wrye Bash with MO2, so it is suggested that you run the Python version of WB, one of the latest builds.

 

Outdated TV created a video how-to on how to get WB Python installed with MO2 here:

https://youtu.be/5yNU9XF9zmc

 

I need to emphasize that this is not a Wrye Bash issue. Wrye Bash is an extremely powerful mod manager in and of itself and is still being very actively developed to support new game features. If something changes in the future that makes it incompatible with MO/MO2 it is not intentional.