batankyu2:
It is very probable that the number of seats at the table are parametrable
when you see how the client/server protocol is implemented.
At the beginning of each hands, the server sends to clients a line of text
beginnning by @$ like this one (from Treasure Trap):
@$Holdem NL 100;1;100;25;50;0.25;3;1;The Free Poker Room;4;1111111111 ; ;false;0;0;50;100;0
* "Holdem NL 100" is the top-left corner title (replaced by tourney number for * tourneys)
* 1;100 are the min and max buy-in (irrelevant for tourneys)
* 25;50;0.25 are the current small, big blinds, and bet granularity
* 3 is the bet structure (0=Fixed, 1=Spread, 2=Pot limit, 3= No limit)
* 1 says the table is a tourney (0 is for ring game)
* "The Free Poker Room" is the title printed on felt
* 4 is the seat number where the button is
* "1111111111" is the seat mask and is what is important here
* 50;100 are blinds for next level
* other infos are yet unknown (seems always false and 0;0)
The seat mask is a string of ten bits, where a 1 stands for
"there is a seat at this postion" and 0 stands for "there is no seat at this position"
(the corresponding seat is hence "masked").
All our tables have mask "111111111", so we have always ten seats,
... except for the stud table, where you see new hands announced by lines like:
@$Holdem NL 100;500;1000;5;10;0.25;3;0;The Free Poker Room;10;1011101110; ;false;0;0;10;20;0
As you can see, the seat mask is "1011101110" for stud,
and this is why seats #2, #6 and #10 are missing
(they have a zero bit in the seat mask and hence they are masked).
So, the presence of this mask tells me that there necessarily is a way
to configure the tables with the the desired number of seats.
Page 1 of 2: 2 »» 