Jump to content


  • Content Count

  • Joined

  • Last visited


Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. OP is addressing 2 distinct issues that I an identify. 1. Manipulating their systems to make you lose (speeding up losing streaks, interrupting auto betting during a winning streak etc) and 2. manipulating your psychology to make you lose (popups to break concentration etc) 1. there's a few things to address. Let's start with a simple example. You're the casino and you know that my next roll is going to be 98.76. Am I going to win or lose my bet? At this point you can't answer because you don't know whether I am betting high or low, or what chance I'm betting at. The only way the s
  2. DiceBots bet call has user balance and seed details included in the response. You might be able to use it instead, I'm just not 100% sure how the GraphQL client I'm using formats and attaches the variables to the query. https://github.com/Seuntjie900/DiceBot/blob/master/DiceBot/PD.cs#L272 Edit: Also, you don't necessarily need to request the balance after every bet. You can update your balance internally by just doing balance+=lastBet.profit. Whether the bet was a win or a loss, that'll stay accurate, then just do a balance every 30 seconds for other things that might a
  3. I would argue somewhat here. There is room for deceit on the operator side if you rotate only server seed and not client seed. Changing the client seed without changing the server seed, there is no way for the site to cheat. In addition, I would argue that letting the site know what your client seed is before they select your server seed leaves room for the operator to choose a server seed with certain properties (cannot have 0 in the first 100 rolls for example). Since the server provides proof that the server seed doesn't change (in the form of the hash), the part that the
  4. An even easier thing for the "not the best programmers" to do is to use DiceBot and its programmer mode. It takes care of the API calls for you and simplifies a lot of the finer programming stuff, so you can just concentrate on your strategy instead.
  5. No more need for it, logins are working normally again.
  6. Yes but it's not really Stakes fault this time, more of a problem with how Windows natively handles SSL encryption levels. Here's a workaround to be able to log in until I publish a new version: https://forum.seuntjie.com/index.php?topic=1334.msg2318#msg2318 Logins are working normally again
  7. Seuntjie

    A scam I noticed

    I have 2 Questions for you. 1. If the video was as believable but it said $ (or whatever your local currency is) would you have even considered it? For some reason people stop thinking of cryptocurrency as money and they become gullible. Whenever you see something like, replace any mention of cryptocurrency with your local fiat currency and think about how believable it is again. 2. When you found out the channel/video is a scam, did you report the video/channel? Youtube doesn't just know when things are scams, they rely on people to report videos that are. So when you see
  8. When's the last time you checked? DiceBot has supported Stake since before Stake officially opened.
  9. Can you post a screenshot of your settings and the malfunction?
  10. Let me rephrase my response. I'm not adding new features to version 3 of the bot at the moment. I'm still open to suggestions or requests for version 4 of the bot.
  11. 1. I'm not adding new features to the bot, and typically any GUI update can have an effect on betting speed. 2. Have you tried opening the settings menu? view->settings.
  12. DiceBot 3.4.1 available for download - https://bot.seuntjie.com/botpage.aspx Change Log New Features Stats window is now dockable to home screen Added percentage increase to martingale settings that works with multiplier (changing one updates the other) stop/start buttons for programmer mode saves last used currency syntax highlighted code box auto load tmpcodebackup script on startup (should be last used script for that instance) Changes Ui Changes to advanced mode and programmer mode Added XLM for bitsler Added XRP for PD (and stake) Added tipping to advanced m
  13. While we wait for feedback from the devs, here's a few work-arounds for common issues: When searching for bets using the bet history form, replace the last number with a %. For example, if you're looking for bets with rolls of 12.34, search for 12.3%. This will search for anything that starts with 12.3, so anything between 12.30 and 12.39. It's not ideal, but it should make it a bit easier to identify (If you know which side the precision tilts it to, you can search instead for 12.339% or 12.340%) If you're using the programmer mode to identify rolls as they happen, you
  14. I did a quick test from DiceBot and then directly from Stakes API page to make sure: The problem is on stakes side, below is a screenshot of roll as it is returned from the API. While I can round the results to 2 decimals, it would be better and more correct for it to be done on the server. I have escalated the issue to the devs and am awaiting feedback
  15. I still need to test and verify this, but I suspect that the problem is on Stakes side, not the bot. DiceBot only shows the number it gets from the site, if it's showing something with too many decimals, the site is sending a number with too many decimals. Once I've had a chance to test it, I will report back. If it's a problem on the bots' side, I will fix it, but if it's a precision problem on stakes/pds side, I will report the problem to them.
  • Create New...