The Good News™ is that this will Soon™ be fixed.

This game came out less than a month ago. There have been several rounds of "voting/resetting"

I'm no programmer, but I just found such occurrence odd for a mere database maintenance/update/whatever issue. In our day and age, a forefront website such as GOG is very unlikely to have such a basic flaw happening just randomly - imagine if that thing happened to their sale department... It's not the end of the world but I also find strange that no one at GOG is willing to say something about it if it is such a common thing. Not willing to see evil where it isn't, but again - transparency? This *does* effectively impact the sale buzz on games.
Yep, convincing possibility.

I wouldn't be so sure. Here on the forums i see threads that have replies within the last few minutes, but it says i've read it. Obviously wrong.

Maybe two games somehow share the same numbers. Maybe there's a connectivity issue between different databases. Maybe it's a badly formed SQL request that involves a ' or " somewhere and it throws errors. Maybe it's a hard drive CRC failure in certain sectors. Maybe there's timeout issues. Maybe there's encoding issues. Maybe it's an AJAX (on the fly updating on the page) issues. If it relies on Google's API then maybe it's something with their scripts and not GoG at all. Maybe the JS is old on those pages and it's trying to load old data or use old API's and is crashing...

I don't know. In programming it's said every 10 lines has a bug. And 99% of errors aren't looked for or handled correctly. So it's VERY likely issues have cropped up.

Not true. We know it takes three licks to get to the center of a tootsie roll pop.

I don't know if Mr Owl is a reliable source of wisdom in this case.

One wonders actually how certain games manage to be almost not buggy at all. Respect to devs.

That being said, sometimes flaws *are* willingly introduced, without having to brand conspiracy theory. 99% chances you are correct, but that post teased a bit the remaining 1%.

Owls are the definition of wisdom! Or essence. Or metaphor or something... they get like +8 to wisdom!

Let's take a simple example. Let's say i want to open a file. So i would do something like:

[code]
FILE *FP = fopen("somefile.txt", "rob");
if (!FP) {

}

char buffer[1024] = fread()...
[/code]

Tell me, how many different errors am i looking for?

There's possibly 20 or more reasons why the file wouldn't open... Now assuming that, let's resume

[code]
int len;
while ((len=fread(buffer, 1024,1,FP))!=0) {
...
}
[/code]

What errors am i looking for in this loop? (these actually happen a lot)

Sorry I'd have to call Mary Poppins on this one.

For the little programming that I do in this one language that I use, I do know however that my number one enemy is parentheses. Man, you're all good!

Well i'll tell you in the loop. I'm not looking for an error, i'm looking for a return of 0 length, which is the assumption it's the end of the file, but i could also get 0 when there's an error, and i'm not checking ERRNO... which is where the actual error code is stored in which to check..

In C++ or other languages there is try/catch, but those generally are treated the same way, either 1-2 specific errors or any error and then you close it down because it's getting too complex to actually handle all possibilities.