next AA
$0.50/$1.00 UTG+1 ($29.08) 15/5/oo (nfinite) - 20 hands UTG+2 ($46.00) (Hero) CO ($17.25) Very bad player, play very loose and often go to SH with small pair even if see much action Preflop: Hero is UTG+2 with A[img]/images/graemlins/heart.gif[/img], A[img]/images/graemlins/spade.gif[/img] <font color="#CC3333">UTG+1 raises</font>, <font color="#CC3333">Hero raises</font>, <font color="#666666">3 folds</font>, CO calls, <font color="#666666">3 folds</font>, <font color="#CC3333">UTG+1 raises</font>, Hero calls, CO calls, Flop: 6[img]/images/graemlins/club.gif[/img], Q[img]/images/graemlins/spade.gif[/img], T[img]/images/graemlins/spade.gif[/img] ( 6.75BB ) <font color="#CC3333">UTG+1 bets</font>, <font color="#CC3333">Hero raises</font>, CO calls, <font color="#CC3333">UTG+1 raises</font>, <font color="#CC3333">Hero raises</font>, CO calls, UTG+1 calls, Turn: 8[img]/images/graemlins/club.gif[/img] ( 12.75BB ) <font color="#CC3333">UTG+1 bets</font>, <font color="#CC3333">Hero raises</font>, <font color="#666666">1 folds</font>, <font color="#CC3333">UTG+1 raises</font>, Hero calls, Raise to protect my hand (and mayby value) or just call down? River: 9[img]/images/graemlins/diamond.gif[/img] ( 18.75BB ) <font color="#CC3333">UTG+1 bets</font>, Hero calls, Final Pot: 19.75BB |
Re: next AA
I'm not capping this flop, and I'm calling down after that.
The thought of pocket queens is making me nauseous... [img]/images/graemlins/crazy.gif[/img] |
Re: next AA
I think capping the flop is fine, but when villain leads out on turn after cap I would check call.
|
Re: next AA
[ QUOTE ]
I'm not capping this flop, and I'm calling down after that. The thought of pocket queens is making me nauseous... [img]/images/graemlins/crazy.gif[/img] [/ QUOTE ] Yep, Me too.. [img]/images/graemlins/laugh.gif[/img] Call the 2nd raise on the flop, then call down the rest of the way if u think you've got a chance your ahead. He raised and reraised in early position and is representing a monster. Not a great flop for u. |
Re: next AA
[ QUOTE ]
Raise to protect my hand (and mayby value) or just call down? [/ QUOTE ] in hands like this it is okay to keep the badplayer in CO in the pot when your main concern is the 'other guy'. If he has a decent (or even a suprisingly crappy) draw he wont probbably wont fold the turn and you risk getting totally pwned by UTGs 3 bet. btw probably you'd get less bias in responses if you cut the action of at what you perceive to be the key decision point. |
Re: next AA
Cap flop, call down after he leads again on the turn.
Unless he views you as a borderline retard, the best you can really hope for after that turn 3bet is that you're chopping. |
Re: next AA
Why aren't we capping this pre-flop?
|
Re: next AA
[ QUOTE ]
Why aren't we capping this pre-flop? [/ QUOTE ] That question occurred to me until I went back and counted raises. |
Re: next AA
theorem: dont raise one player to protect when you dont beat that player
|
Re: next AA
I wouldn't raise the turn. The flop cap followed by a turn lead signals strength.
|
Re: next AA
The flop must be capped. You have a villain who we assume is tight and agggressive from the small sample of hands. Yes you are losing to TT and QQ but the villain may play KK, AQ, or even JJ this way. When the villain leads the turn I agree with most of the previous posters that calling down is the best play even though the third player is still in the hand.
|
Re: next AA
I'm not sure we should be capping this flop, but I think I'm biased by looking ahead and seeing that villain led and 3-bet the turn anyway. Based on the preflop and flop action, villain has either KK or QQ. He might have TT (would he cap that preflop) and I guess he might have AQ (doesn't cap preflop and might not 3-bet the flop) or he might be grossly overdoing things with AK. It's easier for villain to have KK than QQ so I guess the flop is a cap, but IMO this is the street that's borderline. Raising the turn is clearly wrong; you told him you have an overpair, and he's not worried about it.
|
All times are GMT -4. The time now is 11:11 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.