Modpack friendly
Posted: Fri Dec 16, 2016 4:08 pm
Basically, from how I understand how mods work, the name of a mod is the name of the folder the files are in. if this is zipped, the name of the mod is the name of the zip file.
what about modpacks? Since the release of the mod portal (with the idea that a mod pack is listed as a mod on the mod portal, and people just download it and expect it to work) People have approached me asking if it's possible to merge my mods into one big mod to release as a mod pack. This goes against my licence agreement. You're not allowed to release edited versions of my mods (Mostly for version control, make sure everyone actually has the same thing. Also a reason why Config mod is it's own mod with a different licence to allow redistributing edited versions)
Anyway... My suggestion, keep the level of files in a folder, but if multiple folders are located in a zip file, behave differently.
each folder within the zip would function as a mod in itself, bound by a mod pack. the mod pack name would be the zip files name, and have it's own entry in the mods list.
This would allow components of the mod pack to be disabled independently, as well as the mod pack being able to be disabled as a whole.
Perhaps an info.json file could be placed in the zip file alongside the mod folders to hold the modpack information.
what about modpacks? Since the release of the mod portal (with the idea that a mod pack is listed as a mod on the mod portal, and people just download it and expect it to work) People have approached me asking if it's possible to merge my mods into one big mod to release as a mod pack. This goes against my licence agreement. You're not allowed to release edited versions of my mods (Mostly for version control, make sure everyone actually has the same thing. Also a reason why Config mod is it's own mod with a different licence to allow redistributing edited versions)
Anyway... My suggestion, keep the level of files in a folder, but if multiple folders are located in a zip file, behave differently.
each folder within the zip would function as a mod in itself, bound by a mod pack. the mod pack name would be the zip files name, and have it's own entry in the mods list.
This would allow components of the mod pack to be disabled independently, as well as the mod pack being able to be disabled as a whole.
Perhaps an info.json file could be placed in the zip file alongside the mod folders to hold the modpack information.