Okay, after yet another 'herp derp we don't need no steenkin' permission' mod packs that someone attempted to advertise on another forum I happen to frequent, I gave it a brief looksie and said to myself "Hmm... you know, I could probably write a config pack for that, and it would work out nearly identical, other than the end-user having to manually download the mods themselves, all nice and legal-like". Which really gave me an idea.
Lots of people don't like GregTech because they do not like how it changes IC2 recipies. I could probably offer config packs for various custom settings (such as turning all the altered recipes back to IC2 standard) that people who don't like them can use, and those who do like them can point to them as an alternate solution for those who don't. In other words, pretty much putting the whole debate to rest.
Now then, just to clarify:
A Config Pack is from MultiMC. Basically, it saves all of the .cfg settings. You can then freely distribute these config packs because it's just the .cfg settings, not the mods themselves, you still have to (hopefully legitimately) obtain copies of the mods themselves. The advantage of a config pack over a mod pack are; 1) You aren't distributing code or mods, so no need for permissions (although I'd like a mod to pop in and verify that this is okay before I begin, just to be sure), 2) It's just the .cfg files, whose size is measured in KB rather than MB, so it's some thousand times quicker download. Saves a lot on the storage space too.
Config Packs have been around since MMC4.0, around the release of 1.3.2, and was a major point in DW20's App Spotlight. However, I really haven't heard of anyone using them much. So my question is... does anyone care about them? Would anyone actually be interested in obtaining config packs, either as replacements for mod packs being distributed without permissions or as tweaks for FTB mod packs?
Lots of people don't like GregTech because they do not like how it changes IC2 recipies. I could probably offer config packs for various custom settings (such as turning all the altered recipes back to IC2 standard) that people who don't like them can use, and those who do like them can point to them as an alternate solution for those who don't. In other words, pretty much putting the whole debate to rest.
Now then, just to clarify:
A Config Pack is from MultiMC. Basically, it saves all of the .cfg settings. You can then freely distribute these config packs because it's just the .cfg settings, not the mods themselves, you still have to (hopefully legitimately) obtain copies of the mods themselves. The advantage of a config pack over a mod pack are; 1) You aren't distributing code or mods, so no need for permissions (although I'd like a mod to pop in and verify that this is okay before I begin, just to be sure), 2) It's just the .cfg files, whose size is measured in KB rather than MB, so it's some thousand times quicker download. Saves a lot on the storage space too.
Config Packs have been around since MMC4.0, around the release of 1.3.2, and was a major point in DW20's App Spotlight. However, I really haven't heard of anyone using them much. So my question is... does anyone care about them? Would anyone actually be interested in obtaining config packs, either as replacements for mod packs being distributed without permissions or as tweaks for FTB mod packs?