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

[bajing]

is this actually helpful? isnt martingale a flaw system? since it goes by bankroll.

yes sometimes helpful use martingale, you can profit fast but dont play to long when you use martingale strategy

[michael23]

how to write a zig zag betting on programming mode?
i try this codes

Code:

pls=0
basebet=xxxx
chance=xxxx
 
function dobet()
 
if currentstreak<= 0 then
pls = currentstreak
end

if currentstreak<= 0 and (previousbet>=xxxx) and (pls <= -1) then
nextbet=basebet
chance=xxxx
else if currentstreak == 1 and (previousbet>=xxxx) and (pls <= -1) then
nextbet=previousbet*2
chance=xxxx
else if currentstreak == 1 and (previousbet>=xxxx) and (pls <= -1) then
nextbet=previousbet*2
else if currentstreak == 1 and (pls <= -3) then
nextbet=previousbet*6
else if currentstreak == 1 and (pls <= -2) then
nextbet=previousbet*4
else if currentstreak >=2 and (previousbet>=xxxx) then
nextbet=basebet
chance=xxxx
else if currentstreak >=3 then
nextbet=basebet
end
end
end
end
end
end
end

end

but it only betting high, what should i add to make it betting hi and lo, or its not possible?

thanks

There's a variable that you can set to determine whether the next bet will be high or low, namely bethigh. If bethigh is true, the next bet will be high, if betigh is false, the next bet will be low.

if you want to swich on each roll, just add

Code:

bethigh = !bethigh

in the dobet function.

if you have criteria it should meet, for example losing streak of 3, just a simple if statement.

Code:

if zig zag criteria then
bethigh = !bethigh
end

it works, this is getting more exciting thanks a lot

[webchris]

Sorry if this has been discussed before. Is there an auto-reconnect feature I am not seeing?

Trying to get this to work with just-dice and it keeps getting stuck after connection issues. Just clicking "roll hi" or low at site seems to fix most of the time but if I'm not sitting there it just stops. Bot seems really cool though.

Hope zig-zag is fixed in next release

[seuntjie]

is this actually helpful? isnt martingale a flaw system? since it goes by bankroll.

All gambling strategies are flawed and will bust eventually at a casino with an house edge. Winners know when to stop.

Sorry if this has been discussed before. Is there an auto-reconnect feature I am not seeing?

Trying to get this to work with just-dice and it keeps getting stuck after connection issues. Just clicking "roll hi" or low at site seems to fix most of the time but if I'm not sitting there it just stops. Bot seems really cool though.

Hope zig-zag is fixed in next release

The auto reconnect depends on which site and which version of the bot you're using.
It sounds like you're running 2.5.5, probably on 999dice. It has an issue there where it fails to send the bet for some reason at times. Annoying as it is, v 2.5.5 is not getting any maintenance, also mean zig zag isn't getting fixed for that version.

You can try the version 3 alpha bot. It is much more awesome than 2.5.5.
If you are using 999dice, I suggest build 10: http://seuntjie.com/dicebot/dicebot-v3-alpha-b10.zip
for any other site, there's build 11: http://seuntjie.com/dicebot/dicebot-v3-alpha-b11.zip

[chilly2k]

is this actually helpful? isnt martingale a flaw system? since it goes by bankroll.

All gambling strategies are flawed and will bust eventually at a casino with an house edge. Winners know when to stop.

Sorry if this has been discussed before. Is there an auto-reconnect feature I am not seeing?

Trying to get this to work with just-dice and it keeps getting stuck after connection issues. Just clicking "roll hi" or low at site seems to fix most of the time but if I'm not sitting there it just stops. Bot seems really cool though.

Hope zig-zag is fixed in next release

The auto reconnect depends on which site and which version of the bot you're using.
It sounds like you're running 2.5.5, probably on 999dice. It has an issue there where it fails to send the bet for some reason at times. Annoying as it is, v 2.5.5 is not getting any maintenance, also mean zig zag isn't getting fixed for that version.

You can try the version 3 alpha bot. It is much more awesome than 2.5.5.
If you are using 999dice, I suggest build 10: http://seuntjie.com/dicebot/dicebot-v3-alpha-b10.zip
for any other site, there's build 11: http://seuntjie.com/dicebot/dicebot-v3-alpha-b11.zip

Seuntjie,

    He mentioned Just-dice.  Very erratic behavior on there.  I've used both B10 and B11 and stay running anywhere from 1 minute to several hours.  Usually around 20-30 minutes before it hangs.  If I go to the betting tab on the website, I can see the result of the last bet, but the bot doesn't get it.  If I just place a bet manually from the bot, it picks up where it left off and continues.  It seemed to get better when Doog added the throttle (bet delay) back in.  But it seems that was short lived.  It would make sense if you had a return last bet result API call.  Then set a timer in the bot for x seconds and it the timer pops call for the last result and see if you missed it.     

    I've got a problem now on B10 where I can't reset the stats.  I've found that after several thousand bets, betting slows way down.  If I reset the chart that helps a lot, but I prefer to also reset the stats at that point.  (It makes the new chart more dramatic...  )  for some reason it's not working now.     

   All in all an excellent bot.  Keep up the great work. 
 
   Have you thought about creating a separate thread for programmer mode enthusiasts?  I've been having a blast with it.  One thing I love is that you can set variables on the LUA console while the bot is running.  I can change my risk level on the fly, when I'm feeling lucky.  or dial it back down when I want to just let the bot run. 

            Thanks for all of you hard work...     

[seuntjie]

Seuntjie,

    He mentioned Just-dice.  Very erratic behavior on there.  I've used both B10 and B11 and stay running anywhere from 1 minute to several hours.  Usually around 20-30 minutes before it hangs.  If I go to the betting tab on the website, I can see the result of the last bet, but the bot doesn't get it.  If I just place a bet manually from the bot, it picks up where it left off and continues.  It seemed to get better when Doog added the throttle (bet delay) back in.  But it seems that was short lived.  It would make sense if you had a return last bet result API call.  Then set a timer in the bot for x seconds and it the timer pops call for the last result and see if you missed it.     

    I've got a problem now on B10 where I can't reset the stats.  I've found that after several thousand bets, betting slows way down.  If I reset the chart that helps a lot, but I prefer to also reset the stats at that point.  (It makes the new chart more dramatic...  )  for some reason it's not working now.     

   All in all an excellent bot.  Keep up the great work. 
 
   Have you thought about creating a separate thread for programmer mode enthusiasts?  I've been having a blast with it.  One thing I love is that you can set variables on the LUA console while the bot is running.  I can change my risk level on the fly, when I'm feeling lucky.  or dial it back down when I want to just let the bot run. 

            Thanks for all of you hard work...     

Oh yeah he did. I missed that completely, sorry.

On JD in the alpha versions, the stop is deliberate. It sometimes happens that the bet is executed but gets stuck on the server or lost on in the internet somewhere. So the bot stops betting instead of retrying the bet for a very good reason. Imagine the following scenario. You Martingale with a base bet of 1 clam.
1:L
2:L
4:L
8:L
16:L
32:L
64:L
128:L
256:L
512:L
1024:L
2048:L
4096:W, but bet gets lost.
4096:L Bot Retries the last bet
8192:L
You Bust.

So while it is annoying, It is in the best interest of the user/player that the bot stops in this case.
It would be ideal to have the bet method return the bet result, but unfortunately, that's not how JD socket is set up, so while i can change the api to return the object, it would not be any more reliable than it already is. Instead, it would just complicate things in the api and slow it down as a whole.


the reset stats button is a bug in b10, it's been fixed in b11.

Starting a thread for the programmer mode has been suggested to me before. I have no intention of starting one myself, but feel free to do so yourself and post the link to it in this thread. I'll probably keep an eye on it.

[chilly2k]

Seuntjie,

    He mentioned Just-dice.  Very erratic behavior on there.  I've used both B10 and B11 and stay running anywhere from 1 minute to several hours.  Usually around 20-30 minutes before it hangs.  If I go to the betting tab on the website, I can see the result of the last bet, but the bot doesn't get it.  If I just place a bet manually from the bot, it picks up where it left off and continues.  It seemed to get better when Doog added the throttle (bet delay) back in.  But it seems that was short lived.  It would make sense if you had a return last bet result API call.  Then set a timer in the bot for x seconds and it the timer pops call for the last result and see if you missed it.     

    I've got a problem now on B10 where I can't reset the stats.  I've found that after several thousand bets, betting slows way down.  If I reset the chart that helps a lot, but I prefer to also reset the stats at that point.  (It makes the new chart more dramatic...  )  for some reason it's not working now.     

   All in all an excellent bot.  Keep up the great work. 
 
   Have you thought about creating a separate thread for programmer mode enthusiasts?  I've been having a blast with it.  One thing I love is that you can set variables on the LUA console while the bot is running.  I can change my risk level on the fly, when I'm feeling lucky.  or dial it back down when I want to just let the bot run. 

            Thanks for all of you hard work...     

Oh yeah he did. I missed that completely, sorry.

On JD in the alpha versions, the stop is deliberate. It sometimes happens that the bet is executed but gets stuck on the server or lost on in the internet somewhere. So the bot stops betting instead of retrying the bet for a very good reason. Imagine the following scenario. You Martingale with a base bet of 1 clam.
1:L
2:L
4:L
8:L
16:L
32:L
64:L
128:L
256:L
512:L
1024:L
2048:L
4096:W, but bet gets lost.
4096:L Bot Retries the last bet
8192:L
You Bust.

So while it is annoying, It is in the best interest of the user/player that the bot stops in this case.
It would be ideal to have the bet method return the bet result, but unfortunately, that's not how JD socket is set up, so while i can change the api to return the object, it would not be any more reliable than it already is. Instead, it would just complicate things in the api and slow it down as a whole.


the reset stats button is a bug in b10, it's been fixed in b11.

Starting a thread for the programmer mode has been suggested to me before. I have no intention of starting one myself, but feel free to do so yourself and post the link to it in this thread. I'll probably keep an eye on it.

   I agree about just replacing the bet, But if there was a way for the bot to request the last result from the server.  Then the bot could check to see if the last bet was processed or not.  I'm assuming based on everything I've seen so far, that the result is just not being returned.  Whether it's something on the JD side, or something getting lost in windows.  I can see that the bet was placed, according to the JD website, but the bot gets hung, and the results never show up. 

Cool on the reset stats.

   And I'll start a new thread at some point.  When I get a few spare cycles. 

[chaoman]

Can somebody eli5 this for me? I want to set it up so it will run a 4 step matingale. If the 4th step looses it will restart and keep going. Any help appreciated.

[seuntjie]

   I agree about just replacing the bet, But if there was a way for the bot to request the last result from the server.  Then the bot could check to see if the last bet was processed or not.  I'm assuming based on everything I've seen so far, that the result is just not being returned.  Whether it's something on the JD side, or something getting lost in windows.  I can see that the bet was placed, according to the JD website, but the bot gets hung, and the results never show up. 

Cool on the reset stats.

   And I'll start a new thread at some point.  When I get a few spare cycles. 

I'll dig around a bit for a way of doing that later this week. The only way I know of to get your last rolls is to log out and back in again. I'd prefer not to use this as far as possible. It gets lost somewhere between JD and JDCAPI. It's entirely possible that JDCAPI loses it, but consider that sometimes a bet doesn't come through on the site as well. I'll definitely look at improving the stability of JDCAPI once i have time to work on it again.

Can somebody eli5 this for me? I want to set it up so it will run a 4 step matingale. If the 4th step looses it will restart and keep going. Any help appreciated.

Just switch the bot to advanced mode (assuming you're using v3 alpha). in the stop conditions tab, enable "reset after xxxx losses in a row" and set the value to 4.

[webchris]

Oh yeah he did. I missed that completely, sorry.

On JD in the alpha versions, the stop is deliberate. It sometimes happens that the bet is executed but gets stuck on the server or lost on in the internet somewhere. So the bot stops betting instead of retrying the bet for a very good reason. Imagine the following scenario. You Martingale with a base bet of 1 clam.
1:L
2:L
4:L
8:L
16:L
32:L
64:L
128:L
256:L
512:L
1024:L
2048:L
4096:W, but bet gets lost.
4096:L Bot Retries the last bet
8192:L
You Bust.

So while it is annoying, It is in the best interest of the user/player that the bot stops in this case.
It would be ideal to have the bet method return the bet result, but unfortunately, that's not how JD socket is set up, so while i can change the api to return the object, it would not be any more reliable than it already is. Instead, it would just complicate things in the api and slow it down as a whole.


the reset stats button is a bug in b10, it's been fixed in b11.

Starting a thread for the programmer mode has been suggested to me before. I have no intention of starting one myself, but feel free to do so yourself and post the link to it in this thread. I'll probably keep an eye on it.

I understand what you are saying about its better that the bot stops than to possibly double a bet or skip a win. Running the bot for just a day I can tell it's not really usable with JD currently, unless you are sitting there watching it and refreshing the page after every hang. I'm using the latest stable build, but if the alpha is better I will try it. What would be ideal, would be for the bot to automatically refresh JD if it hasn't received a response after X seconds, check the bets to match up the last, then continue. If you are worried about the delayed bet issue, you could mitigate that in two ways... have a minimum time to wait between placing a bet, waiting for response, then re-attempting. If you wait 30+ seconds, it would seem pretty safe to assume the previous bet did not go thru. Secondly, you could have a setting that does not re-attempt betting automatically above a threshold. I don't care if the bot doubles a .00001 clam bet by mistake if it means the bot will run and not wait for 4 hours until I get to my PC to see it stuck. But if its up to 50 clams, sure I don't mind waiting on me.

Hope that makes sense!

[chilly2k]

Oh yeah he did. I missed that completely, sorry.

On JD in the alpha versions, the stop is deliberate. It sometimes happens that the bet is executed but gets stuck on the server or lost on in the internet somewhere. So the bot stops betting instead of retrying the bet for a very good reason. Imagine the following scenario. You Martingale with a base bet of 1 clam.
1:L
2:L
4:L
8:L
16:L
32:L
64:L
128:L
256:L
512:L
1024:L
2048:L
4096:W, but bet gets lost.
4096:L Bot Retries the last bet
8192:L
You Bust.

So while it is annoying, It is in the best interest of the user/player that the bot stops in this case.
It would be ideal to have the bet method return the bet result, but unfortunately, that's not how JD socket is set up, so while i can change the api to return the object, it would not be any more reliable than it already is. Instead, it would just complicate things in the api and slow it down as a whole.


the reset stats button is a bug in b10, it's been fixed in b11.

Starting a thread for the programmer mode has been suggested to me before. I have no intention of starting one myself, but feel free to do so yourself and post the link to it in this thread. I'll probably keep an eye on it.

I understand what you are saying about its better that the bot stops than to possibly double a bet or skip a win. Running the bot for just a day I can tell it's not really usable with JD currently, unless you are sitting there watching it and refreshing the page after every hang. I'm using the latest stable build, but if the alpha is better I will try it. What would be ideal, would be for the bot to automatically refresh JD if it hasn't received a response after X seconds, check the bets to match up the last, then continue. If you are worried about the delayed bet issue, you could mitigate that in two ways... have a minimum time to wait between placing a bet, waiting for response, then re-attempting. If you wait 30+ seconds, it would seem pretty safe to assume the previous bet did not go thru. Secondly, you could have a setting that does not re-attempt betting automatically above a threshold. I don't care if the bot doubles a .00001 clam bet by mistake if it means the bot will run and not wait for 4 hours until I get to my PC to see it stuck. But if its up to 50 clams, sure I don't mind waiting on me.

Hope that makes sense!

    I agree with your frustration.  I have yet to see a bet not go through.  Every time I check the bot I can see it made a bet and is waiting for a response.  When I check my bets on JD I can see the result of bet the bot is waiting on.  For a straight martingale you might be able to just lose the bet, but for most of the stuff I'm playing around with I would rather get the correct info.  

   For myself it doesn't sound to difficult.   I could imagine an API call to get result passing in a nonce.  Then the bot could check and see if thats the one it's waiting for.  Or a get last result call.  

    How easy it is to make suggestion when you don't know what the hell your talking about....    <-- that's directed at me... 

I'm sure Seuntjie will figure it out.  

[chaoman]

   I agree about just replacing the bet, But if there was a way for the bot to request the last result from the server.  Then the bot could check to see if the last bet was processed or not.  I'm assuming based on everything I've seen so far, that the result is just not being returned.  Whether it's something on the JD side, or something getting lost in windows.  I can see that the bet was placed, according to the JD website, but the bot gets hung, and the results never show up. 

Cool on the reset stats.

   And I'll start a new thread at some point.  When I get a few spare cycles. 

I'll dig around a bit for a way of doing that later this week. The only way I know of to get your last rolls is to log out and back in again. I'd prefer not to use this as far as possible. It gets lost somewhere between JD and JDCAPI. It's entirely possible that JDCAPI loses it, but consider that sometimes a bet doesn't come through on the site as well. I'll definitely look at improving the stability of JDCAPI once i have time to work on it again.

Can somebody eli5 this for me? I want to set it up so it will run a 4 step matingale. If the 4th step looses it will restart and keep going. Any help appreciated.

Just switch the bot to advanced mode (assuming you're using v3 alpha). in the stop conditions tab, enable "reset after xxxx losses in a row" and set the value to 4.

Thank you for your response. I set up the bot in martingale mode. I selected reset after 3 losses. However this is the behavior of the bot.

1st loss
bet 100
2nd loss
bet 200
3rd loss
bet 400
4th loss
bet 200.

How can I make the 4th loss bet 100. I don't know why it is betting 200.

[chaoman]

I fixed the issue by using a different option instead of the reset after losses.

after 3 losses in a row change bet to 100 satoshi.

Edit:

even after selecting after 3 losses in a row change bet to 100 satoshi the bot will sometimes make an 800 satoshi bet which should never happen. This is on 999dice. Help please.

[chilly2k]

   Bot stopped working.  Using build11 on Just-dice.  Bot hung as usual.  When I tried to get it going again, the bot seems to not be getting any replies from JD.  I tried a few manual bets from the bot, and a few on the JD website, nothing got it going again.  I tried shutting it down and restarting, and then rebooted the PC and started fresh, still no go.

   As an aside, I filled in my userid/password in the autologon panel.  I saved it, and it shows up when I look at the setting panel, but it doesn't seem to do anything.  
when I first start the bot, I get my JD site stats including balance, as if I'm logged in, but the bottom status bar on the bot says I'm disconnected the login panel is blank, and the login button is active.    Also the manual betting is inactive.  All buttons are greyed out.

   Are there any files that save any kind of state that might be a problem.  Something I can delete?  

In programmer mode, I can see that my program is getting control to init stuff prior to the dobet function.  The ninitial bet is placed, based on the JD website, but the dobet function is not called with the results. 

[webchris]

I think the best fix for JD would be some type of auto-reconnect feature. My bot just breaks after a random time... could be 5 mins, could be 2 hours. But at some point it stops for any number of connection issues and JD has to be refreshed to fix. If there is no response for a certain amount of time, I think the bot should refresh the page and attempt to resume. Maybe have this as an option for those of us who would want that, and that way it wouldn't have those adverse affects for others who would not want this feature.

[seuntjie]

  Bot stopped working.  Using build11 on Just-dice.  Bot hung as usual.  When I tried to get it going again, the bot seems to not be getting any replies from JD.  I tried a few manual bets from the bot, and a few on the JD website, nothing got it going again.  I tried shutting it down and restarting, and then rebooted the PC and started fresh, still no go.

   As an aside, I filled in my userid/password in the autologon panel.  I saved it, and it shows up when I look at the setting panel, but it doesn't seem to do anything.  
when I first start the bot, I get my JD site stats including balance, as if I'm logged in, but the bottom status bar on the bot says I'm disconnected the login panel is blank, and the login button is active.    Also the manual betting is inactive.  All buttons are greyed out.

   Are there any files that save any kind of state that might be a problem.  Something I can delete?  

In programmer mode, I can see that my program is getting control to init stuff prior to the dobet function.  The ninitial bet is placed, based on the JD website, but the dobet function is not called with the results. 

Thanks for pointing this out, I'll have a look at the auto login stuff to make sure it works every where. If you want to clear your settings, delete the folder located at c:\users\<yourusername>\appdata\roaming\dicebot2

Easiest way to get to this folder is to press the windows key + R. This will open the run prompt. Enter %appdata% (with the percentage signs) and click run. This should open the c:\users\<yourusername>\appdata\roaming\ folder.
Now just delete the dicebot2 folder (while the bot is closed)

I think the best fix for JD would be some type of auto-reconnect feature. My bot just breaks after a random time... could be 5 mins, could be 2 hours. But at some point it stops for any number of connection issues and JD has to be refreshed to fix. If there is no response for a certain amount of time, I think the bot should refresh the page and attempt to resume. Maybe have this as an option for those of us who would want that, and that way it wouldn't have those adverse affects for others who would not want this feature.

Again, it sounds like you're using version 2.5.5, which is very old and i'm not working on it anymore. But, that version does in fact have a auto refresh. Should it place a bet and fail to get the response after 2 minutes, It will refresh the page and try to get the result of the bet. If that doesn't work, there's nothing the bot can really do other than stop betting.

Dooglus said he's adding (might be done by now) a way for a client to get the result of the last bet it made, because this is a problem the site as a whole is facing, not just the bot. Once he's added that, I'll add it to JDCAPI and the alpha version of the bot. That should greatly increase stability of both.

[Jackolantern]

May add one for https://rollin.io/ one day ? It would be really interesting

[seuntjie]

May add one for https://rollin.io/ one day ? It would be really interesting

If they have an API and you or the site owner (or anyone else) is willing to pay the standard 0.5Btc fee for adding the site to the bot

[LiQuidx]

May add one for https://rollin.io/ one day ? It would be really interesting

If they have an API and you or the site owner (or anyone else) is willing to pay the standard 0.5Btc fee for adding the site to the bot

They don't have a public API yet. I think it's on the to-do list.

[seuntjie]

May add one for https://rollin.io/ one day ? It would be really interesting

If they have an API and you or the site owner (or anyone else) is willing to pay the standard 0.5Btc fee for adding the site to the bot

They don't have a public API yet. I think it's on the to-do list.

I'll add the site to my watch list and get into contact with the rollin.io crowd once the api is done then