Oblivion Mod:Choosing from Multiple Downloads

Introduction

Sometimes mod download pages have two, four and many more than one options. Sometimes the choice is obvious, as in the case in which an OMOD user has to choose between the not speciall labled download and the OMOD-Ready version. This page simply introduces the different options and for whom each is most desirable.

The Download Types

• Not Labeled: If this is the only option, it might be OMOD-Ready or BAIN-Ready even if the download does not have a description indicating that. Check the mod's description. If it is a simple package, it can be easily prepared for all installation methods, anyway. Sometimes these are executables too.
• OMOD-Ready: This is probable the second most common option. OMOD-Ready indicates that the archive already has an OMOD info folder with the files that will automatically fill out the fields in the OMOD creation window (after adding the archive.)
• OMOD: The mod is already packed in an OMOD file. The OMOD might be packed into another ZIP file, if the author was concerned about the size, but OMOD's are already compressed archives, so often the download will be the actual OMOD.
• BAIN-Ready: These archives are organized in a format that Bash's installer BAIN can be used to install them. These archives may also be OMOD-Ready. Check the mod's description.
• EXE or Installer: These mods are packed into executables that can be run like any other executable one would run on Windows. Sometimes they add entries to the Program Files folder too. Normally, only large mods, such as quest mods, use this format, but some other mods use this format as well. The uninstaller is normally installed to the Data folder with the rest of the mod's files.
• Manual: These are the same as not labeled mods with the exception that they definitely do not included OMOD info (not OMOD-Ready.) Many mods are BAIN-Ready that are not labeled as such because BAIN is new (compared to other installation methods) and there is no reason to add the label to simple mods, really...

The Download Situations

Most Preferable for Manual users

1. Executables require the least work. Double-click to start the install procedure, and then double-click on the unistall file to clean everything up again. Choose this version, when they are available...
2. It is rare to see the "Manual" flag, but that is what you want to choose given the option when EXEs are not offered. The only real benefit this format has over OMOD-Ready options is that they do not include the extra files required for the OMOD.
3. Unlabled mods are "manual", unless specified otherwise.
4. BAIN-Ready downloads simply follow certain organizational rules. There is no reason for the author to offer a BAIN-Ready option and a manual (or unlabeled) option. The basic rule of BAIN package structure is that the entire archive must reflect installed mod structure OR the archive must be split entirely into subfolders that all meet that requirement. Where BAIN users are instructed to check a certan subpackage or plugin, the manual user should copy that package or plugin into the Data folder.
5. OMOD-Ready downloads are fine too, but they may not be organized as nicely (because OMOD packaging rules are practically non-existant as long as there is a script to handle the packaging.)
6. OMODs should be avoided. You must use OBMM to do anything with them. If that is the only option, and you have OBMM, and you want to install the mod manually, choose the convert to archive option from the OMOD menu in OBMM, and everything will be fine.

Most preferable for OMOD users

1. OMODs are the best option. Download the OMOD, double-click on it to register it with OBMM and then activate it from within OBMM (and hope that the OMOD script works.)
2. OMOD-Ready downloads require only one additional step, adding the archive to an OMOD.
3. For every other option excepting executables, if the download is a simple package, the only difference between these downloads and OMOD-Ready downloads is the automatic fill-in (because the archives lack OMOD info). If the package is complex; hopefully, you can find a script. If not, write a script for it (and depending on the complexity that might not be difficult at all) or install it manually (which can become a bit of a mess for an OBMM user.)
4. Executables should be avoided when possible. The best cascenario is that the installer gives you the option of installing the files to a location of your choice, and then the folder's contents can be packed into an OMOD. If that is not possible, using an installer is akin to installing a mod manually without having any say in overwrites, which is worse than mixing manual an OMOD installation by quite a bit. Fortunately, most executables are quest mods that use all new files and will not ovewrite anything.

Most preferable for BAIN users

1. BAIN-Ready downloads are the best choice.
2. For every other option excepting executables, if the download is a simple package, the download is already BAIN-Ready. If the package is complex and is not BAIN-Ready (indicated by a dark gray check box or gray highlight) the archive will have to be repackaged. OMODs belong in this group too because you just need to use OBMM's convert to archive to create a 7-zip version of the OMOD.
3. Executables should be avoided when possible. The best cascenario is that the installer gives you the option of installing the files to a location of your choice, and then the folder's contents can be packed into an archive to be put into the Installers folder. If that is not possible, using an installer is akin to installing a mod manually without having any say in overwrites, which is worse than mixing manual an OMOD installation by quite a bit. Fortunately, most executables are quest mods that use all new files and will not ovewrite anything.