Is mod conflict resolution all-or-none or did I miss something?

[SirBobbyDanger]

Imported over from NMM.

 

BUT... After sorting through my mod conflicts and applying rules (i.e. load this mod before that mod but after this other mod), it looks like mod conflicts are handled on an all-or-none basis.

 

Example--

 

Texture Mod A and Texture Mod B have 8 files in conflict (they both attempt to retexture the same 4 objects, thus the texture and normal map are in conflict for each item). If I resolve the conflict by via Vortex, I can either get Mod A's 8 conflicting textures or Mod B's conflicting textures depending on which I set to load before and after.

 

With NMM, the install prompt would proceed file-by-file. I'd see something like this: "texturea.dds is already installed by Mod A. Overwrite?" and then I could pick and choose which files I wanted to overwrite. I could keep some of Mod A's conflicting files and some of Mod B's conflicting files. If I am understanding correctly, Vortex reduces that operation to be equivalent to clicking "Yes to mod" on NMM.

 

Or put differently, Skyrim SE will mostly function the same but may have some heinous texture and mesh errors that I painstakingly resolved already in NMM.

 

Did I miss something? Will Vortex eventually have the feature to pick and choose which files end up in the data folder?

 

Thanks.

[Tannin42]

Yes, currently you can only resolve conflicts on a per-mod basis but it is planned to allow per-file granularity, it's just not clear how this would work ui-wise

[Casuallycryptic]

That's good. I could envision situations where it could become frustrating otherwise.

[tajetaje]

Yes, currently you can only resolve conflicts on a per-mod basis but it is planned to allow per-file granularity, it's just not clear how this would work ui-wise

Perhaps a structure where you go by the directory of conflicting files like this:

 

data/textures/*

-or-

data/textures/snapnbuild/*

-or-

data/textures/snapnbuild/housekit/*

-or-

data/textures/snapnbuild/housekit/wall.nif

 

and check what you want to override, like with current conflict resolution.

[Grestorn]

MO allowed to select this for each file. You got a list of files which were provided by multiple mods. And you could overwrite the global "overwrite" order manually for each file.

 

The challenge is not so much to implement a feature like this, but to do that in an intuitive way which doesn't confuse people. As we can see right now, the down scaled feature set of Vortex is already a problem as it is right now...

[sopmac45]

MO allowed to select this for each file. You got a list of files which were provided by multiple mods. And you could overwrite the global "overwrite" order manually for each file.

 

The challenge is not so much to implement a feature like this, but to do that in an intuitive way which doesn't confuse people. As we can see right now, the down scaled feature set of Vortex is already a problem as it is right now...

 

I agree with you Grestorn, it will confuse me if it was implemented right now … I hope that is at the bottom of Tannin's to-do-list ….