![]() |
|
|
|
#1
|
|||
|
|||
|
[ QUOTE ]
So you raise 66 on a laggy table in early position, thats suicide. If it was a rock garden then of course but his read was that the table was LAG. [/ QUOTE ] It was a 5-top, and his read was that the CO and button were reasonable, but the blinds were LAGs. Easy raise. It turned out bad when CO woke up with a hand, but it's a moneymaker in the long run. You will frequently see the flop against just the 1 or 2 LAGs, with position, and with a made middle pair. Good times. B. |
|
#2
|
|||
|
|||
|
[ QUOTE ]
It was a 5-top, and his read was that the CO and button were reasonable, but the blinds were LAGs. Easy raise. It turned out bad when CO woke up with a hand, but it's a moneymaker in the long run. You will frequently see the flop against just the 1 or 2 LAGs, with position, and with a made middle pair. Good times. B. [/ QUOTE ] These were my thoughts exactly. Everyone keeps pointing out that I raised with 66 out of position on a LAGgy table. I figured this raise would give me position vs the two LAGs, and I would be in a good spot. After the CO 3-bet, though, it just looks like I really screwed up this hand. I liked the preflop play. |
|
#3
|
|||
|
|||
|
Low pocket pairs suck against 2-3 players. I only raise this trash in CO if the blinds are tight. I want one caller or none. If you get 2 you lose money.
Made middle pair? This is a trash pair, if you dont hit the flop you dont know where you are at. What are you going to do if you miss the flop and you get raised? Call down and get shown a bigger pair. |
|
#4
|
|||
|
|||
|
Fold on the flop. With that action from 3 different players, I'm playing to flop a set or fold. The likelihood of a higher pair is simply too high to invest bet after bet to see the showdown. And even if all they had were overcards, their combination of outs gives you the reverse implied odds necessary to dump it on the flop. You simply threw away 1 BB on the flop IMO.
|
|
#5
|
|||
|
|||
|
I know, of course as soon as I called the flop I knew I was an idiot for doing it... but the BB's lagginess and the size of the pot suckered me into calling (this guy sporadically raises UTG at full tables with 84s or q3 off and calls it "bluffing".)
Ah well. |
|
#6
|
|||
|
|||
|
I guess I just don't understand raising out of position with 66 here. What are you trying to accomplish with this? Maybe you are trying to get the tight player to fold. I'd rather he stay in when my only real hope is to flop a set.
If they were calling stations, I'd call pre-flop and try to flop a set cheaply. Since you say they are loose-aggressive, getting raised by one of the 4 players behind me is fairly likely. This would make me and my 66 quite sad, therefore I fold in this spot. Am I missing something? |
|
#7
|
|||
|
|||
|
The CO and button hadn't played a hand in a while; they were pretty tight players. The SB was loose, but sensible, and didn't get out of line against me very often (we've played together a lot). The BB liked to play anything.
I was fully expecting my 66 to be the best hand, and have either blind defend with junk. I really wasn't anticipating a raise behind me, or multi-way action. I guess my original post was misleading. The table hadn't been THAT crazy up to this point. Only the players in the SB and BB in this hand were the laggy ones, and even then they'd open with a lot of hands, but their 3-betting standards weren't that bad. After this hand though, things went haywire. |
|
#8
|
|||
|
|||
|
I think the first preflop raise is fine (based on table, etc), but I'd fold when it's 2 more bets back to me. Calling that flop bet is really bad, and you should have definitely folded there since you didn't fold preflop.
Freakin |
|
#9
|
|||
|
|||
|
Fold preflop, this is too weak to raise, especially on a laggy table.
Fold on the flop against that much action preflop and 2 overcards to your pair, only a backdoor straight and possible raises after you, you have to fold. |
|
#10
|
|||
|
|||
|
I think folding the flop is the right move. However, if BB is prone to betting with nothing but overcards, then I think you can consider raising.
|
![]() |
|
|