![]() |
#21
|
|||
|
|||
![]()
bluff, please do explain.
|
#22
|
|||
|
|||
![]()
interesting hand sim
less interesting Thats just in terms of general pot equity. Ye mighty denizens of hsnl can do with it what you want. pjn |
#23
|
|||
|
|||
![]()
KQQJ had the absolute worst case scenario come up when the hand was finished. I think we can agree that both AA hands are telegraphed to him at the point where he has his big decision. Now if you weigh the odds of what suits the aces hands are playing with, taking into account how he's holding 2 each of the suit he doesn't want them to have, and average his equity over all possible suits they COULD have, it is definately a +EV play and seems standard to me.
|
#24
|
|||
|
|||
![]()
im more interested in the 13k call than the second call. i think it is more likely that this call was incorrect than the other.
|
#25
|
|||
|
|||
![]()
i think arbiannight lost his roll(onftp) 200k+ to durr today. he got whipped big time
|
#26
|
|||
|
|||
![]()
a guy used to play 5/10 w/ that nick and he was kind of average.
|
#27
|
|||
|
|||
![]()
yea, i remember him from when 5/10 opened on party. He was pretty good, just really nitty.
|
#28
|
|||
|
|||
![]()
[ QUOTE ]
is someone here arabiannight? this guy is playing these stakes? wow. [/ QUOTE ] IIRC he's been at similar stakes for a wihle now edit: The UB player, i mean. I dont know the party player w/ same nick |
#29
|
|||
|
|||
![]()
bluffthis you must be really bad at omaha. KKQJ played the hand fine. folding at any point is 100% mathematically incorrect.
|
#30
|
|||
|
|||
![]()
[ QUOTE ]
folding at any point is 100% mathematically incorrect. [/ QUOTE ] Then by all means enlighten me with a proof of that assertion. Indeed you will be the first since all others who hold your position have yet to offer any. Note that the decision point in question is the call of the 3rd raise to 13K after previously calling two much smaller raises. Presumably you won't be so dim as to maintain that calling to 13K is correct because he would then be pot odds stuck where he would be correct in calling for the rest of his stack (which I said was true as to calling the last raise given that he had wrongly called the 3rd raise). |
![]() |
|
|