Quote:
Originally Posted by Spanishmoon
The failure to cbet here against a skilled V is the essential problem here. Once H caps himself oop, he invites all manner of trickery on subsequent streets.
AP: I think JJ is in my minimum defense range here against a thinking pro who may well interpret our passivity as Ak/Aq. With all respect, H’s preoccupation with the Jd blocker avoids the essential questions in this hand in search of minutiae to justify a suboptimal line.
How would we play AA here? Hero agrees he’s capped his range and justifies his subsequent line based on this fact but this fact is the source of his problem!
I'd have to double check as I'm a bit rusty with solver-work but I think this board is one we have to use a larger sizing on when betting, and in general have a lower c-betting frequency since it connects better with the calling ranges than our opening range. So what hands would you put into your x/c range to defend it if you're cbetting all your overpairs on this flop?
44-55 would probably prefer to be cbetting for protection/ it blocks villains floating range and can barrel certain turns, 66-77 can't really x/c more than 2 streets on most runouts, and 88-99 would probably need more protection/ would get value from similar hands so I'd prefer cbetting these over tt-jj (hands which wouldn't get 3 streets of value anyways), and use qq-aa to get 3 streets (on the more dry runouts).
I'm not saying this strategy is right but what would be a better one? If we bet here, v calls and turn comes the same we x/c, river we x and we're faced with same predicament
If we're just bombing this board with all overpairs that would mean we'd have to do same with all flush draws, most bdfd's as well I'm guessing. Both lines which I'd assume are far from optimal.
Another thing to mention here is given the rake in this game I have maybe 1 or 2 combos of 22-33 and 3 combos of 88. So we're put in a spot where we're facing 2 opponents who both would probably each have all 9 combos of these hands.
Last edited by GrindBox; 06-27-2019 at 11:18 AM.