I still want the ability to manually drag plugins in the load order and here's why

[HadToRegister]

I still want to be able to manually drag plugins in my load order, and individually LOCK them in place, and here's the reason why.
(If everything I typed here is wrong, then tell me how to do what it is I'm trying to do, as I'm not finding it anywhere, and I'm using Advanced Mode)

I want a mod like Scrap Everything to stay at the bottom of my load order, and I want it to stay there, I only see the option to make it load before or after something, I want to lock it in place at the bottom, now, I have another mod I want to load BEFORE Scrap Everything, and I mean RIGHT BEFORE Scrap Everything, not BEFORE Scrap Everything somewhere higher up in my load order, but loading PHYSICALLY RIGHT BEFORE Scrap Everything, is there a way to do that?

EX: Load BEFORE Scrap Everything

Mod I want to load before scrap everything.esp
Scrap Everything.esp

NOT LIKE THIS: Load BEFORE Scrap Everything

 

Mod I want to load before scrap everything.esp
Tons of other mods in between.esp
Scrap Everything.esp

YES, TECHNICALLY "The mod I want to load BEFORE Scrap Everything, IS loading before Scrap Everything, but I want it physically right next to Scrap Everything, without a bunch of mods in between it.

Also, if I want MOD A, to load AFTER MOD B, I DON'T want MOD B to move UP the load order to load before MOD A, I want MOD A to move DOWN the load order to physically sit below MOD B
How do I do that? Because every attempt I make, makes the other mod move UP in the load order.

 

EX: Load mod A AFTER MOD B, MOD A moves to be UNDER MOD B.

MOD B.esp
MOD A.esp

NOT LIKE THIS

MOD B.esp at bottom of load order, MOD B moves from the bottom of the load order to the top of the load order to be ABOVE MOD A

Either I'm not using this to its full potential, or it's missing some important features.
Manually Dragging AND LOCKING a mod in place would be something I'd love, because trying to get a load order the way I'd like currently, is like pushing a chain uphill.

Any help would be appreciated.

[Tannin42]

You don't explain why you need that mod to load immediately alongside scrap everything.

But an easy way to achieve what you want is to create a new group that loads last (after dynamic patches if that's what you want) and assign both scrap everything and that mod to it. Then create a plugin rule to load scrap everything after your mod and you're done.

[HadToRegister]

You don't explain why you need that mod to load immediately alongside scrap everything.

But an easy way to achieve what you want is to create a new group that loads last (after dynamic patches if that's what you want) and assign both scrap everything and that mod to it. Then create a plugin rule to load scrap everything after your mod and you're done.

For instance, if I want a mod to load as far down the load order as possible, so it load AFTER everything else in the load order, but BEFORE Scrap Everything.

 

I'll try messing around with the GROUPS thing and see how that goes, I'm not sure how they work, but I'll give it a go

[Tannin42]

At the risk of annoying you: That is not the why, that's still the what.

You want to load plugins as far down as possible, I get that. I ask why you want that.

Loading plugins at a certain location is not an end in itself, you do it to avoid conflicts, ensure certain records aren't overwritten or because you want to force plugins into a order that is visually pleasing to you.

 

Using load order to create a visual pleasing order is plain wrong.

Conflicts are always between specific plugins, they are better solved with rules.

Trying to ensure records aren't overwritten is dangerous because you can't know if that doesn't break other mods. You can do it with groups but you should be prepared to test if all other plugins work afterwards.

 

"Load a plugin as late as possible" is usually a "I want to ensure that this plugin works correctly and I don't care if anything else breaks" and I want to encourage a more constructive approach to load ordering.

[HadToRegister]

At the risk of annoying you: That is not the why, that's still the what.

You want to load plugins as far down as possible, I get that. I ask why you want that.

Loading plugins at a certain location is not an end in itself, you do it to avoid conflicts, ensure certain records aren't overwritten or because you want to force plugins into a order that is visually pleasing to you.

 

Using load order to create a visual pleasing order is plain wrong.

Conflicts are always between specific plugins, they are better solved with rules.

Trying to ensure records aren't overwritten is dangerous because you can't know if that doesn't break other mods. You can do it with groups but you should be prepared to test if all other plugins work afterwards.

 

"Load a plugin as late as possible" is usually a "I want to ensure that this plugin works correctly and I don't care if anything else breaks" and I want to encourage a more constructive approach to load ordering.

 

When I make patches, I need the patch to sit below the esps I've patched so the patch overrides the previous esps.

It would just be easier to drag it in place and lock it there, than to fiddle around with rules for something that could be dragged and locked in a couple of seconds.

 

I tried using rules last night to do this and ended up with a load order that turned into a complete mess because the sorting part of the program misinterpreted what I wanted to do, so it shifted over half of my load order upside down

 

Ex:

I want MOD A to load after MOD B.

I need MOD B to stay where it is.

 

Instead of moving MOD A down BELOW MOD B, (Where MOD B needs to stay), it moved MOD B ABOVE MOD A, and messed up what I had going with MOD B.

If I could've locked MOD B where it was, then MOD A would've had to move below MOD B.

 

Mod B was automatically placed by Vortex where it was, so Vortex was fine with where MOD B was, so I needed Mod A to go below it, since Vortex was OK with the placement of Mod B, Vortex should've moved MOD A down below MOD B, but instead, it moved MOD B ABOVE Mod A, and subsequently moved MOB B ABOVE a bunch of other Mods I needed MOD B to load AFTER.

 

The order rules are great for what they do, but a little 'divine intervention' by being able to manually set and lock a mod is useful too.

 

EX Load order

 

MOD A - (I need to have this load AFTER MOD B)

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

MOD B

____________________________________________

 

What I needed

 

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

MOD B

MOD A

______________________________________________

 

What I got

 

MOD B

MOD A

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

Mod that needs to load BEFORE MOD B

 

[Grestorn]

If you make a patch yourself - which I also do quite often, to integrate the changes of multiple plugins on the same records - then these just have have to be loaded after all plugins they're integrating. This can still be done with rules ... not that many actually. Just one for each plugin you're integrating.

 

But even if you really want to load a plugin last, then just create a group called "Custom Patch" or something like that, assign that to your patches and use the group graph dialog to make sure that this group is sorted after all other groups. Done.

[HadToRegister]

If you make a patch yourself - which I also do quite often, to integrate the changes of multiple plugins on the same records - then these just have have to be loaded after all plugins they're integrating. This can still be done with rules ... not that many actually. Just one for each plugin you're integrating.

 

But even if you really want to load a plugin last, then just create a group called "Custom Patch" or something like that, assign that to your patches and use the group graph dialog to make sure that this group is sorted after all other groups. Done.

So if I make that group, then the mods inside that group can have their own sub-load order inside the group and will move as a unit?

 

 

[Grestorn]

Yes, that's right.

 

Almost all plugins are in the default group, but the normal sorting in between them is still in effect. Same is true for any other group.

[HadToRegister]

Yes, that's right.

 

Almost all plugins are in the default group, but the normal sorting in between them is still in effect. Same is true for any other group.

 

Oh, that's good to know, that way I can organize and sort by groups and sort WITHIN groups

 

Now that's a handy feature that needs to have a tutorial (did GamerPoets do one?)

[batman1741]

*THIS POST WAS FROM BEIN DUMB XD please pay no mind*