Greasy Fork

Hello. Now the problem is gone, but can you tell me please wich var HIGH_LOW = ?; should I set. for playing with 1.80 odds. Wich will be the most efficent?

Im loving this script even though i turn off the multiplier game, from past experience and some posts here, scripted gambling will never work long term if you leave it running constantly, because its gambling and eventually you will lose everything. Because the probability is never on your side.

But here is a strategy i been using that seems to work quite well, i do it manually sometimes while the script still runs. Lotta people have probably already used this.
Leave the multiplier as 2.0 (47.5% win chance). And choose one of HI or LO and stay with it, and have the bet as the minimum 1 Satoshi. Keep betting until you see like 3-4 losses in a row. Now the next one you try to bet bigger, like 100 satoshi. After several losses in a row its unlikely you will lose even more in a row, but from here if you lose you keep doubling until you win. So yes, you want to have enough in your stack to account for more losses in a row, and when you win you can stop.

But dont keep doing this constantly, if youve lost a lot, then maybe comeback in a couple hours, double it and try again (if you have enough). Or just accept the loss and go back to 1 satoshi.

This can probably be scripted or something but I just do this manually once in a while.

Hi kafarabo,

the script uses exactly the logic you say ;)

1, it waits N hours between one play session and the next one. I set 24 hours as default.
2, it plays with a probability P, to avoid to play exaxctly every 24 hours. Sometimes it is 24, sometimes it's 30h, or 27... random
3, you can set the play mode you were speaking about. GAME_TYPE = 1 is exactly what you said. It waits N losses before to begin to bet.
4, better then this, it's GAME_TYPE=2. That's what has better results right now based on my tests. It waits 3-4-5-6-N losses in a row. Say, ie, 4. After that, it waits the first win. After that, it plays martingale. For example saying L lost, W win P play, if you set MIN_LOSSES_BEFORE_PLAY=4 as we said in our example, schema could be LLLLLLWP or LLLLLLLLLLWP.
So imagine bet 1/2/3/(NSmall) sats till it gets 9 losses ina row, then wait the next win, then bet 1024, 2048, 4096 and 8182 and stop.. would be weird and really unusual to see something like LLLLLLLLLWLLLLL ;/

I'm finding that on the second losing strike there are always less consecutive losts, even if you play a lot.
But I'm also finding in those days, that if you wait 24 hours, then you wait the first 8 losts in a row, then you wait a win, you get quite always one lost and one win after that.

Accepting the lost, as you say, it's always the best method I completely agree with you.

Some more infos about config the youtube video https://youtu.be/kQoTjoN_lVg
Some article in the blog with stats and ideas and conf example, will follow in the next times
hope it helped

daniele