Mod install reasons

[TwistedAkai]

Role

I frequently add a few mods onto mod packs

Suggestion

Track mod install reason: Modpack, explicit, dependency

Benefit

To improve update checking

This suggestion is unique

• I have searched the issue tracker and did not find an issue describing my suggestion, especially not one that has been rejected.

You may use the editor below to elaborate further.

I'd like to see PolyMC record a "reason" for why a mod is added to an instance, similar to linux package managers. Presently, this would have little immediate impact but would enable other requested features.

• Modpack: Instance was created from a modpack (record the pack) with this mod.
• Explicit: User added this mod to the instance after creation
• Dependency: This mod was added because another mod required it, per mod downloader should manage dependencies  #211
• Server: Mod was installed per "Synced to server" instances #816, if implemented.

Reasons could be used to inform update checking: Modpack mods could be skipped over in lieu of checking for a new version of the pack itself. If the modpack removes the mod or changes it's version in an update, the update checker can assume it should update/remove the mod accordingly. #65 #324 #1591
Explicit mods could be handled the way all mods presently are, and dependencies could be checked either the same, or only when their dependents have updates.
Regardless, if a mod is removed, or at the user request, mods with the dependency reason should be checked for dependents that have a different install reason. If there are none, suggest removal.

Reasons could also be displayed in the mod list, to assist users in managing their own additions to packs.

[TwistedAkai]

Added bonus would be to enable users to set reasons, for example: setting a mod as being a dependency of another mod, rather than an explicit install.

[binex-dsk]

This is a good idea, but should likely be roped in with modpack updates. Not a huge change as long as we don't break the MultiMC zip format.