Hello Guest

Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Programmer Mode / Re: Reset on Bet result received does not match
« Last post by Seuntjie on October 14, 2019, 06:23:45 pm »
No. With the way the bot works, once the bot is stopped, there is no more interaction with the script of any kind. There are other challenges in that as well, as you likely will have to wait several minutes to ensure there are no more pending requests from the site before attempting to start the bot again, otherwise it's just going to happen again.

Resetting your history and just starting again isn't going to solve a problem of getting a bet result out of sync with the bets you place. If you place bet y, then get the result of x, it's going to act on the result of x thinking it's y, and place bet z according to that, and possibly only get the result of y after placing z. If the bot knows about x and that it was placed before y, it knows that something is wrong and it can stop. If you make it forget about x, it's not going to know anything is wrong and either continue placing incorrect bets or stop as soon as it gets ys result after placing x.


Edit: Doormat (core code of V4 of dicebot) has the beginnings of script and setting based error handling implemented, and it's a planned feature for when I get time to work on it again. The idea is that when the bot encounters an error, it is categorized and then sent to your script. Your script can have an errorhandler function which will be called with this error, so you can decide what the bot should do for certain errors (ie you can reset your variables and tell the bot to continue betting if you get a reset seed error but stop if you get a withdraw error, or withdraw and then stop if you get a bet mismatch, etc). If your script does not have the errorhandler function implemented or you are using the advanced mode, it will default to your settings, where you will be able to specify similar but more limited actions for the different kinds of errors.
12
Programmer Mode / Reset on Bet result received does not match
« Last post by BlueSuede on October 14, 2019, 05:23:17 pm »
Seuntjie - I know this error gets brought up quite a bit. But I'm hoping what I'm asking is a little different. I definitely do not want the safety feature removed. I greatly appreciate it. Today it's happened multiple times and Im just assuming it's something on Wolf.bets end. But if I can reset, then cool, if not, then no biggy.
In all of my scripts I create a resetbets() function. The function runs whenever my stoploss is reached or if my target profit has been reached.
The function recalculates my basebet, stoploss, and targetprofit based on my balance.

Is there a way I can run my resetbets() function if Dicebot shows the error "Bet result received does not match last bet place! Stopping for your safety. stopping" ?
I know this is protect us and is a great feature that DiceBot has.

What I'm looking to do is something like the following:

   if (error) then
      if (string.find(error_string, "Bet result received does not match last bet")) then
         resetbets()
      end
   end


This will allow me to start a new series and prevent dicebot from stopping all together. I know this error also happens if dicebot is getting results that are several bets behind, in that case is there a function that will reset the history so I can continue placing bets?
13
Bugs and Suggestions / Re: wolf.bet can login but does not play
« Last post by Seuntjie on October 14, 2019, 04:08:25 pm »
They've made some API changes that is currently breaking the bot. To be clear, the bet is going through. You ARE placing a bet at the site, the bot just can't process the result at the moment. Don't carelessly press the start or bet buttons in dicebot and suddenly expect a result.
14
Bugs and Suggestions / wolf.bet can login but does not play
« Last post by cryptomonkey on October 14, 2019, 05:58:49 am »
http://prntscr.com/piw9p6
what could be the issue here? - it can log into wolfbet , but when start, it would not play!
on screenshot , stop was pressed after start, because nothing was happening!
do you need some kind of log or any clues why does it not start?
15
Bugs and Suggestions / Re: Why do you support lying casinos?
« Last post by Seuntjie on October 10, 2019, 01:36:51 pm »
do you really not understand that people are losing real money?

Oh FUCK? Really? I thought Bitcoin was just magical internet money that people pulled out of their asses. If that's the case, then I'm going to abandon this project and never work on it again. Since nothing is up to your standard, you're more than welcome to take over the project. Here's the source code, feel free to fork it and get it up to scratch, remove all the sites you want: https://github.com/Seuntjie900/DiceBot


All of them transmit false information to the dice bot.I already wrote to you about this, you yourself admitted it?
Now if we're done knee-jerking.

Where? When? What did I say? Can you provide examples? If it was via email, feel free to post them here.

I don't remember ever admitting sites send incorrect info to DiceBot. It's happened a bunch of times that DiceBot incorrectly interprets the data sent by the site, or that DiceBot does not 100% conform to the standards of the site (example bot sends the chance as 98.7654 but the site only uses 2 decimal so it sees the chance as 98.77 or 98.76), as is likely the case with the wolfbet error you posted.
16
Bugs and Suggestions / Why do you support lying casinos?
« Last post by dimon121 on October 10, 2019, 12:13:16 pm »
Why do you support lying casinos? /wolf.bet , Bistler ,Primedice All of them transmit false information to the dice bot.I already wrote to you about this, you yourself admitted it, but do not want to remove them from the bot, why? I lost 1000 dollars because of this, do you really not understand that people are losing real money?
17
Bugs and Suggestions / Re: Wolf Bet Did not give a win
« Last post by dimon121 on October 09, 2019, 06:17:51 pm »
played a chance of 29 and the bot without waiting for a win threw a chance of 20. This should not be
18
Bugs and Suggestions / Wolf Bet Did not give a win
« Last post by dimon121 on October 09, 2019, 06:05:10 pm »
   b431a69f-ce8b-4d41-9104-8104a8acc98a   10/9/2019 7:25 PM   True   29.0322580645161   0.00000078   70.96   -0.0000007811   False   1146717   c310ba33d54b87e6085dcbac939e84ba      7a45dc7c206e4b40fcb1e8d0eb6ba47e113c5fce70e9f702f87fa7c2932959e3       I have been playing this scenario for a long time, and this is the first time   
19
Programmer Mode / Preroll X Times and switch high/low
« Last post by RapidovIG on October 05, 2019, 03:00:20 am »
   .      .     2-3 ,       44 High  44 Low.     ?      ,  .
20
Bugs and Suggestions / Re: wolf.bet login cannot make it
« Last post by Seuntjie on October 02, 2019, 05:12:43 pm »
Are you still having issues logging in?

Can you make a few bets on the site and then try logging in again?

If you're still having issues afterwards, can you send me your username on the site so I can escalate it to their developers with an example?
Pages: 1 [2] 3 4 ... 10