does loot help mo2 ?

[Asein]

is using loot in mod organizer 2 with 100+ mods good or bad idea ?

[Scrab]

Loot is never not a bad idea

 

No matter the amount of mods you have:

1) run loot

2) controlling that nothing is placed wrong (e.g. patches loading after whatever they patch)

[Swanky]

What Scrab said.

I'm also making sure that mods making changes I prefer having priorities over mods that make similar changes. Also, sometimes a bit of manually adjusting the LO can clear up the messy grouping I feel loot is sometimes creating.

[Asein]

29 minutes ago, Scrab said:

Loot is never not a bad idea

 

No matter the amount of mods you have:

1) run loot

2) controlling that nothing is placed wrong (e.g. patches loading after whatever they patch)

 

19 minutes ago, Swanky said:

What Scrab said.

I'm also making sure that mods making changes I prefer having priorities over mods that make similar changes. Also, sometimes a bit of manually adjusting the LO can clear up the messy grouping I feel loot is sometimes creating.

i got confused Because some say bad tool and some say great tool 

 

also do i use Loot or sort plugins from mo2 ?

[anjenthedog]

Using loot outside your mod manager is generally frowned on when using Vortex, since Vortex includes its own Loot, which runs in the background during mod deployment setup (ie no need to fiddle with loot directly only deal with any rare leftover contentions it is unable to parse) 

 

Unless you are a "leet configurator",  some form of loot needs to be used, whether manually for MO2 users, or automatically for Vortex users.

 

in around 600 mod installations so far, I've had less than ~2 dozen times where Vortex wasn't able to properly sort my load order on its own. 

[Just Don't]

1 hour ago, NezYx0 said:

i got confused Because some say bad tool and some say great tool 

If you know how to detect and solve record conflicts in your loadorder you don't need LOOT.

If you're following a guide with a pre-made modlist and loadorder you don't need LOOT.

If your current situation is neither of the above you should 1) use LOOT, 2) read the install instructions/descriptions of the mods you use (in the rare case of some specific loadorder shenanigans) and finally 4) you test in game to see if everything is working as intended. Manual tweaks to your loadorder after using LOOT are common but not always necessary.

 

1 hour ago, NezYx0 said:

also do i use Loot or sort plugins from mo2 ?

MO2 should add the LOOT executable automatically, you can run it from said executable and use it as always. The Sort button in MO2 launchs a built-in version of LOOT, in practice you get the same result but you won't see the classic LOOT window to check for errors or messages (in the built-in Sort button you get logs to check said info). So for the most part it doesn't matter, perhaps regular LOOT is better for most users because you get crucial info right after updating the masterlist/sorting.

[Asein]

11 hours ago, anjenthedog said:

Using loot outside your mod manager is generally frowned on when using Vortex, since Vortex includes its own Loot, which runs in the background during mod deployment setup (ie no need to fiddle with loot directly only deal with any rare leftover contentions it is unable to parse) 

 

Unless you are a "leet configurator",  some form of loot needs to be used, whether manually for MO2 users, or automatically for Vortex users.

 

in around 600 mod installations so far, I've had less than ~2 dozen times where Vortex wasn't able to properly sort my load order on its own. 

 

11 hours ago, Just Don't said:

If you know how to detect and solve record conflicts in your loadorder you don't need LOOT.

If you're following a guide with a pre-made modlist and loadorder you don't need LOOT.

If your current situation is neither of the above you should 1) use LOOT, 2) read the install instructions/descriptions of the mods you use (in the rare case of some specific loadorder shenanigans) and finally 4) you test in game to see if everything is working as intended. Manual tweaks to your loadorder after using LOOT are common but not always necessary.

 

MO2 should add the LOOT executable automatically, you can run it from said executable and use it as always. The Sort button in MO2 launchs a built-in version of LOOT, in practice you get the same result but you won't see the classic LOOT window to check for errors or messages (in the built-in Sort button you get logs to check said info). So for the most part it doesn't matter, perhaps regular LOOT is better for most users because you get crucial info right after updating the masterlist/sorting.

Last Question?

 

when i put mod top Priority does it effect all mods or only mods that conflicts with ?

[anjenthedog]

that seems a particularly MO2 oriented question. I don't use MO2 and haven't ever used it, so I can't help with that.  "top priority" is a meaningless phrase in my vocabulary wrt to Skyrim modding. Best of luck

[Swanky]

3 hours ago, NezYx0 said:

 

Last Question?

 

when i put mod top Priority does it effect all mods or only mods that conflicts with ?

You check which mods conflict in the conflicts column in the left panel of MO2. double click on the conflict to see which files are affected. You see a green + or a red -, this tells you if files are conflict winners or losers.

Note that this does not affect contents of plugins. Those are still handled by actual load order (right panel of MO2), and a plugin which is lower has higher priority, eg wins conflicts. This is why you need the Community patch to load after the main game plugins, for example, to make sure it has priority over the base game files. You can use something like Wrye Bash to create a bashed patch to resolve conflicts around plugins (might need manual cleaning however) and levelled lists.

[Scrab]

12 minutes ago, Swanky said:

You can use something like Wrye Bash to create a bashed patch to resolve conflicts around plugins (might need manual cleaning however)

 

Id recommend you to keep your hands away from them in SE, especially when youre new to modding

Theyre usage is very, very limited in SE due to the existance of esls. The same goes for merging plugins

 

[Asein]

42 minutes ago, Swanky said:

You check which mods conflict in the conflicts column in the left panel of MO2. double click on the conflict to see which files are affected. You see a green + or a red -, this tells you if files are conflict winners or losers.

Note that this does not affect contents of plugins. Those are still handled by actual load order (right panel of MO2), and a plugin which is lower has higher priority, eg wins conflicts. This is why you need the Community patch to load after the main game plugins, for example, to make sure it has priority over the base game files. You can use something like Wrye Bash to create a bashed patch to resolve conflicts around plugins (might need manual cleaning however) and levelled lists.

i don't think you get my question, if i install 2 armor mods and there not conflicts with each other, does it matter who get higher priority ?

[Swanky]

8 hours ago, Scrab said:

 

Id recommend you to keep your hands away from them in SE, especially when youre new to modding

Theyre usage is very, very limited in SE due to the existance of esls. The same goes for merging plugins

 

Yesn't. For Levelled lists you still need a bashed patch afaik. I agree that it's an advanced technique however.

 

7 hours ago, NezYx0 said:

i don't think you get my question, if i install 2 armor mods and there not conflicts with each other, does it matter who get higher priority ?

2 different armor mods that both add something to the game but don't alter anything, load order shouldn't matter.