Two Plus Two Older Archives

Two Plus Two Older Archives (http://archives2.twoplustwo.com/index.php)
-   Micro-Limits (http://archives2.twoplustwo.com/forumdisplay.php?f=33)
-   -   General strategy question... blinds defense (http://archives2.twoplustwo.com/showthread.php?t=408368)

KSOT 12-31-2005 09:18 PM

General strategy question... blinds defense
 
I think I've developed a large leak in my game but I want to be sure.

Lately it seems like whenever I'm in the big blind and everyone folds to the small, they raise me. For some reason this really rubs me the wrong way, far more than a regular steal ever could. I wind up calling like 99% of the time and I almost always have to fold to their flop bet when I don't pair. Am I wasting a small bet too often doing this? If I fold here won't it just entice them to start picking on me more often? What is the correct way to handle this situation? How tight should my calling requirements be. I know it's very player dependant, so either assume the SB's stats are 'average' or give either/or examples if you please.

Thanks a lot.

stuartharris 12-31-2005 09:51 PM

Re: General strategy question... blinds defense
 
Certainly don't call 99% of the time. Play half or more of your hands and reraise with a good percentage of those. If you're truly being stolen from, the last thing the stealer wants to see is a reraise. Your reraise will slow the stealer down considerably.

milesdyson 12-31-2005 10:58 PM

Re: General strategy question... blinds defense
 
......and we're back to table selection. keep the loose passive players on your right.

anyway when the rake becomes less of an issue you should be calling almost every time. at the micros, i'd guess you should be folding in this spot probably 30-40% of the time.

KSOT 12-31-2005 11:26 PM

Re: General strategy question... blinds defense
 
Table selection is one thing, but seat selection? I usually don't have any say in the matter.


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

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