Setting the right load order for your Starfield, TES III: Morrowind, TES IV: Oblivion, Nehrim: At Fate's Edge, TES V: Skyrim, TES V: Skyrim Special Edition, TES V: Skyrim VR, Fallout 3, Fallout: New Vegas, Fallout 4 and Fallout 4 VR 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.
While sorting, LOOT checks for load order errors (such as incompatibilities and missing requirements) and notifies you of any issues that it detects. It also provides thousands of plugin-specific messages, such as usage notes and bug warnings, to help keep your game healthy.
Support for Starfield v1.16.236.0's new SFBGS00D.esm and SFBGS047.esm plugins and the Terran Armada DLC's new SFBGS050.esm plugin, which have hardcoded load order positions.
Support for adding multiple plugins to the same group at once, using a new multi-select list in the Groups Editor.
Support for detecting OpenMW v0.50.0 using its Windows Registry key.
Support for building LOOT using a prebuilt copy of minizip-ng without its minizip compatibility layer. minizip and minizip-ng with its minizip compatibility layer were already supported.
A debug-level log message is now written when a plugin is successfully loaded. Via libloot.
Fixed
Warnings about ambiguous load orders when Starfield blueprint plugins or BlueprintShips plugins are installed (aside from BlueprintShips-Starfield.esm, which was already handled as a special case). The Terran Armada DLC and "Trackers Alliance: The Complete Bounty Series" Creation include such plugins.
Starfield BlueprintShips plugins are now correctly displayed as active when there is an active plugin that matches the BlueprintShips plugin's suffix. For example, if a plugin named example.esp is active, then BlueprintShips-example.esm is also active if the latter is installed.
An error that occurred when saving settings when there is no current game (e.g. because LOOT could not detect any installed games).
When switching theme from "default (dark)" or "default (light)" to "default", the colour scheme override was not removed, which led to the wrong colours being used until LOOT was restarted.
The general information card's hidden messages icon colour was not updated on changing between light-coloured and dark-coloured themes until LOOT was restarted.
Depending on the Qt style used, switching themes could lead to the general information and plugin cards changing size, causing their layout to be wrong until LOOT was restarted.
Switching themes did not reliably update the styling of the last card that the user moused over before switching themes.
After deleting a game in the Settings dialog, the displayed game settings would be for the game below the selected game, until another game was selected.
LOOT leaked memory whenever a plugin card's content changed in a way that could affect its height (e.g. by adding a message to the plugin).
When detecting an installed copy of a game that has its different languages installed side-by-side (e.g. Fallout 3 from the Epic Games Store), LOOT attempts to select the same language as the preferred system language(s), but on Linux it was often unable to determine what the preferred languages were.
On Linux the LOOT window icon was displayed with a bright green border.
Building LOOT using CMake's Ninja generator on Windows.
Various compilation, linking and packaging errors encountered when cross-compiling LOOT for Windows using mingw-w64.
Changed
When LOOT sets the load order, it now writes the timestamps of Starfield blueprint masters to match their load order, in addition to including them in plugins.txt. This is so that when Starfield launches and removes the blueprint masters from plugins.txt, it will still use the same load order for those plugins for subsequent launches.
The "Copy Load Order" Game menu action is no longer disabled while there is an unapplied sorted load order. In that state, the action copies the unapplied load order, rather than the game's current saved load order.
Qt's fusion style is now the default on Windows 10 and Windows 11, instead of the windowsvista style. Unlike windowsvista, fusion allows LOOT's default theme to be used in dark or light variants, and those variants can be used following the system colour scheme or independent of it.
Improved the contrast of some text and border colours in the dark colour scheme variant of the default theme.
Windows 11 users can now override the Qt style that LOOT uses by default using Qt's -style CLI argument.
The default behaviour on Windows with a dark colour scheme when using the windows11 or fusion Qt styles is to use the system's accent colour as the hyperlink text colour, but depending on the accent colour this can make hyperlinks unreadable due to low contrast. LOOT now overrides the hyperlink text colour to a shade of blue that has good contrast with the dark colour scheme's background colour.
The default behaviour on Windows with a dark colour scheme when using the fusion Qt style is to use the system's accent colour as the background colour of checkboxes, but depending on the accent colour this can make it difficult to see if a checkbox is ticked or not. LOOT now overrides the checkbox styling to use a neutral background colour.
Unexpected errors in the Groups Editor that could potentially crash LOOT will now display an error message dialog box instead.
Updated LOOT's list of known official plugins for Skyrim SE, Starfield and Fallout 4.
LOOT now logs a warning when it tries to retrieve data for a plugin in the load order that hasn't been loaded.
LOOT now supports v0.29 of the metadata syntax.
User-visible copyright notices now use "The LOOT Contributors" as the copyright holder, and the docs author and executable publisher is now "The LOOT Team".
Updated Boost to v1.90.0.
Updated fmt to v12.1.0.
Updated libloot to v0.29.3.
Updated libtbb used by the Flatpak build to v2022.3.0.