Vortex implementation of MO2's 'overwrite folder' feature.

[turulo]

Hello, recently I started learning a bit of how MO2 works and was pleasantly surprised by the button that creates mods from the unmanaged files that always end up in the Skyrim / Fallout installation.

 

In Vortex I usually ignore them but when using profiles you need to deal with it.

 

So far what I do is to Purge the whole thing and zip it in a file with the profile's name. It's not a big deal but I think MO2's way is a bit more polished.

 

Programs that usually mess up with Vortex are:

- Wrye Bash bashed patches

- Bodyslide .tri morphs and meshes that are not provided in the mod.

- FNIS files.

 

Maybe someday someone figures out an extension to simplify this, I think it would be nice to have.

[rmm200]

How do you feel Vortex messes up FNIS files?

FNIS working with Vortex creates a unique FNIS data file for each profile it is run in. Seems to work great for me.

[HadToRegister]

Hello, recently I started learning a bit of how MO2 works and was pleasantly surprised by the button that creates mods from the unmanaged files that always end up in the Skyrim / Fallout installation.

 

In Vortex I usually ignore them but when using profiles you need to deal with it.

 

So far what I do is to Purge the whole thing and zip it in a file with the profile's name. It's not a big deal but I think MO2's way is a bit more polished.

 

Programs that usually mess up with Vortex are:

- Wrye Bash bashed patches

- Bodyslide .tri morphs and meshes that are not provided in the mod.

- FNIS files.

 

Maybe someday someone figures out an extension to simplify this, I think it would be nice to have.

 

 

OK, you have like 3 or 4 threads over in the Vortex support forum complaining about 4 different things you found with Vortex, and now are claiming Vortex messes up Bashed Patches, FNIS files, and Bodyslide files.

 

Now, if Vortex actually WAS messing these particular files up all the time, there wouldn't be just YOU claiming it's messing up those files.

I use FNIS, and Body Slide, and Wrye Bash to make Bashed Patches, since about 2018, and I haven't run into the Myriad of Problems you've been reporting in th4e Support Forum.

 

At this point I'm genuinely curious as to what you are doing in Vortex, and I'd really like to know exactly the things you are doing in, or to, Vortex that is causing you to have 3 or 4 threads in the support forum worth of problems.

 

Like for instance, walk me through the steps you did to set up your Mod Staging Folder and Download Folder, because nobody has had as many problems in one or two days, for so many different parts of the program, that you have had

 

For instance, what exactly are the steps you're doing when you say "I purge the whole thing and zip it in a file with the profile's name"

 

WHAT files are you just zipping up and naming the archive after the profile?

WHERE are these files located that you're zipping up?

[Tannin42]

MOs overwrite directory makes the game directory appear cleaner, but it's only possible because MO is hooked into the game itself and affects all its accesses to disk.

Further: MO _had_ to move files to the overwrite directory, otherwise it wouldn't have been possible for tools to overwrite files from a mod (because the files in the game directory always have lower priority) and when I introduced that functionality there were at least as many people who hated that as there are people now who want Vortex to work the same.

 

 

Vortex is less intrusive, it simply installs the mods and then the game and tools run as they were intended, basically as if you had installed manually.

 

The tools you mentioned don't "mess up with Vortex", they work exactly as they were programmed. Wrye Bash was developed to write into the game directory. If you consider that a mess then WB "messes up" full stop, got nothing to do with Vortex.

 

Now one could write Vortex extensions to work around that, picking up files from the game directory and move them to separate mod directories, how you identify those files would be up to the extension dev.

 

But it's simply not going to be core functionality in Vortex because it would be another thing that differs from "manual" modding, thus another thing people need to learn about when dealing with Vortex, another exception mod and tool authors may have to point out in their respective descriptions. And it's divisive enough it'd have to be optional and default to off anyway.

And imho a feature that defaults to being disabled should be an extension if possible.