Majestic's avatar

Majestic

2 points

None: 0

April 12, 2014 | 3:29 p.m.

ok so initially I didn't really consider flatting his raise, but I guess it's the best option since I'm getting it in bad OTF... My dilemma was what if blank turn and he bets big again (very likely)? 

My deciision was to get it in because lol I haz nutz draw + top pair,, but yeah I was wondering how good that decision was vs his range..


April 5, 2014 | 3:27 p.m.

Hand History | Majestic posted in NLHE: NL100 letting go of TP+NFD on the flop?
None: 0

April 4, 2014 | 6:23 p.m.

Hand History | Majestic posted in NLHE: NL50 You can't win if you fold
None: 0

Feb. 28, 2014 | 8:32 a.m.

Good points Daz, OTT I think he decides to either give up or fire triple vs my range. So the best play would be to give up Turn


Feb. 28, 2014 | 8:30 a.m.

quality, thanks.


Feb. 28, 2014 | 5:18 a.m.

I thought flop is an obvious give up, given board and our equity. I am impressed w/ the ambitious cB

Feb. 27, 2014 | 6:45 p.m.

someone said "Fold flop vs his barrel stats. You basically want to hit a pair and not
fold vs him. If you call flop with A high he is just going to make you
fold on a later street." - I think this is a good idea, what do u think?

Feb. 27, 2014 | 4:34 p.m.

what value range do I raise flop?


Feb. 27, 2014 | 4:23 p.m.

Hand History | Majestic posted in NLHE: NL50 SH feeling raped by aggro reg
None: Jon Doe: 0

Feb. 27, 2014 | 11:09 a.m.

thanks, other ppl I spoke to said it is a mistake to c/c turn with this hand since it is too strong, so I should 3barrel here.

Jan. 15, 2014 | 8:26 p.m.

Hand History | Majestic posted in NLHE: NL20 SH BVB leveling action
None: Jon Doe: 0

Jan. 13, 2014 | 11:08 a.m.

so u guys are saying it's close, inclined to fold. And as a standard vs unknown fish they are less likely to bluff 2 streets.

Jan. 3, 2014 | 7:56 p.m.

Post | Majestic posted in NLHE: NL20 SH Fighting back vs IP Reg

http://wt.ag/1lEFVr2

Villain is 20/18 reg w/ 15% raise flop, 4 AF

Due to positions, I think he will attack this board fairly often. That said, I think I have enough FE and later barreling opportunities to cB and I think it may be too weak to just give up.

What do you think about reraising flop to 8,5?
He is only repping 44/99 for value (I don't think he is flatting Q9, QQ that often).
Plus, we have Ah so he won't be shoving NFD.

We can rep plenty of hands with our play.
Thoughts?

Jan. 3, 2014 | 1:56 p.m.

http://weaktight.com/6368350

villain is Unkown fish who just posted the blind.

Flop - The problem is he rarely hits the board and I think there is more value in letting him bluff.

As played, I am calling turn since he can still be bluffing, he has a potsized bet behind.

What do you think about my thought process here? Is it ok or are we too optimistic to take this line?



Jan. 3, 2014 | 1:39 p.m.

If I am villain here I also have QQ+ in my flatting range since I have SB fish and I want to keep him in. In this spot I don't see Villain having bluffs.

That said, OTT I am checking for him to vBet worse and I am calling to a smaller sizing and c/f riv, and c/f turn if he bets bigger.

When u barrel turn, your line looks too strong, given preflop sqz, flop cBet 3way with fish in pot on low connected board --> no weaker hands call. Ugly spot for JJ

Dec. 24, 2013 | 8:32 p.m.

Thanks for the feedback guys, appreciate it!

Was thinking about the AK preflop play and my instinct was that I am never dominating unknown's 5b range, basically he doesn't shove AQ ever, so I'm behind almost always, with 40%.

So when I am 4b/calling I am losing money but I am losing less than 4b/folding (which would make no sense ofc) and indeed I think it is compensated by the folds I get from my 4bets. AK doesn't play THAT good w/o initiative postflop anyway, especially vs agg villain.

So I think raising flop is best. And calling turn as played? We are unlikely to get paid off on a Heart. If river bricks do we plan to check back and win vs his bluffs (eg Khx) or shove, representing only flopped flushes, since any other strong hands should have raised at some point and it would be 13 into 22 . 

Still, what about shoving turn? I think we look so strong here and it's difficult to call KQ (no Kh) and weaker, we should only get called by AQ, 22/55/QQ, KK/AA (which we block). Even we called, we have decent equity. Maybe this would be better and produce more fold equity (we rep stronger) than shoving a blank river.

Dec. 24, 2013 | 9:41 a.m.

Hand History | Majestic posted in NLHE: NL20 SH Anon AKo flat 3b IP NFD flop
None: Jon Doe: $0

Dec. 21, 2013 | 10:26 a.m.

thanks guys, I was thinking he can't be bluffing either in this spot so we are just hoping for AA/KK

Nov. 29, 2013 | 10:32 p.m.

Hand History | Majestic posted in NLHE: NL20 SH ATs 4b bluff pre leads to trouble
None: Jon Doe: 0

Nov. 29, 2013 | 4:34 p.m.

None: Jon Doe: 0

Nov. 29, 2013 | 4:01 p.m.

Hand History | Majestic posted in NLHE: NL50 SH Anon bot set overplay?
None: Jon Doe: 0

Nov. 29, 2013 | 3:34 p.m.

this is 3way though, I think they would be less inclined to bluff?

Nov. 24, 2013 | 1:58 a.m.

Hand History | Majestic posted in NLHE: NL20 SH Anon KK slowplayed Pre
None: 0

Nov. 23, 2013 | 5:16 p.m.

Really appreciate your input guys,

I agree that it was a bad fold, in retrospect.

@Daz - thanks for the detailed answer
4) I see him floating very rarely, given positions, maybe only AhKh, but yeah otherwise I think he has little bluffs in his range. 

Also, he might have a looser calling 3b range, but do you think he would go as low as AhTh? I mean he is often dominated by my AK, AQ.

I agree with you on the other points

I remember what was my (flawed) thought process in the hand. All I could think of when Q hit turn was 'fck he has QQ!!!', so my thought process all came from my 'certainty that he had QQ' which was definitely not profitable.


Thanks!


Nov. 17, 2013 | 4:08 p.m.

Hand History | Majestic posted in NLHE: NL50 SH Anon JJ 3rd set in 3b Pot fml
None: Jon Doe: 0

Nov. 14, 2013 | 3:24 p.m.

Load more
Runitonce.com uses cookies to give you the best experience. Learn more about our Cookie Policy