beijingsnake's avatar

beijingsnake

64 points

Hi mark, good to see part 2 of this video
The AQo hand 3bp vs ankhes on QT5r5ss I think the turn is a snapcall with this hand, he still has potentially the same hand or even KQ for value himself and we are very high up in range to ever consider anything other than call, so im very surprised you thought the hand was very close

Dec. 25, 2019 | 4:44 a.m.

more hand examples would be great and maybe show sims for the hand youve played :)

i struggle with these 4bp as well, and for a period of time ive been checking range on A high boards OOP as i ran a sim where we check range on A74 but bet range 1/4 on K74, but its actually very different depending on exact positions/ranges and also SPR

Dec. 22, 2019 | 5:04 a.m.

yes, more practical examples of maybe filtering 4bp youve played would be great

Dec. 21, 2019 | 6:10 a.m.

good format enjoyed it, look forward to pt2

Dec. 2, 2019 | 8:31 p.m.

Hi patrick, nice to see a liveplay video!
The first pio analysis vs mynameiskarl I think the ranges affects our strategy here alot, would be good to see the ranges from preflop but I think youve omitted 99s and 8xs from OOPs range, and because of this your range just continues to bet turn alot and is probably why you think the turn is a high frequency check given you mentioned you ran similar sims in this spot

I reran a sim but was difficult to copy the parameters and ranges youve used preflop, and there was around 36% checking back OTT vs 30% vs your ranges with 1/2 of 99s included and 20pc of 67s and 78s only. I expected this to be abit more like you predicted in game but would be good if could see your whole sim in future videos :)

Nov. 9, 2019 | 9:37 p.m.

adminasrio rerun your sim with multiple OOP bet sizes, think choosing only a pot sized cbet or check is leaking a decent chunk of EV for OOP

Aug. 31, 2019 | 12:07 a.m.

Great video, patrick

The first hand with QTcc I was rather suprised you said all IPs pairs including 22s should be good enough to continue vs a pot sized cbet, decided to run a pio sim and unpaired pocket pairs TTs and below all fold vs a pot sized cbet

More surprisingly is that OOP's pot share is nearly twice the pot share of IP, 217 vs 132, and we are allowed to cbet full range for a variety of sizes here. I initially would have agreed with you that we do some larger cbets and check a decent part of our range too, but that doesnt seem to be the case here. My ranges might be slightly off:

Aug. 30, 2019 | 6:41 p.m.

Nice video

Last hand with KK what do you think to blocking the river? I feel after checking the turn blocking would make the most sense as we’d want to vb some hands such as QQ too and most of our bluffs ie AQ ATs are just going to barrell the turn so we also want to give villian a better price to call as well as challenge him to find raises vs our hands like QQ AJ that can also value bet river as a block. Kk feels like a great hand to defend that range

Aug. 21, 2019 | 5:11 a.m.

Good video for MPN grinders.

July 30, 2019 | 2:51 p.m.

33:03 hand starts

July 29, 2019 | 7:23 p.m.

Hi Ben, great video as always!
the TTs hand on QJ4ccx 3 ways to flop, where you check called flop vs btn and bet 45 into 77 on the QJ4TK runout, you briefly explained that you think we are good here, but this spot feels very thin to me as a VB. I think I can get behind a block on the river. Can you explain deeper your reasoning for value betting and choosing this sizing? Thanks

July 28, 2019 | 8:03 p.m.

Hi henry, nice video and solid plays

your plays preflop though seem overly tight. you have said you are using a pure 3b/fold strategy and also using a larger 3b sizing hence the A9hh and 77s fold from the btn open, but these seem ridiculously tight to me, even with added rake. monker ranges i solved for 100bbs make these hands clear 3bs in a 3b/fold strategy from the sb

my solves included rake and is for 2.5x btn and 11.5x OOP.

would be interesting to see your sims

July 19, 2019 | 5:03 p.m.

like in the dark
always excited to see a new coach :)

July 16, 2019 | 11:04 p.m.

think its because of shallower stack sizes and also that we have a tighter range UTG that our bet sizes become bigger
When stacks are deeper and theres alot more behind left to play and we have a nut disadvantage we want to bet smaller

June 29, 2019 | 10:43 a.m.

Hi Daniel,
the hand where you defended K3o vs btn open on TT3r and you blocked turn on 3hh river, you didnt comment too much on the hand.
I feel villian should probably play a simplified strategy of pure cbet small on this flop, so checking back this board is somewhat intersting.
Also as played, I felt we should probably size up turn, since we are betting more polarised and we have such a wide range. dont think theres many hands in our range on that board that benefits from blocking the turn

June 29, 2019 | 10:33 a.m.

Hi gary liked the video,
Your final hand with KJhh on J35Q you talked about thinking ahead to brick rivers and that you'd choose AJ over KJ as a call turn call river because having an A is better than a K, K blocks KK KQ, A blocks AA AQ which is the same. having K blocks KT and AK which is bad, but having A blocks AT AK and even potentially A24s which you didnt mention. so i dont really understand your explanation

May 17, 2019 | 10:31 a.m.

Hi Juan thanks for reply,
of course OOP has more combos of flushes but as overall % of his range I dont think he has more. decided to run a pio sim. I thought IP would definitely do some betting but was suprised to see full range bet:

May 13, 2019 | 6:17 p.m.

Hi Juan on the QQ hand where you limped and BB checked 753ccc you said you are checking back your entire range on this board? Can understand it’s a good board for BB as his check back range includes lots of small cards but surely we should do some betting after he checks. You also mentioned that bb is going to be more suited than us but I don’t see how his range is more suited

May 13, 2019 | 4:56 a.m.

Hi Ben do you never add in a flop 3b for IP, for AA8r and 446r I think both check raise ranges are exaggerated as OOP assumes they will never face an IP 3b
Think on AA8r IP flop 3b is especially important, but also on 446r even if IP might play pure call vs CR think its important to add in flop 3b for accurate raise frequencies

March 8, 2019 | 7:25 p.m.

Hi Ben loving the videos

77s hand at @5 mins in

I ran the hand in pio as I would have continued this hand on the turn vs 2/3, as I think 77s especially without a club unblocks all his draws on turn and hitting 7 has 2 clean outs to the nuts

However, its interesting to see that pio prefers calling more 77s that do block the bdfd, also choosing to call more 88s and 99s (but folding TTs), intuitively I would have thought 77s is a better continue than 88s or 99s and also not having a bdfd blocker is better, however this seems to be the other way round!

Can you explain please

Nov. 7, 2018 | 4:48 p.m.

Hi there nice video
In the final hand analysis with 45cc vs a 16pc 3bettor from the BB I see you've used snowy ranges for IP, but surely we should widen our 4b range here to include hands like AQs TTs and even some SCs? playing flat with everything except AA-JJ AK and some suited wheel aces seem incorrect

Sept. 19, 2018 | 1:50 a.m.

Quality HU content, do you use a HUD? Why did you choose this size to value bet @21.43?

April 21, 2018 | 5:52 p.m.

Comment | beijingsnake commented on 40 BB Six Max PLO

Nice vid!

Out of curiosity, how can villain use specific blockers to exploit the strategy of folding the lowest flushes?

April 13, 2018 | 8:21 p.m.

Hiya mate love the vids!
K8ss hand you opened co and BB defended. You checked back on 568r and called on a rainbow Q turn. River 2 and you folded to another 2/3 bet. I think this is a spot where I would always have called having checked back the flop. We do block some 2 pairs and I think villains will be over bluffing in this spot whereas you feel they just aren't ever bluffing enough. Can you explain abit more why you thought it was a clear fold? Thanks

April 10, 2017 | 4:26 a.m.

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