If you're logging in with your API key you do not need to log in when the site loads in the browser, that is only to get the relevant headers from the site so the bot can connect. If you're using the browser log-in, just try to log in again, the page should stay visible a little longer the second time.

I'm very happy to announce, firstly that I am not dead as has been rumored. But more importantly the release of version 5 of Seuntjies DiceBot - which has been rebranded as Gambler.Bot, because it's not just dice anymore!

Download here: https://github.com/Seuntjie900/Gambler.Bot/releases

Note, this is a beta release. While I've manually tested most of the application, there have been drastic changes and some features might not work correctly and I do not yet have proper tests written for everything.

Why the re-write? v3 was written in a very old version of .net, supported only windows with a fairly basic and ugly UI and was frankly very slow and rigid. V5 has been re-written in .net 8 and will be maintained on the latest long term release at least, the UI was built with Avalonia and is cross platform capable. The beta release, while it has a linux version, is untested on anything but windows. It will be one of my highest priorities to get the bot working on Linux and Mac, with the aim to eventually get it running on IOS and Android in the long term. Additionally, there have been tremendous performance improvements made to the bot, and architectural changes allow the bot to run more than just Dice!

So whats the important new bits:

• Cross platform
• Brand new UI with light and dark mode and different color accents
• Performance increase - Betting speed and especially simulation speed (1 000 000 bets simulated in under 20 seconds)
• More dynamic betting strategies
• More languages for the programmer mode: CSharp, JavaScript and Python now supported as well
• New programmer mode interface to support more complex functions like error handling (legacy scripts still supported by LUA, but only for Dice)
• Dynamic triggers
• Multiple database providers to store your bets in - defaults to sqlite
• Browser bypass for sites with DDOS protection

What's the plan going forward?

I plan on continuing to work on the bot for the foreseeable future. The basic roadmap for the bot:
Get everything tested and release a stable version. Any feedback on issues would be greatly appreciated, either here or on https://github.com/Seuntjie900/Gambler.Bot/. A to-do for the stable release is also available on github.
I am planning on releasing the Gambler.Bot.Core as a nuget package to provide a standardized way to interact with a variety of casinos for anyone that is interested in writing their own bots.
Gambler.Bot.Strategies will likely also be published as a nuget package for people to use.
Get the bot working on Linux and Mac
Expand the list of supported games - including (hopefully) Plinko, HiLo and Roulette
Expand the list of supported sites
Expand auto-bet functionality
Expand reporting functionality - extra charts, bet history features etc. Need input from users about what they want to see here.


Whats going to happen to DiceBot v3? WinMachine has been somewhat maintaining it and releasing it as version 4. I cannot condone or recommend his releases as he has stopped publishing his code. The public repository of DiceBot will remain available but I will no longer publish updates to it.

interesting... I was wondering why you mentioned earlier you had made a deposit

So, has the deposit transaction that you sent actually confirmed or is the transaction still unconfirmed? The network is insanely busy at the moment with high fees etc... so make sure the transaction has at least the minimum number of confirmations as required by wolf.bet.

AFAIK, seunjti dice bot only "works" for dice game. Never heard he will add other games on seunjti dicebot since it's a "dicebot"

Seunjti dice bot version 3.4.13 is available anyway, just download from this link https://bot.seuntjie.com
(Don't trust other source for download bot since it could scam you)

but how can i make bot stop after it had currentstreak = -10
or 10 losses and it has to win back to original balance then stop?

how do we stop bot if it struck a losing streak of 10, ie, currentstreak = -10 and we need to stop it only when it wins [more losing steps may follow after hitting -10] above the original balance when it was positive?

my sample didn't work:
if currentstreak <= -10 and win then
stop()
alarm()
print("stopping after bad streak")
end