How about an option to not allow auto-joiners to a created table?

[Rex Goodheart]

I would say that at least half the tables I "Create" for 7 Wonders end up having to be cancelled, and then a new table must be created. I understand that 7 Wonders is popular, and many people want to play, but a lot of those people don't show up to the table when they're automatically assigned to a newly created table, and they cause the other live people to sit there and wait.

It typically goes like this:

- Create a table
- Several people join
- Admin presses Start game, and then waits for others to hit "Accept"
- One of the joiners fails to hit Accept
- Admin decides he/she has waited too long, so presses "Cancel game start"
- Instead of reverting back to the table, the table is obliterated, and a new table must be "Create"d

If the system goes back to the table, instead of wiping it out, the Admin could simply expel the player who failed to Accept.

Thank you.

[aesche]

Hmm, that‘s usually what happens, at least if I recall correctly from the games I play (not 7 Wonders). Blocking auto-joiners can‘t really be the option imho.

[Rex Goodheart]

Opting to not allow auto-joiners would be one option for a fix, and was presented here because the first suggestion went unheeded.

The big cause of a problem is that they just sit there at the table and don't "Accept", and when the Admin is finally forced to "Cancel game start" the entire table gets wiped out, and a new one has to be created.

The better fix would be "Cancel game start" returns back to the join table screen, where the Admin can then expel the offending auto-joiner. Instead, the entire table gets obliterated.

[Meeplelowda]

The better fix would be "Cancel game start" returns back to the join table screen, where the Admin can then expel the offending auto-joiner.

This would be a great option.

[Jellby]

In my experience (mostly with Hanabi), that's usually what happens: you cancel game start and are sent back to the lobby, but the table is still open.

What I sometimes see is that when a game start is cancelled, the player who didn't accept in time immediately disappears, and obviously no one had time to kick them out or they to quit. It's as if the player was offline, but the "table" didn't realize until you try to start the game and cancel. If it's a two player game (or if that happens to every other player), you end up with an empty table, or maybe just you. It could be that if this happens to the table owner, the table is just wiped out when the game start is cancelled.

[Rex Goodheart]

Revisiting this thread because the problem hasn't been fixed.

If one player at the table doesn't press ACCEPT, preventing the game from proceeding, when the Administrator presses "Cancel game start" the table is obliterated instead of reverting back to the join screen for that table. A new table must be created, losing all the previous players. It's quite frustrating.