Quote:
Originally Posted by dna92kz
Hello. Where is ante? If i use "Dead money" (cash drops) everyone plays +ev, +bb/100. A little confusing. It shouldn't be that way as far as i know.
I see what you are saying. You could treat posting the ante as a loss, and display the EV of folding as the cost of posting the ante. However, I wouldn't go as far as saying that it is wrong to consider the ante dead money. It's not a forced bet as the blinds are, and it's also not a rake as the money remains in the pot. I think it could make sense to add a separate implementation for antes.
Quote:
Originally Posted by aggrodude6000
Hi,
is there a more in-depth guide on how to use custom actions in the beta? I'm trying to use multiple cbet sizes as an example, how do I do this? And how do I create custom bet/raise/reraise sizes that differ from each other?
Thanks for any help!
There is some information included with the BETA. When creating a new game tree, if you go to 'Custom actions' and '<Create new>' there is a guide describing how to create custom actions, with an example how to do so. Some inference on the side of the user is required however, as the provided syntax is not exhaustive.
Quote:
Originally Posted by aggrodude6000
2nd question, if I save ranges from the solved strategy, e.g. the check/call range on the flop, where does the beta save it to?
Ranges will typically be saved to your clipboard, and you can paste them to another game tree or program for example.
Quote:
Originally Posted by BoboFett
Monkersolver window is pure blank after day 4 of a long
Solve? In the task manager it doesn't list it as "not
Responding" so it's still working fine and crunching numbers but the visuals
In the window are completely blacked out. Is their anyways to save this. I dont wanna waste all this time and exit it.
I can open a new monker fine and visuals their are normal and everything else on my laptop works fine
This looks like some sort of graphical bug that is not common and perhaps specific to your software setup. You could try opening a new instance of Monkersolver and making sure the window is sized the same and then see if you can click where the save button should be and then save that way (simply perform the actions required analogous to what you are doing in the instance of Monkersolver that is displaying normally).
Quote:
Originally Posted by cellar door
I have been trying to lock ranges. When I lock hands which aren't close to the top of the range, they don't seem to lock. So if I lock AA or KK it works fine, but when I lock 89o or 24s, the lock doesn't seem to take effect on those hands. I don't think it is an iteration issue, as I ran the sim for quite some time. Any advice appreciated.
I have not been able to observe such behaviour from the solver personally.
Quote:
Originally Posted by MarburyMad
Has anyone use this for Omaha Hi/Lo limit?
Yes.