Posted January 08, 2024
high rated
I maintain a list of version discrepancies between offline installers and GOG Galaxy builds, it's available here:
https://airtable.com/shrldLsErlUf3eHqS
I've created this thread at (ø,ø)'s suggestion, so that people unaware of my API forensics thread can easily stumble upon it with a forum search and know that such a thing exists.
Now, for a bit of FAQ:
1. How are you generating this list?
I'm collecting a bunch of GOG API data on a daily basis, including offline installer versions and Galaxy build versions. I have a script that goes through the collected data and generates a list of mismatches, which I then validate and update on Airtable. None of it, with the exception of some manual overrides, deviates from what GOG's API reports.
If anyone is interested in how I do that precisely, the code is open source and available here.
2. You've listed a discrepancy that is actually solved by an offline patch included with the outdated installer!
These sort of situations are rather hard to track unfortunately, so (for the time being) I only check the main installer version for the comparison. Do let me know of such cases and I'll filter them manually.
3. Some entries have newer versions in their offline installers and older ones in Galaxy! What gives?
Usually GOG forgets to mark some Galaxy builds as public, which is sort of an issue. These "reverse" discrepancies aren't useful for keeping track of outdated offline installer, but are also a kind of problem captured on this list.
In essence this sort of situation is caused by API visibility issues, since a newer version of the offline installer can't exist without a corresponding Galaxy build. It's just that the Galaxy API doesn't list that version of the build for one reason or another.
4. The versions are different, but their content is the same! I've checked!
Drop me a message here and I'll include a manual override in such cases. There's no way to automate these sort of things. The script generating this list only employs a glorified string comparison (with 100 exceptions and corner-cases, since we're on GOG after all).
5. Your list is outdated!
I plan to refresh it roughly once every two weeks (up to a month, when life gets otherwise hectic) so do expect stale data to creep especially into the more recent entries. The general goal here is to track long-time offenders, not to provide an always in-sync list of discrepancies.
Offline installers lagging a week or two behind their Galaxy builds are not all that surprising on GOG, but some lagging months (or even years) behind are indeed a problem.
https://airtable.com/shrldLsErlUf3eHqS
I've created this thread at (ø,ø)'s suggestion, so that people unaware of my API forensics thread can easily stumble upon it with a forum search and know that such a thing exists.
Now, for a bit of FAQ:
1. How are you generating this list?
I'm collecting a bunch of GOG API data on a daily basis, including offline installer versions and Galaxy build versions. I have a script that goes through the collected data and generates a list of mismatches, which I then validate and update on Airtable. None of it, with the exception of some manual overrides, deviates from what GOG's API reports.
If anyone is interested in how I do that precisely, the code is open source and available here.
2. You've listed a discrepancy that is actually solved by an offline patch included with the outdated installer!
These sort of situations are rather hard to track unfortunately, so (for the time being) I only check the main installer version for the comparison. Do let me know of such cases and I'll filter them manually.
3. Some entries have newer versions in their offline installers and older ones in Galaxy! What gives?
Usually GOG forgets to mark some Galaxy builds as public, which is sort of an issue. These "reverse" discrepancies aren't useful for keeping track of outdated offline installer, but are also a kind of problem captured on this list.
In essence this sort of situation is caused by API visibility issues, since a newer version of the offline installer can't exist without a corresponding Galaxy build. It's just that the Galaxy API doesn't list that version of the build for one reason or another.
4. The versions are different, but their content is the same! I've checked!
Drop me a message here and I'll include a manual override in such cases. There's no way to automate these sort of things. The script generating this list only employs a glorified string comparison (with 100 exceptions and corner-cases, since we're on GOG after all).
5. Your list is outdated!
I plan to refresh it roughly once every two weeks (up to a month, when life gets otherwise hectic) so do expect stale data to creep especially into the more recent entries. The general goal here is to track long-time offenders, not to provide an always in-sync list of discrepancies.
Offline installers lagging a week or two behind their Galaxy builds are not all that surprising on GOG, but some lagging months (or even years) behind are indeed a problem.
Post edited January 09, 2024 by WinterSnowfall