File information

Last updated

Original upload

Created by


Uploaded by


Virus scan

Safe to use

About this mod

Setting the right load order for your mods is a crucial step to enjoying a stable modded game. The Load Order Optimisation Tool (LOOT) can help with that, by providing automated load order sorting that's simple to use and fully customisable.

Permissions and credits

Load Order Optimisation Tool


LOOT is a plugin load order optimiser for TES IV: Oblivion, TES V: Skyrim, TES V: Skyrim Special Edition, TES V: Skyrim VR, Fallout 3, Fallout: New Vegas, Fallout 4 and Fallout 4 VR. It is designed to assist mod users in avoiding detrimental conflicts, by automatically calculating a load order that satisfies all plugin dependencies and maximises each plugin's impact on the user's game.

LOOT also provides some load order error checking, including checks for requirements, incompatibilities and cyclic dependencies. In addition, it provides a large number of plugin-specific usage notes, bug warnings and Bash Tag suggestions for Wrye Bash.

While LOOT is able to calculate correct load order positions for the vast majority of plugins using only their content, it cannot do so for all plugins. As such, LOOT provides a mechanism for supplying additional plugin metadata so that it may sort them correctly. An online masterlist is provided to supply metadata for many plugins that need it, while users can make their own metadata additions, which are saved in their userlist.

LOOT is intended to make using mods easier, and mod users should still possess a working knowledge of mod load ordering.

See Introduction To Load Orders for a general overview and LOOT’s Sorting Algorithm for an in-depth article on how LOOT operates.


To learn more about LOOT, please read it's documentation over at Read The Docs:
- Application Documentation
- API Documentation


LOOT's official version as well as all accompanying files can be downloaded from it's official website or from this Nexus page, though the Nexus will exclusively provide the "LOOT.Installer.exe" executable, which is per se everything you need. In case you prefer a preconfigured .7z archive over an installer executable, please head over to LOOT's official website.

Unofficial "snapshot builds" are a work in progress and generally used to test future versions of LOOT and provide feedback for WrinklyNinja. They are made available on Bintray - however this Bintray link should only be used by experienced users who are willing to test LOOT for WrinklyNinja. There is however no guarantee that they work correctly, please keep that in mind.

Installation & Uninstallation

LOOT requires Windows 7 or later.

LOOT can be installed either using its automated installer or manually. If you are using the installer, just run it and follow the wizard steps. If installing manually, extract the downloaded archive to a location of your choice (use 7-Zip, WinRAR or WinZip to extract the .7z archive), then download and install the MSVC 2015 x86 redistributable if you don’t already have it installed.

If LOOT was installed using the installer, then use the uninstaller linked to in the Start Menu to uninstall LOOT (the executable is called "unins000.exe"). If LOOT was installed manually:

  1. Delete the files you extracted from the location you chose.
  2. Delete the LOOT folder in your local application data folder, which can be accessed by entering %LOCALAPPDATA% into Windows' File Explorer.

Contributing & Support

LOOT is very much a community project, and contributions from its users are very welcome, whether they be metadata, translations, code or anything else. The best way to contribute is to make changes yourself at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our credits.

If you encounter an issue with LOOT, check the Frequently Asked Questions page in case a solution is available there. Otherwise, general discussion and support takes place in LOOT’s official forum thread, which is linked to on LOOT's homepage.

If you want to submit metadata, the easiest way to do so is to add the metadata to your own LOOT install, then use the Copy Metadata feature to easily get it in a form that you can then edit into a masterlist on GitHub or post in the official forum threads.

Information on dirty plugins is very welcome, but for such information to be useful we require at least the filename and the CRC of the dirty plugin. The CRC may be calculated using Wrye Bash or 7-Zip, with other sources being unverified as correct. In the case of 7-Zip, the “CRC checksum for data” is the one required. Any other information, such as the ITM record and deleted reference counts, is very welcome.


LOOT is developed on GitHub, and a full list of GitHub contributors may be found here.

LOOT's masterlists were largely converted from BOSS's masterlists, and so credit is due to the very large number of sources and people who have contributed to them.

In addition, the following are credited with application-related support:

  • Original icon: jonwd7
  • Translations:
    • Brazilian Portuguese: Kassane
    • Chinese: bluesky404
    • Danish: Freso
    • Finnish: 3ventic
    • French: Kaos
    • German: lpradel
    • Japanese: kuroko137
    • Korean: SteamB23
    • Polish: Łukasz Niemczyk
    • Russian: Tokc.D.K.
    • Spanish: Sharlikran
    • Swedish: Mikael Hiort af Ornäs
  • Beta testing: Too many to list, thank you all!

LOOT is written in C/C++, HTML5, CSS3 and JavaScript, and uses the Boost, Jed, Jed Gettext Parser, libespm, libgit2, libloadorder, Marked, pseudosem, Polymer and yaml-cpp libraries, and the Chromium Embedded Framework. Copyright license information for all these may be found here.


LOOT is distributed under the GNU General Public License v3.0, aside from the documentation, which is distributed under the GNU Free Documentation License v1.3. The full texts of the licenses are included with LOOT in the accompanying GNU GPL v3.txt and GNU FDL v1.3.txt files.

While the GPL license allows anyone to make derivative works of LOOT, the LOOT Team encourages those thinking of doing so to first discuss their reasoning for such an endeavour with the Team. It may be that what the derivative work would do differently is already planned for a future version of LOOT or would be happily integrated into LOOT, thus avoiding any extra effort by others.

LOOT has been specifically designed to prevent it being locked into the LOOT Team's official masterlist repositories. Nevertheless, the LOOT Team appeals to the community to avoid the distribution of unofficial masterlists, as this would only hamper the effort to create one set of stores for load order information. Any issues with a masterlist are best brought to the attention of the LOOT Team so that they may be remedied.

Copyright (C) 2012-2018 WrinklyNinja