I reinstalled my oblivion data and most if not all of my oblivion folder and now I have my official DLC files listed in OBMM and WB but no bash patch file.

I am new to the game for a week and not modder technically inclined at this time. I follow directions fine, can install manually if told, trying to learn how to use WB's Bain to install from archives to minimize bad installs (had to clean up Data/Data, Texture/texture, etc before), etc.

When I first started out, there was a thread or something showing how to set this all up.

Thanks.

I believe what you were looking for is in your mopy folder wrye bash.html. I take it you are looking for the official How to use Wrye Bash, the web site that they used to have up for it is no longer up. So they included the Html with the wrye bash. good luck

Patch Usage

? Select a Bashed Patch

? Probably Bash has automatically created one for you. If not, you can copy the blank one from Oblivion\Mopy\Extras to Oblivion\Data.

? Note that the author of the mod must be set to Bashed Patch.

Orange: All package files are present in the data directory, but some esps/esms are not identical. (E.g. another package installed an alternative version of that file, or the user modified the file after installation.)

Grey: Indicates that some files present in the package will not be installed. This is usually due to a complex structure that is only partially handled by Bain, but can also be due to having files that Bain refuses to install (exe's, dlls, sub-archives, etc.)

Bain Conversion Files (BCFs) allow modders to essentially repackage existing archives into a new layout. A BCF doesn't contain any files that are available in the original archives. This means that a BCF is freely distributable, and there is typically no need to worry about permissions. The only files included in a BCF are any new files that you added to the new layout (typically "package.txt" and *.ini tweaks), and a BCF.dat that tells Bash how to reorganize the files. A BCF is usually under 20kb in size.

? Notes

? BCFs are stored in the Oblivion Mods\Bash Installers\Bain Converters directory. This is referred to as the BCF directory.

? The fastest way to access this directory is to open Bash, navigate to the Installers Tab, and right-click on the column header and choose "Open...". This opens Oblivion Mods\Bash Installers and you should easily see the BCF directory.

? BCFs must either end in -BCF.7z or -BCF-*.7z, but the resulting converted archive may use .7z or .zip.

? BCFs store the configuration settings of the original converted archive.

? BCFs supports any level of embedded archives within an archive.

? Any duplicate BCFs in the BCF directory will be moved to Oblivion Mods\Bash Installers\Bain Converters\--Duplicates

? Important: BCFs use what 7z refers to as the "Data CRC" to associate themselves with archives. This "Data CRC" is the cumulative CRC of all the files within an archive, and it is not the same as the CRC of the archive itself. If two archives contain the same files, even if one is a .zip file and the other a .rar, they will have the same "Data CRC". This means that BCFs ignores both the names of archives and how an archive was compressed. For this reason, Bash displays the "Data CRC" on the General Info tab of projects and archives.

? Creating a BCF

? Add all of the source archives to Bain

? Create a new project, and rearrange the files until you are satisfied

? Right-click on the project, and choose "Pack to Archive..."

? Name the new archive, and choose whether to use solid compression. Solid compression will result in a smaller file size, but will also reduce performance, so it is only really recommended for large archives that won't need to be annealed very often. The name will be used as the default suggestion for the BCF name. If this archive uses solid compression, the converted archive will too.

? Set any options on the new archive package that you wish to be initially set whenever the BCF is applied.

? Select all of the source archives in the Installers Tab, right-click and choose "Create..." under the "Conversions" menu. Select the target archive (that you just created and setup), and name the BCF.

? Look over the result log, and make sure that it looks alright. If there is a large number of contained files in the BCF, you may have chosen the wrong source or target archive.

? If it looks wrong (large size, large number of contained files), you may either open the BCF directory and manually delete the new file, or you may simply overwrite it by creating a BCF with the same name.

? If it looks right, you can find the BCF in the BCF for distribution. It is recommended that you copy/paste the result log into your readme for your BCF.

? Installing BCFs

You've downloaded a bunch of BCFs. Now what?

? Simply copy all of the *-BCF.7z and *-BCF-*.7z files that you downloaded into your BCF directory.

? Applying a BCF

? Bash will only display the BCFs that are currently valid. Valid BCFs are those that end in -BCF.7z or -BCF-*.7z, and have all of their required source archives visible on the Installers Tab.

? If a source archive has any associated BCFs, you will see them listed when you right-click an archive package and open the "Conversions" sub menu. If the "Apply" menu is grayed out, then there are no valid BCFs for that particular archive.

? An asterisk is added to the end of the BCF name for every source archive it requires that you don't have currently selected (but do have installed).

? Select a BCF from the "Apply" menu.

? Choose a name for the converted archive, or use the default name suggested.

? Wait while Bash unpacks the source archive, rearranges the files, and packs the converted archive.