Out Now
×

WCOOP $320 PLO Review (part 3)

Posted by

You’re watching:

WCOOP $320 PLO Review (part 3)

user avatar

Lucas Greenwood

Elite Pro

Video Player is loading.
Current Time 0:00
Loaded: 0%
Duration -:-
Remaining Time 0:00
  • descriptions off, selected

Resume Video

Start from Beginning

Watch Video

Replay Video

10

You’re watching:

WCOOP $320 PLO Review (part 3)

user avatar

Lucas Greenwood

POSTED Nov 16, 2014

Lucas continues his short handed play at the final table as he chases a WCOOP title.

5 Comments

Loading 5 Comments...

pokertroy77 10 years, 4 months ago

I enjoy your videos, however I think the 236q ss should be the bottom of limp/fold range. It has enough raw equity, however puts u in too many tricky/dominating spots post flop Especially if bb is a competent opponent.

lofigr 10 years, 4 months ago

I like your videos Luke - good stuff.
Regarding JJ quads hand - I don't know why didn't we bet OTR (30 000 pot) OOP to cca 22,5K when Villain has 62 705 (we have 231 916). Good players are bluffcatching here with hands like Khi flush, don't thin value bet hands worse than Ahi flush, we could have secure +22K instead of counting on potential +62K (not huge diff in #ofChips due to our stack, big diff in EventExpectation imo).
Regarding Q632 hand: is there any merit to just call flop, fold on{9,J,K,A}!s and jam (VB or bluff) any other turn card when and after opponent checks..?

Lucas Greenwood 10 years, 4 months ago

In the last hand I could see folding 47 in big huni`s shoes vs the right opponent, you could also even fold 47 with no redraws ott vs some, because you will have nut combos and also hands with better equity. Top set and a fd for example is a much stronger hand than bare 47. He could also have set + higher straight draw and plan to bluff diamonds, or maybe a flush draw and a straight draw that he can call and bluff river if the board pairs.

Be the first to add a comment

You must upgrade your account to leave a comment.

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