diff --git a/docs/help/LOOT-FAQs.html b/docs/help/LOOT-FAQs.html index 25b2159..cdf6d29 100644 --- a/docs/help/LOOT-FAQs.html +++ b/docs/help/LOOT-FAQs.html @@ -5,7 +5,7 @@ title: FAQs
LOOT is BOSS v3. It got turned into a separate utility because concerns were raised about the major changes in expected functionality between v2 and v3.
+LOOT started development as BOSS v3, but it became a separate utility to avoid confusion once it became clear how little in common it had with BOSS v2.
No. However, most of BOSS's current contributors are now more interested in contributing to LOOT, so BOSS will likely lag further behind in getting unrecognised plugins recognised as time goes on. One of the many improvements in LOOT is that it has no unrecognised plugins.
+No. However, BOSS is no longer maintained for games other than Oblivion, and LOOT generally provides superior functionality.
There can be more than one correct load order for a given set of plugins. For example, some plugins may not conflict or depend on each other, so their relative orders wouldn't matter. The load order BOSS gives is hand-made to look 'neat' as well as work, so plugins from the same mod will usually get grouped together, but LOOT doesn't know which plugins belong to which mod, so it just puts them where it thinks they work.
-The most thorough method is to look for conflicts in TES5Edit and decide for yourself if the load order LOOT gives resolves them to your liking. Alternatively, selecting a plugin in LOOT before applying a sorted load order and ticking the "Show only conflicting plugins" checkbox will let you see if the two plugins conflict at all (though it will also show plugins with BSAs if the selected plugin loads a BSA).
-Users can supply metadata themselves to alter the order LOOT gives. It's not as precise as the user rules feature offered by BOSS, due to the nature of LOOT's ordering system, but there are two types of metadata that can be supplied to change load order:
+The most thorough method is to look for conflicts in TES5Edit and decide for yourself if the load order LOOT gives resolves them to your liking.
+ +Users can supply metadata themselves to alter the order LOOT gives. There are two types of metadata that can be supplied to change load order:
Alternatively, your WinSock configuration may be corrupt: this can be fixed using the instructions here and here, or there's a fix-it utility here.
-If LOOT still can't update its masterlist, you can update manually by downloading this file and placing it in the %LOCALAPPDATA%\LOOT\Skyrim folder. Replace Skyrim with oblivion, fallout3 or falloutnv as necessary, in the URL and the folder path.
If LOOT still can't update its masterlist, you can update manually by downloading this file and placing it in the %LOCALAPPDATA%\LOOT\Skyrim folder. Replace Skyrim with oblivion, fallout3, falloutnv or fallout4 as necessary, in the URL and the folder path.
Mod Organizer 1.2.10 has a bug preventing LOOT 0.7.0 from working properly. This has been fixed in Mod Organizer 1.2.11, and later versions.
-There is also another issue that occasionally causes LOOT's window to be blank when started through Mod Organiser: this can be avoided by adding the --single-process argument to Mod Organiser's LOOT launching settings, though doing so also reduces the quality of text displayed in LOOT.
Mod Organizer can also interfere with LOOT's startup, causing causes LOOT's window to be blank when started through Mod Organiser: this can be avoided by adding the --single-process argument to Mod Organiser's LOOT launching settings, though doing so may have negative side effects.
Steam likes to remove the game's Registry entry when the game is updated or its cache is verified. Run the game's launcher to add the Registry entry back again. LOOT will then be able to detect the game.
- +Steam removes the game's Registry entry when the game is updated or its cache is verified. Run the game's launcher to add the Registry entry back again. LOOT will then be able to detect the game.
Another cause may be that the game is installed in a location where you does not have read permissions, in which case LOOT cannot read your plugins, and so treats the game as undetected. Try checking the game path's permissions, and ensuring you have read access.
plugins.txt and loadorder.txt. Won't this break something?LOOT has probably just replaced the CR LF line breaks with LF line breaks. It doesn't make any difference to the game.
LOOT has just replaced the CR LF line breaks with LF line breaks. It doesn't make any difference to the game.