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

I'm able to log in without a problem. It seems like they have removed most of the ethereum based tokens and now only support btc, ltc, eth and bkb. Make sure when you log in that you have one of these selected.

betking must have changed something. i can't login through dicebot

Primedice and stake both throttle bets, set the "bot speed" setting in the advanced mode to something that works for you. 1 bet per second should do the trick to remove "Please wait a few seconds and try again" message that is received from primedice and stake. Also, don't chat or bet on the site while the bot is running.

I cannot hardcode a throttle because the throttles change regularly.

Unfortunately my internet is not fast enough to be able to do 5 bets a second, so I did the next best thing. I ran a simulation of 60 000 bets using the exact script you gave me. The simulation uses the same code and executes the same functions as normal betting does significantly more bets/s than 5. I exported the bets from the simulation and processed them and what you explained did not occur once.

Thinking about how the bot assigns values to those variables, if the currentstreak variable is not updated, the previousbet variable cannot be updated either, meaning if what you think is wrong is actually wrong, you would duplicate a bet, not place a bigger one.

The only thing I can think of that can cause this is if the bot tries to place a specific bet twice or it received a result unexpectedly because 1) you placed a bet on the site while the bot was running, 2) you placed a manual bet from the bot while it was running, 3) you started the bot again while it was running, 4) You're playing on the same account with more than one bot, 5) There was a network/server error which caused the result of a bet to be delayed by more than 30 seconds and the bot retried the bet.

The bot has checks in place to identify these situations but it's possible that it doesn't work as well as it should with sites that use sockets like yolodice does. I will see if I can find another way to try to reproduce the problem, or to improve the quality of these checks. In the meantime, I suggest you look through your script for anything that might cause it, if the script that you posted is not your full script. Run a simulation, export the files and try to find an occurrence of the bug in your exported file. If it's in there, it's a problem with your script. If it's not, it's a problem with the interface between the site and the bot that I will need to look in to

yes this script make that what im talking about.
yes I need to learn more things

I will be difficult to play and try to catch another one time... but what I can say, really nothing you will see, simple in graph will be tryed to catch 6 winning streak, when my script was made for catching only 5 winnings in row, and then decrease betsize to basebet(or basebet*2) and in console you simple will be 5 winnings in row, and bet 6th with increase while bot/script need to decrease it to basebet.

its simple some kind of functionally error because of abnormal veryfast bets without speed limit.

Are there any API differences between using these currencies and those provided by moneypot?

Is that your whole script? Can you include a screenshot of it happening please? You should learn how to use the modulus (%), larger than (>) and less than (<) operators, it will make your scripts much shorter, easier to understand and more efficient.

Re the minimizing bug: https://bot.seuntjie.com/bugreport.aspx?id=4169

Dicebot users on our site are reporting the balance doesn't show with Doge, Bxo and Clam bets in dicebot.

basebet = 0.15000010
nextbet = basebet
chance = 33

function dobet()

   if (win) then
      if currentstreak == +1 then
         nextbet = previousbet*1.9
      elseif currentstreak == +2 then
         nextbet = previousbet*1.9
      elseif currentstreak == +3 then
         nextbet = previousbet*1.9
      elseif currentstreak == +4 then
         nextbet = previousbet*1.9

      elseif currentstreak == +5 then
         nextbet = basebet*2
      elseif currentstreak == +6 then
         nextbet = previousbet*1.9
      elseif currentstreak == +7 then
         nextbet = previousbet*1.9
      elseif currentstreak == +8 then
         nextbet = previousbet*1.9
      elseif currentstreak == +9 then
         nextbet = previousbet*1.9

      elseif currentstreak == +10 then
         nextbet = basebet*3
      elseif currentstreak == +11 then
         nextbet = previousbet*1.9
      elseif currentstreak == +12 then
         nextbet = previousbet*1.9
      elseif currentstreak == +13 then
         nextbet = previousbet*1.9
      elseif currentstreak == +14 then
         nextbet = previousbet*1.9
      else
         nextbet = basebet
   end
end

     if (!win) then
        nextbet = basebet
        end
     end

end
end


thins kind of stuff, its not frequent bug, it's rare, but time after time, maybe 2-3 times in day(24hours/400 000 bets) bot are makind "missbets" when they need to stop increasing, and bet "basebet" they keep betting one more bet...

maybe its web site bug(YOLOdice) because time ago iv found that they have problems with fast updating balance, and then many of bugbets occurs with very fast betting, if balance are not updeiting right in milliseconds, and basebets are calcualted from currrent balance at the moment

but this one seems like bot bug, because of very fast bets.






and yes another thing, new update had bugs when minimizing bot, and do some things.

https://imgur.com/a/gjA9vMs

Can you post a screenshot of it happening, including your script?

It is more likely that it is something in your script causing this, and if you (like always) refuse to post your script (even in pm) so I can look into the issue, I'm not going to look into it until I get another, independent report of it happening. From the way the programmer mode works and when and where the bot assigns variables to and reads variables from the programmer mode, it is highly unlikely that it's a timing issue or has anything to do with the betting speed.

If you do post your script (or PM/email it to me), I will look through the script to see if I can find anything and let you know what's wrong with it. If I don't find anything, I will take steps to try to reproduce the problem and if I can find the problem, I will fix it.

I wonder if the "currentstreak" value is not working as intended due to some internal timing problem? I can't test it right now... And I don't have the code handy, as I'm travelling at the moment.

Are you able to create your own variable for tracking wins and losses?

Something like this:

You can then use 'theStreak' instead of 'currentstreak'. See if that works... If that still has the same timing problem, then it's probably a timing issue with the websites API

      if currentstreak == X then
         nextbet = X
      elseif currentstreak == X then
         nextbet = X
      else
         nextbet = basebet

using this kind of thing.

The obvious solution is to bet slower...

How is the script detecting the wins/losses? Are you using inbuilt streak values or using "custom" variables?

Hey, last update had bug, time after time, when bets are fast 5+per/sec then he will missread script and do not what he need to do



like sample:

after X loses or wins in row, he need to place basebet, but he are not doing it in 5th bet, but only in 6th bet, because of fast bets.

with small basebet and slow bets, this is not occurs.





what is/can be sollution?!

What happens if you click continue? Does the app open at all?

If it doesn't, click the "details" button and then copy/paste the info it shows here.

i got this error message when i start dicebot
current dicebot version 3.3.22
https://ibb.co/n8SNpf

I'm sure that Seuntjie probably already told you, but that sort of thing would be dependent on the betting site offering that functionality via it's betting API.

So, have a word to whatever site(s) you're wanting to bet on... and ask them to provide this functionality first (via their API). Only then can it possibly be added to the dicebot.

i got your pm .. kindly add this option in future

actually i change my server seed every few bets in dicebot settings ,, but i don't like to change my client seed..
i couldn't find any answer while searching google. so i need your help ,, how to set up CLIENT SEED in Dicebot ?

DiceBot 3.3.22



Change Log

New Features
Added Ethercrash.io


Changes
Added currencies for:
Bitsler: btg,lsk,dgb,qtum,waves
Duckdice: xrp,etc,btg
Stake: bch, doge
Primedice: bch, doge
yolodice: Doge activates 29 oct 2018
Added Ethercrash


Bug Fixes
Login issues for just-dice
Stats not updating for stake