Automatic table creation: bug or intended

[DrKarotte]

I usually use manual table setups, and I have just started to play Arena games with Season 1.

Now I have experienced some strange behaviour. Yestersay I set up several games. In some games the site automatically generated new tables after the game started (these were 2 player games). Additionally, there was one in Bombay, where no one had joined when I went to bed. Bombay is a 4 player game. Today I could see 3 Bombay tables in my list, two of them had one opponent, the third was empty apart from me. Apparently the interface sets up another table automatically after one person has joined. I do not think that this is intended. If so, how can I prevent this? I don't want to play several tables of the same game at the same time. I don't think that tiis happend in all games, so it may indeed be a bug.

That the other player in Bombay didn't fill up the first table may be related to restrictions in his settings.

This may be related to this error which I received several times: Unexpected error: mysql_deadlock_restart_transaction
This popped up in the game setup screen and seems to stop the matchmaking process in a game (at least the green bar disappeared).

[Een]

The general principle of the matchmaking is that you have 3 time profiles in your options (your favourite, an intermediate, and a least favourite).

So unless the table options are completely identical, it's normal. The system is just trying to set up a new table after a while because it hasn't been able to find enough opponents to start the game at the first table with your favourite options.

There can be a max of 3 tables created like this for one user, and of course, not all of the tables will start. When a game starts, you automatically quit the other tables, so you won't be in 3 games.

But actually, when using automatic, it's not meant to spend time checking on created tables

[DrKarotte]

Thanks for the clarification
Seems like I have been away from playing too long

[DrKarotte]

But actually, when using automatic, it's not meant to spend time checking on created tables

I have noticed that accidentally