Board Game Arena

System has been virtually unusable. I play hearts a lot, and there's so many breaks in play, plays get reversed, weird animations, it's just strange. Please fix this ASAP.

Trociu wrote:Really strange things happen i.e. in 6. Nimmt! I sometimes see the next turn! Cards are played, but when i press F5 it appears that everyone is waiting for me to play the card, but now I know which cards they have chosen.

That is the same exact thing that happens to me! I see like the future, and then when I reload the page, it brings me back to the normal game.

It's hard to play this 4 last days. I should use F5 very often during all my games. Today, I was waiting for my oppoment in a Can't stop party, and the computer tells me, I was out of time, and I could'nt do anything, except leave the game. So,I get a penalty.
I hope you'll fix it soon.
Thanks for your excellent job and all this games

Stéphane

all games seem to be almost unplayable and it is getting worse last days, please do something

You can see your future roll in Can't Stop as well and then hit F5 and go back to your turn before the roll. I've thrown all three "Not Possible", hit F5, and gone back to before the roll and then hit stop instead.

Don't want to pile on, but I will anyway.

May I suggest though, that instead of keeping the website up with very drastic server problems that make most games near impossible to play without pressing F5 virtually every turn--take the site down for 24 hours or whatever is necessary to get the issue(s) FIXED. And then put the site back up when it actually works.

Thanks.

Hearts has been virtually unplayable for the last week. It is so annoying to have to hit F5 constantly and still someone always seems to time out eventually. Please get this fixed. Would be better if you take the system down completely until you get it resolved.

Hi,

As you may have noticed, we manage to fix the issue temporarily on July 28th.

The problem got back on August 5th (with a maximum on August 12th).

Then we manage to set up an "almost permanent" fix. Since August 13th, there is very few errors of this type. As there hasn't been additional comments on this thread since August 12th it looks like we found the cause.

We are working on a last fix to clean the latest remaining "timeout" errors.

Thanks for your patience.