Darling, you'll notice AI does not (is not able to) trade resource cards for development cards. About 4 weeks ago this was not the case, but I noticed that the game would lock up when the dev card deck would be empty (late in game when they were all taken) and it would always do this when it was an AI player's turn. The update came out fixed this... but AI players could not trade for a card. I think the AI strategy does not realize this and some how it prioritizes getting a dev card, but the bug in the code makes that impossible, so the AI player hangs until it times out and then ends its turn. If no dice value of 7 occurs for many turns, then the AI player's strategy can be stuck on get a dev card and they will acculate cards until either a 7 occurs or someone takes a card from them. I've seen them have over 50 cards! Anyways long and short of it is that the developers are having a terrible time sorting out all the bugs and AI player is currently useless.
Uncaught RangeError: Maximum call stack size exceeded. Dont know what that all means. But i cant play anymore again. Trying to play through google chrome on Mac.
@jho Thanks for your report. You can either upload a screenshot to a filehoster of your choice and share the link here in the forums or send it direclty to us via firstname.lastname@example.org. Please also include the link to this thread in your e-mail.
Ore for Wool has also this problem in the multiplayer game (windows client) on the red player. Yellow player ends turn but red player does not receive dice. By cutting internet connection and coming back sometimes works if the red player does it. But it happened so many times that I do not play this scenario anymore.
This has also happened to me on a couple of occasions, the most recent being today.
Always in multiplayer mode.
I was first and placed my village and road.
I observed the arrow above my player/avatar moved to the next player.
All other players still saw it was my turn and were wondering what I was doing.
After some time and chatting we all concluded this was a bug and quit.