Alpha version (build 14) of Seuntjies DiceBot is available at seuntjie.com/dicebot/dicebot-v3-alpha-b14.zip

fixes issues at sd with the incorrect balance, should fix the 999dice issue mentioned above. If it does not, enable bot speed and set it to 3 bets/s or slower. added support for bitdice, fixed the simulation error mentioned above.

This was indeed an error, Thanks for pointing it out, it has been fixed.

I have not experienced freezing with the latest few versions.  Betting at PD has been really stable for quite a while now. My bot was betting at prc for almost 2 days before dean took the site down for maintenance without any problems. When he brought the site back online, I simply logged in and continued betting, didn't have to restart the bot or anything.

But I guess vouching for my own program doesn't mean much right?

I couldn't have explained it better myself 

I will look into this to get it fixed in the next version.

my bot is dicebot (seuntjies DiceBot), and please don't use build 12, it's a bit unstable at dadice

seuntjie.com/dicebot/dicebot-v3-alpha-b13.zip is the latest build and is much more stable.


As for the speed of betting: According to steve the api is limited to 2/bets, although i've never been able to achieve more than about 0.75 bets/s. Also, Sid (dadice_dev) asked me to add a throttle to the bot that doesn't allow the placing bets withing 0.7 seconds of each other.

The bot speed cannot speed up the bot, it can only slow it down. If the bot speed option is disabled, the bot bets as fast as the site, your computer and your internet allows it to bet.

The problem with this, is after a few days or weeks, you're going to realize this doesn't work as well as you hoped, so you want to try another level, have it changed the rate of stepping a second time, then a third, then a fourth. Point is, It's not practical for me to make these changes to the bot every time. So instead I added this awesome little thing to the bot called the programmer mode. This allows you to do these kind of customizations yourself.

Yes reverse labouchere works. Labouchere isn't supposed to keep on betting indefinitely. Once it works through your list of bets, it should stop. Unless you set it to reset on a completing a series. also, the shorter your list of bets, the fewer bets it will place.

there are two reset on xxxx btc loss.
the first: reset after xxxx btc STREAK loss -> if you're on a losing streak and lose xxxx btc IN THAT STREAK, it resets
the second: reset after xxxx btc loss -> if your session loss goes below the limit, it resets

if you're doing a pure martingale, the two settings are basically identical, but for other settings, like dAlembert, or a martingale with reset parameters for losing streaks their functions do differ.


part 2: it should.

Not all of them, but the popular ones. At the time of writing, the bot works at Just-dice, PrimeDice, PocketRocketsCasino, 999Dice, SafeDice, Dadice and Roll In. And I'm adding bitdice in the next few days

You're using a very old version of the bot. I suggest upgrading the the latest one:
Alpha version (build 13) of Seuntjies Dicebot version 3 is available at http://seuntjie.com/dicebot/dicebot-v3-alpha-b13.zip


But for the version you're using. For the secret url, just use https://just-dice.com, when the site is loaded, go to the account tab and log in there. From then on, the bot will load the login screen like it does in your normal browser.

Are you sing the latest build (build 13)? I have no problem playing on prc and never had the bot freeze on pd either.

make sure you download the latest alpha version, then select dadice from the "site" menu at the top.
Note: for dadice, you log in using your username and api key, NOT username and password. To get your api key, log in to the site, open the menu on the left hand side, expand "account", then go to "settings". Enable your api in the popup window and copy the api key.

Alpha version (build 13) of Seuntjies Dicebot version 3 is available at http://seuntjie.com/dicebot/dicebot-v3-alpha-b13.zip

This has to do with the way and which data gets transfered after a bet.

A lot of sites, like PD, send data regarding the bet, the player, and the site after a bet. others, like safedice, only send the bet data and rely on periodic updates for the other stats. this has the following implications.

PD always shows the correct stats after a bet, because the latest balance, player stats and site stats are sent along with the site. The server calculates all of the info and is then sent to the client, so it is guaranteed to be correct. The down side of this is if you log in at multiple locations at the same time and withdraw/bet, only the instance that placed the last withdraw/bet is up to date.

At SD, on the other hand, the server only sends info regarding the bet in response to a bet, then the client needs to calculate the new balance and stats, with the occasional request for the *correct* data from the server. every 15 seconds or so, every client should have requested the latest stats, so all clients should be pretty much up to date. This means slightly less load on the server, but could cause some inaccuracies. For example if you are betting, and receive a deposit, but the occasional pull of data fails because of a network error, and you go on a losing streak, the client might think you have a negative balance (because it doesn't know of the deposit), while the server knows that you balance is in fact positive.

I've encountered this with my bot on a few instances where the balance isn't updated after a deposit or a withdrawal from somewhere else and it ends up being higher or lower than it should.

Easiest way is to use the programming mode with a little lua script. There should be a basic one similar to what you want a few pages back in this thread.

I'll take a look at the balance thing for xmr.



My pleasure. Donations are always welcome


Do you have .net 4.5 installed? What does the error say? .net has a lot of error messages for a lot of different things, so ".net error" doesn't say much.


Try disabling zig zag in that version.
or try the newer version: Alpha version (build 13) of Seuntjies Dicebot is available at seuntjie.com/dicebot/dicebot-v3-alpha-b13.zip

New alpha version released with support added for rollin.io and a log of bug fixes for dadice:

Alpha version (build 13) of Seuntjies Dicebot is available at seuntjie.com/dicebot/dicebot-v3-alpha-b13.zip

1) The picture on the forum is about a year old and was made when doge-dice was still active. You can't play in doge on just-dice. Also, the version that resembles that picture is nearly 6 months old. You should try the newer version. See below for a link

2) set your chance to the corresponding payout. for a 2x payout, your chance must be 49.5% to win. to calculate what your chance should be, take 99/payout. for example, for a 10x payout, your chance should be set to (99/10)=9.9%

3) this question doesn't make sense. I think you should read up on how the betting strategies work.

The best settings are what works best for you. There is no global best settings.

It might be something to do with your password. If you have any non utf-8 characters in your password, you won't be able to log in with the bot.

as for your questions:

1. I tested cpu usage and the highest cpu usage I got was 2% at PRC. PD was around 1.5% and JD was just below 1%. Most of the time is spent waiting for a response from the server. Of course a higher betting speed means higher cpu usage, but I cant see it going above about 2.5%.

2. Bet less or reduce the betting speed using the bot speed setting. The bot communicates purely in post data and json with the sites, so no, there's no way to reduce the data usage. The bot sends and receives data constantly while betting, it's almost like downloading a file.
2.1: You can edit the source and disable the chat at primedice. That should reduce data consumption somewhat

If you run more than one instance from the same directory, it's likely the bot will crash. Both bots will try to write to and read from the same database file for the bets, and that could cause some issues. It's more likely that this is causing the bots to crash than the cpu usage.

Glad you got it working. Sorry I couldn't help you more, I have no idea why your one account didn't work.

That should be fixed in the next build yes.



It's very odd that you can't connect to JD. Have you tried the latest build of the bot (build 12)? I recently updated the API the bot uses to connect to JD to make it a bit more stable, so maybe that works. And yes, the bot communicates on a fundamentally different way with the sites in v3 from v2, but it still uses https, it won't get blocked by your firewall as long as you can browse the internet. Unfortunately there is no debug you can run at this time.

The only issue I can think of is that it for some odd reason tries to connect to doge-dice instead of JD, but you would need to have changed some of the code for that to happen. If you haven't yet, try build 12 and see if that works better. I'm sorry you're having these issues.
Alpha version (build 12) of Seuntjies Dicebot is available at seuntjie.com/dicebot/dicebot-v3-alpha-b12.zip

Well i haven't experienced the stopping problem, but I'm working on it. Should be soon

This one can change the server seed. I've been planning on allowing it to set the client seed as well, Just haven't gotten around to it