Loot Fallout 4 Plugin.txt Set to Read Only

LOOT

Contents

1. Introduction
2. Installation & Uninstallation
3. Using Loot
   1. Initialisation
   2. The Header Bar
   3. Plugin Cards & Sidebar Items
   4. Filters
   5. Editing Plugin Metadata
   6. Editing Settings
4. Contributing & Back up
5. Credits
6. License
7. Version History

Introduction

Boodle is a plugin load order optimiser for TES IV: Oblivion, TES V: Skyrim, Fallout 3, Fallout: New Vegas and Fallout iv. It is designed to assistance modernistic users in fugitive detrimental conflicts, by automatically computing a load social club that satisfies all plugin dependencies and maximises each plugin'south touch on the user'southward 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, problems warnings and Bash Tag suggestions for Wrye Bash.

While LOOT is able to calculate correct load lodge positions for the vast majority of plugins using simply their content, it cannot do so for all plugins. Equally such, Boodle provides a mechanism for supplying additional plugin metadata and then 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.

Boodle is intended to make using mods easier, and mod users should still possess a working cognition of mod load ordering. See Introduction To Load Orders for an overview.

Installation & Uninstallation

LOOT does non back up Windows XP or earlier.

LOOT can be installed either using its automatic installer or manually. To install LOOT manually, extract the downloaded annal to a location of your choice.

If LOOT was installed using the installer, then use the uninstaller linked to in the Commencement Menu to uninstall Loot. 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 inbound %LOCALAPPDATA% into Windows' File Explorer.

Using LOOT

Initialisation

When LOOT is run, information technology volition 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 tape of the last game LOOT ran for, it will run for the first detected game.

Boodle can besides be launched with the --game=<game folder name> command line parameter to set the game to run for. If the supplied game binder proper name is valid, the default and last game values are ignored. The default folder names are Oblivion, Skyrim, Fallout3, FalloutNV and Fallout4.

If Loot cannot detect any supported game installs, it volition immediately open up the Settings dialog. There you can edit Boodle's settings to provide a path to a supported game, after which you can select information technology from the game card.

Once a game has been fix, LOOT will browse its plugins and load the game's masterlist, if i is present. The plugins and whatsoever metadata they have are and then listed in their electric current load order.

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

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 Spring To Full general Information push, the game menu, and the sorting, masterlist update, search and principal carte du jour buttons. The game card, masterlist update push button and sorting button have been disabled, as the metadata editor is open.

The header bar provides access to Boodle'southward master features. Almost of these features become disabled while the metadata editor is open, and then if you're trying to use an pick that is faded out, first close the editor.

Game Menu

LOOT'south active game tin be inverse by clicking on information technology in the header bar, and selecting another game from the menu that is displayed. Games that have no install detected have their bill of fare items disabled.

Masterlist Update & Sorting

The masterlist update process updates the agile game's masterlist to the latest revision at the location given past the game's masterlist repository settings. If the latest revision contains errors, Loot will curlicue back to the latest revision that works.

By default, sorting first updates the masterlist. Boodle then calculates a load gild for your plugins, using their internal information and whatsoever metadata they may take. If a cyclic interaction is detected (eg. A depends on B depends on A), then sorting will fail.

One time Boodle has calculated a load order, information technology is compared with the current load order. If the current and calculated load orders are identical, LOOT will inform the user that no changes were made via a pop-up 'toast' notification. If the calculated load social club contains changes, the plugin cards are sorted into that order and the masterlist update and sorting buttons are replaced with Utilise and Cancel buttons, which apply and discard the calculated load guild respectively. Changing games is disabled until the calculated load guild is applied or discarded.

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

Any errors encountered during sorting or masterlist update will exist 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 exist closed using the close push button at the right of the toolbar.

Searching is performed as-you-blazon, or when the Enter key is pressed. All content visible on the front of plugin cards is searched, and then the results may be affected by whatever filters you have agile.

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

Master Menu

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

• Redate Plugins is provided so that Skyrim modders may gear up the load order for the Creation Kit. Information technology is only enabled for Skyrim, and changes the timestamps of the plugins in its Data folder to match their current load social club. A side result of changing the timestamps is that any Steam Workshop mods installed volition be re-downloaded.
• Re-create Load Social club copies the displayed list of plugins and the decimal and hexadecimal indices of active plugins.
• Re-create Content copies the information 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 lot have made changes to your installed plugins while Boodle was open. Refreshing content will also discard whatever CRCs that were previously calculated, as they may accept changed.

Plugin Cards & Sidebar Items

Examples of plugin cards.

Each plugin is displayed on its own menu, which displays all the information LOOT has for that plugin, and provides admission to plugin-specific functionality, including editing its metadata. Each plugin also has an particular in the sidebar's Plugins tab. The sidebar particular contains the plugin's name and icons for plugins that load archives or have user metadata. Clicking on a plugin'southward sidebar item volition leap to its card, while double-clicking will jump to its card and open it in the metadata editor.

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

1. The Agile Plugin icon.
2. The plugin name.
3. The plugin's version number, extracted from its clarification field.
4. The plugin's CRC, which tin can be used to uniquely place it. CRCs are just displayed after they take been calculated during conflict filtering or sorting, except the the CRC of the game's main chief file, which is never displayed.
5. The Chief File icon.
6. The Empty Plugin icon.
7. The Loads Archive icon.
8. The Has User Metadata icon.
9. The plugin menu button, which provides access to a few plugin-specific features, including a conflict filter and admission to it in the metadata editor. These are explained in later sections.

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

If Boodle suggests any Fustigate Tags to be added, they will be displayed in light-green text, while whatever Bash Tags to exist removed volition be displayed in scarlet text. For completeness, the list of Bash Tags to add will include whatsoever Bash Tags that are already specified in the plugin's description field. Users by and large don't demand to practice annihilation with this information, as if they're using Wrye Fustigate information technology will automatically apply Boodle's suggestions, and if they're non using Wrye Bash then this data doesn't utilise.

LOOT's plugin letters are a valuable resource, acting equally a means of providing users with information that they might otherwise not obtain. It is important for a stable, good for you game that y'all human activity on any messages that require action. If yous think a bulletin suggests an unnecessary activeness, written report information technology to an official Boodle thread. If y'all run across a message that is non-conditional, ie. it suggests an action but is nevertheless displayed on subsequent runs of LOOT later on the action has been carried out, also study 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 tin can be applied to hide diverse combinations of plugins and other content. The available filter toggles are:

• Hibernate version numbers: Hides the version numbers displayed in blueish side by side 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 Fustigate Tag suggestions.
• Hide notes: Hides all plugin messages that have the Notation: prefix, or the equivalent text for the linguistic communication selected in Boodle'due south settings.
• Hide 'Practice not clean' messages: Hides all letters that contain the text Exercise not clean, or the equivalent text for the language selected in LOOT's settings.
• Hide all plugin messages: Hides all plugin messages.
• Hibernate inactive plugins: Hides all plugins that are inactive.
• Hide messageless plugins: Hides all plugins that have no visible letters.

The filter toggles have their states saved on quitting LOOT, and they are restored when Boodle is next launched. In that location 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 text on their cards.
• A conflict filter that tin can be accessed through each plugin card'due south card. This filters the plugin cards displayed so that only plugins which conflict with this plugin volition be visible. If this plugin loads an archive, other plugins that load athenaeum which may contain conflicting resources are also displayed. Only one plugin's conflict filter can exist agile at whatsoever 1 time, so activating a 2d conflict filter volition conciliate the showtime. The plugin for which the filter is currently active has its menu highlighted. Sorting with a disharmonize filter active will first deactivate it.

Editing Plugin Metadata

The metadata editor console.

LOOT uses metadata to supply plugins with messages and Fustigate Tag suggestions, and to assistance information technology sort plugins that it tin't otherwise sort correctly. Users can add to their plugins' metadata through the metadata editor panel, and plugins with user metadata are indicated with a Has User Metadata icon.

The editor panel is accessed by clicking the Edit Metadata item in a plugin'southward carte, or past double-clicking a plugin name in the sidebar. Only one plugin'south metadata can be edited at a fourth dimension. While the editor panel is open, the plugin sidebar also displays any non-null plugin priorities, to aid setting new priority values. The editor tin exist resized by grabbing the top of the editor's header and dragging it upwardly or downwards.

The editor'southward header displays the name of the plugin being edited, Save Metadata and Cancel buttons, and a row of tabs. The Master tab's page contains the following inputs:

• The Enable Edits toggle must be on for Loot to use any user-added metadata, otherwise information technology volition be ignored.
• The Global Priority toggle controls how LOOT compares plugin priorities. If off, the plugin's priority volition only exist compared confronting 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'southward priority value, which is used to modify plugin position relative to others. Plugins with college priority values load later on plugins with lower priority values. Plugins have a default priority of 0.

The other tab pages contain metadata tables, which are detailed beneath. New rows can exist added, and existing user-added rows can be removed, though rows containing metadata from the masterlist cannot. The Load Afterward, Requirements and Incompatibilities tables can have rows added past dragging and dropping plugins from the sidebar into the table surface area.

Table	Description
Load After	This is a listing of plugins which, if present, the current plugin must load afterward, just which are not required. This metadata can be used for resolving specific compatibility bug. Each entry has iii fields: The filename is the path, relative to the game's Data binder, of the file to exist checked for. This field is required. The display name is optional, and if specified will exist used instead of the filename in any error letters that are displayed if a problem is encountered relating to the file. The status is the optional condition cord that is used to determine if the file should be checked for. If left blank, the file will e'er be checked for. Condition strings are a relatively advanced part of Boodle's functionality, and their syntax is covered in the Metadata Syntax documentation.
Requirements	This is a listing of files that are required by the current plugin for it to function correctly. The electric current plugin will be loaded after whatsoever plugins listed. Loot will also display an mistake message if any of the listed files are missing. Any file, not just plugins, can be listed here, and each entry has the aforementioned iii fields as for the load after table. Note that listing a plugin's masters as requirements is unnecessary, as Boodle already checks them.
Incompatibilities	This is a list of files that are incompatible with the plugin. Boodle will display an error message if any of the listed files are found. Any file, not just plugins, tin can be listed hither, and each entry has the same three fields as for the load after tabular array.
Letters	A list of messages that are to be displayed for the plugin in LOOT's report. These have no bearing on a plugin's position in the load guild. Each message has four fields: The type is fairly self-explanatory, and is used to provide messages of varying severity with appropriate emphasis in Boodle's report. The content is the actual message text. The status is, like for the corresponding file field, used to determine if the message should be displayed. If left blank, the message is displayed. The language is the language Boodle runs in that the message will be displayed for. This field has no outcome for user-added messages, as they cannot contain multiple localisations, and LOOT volition always brandish letters that have only ane localisation, even if it doesn't lucifer the current linguistic communication. If a message'south condition determines that it should non be displayed, then it volition non be displayed, no matter the language. However, if a message'south status determines that it should be displayed, only the language is specified and doesn't match the language LOOT is running in, the message volition non exist displayed.
Bash Tags	A listing of Bash Tags. These are used by Wrye Bash when generating a Bashed Patch, and are detailed in Wrye Bash'south readme. LOOT's metadata includes Bash Tag addition and removal suggestions, and any Bash Tags that came with the plugin are also displayed. As Loot can suggest Fustigate Tags exist added or removed, information technology is possible for the same Tag to announced twice, beingness suggested for improver and removal. In such cases, removal overrides add-on. Each Fustigate Tag has three fields: The state determines whether the Tag is to exist suggested for improver or removal. The name is the actual Bash Tag name. The status decides if the Tag is to be suggested or not. It functions as for files and letters. If a plugin's masters are missing, an error message volition be displayed for it. Filter patches are special mods designed for utilize with a Bashed Patch that exercise non require all their masters to be nowadays, and so whatsoever plugin with the Filter tag practical and missing masters volition not crusade any errors to be displayed.
Dingy Info	A listing of dirty plugin CRCs and related information. Each row has 5 fields: The CRC of the dirty plugin. The ITM Count for the dirty plugin. The number of Deleted References that the dirty plugin contains. The number of Deleted Navmeshes that the dirty plugin contains. The name of the Cleaning Utility to apply to clean the dirty plugin. LOOT uses the information supplied to construct a warning message for the plugin if it matches any of the given CRCs.
Locations	A list of URLs that the mod to which the plugin belongs can be found at. This metadata is not currently used past Loot, but it may be useful to record information technology. Each location has two fields: The URL at which the plugin'due south parent modernistic can be establish. The Proper noun you wish to requite the URL.

Editing Settings

LOOT'south settings dialog.

Loot's settings may exist accessed by clicking Settings button in Boodle's menu bar. The settings are detailed in the tabular array below.

Setting	Clarification
Default Game	If set to something other than Autodetect, this overrides game autodetection. If the game specified is not detected, Loot falls back to autodetection.
Linguistic communication	Controls the linguistic communication Boodle uses. Whatever plugin letters that practise not accept translations in the selected linguistic communication will be displayed in English, if available, or in their bachelor language otherwise.
Enable Debug Logging	If enabled, writes debug output to %LOCALAPPDATA%\LOOT\LOOTDebugLog.txt. Debug logging can accept a noticeable impact on performance, so information technology is off past default.
Update masterlist before sorting	If checked, Loot volition update its masterlist, should an update be bachelor, earlier sorting plugins.

LOOT'south game-specific settings can be customised in the games table. New game profiles can exist added, making it easy to utilise LOOT across multiple copies of a game, including full conversion mods. LOOT ships with settings for the Nehrim - At Fate'southward Edge total conversion mod as an example. Game profiles tin can also be deleted, though the agile game cannot have its contour deleted, and Boodle will recreate the profiles for the base games it supports (Oblivion, Skyrim, Fallout 3, Fallout: New Vegas, Fallout 4) when it is side by side run.

The game settings are explained in the table below.

Game Setting	Description
Name	The proper noun of the game, or another identifying text, that is displayed in menus and the LOOT'due south championship bar.
Base Game Type	Every game LOOT runs for must use the plugin file format and load social club system of one of the following games: TES 4: Oblivion TES V: Skyrim Fallout three Fallout: New Vegas Fallout 4
LOOT Folder Name	The sub-folder which Loot uses to shop the game'south files in. Each game must exist given a unique sub-binder.
Master File	The game's master chief file. This is checked for when detecting if the game is installed.
Masterlist Repository URL	The URL of the repository that Loot uses to update its local copy of the masterlist. If left empty, masterlist updating will exist skipped. Masterlist repositories are Git repositories that are configured to allow unauthenticated read access and contain a masterlist file named masterlist.yaml in their root directory. The LOOT team maintains a set of official repositories for the games that LOOT supports by default.
Masterlist Repository Branch	The co-operative of the masterlist repository that LOOT should become masterlist updates from.
Install Path	The path to the game's folder, in which the Information folder lies. Either this or a registry primal must exist supplied.
Install Path Registry Key	The registry cardinal, in HKEY_LOCAL_MACHINE, that contains the install path of the game. This is used to obtain the install path if LOOT has no previous record of the game's install path, or LOOT'due south stored install path is invalid. Either this or an install path must be supplied.

Contributing & Support

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

If you encounter an outcome with LOOT, check the Ofttimes Asked Questions wiki page in instance a solution is available at that place.

Otherwise, full general discussion and support takes place in Boodle's official forum thread, which is linked to on LOOT'southward homepage.

If you want to submit metadata, the easiest way to exercise then is to add the metadata to your ain LOOT install, so use the Re-create Metadata characteristic to easily get it in a course that you tin then edit into a masterlist on GitHub or mail service in the official forum threads.

Information on dirty plugins is very welcome, just for such data to be useful we crave at least the filename and the CRC of the dirty plugin. The CRC may be calculated using Wrye Bash or seven-Zip, with other sources being unverified as right. In the case of vii-Zip, the CRC checksum for information is the 1 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 on GitHub, and a total list of GitHub contributors may exist institute here.

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

In add-on, the post-obit are credited with application-related support:

• Original icon: jonwd7
• Translations:
  • Brazilian Portuguese: Kassane
  • Chinese: bluesky404
  • Danish: Freso
  • Finnish: 3ventic
  • French: Kaos
  • German language: lpradel
  • Korean: SteamB23
  • Polish: Łukasz Niemczyk
  • Russian: Tokc.D.K.
  • Spanish: Sharlikran
• Beta testing: Too many to listing, cheers all!

Boodle is written in C/C++, HTML5, CSS3 and JavaScript, and uses the Heave, 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 hither.

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 total 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 talk over their reasoning for such an endeavour with the Team. Information technology may be that what the derivative piece of work would do differently is already planned for a future version of LOOT or would be happily integrated into Loot, thus fugitive any extra effort past others.

Boodle has been specifically designed to foreclose it existence locked into the LOOT Team's official masterlist repositories. Nevertheless, the LOOT Squad appeals to the community to avoid the distribution of unofficial masterlists, every bit this would only hamper the attempt to create one set of stores for load order data. Whatever issues with a masterlist are best brought to the attention of the LOOT Squad and then that they may be remedied.

GNU Free Documentation License Version 1.3 Find:

Copyright (C) 2012—2016 WrinklyNinja
Permission is granted to copy, distribute and/or modify this certificate under the terms of the GNU Free Documentation License, Version one.3 or any later on version published past the Free Software Foundation; with no Invariant Sections, no Front-Comprehend Texts, and no Back-Comprehend Texts.
A copy of the license is included in the file named "GNU FDL v1.3.txt".

Version History

Only program history is recorded hither. A total history of masterlist changes may be viewed past browsing the GitHub repositories.

0.ix.0 - 21 May 2016

Fixes

• Redate Plugins attempted to redate plugins that were missing, causing an fault.
• LOOT would not launch when run by a user with a non-ASCII local application data path.
• Sorting processed priority value inheritance throughout the load lodge incorrectly, leading to some plugins being positioned incorrectly.
• The conflict filter displayed only the target plugin when enabled for the first time in a session.
• The behaviour of the search functionality was inconsistent.
• Duplicate messages could be displayed under certain circumstances.
• Opening the metadata editor for one plugin displayed the metadata for another plugin under certain circumstances.
• Changing the current game quickly could leave the UI unresponsive.
• Applying a filter then scrolling the plugin carte list would display some cards with no content.
• Plugin cards would disappearing when jumping to a plugin bill of fare virtually the bottom of the load society using the sidebar.
• Clicking on a disabled element in a dropdown menu would cause the carte du jour to close.
• The UI font size was also large, due to a misunderstanding of the Material Design guidelines.
• Attempting to build native Linux and 64-fleck executables produced errors. Such builds are unsupported and no official builds are planned.

Additions

• Back up for Fallout 4.
• A warning message is displayed in the Full general Information carte du jour if the user has not sorted their load order in the electric current Boodle session.
• An fault bulletin is displayed in the General Information card when a circadian interaction sorting error is encountered, and remains at that place until sorting is side by side attempted.

Changes

• Improve sorting functioning past just reading the header when loading game's main master file.
• References to "BSAs" have been replaced with the more generic "Archives" as Fallout 4's BSA equivalents employ a different file extension.
• The sorting process at present recognises when the sorted load guild is identical to the existing load society and informs the user, fugitive unnecessary filesystem interaction.
• The metadata editor has been reimplemented every bit a single resizeable panel displayed below the plugin carte list instead of a split up editor for each plugin card.
• Editable table styling has been improved to more than closely align to the Material Blueprint guidelines.
• Minor UI changes have been fabricated to scrollbar and focus outline styling to ameliorate accessibility.
• UI interaction performance has been improved, especially when scrolling the plugin carte list.
• The PayPal donation link at present points to the PayPal.Me service, which has a more than polished UX and lower fees.
• LOOT'south settings file handling has been reimplemented, fixing crashes due to invalid settings values and allowing missing settings to utilise their default values.
• Plugin version cord extraction has been reimplemented, improving its accurateness and maintainability.
• Plugin CRC, file and version status evaluation has been optimised to employ cached data where it exists, fugitive unnecessary filesystem interaction.
• The French and Danish translations take been updated.
• The installer now only creates one shortcut for LOOT in the Start menu, following Microsoft guidelines.
• A lot of code has been refactored and improved to increase its quality.
• The Boost (1.60), CEF (3.2623.1401.gb90a3be), libespm (2.5.2), libgit2 (0.24.ane), libloadorder (9.3.0) and Polymer (1.4) dependencies take been updated to the versions given in brackets.

Removals

• The Flattr donation link.
• The experimental theming support, as its implementation was incompatible with Polymer 1.ii's styling mechanisms.

0.viii.1 - 27 September 2015

• Fixed crash when loading plugins due to lack of thread safety.
• Fixed masterlist updater and validator non checking for valid condition and regex syntax.
• Bank check for rubber file paths when parsing conditions.
• Updated Chinese translation.
• Updated Heave (1.59.0), libgit2 (0.23.2) and CEF (co-operative 2454) dependencies. This fixes the masterlist updater non working correctly for Windows Vista users.

0.8.0 - 22 July 2015

• Stock-still Cannot read property 'button' of undefined errors when sorting.
• Fixed many miscellaneous bugs, including initialisation crashes and incorrect metadata input/output treatment.
• Fixed metadata editors not immigration unsaved edits when editing is cancelled.
• Fixed LOOT silently discarding some not-unique metadata: an error message will now be displayed when loading or attempting to apply such metadata.
• Stock-still userlist parsing errors being saved as general messages in the userlist.
• Fixed and improved LOOT'south version comparing behaviour for a broad variety of version string formats. This involved removing Boodle'south usage of the Alphanum code library.
• Improved detail of metadata syntax error messages.
• Improved plugin loading operation for computers with weaker multithreading capabilities (eg. not-hyperthreaded dual-core or single-core CPUs).
• LOOT no longer displays validity warnings for inactive plugins.
• LOOT now displays a more user-friendly fault when a syntax error is encountered in an updated masterlist.
• Added back up for loading custom user interface themes, and added a dark theme.
• Metadata syntax support changes, meet the metadata syntax document for details.
• Boodle'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 High german and Russian translations.
• Updated libgit2 to v0.23.0.

0.7.one - 22 June 2015

• Stock-still Boodle UI opening in default browser on launch.
• Fixed No existing load club position errors when sorting.
• Fixed bulletin filters being ignored by plugin cards later on 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 equally numbers.
• Boodle now uses versioned masterlists, and 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 concluding country restored on launch.
• Darkened background backside cards to increase dissimilarity.
• Added content search, accessible from an icon button in the header bar, and using the Ctrl-F keyboard shortcut.
• Added Copy Load Club feature to chief menu.
• Updated French translation.

0.7.0 - 20 May 2015

Fixes

• The settings.yaml included with the installer was very old.
• Inactive incompatibilities were displayed equally mistake letters. They are now displayed every bit warnings.
• Masterlist entries that matched the aforementioned plugin were non being merged. Now one exact match and whatsoever 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 at present handled past deleting the local repository and re-cloning the remote.
• Masterlist updating failed when the path to LOOT'due south folder included a junction link.
• Masterlists would not 'update' to older revisions. This tin can be useful for testing, so now they can do and then.
• 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 accept read permissions, now such games are treated as non 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.
• Boodle would merely detect Skyrim plugins equally loading BSAs. Plugins for the other games that besides load BSAs are at present correctly detected as such.
• Depending on the plugins involved, sorting could produce a different load guild every time it was run. Sorting now produces unchanging load orders, using existing load lodge position where in that location is no reason to move a plugin.

Additions

• Danish and Korean translations.
• If LOOT can't detect any installed games, information technology now launches to the settings dialog, where the game settings can be edited to allow a game to be detected.
• A Copy Content detail in the principal bill of fare, to copy the plugin listing and all information information technology contains to the clipboard every bit YAML-formatted text.
• A Refresh Content item in the principal menu, which re-scans plugin headers and updates Loot's content.
• Loot is now built with High DPI display support.
• Masterlist updates can at present be performed independently of sorting.
• A First-Time Tips dialog volition exist displayed on the first run of any detail version of Loot.
• Attempting to close Boodle with an unapplied sorted load society or an open up plugin editor will trigger a confirmation dialog.
• Back up for GitHub Flavored Markdown in letters, minus features specific to the GitHub site, such as @mentions and emoji.
• Support for message content substitution metadata syntax in the masterlist.
• Display of Boodle'southward build revision has been added to the About dialog.
• Plugin location metadata can now exist added through the user interface.
• A content filter, which hides plugins that don't accept the filter text nowadays 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 Pattern.
• LOOT now parses the masterlist and plugin headers on startup, and the resulting content is displayed with the plugins in their electric current load social club.
• Each plugin now has its ain editor, and multiple editors can exist opened at once.
• Drag 'due north' 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, then are not displayed until either procedure has been performed.
• The View Debug Log menu item has been replaced with a Open Debug Log Location bill of fare item to make it easier to share the file itself.
• Debug logging command has been simplified to enable/disable, replacing the Debug Verbosity setting with an Enable Debug Logging toggle.
• Changes to game settings at present take immediate effect.
• Masterlist updating now exits earlier if the masterlist is already upwards-to-appointment.
• Masterlist revisions are now displayed using the shortest unique substring that is at least seven characters long.
• Making edits to plugin metadata before applying a calculated load society no longer causes Boodle to recalculate the load order. Instead, the displayed load order is applied, and the metadata edits volition be applied the side by side 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 functioning improvements.
• Updated Boost (1.58.0), libgit2 (0.22.ii) and libloadorder dependencies.

Removals

• Messages with multiple language strings can no longer be created through the user interface. User-added multiple-language letters will be converted to single-linguistic communication strings if their plugin's editor is opened and then closed using the OK button.
• The Copy Proper name menu item has been removed, equally plugin names can now be selected and copied using Ctrl-C.
• Equally Loot no longer generates reports, it doesn't salve them either.

API

• Fixed some documentation errors.
• Fixed the API creating a LOOT folder when being initialised.
• Stock-still 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 linguistic communication codes.
• Stock-still 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 guild 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 definiteness and consistency of functionality.
• Added loot_get_build_id(), which outputs the shortened revision ID that the API was built from.

0.half dozen.1 - 22 December 2014

• Fixed: Default Nehrim registry entry path.
• Fixed: Messages in the wrong language existence selected.
• Fixed: LOOT windows opening off-screen if the screen expanse 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 tin can no longer be deleted from the settings window.
• Stock-still: Plugin metadata being lost when the settings window was exited with the "OK" button, leading to possible condition evaluation problems.
• Fixed: A bare report bug when running on systems which don't have Internet Explorer xi installed.
• Fixed: Reports appearing empty of all content when no global messages are to be displayed.
• Changed: Updated Heave (1.57.0), libgit2 (0.21.iii), wxWidgets (3.0.2) and libloadorder (6.0.three) dependencies. This includes a critical security vulnerability set up 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 Accost Aware flag to the LOOT executable.

0.half dozen.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 loftier priority doesn't cause other plugins with lower priorities to be positioned incorrectly.
• The default linguistic communication is at present correctly ready to English language.
• 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 final position and size.
• Command line parameter for selecting the game Boodle should run for.
• Finnish translation.

Removals

• Back up 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 upshot.
• The power to open reports in an external browser. This was necessitated past the changes to report generation.
• The MSVC 2013 redistributable requirement.
• The "None Specified" language option is no longer available: English language is the new default.

Changes

• Unified and improved the metadata editors launched during and exterior of sorting.
  • The metadata editor now resizes more accordingly.
  • The mid-sorting instance hides the requirement, incompatibility, Bash Tags, dirty info and message lists.
  • Both instances now accept a disharmonize filter, priority display in their plugin list and drag 'n' drib from the plugin list into whatever metadata lists are visible.
  • The mid-sorting example also hides the load after entry edit button, and the button to add together new entries (so drag 'due north' 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 accept their listing entry text bolded.
  • Checkboxes have been added to set whether or non a priority value is "global". The UI also at present displays the priority value used in comparisons (ie. with the millions and college digits omitted).
  • A right-click carte command for clearing all user-added metadata for all plugins has been added to the metadata editor.
• Missing chief/requirement and incompatibility errors are downgraded to warnings if the plugin in question is inactive.
• Masterlist update errors have been made more than user-friendly.
• If an mistake is encountered during masterlist update, LOOT will now silently delete the repository binder and attempt the update again. If it fails again, it volition then report an mistake.
• Masterlist update now handles repository interaction a lot more than like Git itself does, so should be less error-prone.
• Circadian dependency fault messages at present particular the full bicycle.
• LOOT's report now uses a static HTML file and generates a javascript file that is dynamically loaded to comprise the report data. This removes the PugiXML build dependency.
• Debug log message priorities adjusted and then that medium verbosity includes more useful data.
• Updated dependencies: libgit2 (v0.21.0), wxWidgets (v3.0.i), libloadorder (latest), libespm (latest).

0.5.0 - 31 March 2014

• Initial release.

brodiedwellied1975.blogspot.com

Source: https://loot.github.io/docs/0.9.0/LOOT%20Readme.html

Share this post