PLO preflop actions on GTO Trainer
Using the Training Software from PLO Mastermind, the following flop actions were suggested. Can someone simply explain in general terms why these actions were chosen?
6max.. cut off vs BB.
Cut off opens for pot.
Folds to us in the BB.
with KsQsJhTh7d, it says calling from the BB is the best play.
with KsTd9h8h7s, it says raising from the BB is the best play.
It would seem that the first hand is stronger then the second, so why is it choosing the second hand to raise with? Much appreciated if someone could just give a simple , intuitive explanation of this example.
3 Replies
Using the Training Software from PLO Mastermind, the following flop actions were suggested. Can someone simply explain in general terms why these actions were chosen?
6max.. cut off vs BB.
Cut off opens for pot.
Folds to us in the BB.
with KsQsJhTh7d, it says calling from the BB is the best play.
with KsTd9h8h7s, it says raising from the BB is the best play.
It would seem that the first hand is stronger then the second, so why is it choosing th
oops, sorry, meant to say our position was the BUTTON, not the BB.
Ok, I'll take a shot. I wrote this assuming Hero was BB before seeing the next post.
The first hand IS stronger, but it plays worse vs premium hands and a possible 4! because its broadway cards are easily dominated. It also has good playability postflop.
The second hand has much less risk of being dominated vs premium hands and benefits more from fold equity because it will win less often than the first hand at showdown.
Solvers aren't always easily described in human logic, especially with how it balances ranges.
Edit for btn: hand 1 has better multiplayer equity and playability than hand 2, it doesn't mind more actions from the blind; hand 2 prefers less players
Maybe I can add something, the solver assumes players will fold, hence certain 3 bets from CO / BTN to knock out the blinds and play HU IP. If you play in games where 2-3 players happily see the flop even after a 3 bet, then better fold Hand 2.
