Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I use it. Never ran into any problems and I'm running 94 plugins (although its more like 100 plugins, but I merged many of them), without a single crash.
Huh? You're referring to the Load Order Optimization Tool, yes? https://loot.github.io/
It uses a Masterlist and the FalloutNV.esm and additional DLC plugins are always loaded first by default using LOOT.
If OldWorldBlues.esm was loaded in the second slot (assuming you mean right below FalloutNV.esm) its form IDs would be prefixed 01. Every time. It doesn't change by playthrough, it depends entirely on the order you load your plugins.
The game will recognize that your load order has changed. As long as you account for master dependencies and record overrides, no harm should come from rearranging things.
Pay attention to mod descriptions though: if a mod mentions if it has to be placed at a specific place in the load order (say: after/before this or that mod, at the end of your mod list), check manually after running LOOT. (I have one mod that requires its esm files to be put at the end of the load order, and LOOT messes this up every time.)
Yes. I've never heard of LOOT doing this before, and I've been using it for years. Never has it loaded mods before the DLC or main esm.
LOOT works even better than its predecessor, BOSS.