LOOT – Load Order Optimisation

LOOT – Load Order Optimisation

LOOT

A plugin load order optimiser for TES IV: Oblivion, TES V: Skyrim, Fallout 3, Fallout 4 and Fallout: New Vegas.
Posted with permission from the author (wrinklyninja)

This following provides a general overview of load ordering in the games LOOT supports for those who are unfamiliar with the concept. For simplicity, “the game” will be used when the text refers to any of the games that LOOT supports.

Mod plugins for the game are files that end in .esp or .esm.
These files are created by the game’s official editing tools, or by third-party modders’ tools. They contain various data records, which cover almost all aspects of what is in the game – NPCs, items, races, interiors, worlds, quests, etc. – and can either be new or changes to the records added by another plugin.

When the game is run, it loads each installed plugin one by one in a certain load order. The load order is important for two reasons:

If one plugin changes a record added by another plugin, the former must load after the latter. If it doesn’t, the game will crash on launch.
The game can only apply one version of a record, so if multiple plugins contain the same record, the last-loaded plugin’s version overrides all others. This is known as the rule of one, and it holds true for almost all record types. Some overrides can cause problems in-game, and a good load order is one that arranges plugins to avoid such problems.

There are a few hardcoded rules related to load order:

Master plugins always load before non-master plugins. The difference between the two plugin types isn’t really relevant, except that a plugin’s type is decided by a setting inside it, and not by its file extension (even though .esm stands for Elder Scrolls Master).
There is a limit of 255 active plugins that can be loaded by the game. This isn’t strictly a load order thing, but is worth mentioning.
In Fallout 4, Fallout4.esm always loads before all other plugins.
If Update.esm is present for example, it is always loaded. It loads after all other master plugins, unless it has another position explicitly set.

A plugin’s position in the load order is often displayed by mod managers as a hexadecimal number, from 00 to FE (0 to 255 in decimal). The plugin with position 00 loads first, and the plugin with position FE is loaded last. Hexadecimal numbers are used to display the load order positions of plugins because these numbers form the first two digits of the code that the game uses to reference the records that the plugin adds, so knowing the numbers allows modders and mod users to determine from which plugin a record is from.

In Oblivion, Fallout 3, Fallout 4 and Fallout: New Vegas, load order is determined by plugin timestamps, and the plugins you have accessed are listed in %LOCALAPPDATA%\\plugins.txt.
As such, it’s best to use a mod manager to create a backup of your load order. Many modding utilities generally use %LOCALAPPDATA%\\loadorder.txt to store the load order of all plugins. This makes backing up your load order as easy as making copies of those two files.

Downloads

LOOT can be downloaded from its website. The latest stable version and snapshot build will be posted here on the FO4 Nexus for convenience, but are also available in the official Github Latest Release location as well.

Snapshot Builds

Snapshot build archives are made available on Dropbox fairly regularly. If you can’t or don’t want to build LOOT yourself, but still want to test a more recent build than the latest release or pre-release, you can check to see if there is such a build available.
The archives are named in the following manner:
LOOT –g.7zFor example LOOT v0.7.0-alpha-2-10-gf6d7e80.7z was built using the revision with shortened commit ID f6d7e80, which is10 revisions after the revision tagged v0.7.0-alpha-2.

Introduction

LOOT is a plugin load order optimiser for TES IV: Oblivion, TES V: Skyrim, Fallout 3, Fallout 4 and Fallout: New Vegas. 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 an overview.

Installation & Uninstallation
LOOT does not support Windows XP or earlier.

LOOT can be installed either using its automated installer or manually. To install LOOT manually, extract the downloaded archive to a location of your choice.If LOOT was installed using the installer, then use the uninstaller linked to in the Start Menu to uninstall LOOT. If LOOT was installed manually:

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

Using LOOT

Initialisation

When LOOT is run, it will attempt to detect which of the supported games are installed. If a default game has been set, LOOT will run for it, otherwise it will run for the same game as it last ran for. If the relevant game cannot be detected, or if there is no record of the last game LOOT ran for, it will run for the first detected game.

LOOT can also be launched with the –game= command line parameter to set the game to run for. If the supplied game folder name is valid, the default and last game values are ignored. The default folder names are Oblivion, Skyrim, Fallout 3, Fallout 4, and FalloutNV.

If LOOT cannot detect any supported game installs, it will immediately open the Settings dialog. There you can edit LOOT’s settings to provide a path to a supported game, after which you can select it from the game menu.

Once a game has been set, LOOT will scan its plugins and load the game’s masterlist, if one is present. The plugins and any metadata they have are then listed in their current load order.

If LOOT detects that it is the first time you have run that version of LOOT, it will display a First-Time Tips dialog, which provides some information about the user interface that may not be immediately obvious.

The Header Bar

LOOT’s header bar, divided into sidebar and panel areas. The sidebar area contains the plugins and filters tabs. From left to right in the panel area are the Jump To General Information button, the game menu, and the sorting, masterlist update, search and main menu buttons. The game menu, masterlist update button and sorting button have been disabled, as a plugin metadata editor is open.

The header bar provides access to LOOT’s main features. Most of these features get disabled while there is at least one plugin editor open, so if you’re trying to use an option that is faded out, first close any editors you have open.

Game Menu

LOOT’s active game can be changed by clicking on it in the header bar, and selecting another game from the menu that is displayed. Games that have no install detected are disabled have their menu items disabled.

Masterlist Update & Sorting

The masterlist update process updates the active game’s masterlist to the latest revision at the location given by the game’s masterlist repository settings. If the latest revision contains errors, LOOT will roll back to the latest revision that works.

By default, sorting first updates the masterlist. LOOT then calculates a load order for your plugins, using their internal data and any metadata they may have. If a cyclic interaction is detected (eg. A depends on B depends on A), then sorting will fail.

Once LOOT has calculated a load order, the plugin cards are sorted into that order. The masterlist update and sorting buttons are replaced with APPLY and CANCEL buttons, which apply and discard the calculated load order respectively. Changing games is disabled until the calculated load order is applied or discarded.

LOOT is able to sort plugins ghosted by Wrye Bash, and can extract Bash Tags and version numbers from plugin descriptions. Provided that they have the Filter Bash Tag present in their description, LOOT can recognise filter patches and so avoid displaying unnecessary error messages for any of their masters that may be missing.

Any errors encountered during sorting or masterlist update will be displayed on the General Information card.

Search

The search toolbar is displayed by clicking the search icon in the header bar, or using the Ctrl-F keyboard shortcut. It may be closed using the close button at the right of the toolbar.

Searching is performed as-you-type, or when the Enter key is pressed. All content visible on the front of plugin cards is searched, so the results may be affected by any filters you have active.

The plugin card list will be scrolled to the first card that contains a match. Matches may be scrolled between using the up and down chevron buttons, and the current match and the number of matches are displayed between them and the search input.

Main Menu

A few items in the main menu are not self-explanatory:

Redate Plugins is provided so that Skyrim modders may set the load order for the Creation Kit. It is only enabled for Skyrim, and changes the timestamps of the plugins in its Data folder to match their current load order. A side effect of changing the timestamps is that any Steam Workshop mods installed will be re-downloaded.
Copy Load Order copies the displayed list of plugins and the decimal and hexadecimal indices of active plugins.
Copy Content copies the data displayed in LOOT’s cards as YAML-formatted text.
Refresh Content re-scans the installed plugins’ headers and regenerates the content LOOT displays. This can be useful if you have made changes to your installed plugins while LOOT was open. Refreshing content will also discard any CRCs that were previously calculated, as they may have changed.

Plugin Cards & Sidebar Items

Examples of plugin cards.

Each plugin is displayed on its own card, which displays all the information LOOT has for that plugin, and provides access to plugin-specific functionality, including its metadata editor. Each plugin also has an item in the sidebar’s PLUGINS tab. The sidebar item contains the plugin’s name and icons for plugins that load BSAs or have user metadata. Clicking on a plugin’s sidebar item will jump to its card, while double-clicking will jump to its card and open its metadata editor.

The plugin card’s header holds the following information, some of which is only displayed if applicable:

The Active Plugin icon.
The plugin name.
The plugin’s version number, extracted from its description field.
The plugin’s CRC, which can be used to uniquely identify it. CRCs are only displayed after they have been calculated during conflict filtering or sorting.
The Master File icon.
The Empty Plugin icon.
The Loads BSA icon.
The Has User Metadata icon.
The plugin menu button, which provides access to a few plugin-specific features, including a conflict filter and access to its metadata editor. These are explained in later sections.

Bash Tag suggestions and messages are displayed below the plugin card’s header.

If LOOT suggests any Bash Tags to be added, they will be displayed in green text, while any Bash Tags to be removed will be displayed in red text. For completeness, the list of Bash Tags to add will include any Bash Tags that are already specified in the plugin’s description field. Users generally don’t need to do anything with this information, as if they’re using Wrye Bash it will automatically apply LOOT’s suggestions, and if they’re not using Wrye Bash then this information doesn’t apply.

LOOT’s plugin messages are a valuable resource, acting as a means of providing users with information that they might otherwise not obtain. It is important for a stable, healthy game that you act on any messages that require action. If you think a message suggests an unnecessary action, report it to an official LOOT thread. If you encounter a message that is non-conditional, ie. it suggests an action but is still displayed on subsequent runs of LOOT after the action has been carried out, also report it to an official LOOT thread, so that it can be made conditional.

Filters

Clicking the FILTERS tab in the sidebar will replace the sidebar’s plugin list with a list of filter toggles that can be applied to hide various combinations of plugins and other content. The available filter toggles are:

Hide version numbers: Hides the version numbers displayed in blue next to those plugins that provide them.
Hide CRCs: Hides the CRCs displayed in orange next to those plugins that provide them.
Hide Bash Tags: Hides all Bash Tag suggestions.
Hide notes: Hides all plugin messages that have the Note: prefix, or the equivalent text for the language selected in LOOT’s settings.
Hide ‘Do not clean’ messages: Hides all messages that contain the text Do not clean, or the equivalent text for the language selected in LOOT’s settings.
Hide all plugin messages: Hides all plugin messages.
Hide inactive plugins: Hides all plugins that are inactive.
Hide messageless plugins: Hides all plugins that have no visible messages.

The filter toggles have their states saved on quitting LOOT, and they are restored when LOOT is next launched. There are also two other filters:

A content filter, located beneath the filter toggles in the FILTERS sidebar tab. This hides any plugins that don’t have the filter input value present in any of the following:

Filename
Version
CRC value
Bash Tag suggestions
Messages

A conflict filter that can be accessed through each plugin’s menu. This filters the plugin cards displayed so that only plugins which conflict with this plugin will be visible. If this plugin loads a BSA, other plugins that load BSAs which may contain conflicting resources are also displayed.

Only one plugin’s conflict filter can be active at any one time, so activating a second conflict filter will deactivate the first. The plugin for which the filter is currently active has its card highlighted. Sorting with a conflict filter active will first deactivate it.

Editing Plugin Metadata

A metadata editor panel.

LOOT uses metadata to supply plugins with messages and Bash Tag suggestions, and to help it sort plugins that it can’t otherwise sort correctly. Users can add to their plugins’ metadata through each plugin’s metadata editor panel, and plugins with user metadata are indicated with a Has User Metadata icon.

A plugin’s editor panel is accessed by clicking the Edit Metadata item in the plugin’s menu. Multiple plugins can have their editor panels open at once. While at least one editor panel is open, the plugin sidebar also displays any non-zero plugin priorities, to aid setting new priority values.

The editor’s header bar is similar to the header on the front of the plugin card, minus the Has User Metadata icon, and with the addition of Apply and Cancel icon buttons and a row of tabs. The MAIN tab contains the following inputs:

The Enable Edits toggle must be on for LOOT to use any user-added metadata, otherwise it will be ignored.
The Global Priority toggle controls how LOOT compares plugin priorities. If off, the plugin’s priority will only be compared against plugins that conflict, and empty plugins. If on, the plugin’s priority will be compared against all plugins.
The Priority Value input sets the plugin’s priority value, which is used to modify plugin position relative to others. Plugins with higher priority values load after plugins with lower priority values. Plugins have a default priority of 0.

The other tabs contain metadata tables, which are detailed below. New rows can be added, and existing user-added rows can be removed, though rows containing metadata from the masterlist cannot. The LOAD AFTER, REQUIREMENTS and INCOMPATIBILITIES tables can have rows added by dragging and dropping plugins from the sidebar into the table area.

LOOT’s settings dialog.

LOOT’s settings may be accessed by clicking Settings button in LOOT’s menu bar. The settings are detailed in the table below.

LOOT’s game-specific settings can be customised in the games table. New game profiles can be added, making it easy to use LOOT across multiple copies of a game, including total conversion mods. LOOT ships with settings for the Nehrim – At Fate’s Edge total conversion mod as an example. Game profiles can also be deleted, though the active game cannot have its profile deleted, and LOOT will recreate the profiles for the four base games it supports (Oblivion, Skyrim, Fallout 3, Fallout 4 and Fallout: New Vegas) when it is next run.

Themes

LOOT’s user interface has experimental support for the use of alternative and custom CSS themes. To use a theme, place its CSS file into the resources/report/css folder inside LOOT’s installation folder, and rename the file to theme.css. LOOT will then load this file when it launches. A dark user interface theme is provided with LOOT: to use it, rename dark-theme.css in the resources/report/css folder to theme.css.

Theme support is experimental because future updates to LOOT’s user interface may break existing CSS selectors.

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 wiki page in case a solution is available there. If not, please direct all issues to the official Bug Tracker.

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. In addition to the CRC, the number of records removed (the ITM count) and/or undeleted (the UDR count) are also welcome.

Credits

LOOT is developed by a team on GitHub, with contributions from users. A full list of GitHub contributors may be found here. A list of team members may be viewed on the project wiki. Unless otherwise noted, team members can be contacted on the Bethesda Softworks Forums or on The Nexus Forums via the private messaging system.

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
Finnish: 3ventic
French: Kaos
German: lpradel
Korean: SteamB23
Polish: Łukasz Niemczyk
Russian: Tokc.D.K.
Spanish: Sharlikran
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, Polymer RequireJS and yaml-cpp libraries, and the Chromium Embedded Framework. Copyright license information for all these may be found here.

License

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.

GNU Free Documentation License Version 1.3 Notice:

Copyright (C) 2012—2015 WrinklyNinja
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the file named “GNU FDL v1.3.txt”.

Version History

Only program history is recorded here. A full history of masterlist changes may be viewed by browsing the GitHub repository Commits Page.

0.8.0 – 22 July 2015
Fixed Cannot read property ‘push’ of undefined errors when sorting.
Fixed many miscellaneous bugs, including initialisation crashes and incorrect metadata input/output handling.
Fixed metadata editors not clearing unsaved edits when editing is cancelled.
Fixed LOOT silently discarding some non-unique metadata: an error message will now be displayed when loading or attempting to apply such metadata.
Fixed userlist parsing errors being saved as general messages in the userlist.
Fixed and improved LOOT’s version comparison behaviour for a wide variety of version string formats. This involved removing LOOT’s usage of the Alphanum code library.
Improved detail of metadata syntax error messages.
Improved plugin loading performance for computers with weaker multithreading capabilities (eg. non-hyperthreaded dual-core or single-core CPUs).
LOOT no longer displays validity warnings for inactive plugins.
LOOT now displays a more user-friendly error when a syntax error is encountered in an updated masterlist.
Added support for loading custom user interface themes, and added a dark theme.
Metadata syntax support changes, see the metadata syntax document for details.
LOOT’s installer now uses Inno Setup instead of NSIS.
LOOT’s installer now uninstalls previous versions of LOOT silently, preserving user data, instead of displaying the uninstaller UI.
Updated German and Russian translations.
Updated libgit2 to v0.23.0.

0.7.1 – 22 June 2015
Fixed LOOT UI opening in default browser on launch.
Fixed No existing load order position errors when sorting.
Fixed message filters being ignored by plugin cards after navigating the list.
Fixed output of Bash Tag removal suggestions in userlists and the API’s `loot_write_minimal_list()`.
Fixed display of masterlist revisions where they were wrongly interpreted as numbers.
LOOT now uses versioned masterlists, so that new features can be used without breaking LOOT for users who haven’t yet updated.
Moved content filter into Filters sidebar tab. The Ctrl-F keyboard shortcut no longer focusses the content filter.
Checkbox-toggled filters now have their last state restored on launch.
Darkened background behind cards to increase contrast.
Added content search, accessible from an icon button in the header bar, and using the Ctrl-F keyboard shortcut.
Added Copy Load Order feature to main menu.
Updated French translation.

0.7.0 – 20 May 2015Fixes
The Settings.yaml included with the installer was very old.
Inactive incompatibilities were displayed as error messages. They are now displayed as warnings.
Masterlist entries that matched the same plugin were not being merged. Now one exact match and any number of regex matches will be merged.
Masterlist updating failed when a fast-forward merge was not possible (eg. when remote has been rebased, or a different repository is used). Such cases are now handled by deleting the local repository and re-cloning the remote.
Masterlist updating failed when the path to LOOT’s folder included a junction link.
Masterlists would not ‘update’ to older revisions. This can be useful for testing, so now they can do so.
Crashes when trying to read corrupt plugins and after masterlist update completion.
LOOT would crash when trying to detect a game installed to a location in which the user does not have read permissions, now such games are treated as not being installed.
Plugins with non-ASCII description text would cause codecvt to wstring errors.
LOOT would accept any file with a .esp or .esm extension as a plugin. It now checks more thoroughly, by attempting to parse such files’ headers.
LOOT would only detect Skyrim plugins as loading BSAs. Plugins for the other games that also load BSAs are now correctly detected as such.
Depending on the plugins involved, sorting could produce a different load order every time it was run. Sorting now produces unchanging load orders, using existing load order position where there is no reason to move a plugin.

Additions
Danish and Korean translations.
If LOOT can’t detect any installed games, it now launches to the settings dialog, where the game settings can be edited to allow a game to be detected.
A Copy Content item in the main menu, to copy the plugin list and all information it contains to the clipboard as YAML-formatted text.
A Refresh Content item in the main menu, which re-scans plugin headers and updates LOOT’s content.
LOOT is now built with High DPI display support.
Masterlist updates can now be performed independently of sorting.
A First-Time Tips dialog will be displayed on the first run of any particular version of LOOT.
Attempting to close LOOT with an unapplied sorted load order or an open plugin editor will trigger a confirmation dialog.
Support for GitHub Flavored Markdown in messages, minus features specific to the GitHub site, such as @mentions and emoji.
Support for message content substitution metadata syntax in the masterlist.
Display of LOOT’s build revision has been added to the About dialog.
Plugin location metadata can now be added through the user interface.
A content filter, which hides plugins that don’t have the filter text present in their filenames, versions, CRCs, Bash Tags or messages.

Changes
New single-window HTML5-based interface and a new icon, based on Google’s Material Design.
LOOT now parses the masterlist and plugin headers on startup, and the resulting content is displayed with the plugins in their current load order.
Each plugin now has its own editor, and multiple editors can be opened at once.
Drag ‘n’ drop of plugins from the sidebar into metadata editor tables no longer requires the conflicts filter to be enabled.
CRCs are calculated during conflict filtering or sorting, so are not displayed until either process has been performed.
The View Debug Log menu item has been replaced with a Open Debug Log Location menu item to make it easier to share the file itself.
Debug logging control has been simplified to enable/disable, replacing the Debug Verbosity setting with an Enable Debug Logging toggle.
Changes to game settings now take immediate effect.
Masterlist updating now exits earlier if the masterlist is already up-to-date.
Masterlist revisions are now displayed using the shortest unique substring that is at least 7 characters long.
Making edits to plugin metadata before applying a calculated load order no longer causes LOOT to recalculate the load order. Instead, the displayed load order is applied, and the metadata edits will be applied the next time sorting is performed.
All references to UDRs have been replaced by the more technically-correct Deleted References term.
The Hide inactive plugin messages filter has been replaced by a Hide inactive plugins filter.
Copied metadata is now wrapped in BBCode [ spoiler ][ code ]… [ /code ][ /spoiler ] tags for easier pasting into forum posts.
The Summary and General Messages cards have been combined into a General Information card.
Sorting performance improvements.
Updated Boost (1.58.0), libgit2 (0.22.2) and libloadorder dependencies.

Removals
Messages with multiple language strings can no longer be created through the user interface. User-added multiple-language messages will be converted to single-language strings if their plugin’s editor is opened then closed using the OK button.
The Copy Name menu item has been removed, as plugin names can now be selected and copied using ctrl+c.
As LOOT no longer generates reports, it doesn’t save them either.

API
Fixed some documentation errors.
Fixed the API creating a LOOT folder when being initialised.
Fixed false successes for loot_create_db() when invalid paths were supplied.
Fixed loot_load_lists() ignoring userlist paths, and accepting invalid paths.
Fixed loot_eval_lists() accepting invalid language codes.
Fixed loot_get_dirty_info() never outputting the loot_needs_cleaning_no code.
Fixed loot_write_minimal_list() causing a crash when passed an invalid output path.
Added load order sorting and application functions.
Added masterlist update and revision checking functions.
Added support for native Linux builds.
Added unit testing of API functions to help ensure correctness and consistency of functionality.
Added loot_get_build_id(), which outputs the shortened revision ID that the API was built from.

0.6.1 – 22 December 2014
Fixed: Default Nehrim registry entry path.
Fixed: Messages in the wrong language being selected.
Fixed: LOOT windows opening off-screen if the screen area had been changed since last run.
Fixed: Read-only .git folders preventing repository deletion.
Fixed: Unnecessary plugins in cyclic dependency error messages.
Fixed: Bash Tag suggestions displaying incorrectly.
Fixed: The current game can no longer be deleted from the settings window.
Fixed: Plugin metadata being lost when the settings window was exited with the “OK” button, leading to possible condition evaluation issues.
Fixed: A blank report bug when running on systems which don’t have Internet Explorer 11 installed.
Fixed: Reports appearing empty of all content when no global messages are to be displayed.
Changed: Updated Boost (1.57.0), libgit2 (0.21.3), wxWidgets (3.0.2) and libloadorder (6.0.3) dependencies. This includes a critical security vulnerability fix in libgit2.
Changed: The game menu is now updated when the settings window is exited with the “OK” button.
Changed: Updated Russian translation.
Changed: Updated Brazilian Portuguese translation.
Added: German translation.
Added: The Large Address Aware flag to the LOOT executable.

0.6.0 – 05 July 2014
Fixes
The uninstaller not removing the Git repositories used to update the masterlists.
Miscellaneous crashes due to uncaught exceptions.
Plugin priorities are now temporarily “inherited” during sorting so that a plugin with a low priority that is made via metadata to load after a plugin with a high priority doesn’t cause other plugins with lower priorities to be positioned incorrectly.
The default language is now correctly set to English.
Defaults for the online masterlist repository used for Nehrim.
Endless sorting loop that occurred if some user metadata was disabled.

Additions
Display of masterlist revision date in reports.
Report filter for inactive plugin messages.
The number of dirty plugins, active plugins and plugins in total to the report summary.
A find dialog to the report viewer, initiated using the Ctrl-F keyboard shortcut.
LOOT’s windows now remember their last position and size.
Command line parameter for selecting the game LOOT should run for.
Finnish translation.

Removals
Support for Windows XP.
Support for loading BOSS masterlists using the API. This was a leftover from when LOOT was BOSSv3 and backwards compatibility was an issue.
The ability to open reports in an external browser. This was necessitated by the changes to report generation.
The MSVC 2013 redistributable requirement.
The “None Specified” language option is no longer available: English is the new default.

Changes
Unified and improved the metadata editors launched during and outside of sorting.
The metadata editor now resizes more appropriately.
The mid-sorting instance hides the requirement, incompatibility, Bash Tags, dirty info and message lists.
Both instances now have a conflict filter, priority display in their plugin list and drag ‘n’ drop from the plugin list into whatever metadata lists are visible.
The mid-sorting instance also hides the load after entry edit button, and the button to add new entries (so drag ‘n’ drop is the only available method of adding entries).
The metadata editor now displays plugins with user edits using a tick beside their name, rather than bolding their name text.
Plugins that have been edited in the current instance have their list entry text bolded.
Checkboxes have been added to set whether or not a priority value is “global”. The UI also now displays the priority value used in comparisons (ie. with the millions and higher digits omitted).
A right-click menu command for clearing all user-added metadata for all plugins has been added to the metadata editor.
Missing master/requirement and incompatibility errors are downgraded to warnings if the plugin in question is inactive.
Masterlist update errors have been made more user-friendly.
If an error is encountered during masterlist update, LOOT will now silently delete the repository folder and attempt the update again. If it fails again, it will then report an error.
Masterlist update now handles repository interaction a lot more like Git itself does, so should be less error-prone.
Cyclic dependency error messages now detail the full cycle.
LOOT’s report now uses a static HTML file and generates a javascript file that is dynamically loaded to contain the report data. This removes the PugiXML build dependency.
Debug log message priorities adjusted so that medium verbosity includes more useful data.
Updated dependencies: libgit2 (v0.21.0), wxWidgets (v3.0.1), libloadorder (latest), libespm (latest).

0.5.0 – 31 March 2014
Initial release.