Auto-reserving seat

[1eyedjack]

I wish raise the problem of a player losing connection with a table, otherwise than in a paid tournament.

 

The problem being a lack of control over who occupies that seat.

 

In a paid tournament, the seat is auto-reserved for the player who lost connection.

 

But in a main/club table that option is not available to table host.

 

The best that you can achieve is for host to set the flag "permission required to sit". As a workaround this is almost playable, but is less than ideal for several reasons:

1) You might not want to insist on permission in other circumstances

2) As host you may get bombarded with unwanted requests to sit by random humans other than the individual returning from having been booted.

3) As the returning disconnected player, you do not get auto-reseated

4) As the returning disconnected player, you do not even get an invitation to rejoin the table

5) As the returning disconnected player, you can rejoin the table, but depending on the method of joining you may get to see all 4 hands before sitting.

 

 

 

 

 

[Bbradley62]

Couldn't quite wait a year for a response, huh? B-)

http://www.bridgebase.com/forums/topic/62838-autoreserve-seat-in-mbc/

[1eyedjack]

Couldn't quite wait a year for a response, huh? B-)

http://www.bridgebas...ve-seat-in-mbc/

 

Damn! you have a better memory than me.

[barmar]

I think the assumption behind the current design is that if you want to play with specific players, you'll reserve their seats when you create the table. If you don't, you're playing with randoms, and when a player leaves (for whatever reason) you're willing to take the next one who comes along.

[1eyedjack]

I think the assumption behind the current design is that if you want to play with specific players, you'll reserve their seats when you create the table. If you don't, you're playing with randoms, and when a player leaves (for whatever reason) you're willing to take the next one who comes along.

 

OK I am being lazy here, as I am at work and cannot instantly check it, but are you saying that if a seat is reserved for a player at the outset, then that reservations "sticks" to the seat if the player subsequently loses connection?

 

That would be useful to know.

[Bbradley62]

OK I am being lazy here, as I am at work and cannot instantly check it, but are you saying that if a seat is reserved for a player at the outset, then that reservations "sticks" to the seat if the player subsequently loses connection?

 

That would be useful to know.

And, if my table is not initially set up that way, and it happens that I end up with a good foursome that I'd like to keep, can I retroactively reserve their seats to protect against disconnections?

[barmar]

OK I am being lazy here, as I am at work and cannot instantly check it, but are you saying that if a seat is reserved for a player at the outset, then that reservations "sticks" to the seat if the player subsequently loses connection?

Yes. Reserved seats stay reserved until you release them.

And, if my table is not initially set up that way, and it happens that I end up with a good foursome that I'd like to keep, can I retroactively reserve their seats to protect against disconnections?

I think you can do this by clicking on Table to change the settings, but I'm not sure.