It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like:Chrome,Firefox,Internet Explorer orOpera

×
arrow-down2arrowcart2close4fat-arrow-leftfat-arrow-rightfeedbackfriends2happy-facelogo-gognotificationnotifications-emptyownedremove-menusad-facesearch2wishlist-menuwishlisted2own_thingsheartstartick
Hi everyone,

I just wanted to say that we will have this looked into Monday morning. I know that this doesn't help to ease the mood but it is the weekend right now, so please bear with us and we'll do what we can to fix this problem as quickly as possible.

So, in short, we are quite aware of this issue. Also, sorry for not saying anything earlier but I was in the process of verifying this myself.

On behalf of GOG.com, I just want to say sorry about this, guys.
avatar
JudasIscariot: Hi everyone,

I just wanted to say that we will have this looked into Monday morning. I know that this doesn't help to ease the mood but it is the weekend right now, so please bear with us and we'll do what we can to fix this problem as quickly as possible.

So, in short, we are quite aware of this issue. Also, sorry for not saying anything earlier but I was in the process of verifying this myself.

On behalf of GOG.com, I just want to say sorry about this, guys.
avatar
vohk: That is.. incredibly disappointing. I see two possibilities here:

1. The GOG version was recently patched, updated, or otherwise changed, which would be inexcusably foolish to do when staff are unavailable to put out fires (re: during a promotion and before a weekend)

2. Gremlins/Murphy's Law

In either case, does GOG not have a system in place to just fire off a rollback? This really doesn't seem like the kind of issue that should be simmering over a weekend.
Like I said before, we will get this issue fixed ASAP, it's just going to take some time. I am sorry but I can't do anything at this time to solve this on my own and I really wish I could :(