- #Skyrim special edition mod organizer 2 how to#
- #Skyrim special edition mod organizer 2 mod#
- #Skyrim special edition mod organizer 2 mods#
I wonder if MO1 is writing something WB is reading for the virtual modlist that newer versions of WB can't handle? Where the last file listed in the error is configparser, it sounds like it may be dying on reading a config file.Īnyway, I'm at my wits end with this one.
#Skyrim special edition mod organizer 2 mod#
So I'm trying to figure out if maybe it's an incompatibility with the version of Mo (the legacy very linked to from the MO2 mod page) and WB 306 or 307 (tried both). Anyway, I've seen references to bad characters in ini files causing WB to choke, but I've yet to find anything that might be the culprit. But running it through MO1 throws this error, and I've been researching it for days, (without the help of the STEP forums, as the STEP site is currently down.go figure.). If I run the WB exe directly, it loads my Skyrim data folder without error, obviously without anything installed through MO1. Then test running Wrye Bash, and it throws an error:įile "bash\bash.pyo", line 381, in _detect_gameįile "bash\initialization.pyo", line 161, in init_dirsįile "ConfigParser.pyo", line 242, in _init_ĪttributeError: 'unicode' object has no attribute 'items' Then I go installing the extenders (FISS, SKSE, etc), run LOOT, and order my mods. After creating a completely clean build, and launching MO, I can launch Wrye Bash from MO just fine. I'm using the STEP 2.10 guide (I've used STEP previously a few years ago and my Skyrim build was extremely stable, so I figured I'd give it a try again). I'm having problems with Skyrim LE using MO1 and launching Wrye Bash through it.
#Skyrim special edition mod organizer 2 how to#
#Skyrim special edition mod organizer 2 mods#
Submit Help Post Submit Text Post Posting Rules FiltersĪdd, ,, , or in the title of your post so posts can be filtered! Unfilter Using Mods