|
Working on exploiting LAggish player
HAND 1:
I had like 40 hands on villain at this point, but hadn't seen him show anything down (i had made him pay for limp/calling with a few cbets before this, but that's our only history). he was running 52/25/3 or something at the time of the hand. street by street thoughts below:
Full Tilt Pot-Limit Hold'em, $0.10 BB (5 handed) - Full-Tilt Converter Tool from FlopTurnRiver.com
UTG ($10.34)
Hero (MP) ($14.48)
Button ($12.78)
SB ($18.50)
BB ($9.67)
Preflop: Hero is MP with , 
UTG bets $0.35, Hero calls $0.35, 3 folds
maybe it's nitty of me, but this is actually a borderline call for me. i usually make the call but i always have to think about it first. i saw his 25% PFR and figured he wasn't very positionally aware and was almost certain this was an opponent i could position pwn if given the right flop, so i call.
Flop: ($0.85) , , (2 players)
UTG bets $0.85, Hero raises to $2.50, UTG calls $1.65
his cbet% was 100 (i had factored this going into the flop), and seeing as how he'd raised 1/4 of his first 40 hands i figured he had cbet 10 times which is a large enough sample for me to start to figure he cbets air. i have outs against his range, so i try to take it down here. i'm guessing floating is actually a better option here, especially because we have position?
Turn: ($5.85) (2 players)
UTG checks, Hero checks
no way i'm barrelling this turn.
River: ($5.85) (2 players)
UTG checks, Hero checks
i thought long and hard about bluffing again here, but couldn't justify it based on ranges. i dont' think he's ever folding a K here if he didn't on the flop, and the more T's and QQ and JJ type hands i put into his range, the looser of a fish he is for calling the flop so the more likely he is to call a river bluff even if he shouldn't. please shit on my thought process so i can learn and grow...
HAND 2:
same opponent like 50 hands later. now i have a bit more history because he saw me raise his cbet as a bluff (the hand before), and like two hands before this, i raised with K4s on the BU when he limped UTG, and delayed cbet an A-high board with no outs. he folded after thinking long and hard and i showed my garbage because i felt i was starting to get to him. i also had picked up a few reads by now but the only relavent one to this hand is that he ended up showing down AT in hand 1 of this post (meaning he's willing to continue with marginal hands to a flop raise).
i hate to be that dude who posts about maximizing value with an f'ing boat but i have to start figuring out how to exploit against specific types of fish
Full Tilt Pot-Limit Hold'em, $0.10 BB (6 handed) - Full-Tilt Converter Tool from FlopTurnRiver.com
MP ($3.05)
CO ($7.49)
Button ($19.09)
SB ($2.40)
Hero (BB) ($11.99)
UTG ($17.29)
Preflop: Hero is BB with , 
2 folds, CO calls $0.10, Button calls $0.10, SB calls $0.05, Hero checks
Flop: ($0.40) , , (4 players)
SB checks, Hero bets $0.20, CO raises to $0.40, 2 folds, Hero raises to $1.20, CO calls $0.80
the second i make this bet i regret that it's not bigger. i like auto half pot flops that are this bone dry, but i shoulda been more concerned about building a big pot rather than merging ranges. he min raises so i figure he likes his hand. should i raise more here? i don't want to push 98o off the hand and i he doesn't have TT+ 'cause my notes show that he PFR's his good hands. so the second he minraises i figure i might be able to get his stack but have a hard time imagining what he has, so i'm trying to get him to bluff his stack away.
Turn: ($2.80) (2 players)
Hero checks, CO checks
i feel a bet here makes him suspicious. before the turn even came i thought i was either going to have to insta-check or long-think/bet here in order to get the desired results of having him bang his head against the wall some more. am i getting too tricky?
River: ($2.80) (2 players)
Hero bets $2.40
i'm obviously betting here. i'm never expecting him to call a CRAI and think there's a chance he'll push over because i'm not repping much (i've never seen him bluff without a draw though). bet sizing also seems fine to me but everything's up for discussion.
|