Broken game

Hi,

Unfortunately I have a broken game. I started several matches against a bot, the games with the numbers 1436872 to xxxxx76, but after approx. 50 moves I got this error message:

http://www.littlegolem.net/jsp/game/game.jsp?gid=1436872

Now, this game is not in my 'List of games' anymore in my profile:

http://www.littlegolem.net/jsp/info/player_game_list.jsp?gtid=einstein&plid=12075

...but it is still the next of "Your games" in which I should do the next move, but I always get this error message only after clicking, I can't do any move.

Can anyone help? It is a bit annoying to click on any other game in my list, where I have to make a move and then to get always this error message afterwards because the 'next game' is broken or even not existing anymore...

It looks like a bug in LG.

or my fault, perhaps, my bot sent a move that is not allowed. But I can't find out anymore what happened because the game is away..

It's the server's duty to not allow illegal moves. Perhaps your bot found a bug. Send a message to the Webmaster.

YHW, don't worry, it will soon run out of time and you lose it, and then it's gone.

It will use up all your vacation first, however... ;-) not sure why I find this funny.

that's what makes me care...

I also have a broken game. It is in my list of games, but I always get an OutOfBoundsException error when I try to view it: http://www.littlegolem.net/jsp/game/game.jsp?gid=1432273

Unfortunately, that's also a game against one of my bot instances. But these programs are playing automatically all the time for months without causing problems.

I had the feeling yesterday morning that something happened to the server and I don't know if 2 different instances of my bot sent coincidentally their moves in that moment and that's the reason for the broken games or the server problem was caused by them. OneStone stopped also playing at this time, perhaps because of a server problem or maybe killed my programs also that bot with another broken game...please tell me someone that it was just a server problem. ;)