Where is oblivion mods bash installers

The basic question I'm having a hard time locating in the guides What is the point of the Installer tab really? Sorry if these seem like dumb questions These packages are shown in the Installers Tab in Wrye. To install one of those packages, right-click on it, and choose "Install".

If you then go to the "Mods" tab, you'll see all esp-files Skyrim currently has in it's Data directory. There the new esps of your newly installed mods have to be activated by left-clicking on the checkboxes on the left of them.

After enabling those esps run BOSS to configure your load order. You can also load up your game with TESVEdit and see where your mod esps conflict and then determine which esp should win over the others and place this esp lower than the others.

If using the Boss Userlist Manager, you can also select categories which match what the esp is doing best, for example "Water and Lava". It will then show you a list of mods changing those aspects in Skyrim and you can place it amongst them. THANK you tormenator! That helps quite a bit! There are just so many guides and little instructions but they're scattered all over. Wish they revamped the STEP guide just a tad more for people like me that just want a clear, what-to-do-next process and all in a row.

Maybe i'll work my way up and be a contributor or something, to maybe clear some of it up for future modders! At least that way I know they will appear so I can work with them. It details installer management at a much more detailed level than the official doc. It would be redundant to add what is already well documented in the official doc. You need to be a member in order to leave a comment. Sign up for a new account in our community. It's easy!

Already have an account? Sign in here. By using this site, you agree to our Terms of Use. Search In. Sign in to follow this Followers 1. Question mobias 0. Mismatched is which files are installed same file name , but are different, either because they are overwritten by a later mod, or were hand changed. Skipped lists files and directories that are not installed because Wrye Bash doesn't recognize them. Some are silently skipped and not listed. The only affected culprit here is - once again - Oblivion Reloaded 9.

Lastly, Underridden and Dirty usually happens when you change the order of installers and can be fixed by right clicking on the mod and selecting Anneal. Except for curiosity while actually creating mods, I barely check those. Shape Squares are archives zip, rar, 7z. Diamonds are unpacked directories also called "projects". Can be fixed by right-clicking and selecting Anneal. Yellow - The install has underrides. Text Color Navy Blue - This is really hard to see. It means the package has sub-packages.

You can create them by right clicking on the header, selecting Add Marker They are only used for convenience, if you want to visibly group mods between two markers. In case of patches, just make sure to really load the updated esp last, and you can also just uncheck the esp in the outdated packages so it all turns yellow again. If the icon is grey or red, you need to look into it. If a mod has a yellow or orange background, hit Anneal.

You can select what to install on the right side by checking and unchecking boxes. As you can see, I selected some of the sub-packages and some of the esps of this mod. To sort the sub-packages, they are usually named with a two digit number in front. Other options are often grouped up, like here all the different cup sizes. If several options have the same number, it usually means you have to pick only one of those. There is no point in selecting more than one of the 10s.

They have a special Icon. It will guide you through the installation process. At the end, you have the choice to apply your selection, install the files or both. It can't hurt to switch to the Ini Tweaks tab and double check, though. Some mods are not recognized by Wrye Bash. This is often the case with very old mods, from a time when there was no mod manager and no common structure, but also.

Fish for the files you want and place them in the right structure into the new directory. You can probably follow these, but , instead of moving them to the Data directory, you move them into your newly created folder.

Depending on your installation size, this will take a long time, so if you can do it manually, that's probably preferred.

If not, press that option. You can now follow whatever install instructions to put the mod directly into your data folder, be it installing it with oblivion mod manager or as an exe file. It will scan the folder again and then present you with a window of all the files it found that were added to the data folder.

Press create project and add a name. You know when I said to occasionally close Wrye Bash and open it again? If you haven't done so yet, now would be a splendid time to do so, so all your preparations and orders are saved. Right click on the mod. Select Install. Installing many at once might take a long time. I personally wouldn't install more than a few at a time.

If that happens, right click on them and use Anneal. Unless for some reason you are making changes to mod files in the Data folder, it should always be safe to use anneal after you've changed something. The installer icon will turn orange, though. This will also keep them safe should you ever accidentally or on purpose replace them with an uncleaned version. This will also keep cleaned DLCs safe that would be reset by verifying game data with steam.

Answering no is semi-permanent and will leave you unable to install that certain dll with Wrye Bash unless you reset some settings. To change which dlls you trust, click on the little cogwheel in the status bar and select the option Trusted Binaries. There you can move dlls from Untrusted to Trusted and back.

If by uninstalling a mod the conflict status of any resources changes, Wrye Bash will handle it automatically. I assume this is so you don't lose your changes or configs. This is useful if you changed a package after initially installing it.

You could select "Install Missing Files" to only install files that were not installed before. Careful : This will not install files that have been installed before, even if they would be changed now in the new config. A double click opens the archive or directory, so you can look inside, and, in the case of a directory, edit files directly.

This will give you a list of changed files that you can pack into the mod file. This works on both, archives and directories. If you want to add cleaned esps back into the mod file they came from, or keep them all in a separate folder, is a matter of preference. I would suggest using one way or another to keep them safe, though. There are a few mods that cannot be installed with Wrye Bash.

Realistic Leveling requires manually editing the ini, as it ships with placeholder values in its ini that would get set by the OBMM install script. However, I would suggest checking out Ultimate Leveling , which has a RL mode and is much more modern and should not carry the same bugs RL did. The full package of QTP comes in 11 eleven.

However, I don't think most of them work well nowadays, and would be especially incompatible with ENB and Oblivion Reloaded, which most people use these days. I honestly would stay away from modifying the game shaders.

When we refer to projects and archives together we will also be using the collective term packages or installers.

If BAIN is disabled, ie. Packages need to be placed in the Bash Installers directory which is created the first time Bash runs inside the "Game" Mods directory. 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 setting Now 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 to be restructured.

When scanning an installer package or project BAIN follows some rules to decide what's in there and if it can be installed. All directory detection is case insensitive. Directories BAIN is aware of, independently of the game, are:. Complex Installer has top-level subdirectories that each have a simple structure as defined above.

The top level subdirectories known as subpackages must NOT have the same name as any of the standard game directories for this game like docs, or meshes. Otherwise BAIN thinks this is a simple package and will skip subpackages. Each top-level subdirectory will be treated as a sub-package, and can be independently activated or deactivated as desired. It is treated as a simple installer, starting at this top level subdirectory. Examples include mods packaged with a top-level Data directory.

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. The mod is distributed as an OMOD ie. 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. It will need manual restructuring.

The mod is distributed as an executable ie. 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. From the BAIN installers list, select the archive s to be converted i. Click on Apply to open a second sub-menu and select the BCF from it. 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. This can either be done via Windows Explorer, or by dragging and dropping the package into the Wrye Bash window when the Installers tab is open. If you drag and drop, you will be asked whether you want to copy the package or move it. For the most part, you can simply right-click the package and select Install If you want to learn more about each type of package and how to install and configure their options manually, read on.

If a package contains a Wizard ie. You can also choose to install using the Wizard's default options by selecting Auto Wizard. If you chose Manual Wizard , navigate through the steps of the Wizard to install the package. Otherwise, you will be skipped to the Wizard finish screen. At the Wizard's finish screen, click the Finish button to apply its selections.

Choose which plugins to install from it using the Plugin Filter box to the far right of the package list. Checked plugins will be installed, while unchecked plugins will be skipped. Right-click the package and select Install If a package has a Complex structure: Select the package in the package list. Choose which sub-packages to install from the Sub-Package box to the right of the package list. Checked sub-packages will be installed, while unchecked sub-packages will be skipped.

If you install a package then later change the sub-packages or plugin files selected, you can apply these changed by right-clicking the package in the list and selecting Anneal. A Wizard provides a scripted installation method that can be useful for more complex mods with many options. Any files that are simply named readme eg. To uninstall any package from the Installers tab select the package and right click on it, then select Uninstall.

This will uninstall all Matched files. A Mismatched file is a file that has been altered after it was installed.

For example, if the file was altered because it was replaced by another mod that was installed manually, then uninstallation of the Mismatched file may not be desirable. On the other hand, if the file was altered because it was cleaned or edited with TESxEdit, or because it was an ini file that was edited with a text editor, then it may be desired to uninstall the Mismatched file along with the package that it came from.

Such files could be deleted from the data folder manually, but there is an easy way to do this through BAIN. Before uninstalling the mod, first select the package and right click on it, then select Install Configured. This will overwrite any Mismatched files with the version of the file contained in the package, making them Matched.

You can also uninstall packages that BAIN hasn't installed, which will remove any installed files that match the ones in the package. This is useful for cleaning out mods that were manually installed. Of course you need to add the packages to BAIN first. Uninstalling via BAIN respects the ownership of files, ie.

However, if the Auto-Anneal option is enabled the default , then files from other packages previously overridden by the uninstalled package's files will be automatically restored. The Install Order of packages in BAIN is important as this decides which package gets its files installed in the case of resource conflicts. Packages may be listed in Install Order by left-clicking on the Order column header. If two packages try to install the same file, then the package installing later in the list will have its file overwrite the file of the package installing earlier in the list.

For example, files in a package in install order position 06, would overwrite conflicting files in a package at install order position Note that packages with a higher install order appear lower in the list of packages, and that may lead to confusion as people refer to them as "lower".

The order of sub-packages within a package follow the same rules as packages. Checked sub-packages later lower in the sub-package list will overwrite conflicting content from sub-packages earlier higher in the list than them.

Package conflicts are detailed in the Conflicts tab to the right of the package list when you select a package. This tab tells you which packages have which files that conflict with files in your currently-selected package. It gives this information for packages in the Install Order both earlier and later than the selected package in the package list. BAIN allows you to easily adjust the conflict status of packages by moving their order around.

This can be done by dragging and dropping packages within the list, or by right-clicking packages and selecting the Move To You can also select multiple packages and move them, in which case they will be moved as a group, retaining their order relative to one another in their new location. A third option is to select the package s and use Ctrl-Up or Ctrl-Down to move them up or down respectively. BAIN uses the colours of packages in the package list and the state of their checkboxes to convey information about their status to the user.

A checkbox state may be combined with any checkbox or text colour, and the possible states and colours are described in the tables below. Note: Installed packages are marked with a plus, eg.

Corrupt or incomplete packages are marked with a cross, eg. They don't represent an archive or folder and so contain no files, but may be used to organise the package list. Checkbox Shape Meaning The package is a Project, ie. The package is an archive. Checkbox Colour Meaning All the files in the package are installed as configured.

Some or all of the files in the package are not installed as configured. All the package files are installed, but the. All the package files are installed, but some resource ie. This can happen for complex packages where none of the sub-packages are selected for installation.

BAIN does not recognise the structure of this package so cannot install it. Grey BAIN does not recognise the structure of this package so cannot install it. Orange Background The install is dirty. This will occur for packages for which the configuration has been altered either by altering active sub-packages and esmps, or by altering the package itself. This can be repaired by running Anneal or Anneal All.

Yellow Background The package has "underrides" i. This may happen after reordering mods that have already been installed. It can be repaired by running Anneal or Anneal All.

Grey Background Some files present in the package will not be installed. Useful Context Menu Commands Back to top The following commands found in the package and column header context ie.

Open Folder Opens the Installers directory in Windows Explorer. Opens a dialogue window allowing you to select which hidden packages to unhide. Refresh Data Re-scans the Data directory and all project directories. This is done once per run of Wrye Bash, when the Installers tab is first opened. If you manually alter the directories after that, you should run this command to update BAIN to reflect the changes. BAIN refreshes itself automatically if changes are made to packages in the Bash Installers directory.

New Marker Creates a marker for organising your packages. List Packages Displays a list of projects and archives and copies the list to your clipboard. This is useful for posting your package order on forums, eg. Uninstall All Packages Uninstalls all the packages in the package list.

Clean Data Removes files from the Data folder that are not from one of the following sources: Vanilla game content. Official DLC content. Wrye Bash. Installed BAIN packages. Anneal All Installs any missing files for active installers and corrects all install order errors.

If this is checked, files in the script extender plugins folder e. Opens the selected package s in the file system. Renames the selected package or marker. Makes a duplicate of the selected package s.

Delete Deletes the selected package s. Deleted packages are sent to the Recycling Bin, not permanently deleted. Open at Attempts to open the selected package's page on the selected site. If Google is selected, performs a Google search for the package name. For the other three sites, this command assumes that the trailing digits in a package's name is the package ID at the sites. If this assumption is wrong, a random page, or an error page, will be opened. Anneal Installs missing files and corrects install order errors according to the package configuration.

Advanced Installation.. Install Configured Fully installs the package as configured except for files that would be overridden by later packages. Wizard Installer.. Manual Wizard Runs the Wizard for the package, if it has one. Auto Wizard Runs the Wizard for the package, if it has one, selecting the default options.

Uninstall Uninstalls the package. If Auto-Anneal is active the default then files from earlier packages that were previously overridden will be installed as required.

Quick Refresh Refreshes all info for the selected package s. Note that scanning a project for changes takes much longer than scanning an archive for changes.

Move To Moves the selected package s to the specified position. List Structure Generates a list of the files and directories in a package. Useful for posting package structure on forums, eg. Has Extra Directories BAIN only recognises a limited set of subdirectories of the Data folder, and skips any unrecognised subdirectories.

Checking this option will cause BAIN to install unrecognised subdirectories. Overview Back to top Wrye Bash displays your installed plugins in its Mods tab. Your load order of active installed plugins, which Wrye Bash marks with a ticked checkbox, is important as it decides what plugin 'wins' any conflict between plugins, with later loading plugins overriding those that change the same thing.

A mod loading later in the list will have a greater number in the Load Order column, and will "win" if there's a conflict with a mod loading earlier which will have a lower number.

Load order is not the same thing as BAIN install order! Install order determines which package's files overwrite other packages files when they conflict. Although in general "Load Order" stands for the load order of the active plugins, all installed plugins have a load order assigned to them. Bash needs plugin load order even for inactive plugins to correctly merge inactive mods in the Bashed Patch, for instance.

Plugins may be activated by clicking their checkbox so that it is ticked, or by selecting a plugin or group of plugins and pressing the space bar on your keyboard. Plugins may be deactivated by again clicking their checkbox or pressing the spacebar. If a group of selected plugins contains a mix of active and inactive plugins, pressing the space bar once will activate them all, thereafter it will function as normal.

Some plugins are explicitly dependent on other plugins - they have these plugins as masters. When a plugin is activated, its masters are also activated. Conversely, when a plugin upon which other plugins depend is deactivated, those plugins are also deactivated. When setting the load order, make sure that Wrye Bash is displaying your plugins sorted by Load Order. Do so by clicking on the Load Order column header near the top of the tab.

You can also display the plugins sorted by other attributes by clicking on any of the other column headers. Clicking twice will reverse the display order for any column but Load Order. The load order of plugins is given in hexadecimal digits, from 00 to FE, which is 0 to in decimal. This number also forms the first two digits of a record's Form ID. Note that you can only have a maximum of plugins active at any one time, including your game's master file.

Generally speaking, if you end up with an invalid load order of some kind, Wrye Bash will automatically fix it upon booting or refreshing, but a backup copy with the. With the advent of ESL files , the load order system was modified.

The following list contains the most important facts you need to know about how Wrye Bash handles ESL files:. Just like the game's masters, this load order is hardcoded, and so it cannot be changed - Wrye Bash will show an error message when an attempt is made. Setting up a correct load order that minimises detrimental conflicts that could cause issues in-game can be a difficult and time-consuming process.

Effective load-ordering often requires a knowledge of what each plugin in your load order contains so that you can position the plugins to minimise these conflicts. For simple mods, the description in the mod's readme will usually be sufficient to determine the records it contains, but to be sure a utility such as TES4Edit is required.

LOOT can be used to greatly simplify the process of setting the load order, as it can correctly position thousands of plugins automatically. However, you may still need to order some plugins manually. Moving plugins up or down the load order by selecting them and using Ctrl-Up or Ctrl-Down respectively. This also works with groups of plugins and preserves the group's internal order. Dragging and dropping plugins will also change the load order if the plugins are being sorted by Load Order.

Timestamp-based games only. Editing plugin modification dates in the right-hand details panel. When running Wrye Bash, you can also lock your load order in place to prevent unintended changes to it by selecting the Lock Load Order option in the column header right-click menu. Note that this will prevent other utilities from changing the load order, so uncheck this option if you use such a utility to set your load order. Note that for Skyrim and later games Wrye Bash will automatically undo any changes to load order done made by the game's launcher or any utility that does not follow the textfile-based load order standard in order to maintain a fully coherent load order.

This effectively means that unintended changes are prevented. Like in the Installers tab, Wrye Bash uses colour-coding and other formatting effects to convey information about the state of plugins. The different types of formatting used and their meanings are explained here. Many of these can be changed in the Color Configuration menu. The context menus for the column headers and plugins contain a large number of commands, most of which are unlikely to be of use to the average user so are not detailed here.

New Bashed Patch Creates a new Bashed Patch plugin. Useful if you accidentally delete your current one or wish to have more than one. List Mods This lists the load order, including version information, activation status and major load order errors. It can be useful for debugging a broken load order. If the Shift key is held when this command is selected, the CRCs of plugins will also be displayed in the output. If the Ctrl key is held, then the versions of plugins will not be shown in the output.

In Skyrim there is a different problem, namely if you have over mod files in your data directory, the engine just plain refuses to load any of them, active or not see here: Thrashing, thread 1, post 1. Auto-Ghosting adds a. When a ghosted plugin is activated, the. Note that most other utilities will not recognise ghosted plugins, so there are options available for individual plugins to control which get ghosted. Bash displays a warning if a lot of mods and BSAs are detected that you can disable via the ini.

If enabled, then any built Bashed Patches will automatically be ESL-flagged, saving a load order slot. Lock Load Order This prevents other utilities from altering your load order. More accurately, it detects changes to your load order when Wrye Bash starts or is focused i. Outputs a list of the selected plugin's masters. List Bash Tags