Run Martingale, Paroli, D'Alembert or Pluscoup from 1 script. I had this kicking around in my emails from ages ago, hope everyone has fun! ------------------------------------------------------------------------------------------------------ //[WARNING] Use this script at your own risk, nobody is responsible if you lose money on bustabit when you use this bot. //Settings var GameMode = 3; //Default: 1 1 = Martingale, 2 = Paroli, 3 = D’Alembert, 4 = Pluscoup var MaxProfitMode = false; //Default: true If this setting is true, you will always bet ("PercentOfTotal" / 100 * your balance), if this setting is false you will just bet your BaseBet. var PercentOfTotal = 0.1; //Default: 1 If MaxProfitMode is true, your BaseBet will a...
UPDATE: Check the picture below for tips to avoid the glitch. I know its vague and includes of reasons why this could happen but until a solution is found everything that is highlighted, watch out for while running DB.
https://s7.postimg.org/wardpzq2z/quotefromtheman.png
YOU CAN USE DICEBOT
But it will run into an issue after a random amount of time, picking up whats causing the glitch and stopping it is harder then it seems. I do not reccomend using DB right now but if you do, please always watch it every bet and if you see your profit dip below -0.01 type stop() in the console and hit enter. (I suggest having it pre-written and just hit enter when it gets to the profit loss.)
After that sign out, close the program, reopen, sign in and continue gambling.(That is the only known current fix, double check in task manager it is not running in background before resuming gambling.)
Update2017-11-21: This is an untested edit to try and resist the glitch.
http://textuploader.com/dqr4c <--- Reduced Basebet with new reset Untested.
http://textuploader.com/dqr4x <---- No reduced basebet, just new rest. Both still untested!
This is interesting. I i understand correctly the issue is that system does not stop when the loos is biger than a 100K. I experienced it the hard way 3 times and it cost me 0.4BTC in total system swallows the balance without the stop on bitsler. The same time i used a different script and it stopped after 100K lose bet with the commend that the bet is to high. What worries me is that bitsler adjusted itself to your script as 2 days ago i was winning and it run for more than 20 000 bets and yesterday and today every roll ended up after couple off thousands of bets with me loosing all. But i did not have any glitches or anything it was just red rolls over 20 lost strike in one direction i winder if script should not change hi lo durring the loosing too~?
ReplyDeleteI can add a switch after the stoploss reset, but with risking 0.001 btc reset and having 0.05 bankroll you should be able to handle 50 resets before losing your bankroll. If you ever lost more then 0.001 in a loss streak(depending which version of CR you are using) then a glitch occured. I have another version of CR with a reset after 15 Losses but often times would register a win as a loss then multiply the bet. Basically turning it into a slow way to lose your entire bankroll, regardless the issue seems to be with websites, internet connectivity on both your end and the websites, as well as a laundry list of potential others. Its all in the latest picture. I always say to watch DiceBot while using it but right now, I don't even see the point of watching it. As Seuntjie said, it was never meant to make profit, run for extended periods of time, or run unattended. Just to make gambling more fun, in my eyes it looses the fun knowing I am watching out for an error.
DeleteI have do not think Bitlser does that, simply a law of probability. Have one good day your likelihood for a bad day grows, just how it works.
PS. If you stop() the script do not use the start() command to resume betting, log out, close dicebot, then log back in and continue betting.