As much as I love all the modpacks on FTB, I really wish it made it easier to update them.
Here's the deal, I, like some of you like to disable some mods they may not like, and add in ones we do, some may tweak the configs to have some thing's spawn and some not.
Like for me with DW20's 1.6 pack, I like adding in Better grass and leaves, more bees and trees, Mekanism, magical crops, and two furniture mods, along with a few smaller ones like one that lets you format books/signs allowing colored text and such on them. I like editing some of the world gen mods to have only such and such biomes spawn, to have more of the BIG hu8ge redwood trees spawn.
However when we update a modpack, even if it gets plopped into the same location, it removes all the mods, it removes all the configs and plops in all default.
It would be very nice if instead of wiping everything and plopping in all new, it would just replace the old mod files with the mods that got updated, as not all of them have changed! Leave everything else the same, and leave the configs alone unless it was truly fully needed to regen due to mod change.
I did a simple "Copy all from pack backup, paste over existing 'update', ignore if already there there" and really between DW .11, and .12 only a handful of the mods changed/updated from what I saw. Do we really need -everything- cleared just for that?
Now with the new update, I have to re-do all the ID clonflicts from the mods I added, redo all the config changes. Now I could just C&P the configs, but if it happens to be a mod that did change something? Then such would botch it up. I have no idea what configs will work just the same, and what ones may have added or changed something. So it's back to doing it all by hand.
This is an annoying hassle. I do want to keep up to date with the mods, but I don't want to run the risk of screwing over my world. If the pack updates, it should REPLACE -just- the mods it is updating and perhaps also tell us that 'this change in config has happened, DO YOU WANT IT TO?"
I seen updates that have changed nothing but ONE setting in a config.. and it wiped out everything.
I think from now on I'm just going to manually update thing's as I find them updated, as I'm tiered of no matter how small the update it, having it wipe everything you have added/disabled/changed.
Here's the deal, I, like some of you like to disable some mods they may not like, and add in ones we do, some may tweak the configs to have some thing's spawn and some not.
Like for me with DW20's 1.6 pack, I like adding in Better grass and leaves, more bees and trees, Mekanism, magical crops, and two furniture mods, along with a few smaller ones like one that lets you format books/signs allowing colored text and such on them. I like editing some of the world gen mods to have only such and such biomes spawn, to have more of the BIG hu8ge redwood trees spawn.
However when we update a modpack, even if it gets plopped into the same location, it removes all the mods, it removes all the configs and plops in all default.
It would be very nice if instead of wiping everything and plopping in all new, it would just replace the old mod files with the mods that got updated, as not all of them have changed! Leave everything else the same, and leave the configs alone unless it was truly fully needed to regen due to mod change.
I did a simple "Copy all from pack backup, paste over existing 'update', ignore if already there there" and really between DW .11, and .12 only a handful of the mods changed/updated from what I saw. Do we really need -everything- cleared just for that?
Now with the new update, I have to re-do all the ID clonflicts from the mods I added, redo all the config changes. Now I could just C&P the configs, but if it happens to be a mod that did change something? Then such would botch it up. I have no idea what configs will work just the same, and what ones may have added or changed something. So it's back to doing it all by hand.
This is an annoying hassle. I do want to keep up to date with the mods, but I don't want to run the risk of screwing over my world. If the pack updates, it should REPLACE -just- the mods it is updating and perhaps also tell us that 'this change in config has happened, DO YOU WANT IT TO?"
I seen updates that have changed nothing but ONE setting in a config.. and it wiped out everything.
I think from now on I'm just going to manually update thing's as I find them updated, as I'm tiered of no matter how small the update it, having it wipe everything you have added/disabled/changed.