Coming from a background of working with security for financial institutions (Banks, Creditcard companies and so on), I'd highly recommend re-evaluating this implementation from a liability perspective.
Feel free to send me a message (contact information in profile), and I can share advise on how the banking and creditcard industry deals with cross authentication and verification.
Though it did (in the simulation). The accumulated winnings with the limits on bankrupt and cashing out at 1500 created a over time win percentage in a otherwise negative-biased game?
The game I picked was "Casino War" [ http://wizardofodds.com/games/casino-war/ ], as it was very quick to implement in a few lines of code. I selected the base rules as played in Garden City Casino [Bay Area] (50c drop per every $100), and came up with the following:
Game/House Rules:
- 6 deck of cards.
- Played until 1/2 is gone.
- 50c drop for every $100 [Example: $200 bet costs $1, $300 $1.5.]
Betting Rules:
- Base Bet is always 1% of current wallet, at starting point - $10.
- If the proportional bet can not be covered by wallet, the round is surrendered and the player waits until re-shuffle. [Example: Lost up to $500, next bet is $1000, wallet has $700, game ends/waits and the player accepts a loss of $300.]
- Bets are doubled on loss as defined in the Proportional betting link.
Here's my data, though I believe something is wrong due to its results:
- I ran the initial program, as is, expecting the player to play one round every day for 10 years.
- Losses and earnings were added together.
- The average win % went to 58.4%.
- The average cash win [the times the player didn't go bankrupt] was $1590.
- Max loss [consecutive] cash $2980. [Bankroll covered over multiple sessions]
* A key point here is the average cash win. It was highly consistent and never below 1500.
I then added a factor that stated in the software:
- If winnings are at $1500, the player stops, takes the winnings and waits for a re-shuffle.
* Win percentage went up to 64.8% !
If anyone is interested, I'd be happy to share/pastebin the code or similar. Overall, due to the percentages I'm assuming something is wrong with my assumptions/gameplay, but so far an interesting experiment.
Feel free to send me a message (contact information in profile), and I can share advise on how the banking and creditcard industry deals with cross authentication and verification.