Wrye Bash ini Paths help

[yarddogg77]

I've downloaded and installed wrye bash. I moved my Skyrim install to C:\Games\Skyrim, then installed Wrye bash. The Mopy folder is in my game folder right where it should be, Wrye bash sees the installed mods (nothing right now), and my games saves. I'm trying to add mods in loose file format to the installer folder for editing in wrye bash. I have copied the bash_default.ini file and renamed it bash.ini like it says to do. Now all I need to do is set the paths so wrye bash knows where everything is. Unfortunately the bash.ini file is written like crap and hard to understand, as is almost every tutorial about Wrye Bash. It doesn't look like any ini file I'm used to dealing with. I don't know which paths to change. I am modding skyrim not Oblivion, and damned near everything starts with Oblivion. I need help with this.

 

Skyrims install path is C:\Games\Skyrim

The installer folder is C:\Games\Skyrim Mods\Bash Installers

 

I don't know which other options I might need to change for other software but I've got it all, TesVEdit, Loot, Bain, and I'm using NMM. Which options am I supposed to change because there are about 16 of them.

[Thenryb]

Thread necromancy. Having same questions as you did. When I saw this in Google I thought finally I would get an answer only to find you had gotten no responses. My Skyrim install and intaller folder is set up the same as yours except no "Games" folder. Your comments about trying to figure out the default ini are spot on.

[NocturnalDeity]

I believe I had the same problem. I'm using wrye for fallout 4 and thought I would have to change the oblivion part in the ini paths, but I believe this is part of the .ini that is needed to guide for any game regardless. I'll paste below the example of what worked for me.

 

[General]

;--sOblivionMods is an alternate root directory for Bash Installers and other Bash data.

; Putting it under the game's install directory can cause performance problems

; during gameplay, so by default it is placed at the same level as the game folder.

; Here are the Oblivion and Skyrim defaults, and two other examples.

;sOblivionMods=..\Oblivion Mods

sOblivionMods=F:\Games\Fallout4 Mods

;sOblivionMods=C:\Games\Oblivion Mods

;sOblivionMods=C:\Steam\SteamApps\common\Skyrim Mods

;--sBashModData is the directory containing data about your mods, ini edits, etc.

; If using MOM, mTES4 Manager, or other utility to manage multiple installs,

; you will want to change this to keep the Bash data with your saved games.

; You'll need to use an absolute path to your saved games folder, so here

; are the defaults and a few examples.

;sBashModData=..\Oblivion Mods\Bash Mod Data

sBashModData=F:\Games\Fallout4 Mods\Bash Mod Data

;sBashModData=C:\Documents and Settings\Wrye\My Documents\My Games\Oblivion\Bash Mod Data

;sBashModData=C:\Users\Wrye\AppData\Local\Skyrim\Bash Mod Data

;--sInstallersData is the directory containing data about which installers

; are installed by Wrye Bash. If you changed sBashModData above, you'll

; probably want to change this one too. Examples:

;sInstallersData=..\Oblivion Mods\Bash Installers\Bash

sInstallersData=F:\Games\Fallout4 Mods\Bash Installers\Bash

;sInstallersData=C:\Documents and Settings\Wrye\My Documents\My Games\Oblivion\Bash Installers\Bash

;sInstallersData=C:\Users\Wrye\AppData\Local\Skyrim\Bash Installers\Bash

;sInstallersData=C:\Users\Wrye\AppData\Local\Skyrim\Bash Installers Data

;--OblivionPath is the game directory (containing Oblivion.exe, TESV.exe, etc).

; A "normal" install of Bash will place the Mopy directory in your game directory.

; Use this argument only if you placed Bash outside of the game directory and the

; automatic detection and -g command line parameter fail to find the game.

; If using a relative path, it will be relative to the Mopy directory.

;sOblivionPath=C:\Games\Oblivion

;sOblivionPath=G:\Oblivion

sOblivionPath=C:\Games\Fallout 4

;--User directory arguments.

; These arguments allow you to specify your user directories in several ways.

; These are only useful if the regular procedure for getting the user directory fails.

; And even in that case, the user is probably better off installing win32com.

;--UserPath is the user profile path.

; May help if HOMEDRIVE and/or HOMEPATH are missing from the user's environment.

; Example=C:\Documents and Settings\Wrye

;sUserPath=C:\Documents and Settings\Wrye

;sUserPath=C:\Users\Wrye

;--PersonalPath is the user's personal directory ("My Documents").

; Should be used in conjunction with either the -l argument or

; setting sLocalAppDataPath.

;sPersonalPath=C:\Documents and Settings\Wrye\My Documents

;sPersonalPath=C:\Users\Wrye\Documents

;--LocalAppDataPath is the user's local application data directory.

; Should be used in conjunction with either the -p argument or

; setting sPersonalPath.

;sLocalAppDataPath=C:\Documents and Settings\Wrye\Local Settings\Application Data

;sLocalAppDataPath=C:\Users\Wrye\AppData\Local

;--SteamInstall Bash will try to detect if you have a Steam install but

; if it fails to properly detect it (or incorrectly detects that you do)

; you can set this to the desired setting.

;bSteamInstall=True

;bSteamInstall=False

----

I applied bold to the lines edited. I only touched portions of the .ini under General. Despite modding fallout 4 I needed to maintain the oblivion portion. I don't know enough technical aspects to know why this is the case, but it is. Also note, in case you're not aware, the semi-colon ( ; ) before the lines you wish to be used must be deleted for the .ini to register your entry. Review for any unintended spaces in the edited lines after saving as sometimes this is an easy mistake for some and it will also not work. Hope this helps!

[JWRaven]

Confirming this solution worked! Thank you NocturnalDeity! Realizing it's an old post, but still relevant.

[bodiddley]

Confirming this solution worked! Thank you NocturnalDeity! Realizing it's an old post, but still relevant.

I'm also grateful for the suggestion, but for some reason Wrye Bash wouldn't read the bash installers once I moved it and kept recreating a new (empty) mods and installers folder in the old location. I used a Symlink ...

https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

...and then put that link in the old location and voila! Wrye Bash reads the link as if it was the original folders there and I get to save the space on my SSD :)

 

Hope it helps. This is a long dead post, but it's not the first time I've wanted to do this and it's worked well both times.