Two Plus Two Older Archives  

Go Back   Two Plus Two Older Archives > Limit Texas Hold'em > Micro-Limits
FAQ Community Calendar Today's Posts Search

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #7  
Old 09-17-2005, 05:59 PM
Aaron W. Aaron W. is offline
Member
 
Join Date: Sep 2002
Location: San Diego, CA
Posts: 87
Default Re: *Yawn* Preflop decision

[ QUOTE ]
In this hand, CO has been here for 10 hands but is already shaping up to be a LAG. He's raised every time he's come in at this point. I believe SB is a browntrout since his name sounds familiar, but he seems a little loose and a little aggy over a small sample size so I'm not sure.

Party Poker 1/2 Hold'em (9 handed) FTR converter on zerodivide.cx

Preflop: Hero is BB with 8[img]/images/graemlins/spade.gif[/img], 9[img]/images/graemlins/spade.gif[/img].
<font color="#666666">1 fold</font>, UTG+1 calls, <font color="#666666">1 fold</font>, MP2 calls, MP3 calls, <font color="#CC3333">CO raises</font>, <font color="#666666">1 fold</font>, <font color="#CC3333">SB 3-bets</font>, Hero...

After a preflop revelation by Aaron and d5 yesterday, I wanted to reexamine a few pf decisions. Is this one trivial?

[/ QUOTE ]

I don't think it matters much either way. You're probably going to see this flop 4-5 handed and you have a pretty good mutliway hand. You've got a potential LAG in the pot who will likely help you to pump the pot if you flop a strong draw.

On the other hand, I don't like the 3-bettor's position relative to you. He's going to come out firing on most flops and if you catch a weak draw, you may find yourself getting trapped between LAG and TAG.

I would probably fold until I get a better read on SB and LAG.
Reply With Quote
 


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 09:16 PM.


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