Oblivion Mod:Load Order

The UESPWiki – Your source for The Elder Scrolls since 1995
Jump to: navigation, search

Introduction[edit]

A load order is the "date modified" ordering of your the plugins that are processed in the game from earliest to most recent, the order in which content is processed by the game engine. Active plugins are plugins loaded into the game. A plugin is installed once you put it in your data folder, but it is only active if the launcher shows that it is checked. Oblivion's launcher does not allow you to do much with your load order outside of activating and deactivating plugins. This becomes another of the motivations for installing a mod management utility (i.e, OBMM, Wrye Bash, etc.) These tools let you move plugins around (by modifying their timestamps) through a GUI, with buttons and your mouse.

Example #1 - a simple load order (with fake timestamps)

  • Oblivion.esm (timestamp=2006)
  • Progress.esm (timestamp=2007)
  • Unofficial Oblivion Patch.esp (timestamp=2008)
  • DLCShiveringIsles.esp (timestamp=2009)
  • Progress.esp

Once you have more than a few plugins, putting a well-structured load order together is no simple task. Even if you have only a few mods, your small load order can still be very order-dependent. There are a few rules that are forced by the game, and then there are many more rules that appear as a result of plugin interactions. Certain groups of mods are better off loading in certain locations in a load order because of how they overlap with other mods in that load order. First and foremost, Oblivion.esm load first. Then, all of the ESMs are loaded after it, followed by the ESPs. If a load order breaks these enforced rules, the game will throw errors and problems at the user.

Example #2 - a simple correct load order

  • Oblivion.esm <-- Oblivion.esm is first ✓
  • Progress.esm <-- ESMs are next ✓
  • Unofficial Oblivion Patch.esp <-- ESPs bring up the end ✓
  • DLCShiveringIsles.esp
  • Progress.esp

The other "rules" are more implicit (unless you are looking at the insides of plugins.) You learn through trial and error, and it takes time. However, there is one utility that can expedite the process of ordering plugin lists, and that is BOSS. It is not perfect, and it does not recognize every plugin, but BOSS does recognize over 13,000 plugins, and the LO it generates is a nice place to start. For many mods, especially older mods, BOSS has more current placement and compatibility information than what might be in the ReadMe, so it is okay if the LO it generates does not match that of every ReadMe. As for the unknowns, the mods it does not recognize, (or how one might go about hand-ordering an LO) the LO template below is a good reference. Use a mod's download category, description and compatiblity information to help place it where it needs to be.

The last set of rules have to do with plugin dependencies. Plugins must load after their masters. Both ESMs and ESPs can have dependencies. An ESM cannot depend on an ESP because ESMs must load before ESPs. However, ESMs can depend on other ESMs and ESPs can depend on either type of plugin. They can both have multiple masters, but most ESMs do not depend on more than one ESM, and most ESPs depend upon one ESM. However, patches (always ESPs) often depend on multiple plugins. Not only must plugins load after their dependencies, but also their dependencies should be in the dependent order. If the masters have overlapping records, missorting them can cause serious problems in the game. If the masters are in the correct load order, and the dependent's list does not match, the dependent plugin's master list needs to be sorted.

Example #3 - a simple correct load order

  • Oblivion.esm <-- Oblivion.esm is Progress.esp's first master, loading at 00 ✓
  • Progress.esm <-- Progress.esm is Progress.esp's second master, loading at 01 ✓
  • Unofficial Oblivion Patch.esp
  • DLCShiveringIsles.esp
  • Progress.esp <-- Progress.esp is loading after all of its masters ✓

Pay attention to your load order. It is completely separate from mod installation order. Get BOSS. It is a great tool, very useful, but do not just use it. If you use plugins that it does not recognize (i.e., plugins of your own making) you should have some idea of where those should go. Even if you do not let BOSS sort your load order, you can run it, and use the BOSS Log as a guide, no harm done. If mods do not seems to be working properly, do not forget to check this. Many, many mod-related issues can be resolved by making a few quick adjustments to the load order. The last thing to note is that the Oblivion LO is limited to 255 plugins, including the Oblivion.esm. The closer an LO is to that number, the more unstable the game will get. Be mindful of that too, and make choices accordingly. All installed plugins and BSAs count toward another limit, a total somewhere between 300 and somewhere over 400, varying based upon unknown factors. Keep your data folder and your load order clean of unnecessary and unused mod files.

Load Order Jargon[edit]
  • Some of the following are used when speaking of install order as well.
  • override - load after
    • (Ex: "A should override B." => "A should load after B."
  • give priority - load after
    • (Ex: "Give B priority (over A.)" => "Have B load later (after A.)"
  • dependency (or master) - plugin a plugin depends upon
    • (Ex: "A is B's dependency." => "B is a master of A." => "B modifies A."
  • master file - ESM

The Bash-Extended Load Order[edit]

Wrye Bash has upped the level of complexity of the Oblivion load order, in a good way (for those that use it or plan to use it.) The presence of the Bashed Patch introduces two new plugin states, merged and imported, and they allow for much greater compatibility among mods. When you rebuild the Bashed Patch (by right-clicking on it and choosing the appropriate option from the context menu) there are the groups of options: the merge menu, the import menus and the tweaks menus.

Plugins selected in the merge menu, have their content merged into the Bashed Patch. The merge is in accordance with the load order, so if two mods make changes to the same record, the latter's changes will be found in the Bashed Patch (unless some other setting in the Bashed Patch changes it, as the Bashed Patch loads latest.) The plugins does not have to be active at the time of the merge. If the plugin was not active prior to the merge or was unchecked afterward, Bash displays a plus sign in the check box, indicating that the plugin is merged. The plugin is still installed, however. There is no point leaving a merged plugin active because its changes are being completely written over by the Bashed Patch. Once you merge a plugin, deactivate it.

Notes: 1) Bash-mergeable plugins are distinguished by green text. 2) Some Bash-mergeable mods only need to be imported, and those are often have purple-text. Those with purple text have been tagged with NoMerge.

Plugins selected in the import menu have content that meets the criteria of the specific import merged into the Bashed Patch. Again, the merge is in accordance with load order. However, only changes are imported. If a mod's records are not overwritten by other mods in the LO, those records are not being changed by anything and, thereby, will not be imported into the Bashed Patch. To ensure that a plugin's changes are imported, deactivate the plugin before rebuilding the Bashed Patch. Few mods are import-only. Those tend to be aesthetic mods (i.e., retexturers.) If a mod is not import-only (as is the case with most race mods and worldspace-affecting mods) do not deactivate it before rebuilding.

Notes: 1) Import-only plugins are distinguished by italicized and/or purple text. 2) Some plugins that are mergeable, and even some that are not, deactivated to be import-only. If activating the Bashed Patch causes the plugin(s) to be reactivated, that is not a possibility.

Taking advantage of these extended features not only allows for greater compatibility among mods, but also allows the user to save plugins slots. Deactivated and imported mods can be ghosted (hidden from the game.) Deactivated mods do not count toward the 255 plugin cap because they are not part of the load order; however, they can still be installed. Take advantage of Bash's ghosting feature, by manually right-clicking on plugins and selecing the option from the context menu or by setting auto-ghost in the File header context menu. Other features of Bash that make it a very helpful LO management tool are 1) the Lock Times features, also available through the File header context menu, that, when activated, prevents installation of new plugins from messing up the load order and 2) the check box colors that indicate whether a plugin's masters are present, missorted or missing (which is okay only for plugins with the Filter tag.) There is not tool that gives the users as much information about the state of their load orders, and, for Obilvion, that is quite important.


Load Order Template[edit]

based on the BOSS masterlist ...

  1. Oblivion.esm
  2. ESMs (see ReadMes)
  3. Early-Loading Mods (see ReadMes)
    1. NPC Faces
    2. Vanilla Fixes - miscellaneous fixes, UOP, etc.
    3. SI - miscellaneous fixes, USIP, etc.
    4. Fran files for FCOM
      1. Base Mods - library mods, new content mods, etc.
      2. Environmental Mods - weather, water tweaks, sound, lighting
      3. Mods that can be overwritten or add new content
      4. UI mods - Map Marker tweaks, Hotkey mods
    5. DLCs I - Horse Armor, Orrery, Vile Lair, Mehrunes, Spell Tomes
    6. Body replacers
  4. Items
    1. Early loaders (see ReadMes)
    2. New items
    3. Armor and clothing replacers for body replacers
  5. Pre Overhaul (see ReadMes)
    1. Mods with specific conflicts
    2. Mods that change names (that can use the Import Names Bash tag)
    3. DLCs II - Thieves Den
  6. Overhauls (See ReadMes for specific load ordering information)
    1. Fran options
    2. FCOM and OOO support mods
    3. OOO
    4. MMM & FCOM (main)
    5. MMM & FCOM options (must see ReadMes for specific load ordering info)
    6. Other overhaul-compatible mods
    7. Overhaul immediate override patches
  7. Post Overhaul (see ReadMes)
  8. Quests and Locations
  9. FCOM quest compatibility patches
  10. More quests (See ReadMes)
  11. Landscape and City aesthetics
    1. Unique Landscapes
    2. Mods that have to load after ULs and before city overhaul mods
    3. Open Cities
    4. Quests that have to load after OC and ULs
    5. Overrides
      1. Harvest Flora
      2. Other visual improvements (i.e., Better XX)
      3. Realism
      4. Vampires
      5. Magic
      6. Combat
      7. Skills, Attributes and Leveling
      8. Poses and animations
      9. Late loading overrides - darkening mods, Item Interchange
      10. Cosmetic mods and race rebalancers
      11. Companions
      12. Post BC and OBC
      13. Message suppression
      14. Respawn & Day length overrides (most made obsolete by bashed patch)
      15. Shader mods
  12. Pre Bash (See ReadMes)
  13. Bashed Patch
  14. Post Bash (See ReadMes)
    1. Most Duke Patrick mods
    2. Last Files
      1. Land Magic
      2. Map changing mods
      3. Stability mods (scripts) - FormID Finder, Kuertee Actor Details, Clean up, Clean quit, OGE Support, Streamline (last)

Load Order Management Utilities[edit]

BOSS automatically orders more than 10000 plugins, and it will save the user a ton of work when it comes time to perfect an load order. After running BOSS, it will place plugins that it does not recognize at the bottom of your load order and those should be moved by hand with Wrye Bash before launching the game and/or updating Bashed Patches.

  1. BOSS


See Also[edit]

Retrieved from "https://en.uesp.net/w/index.php?title=Oblivion_Mod:Load_Order&oldid=3179058"