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

[seuntjie]

Seuntjie, why you not commented anything about my Nitrodice cheating proofs?!

Unless you provide PROOF of their cheating, you just sound like a sore loser. You claim to have proof, and I don't want to support a site that's cheating. So if you send me the proof and it's valid, I WILL remove the site from DiceBot. I will remove any site that is proven to cheat.

I haven't had time to go through your thread yet, but from what I can see, their hosted DiceBot thing seems to be cheating and I would not use it. Their bet ids doesn't seem to be in order and I've had other people mention that the betids from their hosted bot doesn't show up on the site when you look for it or the bet id on the site matches to someone else's bet on the site.

Can you view your bet history in their hosted bot?

after first time I get 1k+ loses in 5% chance im not played from "web hosted bot", all other are from your Dicebot windows version, and I dont understand what you mean by name "history", but yes from this hosteddicebot you will get really ridiculus things, without closing eyes, with your Dicebot from personal windows connection you will get little bit less s*it and deviations from normal things

Go to View-> Bet History.

Since you are playing form windows, can you send me the dicebot.db file from an instance of the bot where you found unusual behaviour?

[1713533662]

1713533662

[1713533662]

1713533662

[1713533662]

1713533662

[housework]

Since you are playing form windows, can you send me the dicebot.db file from an instance of the bot where you found unusual behaviour?

ofc I can send, say where to upload or where to send, and what you needed, but I havent big sample, in every few days im making fresh dicebot, but something i had.

but what is that? verified some bets are not "ticked" what does that means?!??
https://imgur.com/ghIUf1Z
and why there are missed nonce numbers to be sequence?!

[housework]

here uploaded db file its ~280mb, but its only 800k hands, its something like last 40hours

https://easyupload.io/2ccf3i

on this period watch last ~50-100k bets there was "that kind of thing" what im talking. (if im remember right)

btw, if you need I can help you track that, I can "hunt" another times it, if there is need in that, and you can't see nothing in this period.

Waiting for your answer, Seuntjie!

Seuntjie, you still dont anwered me, and forget maybe?!

[anunnaki1202]

Is anyway to make the bot faster ?
On old casinos like playtech platforms they allow very fast betting like 3 bets a second on roulette RNG tables.

And here new tech should be more faster than older one i believe    

[joksim299]

Is anyway to make the bot faster ?
On old casinos like playtech platforms they allow very fast betting like 3 bets a second on roulette RNG tables.

And here new tech should be more faster than older one i believe    

Bot is usually faster than on site betting.
It all depends on the site where you play.

[seuntjie]

Is anyway to make the bot faster ?
On old casinos like playtech platforms they allow very fast betting like 3 bets a second on roulette RNG tables.

And here new tech should be more faster than older one i believe    

https://bot.seuntjie.com/faqs.aspx#faq24

[housework]

Seuntjie, you hadn't time to check file?  

btw, again about missing bets, maybe all missed bets in dicebot are connected with not verified bets?!

https://imgur.com/oVmukjP (p.s in screenshot i put black squares to cover desktop image )

in the screen you can see - in reality I was made 62385 bets, but graph shows less (something like ~60300) 5% of bets are missing(red squares), and you can see that missing are losing bets, because in dicebot you can see overall profit is ~23.36..... but in graph is something like ~27.5..... (red lines) it means graph shows more profit, then you have in reality.

It's all about Nitrodice thing.

 

edited:
https://imgur.com/CYFTtUT the larger sample, the more bets are missing. ofc missing losing bets.

[4nn0nn]

Hey Seuntjie,

I am getting so many graphql errors on Primedice, it is not funny anymore. The bot hangs every 30~45 seconds.
My betting speed is actually quite fast. What can I do?

Thanks

[anunnaki1202]

@4nn0nn hello matey ..  how fast you mean 1 bet per second ?

[4nn0nn]

about 3 bets per second lately, I think primedice/stake have updated their servers/cdns or whatever.

@4nn0nn hello matey ..  how fast you mean 1 bet per second ?

[housework]

https://imgur.com/6x4mmXB

20% of bets are missing in Nitrodice.
graph shows ~400k, real bets with that new fresh bot&acc are ~500k
graph shows profit ~ -27, but in reality is ~ -53.

 

btw, I catched another RNG streak, here will be dicebot database file - https://easyupload.io/08qbyx need to watch last 450bets

[anunnaki1202]

@4nn0nn am using primedice as well and fastest goes as 1 per second cannot be my internet because is fiber optic.

And I played with the bot setting on speeds all same it just make it slower than 1 second 

are you betting like 0.1 at a time ?

[4nn0nn]

@4nn0nn am using primedice as well and fastest goes as 1 per second cannot be my internet because is fiber optic.

And I played with the bot setting on speeds all same it just make it slower than 1 second 

are you betting like 0.1 at a time ?

Yes I am not making big bets, I think my bets would be considered low, however whenever I start the bot, the first 300+ bets are extremely fast, like 3-4 per second, after that the graphql errors begin to come up and it slows down tremendously, to like 1 bet per 3 secs

[seuntjie]

Houseworks - sorry, I still haven't had a chance to look into your posts yet, but I did find something that might have been exploited.

1st - I accidentally used the wrong field for the betid, meaning your roll*10000 is yoru betid, not your actual betid. While not
2nd - my roll verifier has a bug in which will result in about 30% of rolls will not verify correctly.
3rd - This is the important one. I didn't do proper research about how .nets Random class works, and I've been using Random directly to generate client seeds. I've since found out that after x numbers, Random can be predicted. This means it's possible that they(and a lot of other sites) could predict the client seed before it was sent to them and could thus choose server seeds that would lose.

My next update will address all 3 of these issues. If suddenly, after the update, people get fewer losing streaks, we can be somewhat certain that they exploited the client seed, although it's not really provable.

I cannot guarantee that this update will make it to their hosted dicebot though, so it's possible that that will never be fixed. If they are actually cheating, that bot will never get this update.

@4nn0nn am using primedice as well and fastest goes as 1 per second cannot be my internet because is fiber optic.

And I played with the bot setting on speeds all same it just make it slower than 1 second 

are you betting like 0.1 at a time ?

Yes I am not making big bets, I think my bets would be considered low, however whenever I start the bot, the first 300+ bets are extremely fast, like 3-4 per second, after that the graphql errors begin to come up and it slows down tremendously, to like 1 bet per 3 secs

Do you have a reset seed setting enabled or use the resetseed function in your script?
If so, try disabling it and see if you still get the errors. PD limits the number of times you can reset seed per hour and going over that limit might cause errors that slows down bets a bit.

[housework]

Houseworks - sorry, I still haven't had a chance to look into your posts yet, but I did find something that might have been exploited.

1st - I accidentally used the wrong field for the betid, meaning your roll*10000 is yoru betid, not your actual betid. While not
2nd - my roll verifier has a bug in which will result in about 30% of rolls will not verify correctly.
3rd - This is the important one. I didn't do proper research about how .nets Random class works, and I've been using Random directly to generate client seeds. I've since found out that after x numbers, Random can be predicted. This means it's possible that they(and a lot of other sites) could predict the client seed before it was sent to them and could thus choose server seeds that would lose.

My next update will address all 3 of these issues. If suddenly, after the update, people get fewer losing streaks, we can be somewhat certain that they exploited the client seed, although it's not really provable.

I cannot guarantee that this update will make it to their hosted dicebot though, so it's possible that that will never be fixed. If they are actually cheating, that bot will never get this update.

thanks for replied, waiting for update, and will test and inform you about this all stuff, if you are interested in that...

but btw, you read topic what I made? you heard that if im will have runned more accounts at same time(with dicebot), in all accounts in exactly same time you will get unreal losing streaks?! (in screenshot you can see i catched it with 5 different accounts in same time more than one time)
so its ridiculus insane! they RNG are not random, but somehow fixed and they are smashing every propability deviaton on certain playing percentage! (but its happens not all the time, but few times in week, i dont get if its random or some kind of criterias like connected time, runned bot time, last nonstop bets made or something, but still far i get that it simple for every user online who was betting in that time for few minutes - will have happens unreal deviations.)

okey with verified bets whatever, but what about missed nonces?!

[anunnaki1202]

Do you have a reset seed setting enabled or use the resetseed function in your script?
If so, try disabling it and see if you still get the errors. PD limits the number of times you can reset seed per hour and going over that limit might cause errors that slows down bets a bit.

Advanced Bet Settings : <--- all the white square boxes are not ticked on that tab

[SM23031997]

Do anyone know how I reset the bet to base bet after a number of bets.

chance  = math.random(10,25)
bethigh = true
basebet = 0.00000001
nextbet = basebet

function dobet()

    chance = math.random(25,35)

if (win) then
   nextbet = basebet
   bethigh = !bethigh
  
else
  
   nextbet = previousbet * 1.25
  
end

end


I want the script to start from the beginning after 50 losses in a row.

[HCP]

I want the script to start from the beginning after 50 losses in a row.

check the streak variable... "currentstreak"... if it's a positive number it is a winning streak, if it is a negative number, it is a losing streak... so something like:

Code:

....
function dobet()
...
  if (win) then
    ..do win stuff..
  else
    -- check if we're on a >= 50 losing streak
    if currentstreak <= -50 then
      -- yes? time to reset to basebet
      nextbet = basebet
    else
      -- no? keep raising!
      nextbet = previousbet * 1.25
    end
  end

end

Basically... "If it's a loss, is it loss #50 (or higher) in a row? If so, reset to basebet, else increase by 1.25 and continue"

NOTE: The bot won't reset the currentstreak variable until you have a win... so, if you continue to lose, the bot won't reset the counter and you'll be constantly betting at basebet. Theoretically you could get an endless streak of losses without it resetting.

If you need it to reset the count at 50, then I'd use my own counter variable and not rely on the internal variable:

Code:

....
losscount = 0
...
function dobet()
...
  if (win) then
    losscount = 0
    ..do win stuff..
  else
    losscount = losscount + 1
    -- check if we're on a >= 50 losing streak
    if losscount >= 50 then
      -- yes? time to reset to basebet
      nextbet = basebet
      losscount = 0
    else
      -- no? keep raising!
      nextbet = previousbet * 1.25
    end
  end

end

[SM23031997]

After the first instance, the script went into making basebet one after another. We need to do something else.

[HCP]

After the first instance, the script went into making basebet one after another. We need to do something else.

2 options...

First option: change it to "if currentstreak == -50 then"

However, if the loss streak continues to 100+, it won't reset again on the next "50", it'll just keep going!


Second option: Use your own counter like I put in the 2nd code snippet. (I edited that in after my initial post, so you might not have seen it)