blonde poker forum
Welcome, Guest. Please login or register.
July 22, 2025, 11:44:31 PM

Login with username, password and session length
Search:     Advanced search
2262378 Posts in 66606 Topics by 16991 Members
Latest Member: nolankerwin
* Home Help Arcade Search Calendar Guidelines Login Register
+  blonde poker forum
|-+  Poker Forums
| |-+  Poker Hand Analysis
| | |-+  Horrible Level Spot
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: 1 [2] Go Down Print
Author Topic: Horrible Level Spot  (Read 2850 times)
SuuPRlim
Hero Member
*****
Offline Offline

Posts: 10437



View Profile
« Reply #15 on: October 08, 2010, 09:28:18 AM »

In your opinions, how standard is it for someone to Vbet AAxx naked here? I think it's safe to say he'd never expect me to fold any flush vs him here, but then the amount of smaller heart combo's I can have are limited, so it's quite possible he's betting for value vs a medium/high strength flopped hand.

AAxx is exactly the same hand as  small flush relative, and - like you say - if he doesn't think I have many high flushes then he could easily Vbet AA, or a small flush, or even 89.

I dont think he makes this bet ever for anything but value, unless he has maybe ATxx with Ahearts and is turnign his hand into a bluff somehow or attempting a crazxy merge cos he knows im a bit of a sheriff in these spots. So surely this rules a call out as I cant really beat anythign in his value range,

JAM or FOLD ?


all your beating is a bluff its an easy fold IMHO

Jam ever?
Logged

Ironside
Administrator
Hero Member
*****
Offline Offline

Posts: 41933



View Profile
« Reply #16 on: October 08, 2010, 09:53:37 AM »

I never jam a set on a flushed board river in plo, player dependant I will sometimes call, but here I can't see him folding better hands than yours, so your jamming to fold a bluff
Logged

I am the master of my fate
I am the captain of my soul.
Patonius2000
Full Member
***
Offline Offline

Posts: 236


View Profile
« Reply #17 on: October 08, 2010, 01:05:37 PM »

In your opinions, how standard is it for someone to Vbet AAxx naked here? I think it's safe to say he'd never expect me to fold any flush vs him here, but then the amount of smaller heart combo's I can have are limited, so it's quite possible he's betting for value vs a medium/high strength flopped hand.

AAxx is exactly the same hand as  small flush relative, and - like you say - if he doesn't think I have many high flushes then he could easily Vbet AA, or a small flush, or even 89.

I dont think he makes this bet ever for anything but value, unless he has maybe ATxx with Ahearts and is turnign his hand into a bluff somehow or attempting a crazxy merge cos he knows im a bit of a sheriff in these spots. So surely this rules a call out as I cant really beat anythign in his value range,

JAM or FOLD ?


all your beating is a bluff its an easy fold IMHO

Jam ever?

I mean it's not definitely either a jam or a fold you just need to work out how you want to play vs this villain and why. I think it is perfectly reasonable to call with 0 hands in this spot on the river but it doesn't necessarily mean it's the best strategy to exploit this villain. Some players never have a bluffing range in certain spots, I try to have a bluffing range for every spot for better or worse, a set is fairly near the bottom of my range here (and it is behind all his value range which you mention) so I would usually bluff with it (ie crai).
Logged
SuuPRlim
Hero Member
*****
Offline Offline

Posts: 10437



View Profile
« Reply #18 on: October 08, 2010, 01:41:22 PM »

I never jam a set on a flushed board river in plo, player dependant I will sometimes call, but here I can't see him folding better hands than yours, so your jamming to fold a bluff

If he's bet calling 89 or AA then we DEFO shouldn't be Jamming! It would ofc be as a bluff if we were to shove.
Logged

Pages: 1 [2] Go Up Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.086 seconds with 20 queries.