I think that resources such as mod pack images and descriptions should be stored locally instead of downloading them each time. After a typical user first downloads a mod pack, the only thing they will use the launcher for is actually launching Minecraft. You could still push mod pack updates, additions, and deletions to the launchers, but downloading once is enough for the same resource. This would also reduce server load.
Store Resources Locally
- Thread starter Xadneil
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
- Status
Aye.... suggestion #1... (similar to how the "t______ launcher" works) ...make a checksum list of all the current files, and have the launcher download that checksum list and check it against a locally cached copy of each file.... if a checksum has changed on an individual file, only that file should be downloaded again...
right now you're downloading the logo and splash multiple times per single launch... not only would it reduce server load, but it'll speed up loading the list of modpacks and maps (and texturepacks whenever they arrive)....
...suggestion #2... a progress bar for loading the modpacks and maps would be nice so we will know when it's done... (especially in the future when there's more than just 3 things in the list)
...suggestion #3... right now if a file for the modpack or map lists fails download for whatever reason (such as an overloaded launcher server), it screws up and gives an error (the common error everyone was seeing the other day).... you need some sort of error checking to catch that and redownload the file....
all of these suggestions kinda go together so i didn't bother making a new thread for each one
right now you're downloading the logo and splash multiple times per single launch... not only would it reduce server load, but it'll speed up loading the list of modpacks and maps (and texturepacks whenever they arrive)....
...suggestion #2... a progress bar for loading the modpacks and maps would be nice so we will know when it's done... (especially in the future when there's more than just 3 things in the list)
...suggestion #3... right now if a file for the modpack or map lists fails download for whatever reason (such as an overloaded launcher server), it screws up and gives an error (the common error everyone was seeing the other day).... you need some sort of error checking to catch that and redownload the file....
all of these suggestions kinda go together so i didn't bother making a new thread for each one
I just want to give this suggestion a thumbs up.
Last night, my FTB installation is working perfectly. This morning, the launcher crashes due to a missing image on creeperhost. All the game files are complete and ready to play on my computer. I just cannot launch them due to the way the launcher is designed.
Last night, my FTB installation is working perfectly. This morning, the launcher crashes due to a missing image on creeperhost. All the game files are complete and ready to play on my computer. I just cannot launch them due to the way the launcher is designed.
Yep this was a suggestion I was going to make as well ( I removed my existing post
"
"
There are a few improvements I would like to suggest for the launcher.
1. Launcher should have cached versions of files to fall back on if server can't be reached
2. When the launcher pulls the modpacks.xml file from the server, this file should contain checksums for the modpack files
3. if checksums match cached copies, these files should not be downloaded. This should reduce server load, as only a single xml file will be downloaded at launch if files are up to date
also, a loadbalancer for your servers with some mirrors would likely be a good investment
"1. Launcher should have cached versions of files to fall back on if server can't be reached
2. When the launcher pulls the modpacks.xml file from the server, this file should contain checksums for the modpack files
3. if checksums match cached copies, these files should not be downloaded. This should reduce server load, as only a single xml file will be downloaded at launch if files are up to date
also, a loadbalancer for your servers with some mirrors would likely be a good investment
When it comes to improvements; Launcher should have a 'Choose version' option.
Example:
Suppose: I'm playing a specific version of FTB. Server is running that version.
The FTB modpack is updated and the update is pushed to the users. Server will still be the previous version, rendering users unable to play on their regular server.
At least, until server admin finds time to upload new server files, reboot the server and check that the update was OK.
Now then, imagine that someone finds out there's a game-breaking bug in the modpack, killing the worlds and ruining the server. Sure, a smart server admin would have backup archives, but the player would not be able to roll-back their version as the current update system is forcing the update onto the user. (Note: When the updates were released yesterday, I could choose whether or not to update the client. However, if I clicked 'No', the client would close instead of allowing me to launch the game.)
This would also keep files locally, though separated into backup archives. That way, the repo server wouldn't have to be loaded with different versions of the mods in order for folks to download these if a game-breaking bug is discovered.
Example:
Suppose: I'm playing a specific version of FTB. Server is running that version.
The FTB modpack is updated and the update is pushed to the users. Server will still be the previous version, rendering users unable to play on their regular server.
At least, until server admin finds time to upload new server files, reboot the server and check that the update was OK.
Now then, imagine that someone finds out there's a game-breaking bug in the modpack, killing the worlds and ruining the server. Sure, a smart server admin would have backup archives, but the player would not be able to roll-back their version as the current update system is forcing the update onto the user. (Note: When the updates were released yesterday, I could choose whether or not to update the client. However, if I clicked 'No', the client would close instead of allowing me to launch the game.)
This would also keep files locally, though separated into backup archives. That way, the repo server wouldn't have to be loaded with different versions of the mods in order for folks to download these if a game-breaking bug is discovered.
Personally I think all of these suggestions for the most part are great, however it needs to be kept in mind that you the launcher needs to be easy to upkeep so things like multiple versions isn't the best thing in the world once you take that idea off of paper (or off of the computer screen I guess?). Having a "Cache" that is downloaded and re-updated every time the launcher gets a solid connection to the host would be nice. This way it would try and update the cache, if it cannot then it would use what cache is there and you would still be able to play if the host was down for any of the numerous reasons it could be.
- Status