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 detecting OpenMW v0.51.0 using its Windows Registry key.
A new dialog for comparing current and sorted load orders. The dialog can be accessed from the Game menu or the toolbar while LOOT is displaying an unapplied sorted load order.
When a masterlist update removes groups that are referenced by user metadata (directly or indirectly), LOOT will now recover those groups as user metadata, appending (Recovered) to their original names. User metadata for installed plugins is also updated to use the new group names, and a general warning message is displayed for each recovered group to inform the user of the change, so that they can update their user metadata as necessary. A separate warning message is displayed after loading metadata if there are any groups with names ending in (Recovered).
Fixed
A crash that could occur when enabling the official plugin cleaning message filter for Fallout 4, Skyrim VR or Nehrim.
When LOOT was run through MO2 for a game install path that included a symlink, plugins installed by MO2 would not appear in LOOT. Note that although such plugins are now displayed in LOOT, it's a known issue that MO2's virtual filesystem does not work with symlinks, so there may be other negative effects when they are used together.
When regenerating state-based general messages in response to state changes (e.g. loading data or sorting), LOOT now only removes the existing messages that are relevant to the state that has changed before generating any new messages. For example, if there is a message about a metadata parsing error, it will no longer be removed when loading plugins.
It was not possible to select the toolbar buttons (e.g. sort plugins, update masterlist) using the keyboard. They can now be selected using the Tab key.
When LOOT was running as a Flatpak application and OpenMW was not installed as a Flatpak application and the host did not have the XDG_CONFIG_HOME and/or XDG_DATA_HOME environment variables defined, LOOT would incorrectly look for OpenMW's default user config and user data directories inside its own Flatpak data directory instead of in the host's home directory. Via libloot.
Changed
The search dialog has been replaced by a toolbar, making it accessible when using only a keyboard. In addition, the find next and find previous buttons now support the desktop's standard keyboard shortcuts for those operations (e.g. F3 and Shift+F3 respectively on Windows, KDE and GNOME).
When multiple versions of OpenMW are installed, LOOT can now detect them all using their Windows Registry keys instead of stopping at the first version it finds.
The dropdown list of plugins displayed by the plugin metadata editor when editing filename values for requirements, incompatibilities or "load after" metadata no longer includes the plugin that is having its metadata edited.
When reading BSAs and BA2s, LOOT now uses asset paths instead of hashes of those paths. This improves the accuracy of asset overlap checks performed during sorting, as the hashes used by BSAs are relatively collision-prone.
This means that BSAs are now required to include folder and file names, and any that don't will be skipped with an error logged for each. All official BSAs and BSAs created using the official tools include folder and file names. Via libloot.
Updated libloot to v0.29.6.
Updated Qt to v6.11.1. This may impact users running LOOT through Wine, as it means that LOOT's installer no longer packages icuuc.dll: instead, it is provided by Wine as of v11.5.