![]() |
Re: Continuationbet +EV?
Looks completely standard to me.
|
Re: Continuationbet +EV?
[ QUOTE ]
dont like [/ QUOTE ] You c/c flop here? |
Re: Continuationbet +EV?
I would c/c flop and c/f after that
Once it checks thru I would bet turn for 2/3 pot |
Re: Continuationbet +EV?
It of course looks standard but should be pretty bad theoretically. Only reason for the bet is that it makes the hand easier to play against straightforward opponents. Still checking has to be superior imo.
|
Re: Continuationbet +EV?
[ QUOTE ]
It of course looks standard but should be pretty bad theoretically. Only reason for the bet is that it makes the hand easier to play against straightforward opponents. Still checking has to be superior imo. [/ QUOTE ] assuming opponent bets his entire range and checks hands you beat on the turn, absolutely. this would be a line to take against a garden variety TAG. |
Re: Continuationbet +EV?
in a vacuum checking is probably superior, if you are good at handling tough decisions out of position against aggressive opponents.
from a metagame POV its probably bad since if you 3bet this guy with 78s, this is a good flop to cbet i think. im bad at playing OOP so i like to make the hand easier to play and just bet/fold note: if i had 3bet this guy in position and he called, and tthe flop came like this, i'd check behind nearly always. |
Re: Continuationbet +EV?
in a vacuum checking might be better than betting but I think betting is the best for other reasons.
|
Re: Continuationbet +EV?
I like it and bet size. If called your done with hand. Against a super passive, you might check and plan to call one bet on next three streets, but against a better player, this is easier and standard.
|
Re: Continuationbet +EV?
i like it! you often take it down...
what do we do if the just calls?! |
Re: Continuationbet +EV?
[ QUOTE ]
i like it! you often take it down... what do we do if the just calls?! [/ QUOTE ] c/f turn |
All times are GMT -4. The time now is 01:08 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.