UhuruNUru: Yet in all that two years, what's the dev actually done about it?
Released ~26 updates that never made it to GOG, but are available for anonymous download from the developers' AWS-leased web server. For users who accept the default-enabled automatic update mechanism, the game (supposedly) can update itself with nothing more than an Are-you-sure confirmation from the user.
UhuruNUru: Simple fact is, it's the devs responsibility to update all versions of their game, wherever they sold them.
If they "send" an update, and game fails to update on GOG, the dev needs to find out why.
Not shrug their shoulders, and ignore it.
I am not familiar with GOG's developer-facing portals. Are you saying that the developer has an easy way to detect that GOG is out of date? It's not particularly easy for customers to see; it's impossible for anonymous users reading the GOG store page to see. If the developers don't have their game listed in a GOG account, they can't check the version that way, so either GOG has a developer-facing portal that shows it to them or they simply cannot see it at all and must rely on user feedback. That is part of what I mentioned above: provide a transparency mechanism so users can see whether the developers have done anything at all to provide updates.
UhuruNUru: Over 2 years of inactivitty, suggests it's the dev that doesn't give a damn, and I wouldn't be surprised if the update was never semt.
The developer has been very responsive to the community and released numerous patches (most of them beta patches, but some full formal releases too). Per the link in my prior post, GOG elected to stop updating the game because there were more beta patches released than GOG cared to handle.
UhuruNUru: This is such an example, update was sent to a testing channel, only dev can access.
Misunderstanding was quickly sorted out, and the patch released.
Sorted out after someone who had no access to see this complained publicly, prompting an investigation.
UhuruNUru: Since Galaxy came out, it's easier than ever for a dev to provide updates on GOG.
GOG's only responsible for packaging the offline installers, once they have the update on the Galaxy release channel.
Please don't act like Galaxy is actually useful for this.
UhuruNUru: Providing the update is always the devs responsibilty, and simply saying we sent one, doesn't change it.
Even if the dev did send one, as in this game, it has to be sent on the release channel, to be added automatically.
Sure, and with increased transparency as I described above, we'd have a better idea of what happened in cases like this:
- Developer didn't send it at all. Maybe they said they sent it because
they misremembered, or they don't want to admit not sending it.
- Developer thought they sent it, but it was orphaned in the update
system or otherwise dropped, so nobody on the GOG side even knew to
look at it.
- Developer sent it properly and GOG is sitting on it due to lack of
employee time to package the patch.
- Developer sent it properly, GOG is aware of it, and is sitting on it
due to quality control / policy issues.