Open kayila opened 9 years ago
kayila
commented
9 years ago It would also make sense, in this paradigm, to have the pack file point to one or more index files to actually pull the mods from.
For example... Pack file A specifies to use index file B. Later on it says 'I require mod C version 5' which would then get looked up in the index file and traced back to it's individual quickmod file.
02JanDal
commented
9 years ago Modpacks are simply handled by having a QuickMod file without any actual files (no .jars) but instead it has all it's contained mods as dependencies. Config files can either be done by depending on a QuickMod file for it, or directly in the modpack QuickMod.
Since the references field tells where to look for QuickMod files a link to an index file is not really needed.
kayila
commented
9 years ago Alright, looking at the spec with this in mind, I think I might see a way where it could work. I'd like to work on creating a small modpack to test with and then, if it seems to work reasonably well, I'd be happy to close the issue. Does that work for you?
02JanDal
commented
9 years ago It's outdated, but here's an example: https://github.com/02JanDal/QuickMod/blob/master/FTBUnstable.json
I think it would be super helpful for QuickMod to have the concept of a 'mod pack.' That is, a selection of mods which are packaged together including a specific version for minecraft/forge/etc. It can have a selection of required mods and optional mods. This would be similar in concept to the index file, except it would come with a pre-configured set marked as required as well as specifying what version of minecraft to use. This would enable projects such as MultiMC to import a single quickmod URL and get an entire instance setup with minimal user configuration, allowing for easier distribution of a mod pack
If this is a concept which people are interested in but don't have the cycles to implement, I don't mind forking the project and creating a pull request to submit it back.