Xeshra: Seems it is "hitting me hard" here, because i got those games. Do you think it is realistic just to make a community patch using the Steam data added for some of those games? It depends on how a patch is made because if it goes very deep on the engine then it is nearly impossible without knowing the source code. "Unless the game is reverse engineered"°°, which is a huge work... not realistic on almost any mod, and of course the legality is another issue.
For, almost, certain: The devs seems to have either low interest or low capability sufficiently supporting the GOG build, which is in many terms almost equal to the Steam build.
°°Would be 1000 times lesser work just to "break apart" the DRM of Steam and then it is basically a non legal "alternate GOG version", as it is how we would like the game to be served.
Anyway, yes, the devs/publishers are acting very different toward GOG. Some of them are updating their GOG games like crazy and apparently got no issues doing it and others are simply not moving a small finger for whatever reason.
Oh, besides, i am not sure it is true with the "lack of update" of Vampire The Masquerade Bloodline because the issue is that the newest patch is NOT having a OWN version number. It kinda has been added to GOG with the same version number, although it is a different build, making it hard to pin down on what you actually have.
Not the only game with this difficult patch policy... i got comparable issues on Baldurs Gate 3 for example with 3 different builds which all got the same version number, so without checking the filesize it is impossible to tell the difference.
How i had to solve the issue can be seen on the picture. So basically "comparable builds" are Version related Legacy files with the same "surface" ID such as the current build.
If it is the version of the "actual build" is is tagged as "V1" and so on... instead of "1" and further. If there is a new version at some point it will simply be named "1 V.1"... the first number pointing at the same build with a "variation". An actual build does not have a number, but can have a version.
Another issue: BG3 V.2 is according to SHA 256 (this is a very high grade redundancy, impossible to have the same hash on different files) the exact same file, so i dunno why GOG was marking it as "updated"; it is just a mess for certain game files.
: the third entry as visual novels in Vampire the Masquerade world.
For Tangledeep : sooner or later i believe the game will be updated. .... but when ?? that is the question ...
The most problematic of the three is Edge of Eternity : iirc the team is composed of 5 persons...
A mail address (don't remember if it's still working though) : contact@midgar-studio.com (i believe i sent a mail but no answer since 8/9 months)
And a Discord link (i don't use Discord and an account is required after the captcha) :
As GOG and the version number: it's just a pity .... they simply should use the build number of a game instead so many different naming versions ...
