Giving up on Vortex for now

[Deleted3897072User]

I've uninstalled Vortex and gone back to using NMM. You can recycle my slot in the alpha and allow someone else to participate if you like.

 

Alas, it doesn't support the kind of things that I need to do when I'm developing and testing mods, so I won't be using it.

 

Thanks for all the hard work and for running the alpha. It will be great for a lot of people and I wish you well with the project.

 

OMB

[Tannin42]

It would be great if you'd let us know what it is that you'd need Vortex to do before you could switch.

[Deleted3897072User]

Two things that I've already posted about elsewhere - conflict resolution at the individual file level and precise positioning of plugins in the load order. Doing these in NMM is easy and doing them in Vortex is a pain. So ... for me it's a no-brainer.

 

But most users don't test mods the way I do and don't need such features anyway. So don't treat this as a feature request :D

[Tannin42]

Individual file conflict resolution is on the todo list.

 

But why do you need exact plugin positioning?

[Ethreon]

It makes for good visual representation of a load order. It's very easy and intuitive to drag plugins around where we want them to be as opposed to setting up rules.

[Ghostwalker71]

quick and simple mod order adjustments help a great deal during mod development to figure out the best placement of the mod file in relation to conflicting or potential conflicting mods. the need to set up rules and adjust settings each time a function is changed is a rather intrusive disruption as I try to produce the most efficient functionality in my mod.

[Tannin42]

@Ethreon It's what you're used to, that's not the same as intuitive.

And my question was why you need precise plugin positioning to do mod development?

 

 

Edit:

@Ghostwalker71: How are you going to figure out the best placement by moving it around in your local list? I'd like to understand what your process here is that makes that feature necessary.

[Ghostwalker71]

I can't speak for the OP on this, but for me I NEED precise plugin placement, because having to stop development just to rewrite rules for the mod to get placed where I want it, rather than just dragging it to the position I want to test, not only completely breaks my thought process but also wastes a considerable amount of time over the course of development. In other words it is unduly cumbersome and restrictive.

[ousnius]

I can't speak for the OP on this, but for me I NEED precise plugin placement, because having to stop development just to rewrite rules for the mod to get placed where I want it, rather than just dragging it to the position I want to test, not only completely breaks my thought process but also wastes a considerable amount of time over the course of development. In other words it is unduly cumbersome and restrictive.

 

Why do you need to move your plugin order around to test your mods?

You said you need it at specific positions to test, but what's the technical reason for that?

 

You can temporarily force a global priority to the plugin, if you need it to be at the end always for testing purposes.

I'm not sure why would need to test intentionally breaking your mod by putting it above conflicting other plugins.

 

What I do agree on is the visual representation of both the mod and plugin order.

The result of what all your rules and priorities come down to isn't clear enough to me yet.

[sr383]

The challenge of depending on meta rules in Loot is that those are more or less invisible, unless you're looking at an individual file. In some cases, I probably create more rules than I need to because I'm trying to reverse some undesirable result that I set in motion. :dry:

 

I find it easier to drag and drop plugs-ins on the right and assets on the left until I get the results I'm after. I then create rules in Loot so that its load order matches what I've come up with, at least, in the essentials.