Stake has cloudflare protection across all of their endpoints and you need find a way to bypass it. It used to be as (relatively) simple as getting a valid cf_clearance cookie and passing that along with your request, but they've gotten a lot more snazzy with their requirements. You can take a look at Gambler.Bots usage of the stake api in the bots' source code on github, but it won't mean much unless you can bypass CF. |
|
|
|
Success.Thank you. Now I am just trying to get a script to run. 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.
Take a look at https://github.com/Seuntjie900/Gambler.Bot/blob/master/ProgrammerMode.md. It (poorly, for now) documents the new programmer mode APIs and the legacy compatibility for older LUA scripts. Hi
Is there anyone that can help me with a LUA script. The strategy is to increase on win and increase on loss. The winchance changes for win and loss. When it reaches profit, the script should reset and restart. I have all the conditions in but it stops on the first bet each time I try to run it. Not sure if the gamblerbot can do such a script.
Any advice/help would be appreciated.
Thanks
Can you post your script that you've written so far? |
|
|
|
|
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've released a new version of the beta: https://github.com/Seuntjie900/Gambler.Bot/releases/latestAdded browser login functionality, started implementing Better browser bypass Portable version crashing fix Fixed freebitco.in login Package updates Blocking login without required fields and displays a required error |
|
|
|
I've released a new version of the beta: https://github.com/Seuntjie900/Gambler.Bot/releases/tag/5.0.42Fixed login bug for DuckDice, Stake, PrimeDice and Bitsler Fixed bet verifiers for working sites Fixed reset seed for supported sites Added bet verifiers for different games Added support for different games to simulators Fixed version shown on app Switched portable indicator to use installers added OSX ARM build for Apple silicon devices |
|
|
|
Yep! For FBTC: 2025-04-05 02:32:06.001 -05:00 [ERR] System.Net.CookieException: The 'Domain'=' https://freebitco.in/' part of the cookie is invalid. at System.Net.Cookie.VerifySetDefaults(CookieVariant variant, Uri uri, Boolean isLocalDomain, String localDomain, Boolean setDefault, Boolean shouldThrow) at System.Net.CookieContainer.Add(Cookie cookie) at Gambler.Bot.Core.Sites.Freebitcoin._Login(LoginParamValue[] LoginParams) I've pushed a few updates since and DuckDice should work fine in the latest one, but I'm having trouble with the captchas in freebitcoin and will have to implement a different authentication flow to handle it. I'll post an update when that is available |
|
|
|
Yep! For FBTC: 2025-04-05 02:32:06.001 -05:00 [ERR] System.Net.CookieException: The 'Domain'=' https://freebitco.in/' part of the cookie is invalid. at System.Net.Cookie.VerifySetDefaults(CookieVariant variant, Uri uri, Boolean isLocalDomain, String localDomain, Boolean setDefault, Boolean shouldThrow) at System.Net.CookieContainer.Add(Cookie cookie) at Gambler.Bot.Core.Sites.Freebitcoin._Login(LoginParamValue[] LoginParams) Got it, thank you. Will take a look and push an update asap |
|
|
|
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/releasesNote, 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. Surprised to see you back! So far I'm not having luck getting sites to work, though. Both DD and FBTC are giving errors on login and just refuse to do anything. It's good to see you're still alive though! Could you please send me your log file so I can try to figure out why they're not working? in the folder you installed the bot (c:\users\<yousername>\appdata\local\gambler.bot\current if you used the installer, or the current folder if you used the portable version) look for a gamblerbotlog.log file and send that me? either here or via email please |
|
|
|
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/releasesNote, 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. |
|
|
|
I have a small query if someone can help me.
Actually, I used this bot to bet at stake casino and I was able to bet on a 0.99x multiplier or something like that but the same odds are not possible to bet on directly at stake. I am sorry but I don't know how gambling bots exactly work but one shouldn't be able to bet on negative multipliers basically.
I used those odds that time because I was looking for the cheapest wager possible and that was one easy way of doing it.
Are you confusing multiplier with payout? Multiplier is what the bot multiplies your bet with when you lose/win. Here it should absolutely be possible to have a multiplier below 1 because many people want to reduce their bets gradually instead of resetting. Payout is what the site pays out when you win. DiceBot doesn't do any validation on payout but it uses the same API as the website does. If the website declines a bet with a payout below 1.0102 (typical minimum payout for 1% edge sites) it will decline it if placed through dicebot as well. The confusion between payout and multiplier isn't helped by the fact that some sites have switched to referring to payout as multiplier. |
|
|
|
the support service responded
You need to have made at least one deposit in your account to use the API in your bot.
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. Thanks. I am opening a ticket for our team to check the issue. It can take around 12 to 24 hours. So please be patient. the support service responded You need to have made a deposit with the currency you are trying to use in dicebot into the account you're trying to use. Try placing a bet on the site in that currency and account before switching to DiceBot. |
|
|
|
|
Just FYI, 999dice uses a new server and client seed combination for every (normal) bet, the nonce will always be 0 for 999dice in DiceBot.
Similarly, calling resetseed on 999dice has no effect, since it's reset for every bet anyway. (to the effect that no request is actually sent to the site when you call resetseed)
|
|
|
|
DiceBot version 3.4.15 is available to download from https://bot.seuntjie.com/botpage.aspxChange LogNew Features None Changespdated edge and implemented flexible edge for crypto.games added currencies for wolf Bug FixesBitsler 0 chance and always low, win multiplier |
|
|
|
If you really want to test your strategy you could play at crypto.games and use play money. This gave me an idea of how the bot works, also in programmer mode, without risking my real coins.
I hope it can work for you too.
I mean you could use the built in simulator that uses the sites own RNG with random seeds to do a simulation at 20+x the speed of actually placing bets... |
|
|
|
Can someone actually tell me if the bots actually give the user an edge over other people who do not use this bot? I know strategies like Martingale does not work on most sites offering "Dice" games, but does this bot give you other strategies that gives you the advantage? I downloaded the latest version and I tried it on Stake, but I do not see anything different to my normal wins/losses? (Or do you apply your own strategies for success?) It's not about getting an edge over others, it's about the friends you made alo..... no wait that doesn't make sense. It's about the fun you had while playing around with settings. Bots don't give you an advantage, it just makes a fairly boring game a bit more interesting. |
|
|
|
is there any chance of adding one of the bitsler cashback games, like boom or twist or something? they work a lot like the dice game but give 2x xp and cashback
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) it has ethercrash, which is not a dice game either. the other two i asked about are exactly like dice, just with a different interface. in both you pick your bet of hi or lo and you either hit a number higher than goal or lower and that determines the win I was somehow able to beat the crash game into working in DiceBot. I can't add the other games for Bitsler as is because the architecture of the bot doesn't allow for multiple games per site. While there are viable work arounds, supporting multiple games is something I have planned for and designed v4 to do, so I would rather spend my time working on getting v4 ready than spaghettiing more games into v3. |
|
|
|
DiceBot version 3.4.12 is available to download from https://bot.seuntjie.comChange Log
New FeaturesNone ChangesNone Bug FixesBitsler - wrong currency stats showin Bitvest - stats fix, Bitvest - auto withdraw fixed, but gut says it's a temp fix Fixed chart starting from first bet instead of (0,0) simulation resetseed fix Duckdice fix Stake (and maybe PD) fix - betting call needs to be whitelisted still |
|
|
|
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?
Saw your other post on the other bot thread... 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
You will never have currentstreak < 0 and win == true at the same time... as soon as a win is recorded, if currentstreak was < 0, then currentstreak is set to 1... likewise, currentstreak will never be > 0 and win == false, because as soon as a loss is recorded, if currentstreak was > 0, then currentstreak is set to -1. You will need to create your own "flag" variable... set that to true when currentstreak >= -10... then when you get a "win", check the flag and stop as required. Something like this: ...
badstreak = false
...
function dobet()
...
if win then
if badstreak then
stop()
alarm()
print("stopping after bad streak")
end
badstreak = false
...
end
...
if currentstreak <= -10 then
badstreak = true
end if
end
Another way you can do this (that is a bit simpler imo) is to manually tack your previous streak, for example: ...
previousstreak= 0
...
function dobet()
...
if win then
if previousstreak <= -10 then
stop()
alarm()
print("stopping after bad streak")
end
...
end
...
previousstreak=currentstreak --make sure this is always at the end of dobet
end
|
|
|
|
DiceBot version 3.4.11 is available to download from https://bot.seuntjie.com/botpage.aspxChange LogNew FeaturesNone
ChangesBitsler Currencies Cryptogames currencies 999dice error wording PD Currencies Stake Currencies Windice Currencies
Bug FixesBitvest resetseed Programmer mode withdraw amount fix, Programmer mode doesn't start without nextbet and chance being set duckdice fix Wolfbet decimal rounding
|
|
|
|
|
Show Posts
