[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4783: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3888)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4785: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3888)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4786: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3888)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4787: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3888)
AK top two in limped family pot $200 5-max - Live Poker Forums

Advanced search

AK top two in limped family pot $200 5-max

Hand analysis. Post your trouble hands here

Moderators: iceman5, LPF Police Department

Postby Zmej » Fri Dec 15, 2006 8:35 am

To Ice:
IMO even if poster asks only a question on a final street, a better advice is the one that considers the play on all streets. Lots of hands can be very tough to play postflop without a proper preflop play,or a real mistake of the poster could be made on an earlier street.

Here IMO postflop is standard, and I think that a bet in the end is very stndard too. OP is short and Ax makes a great part of his range, so pushing is better. What is much less standard is preflop. That's why I concentrated on it more. I agree that occasionally one can limp with AK, I guess one could consider limping with AA from time to time, to mix it up. But IMO a stndard line with AK is to raise, and being standard it means that one raises it like 90% of time. From Electrolux post, I had the impression (and from his stats too) that he rarely raises AK from the blinds. I think that it is a big leak, that's why I concentrated on it.



To add a bit to discussion of limping vs raising AK preflop.
First, it is simply theoretically correct, AKo will often be the best hand preflop and we want to put money in when we are ahead.

Second, AKo plays much better in HU pots, rather than multiway. If you are HU and flop TPTK it is very rarely that someone outflops you, so in HU pot you are mostly good. In multiway pots TPTK becomes marginal OOP. Moreover after raising preflop and taking the flop HU you are very likely to take it with a CB. If flops comes [2h] [8c] [Qc] one should make a CB in HU pot rather often, and one will take it a very large % of time.

And finally, let's consider a situation when CO limps, Button limps with 97o, and you have AKo in BB.
We will look at this with Button vs BB perspective, ignoring CO for simplicity. (I choose this one because I could find myself on both sides and it is interesting for anlysis.)

A. Raise preflop.
Now, If you raise preflop a likely outcome is that CO folds, Button folds and you take the pot, which is great. If Button decides to call he will make a major preflop mistake that will be difficult to repair postflop. BB needs one card A or K to make a strong hand, while Button needs 2. I mean that for BB the problematic flops are 77K, 79K, 86A. While on most of the flops that hit both like K95, or hit no one Q83 BB is not in trouble and will take it with a CB or if Button decides to float with a middle pair BB wins even more.There is of course some room for postflop play, I even think that against against aggresive Button who will raise or float with middle pair it is ok to go broke on K97 flops, because the times BB takes a large chunk of Button stack when Button will float K96 flops will compensate for the loss.

B. Limp (check) preflop.
Here Button made a slight preflop mistake by calling, IMO it is not even a mistake and I would make such a limp a lot. Now, postflop I would prefer to be in Button shoes, as Button is very unlikely to lose a big pot, while BB can.
Situation changed, in a limped pot Button plays correct if he just waits to hit the flop big i.e. K97, K86 flops, and folds when he doesn't hit. Moreover for BB now the hard times came, let say the flop is K97 or K86 BB bets , Button raises. BB folds? If BB calls does he fold to a second barrel? Moreover There are tricky flops like KT6, BB bets, and Button could call here with just a gutshot. (Yes, I do such calls against a right OP. Preferrably a tight one.) If turn comes an 8, there is no way BB would see this coming. (Making comparison with a raised pot, Button wouldn't have correct implied odds to call on the same flop, due to the different pot to stack ratio.) In all the other cases Button could just fold if BB leads, or try to steal the pot if everyone checks to him.

So from this (incomplete, of course) comparison we see that if BB doesn't raise then Button played correctly, while if BB(SB) raises Button made a mistake in the hand. (By limping preflop or calling a raise.) Raising is +EV for BB. Limping is +EV for Button.
"#3 pencils and quadrille pads."
- Seymoure Cray (1925-1996) when asked what CAD tools he used to design the Cray I supercomputer; he also recommended using the back side of the pages so that the grid lines were not so dominant.

"Interesting - I use a Mac to help me design the next Cray."
- Seymoure Cray (1925-1996) when he was told that Apple Inc. had recently bought a Cray supercomputer to help them design the next Mac.
User avatar
Zmej
 
Posts: 2307
Joined: Wed Mar 29, 2006 5:44 am
Location: France. (Russian origin.)

Previous

Return to No Limit Hold'em Cash Games

Who is online

Users browsing this forum: No registered users and 36 guests

cron