Nexus-Mods / Vortex

Vortex Development
GNU General Public License v3.0
910 stars 134 forks source link

Suggestion - Collections: Differ mods #10685

Closed VortexFeedback closed 2 years ago

VortexFeedback commented 2 years ago

Vortex Version: 1.5.0-r48+internal Memory: 15.95 GB System: win32 x64 (10.0.19043) It would be great if Vortex could differ between mods that are from (other) collections. So we could create very modular collections without the need to remove unwanted (other collections) mods from the current collection profile when updating a revision.

Simple example: Collection A contains F4SE... Collection B uses F4Se and provides more mods Collection C is what i work on - wich requires some mods from Collection B, but I'll have to remove all mods from Collection A and B on every revision update.

I think this is very much the reason why almost everybody is doing an "all in one" collection.

Reported by: Sephrajin

TanninOne commented 2 years ago

I genuinely don't understand what you're suggesting. Why would you have to remove mods from Collection A&B when you update C? There isn't anything stopping you from creating modular collections in the current system and it shouldn't matter if they overlap.

TanninOne commented 2 years ago

closed due to lack of feedback