As someone who has played with mods and custom modpacks for a while, I had an idea. I was looking around at things like magic launcher and other mod-related programs, and something caught my eye. In MultiMC, there is a central mod folder button. It doesn't really do anything useful, just a place to keep spare mods, but it could be so much more. So here comes my idea: what if all of FTB's packs were based off of virtualization?
Now that may not make much sense, so let me explain. With the Technic custom packs, you're not allowed to redistribute minecraft.jar, so you have to make a modpack.jar, which is virtually merged with minecraft.jar in the RAM. If FTB could do this with mods instead of the jar, it would be a revolution in modpack making. Instead of a copy of mods in each pack, there would be a central folder with all FTB mods, and there would be a .json file that would specify which mods to merge.
Imagine the implications. To make a custom pack, you could choose with a checklist of mods, and they would be virtually loaded with the pack. Dependant mods, like ChickenBonesCore would automatically be added. Coupled with no ID conflicts in 1.7 and universal configs, there would be nary a problem. Also, when updating, instead of redownloading everything, there could be one file to add, and one file to delete.
Of course, there are probably plenty of technical implications, but it shouldn't be too much of a problem. Instead of checking the mods folder and loading all the mods in there, one file would specify which mods to load, all in one folder. It would simply be loading mods from a different location.
If this were to be added, modpacks could be changed forever.
Now that may not make much sense, so let me explain. With the Technic custom packs, you're not allowed to redistribute minecraft.jar, so you have to make a modpack.jar, which is virtually merged with minecraft.jar in the RAM. If FTB could do this with mods instead of the jar, it would be a revolution in modpack making. Instead of a copy of mods in each pack, there would be a central folder with all FTB mods, and there would be a .json file that would specify which mods to merge.
Imagine the implications. To make a custom pack, you could choose with a checklist of mods, and they would be virtually loaded with the pack. Dependant mods, like ChickenBonesCore would automatically be added. Coupled with no ID conflicts in 1.7 and universal configs, there would be nary a problem. Also, when updating, instead of redownloading everything, there could be one file to add, and one file to delete.
Of course, there are probably plenty of technical implications, but it shouldn't be too much of a problem. Instead of checking the mods folder and loading all the mods in there, one file would specify which mods to load, all in one folder. It would simply be loading mods from a different location.
If this were to be added, modpacks could be changed forever.