[quote=“SunPowerGuru, post:19, topic:6651”]
Except this NEVER happens in real life.
[/quote]SPG,
My dad introduced me to computers on a Apple IIe, all that loaded was was it need’d to talk to the floppy drive… or howabout most Ti calculators, that can run mini programs, and use a RND function… So yess, it does happen in real life…[quote=“spivak, post:17, topic:6651”]
Just don’t use the same seed each time and the problem is solved.
[/quote]Exactly Spivac, you build in a “seed” that is input by a human… and you go from there…
As SPG has shown, in the quote from Gatsby, is in my opinion and a few teachers I had opinions to be a pretty shabby “shuffle”… not only does this describe a 1 shuffle senario, but then each time it is pulling from a “clean” deck… Since a computer can complete this task in surely under 1 second, why not repeat this process between 5-9 times, randomly varry’n it between the 5-9 times, I think the table can survive an xtra second between hands…
That approach lends itself to patterns all by itself, especially since you are starting with a clean deck each time. No matter how you shuffle, 1 sure fire way to dismiss “rigg’d claims” is to create a simple slider… allow the person to the right of the dealer to “cut” the cards using the slider each hand… who cares if this adds 3-5 seconds to each hand…
If you go to a bar, or any casino with a human dealer/shuffler, there’s no freak’n way that dealer is only gonna shuffle the cards once between hands, and prolly every once around the table they do a “wash” on the table… why would Replay only want 1 “shuffle”, makes no sence to me from a programming standpoint.
I was just taught differently by my dad, and then my teachers… over time you get randomness of randomness, rather than randomness from order… if your starting point is continually variable, then the outcome from even just picking numbers from that pool, becomes more random…
I agree with Spivak that it would be terribly hard to have a switch that just hurts 1 player, or criteria that would tell the code to start making player XXXXX lose… Spivak is also right, by saying # of hands per hour makes a huge difference ( as well as look’n @ your cards while play continues )… One of the next biggest factors, is crappy play resulting in too many suckouts… this is directly tied to free chip poker… and the strategies that have been born from that environment…
So I don’t see any algorithm necessary… in real estate its always Location, Location, Location… well in almost everything else its Implementation, Implementation, Implementation… you can have the best idea, with crappy implementation just turn out… well crappy…