Two Plus Two Older Archives  

Go Back   Two Plus Two Older Archives > Limit Texas Hold'em > Small Stakes Hold'em
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Display Modes
  #1  
Old 12-14-2005, 11:42 PM
MegumiAmano MegumiAmano is offline
Member
 
Join Date: Jun 2005
Posts: 38
Default Re: HU against a \"PT\'er\"

[ QUOTE ]
I think this explanation helps me the best. I was evaluating pot odds incorrectly by looking at the "turn" portion of a pot odds chart to justify the call with this small number of outs in this hand. So, basically, I'm better off just looing at the "river" portion of a pot odds chart to make a correct judgement.

[/ QUOTE ]

Right. On the flop you can use the rule of thumb that a backdoor straight and/or flush are worth about 1.5 outs each, then just use the odds to see one card on your chart.
Reply With Quote
  #2  
Old 12-26-2005, 03:33 PM
Guest
 
Posts: n/a
Default Re: HU against a \"PT\'er\"

Surely by calling the flop, and then showing down your made straight you are ENCOURAGING him to take pops at you in future, as you have shown you will call with bad odds?
Reply With Quote
  #3  
Old 12-26-2005, 03:56 PM
silkyslim silkyslim is offline
Senior Member
 
Join Date: Feb 2005
Location: Illinois
Posts: 359
Default Re: HU against a \"PT\'er\"

[ QUOTE ]
Surely by calling the flop, and then showing down your made straight you are ENCOURAGING him to take pops at you in future, as you have shown you will call with bad odds?

[/ QUOTE ]
wow this is an old post. i am flattered. anyway, no I don't think this will encourage him because the point of taking pops is to get me to fold. so if i am calling his shots wont work. Do you bluff against calling stations?
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 06:06 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.