![]() |
|
#11
|
|||
|
|||
|
If I were playing against you and had a maniac image and its pretty clear from this hand you have a king most of the time and occasionally two pair or a set I dont think Im going to ever triple barrel in this spot because Im thinking you want to make a big call with your kings.
That being said if hes not thinking on this level and just playing a very aggressive game without hand reading the call is probably correct. If you have reason to believe he is a decent LAG who will understand the basic hand reading and his image I think blocking the river is best. If hes a very good LAG I think your block will be extremely transparent so I would c/f but I think this is the rarest case at 200nl. Finally if hes a just an overly aggro losing player I think checking and calling is OK but if you arent ready to call this bet I think you should block as this player isnt likely to recognize your blocking. Very interesting hand thanks for sharing it. If you had any read as to what level villain was thinking at I hope you can share it. |
|
#12
|
|||
|
|||
|
I don't think villain was thinking beyond the second level, as I was able to induce a "heroic" call by overbetting the pot AI on the river with a pretty big hand, which he interpreted as a bluff (as I expected) and called with second pair mid kicker. I believe, but I may be wrong, that he would have fired a large bet at that river even if he hadn't hit his back door straight. My notes on him consist of hte words "aggro lagtard" and "set him up pf and on flop for large 3 and 4 bets" because he often would check raise the flop or turn and raise my donk leads, along with 3 and 4 betting pf (assumingly thikning that I was 3 betting light given his image). These are the types of players that give me the most trouble HU. I play back at him pf OOP with any reasonable holding, continue bet the flop, and if he raises i am either forced to jam or fold. it just seemed that i could never get any action with my monsters when i donked him, and that when i donked him with nothing he ALWAYS raised. it was quite frustrating as I'm sure you can imagine. Anyways, thanks for the input, I appreciate it.
Ryan |
|
#13
|
|||
|
|||
|
Because he made that heroic call you know that he is actively trying to hand read (although not necessarily well) and I think its very unlikely that he will ever try a triple barrel bluff in this spot and I also think you should block the river given your read and fold to a push/raise.
Also, I mean this as constructive criticism but those notes you have are not very useful. The fact that he raises donks and c/raises often are good notes but things like "aggro lagtard" and "set him up pf and on flop" are not. It also seems like you are underestimating his skills quite a bit an aggressive even maniacal style heads up is quite profitable if used correctly. |
|
#14
|
|||
|
|||
|
I understand what you're saying about my notes, but, in defense of them, those appeared after my specific notes about raising donk bets and check raising often. They were by no means general notes.
As for his style, it seemed to me that he was being aggro for the sake of being aggro/maniacal to tilt me or get me off my game. It worked (once he caught his BD straight and stacked me 150 BB's deep lol). I may be underestimating his skills, but my gut tells me he is just a maniac who got really lucky a couple times. I do, however, agree that I should have block bet/folded the river, as it may have prevented a big bluff and/or gotten value out of curious call. Thanks again for the valueable insight. Where do you play? FTP PS? Ryan |
|
#15
|
|||
|
|||
|
90% of the time Im on FT.
|
|
#16
|
|||
|
|||
|
what levels? is your s/n public?
|
|
#17
|
|||
|
|||
|
I like everything except the pre-flop re-raise out of position.
|
|
#18
|
|||
|
|||
|
so you don't play back at these guys with sub-premium hands pf out of position to try to take down the pot since they're likely raising air?
Ryan |
|
#19
|
|||
|
|||
|
Is villian SecretofMana?
|
|
#20
|
|||
|
|||
|
Hes right K8o is not the kind of hand to play back with OOP.
|
![]() |
|
|