Fallout 76 Quick Configuration - Ini-editor And Mod Manager

[Claribel Lizama]

WryeBash is a powerful mod management utility for games based on Bethesda's Creation Engine. Its features include: A mod installation and conflict manager A plugin load order manager Increased mod compatibility Lifting of the 255 plugin limit through automatic merging of compatible mods .ini and settings files tweak management Screenshot management And many, many moreIt currently supports the following games:

Wrye Bash can appear daunting at first. To help make it more manageable, the documentation has been split into a few readmes that are targeted towards different usage requirements.This readme covers only the most commonly used features, so that the average user can start using Wrye Bash without being overwhelmed. Information on the less commonly used features and more technical details of the features covered in this readme may be found in the Advanced Readme. Information on some of the syntaxes and file formats that Wrye Bash uses are found in the Technical Readme. Finally, Wrye Bash's version history is stored in the Version History document.

This readme will also use the placeholder [Game]. Replace this with the game that you're managing with Wrye Bash. Additional terminology specific to Wrye Bash's functions will be introduced as required. Also, links that are followed by go to pages that are not part of the Wrye Bash documentation.

The simplest way to install Wrye Bash is using the installer, as it installs Wrye Bash and its dependencies automatically. Note: If you want to manage a Windows Store game (since the installer does not and cannot support Windows Store games) or prefer to manually install Wrye Bash for any other reason, read the instructions below.

Note: There are two versions of Wrye Bash available: the Python version and the Standalone version. Both are the same program, but the Standalone version has fewer dependencies and so is recommended for most people.Windows Vista, 7, 8 & 10 users: Windows' User Account Control feature may interfere with the running of Wrye Bash and other utilities. See the File Permissions section for solutions.Manual Standalone Version Installation: Download and install the latest MSVC Redistributable (x64). You now have a choice: Extract the downloaded Wrye Bash archive into any folder. Extract the downloaded Wrye Bash archive into the game folder (e.g. Oblivion, Skyrim or Fallout, depending on the game) so that the Mopy directory appears in the game folder. Run Wrye Bash by double-clicking Wrye Bash.exe in the new Mopy folder. If you chose the second option above, Wrye Bash will now open. However, you will have to repeat the procedure for each new game you install. If you chose the first option, you will see a game select screen. Simply select one of the listed games to continue: Manual Python Version Installation: Download and install all the required Python libraries and python itself. See the Python Components section of the Advanced readme for the list of included libraries and their versions. If you have previously installed Python and any Python libraries, you may not need to install them again. Download and install the latest MSVC Redistributable (x64). Extract the downloaded Wrye Bash archive into your game folder (e.g. Oblivion, Skyrim or Fallout, depending on the game) so that the Mopy directory appears by the game executable. See the Alternative Install Locations if you wish to install to a different directory. Navigate to the Mopy directory and run Wrye Bash by double-clicking Wrye Bash Launcher.pyw.Uninstallation Back to topThe ease with which Wrye Bash can be removed is dependent on how much you use it to manage your modded game. If you use a Bashed Patch, you will need to remove any dependencies on it from your saves before uninstalling Wrye Bash in order to avoid in-game issues. This may be near-impossible to do, depending on what is in your Bashed Patch. If you use BAIN to manage your installed mods, you will need to ensure that you have an adequate alternative management system ready, as although uninstalling Wrye Bash will not uninstall your mods, you will no longer be able to use BAIN's conflict resolution features. If you use any INI tweaks applied through Wrye Bash, you will need to make a note of which tweaks you have applied, as although uninstalling Wrye Bash will not undo your tweaks, you will no longer have any record of tweaks applied or default values. If you use the People tab, you will need to transfer your notes on people and record their karma outside of Wrye Bash.If none of the above points apply to you, or once you have taken the necessary measures for the points that apply, you can uninstall Wrye Bash by either running the uninstaller, if you used the installer to install Wrye Bash, or delete the following files and folders if you installed it manually. [Game]\Mopy - If you've edited any localisation files in the l10n folder that you want to keep, back them up. [Game]\Data\Bash Patches - If you've exported any CSV files that you want to keep, back them up. [Game]\Data\BashTags - If you've manually created any tag files that you want to keep, back them up. [Game]\Data\Docs [Game]\Data\INI Tweaks Documents\My Games\[Game] - Only delete the BashProfiles.dat, BashProfiles.dat.bak, BashSettings.dat, BashSettings.dat.bak, Messages.dat, Messages.dat.bak, People.dat and People.dat.bak files and the Saves\Bash folder. [Game] Mods (in the same folder as [Game] for most games, in Documents\Wrye Bash for Windows Store games) - The Bash Installers folder stores the mods you've installed via BAIN.Installing Mods Back to topOverview Back to top Wrye Bash's Installers tab.Wrye Bash mod installer are known as BAIN (BAsh INstallers), and are presented on the Installers Tab.The first time the Installers tab is opened, a dialog will appear asking if BAIN should be initialized.If you click Yes, BAIN will be initialised, which can take some time.After that, the information refresh performed when the Installers tab is opened is much faster.

If BAIN is disabled, i.e. if you clicked No on the dialog that was displayed the first time you selected the Installers tab, it can be re-enabled by right clicking on a column header in the Installers tab and selecting Enabled.Packages need to be placed in the Bash Installers directory which is created the first time Bash runs inside the "Game" Mods directory. This directory is by default created on the same level as your game directory (that is, if your game exe is located in "C:\GAMES\TESIV\Oblivion", then by default Bash will create the "C:\GAMES\TESIV\Oblivion Mods\" directory on first run), but you can point Bash to create this "Game" Mods directory wherever you want (or point it to an existing one) via the sOblivionMods ini setting. Do not however put it inside the game Data directory, as the game may well be confused and scan it adding to performance deterioration, mods thrashing.To add an installer to Wrye Bash Installers, you can either manually copy and paste the zip to the Bash Installers Directory, or just drag and drop the zip onto the Installers tab.Bash will scan the Bash Installers directory and pick up all subfolders and all archives - except for: folders or files that begin with -- will be skipped a Bain Converters subdir of Bash Installers will be skipped folders or files that begin with bash will be skipped you may specify additional directories to be skipped via the sSkippedBashInstallersDirs ini settingNow BAIN will try to classify the packages it detected in Bash Installers into its package formats - if it fails the package will display as unrecognized and will have tobe restructured.

When scanning an installer (package or project) BAIN follows some rules to decide what's in there and if it can be installed. BAIN will search for specific directories and file extensions (bsa/ba2, ini, all plugin extensions). All directory detection is case insensitive. Directories BAIN is aware of, independent of the game, are:

Note for mod authors: it is strongly recommended that you use either a simple or complex structure, not a scattered one! This will make it easier for users to inspect your package and will even allow them to perform the installation by manually checking the sub-packages. All major mod managers support these types of packages.

The easiest way to tell if a package needs manual converting to be compatible with BAIN is to try installing it. If it is listed in the Package list with a grey checkbox and name, then BAIN cannot install it. Due to BAIN's flexibility, many mods are already packaged in ways that are compatible, but for those that are not, there are a few possible cases: The mod has a BCF. BCFs are special packages that tell BAIN how to restructure the mod to be compatible with BAIN without the user having to do any work. The mod is distributed as an OMOD (i.e. has file extension .omod or .fomod). These mods are intended for installation with the Oblivion Mod Manager or Nexus Mod Manager. Such mods usually have a non-OMOD download option: if one is available, download that instead as it is more likely to be compatible. Otherwise, OMOD files can be converted to Projects automatically by dragging and dropping them into the Installers tab. The mod is distributed as an archive, or is a converted OMOD Project, but doesn't have a folder structure that BAIN recognises. It will need manual restructuring. The mod is distributed as an executable (i.e. has file extension .exe). This is very rare, as mods do not require the complexity of executables, and the greater security risk executables represent makes their use unpopular. BAIN cannot install mods distributed in this way: often the only way to install them is to run the executable. You can often run the installer, installing to a dummy folder, and then repack the installed files into a BAIN-compatible format.If an archive has a BCF, it can be converted for installation with BAIN using the following instructions. Ensure that the BCF is installed in the correct location, [Game] Mods\Bash Installers\Bain Converters. Also ensure that the archive(s) it converts is/are in [Game] Mods\Bash Installers. From the BAIN installers list, select the archive(s) to be converted (i.e., the source packages) and right click on the selected file(s) to bring up the context menu, and select Conversions to open the sub-menu. Click on Apply to open a second sub-menu and select the BCF from it. There may be more than one BCF listed if multiple installed BCFs can convert the selected package(s). An asterisk ('*') is added to the end of a BCF's name for every archive it converts that isn't selected. Optionally choose a name for the converted archive(s). Once Wrye Bash has finished the conversion, the converted archive(s) will appear in the BAIN package list ready for install. You can now delete the original archive(s).If a package is unrecognised by BAIN and has no associated BCF, its contents will have to be rearranged so that the structure matches one of the three types of BAIN-compatible package structures.

3a8082e126