I'm playing Dice for a couple of days now and I use Seuntjies DiceBot to run it in the background and to try different strategies but I noticed something, after some hundred of bets the bets from 2-3 bets per second to 1 bets per second which means it slows down. Is it natural that when you run it for a couple of hours, it would slow down eventually?
Anyways, made a good progress with the bot, I first tried to hit a high multiplier like the winner from the previous post though I lost some quite amount and decided to change strategy and managed to win back the losses and win some more, it's quite interesting since there's a lot of advance strategy you can use.
yeah it is typical for bots to slow down after hours. You will find almost all casinos throttle small bet sizes or cap bet speeds. other hand local script is used in bot issues like heavy prints, math.random calls or memory leaks put together long runs swap & slow down. you know casino servers employ websocket loadbalancing, rate limits & per user throttles which slow down your ticks over time or force reconnects. for solution you could look over DiceBot logs for throttle & errors, keep an eye on CPU & RAM, eliminate debug prints, sometimes increasing bet sizes solves this prob, add jitter/backoff & reconnect logic, also you could bring your bot up to date.
Regards
Duke