[Stefan_O]

If you start a Teams Match with known friends,
it's very annoying that unknown players start requesting to sit immediately.

When I have tried, as soon as you create the table,
you get new requests from unknowns every few seconds that you need to click Reject or Ignore.

In the old webclient, you can fill in the player names before creating the table,
but if all players are not yet logged, it is still not possible to start the table.

In the new webclient, I don't even find a way to fill in any names before creating the table,
and unwelcome request from unknown people immediately start pouring in.

Very annoying.

Unless I have missed something in the current functionality (if so, please enlighten me! )
I do request a checkbox option when starting a Teams Match,
that ONLY PEOPLE I INVITE can sit.
When selecting this option, other players should NOT be able to request seating by their own initiative.

[manudude03]

That functionality is there. When you click Create Team Match, there is a tab at the top for Reserve Seats. The randoms will only be able to join the seats which are not reserved.

[Stefan_O]

manudude03, on 2020-April-12, 15:14, said:

That functionality is there. When you click Create Team Match, there is a tab at the top for Reserve Seats. The randoms will only be able to join the seats which are not reserved.

Aah, thanks for hint, manu.
Yes, I missed that, sorry

But still, if everyone is not online yet, it would still be very desirable to block others from requesting seats in these games.
Very annoying with those unwanted requests pouring in continuously.

[Stefan_O]

Another solution (perhaps easier to implement) would be,
just remove the requirement that people have to be online to be reserved.

Allow Reserve a set, even if the user isn't logged in, yet.

That would work almost as well.

[bascule]

Seems mightily strange that this feature has not been implemented before. Is it on similar sites. Do not the powers behind the scenes re development not have regular brainstorm sessions. Looks to me as if everything is reactive not proactive. Sad when one considers how many years has BBO been going. Glad I am retired and no longer in QA.

[mmbridge]

Stefan_O, on 2020-April-13, 02:06, said:

Aah, thanks for hint, manu.
Yes, I missed that, sorry

But still, if everyone is not online yet, it would still be very desirable to block others from requesting seats in these games.
Very annoying with those unwanted requests pouring in continuously.

I believe if you put the exact text +private+ in the Description field then your table will not be shown to random players looking to jump into a team game.

Try it and reply back here how it works for you.

[SelfGovern]

Stefan_O, on 2020-April-13, 02:12, said:

Another solution (perhaps easier to implement) would be,
just remove the requirement that people have to be online to be reserved.

Allow Reserve a set, even if the user isn't logged in, yet.

That would work almost as well.

I can tell you one problem with this solution: People are often not careful in their typing. I predict you'd have an avalanche of people who couldn't get in because their name was mistyped.
Oh well.

[sandiem]

We had a problem last night when one of our members did not get an accept button on her invitation, repeatedly. In the end I had to remove her name from the table and reject a couple of dozen requests to sit before she could get on. It was very annoying and anything to stop this would be great.

[paulg]

sandiem, on 2020-April-14, 04:49, said:

We had a problem last night when one of our members did not get an accept button on her invitation, repeatedly. In the end I had to remove her name from the table and reject a couple of dozen requests to sit before she could get on. It was very annoying and anything to stop this would be great.

Put +private+ in the description when you start the match. This will prevent the numerous unwanted requests.

Then invite your player (substitute her in).

[pescetom]

SelfGovern, on 2020-April-13, 19:38, said:

I can tell you one problem with this solution: People are often not careful in their typing. I predict you'd have an avalanche of people who couldn't get in because their name was mistyped.
Oh well.

It would be sufficient for the system to check that the nickname exists and warn if it is not in recent use or has never previously played with me or in an event I organised.
As bascule says, this is not Rocket Science, just common sense.

[sandiem]

paulg, on 2020-April-14, 05:16, said:

Put +private+ in the description when you start the match. This will prevent the numerous unwanted requests.

Then invite your player (substitute her in).

good to know. Thanks

[barmar]

pescetom, on 2020-April-14, 14:45, said:

It would be sufficient for the system to check that the nickname exists and warn if it is not in recent use or has never previously played with me or in an event I organised.
As bascule says, this is not Rocket Science, just common sense.

It almost certainly checks that the name exists, but not that it has logged in recently. But there are many similar names, so it's easy to type the wrong name and it will still be valid.

[pescetom]

barmar, on 2020-April-15, 18:37, said:

It almost certainly checks that the name exists, but not that it has logged in recently. But there are many similar names, so it's easy to type the wrong name and it will still be valid.

If I typed the wrong name, but it is in recent use and has played with me before and is not online, then I will face the consequences. Much prefer that to having to oblige everyone to be online at the moment of creation.