We have a name! And a Q&A session with Tannin regarding the new mod manager.

[SorrelKat]

In response to post #50032012. #50032057, #50032732, #50052427, #50054092, #50054512, #50055082, #50076857, #50077437, #50077572, #50081452, #50103602, #50114677 are all replies on the same post.

othmanarnaout wrote: I don't know if this has been asked before, but here goes,..

Does this mean that a Vortex-made modded, say, Skyrim can run without launching it through vortex. What I mean to say is, will one be able to share one's custom Skyrim with a friend, by giving said friend a copy of one's Skyrim folder, and that friend would be able to run it by starting skse without the need for them to install or use vortex?

please forgive one for one's language.

othmanarnaout wrote: please note that I am not referring to piracy, but the act of sharing a modded Skyrim with a newb friend :P

Roccondil wrote: you specifically sharing just your (mod) data folders? probably not- if I understand this correctly, what's placed in your Skyrim directories are not the actual mod files, which are stored elsewhere. You'd have to share both your Data folders and your mod folders, and hope that the paths to the mod folders are identical on both machines.

othmanarnaout wrote: let me clarify,.. Im a hardcore MO user, as such, I know that sharing setups with a friend is a huge pain in the rear, because of the vfs and how it handles mods. Now don't get me wrong, I love MO more than anything, but i wish there were a way to easily "compile" a working setup that would run on another computer by simply running skse.As an upside to this, your skyrim folder would be very clean, relatively. NMM on the other hand, puts your installed mods into the skyrim folder and things get messy, yes, but in theory you should be able to run a copy of your nmm-modded skyrim on another pc by simply running skse(though i haven't really tested that). Point is, since Vortex will have a virtualization system similar to that of nmm, does that mean that the data folder in the actaul game folder will also contain the installed mods, making it copy-able and run-able on another pc without the need for vortex on said system? (since there is no vfs involved).

TechAngel85 wrote: "Profile sharing" has been planned for some time with Nexus. I'm not sure if it'll be implemented with Vortex, but that would be logical. The way I understood it is users would be able to save their setups and upload it to Nexus. Then users could download the setup and the manager would do most of the work of setting it up for the user. This is suppose to give an identical setup as the author. For example, if you wanted you have the exact same setup as Gopher, all you would have to do is download his shared setup.

If this was ever worked out completely, I'm not sure. I haven't heard anything on it in a long time. To be honest, this sounded like a dream because I can't see how they would be able to work out all the small details that come with modding (FOMOD installers, hidden/deleted assets, load orders, patches, etc, etc). I could see it being possible on more simple setups, but not on advanced ones.

TerminusVitae wrote: @TechAngel85 oh my everloving frak... Skyrim Modpacks?!? hell to the yes, my god... modded Minecraft better step up their game, if that ever comes true. :)

TechAngel85 wrote: Here's the news article discussing it: http://www.nexusmods.com/skyrim/news/12569/?

As I mentioned, it just sort of died, so I don't know if they ever figured it out.

othmanarnaout wrote: that would be nice, it would also help each mod's author get the right amount of downloads.

lued123 wrote: Apparently someone over at ModPicker is working on this.
Or was anyway...

Dark0ne wrote: This sort of functionality has been delayed until we can get some proper file version control on the main site themselves with mod authors using it properly. There's no point in doing it without it, else mod profiles become obsolete the moment mod authors delete their files.

TechAngel85 wrote: Proper mod versioning? OMG yes!

I've always been a fan of Major.Minor.Hotfix.

Major = introduce new functionality or assets, etc. (rarely changes)
Minor - smaller changes such as expanding mod coverage, updating current assets, etc.
Hotfix - fixes bugs or issues but changes nothing else.

A standardized versioning scheme for mods on Nexus is severely needed! Though it would need to be well enough defined (with enough examples given) so anyone could understand it.

othmanarnaout wrote: um,.. YES PLEASE!! <3

Arthmoor wrote:

proper file version control

What exactly does this mean?

I'm also interested in what "proper file version control" means. It sounds like it could mean forced versioning, which is one of my complaints about Bethesda. Sure, they allow you to do a custom version, then ignore it in a few places, confusing users. Download version 12 of this mod, version 3.1. Uh. :D

[SorrelKat]

In response to post #50086932. #50092882 is also a reply to the same post.

audixas wrote: Hey Tannin, sorry for the dumb question, but I probably failed to understand how exactly the vfs will work.

The way I understand it, is that you will install mod A, a texture pack for example, and then you install another pack B that replaces some of the textures contained within pack A. The Vortex then puts these files in the Data directory, depending on which mod takes priority. So if B has a higher priority, the overwriting files from it will be used, but if you change the priority or remove mod B, then A's file will be used.

Is that correct?

lued123 wrote: Vortex establishes links between the data folder and the mods' individual folders. It doesn't actually put the files in the data folder, it just sort of says "pull those from here when the user says go". This means that you can control and/or undo overwrites in post, just like you would in MO, since all of the mod files are intact. It's done a little differently here though. You don't specify the entire mod order, you just specify rules for it like, say, "Noble Skyrim and Skyrim HD have overwrites, use the files from Noble". That way, you don't have to come up with a logical order for your 7000 totally compatible mods that aren't touching each other. You only have to order the ones that need ordering, the conflicts.
TLDR: Yes, if I understand your question correctly.
However, this is not the vfs. MO is the only manager to feature that so far. Vortex may have it as an option later, but the default will be basically a souped up version of NMM's file management that doesn't take years to do anything.

One probable conflict with this approach, if you don't have a set load order, then my hotkeys won't trigger the appropriate things. Yes, every time I change my load order (rare) I have to go into the file and change the first (two) characters, but that's a minor thing. My hotkeys would be useless if there is no set load order.

[Jennievm]

Ok I'm no expert when it comes to any of this jargon you guys talk about. I am however an avid user of MO. I've tried NMM for Skyrim SE and its way more complicated IMO to keep things in order and mind you this talk that vortex is gonna use a similar method of doing things than NMM scares me a little as your average user. As long as I have my two windows one for plugins and one for the actual mods where i can move mods and plugins around its just way easier for me than having to look at one big mess of things. Will people coming from MO find this new thing easy to navigate ?

[nagothm]

One question,

I know that Vortex is being developed by Nexus, but there are some mods that people develop on their own sites, especially some in alpha stages. One feature that Tannin added to MO2 was the ability to add custom hyperlinks to other sites. I know that version tracking is probably impossible, but will simple custom hyperlinks to other sites be a feature in Vortex?

[Quaxolotl]

In response to post #50119747.

Jennievm wrote: Ok I'm no expert when it comes to any of this jargon you guys talk about. I am however an avid user of MO. I've tried NMM for Skyrim SE and its way more complicated IMO to keep things in order and mind you this talk that vortex is gonna use a similar method of doing things than NMM scares me a little as your average user. As long as I have my two windows one for plugins and one for the actual mods where i can move mods and plugins around its just way easier for me than having to look at one big mess of things. Will people coming from MO find this new thing easy to navigate ?

From what I've read in this they don't talk about the Interface at all. It's probable that it will be neither NMM like nor MO like. If they put emphasis on usability like they say they do I doubt you'll be disappointed.

[lued123]

In response to post #50086932. #50092882, #50118302 are all replies on the same post.

audixas wrote: Hey Tannin, sorry for the dumb question, but I probably failed to understand how exactly the vfs will work.

The way I understand it, is that you will install mod A, a texture pack for example, and then you install another pack B that replaces some of the textures contained within pack A. The Vortex then puts these files in the Data directory, depending on which mod takes priority. So if B has a higher priority, the overwriting files from it will be used, but if you change the priority or remove mod B, then A's file will be used.

Is that correct?

lued123 wrote: Vortex establishes links between the data folder and the mods' individual folders. It doesn't actually put the files in the data folder, it just sort of says "pull those from here when the user says go". This means that you can control and/or undo overwrites in post, just like you would in MO, since all of the mod files are intact. It's done a little differently here though. You don't specify the entire mod order, you just specify rules for it like, say, "Noble Skyrim and Skyrim HD have overwrites, use the files from Noble". That way, you don't have to come up with a logical order for your 7000 totally compatible mods that aren't touching each other. You only have to order the ones that need ordering, the conflicts.
TLDR: Yes, if I understand your question correctly.
However, this is not the vfs. MO is the only manager to feature that so far. Vortex may have it as an option later, but the default will be basically a souped up version of NMM's file management that doesn't take years to do anything.

SorrelKat wrote: One probable conflict with this approach, if you don't have a set load order, then my hotkeys won't trigger the appropriate things. Yes, every time I change my load order (rare) I have to go into the file and change the first (two) characters, but that's a minor thing. My hotkeys would be useless if there is no set load order.

Setting priority in this way doesn't change load order. It changes installation order. Your load order will be managed by you and LOOT, like it always has been.

[SorrelKat]

In response to post #50086932. #50092882, #50118302, #50130152 are all replies on the same post.

audixas wrote: Hey Tannin, sorry for the dumb question, but I probably failed to understand how exactly the vfs will work.

The way I understand it, is that you will install mod A, a texture pack for example, and then you install another pack B that replaces some of the textures contained within pack A. The Vortex then puts these files in the Data directory, depending on which mod takes priority. So if B has a higher priority, the overwriting files from it will be used, but if you change the priority or remove mod B, then A's file will be used.

Is that correct?

lued123 wrote: Vortex establishes links between the data folder and the mods' individual folders. It doesn't actually put the files in the data folder, it just sort of says "pull those from here when the user says go". This means that you can control and/or undo overwrites in post, just like you would in MO, since all of the mod files are intact. It's done a little differently here though. You don't specify the entire mod order, you just specify rules for it like, say, "Noble Skyrim and Skyrim HD have overwrites, use the files from Noble". That way, you don't have to come up with a logical order for your 7000 totally compatible mods that aren't touching each other. You only have to order the ones that need ordering, the conflicts.
TLDR: Yes, if I understand your question correctly.
However, this is not the vfs. MO is the only manager to feature that so far. Vortex may have it as an option later, but the default will be basically a souped up version of NMM's file management that doesn't take years to do anything.

SorrelKat wrote: One probable conflict with this approach, if you don't have a set load order, then my hotkeys won't trigger the appropriate things. Yes, every time I change my load order (rare) I have to go into the file and change the first (two) characters, but that's a minor thing. My hotkeys would be useless if there is no set load order.

lued123 wrote: Setting priority in this way doesn't change load order. It changes installation order. Your load order will be managed by you and LOOT, like it always has been.

From other posts, it's my understanding that Vortex will incorporate LOOT-like sorting.

Edit: Tannin42 says that we'll be able to change the load order, so nvm. Edited May 15, 2017 by SorrelKat

[btn2k3]

Any Chance we could see a Virtual version of the root folder.

So tools like xedit, enb, etc can be installed in virtual folder and not touch the game folder at all?

 

This could also work out well for quickly swapping out enb configs without having to worry about if you have removed all of the old files from a previous enb (each gets a folder and that folder can be enabled/disabled from a tab in Vortex similar to how MO currently enabled and disables folder reads for virtuallization).

 

Just a thought...

[wheelchairwillie]

In response to post #50135442.

btn2k3 wrote: Any Chance we could see a Virtual version of the root folder.
So tools like xedit, enb, etc can be installed in virtual folder and not touch the game folder at all?

This could also work out well for quickly swapping out enb configs without having to worry about if you have removed all of the old files from a previous enb (each gets a folder and that folder can be enabled/disabled from a tab in Vortex similar to how MO currently enabled and disables folder reads for virtuallization).

Just a thought...

Great idea! Image enhancers are so common now having improved root support to switch between them from a dropdown or something as well as storing the setting in the mod list (in case one switch between have several) would be a great time saver.
Particularly since many mods are optimized to only work with specific releases and versions like weather changers or overhauls.
Would also make mod development easier by making it quicker to change between "vanilla" and modded setups with the required tools in place for testing.

[JakFlacket]

In response to post #50135442. #50140607 is also a reply to the same post.

btn2k3 wrote: Any Chance we could see a Virtual version of the root folder.
So tools like xedit, enb, etc can be installed in virtual folder and not touch the game folder at all?

This could also work out well for quickly swapping out enb configs without having to worry about if you have removed all of the old files from a previous enb (each gets a folder and that folder can be enabled/disabled from a tab in Vortex similar to how MO currently enabled and disables folder reads for virtuallization).

Just a thought...

wheelchairwillie wrote: Great idea! Image enhancers are so common now having improved root support to switch between them from a dropdown or something as well as storing the setting in the mod list (in case one switch between have several) would be a great time saver.
Particularly since many mods are optimized to only work with specific releases and versions like weather changers or overhauls.
Would also make mod development easier by making it quicker to change between "vanilla" and modded setups with the required tools in place for testing.

This would be an EXTREMELY appreciated edition to vortex. It would further serve to streamline management of these mods, and as a user of multiple of these root folder modifications, it would really make vortex the obvious choice.