![]() |
ftops event #3. how bad is this resteal?
How much do you hate this resteal? I know i shouldn't post results, but i busted on this hand. Maybe it's not that interesting, but after playing freaking 3 and a half hours of solid poker i went out on this one 493rd (405 money) and have been thinking about whether or not it was really horrible.
i'm somewhat new to the table and haven't made any big moves yet. villain had not been super aggro on my BB but had been active and it seemed to me he could certainly be open raising from the button with a wide range here. Full Tilt Poker No Limit Holdem Tournament Blinds: t250/t500 (Ante: t50) 9 players Converter Stack sizes: UTG: t18435 UTG+1: t14628 MP1: t29770 MP2: t20891 MP3: t6071 CO: t18982 Button: t24233 SB: t22826 Hero: t8829 Pre-flop: (9 players) Hero is BB with 6[img]/images/graemlins/diamond.gif[/img] 7[img]/images/graemlins/spade.gif[/img] 6 folds, <font color="#cc0000">Button raises to t1250</font>, SB folds, <font color="#cc0000">Hero raises all-in t8779</font> |
Re: ftops event #3. how bad is this resteal?
It is'nt bad at all if it worked you increase your stack by about 20% he could have a pretty wide range of hands many of which he will drop to a reraise. The fact you are within 100 of the money is not a consideration, you are short and unless you pick up some chips you are not going to make the money in any event.
regards Ross |
Re: ftops event #3. how bad is this resteal?
It's marginal but OK, given stack sizes and reads.
|
Re: ftops event #3. how bad is this resteal?
I like it
|
Re: ftops event #3. how bad is this resteal?
yeah maybe it's just results oriented thinking. he thought and called with KJo and his hand held and i went out. the call was obviously gross but it just got me wondering if i should have been more patient and looked for a better spot to get my chips in. or at least had a better read that he was willing to fold a marginal hand here.
|
| All times are GMT -4. The time now is 07:00 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.