Unusual Behavior in Assigning A Load Order Index

[TechDaddy]

Vortex Version: 1.1.10

Game: Fallout 4

 

When starting my game today I noticed none of my console scripts were working properly. I discovered that the load order had been changed, and all the mod assets given different indices.

Now, when I specify a Mod Index in Vortex in order to assign a static location in the load order, it increments the value by seven(7) places. For example, if I assign a mod to index 30 (hex 0x30), it instead sets it to 37 (0x37). So when I then assign it 29 (0x29) it sets it to 30 (0x30) where I intended it. Has anyone else experienced this? If so, what was the resolution, if any?

Please don't hijack this thread with statements telling me how I shouldn't be assigning load order indices manually. I just need to know (1) if anyone else has ever experienced this, and (2) what the resolution was, if any.

Thanks. (Screenshot follows)

 

 

 

[HadToRegister]

Well, telling you to NOT lock order to index isn't hijacking the thread, and it's something you should NOT be doing.

The reason people are going to come in here and tell you NOT to do that, is because you're CREATING a problem that wouldn't BE a problem, by doing this.

If you're following a Load Order Guide, I suggest you stop trying to force Vortex to follow that guide and let Vortex do the sorting.
You're dooming yourself to forever be fighting AGAINST Vortex

[DarkDominion]

If you click on the i behind the Lock Mod Index you will see this ( and thus your answer )

 

 

Edited January 28, 2020 by DarkDominion

[TechDaddy]

Thanks, DarkDominion, for at least addressing the question that was asked.

I was already aware of the info you cited. The problem is that, prior to today, Vortex had never exhibited this behavior. Offsetting the load order index is a minor annoyance and not worth a lot of trouble, but sometimes behavior like this can be symptomatic of a larger issue, which is why I tried to get information here on any known bug or glitch that may exist in Vortex. It doesn't seem like that's going to happen, so at this point, I'll just write script(s) to keep this from happening in the future.

Thanks again, DarkDominion.

[Tannin42]

We fixed a problem in 1.1.11 where the index of locked plugins was always offset by the number of "native" plugins (part of the vanilla game, the ones you can't enable/disable). Is that the offset you're seeing?

 

EDIT: Btw, I found this to be needlessly passive-aggressive:

which is why I tried to get information here on any known bug or glitch that may exist in Vortex. It doesn't seem like that's going to happen

 

Your first post was at 10PM in my timezone and your last one half past midnight. That's hardly a time frame after which you can conclude that you're not going to receive answers.