Jump to content

Vortex creating cyclical rules


MarineCorps

Recommended Posts

 

 

that is blatantly false. Scrap everything and satellite world map both have issues with other mods that vortex doesn't seem to know about or ignores.

 

 

Vortex doesn't claim to know everything about every plugin but the rules that exist are curated by people who know what they're doing.

When you're saying things like "I can't move a master below regular plugins? that sucks" you clearly don't understand the basic rules of load ordering. This isn't a rule Vortex or LOOT enforce, it's how the engine works and it's one of a bunch of things you need to know before you can expect to create a valid load order.

 

To create a cycle you have to add a rule that contradicts one of the masterlist (or implicit) rules and considering you don't know how masters work there is no chance in hell that the incorrect rule isn't the one you added yourself.

Link to comment
Share on other sites

 

 

The thing is, with Vortex, if Vortex is not complaining about File Conflicts, then it means your load order is good.

 

The only way to get a bad load order, is to start messing with making your own rules and groups.

 

The only time you should be doing anything in Vortex is when it gives you an error message

 

that is blatantly false. Scrap everything and satellite world map both have issues with other mods that vortex doesn't seem to know about or ignores.

 

 

 

*Response Deleted*

 

Not worth my time.

 

Vortex doesn't claim to know everything about every plugin but the rules that exist are curated by people who know what they're doing.

When you're saying things like "I can't move a master below regular plugins? that sucks" you clearly don't understand the basic rules of load ordering. This isn't a rule Vortex or LOOT enforce, it's how the engine works and it's one of a bunch of things you need to know before you can expect to create a valid load order.

 

To create a cycle you have to add a rule that contradicts one of the masterlist (or implicit) rules and considering you don't know how masters work there is no chance in hell that the incorrect rule isn't the one you added yourself.

Thats ok. I saw it anyways. You seem to have added a bunch of words to "my sucks" comment. I was lamenting that I would no longer be able to solve my conflict by moving it down on the load order. Not complaining that I couldn't move a ESM to the bottom of a load order. I'm aware that is not something can be done by the game engine, I hadn't noticed that SS2 was a master. I had at that point been trying to get SS2 to work for over 6 hours, I was more than a little frustrated and vortexes generic error message was not helping.

Link to comment
Share on other sites

It still doesn't make sense. You can not have a conflict that would be resolved by dragging a master below a regular plugin. It's not possible for anyone and never has been, including the mod author.

If you think you have a conflict that could be solved that way that is 100% a misunderstanding on your part.

Your problem isn't that you can't do what you need to do, your problem is that you want to do something that makes no sense and is definitively not necessary.

 

And Vortex's error message in this case is absolutely not generic, when a cycle happens you can press "More" for "More information" and it will tell you exactly which plugins are involved in the cycle and why. There is literally no further information necessary.

Link to comment
Share on other sites

I hadn't noticed SS2 was a master at the time. 6 hours of frustration led me to miss that fact. It would have been nice if vortex had said unable to load a master file after a esp or something like that

 

It does say that!

If you look at the details for a cycle it says "a.esm --> b.esp" (as in: b loads after a) and when you hover over the arrow (which is a visibly a link) it says "a.esm is a master, b.esp is not".

So it's telling you everything you need to know: b loads after a because a is a master and b isn't.

The only way you didn't see that is if you either in those 6 hours never even cared about what Vortex was telling you or you didn't understand what masters are and didn't consider it could be important.

Sorry, but if you don't read what Vortex is telling you, don't complain that Vortex didn't tell you something. This is frustrating.

Link to comment
Share on other sites

Guest deleted34304850

it is abundantly clear here that you are pushing all the blame for your ails onto Vortex. This is completely disengenuous.

 

Each time you come back with a counter argument the evidence that Vortex has done nothinig wrong, and contains no errors to support you is overwhelming.

 

All your problems start and end with you and your lack of understanding about basic modding concepts.

 

I would suggest that you stop arguing and instead spend some time watching Gopher on YouTube, who has an entire series that is designed to get you going with Vortex (and other mod managers too, to be fair).

You 100% need to educate yourself. This is not a criticism or a personal attack it is my opinion based on the evidence of your posts in this topic thus far.

 

Spend time to educate yourself, and then come back to Vortex and try again.

 

If you continue on your current path, all you are going to do is destroy your game, and frustrate yourself immensely.

 

The thing is, the people who offer help in these forums have been through what you're going through and want to help you, but you only get help if you help yourself and stop trying to blame Vortex for everything you've done wrong thus far.

Link to comment
Share on other sites

The thing is, with Vortex, if Vortex is not complaining about File Conflicts, then it means your load order is good.

 

The only way to get a bad load order, is to start messing with making your own rules and groups.

 

The only time you should be doing anything in Vortex is when it gives you an error message

The thing is, with Vortex, if Vortex is not complaining about File Conflicts, then it means your load order is good.

Ummm... whut? Wouldja like some apple with that orange?

 

The thing is, with Vortex, if Vortex is not complaining about File Conflicts, then it means your load order is good.

 

The only way to get a bad load order, is to start messing with making your own rules and groups.

 

The only time you should be doing anything in Vortex is when it gives you an error message

that is blatantly false. Scrap everything and satellite world map both have issues with other mods that vortex doesn't seem to know about or ignores.

 

*Response Deleted*

 

Not worth my time.

Not worth my time.

I'm also not worth your time? How does load order affect file conflicts, which are reported independently of, and I believe before, when load order is calculated?

Not worth my time.

I'm also not worth your time? How does load order affect file conflicts, which are reported independently of, and I believe before, when load order is calculated?

 

What are you on about?

 

Where in my post did I quote you, that you would even assume that?

Does that summarize it sufficiently? You didn't respond to my first incredulous query, as if I also wasn't worth the time, so I restated the question more directly. You still haven't explained how file conflict detection in Vortex is dependent upon load order. Tannin didn't respond to it, either.

 

Is this a well-you-know-what-I-meant moment?

Link to comment
Share on other sites

Guest deleted34304850

don't take this the wrong way, but can you not bicker in a thread where someone obviously has an issue with vortex?

all you are doing is making the thread just that much more difficult to follow.

concentrate on helping the OP in their thread. everything else can go in the bin. thanks.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...