Quote:
Originally Posted by Ketlar
Would be really cool if there were additional options apart from random for the flop that would fall into either a wet or dry category, I.e baby cards, broadways, paired flops and monotone.
?
Todd Terry - thanks for good feedback on app.
V.3.7.1 has gone live with the above additional random flop buttons, sorry for the long delay between updates this time.
1) Select (tap) a flop card.
2) Menu->RandomFlop then has buttons for dealing a random {broadway, medium, low, suited, paired} flop.
3) The "Rnd" button on the main screen remembers what you did last in Menu->RandomFlop so you can tap it repeatedly to generate e.g. many random broadway/suited/etc. flops.
Thanks for this suggestion Ketlar, I think it helps generate better what-if scenarios.
There's a subtle remaining issue/improvement with the random flop feature, but I don't think it's serious enough to really screw things up for anyone. To deal a random flop of any kind (pure random, broadway, etc.), the code currently simply picks random cards that are still live (not assigned to players and not marked dead). But this feature doesn't look at or consider hand ranges that have been assigned to players. This affects the distribution of the generated random flops.
For example say you do a ResetAll, so no card is assigned or dead, and look at the distribution of the generated random flops. Then you enter hand range {top 5% of hands} for Player1. This range has mostly high cards, so the distribution of random flops should now have fewer flops that have high cards than in the after-ResetAll case. But currently the distribution in these two cases is the same.
This was pointed out to me by app user John at Bellagio a month ago, his use case was he entered range 66 for P1, range AK for P2, and was generating many random flops to get a feel for e.g. how often the "death flop" for AK would come (both an Ace/King and a 6 on the flop). But one generated flop was 666. No big harm done, because then when you calculate the app says "can't calculate because can't assign hand ranges", but this is a glitch I'll keep my eye on for an app update at some point. Thanks for pointing this out John.