Dependency Fulfiller export mod name and download location and for conflicts before/after rules.
But, for per-file conflicts Vortex also includes "winner" mod. Exporting these "winner" mods files in case they don't follow the per-mod rules would be an advantage.
In addition to the common before/after conflict rules, Vortex can create two other type of rules by drag-and-drop a connection from any mod to another mod, regardless of have any loose file conflicts or not. The first rule is "Requires", meaning example mod B requires mod A and if you enable mod B you'll get a warning if mod A isn't also enabled. Since Dependency Fulfiller can fulfill such requirements it's not so important to include the "Requires" rules, but still would expect it's easy to export these rules so I see little reason to not export them and afterwards import them.
The second is the "Conflicts with" rule, where example mod C is incompatible with mod D and you shouldn't enable both mods. Since it's not so easy having Dependency Fulfiller disable the incompatible mods, exporting and importing "Conflicts with" rules are important.
Since different "Mod Type" is very few mods not sure if this type of information would be relevant for Dependency Fulfiller, or where's better options for example correctly specifying dependency for downloading and installing file 2 for everyone installing SSE Engine Fixes.
The hardest one is what, if anything, should Dependency Fulfiller do with FOMOD installers. The FOMOD choices can heavily depend on installed mods and having a tailor made auto-FOMOD-installer for a specific selection of mods will definitely be an advantage. The easiest part is to export the FOMOD choices, but since AFAIK Vortex don't seem to have this information meaning even exporting FOMOD-information can be difficult. One possible help here is, NMM at least tried saving the FOMOD information back in 2018, but granted NMM did sometimes "forget" to save this information.
After exporting FOMOD-information, the next problem is, what should Dependency Fulfiller to on importing? Example, if profile 1 already have mod installed and you're on profile 2, should Dependency Fulfiller use the already installed copy even this can use completely different FOMOD choices and wherefore not fulfill all dependencies, or should profile 2 get a profile-specific installation of the mod with correct FOMOD choices? Since profile 2 can include some extra mods not part of dependencies, it's possible the FOMOD choices should really be different from the ones used in profile 1 and the ones being currently imported.
Dependency Fulfiller export mod name and download location and for conflicts before/after rules.
But, for per-file conflicts Vortex also includes "winner" mod. Exporting these "winner" mods files in case they don't follow the per-mod rules would be an advantage.
In addition to the common before/after conflict rules, Vortex can create two other type of rules by drag-and-drop a connection from any mod to another mod, regardless of have any loose file conflicts or not. The first rule is "Requires", meaning example mod B requires mod A and if you enable mod B you'll get a warning if mod A isn't also enabled. Since Dependency Fulfiller can fulfill such requirements it's not so important to include the "Requires" rules, but still would expect it's easy to export these rules so I see little reason to not export them and afterwards import them.
The second is the "Conflicts with" rule, where example mod C is incompatible with mod D and you shouldn't enable both mods. Since it's not so easy having Dependency Fulfiller disable the incompatible mods, exporting and importing "Conflicts with" rules are important.
Since different "Mod Type" is very few mods not sure if this type of information would be relevant for Dependency Fulfiller, or where's better options for example correctly specifying dependency for downloading and installing file 2 for everyone installing SSE Engine Fixes.
The hardest one is what, if anything, should Dependency Fulfiller do with FOMOD installers. The FOMOD choices can heavily depend on installed mods and having a tailor made auto-FOMOD-installer for a specific selection of mods will definitely be an advantage. The easiest part is to export the FOMOD choices, but since AFAIK Vortex don't seem to have this information meaning even exporting FOMOD-information can be difficult. One possible help here is, NMM at least tried saving the FOMOD information back in 2018, but granted NMM did sometimes "forget" to save this information.
After exporting FOMOD-information, the next problem is, what should Dependency Fulfiller to on importing? Example, if profile 1 already have mod installed and you're on profile 2, should Dependency Fulfiller use the already installed copy even this can use completely different FOMOD choices and wherefore not fulfill all dependencies, or should profile 2 get a profile-specific installation of the mod with correct FOMOD choices? Since profile 2 can include some extra mods not part of dependencies, it's possible the FOMOD choices should really be different from the ones used in profile 1 and the ones being currently imported.