First it would make installation repair impossible, if some of your install is corrupted then it would mean download the last full installer and. Same thing if you want to rollback to a previous version, instead of, again, only downloading the delta, it would also mean download the last full installer before the desired rollback version and download and re-apply all the delta patches.Īs I said in my previous post, IMHO, the only way to avoid storing twice everything would be to create the installers 'on demand', or an hybrid approach, where the latest version is stored and if you want a rollback version then it creates a zip or a rar on demand with the right files. First it would make installation repair impossible, if some of your install is corrupted then it would mean download the last full installer and reapply all the patches instead of just downloading the delta to fix the issue. It's an insane amount of 'make work' that's entirely self-inflicted by Galaxy for which offline installers hilariously get the blame for being a 'burden'.īrianSim: A far saner solution would have been to have only offline installers (inc delta patches) logistical path, but create a script per game that automates the process of Galaxy downloading offline installers (including handling multi-part installers transparently), fetches and applies the correct delta patch based on detecting installed game version, then installs them with a /silent switch, then at the end offers to either delete them or back them up (maybe even automate that based on a Galaxy preference). info, galaxy.dll, etc, files), having to repack multi-game installers into individual ones, or the endless stream of Galaxy related 'updated internal installer structure, no change to game save files' changelogs which also only sprang into existence in 2014.

Only GOG could think of doing absolutely everything twice over via two different logistical branches, and then deliberately degrade the one directly related to GOG's Unique Selling Point as 'progress'.Įdit: And I'd love to know how much time was wasted having to unnecessarily repack the whole GOG catalogue offline installers to include Galaxy metadata (.hashdb. A far saner solution would have been to have only offline installers (inc delta patches) logistical path, but create a script per game that automates the process of Galaxy downloading offline installers (including handling multi-part installers transparently), fetches and applies the correct delta patch based on detecting installed game version, then installs them with a /silent switch, then at the end offers to either delete them or back them up (maybe even automate that based on a Galaxy preference). Prior to Galaxy there was no need to store everything twice 'because muh client'. The 'storage space problem' was only created in 2014 by Galaxy doubling up on logistics under the guise of 'simplification' in the first place.

Steam offline installer