Jump to content

Seuntjie

Member
  • Content Count

    50
  • Joined

  • Last visited

5 Followers

About Seuntjie

  • Rank
    Enthusiast

Player Details

  • Username
    Seuntjie
  • Wagered (BTC)
    1.97155734
  • Wagered (ETH)
    0.03114882
  • Wagered (LTC)
    0.00013007
  • Wagered (DOGE)
    120,749.81562

Recent Profile Visitors

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

  1. Rollhunt should be working normally now. I'll make XRP available for rollhunt as well soon.
  2. Rollhunt is working as far as I know. The last time I tested it (after the big update) it was working normally. If there aren't any hunts, it's because the mods aren't starting them. It's because the command is enabled. I've restarted it and it should be working normally again now
  3. dicebot is open source, but unfortunately most "custom" versions that people distribute are malware and tend to try to steal your balance or login credentials
  4. 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 tip to advanced mode Bug Fixes Stake and PD not working correctly
  5. Alternatively, just update the bot to the newest version/get the latest code from github
  6. This topic isn't about DiceBot, it's about ChatBot.
  7. There is a blacklisting feature that mods can use (!blacklist <username> <time in hours> <reason for blacklist>). A blacklisted user is unable to use bot commands. The bot has some anti spam features and protection, but it doesn't protect against people attempting to abuse it for rain. This is up to the mods. If you spot someone just using the bot for that purposes, notify a mod or support person and have them blacklist the people. My argument for keeping chatbot response public has always been a kind of anti spam but also just ease of use. If you see someone using, for example, the price command in public, but not getting a response (because he got a response in PM) and you also want to know the price, you're also going to use the command - and the 10 other people in chat that wants to know the price. Now you have 10 people just sending !price in chat directly after each other. You'll also likely just get someone that does the command and posts the response in the chat afterwards. Also, if you and someone else is talking about a coin/trade w/e and the price of a coin comes up (or any of the commands chatbot has available), using it in a way both/all can easily see the response is easier than each one having to do the command or one having to trust another one about the response.
  8. Did you remove the value property from your request like I suggested?
  9. don't request the value property and make sure your x-access-token header is set to your access token or api key.
  10. If you're talking about pre-rolling, there's a combination of settings to enable that. Set your multiplier to 1 (so that your bet doesn't change), set your multiplier mode to change once. Then for the setting "after x bets, time multiplier by y", set x to number of prerolls you want to do, and y to what you want your multiplier to be after pre-rolling. Then you can set it to multiply after every z losses in a row, in stead of every loss (bottomish of the multiply on loss box). You just need to ensure that your settings match. For example if you change your multiplier to 2 after 99 bets, but multiply after every 49 bets, your bet is only going to be multiplied after a total of (49*3) bets. (after at 49 bets, multiply by 1, after 98 total bets, multiply by 1, after 99 total bets, multiplier is changed to 2, after 137 total bets, multiply by 2). You can also look at the setting "after a losses, change bet to b"
  11. Any plans to release the source for this project? People always trust open source more than pre-compiled executables.
  12. DiceBot 3.3.7 is now available to download from https://bot.seuntjie.com/botpage.aspx Change Log New Features Added Stake added freebitcoin added sitedetails object to the programmer mode. Changes changed the login failed message. pd speed increase Added XMR to 999dice. Bug Fixes Betterbets and ETC bets error display issues fixed. bitsler slow bets hopefully fixed Simulation form no longer requires simulation/start to be run from programmer mode before sim. safedice login issues (hopefully) bet history display issues.
  13. @AltonNy No, gambling in general is only profitable for the house (Except for player vs player games, like poker). This is due to the casino having a mathematical advantage over the player. I wrote a crappy little piece about this on steemit if you're interested in reading it: https://steemit.com/gambling/@seuntjie/why-botting-doesn-t-work-at-casinos Never gamble for profit, gamble for fun. Never gamble more than you can afford to lose.
  14. The bets are stored in a sqlite database called dicebot.db which is found in the same folder as the executable (the file you click on to run the bot). You can use any program with a sqlite driver to access the data, sqlitebrowser (http://sqlitebrowser.org/) or excel is you install the odbc sqlite driver (http://smallbusiness.chron.com/connecting-excel-sqlite-42473.html)
×