Solver with most flexible node locking for opponent mistakes (e.g. sizing mistakes)?

Solver with most flexible node locking for opponent mistakes (e.g. sizing mistakes)?

What solver allows for the most flexible, easy, and robust node locking for opponent mistakes? Basically, I'm looking to experiment with exploitative responses to opponent imbalances of different kinds.

For example, consider bet sizing mistakes. Say I have an opponent that c-bets too large; they bet medium with the same range hands that should bet small, and bet large with the same range of hands that should bet medium. Or say I have an opponent who raises too small; they minraise with the same range of hands that should have a more theoretically-sound raise size. Bet sizing mistakes aren't the only kind of mistakes I'd like to explore, but it's a class of mistake that I find difficult to node lock with the tools I'm familiar with. I'd like to make adjustments like this, and preferably lots of adjustments like this in a single hand, without too much muss or fuss.

Currently, I have GTO+ on my machine. If I want to node lock something like a bet sizing mistake, it's pretty tedious to manually edit or copy ranges and re-run the solution, especially if I'm trying to account for multiple opponent mistakes in a hand.

It looks like Postflopizer has a robust node locking feature with an intuitive interface. Also, GTO Wizard's AI-driven node locking for their Elite tier looks fairly powerful. Are these the best options for node locking out there?

Thanks!

15 April 2024 at 05:50 PM
Reply...

7 Replies



You could try out free for 7 days https://app.deepsolver.com/ it has very fast nodelocking solutions like one minute. You just create the tree with the bet and raise sizings, edit the combos and run the sim.


Many of the more serious players seem to be using gtowizard these days.

That being said, since you're already using GTO+ you might try creating a variety of exploitative ranges, ie "BB overfold defense range vs button."

I've noticed creating the ranges is the most tedious part, but once you have them saved along with saved tree options (bet and raise sizes), then it's quicker to plug in saved ranges, make quick edits as needed, and run a sim.

If it's a deep-stack cash game sim it still takes a while to run, but you can just do something else while it's running.


Thanks for the replies.

It's not the preflop ranges that I want to adjust; it's the postflop ranges (specifically, their sizing and/or composition). For example, I just had a discussion with a fellow poker player about the merits of various turn donk sizes. I wanted to see what would happen if OOP took the range that should donk for 1/3 pot and instead donked 1/2 pot or 3/4 pot or whatever.

In order to do this in GTO+, I had to run the solution with 1/3 donk sizing, copy the OOP turn donking range to the clipboard, copy IP's turn range to the clipboard, create a new solution with these ranges, set the pot size and effective stacks to what they were on the turn, manually edit the tree to force checks on the flop and an OOP bet on the turn for the size that I want, and then run a new solution with these forced parameters.

That's a lot of work!

That's why I'm looking for a solver that allows for flexible, easy, and robust node locking for opponent mistakes. I'd love to be able to do something like right-click on OOP's 1/3 pot donking range and say "bet this range for 3/4 pot instead," and re-run the solution from there without all the tedious manual fiddling.

Is there a solver that is designed to facilitate tinkering like this? Postflopizer seems to be the most promising, but I wanted to see what else is out there before I start the countdown timer on the free trial. Any ideas?


by Grendel k

Thanks for the replies.

It's not the preflop ranges that I want to adjust; it's the postflop ranges (specifically, their sizing and/or composition). For example, I just had a discussion with a fellow poker player about the merits of various turn donk sizes. I wanted to see what would happen if OOP took the range that should donk for 1/3 pot and instead donked 1/2 pot or 3/4 pot or whatever.

In order to do this in GTO+, I had to run the solution with 1/3 donk sizing, copy the OOP turn donking range

I don't think you need to do any of that in GTO+ to change the sizing, you just click the little circle and change the tree


by aner0 k

I don't think you need to do any of that in GTO+ to change the sizing, you just click the little circle and change the tree

Which little circle? On the "Edit tree" screen, I know I can click on a node to add and remove actions, but I don't see any way to change the sizing that a specific range uses.

In this example, I have a range that OOP donks for 1/3 pot. I want to force that same range to donk for 3/4 pot instead. I can add an action for donking 3/4 pot (and optionally remove the action for donking 1/3 pot) and re-run the solution, but then it is a GTO solution that correctly balances the 3/4 pot donking range. I don't want a balanced GTO solution for OOP. I want to lock OOP's mistake of donking 3/4 pot with a range that should be donking 1/3 pot.


by Grendel k

Which little circle? On the "Edit tree" screen, I know I can click on a node to add and remove actions, but I don't see any way to change the sizing that a specific range uses.

In this example, I have a range that OOP donks for 1/3 pot. I want to force that same range to donk for 3/4 pot instead. I can add an action for donking 3/4 pot (and optionally remove the action for donking 1/3 pot) and re-run the solution, but then it is a GTO solution that correctly balances the 3/4 pot donking range. I

I don't think of the top of my head that you can do that on any solver, you have to manually copy the range


You can re-run the solution with the allowed sizings you want and then copy the ranges from the first solve with the 1/3rd pot donk and paste them into the second solution... then nodelock.

I've done something similar before. It is indeed time consuming. For PIOsolver you can open multiple instances of the software which makes this a little smoother.

Reply...