Seuntjies DiceBot -Multi-Site, multi-strategy betting bot for dice. With Charts!

[seuntjie]

Hi, guys, I have a quick question

What are the casinos with the fastest API in terms of maximum number of bets per second that the Seuntjies DiceBot works with? I want to test the strategy described in this thread (mostly academic interest but still), and in order to build a big enough sample I need more bets per unit of time. If someone has already tried out what I want to test there (and it didn't work out), let me know, still better in that thread directly (so as not to derail this one)

If it's for academic purposes, use the simulator built into DiceBot.

(If you're looking for more performance and are fairly tech savvy, clone and compile doormat: https://github.com/Seuntjie900/Doormat. It's simulator is much much faster)

[1715028052]

1715028052

[1715028052]

1715028052

[1715028052]

1715028052

[1715028052]

1715028052

[deisik]

Hi, guys, I have a quick question

What are the casinos with the fastest API in terms of maximum number of bets per second that the Seuntjies DiceBot works with? I want to test the strategy described in this thread (mostly academic interest but still), and in order to build a big enough sample I need more bets per unit of time. If someone has already tried out what I want to test there (and it didn't work out), let me know, still better in that thread directly (so as not to derail this one)

If it's for academic purposes, use the simulator built into DiceBot

Thanks for replying, I will try it

But I still want to know how real casinos rank up in terms of the metric described (bet speed). I think it will be interesting to find out. As far as remember, PrimeDice, for example, now limits bets to 1 roll per second, even though their autobet was way faster when they had first introduced it in circa 2014 (back in the day I lost like 1.5 BTC with it, huh). Right now, I'm running autobet at wolf.bet, and it is visibly faster than just 1 bet per second (actually pretty close to 2 bets per second)

(If you're looking for more performance and are fairly tech savvy, clone and compile doormat: https://github.com/Seuntjie900/Doormat. It's simulator is much much faster)

Can I compile it for Linux? What framework is it using (Qt would be fine)?

[seuntjie]

Can I compile it for Linux? What framework is it using (Qt would be fine)?

Yes. It's built using .net standard, there's no GUI for it yet. (It has a CLI that is somewhat limited that's built using .net core)

[kodark]

Where to report bugs?

There is a bug that, when the lua scripts stops for not having sufficient funds, if you deposit more and start again, it will go ahead with the next betting with a higher value or, when changing coins and pasting a new whole script with the correct basebet, it will use the previous basebet and so, you can be bankrupt because of this.

OP, it would be good if this bug would be solved because it cleared my balance at least 3 times before I learned it and thats the main reason I am not donating.

The bot isn't stopped unless it says "stopping" with a reason in the status bar. If you run out of funds, the bot retries the bet every 30 seconds. If you deposit, it will resume within 30 seconds of the funds being available in your account.

If you do stop it and then type start again to start betting, and it bets from where you left off, it's a problem with your script. Your script is supposed to set the starting bet when it's parsed.

See the tutorials on https://bot.seuntjie.com/programmermode.aspx

I do it, use function stop(), see an example:

 

Code:

 if balance < stoplosslimit then
         nextbet = basebet
         ching() 
          alarm()
          stop()
         
       end

My stoplosslimit is working as I tested it many times, but, when the martingale fails, it does not returns to the basebet.

And really, sometimes I stop it manually. The solution is close the bot and open again with a new script setting the basebet.

[kodark]

Hi, guys, I have a quick question

What are the casinos with the fastest API in terms of maximum number of bets per second that the Seuntjies DiceBot works with? I want to test the strategy described in this thread (mostly academic interest but still), and in order to build a big enough sample I need more bets per unit of time. If someone has already tried out what I want to test there (and it didn't work out), let me know, still better in that thread directly (so as not to derail this one)

Duckdice is the fastest.

[kodark]

Can I compile it for Linux? What framework is it using (Qt would be fine)?

Yes. It's built using .net standard, there's no GUI for it yet. (It has a CLI that is somewhat limited that's built using .net core)

seuntjie, How do I reset the time running in the stats?
resetstats() does not do the trick.

[seuntjie]

Can I compile it for Linux? What framework is it using (Qt would be fine)?

Yes. It's built using .net standard, there's no GUI for it yet. (It has a CLI that is somewhat limited that's built using .net core)

seuntjie, How do I reset the time running in the stats?
resetstats() does not do the trick.

are you using doormat? iirc doormat creates a new stats object when you reset stats and the time running should be contained in there. so the time running should reset in doormat.

If you're not using doormat, why did you quote a post about doormat to ask me that question?

In that case. Update your bot.

[seuntjie]

Where to report bugs?

There is a bug that, when the lua scripts stops for not having sufficient funds, if you deposit more and start again, it will go ahead with the next betting with a higher value or, when changing coins and pasting a new whole script with the correct basebet, it will use the previous basebet and so, you can be bankrupt because of this.

OP, it would be good if this bug would be solved because it cleared my balance at least 3 times before I learned it and thats the main reason I am not donating.

The bot isn't stopped unless it says "stopping" with a reason in the status bar. If you run out of funds, the bot retries the bet every 30 seconds. If you deposit, it will resume within 30 seconds of the funds being available in your account.

If you do stop it and then type start again to start betting, and it bets from where you left off, it's a problem with your script. Your script is supposed to set the starting bet when it's parsed.

See the tutorials on https://bot.seuntjie.com/programmermode.aspx

I do it, use function stop(), see an example:

 

Code:

 if balance < stoplosslimit then
         nextbet = basebet
         ching() 
          alarm()
          stop()
         
       end

My stoplosslimit is working as I tested it many times, but, when the martingale fails, it does not returns to the basebet.

And really, sometimes I stop it manually. The solution is close the bot and open again with a new script setting the basebet.

This sounds like your script doesn't set the same basebet when it's parsed as what you set when it stops.

[kodark]

Where to report bugs?

There is a bug that, when the lua scripts stops for not having sufficient funds, if you deposit more and start again, it will go ahead with the next betting with a higher value or, when changing coins and pasting a new whole script with the correct basebet, it will use the previous basebet and so, you can be bankrupt because of this.

OP, it would be good if this bug would be solved because it cleared my balance at least 3 times before I learned it and thats the main reason I am not donating.

The bot isn't stopped unless it says "stopping" with a reason in the status bar. If you run out of funds, the bot retries the bet every 30 seconds. If you deposit, it will resume within 30 seconds of the funds being available in your account.

If you do stop it and then type start again to start betting, and it bets from where you left off, it's a problem with your script. Your script is supposed to set the starting bet when it's parsed.

See the tutorials on https://bot.seuntjie.com/programmermode.aspx

I do it, use function stop(), see an example:

 

Code:

 if balance < stoplosslimit then
         nextbet = basebet
         ching() 
          alarm()
          stop()
         
       end

My stoplosslimit is working as I tested it many times, but, when the martingale fails, it does not returns to the basebet.

And really, sometimes I stop it manually. The solution is close the bot and open again with a new script setting the basebet.

This sounds like your script doesn't set the same basebet when it's parsed as what you set when it stops.

Is your primedice nick seuntjies ?

[seuntjie]

Is your primedice nick seuntjies ?

Just Seuntjie. The same as my forum username.

[anunnaki1202]

Hi,
Is anyway to keep history only 24h so the bot won't need save days behind?

[kodark]

The bot reads the profit wrong when the time pass after 24 hours.

[kodark]

Is your primedice nick seuntjies ?

Just Seuntjie. The same as my forum username.

When I will be in green again sure I will tip you anyway thanks for this great app.

[seuntjie]

Hi,
Is anyway to keep history only 24h so the bot won't need save days behind?

No

The bot reads the profit wrong when the time pass after 24 hours.

Can you elaborate?

[docthusinh]

Yeah... I suspect you might be confused by the 4.95% == 0.0495...

In this formula, you need to use a "decimal percentage"... This is basically the percentage you are using / 100. All the values should end up between 0 and 1.

So, if you are using a percentage of 1%, the decimal value is (1 / 100) => 0.01

0.495% => 0.495 / 100 => 0.00495
4.95% => 4.95 / 100 => 0.0495
10% => 10 / 100 => 0.1
56.7% => 56.7 / 100 => 0.567
100% => 100 / 100 => 1

Because the start percentage is for "wins" and we're after "losses"... we then use (1-p) to get the loss percentage... so the formula, for 4.95% should look something like:

=abs(ln(4166576)/ln(1-0.0495))

What site are you using that is given you these 1700-1900 loss streaks?

Yes I am a bit confused in displaying percentage number in decimal. It is 0.495% aka 0.00495, =abs(ln(4166576)/ln(1-0.00495)) = 3071.68 (by the use of formula). And actual result as mentioned 1700-1900 are easy to see, above 2000 is "rare" in which i withness 3 or 4 time at 2000+ and once at 2367 (the biggest I've seen).

For sites: anysite would yield the same thing as long as they have "provably fair" but I've played on Freebitco.in and Bitdice.me. You can check for my profit on Bitdice since it can show profiles.
And btw: I am not betting with this bot but my private one (with credit to Seuntjie in which i copied his code specifically the login & send bet command/ syntax to talk with the site and implement my own logics).

[seuntjie]

And btw: I am not betting with this bot but my private one (with credit to Seuntjie in which i copied his code specifically the login & send bet command/ syntax to talk with the site and implement my own logics).

If you're only using the login and bet functionality, why not just use the bot's programmer mode to write your own logic? then you don't need to maintain any other code to ensure compatibility with the site and you can switch to any number of sites without having to change your code.

[docthusinh]

And btw: I am not betting with this bot but my private one (with credit to Seuntjie in which i copied his code specifically the login & send bet command/ syntax to talk with the site and implement my own logics).

If you're only using the login and bet functionality, why not just use the bot's programmer mode to write your own logic? then you don't need to maintain any other code to ensure compatibility with the site and you can switch to any number of sites without having to change your code.

The reason is I need the least memory footprint as possible (constantly 10MB RAM usage is kept after a month or a few months run) in which a console program is best suite. Secondly I need to define some static and dynamic variables in which I am not sure how to keep it right in LUA script and also save that in case of restart or abnormal power outage. Thirdly alot of if and else as well as loop is used and lastly resolving the issues with error from site (HTTP 404/502) in which I let it just wait (in a loop) until the site is back to normal and continue playing without extra babysitting it.

[felicita]

thanks iam using your bot on just-dice to enable auto roll there.
Is there any plans to make it for Linux OS ?


regards

This is planned for v4 of the bot but is not guaranteed and I do not have an ETA.

iam still hot for a linux application XD
I hope you have enough time for v4 soon.

kind regards

[seuntjie]

The reason is I need the least memory footprint as possible (constantly 10MB RAM usage is kept after a month or a few months run) in which a console program is best suite. Secondly I need to define some static and dynamic variables in which I am not sure how to keep it right in LUA script and also save that in case of restart or abnormal power outage. Thirdly alot of if and else as well as loop is used and lastly resolving the issues with error from site (HTTP 404/502) in which I let it just wait (in a loop) until the site is back to normal and continue playing without extra babysitting it.

Memory: Fair enough, though in my experience, DiceBot doesn't really increase the amount of memory it uses once it's running and the chart and bet log are at their maximums (Which can be decreased in the settings tab).
Variables: Variables can just be defined as in any other language and you can use lua io library to save them to a file or read them from a file.
If-else/loops: this is the same for any programming language and shouldn't dissuade you from using one or another
Error from site: DiceBot automatically retries the most recent bet every 30 seconds if there is an error, and with the way freebitco.in works, it should just resume betting even after several hours of downtime or maintenance.

[HCP]

I guess some people just like to reinvent wheels

But full credit to them for going to the effort of creating their own setup... Still seems like a lot of work, for what will still likely result in a loss of money... and time Not sure I'd have the patience to have a bot running for a month!