Hi Seuntjie,
Thank you for the bot. I've been using it for a couple of months and it's been working great until recently,
I've been experiencing some problems where sometimes the bets stop being reflected to the balance or is not reflected correctly. (e.g. the balance doesn't bounce back after winning after a losing streak, or deducts more from the balance than the loss amount)
It took away most of my balance once, and now I'm a little scared to use it.
Could you please advise on how I can prevent this from happening?
Thanks,
I have not experienced anything like this since v 3.1.0 ish (if you're still using an older version, it's your own fault. There're updates for a reason). Obviously, if this is actually the bots' fault, this is a very serious issue and I'd like to fix it asap. so:
On which site are you betting?
Have you compared your balance on the site vs in the bot?
Are you betting at the correct chance you think you're betting at?
What sometimes happen, especially if you have a stop condition set it the bot places the bet but the stats aren't updated. So it just doesn't show the new balance.
Can you describe your settings? or even better, send me and exported settings file? If you don't want to share it publicly, you can email me on
[email protected]I need as much details as you can to accurately diagnose/reproduce the bug.
Hi Seuntjie
Sorry for the late reply.
I was planning to check and see if the same phenomenon occurs again, before sending you the setttings but was unable to since the primedice update, thus late reply.
I was using the latest version of the bot and I also checked that the balances displayed in the bot and the site match. (the balance had not recovered on win after consecutive losses)
I've sent you the screenshot of the bot when this occured, to the e-mail address displayed on your top page about 2 weeks ago from e-mail yu******515@gmail
Please let me try if the same occurs again, after I'm able to login to primedice through the bot, and if so,
allow me to send you the settings for further investigation.
Thanks for your efforts!
I don't have access to that email at this moment (i'm on my lappy, the account is on my home PC), so I'll take a look at it as soon as I get home. If you are able to reproduce the problem, please let me know and send me as many details as you can.
I can't say deleting dicebot.db while the bot is open is a good idea. I'm surprised this doesn't cause more issues.
To prevent the crash, open the settings window (view->settings) and disable the setting to automatically look for missing seeds. If that doesn't work, please let me know.
I did as you said, but also when disabling to look for the seeds I still get the .NET Framework error.
I also noted an easier way on 'bypassing' the bot to write to the Dicebot.db file:
- Start the bot.
- Upon loading, assuming no Dicebot.db file is yet present/deleted after former session/first start, the bot creates the Dicebot.db file of 5kb size.
- When bot is loaded, and not yet actively running, delete the Dicebot.db file.
- Activate the bot, and then it creates a 0kb size Dicebot.db file which it doesn't write to (no HDD activity), yet places the bets very fast.
Personally, I like it when the bot does not utilize the Dicebot.db file and/or doesn't write to it. Because this way, I noted it is possible to bet smaller bets at the same high speed as with larger bets (which normally is not), without any issues (at least, not on 999dice).
Did you click save settings after disabling the feature? It might also require a bot restart to work? Sorry if this questions seems offensive, people forget/miss things sometimes.
I'll take a look at fixing the crash and speeding up the DB writes. I will not be providing the option to disable the bet logging though. You completely lose your ability to verify your bets and make yourself vulnerable to the site cheating you if you remove the logs, but I do understand your want for faster bets. I never noticed the DB causes such a bottleneck, since i have been able to bet at much faster speeds (10-15 bets/s) with the db enabled, also on a normal hdd.