Only download new/changed content when updating a modpack

[NightKev]

The FTB launcher really needs to only download any mods/configs that are new/changed between updates, rather than re-downloading the entire thing. There's no reason for every update to cause a new 40MB+ of data to be downloaded, that's massively wasteful.

 

[TheSandwichMakr]

That would be much more difficult since the entire pack is archived to reduce the filesize, if every mod and config file were archived separately the modpack would be much larger and it would be more complicated to code it that way.

 

[NightKev]

They're kind of canceling out any gains they're getting from archiving the modpacks by making the launcher redownload the entire pack on every update...

 

[TheSandwichMakr]

True, however it's much easier to code and there's not only people updating, and you have to consider that there's still people downloading the modpack for the first time after the first update.

 

[tigar tar]

why not have both? for those first time users it downloads the zip and then it runs a check to see if the mods are there and if they are it wont download the zip it will just download those that are newer versions(could be checked by date created or md5 or anything)

 

[TheSandwichMakr]

Wow, I must have been really tired and not thinking before... It would probably be relatively easy for them to keep a download containing only the updated files and when theres an update the launcher could simply check to see if the update is only one version different and if it is it could just use the download link in the xml file with a -updated suffix. This could actually really lighten the load on creeperhost's servers.