Topic: Seuntjies DiceBot -Multi-Site, multi-strategy betting bot for dice. With Charts! - page 138. (Read 274841 times)

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.



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.

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.

   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. 

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.

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...     

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




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

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

it works, this is getting more exciting thanks a lot

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

so far seuntjie bot is very helpful to me,
  indeed it is the martingale system is flawed but that depends on how you setting the bot

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

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
in the dobet function.

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


That is very odd. I'll have it fixed in the next build.

Hi thanks for the fast answer, the error indeed started to occure when my balance was a little higher, now my balance and investments are at zero and i still have this problem. i deleted all files and downloaded it again but the problem is still there. Hope you can fix it soon

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


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

thanks

Thanks for pointing that out, I'll get it fixed ASAP. The problem is that your balance is too large (A problem I wish I had). A temporary fix will be to withdraw some funds or move some into a different account. Make sure your balance+invested amount (they're summed in the api iirc) is smaller than 21.47483647 on the account you're logging in to. Any time you balance exceeds this amount, the bot might crash.

I can´t login to SafeDice.com

I get this error:


On continue the program does nothing, on quit it closes. I can login to all the other dice sites.

    Yes, it's working now.  under view->setting  try to get server seed, was checked.  I unchecked that box and manually placed a bet (with the bot) and my programmer mode program took off. 

    Now that I just looked again, that is still checked (get server seed)  but everything is still working ok, so I'm not really 100% sure what the problem was. 

so does it work now or not?

looks like there is a bug in the zig zag option in that version. sorry about that.

sir im using version 2.5.5
everytime i use zigzag option it crash
why is that ?

Nevermind,  Somehow I had the get server seed box checked.  Unchecked that and everything took off.

    Just tried running the bot on PRC.  Doesn't seem to be working.  I can see the bet being made on the website, but the result is not being returned to the bot.  

  Any ideas on this one.  Tried V3 B10 and my copy of B11.  

NEW....

Downloaded the zipped B11 bot.  Still failing but now three is a message at the bottom that it "Failed to place bets after 3 retries, stopping.  Please check network and bot settings"

    I can see that it really did place 2 bets according to the website.