Suggestion: Merge mods option in contextual menu

[Emilie217]

The problem

Suggestion : Add a "merge mods" option in contextual menu

Environment

MO2

Details

MO2 is already capable of merging mods if you try to give a new mod an existing mod's name during the installation phase.

It would be great if a "merge" option could be added to the contextual menu (right click) when 2 or mod mods are selected.

I'm not talking about merging ESPs or anything like that, just re-use the "merge" option that already exists within MO.

WHY :

A) Sometimes mods are split into smaller mods. A good example are mods with hot fixes or patches like armors for skyrim who have a "CBBE" patch or BodySlide file. I'll never NOT use CBBE so I'd have no problem merging the CBBE patch in the base mod.

B) This would also help keeping a shorter mod list if we could merge mods to create "packages". A good example I encountered tonight was the 4K texture pack for Skyrim SE which is designed to be modular and so is split in 12 mods. I should have thought ahead and merged them but didn't :/

There's even mods I always use together so if I could merge them I could enable/disable them all at once with this "package" mod.

The current alternative is to either reinstall and use the merge option or to manually go into the folder and drag the files in the mod you want to use as a "base" which is a bit of a pain if you just spent 5 hours on nexus downloading 50+ new shiny things and didn't think ahead >.>.

Thank you for your consideration!

Link to Mod Organizer logs

USVFS

N/A

MO Interface

N/A

[Al12rs]

Instead of adding a context menu I would change the rename option to make it ask whether you want to overwrite/merge or cancel. You would need to manually enter the name of the mod which would be somewhat less convenient. In exchange we don't clutter the menu with an option that will rarely be used.

[mihaifm]

+1 for the merge option, and I think there needs to be a better way of handling merged mods.

Firstly, a flag or some kind of indicator to show that a mod is a merge would be nice, and a warning when attempting to reinstall a merged mod. I've had countless problems when re-installing mods because I forgot to also install patches or optional files that came with them.

Secondly, I agree with OP, a context menu option for merging mods would be nice and useful.

[Al12rs]

+1 for the merge option, and I think there needs to be a better way of handling merged mods.

Firstly, a flag or some kind of indicator to show that a mod is a merge would be nice, and a warning when attempting to reinstall a merged mod. I've had countless problems when re-installing mods because I forgot to also install patches or optional files that came with them.

Secondly, I agree with OP, a context menu option for merging mods would be nice and useful.

But why do you merge patches in the first place? Mo2 isn't actually merging plugins or anything. It's literally copy pasting the contents of modA on top of modB, overwriting modB files if necessary.

In any case the use case offered by OP is a valid one. Merging patches and optional files isn't a good idea. The whole point of MO2 is to keep mods separate so you don't actually overwrite files when installing mods and can easily reinstall stuff since you kept everything separate. Merging goes against that and makes things very difficult to manage.

You can currently add notes to mods if you want to mark them as merged stuff. We already have an issue open for the merged flag here: #1126

[mihaifm]

My bad, I didn’t mean patches, I was referring to optional or miscellaneous files that often come with mods.

Thanks for referencing the other issue, the merged flag would be a nice feature, and keeping track of the merged files even better.

[MinglunZhu]

Guys, stop arguing. Make it an option that you can turn off if you don't want it in the context menu. For people that want it, they can turn it on.