Pages:
Author

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

HCP
legendary
Activity: 2086
Merit: 4314
I found this script on dicebot site, and I was wondering if there is any way to implement code that would set maximum chance to 98%. Problem is that after long streaks of red, script tries to increase chance above 98% and then ofc it stops betting.
Yes, of course. A simple check when the chance is being calculated will stop that... the question is, what do you want to happen when it gets to 98%? Just continually bet 98% or should it "reset"? Huh


This code will simply set the chance to 98 if it tries to increase it over 98%... so once it hits 98, it will stay at 98 until a win causes it to drop (assuming winpercent is always going to be < 1):

NOTE: I HAVE NOT TESTED THIS CODE! I make no guarantees it will work, use at your own risk Tongue
Code:
basebet     = 0.00000001
chance      = 80
maxchance = 98
losepercent = 1.03
winpercent  = 0.99
lossbet      = 2
winbet      = 1.12
bethigh     = false
nextbet     = basebet

function dobet()

    if profit > 0.0000000000001 then
    print(profit)
       resetstats()
        nextbet = basebet
        chance  = 80
        end
      
      if win and profit < 0.000000000001 then
   print("We Won")
 print(profit)
 chance = lastBet.chance * winpercent
 if chance > maxchance then
   chance = maxchance
 end
 nextbet  = lastBet.amount * winbet
bethigh  = false
end

if win == false and profit < 0.0000000001 then
print("We Lose")
 print(profit)
chance = lastBet.chance * losepercent
if chance > maxchance then
  chance = maxchance
end
nextbet = lastBet.amount * lossbet
   bethigh  = false
end
        
end



Quote
Thank you in advance.
You're welcome Wink

newbie
Activity: 48
Merit: 0
Seuntjie, what new about Nitrodice? you checked my database file what Im given to you?!  Huh
newbie
Activity: 7
Merit: 0
Hi, first I'd just like to thank Seuntjie for providing this awesome bot as well thank other contributors to this topic.

I found this script on dicebot site, and I was wondering if there is any way to implement code that would set maximum chance to 98%. Problem is that after long streaks of red, script tries to increase chance above 98% and then ofc it stops betting.

Thank you in advance.

basebet     = 0.00000001
chance      = 80
losepercent = 1.03
winpercent  = 0.99
lossbet      = 2
winbet      = 1.12
bethigh     = false
nextbet     = basebet

function dobet()

    if profit > 0.0000000000001 then
    print(profit)
       resetstats()
        nextbet = basebet
        chance  = 80
        end
     
      if win and profit < 0.000000000001 then
   print("We Won")
 print(profit)
 chance = lastBet.chance * winpercent
 nextbet  = lastBet.amount * winbet
bethigh  = false
end

if win == false and profit < 0.0000000001 then
print("We Lose")
 print(profit)
chance = lastBet.chance * losepercent
nextbet = lastBet.amount * lossbet
   bethigh  = false
end
       
end
legendary
Activity: 1717
Merit: 1125

I don't want the bot to stop there at least it should start betting from the base bet in that case.
Can I configure it that way?

No.
hero member
Activity: 1092
Merit: 582
Will it speed up the betting process of the bot?
For the bot sometimes it runs faster and another sec it stopped betting for a while. Doesn't look like the logging issue with the dicebot.db file.


I have faced one more issue with the bot. I can't leave the bot unseen because after a while it makes a bet twice and then stops betting. I was planning to run the bot on VPS but because of the issue, I can't.
Do we have anything to stop that behaviour or start everything from the beginning without manual intervention?

Only if your script is querying the database.

Usually if it stops for a few seconds at a time, it's a site issue. Lots of sites seem to have issues where either one of your own or everyones bets get delayed by a few seconds. Could be a site update, network issue at the site etc.

If it stops for 30 seconds, the bet likely failed for some reason and the bot is retrying the bet (network issue, invalid bet, site error etc).

Regarding the placing the bet twice and then stopping, FAQ again: https://bot.seuntjie.com/faqs.aspx#faq28
Usually network error, ie the site is taking more than 30 seconds to respond to a bet, when it retries, the site finishes the previous bet and the first bet at the same time and returns both results. The Bot HAS to stop in this case, otherwise it's running 2 loops concurrently and that creates extremely weird betting patterns. There's no way to restart the bot from this without manual intervention because it's such a dangerous and unpredictable situation.

I don't want the bot to stop there at least it should start betting from the base bet in that case.
Can I configure it that way?
legendary
Activity: 1717
Merit: 1125
Will it speed up the betting process of the bot?
For the bot sometimes it runs faster and another sec it stopped betting for a while. Doesn't look like the logging issue with the dicebot.db file.


I have faced one more issue with the bot. I can't leave the bot unseen because after a while it makes a bet twice and then stops betting. I was planning to run the bot on VPS but because of the issue, I can't.
Do we have anything to stop that behaviour or start everything from the beginning without manual intervention?

Only if your script is querying the database.

Usually if it stops for a few seconds at a time, it's a site issue. Lots of sites seem to have issues where either one of your own or everyones bets get delayed by a few seconds. Could be a site update, network issue at the site etc.

If it stops for 30 seconds, the bet likely failed for some reason and the bot is retrying the bet (network issue, invalid bet, site error etc).

Regarding the placing the bet twice and then stopping, FAQ again: https://bot.seuntjie.com/faqs.aspx#faq28
Usually network error, ie the site is taking more than 30 seconds to respond to a bet, when it retries, the site finishes the previous bet and the first bet at the same time and returns both results. The Bot HAS to stop in this case, otherwise it's running 2 loops concurrently and that creates extremely weird betting patterns. There's no way to restart the bot from this without manual intervention because it's such a dangerous and unpredictable situation.
hero member
Activity: 1092
Merit: 582
Is any way to delete all my betting history because it seems slows the bot down after a while  Huh

As always, the FAQ is a good starting point: https://bot.seuntjie.com/faqs.aspx#faq17
Will it speed up the betting process of the bot?
For the bot sometimes it runs faster and another sec it stopped betting for a while. Doesn't look like the logging issue with the dicebot.db file.


I have faced one more issue with the bot. I can't leave the bot unseen because after a while it makes a bet twice and then stops betting. I was planning to run the bot on VPS but because of the issue, I can't.
Do we have anything to stop that behaviour or start everything from the beginning without manual intervention?
newbie
Activity: 48
Merit: 0
need to refresh topic!

Im made little bit alarm with my posts, and now people know about it, and im not only one who was not satisfied with this site.

you can join they telegram channel and read, they are not paying withdraws within days, they are locking accounts etc. https://t.me/nitrodiceofficial

https://imgur.com/pZj9JoA

if you start talk something about rigged and cheating, verified bets etc, he are saying that all was Seuntjie and hes bot fault, that site is fair bla bla bla.



Seuntjie, why you dont involve in conversation with me? https://bitcointalksearch.org/topic/m.53648168

legendary
Activity: 1717
Merit: 1125
Is any way to delete all my betting history because it seems slows the bot down after a while  Huh

As always, the FAQ is a good starting point: https://bot.seuntjie.com/faqs.aspx#faq17
jr. member
Activity: 78
Merit: 1
@HCP Thanks i'll look into that
HCP
legendary
Activity: 2086
Merit: 4314
You can simply shutdown dicebot and then delete the dicebot database file named "DiceBot.db"... or simply rename that file it if you think you want/need to access that history again at some point... The file will be in the directory you run the dicebot.



NOTE: If your Windows is setup to hide file extensions, it might just show up as "DiceBot"... but the file type will be listed as "Data Base File" like in the screenshot above. You can read how to show file extensions for Windows 10 here: https://www.tenforums.com/tutorials/62842-hide-show-file-name-extensions-windows-10-a.html
jr. member
Activity: 78
Merit: 1
Is any way to delete all my betting history because it seems slows the bot down after a while  Huh
newbie
Activity: 48
Merit: 0
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! Smiley

Seuntjie, you still dont anwered me, and forget maybe?! Huh
Seuntjie, you still forget to answer and check something?!

I haven't forgotten, I've just been busy.

I did do some tests on the site though. I left 2 accounts betting at the site, one using a fixed RNG for seed and one not for 24 hours. One account did around 900k bets and the other around 700k. During that time I got a max losing streak of 19 losses at 49.5% and a max winning streak of 20 at 49.5% one the 900k account and max losing streak of 19 (twice) and a max winning streak of 17 or the 700k account. I had no skipped or repeated nonces on either account. I used a fixed verifier for the site to check thousands of bets, especially the bets where I had a losing streak and all of the bets verified correctly.

If there are skipped nonces in the bet history database for DiceBot, it's probably because the SQLite interface can't keep up with the speed of the bets when you're close to their server. Since the all time graphs draw from the database, that explains why the graph might not show the same number of bets as your nonce. I haven't had time to verify this using either your or one of my own DBs. It's also very possible that with the time it takes to draw charts with hundreds of thousands points and because it's multi threaded, the bot is suppressing errors that arises when trying to add points to the charts.
i have runned last 10days without rng streak, so ofc you has not get it in last time(because how much i understand of my test this streaks need to be in same time for all users), and idk about other pecentage, if you want really test it run on 5%(im talking only about 5% chance play, idk if streaks was on others percentages) chance and left it next week/twos, how much i remember before christmas was two weeks without streaks it was record long period without.
and yes, in my last uploaded database last 450bets was losing on 5% i simple pressed stop, that was enough ridiculus
but maybe simple they technical team turned it off for some time until this all stuff quites down, because its strange long period without rng streaks
btw, even owner contacted me about thats stuff he dont like this kind of posts in internet, so maybe while i pushing up this talks streaks will not gonna occurs 😁
legendary
Activity: 1717
Merit: 1125
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! Smiley

Seuntjie, you still dont anwered me, and forget maybe?! Huh
Seuntjie, you still forget to answer and check something?!

I haven't forgotten, I've just been busy.

I did do some tests on the site though. I left 2 accounts betting at the site, one using a fixed RNG for seed and one not for 24 hours. One account did around 900k bets and the other around 700k. During that time I got a max losing streak of 19 losses at 49.5% and a max winning streak of 20 at 49.5% one the 900k account and max losing streak of 19 (twice) and a max winning streak of 17 or the 700k account. I had no skipped or repeated nonces on either account. I used a fixed verifier for the site to check thousands of bets, especially the bets where I had a losing streak and all of the bets verified correctly.

If there are skipped nonces in the bet history database for DiceBot, it's probably because the SQLite interface can't keep up with the speed of the bets when you're close to their server. Since the all time graphs draw from the database, that explains why the graph might not show the same number of bets as your nonce. I haven't had time to verify this using either your or one of my own DBs. It's also very possible that with the time it takes to draw charts with hundreds of thousands points and because it's multi threaded, the bot is suppressing errors that arises when trying to add points to the charts.
newbie
Activity: 48
Merit: 0
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! Smiley

Seuntjie, you still dont anwered me, and forget maybe?! Huh
Seuntjie, you still forget to answer and check something?!
jr. member
Activity: 78
Merit: 1
Thanks for the update seuntjie  Cool and is a little bit faster on the bets like 25% faster than previous version of the bot
legendary
Activity: 1717
Merit: 1125
hi seuntjie, i saw the latest version of the bot and it showed a fix for wolf.bet but login still seems to not be working and it wasn't noted on the changelist so i was wondering if that should be fixed already or if it is still pending

The login issue is due to them having cloudflare on high at the moment. Nothing I can do to fix that. Once whomever is trying to attack them lets off a bit and they can lower the protection, DiceBot will work again.
member
Activity: 309
Merit: 12
hi seuntjie, i saw the latest version of the bot and it showed a fix for wolf.bet but login still seems to not be working and it wasn't noted on the changelist so i was wondering if that should be fixed already or if it is still pending
jr. member
Activity: 78
Merit: 1
Alright i upload it into your site seuntjie if anyone wants a win/win system can get it from there.

Or get it from here http://www.mediafire.com/file/789x4f89itg53nd/Fibonacci_%2526_Anunnaki/file
legendary
Activity: 1717
Merit: 1125
Is just Advanced mode i saved as a file i look inside and no logins details in it.  Grin

But is more easy with 2 screenshots than the file itself

Also, you can share settings files at https://bot.seuntjie.com/settings.aspx once you've created an account
Pages:
Jump to: