How to delete LOOT rules and turn off LOOT?

[Grestorn]

Unless you tell us an example where a dependency rule would make a wrong decision, it's hard to answer that.

 

The rules used by LOOT are created by the community (and the mod authors). If there's an error in the masterlist, you should discuss that with the people responsible for it. On this site you can go to their discord server: https://loot.github.io/

 

Cyclic rules are not only caused by masterlist rules. Sometimes you've just added a erroneous rule yourself which causes a cycle.

[Grestorn]

The why is: to run a mod that requires esm and esp in a set order but Vortex is auto ruling itself in either an unstable game or dependcy loop error thus making a game unstable.

 

Which mods and plugins are you talking about? (Don't worry, no one will judge you, even if those mods are from LL or other sources :) )

[Furrnado]

The mod's esm gets auto ruled to load after main game and expansions' esm. The mod author recommends to moving the mod's esm between main game and expansion to stablize the game. When I move the mod esm, vortex will not take off that auto rule that has been applied. And if I apply new a rule the old one stays in pllace forcing into a dependency loop.

 

**fixed spelling**

Edited November 4, 2018 by Furrnado

[Furrnado]

FO NV: New California, the install instruction say place ESM between main game ESM and its expansions. But on installation the mod ESM gets tagged to load after expansions and you can't get rid of the auto rules it puts in place.

[sopmac45]

FO NV: New California, the install instruction say place ESM between main game ESM and its expansions. But on installation the mod ESM gets tagged to load after expansions and you can't get rid of the auto rules it puts in place.

 

 

When you installed this mod, it did also automatically install its expansions or you had to install them manually ?

[Furrnado]

I used the Install from File button on Vortex to install the mod. Sadly I didn't view the install instructions until after the game become unstable. But that doesn't help get rid of the auto rules that vortex put in place.

[HadToRegister]

FO NV: New California, the install instruction say place ESM between main game ESM and its expansions. But on installation the mod ESM gets tagged to load after expansions and you can't get rid of the auto rules it puts in place.

 

Go to the PLUGINS tab TURN OFF AUTOSORT

 

Doubleclick on the New California ESM, a panel on the right should open up, scroll down the panel until you see this

 

 

 

Select LOCKED TO INDEX, change the Number of the Index to a Number that will go between the Main ESM and the DLC esms.

 

Let me know if that works

 

IE New Vegas.esm = Index 0

New California esm index = 1

Dlc esm = 2

DLC esm = 3

etc

[Furrnado]

 

FO NV: New California, the install instruction say place ESM between main game ESM and its expansions. But on installation the mod ESM gets tagged to load after expansions and you can't get rid of the auto rules it puts in place.

 

Go to the PLUGINS tab

Doubleclick on the New California ESM, a panel on the right should open up, scroll down the panel until you see this

 

 

 

Select LOCKED TO INDEX, change the Number of the Index to a Number that will go between the Main ESM and the DLC esms.

 

Let me know if that works

 

Does this overwrite/turn off/ignore the dependency rule that vortex puts in?

[HadToRegister]

 

 

FO NV: New California, the install instruction say place ESM between main game ESM and its expansions. But on installation the mod ESM gets tagged to load after expansions and you can't get rid of the auto rules it puts in place.

 

Go to the PLUGINS tab

Doubleclick on the New California ESM, a panel on the right should open up, scroll down the panel until you see this

 

 

 

Select LOCKED TO INDEX, change the Number of the Index to a Number that will go between the Main ESM and the DLC esms.

 

Let me know if that works

 

Does this overwrite/turn off/ignore the dependency rule that vortex puts in?

 

 

That's what it's for

You only want to use it on special cases though, not for your entire load order, but for ONE mod that must go a certain place

[Grestorn]

Well, I don't think that New California needs to be loaded after the DLCs.

 

Could you link where you've read that? I don't remember reading that.