Quote:
Originally Posted by scylla
Just to be clear, what we're being asked for here is input like geo3. This will create a bet corresponding to getting the money in geometrically in 3 bets. And this will only affect the current bet, and not the following ones?
The problem that I personally see with this feature is that some users will spam the entire tree building menu with it, resulting in trees that will make no sense. My counter-offer is to create geo50 input. This would mean that whichever geometric size is closest to 50% will be used. The advantage is that it's not possible to make mistakes with this function, and it will always lead to realistic play.
The problem with your offer of geo50 is that I genuinely don't see any situation where I would use it.
From what I can tell, what I'm proposing is how it works in Pio (
here is a 3min video explaination), and I've seen multiple people using it, and it never seems to be confusing.
An extreme example of using geoX options would look like this (recreated in Excel because the inputs are too long to show in a screenshot of GTO+) :
The result is pretty similar to what it would be if I was using "With only 2 bets left, get the money in smoothly", except it keeps the multiple sizings, and it also does it when the bets are overbets, not only when they are around 70% pot.
And to me, creating this tree isn't confusing: when I input geo2, I know that in the following nodes I probably need to include geo1. You just follow the branches, and you have a tree with perfect geometric sizes. The "Go all-in if push less than 60% pot" option is perfect to prevent geo3/geo2 to be used when the pot is already big.
And this is an extreme example, most people would probably not use geoX sizings for raises anyway.
Quote:
Originally Posted by scylla
We're happy to offer both (it's just coded input, and it's not difficult to write)
If you don't mind offering both, then I don't see why not