diff --git a/docs/LOOT Readme.html b/docs/LOOT Readme.html index 7c099498..0886da00 100644 --- a/docs/LOOT Readme.html +++ b/docs/LOOT Readme.html @@ -259,7 +259,7 @@ figure > div { -
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.
+
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 the metadata editor is open.

The header bar provides access to LOOT's main features. Most of these features get disabled while the metadata editor is open, so if you're trying to use an option that is faded out, first close the editor. @@ -274,7 +274,7 @@ figure > div {

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. +

Once LOOT has calculated a load order, it 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 order contains changes, the plugin cards are sorted into that order and 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. @@ -309,19 +309,19 @@ figure > div {

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 archives 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. +

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 editing its metadata. 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 archives 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 it in the metadata editor.

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

  1. The Active Plugin icon.
  2. The plugin name.
  3. The plugin's version number, extracted from its description field. -
  4. 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. +
  5. 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, except the the CRC of the game's main master file, which is never displayed.
  6. The Master File icon.
  7. The Empty Plugin icon.
  8. The Loads Archive icon.
  9. The Has User Metadata icon. -
  10. 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. +
  11. The plugin menu button, which provides access to a few plugin-specific features, including a conflict filter and access 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. @@ -359,10 +359,10 @@ figure > div { -

A metadata editor panel.
+
The 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. +

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 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's menu, or by double-clicking a plugin name in the sidebar. Only one plugin's metadata can be edited at a time. While the editor panel is open, the plugin sidebar also displays any non-zero plugin priorities, to aid setting new priority values. The editor can be resized by grabbing the top of the editor's header and dragging it up or down. @@ -535,6 +535,7 @@ A copy of the license is included in the file named "GNU FDL v1.3.txt".Fixes