Polymod has support for 'modpacks' but they don't really work as expected in the mod configuration menu.
My ideal scheme for this is:
Implement #14 to easily allow modpacks to be installed in one folder.
When scanning for mods, detect any mods with a modpack file.
If there is a modpack file, hide all mods contained within that modpack in the mod configuration menu, and instead render the modpack in the mod configuration screen.
Enabling and disabling the modpack will, as expected, enable and disable all mods in that modpack, and load all requested mods in the provided order.
Modpacks will have a visual indicator that they are modpacks, rather than individual mods.
Modpacks will have a 'break up modpack' button on them. Clicking this button will remove the modpack from the mod configuration list, and put all the individual mods in the pack in their place. The user can then enable or disable the individual mods as expected.
When loading an existing configuration, automatically break up a modpack if one of the components of that modpack has been loaded individually.
A couple examples of modpacks include:
A 'Tricky' modpack, which includes the 'Tricky Song Pack' mod and the 'Tricky Menu Mod' mod. By breaking them up, you can choose to enable just the Tricky songs and disable the menu modifications.
A 'classics' modpack, which might include song packs for Whitty, Carol, Hex, Zardy, Annie, etc. These would be implemented by creating individual mods for each, then simply creating a modpack which contains all of them. Again, the user could break up the modpack to enable just the mods they're interested in, or click one button to load them all at once.
Polymod has support for 'modpacks' but they don't really work as expected in the mod configuration menu.
My ideal scheme for this is:
A couple examples of modpacks include: