pangea-poker icon indicating copy to clipboard operation
pangea-poker copied to clipboard

A backend response for Table Selection is needed

Open norbertdragan opened this issue 5 years ago • 3 comments

@sg777#2257 there are two missing pieces for the Table Select feature to work:

1. The ability to check how many people are currently at the table before joining the table This is important to know to which table the user can join to when she picks from the list. (https://share.getcloudapp.com/NQuv1qkg).

2. A way for the player node to know where the other players are sitting at the table When the player joins the table, before sitting down to an available seat, we must update the GUI with all the other players currently sitting at the table. This way the player can know which seats are free and we can seat the player there.

A potential solution may be for both of the above is to have a method (eg. game) that responds from the dcv (or even from the player) with the following info:

  • number of seats available at the table
  • number of players currently at the table
  • small blind/big blind
  • game type
  • which seats are occupied and which are empty

norbertdragan avatar Dec 19 '19 13:12 norbertdragan

@sg777 can you please clarify how the new status_info messages are addressing point 1. and 2. in the issue description above? Thank you!

norbertdragan avatar Jan 27 '20 04:01 norbertdragan

@sg777 can I get an update on this one? This is necessary for the multiplayer to work properly. Is there a method doing this already?

I think receiving something like

{
    method: tableInfo,
    players: [playerId] 
    blind: small/big
    game type
}

players: [playerId] - I plan to read which sears are empty and which are occupied from this, so the player ids should be the seat number ids not the backend rand strings.

piggydoughnut avatar Jun 05 '20 20:06 piggydoughnut

Since players need to know about the updates at the table, we need to receive tableInfo (with the current players seating ) when something happens (player disconnect, etc).

Could do it in two ways:

  1. It can be sent with every message users receives.
  2. It is triggered on certain events affecinig the seating.

I imagine first one is easier and quicker to implement, so I think it will suffice for now.

piggydoughnut avatar Jun 05 '20 21:06 piggydoughnut