Upgrade page:
http://www.briggsoft.com/patches.htm
Changes:
Fixed a memory corruption bug caused by player disconnects. This is a critical fix, everyone should upgrade. This fix should also stop the TCPServerDisconnect errors found in the error logs.
Added "Auto check hands" option to Client Settings so that a non-response by a player will be treated as a check instead of a fold when no bet is present.
Hands played across midnight are no longer split across two hand history files.
Edit : 2012-02-01 --> There's a bug with the Data Folder setting that may cause you to lose your table, blacklist, and buddylist settings. I have taken down the 2.92 patch and will fix it today.
Poker Mavens 2.92 Released
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: Poker Mavens 2.92 Released
Has anyone documented a incident regarding the blinds when a player is eliminated during tournament play?
There is an issue where the application behavior is not following the actual game rules.
If a player is eliminated and they would be in the blind the next hand the bug can occurs.
For example lets say we have a full table of 10 players with player 1 on the button, player 2 in small blind and player 3 in big blind.
Situation 1 player 2 is eliminated during the hand described above.
The following hand player 3 has the button player 4 is in the small blind and player 5 is in the big blind.
This is not correct because player 4 got to go through an orbit without posting the big blind.
One correct solution would be to a dead button in seat 2 with player 3 in the small blind and player 4 in the big blind.
Situation 2 player 3 is eliminated during the hand described above.
The following hand player 2 has the button player 4 is in the small blind and player 5 is in the big blind.
This is not correct because player 4 got to go through an orbit without posting the big blind.
One correct solution would be to have player 4 be the big blind with no player in the small blind.
Situation 3 player 2 and player 3 is eliminated during the hand described above.
The following hand player 4 has the button player 5 is in the small blind and player 6 is in the big blind.
This is not correct because player 4 got to go through an orbit without posting both small blind and big blind.
Additionally player 5 didn't have to post the big blind during that orbit.
One correct solution would be to have player 4 be the big blind with no player in the small blind (the button would be in dead seat 2).
Following hand should have player 4 be the small blind with player 5 in the big small blind (the button would be in dead seat 3).
Situation 3 could also occur with more than 2 players being eliminated in same hand for example player 2, 3, 4, and 5 get knocked out in same hand and button moves to seat 6.
Thank you for the recent update.
Keep up the good work!
There is an issue where the application behavior is not following the actual game rules.
If a player is eliminated and they would be in the blind the next hand the bug can occurs.
For example lets say we have a full table of 10 players with player 1 on the button, player 2 in small blind and player 3 in big blind.
Situation 1 player 2 is eliminated during the hand described above.
The following hand player 3 has the button player 4 is in the small blind and player 5 is in the big blind.
This is not correct because player 4 got to go through an orbit without posting the big blind.
One correct solution would be to a dead button in seat 2 with player 3 in the small blind and player 4 in the big blind.
Situation 2 player 3 is eliminated during the hand described above.
The following hand player 2 has the button player 4 is in the small blind and player 5 is in the big blind.
This is not correct because player 4 got to go through an orbit without posting the big blind.
One correct solution would be to have player 4 be the big blind with no player in the small blind.
Situation 3 player 2 and player 3 is eliminated during the hand described above.
The following hand player 4 has the button player 5 is in the small blind and player 6 is in the big blind.
This is not correct because player 4 got to go through an orbit without posting both small blind and big blind.
Additionally player 5 didn't have to post the big blind during that orbit.
One correct solution would be to have player 4 be the big blind with no player in the small blind (the button would be in dead seat 2).
Following hand should have player 4 be the small blind with player 5 in the big small blind (the button would be in dead seat 3).
Situation 3 could also occur with more than 2 players being eliminated in same hand for example player 2, 3, 4, and 5 get knocked out in same hand and button moves to seat 6.
Thank you for the recent update.
Keep up the good work!
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: Poker Mavens 2.92 Released
Poker Mavens uses the "button always moves" method, same as PokerStars. See this thread for a full explanation:Nutzs wrote:Has anyone documented a incident regarding the blinds when a player is eliminated during tournament play?
There is an issue where the application behavior is not following the actual game rules.
http://www.briggsoft.com/forums/viewtop ... f=10&t=415
-
- Posts: 41
- Joined: Sat Feb 12, 2011 11:32 pm
Re: Poker Mavens 2.92 Released
Kent excellent upgrades.
Re: Poker Mavens 2.92 Released
Thanks for the reply. I understand the rule is working as designed. However, I can't agree it always it create a fair game.Kent Briggs wrote:
Poker Mavens uses the "button always moves" method, same as PokerStars. See this thread for a full explanation:
http://www.briggsoft.com/forums/viewtop ... f=10&t=415
Especially later in a tournament when blinds are high. This can be a real game changer and someone who might have been all in during the blind gets to wait 1 entire orbit.
I will accept it as working as designed and more on.
Thanks again.
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: Poker Mavens 2.92 Released
Someone will get an advantage either way. Either someone skips a blind or someone else gets the button twice in a row (or the equivalent if it lands in an empty seat) and gets to act last again. That's probably a bigger advantage.Nutzs wrote: Thanks for the reply. I understand the rule is working as designed. However, I can't agree it always it create a fair game.
-
- Posts: 41
- Joined: Sat Feb 12, 2011 11:32 pm
Re: Poker Mavens 2.92 Released
Hi Kent, the rake appe is very good, but the app no show properly the tournament and table separate, i have many hand files and the program show all hands in the ring games list, the rake calculation is perfect, the last year i built my own rake calculation based in The weighted contributed rake method (paid rake), what do you think about that? what is wrong in my hand files? i adjunt some files to you.
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: Poker Mavens 2.92 Released
My rake utility only works with English language files, including the names of the files. If it sees the name ending with " - Table x" then it assumes it to be a tournament. Yours all end with " - Mesa x" so it thinks those are ring games. They will get skipped during the scan process anyway. Whether or not your actual ring files get imported correctly will depend on the English key words it finds. Below is the actual parsing routine I use in Pascal (Delphi 2009):ddominguez wrote:Hi Kent, the rake appe is very good, but the app no show properly the tournament and table separate, i have many hand files and the program show all hands in the ring games list, the rake calculation is perfect, the last year i built my own rake calculation based in The weighted contributed rake method (paid rake), what do you think about that? what is wrong in my hand files? i adjunt some files to you.
Code: Select all
function TMainForm.ImportHH(HH: TStringList): integer;
var
i, j, p, Stage, DBHand, DBRake, DBDealt: integer;
s, DBTable, DBDate, DBTime, SQL: string;
DBShare: double;
Players: TStringList;
Stmt: TDISQLite3Statement;
begin
Result := 0;
Players := TStringList.Create;
Players.Sorted := True;
Players.Duplicates := dupIgnore;
DBHand := 0;
DBTable := '';
DBRake := 0;
Stage := 0;
for i := 0 to HH.Count - 1 do
begin
s := HH[i];
if Pos('Hand #', s) = 1 then
begin
p := Pos('-', s);
if p = 0 then Continue;
DBHand := StrToIntDef(Copy(s, 7, p - 7), 0);
if DBHand = 0 then Continue;
p := Pos(' - ', s);
if p > 0 then
begin
DBDate := Copy(s, p + 3, 10);
DBTime := Copy(s, p + 14, 8);
end else
begin
DBDate := '';
DBTime := '';
end;
DBTable := '';
DBRake := 0;
Players.Clear;
Stage := 1;
Continue;
end;
case Stage of
0: Continue;
1: if Pos('Game: ', s) = 1 then
begin
if Pos('+', s) > 0 then Break; // skip if tournament
Stage := 2;
end;
2: if Pos('Table: ', s) = 1 then
begin
DBTable := Copy(s, 8, 99);
Stage := 3;
end;
3: if Pos('** Deck **', s) = 1 then
begin
Stage := 0;
DBDealt := Players.Count;
if (DBRake = 0) or (DBDealt = 0) then Continue; // no rake if no flop
DBShare := DBRake / DBDealt;
SQL := 'REPLACE INTO Master (Hand, TableName, Date, Time, Rake, Dealt, Share) ' +
'VALUES(?, ?, ?, ?, ?, ?, ?);';
Stmt := RakeDatabase.Prepare16(SQL);
Stmt.Bind_Int(1, DBHand);
Stmt.Bind_Str16(2, DBTable);
Stmt.Bind_Str16(3, DBDate);
Stmt.Bind_Str16(4, DBTime);
Stmt.Bind_Int(5, DBRake);
Stmt.Bind_Int(6, DBDealt);
Stmt.Bind_Double(7, DBShare);
Stmt.Step;
Stmt.Free;
SQL := 'REPLACE INTO Detail (Hand, Player) VALUES(?, ?);';
Stmt := RakeDatabase.Prepare16(SQL);
for j := 0 to Players.Count - 1 do
begin
Stmt.Bind_Int(1, DBHand);
Stmt.Bind_Str16(2, Players[j]);
Stmt.StepAndReset;
end;
Stmt.Free;
Inc(Result);
end else
if Pos('Rake (', s) = 1 then // multiple rakes if side pots
begin
p := Pos(')', s);
DBRake := DBRake + StrToIntDef(Copy(s, 7, p - 7), 0);
end else
begin
if Pos('"', s) > 0 then Continue; // skip chat lines
p := Pos(' posts ', s);
if p = 0 then p := Pos(' has the dealer button', s);
if p = 0 then p := Pos(' checks', s);
if p = 0 then p := Pos(' calls ', s);
if p = 0 then p := Pos(' bets ', s);
if p = 0 then p := Pos(' raises ', s);
if p = 0 then p := Pos(' folds', s);
if p = 0 then p := Pos(' wins ', s);
if p = 0 then p := Pos(' refunded ', s);
if p > 1 then Players.Add(Copy(s, 1, p - 1));
end;
end;
end;
Players.Free;
end;
-
- Posts: 41
- Joined: Sat Feb 12, 2011 11:32 pm
Re: Poker Mavens 2.92 Released
Excellent Thanks Kent, very very good work.
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: Poker Mavens 2.92 Released
By the way, for those who didn't see my other post, the new rake reporting utility with instructions is available here:
http://www.briggsoft.com/docs/pmavens/U ... s.htm#rake
It now includes the screen shot images which I forgot to upload earlier.
http://www.briggsoft.com/docs/pmavens/U ... s.htm#rake
It now includes the screen shot images which I forgot to upload earlier.