|
btw Seuntjie, what kind of "built-in variable" do not working at simulation?! i know there is something wrong. like example simulation dont use "profit from stats statesment" you need to write manual "own roundprofit" to use that kind of things, but what else?! simulation using "currentstreak"? etc or everthing are need to be written by "own"?!
my target is to say, simulation dont use currentstreak right or not at all in it, can be?!
|
|
|
|
how I can simple make something:
if currentstreak "every number" then
do something
end
11111222223333344444
for example every 5 streak next 5 streak made nextbet = previousbet + 0.00000001
Do you mean every 5 loss streak? 5 win streak? or something else? Personally, I would do something like: myLossStreakCounter = 0
streakLimit = 5
function dobet()
...
if (!win) then
-- If it was a loss, increment the counter
myLossStreakCounter = myLossStreakCounter + 1
end
...
if myLossStreakCounter == streakLimit then
-- reached the streak limit, increase bet and reset counter
nextbet = previousbet + 0.00000001
myLossStreakCounter = 0
end
...
If should be relatively obvious how the code can be modified to be used for a Win streak I dont understand, last period when bot was updates with this "blue words" in code box, they dont like = simbol.
'then' expected, got '='
This error suggests that you have a syntax error in your code. The bot thinks you're trying to use an "if something then" command, but it can't find the "then" part of the command before it finds an "=". Usually it shows a line number where the error occurred. Check near there for incorrect code... failing that, you'd need to post the code for others to be able to debug it properly. thanks! |
|
|
|
hello, what possible problems can be that dicebot are get msg and closed "dicebot has stopped working" checking for solution etc. when try to run simulation?!
Are you using the latest version of the bot (3.4.4)? Which site do you have selected when this happens? How many bets are you simulating? How long does it take between clicking start and the crash? yes 3.4.4 does that make sense which site are selected when im trying to run simulation? its YOLO, but after this commend add I will try change another. bet numbers are nothing, there is no change if I write runsim(0.1, 999) or runsim(0.1, 100000) or something. between press enter and crush are 1-2seconds. update, you know, after changing site simulation are not crushin... wtf  |
|
|
|
|
how I can simple make something:
if currentstreak "every number" then
do something
end
11111222223333344444
for example every 5 streak next 5 streak made nextbet = previousbet + 0.00000001
I dont understand, last period when bot was updates with this "blue words" in code box, they dont like = simbol.
'then' expected, got '='
|
|
|
|
hello, what possible problems can be that dicebot are get msg and closed "dicebot has stopped working" checking for solution etc. when try to run simulation?!
And no problem running the bot in the normal (rolling) mode ? I never really used the simulation because it wasn't that fast. Is that still not that fast or have that improved in last versions? all was fine with simple betting bot 24/7 without errors  |
|
|
|
|
hello, what possible problems can be that dicebot are get msg and closed "dicebot has stopped working" checking for solution etc. when try to run simulation?!
|
|
|
|
The best explanation including a mathematical formula I have found is this one: Winning and Losing Streaks Formula The longest expected losing streak (or winning streak) can be calculated using the following formula:  n = number of trials (i.e. total number of bets) ln = natural logarithm 1P = probability 2 | .. | = absolute value or ‘modulus’ 1 - Suffice to say, explaining what natural logarithm is would be worthy of a series of articles. For the time being, use Excel to calculate this for you.2 - For winning streak calculations use the positive value (i.e. the probability of winning). For losing streak calculations use the negative probability value. For example, if the probability to win the bet is 33% then the probability that the bet loses (negative probability) is 67%.If you want a formula for Excel or Google Sheets it would be: "n" = number of rolls "p" = needs to be expressed as percentage value between 0-1, so (percentage / 100). ie. 60% = 0.60, 5% = 0.05 You can see it in action here: https://docs.google.com/spreadsheets/d/1T7k5KVUwB606rfyrCrfZNTs8xyVyF7C-0PLlIPzaU8oIt seem incorrect n = 4166576 p = 0.0495 => 3358.8 (3359) While my actual result is currently at 1744 after above "n" rolls (ever seen of 2100-2300++ but not 2400++), it might be correct if above result is not "mean" or "average" but it is "rare", "extremely rare" streak. you cant get never in reality with probably fair dice game with ~1% HE more than ~400 loses in row on 4.95% winning chance. (even on simalator with 100m bets)! on 0.495% (half of 1%) you can get this 3,3k loses in row till 4k loses in row. so your manual calcualted results or whatever from where you get it its totally wrong, please show me proof where you get on ~5% winning change more than 350 loses in row at all in your life! |
|
|
|
finally stable version, without crashing after many running days, even watching "alltime graph" not crushing it after few days  thanks! |
|
|
|
Hey, iv made some "real play" tests. there in image you can see 1 million bets of playing. https://imgur.com/a/jYokhZw this is with basebet 1satoshi and 100k br and without stoplose limit at all, you can see that two times in 1 million bets you was been hitten 20k unit streak, but never 30k unit streak. without stoplose your winrate are something around ~0.083/per bet in this graph 1 000 000 bets with 1satoshi basebet ive made ~83 000 satoshis. if you made stoplose lets say 20k units, and after reach losing round of 20k units, you will reset to start, in this 1m bets you hit it 2x times, it means you not get 83k unit profit, but 83k - 40k(2x 20k) = 43k units per 1m bets with stoplose 20k units. its ~0.043/per bet winrate! but for me its not finish, there is need to test more, more and more. from this distance you was never get 30k units streak, so need to test more million bets, to find perfect/better stoplose number. from this graph you can see that in every case profit will cover any lose spike with propper and thinking stoplose using! |
|
|
|
According to Microsoft... the limits on Excel should be: Total number of rows and columns on a worksheet: 1,048,576 rows by 16,384 columns Still not quite enough if you have 100+ million lines... I'm not sure of many data packages that can deal with that much data outside of very specialist packages like Matlab etc.  when I was imported my file, excel says something about 32 000 rows or lines limit idk, my excel was not in english language, but russian... hmmm what is Matlab at all, hearing first time, need to watch google |
|
|
|
|
Hello, so after 1,5 year of heard about crypto at all and dice game, im doing some testing, reediting, making scripts - and only now iv found "gold middle road"
maybe other/many of forum seen me in YOLOdice, I have there 13 different account for "ingame" testing, and made "offgame" 1000millions+ bets simulations.
so about script:
-its not short distance "hit and run" thing like other roulette players doing.
-script are made for longrun, it means he can be under break even point some time, even 10k bets(statistic side I will publish later when Iv collect more data)
-its some kind of middle winning percentage made, not low chance build where variance can be bitch and can kill you.
-its not targeting to get every losing bet to profit or break even point.
-script can't lose because of max possible losing streak in row.
-script will be profiting if luck will be 90-99% close to normal(depends on how much, and how big losing streak is in this last period from last "high") real winrate will occurs when ~33%+% of max losing streaks are gettin.
-earning outcome(winrate) from script are ~0.018/per bet(basebet/~55 times, it means, if your basebet will be 1000(satoshi, litoshi whatever), your estimated income will be 18 per every bet you made)
it means every ~6 million bets, your will get double up your bankroll size. (bankroll size need to be 100 000 units)
so what does that means? for example, if you play in YOLOgames with good betting speed 5bets/sec, in month you can made around ~12 million bets, this means every month you can earn 2times a bankroll(with good monitoring when site has updates and bets are stopped, and run it 24/7)
of course time after time maybe you can lose your 100 000 unit bankroll(idk maybe 1-3 times in 100million bets), but in any case your winnings will cover all loses in longterm. (script are passed 10million bet simulation, and bankrollsize are grown ~280%(initial bankroll+90%ofbankroll+90%bankroll)) every 5 million bets + 90% of bankroll. (maybe theoretically if you play with 1 000 000 unit BR you never will lose)
for my computer to do 10millions bets of simulation I need ~75hours, so later will be more accurate results.
when I will made 10x 10millions of simulations, I will post results with expected win/lose rate.(how much times in 100million bets he can lose 100k unit BR)
so what Im offering and why?
Im selling this script for not small money, maybe some rich gambler or whale want to better buy script and start to make slow passive but safe earnings, not simple catch adrenaline from gambling.
not small money, I mean 5 digit number in currency and another 4digits in cryptocurrency.
you will ask why I selling it? short story: things get not so good for me, i was been full time poker player 5 years for living till 2015, then I have problems in my personal life and stopped playing and now I was working poor people 9-5h work. I want it all back, quit job, continue my poker carrer and get passive earnings from dice, but I have not budget for that all.
btw, can give you the proof of simulations, if anyone can teach me how to make graphs in MS Access from .csv file(from seuntjie dicebot simualtions)
if you are interested, please write here or private messages.
*sceptic small minded people, please don't comment about things what you don't understand.
|
|
|
|
|
anyone know how to make graph from very very big .csv database what are exported from simulation?!
excel are crushing, and dont allowed to open more than 30k lines.
trying with access but im newbie there... there cannot be opened more than collumns rows at same time.
need to make graph from i thinks more than 100+ million lines and rows, from 10million bets simulation.
any one can help me, please?!
|
|
|
|
basebet = 0.15000010 nextbet = basebet chance = 33 function dobet() if (win) then if currentstreak == +1 then nextbet = previousbet*1.9 elseif currentstreak == +2 then nextbet = previousbet*1.9 elseif currentstreak == +3 then nextbet = previousbet*1.9 elseif currentstreak == +4 then nextbet = previousbet*1.9 elseif currentstreak == +5 then nextbet = basebet*2 elseif currentstreak == +6 then nextbet = previousbet*1.9 elseif currentstreak == +7 then nextbet = previousbet*1.9 elseif currentstreak == +8 then nextbet = previousbet*1.9 elseif currentstreak == +9 then nextbet = previousbet*1.9 elseif currentstreak == +10 then nextbet = basebet*3 elseif currentstreak == +11 then nextbet = previousbet*1.9 elseif currentstreak == +12 then nextbet = previousbet*1.9 elseif currentstreak == +13 then nextbet = previousbet*1.9 elseif currentstreak == +14 then nextbet = previousbet*1.9 else nextbet = basebet end end if (!win) then nextbet = basebet end end end end thins kind of stuff, its not frequent bug, it's rare, but time after time, maybe 2-3 times in day(24hours/400 000 bets) bot are makind "missbets" when they need to stop increasing, and bet "basebet" they keep betting one more bet... maybe its web site bug(YOLOdice) because time ago iv found that they have problems with fast updating balance, and then many of bugbets occurs with very fast betting, if balance are not updeiting right in milliseconds, and basebets are calcualted from currrent balance at the moment but this one seems like bot bug, because of very fast bets. and yes another thing, new update had bugs when minimizing bot, and do some things. https://imgur.com/a/gjA9vMsIs that your whole script? Can you include a screenshot of it happening please? You should learn how to use the modulus (%), larger than (>) and less than (<) operators, it will make your scripts much shorter, easier to understand and more efficient. Re the minimizing bug: https://bot.seuntjie.com/bugreport.aspx?id=4169yes this script make that what im talking about. yes I need to learn more things I will be difficult to play and try to catch another one time... but what I can say, really nothing you will see, simple in graph will be tryed to catch 6 winning streak, when my script was made for catching only 5 winnings in row, and then decrease betsize to basebet(or basebet*2) and in console you simple will be 5 winnings in row, and bet 6th with increase while bot/script need to decrease it to basebet. its simple some kind of functionally error because of abnormal veryfast bets without speed limit. |
|
|
|
The obvious solution is to bet slower...  How is the script detecting the wins/losses? Are you using inbuilt streak values or using "custom" variables? if currentstreak == X then nextbet = X elseif currentstreak == X then nextbet = X else nextbet = basebet using this kind of thing. Can you post a screenshot of it happening, including your script? It is more likely that it is something in your script causing this, and if you (like always) refuse to post your script (even in pm) so I can look into the issue, I'm not going to look into it until I get another, independent report of it happening. From the way the programmer mode works and when and where the bot assigns variables to and reads variables from the programmer mode, it is highly unlikely that it's a timing issue or has anything to do with the betting speed. If you do post your script (or PM/email it to me), I will look through the script to see if I can find anything and let you know what's wrong with it. If I don't find anything, I will take steps to try to reproduce the problem and if I can find the problem, I will fix it. basebet = 0.15000010 nextbet = basebet chance = 33 function dobet() if (win) then if currentstreak == +1 then nextbet = previousbet*1.9 elseif currentstreak == +2 then nextbet = previousbet*1.9 elseif currentstreak == +3 then nextbet = previousbet*1.9 elseif currentstreak == +4 then nextbet = previousbet*1.9 elseif currentstreak == +5 then nextbet = basebet*2 elseif currentstreak == +6 then nextbet = previousbet*1.9 elseif currentstreak == +7 then nextbet = previousbet*1.9 elseif currentstreak == +8 then nextbet = previousbet*1.9 elseif currentstreak == +9 then nextbet = previousbet*1.9 elseif currentstreak == +10 then nextbet = basebet*3 elseif currentstreak == +11 then nextbet = previousbet*1.9 elseif currentstreak == +12 then nextbet = previousbet*1.9 elseif currentstreak == +13 then nextbet = previousbet*1.9 elseif currentstreak == +14 then nextbet = previousbet*1.9 else nextbet = basebet end end if (!win) then nextbet = basebet end end end end thins kind of stuff, its not frequent bug, it's rare, but time after time, maybe 2-3 times in day(24hours/400 000 bets) bot are makind "missbets" when they need to stop increasing, and bet "basebet" they keep betting one more bet... maybe its web site bug(YOLOdice) because time ago iv found that they have problems with fast updating balance, and then many of bugbets occurs with very fast betting, if balance are not updeiting right in milliseconds, and basebets are calcualted from currrent balance at the moment but this one seems like bot bug, because of very fast bets. and yes another thing, new update had bugs when minimizing bot, and do some things. https://imgur.com/a/gjA9vMs |
|
|
|
The obvious solution is to bet slower... How is the script detecting the wins/losses? Are you using inbuilt streak values or using "custom" variables? if currentstreak == X then nextbet = X elseif currentstreak == X then nextbet = X else nextbet = basebet using this kind of thing. |
|
|
|
|
Hey, last update had bug, time after time, when bets are fast 5+per/sec then he will missread script and do not what he need to do
like sample:
after X loses or wins in row, he need to place basebet, but he are not doing it in 5th bet, but only in 6th bet, because of fast bets.
with small basebet and slow bets, this is not occurs.
what is/can be sollution?!
|
|
|
|
Your script doesn't always recover. Im playing on stake.com with a 1% house edge. is there a setting i can edit? im using the "SCRIPT FOR PLAYERS USING BANKS LESS THAN 0.05000000 IS PROVIDED BELOW - ENJOY!" script   Any bot will have the same result, the longer you played, you will lose your entire balance up, there is no way you will get a good result by keep on playing because there is always house edge. Because what I know his dice script is pretty save to play with small amount so there is no way you will bust so fast just to get a few satoshi around. Either you are being greedy or may be luck does not apply it yet on you you cant beat house edge if you talk about flat betting! how house edge are disturb you? house edge is fixed, so all other its in your hands, don't talk one and the same shit everywhere all day long. "bla bla bla, you cant beat house edge, etc." YES you can't with flat betting, you can't bet flat basebet and be break even in the longrun, because you will be eaten. otherwise HE are dont distrubing you. |
|
|
|
Your script doesn't always recover. Im playing on stake.com with a 1% house edge. is there a setting i can edit? im using the "SCRIPT FOR PLAYERS USING BANKS LESS THAN 0.05000000 IS PROVIDED BELOW - ENJOY!" script with given settings is unreal to be above bre ak even, and from winning cover losing roundups. everyone need to think with own head and do some calculations, and rebuild/reedit script for self. in your given screenshots i dont see anything dont typical, its sh*t not distance, omg 600bets, play 1millions bets, then watch... (but with given settings you will can't survive 1million bets) watch screenshot :  https://imgur.com/a/iJlmGVQthere you can see that "its normal to get swings" where you will be running under EV(under luck) but after that you will recover all(with good configured and calculated script and proper bankroll managment) or even with that swing, you are +EV in the long run. thinng is that simple, you need to find "middle" where your profit from winning streak(above EV/luck) covers loses from loosing streaks(below EV/luck) and you can survive worst deviations from "normal"(0) with your bankroll size in screenshot its the same helloguys script, reedited and recalcualted by myself. |
|
|
|
|
going up - jackpot edition, you saying you was get 3x(hitting stoplimitround 25%) losing roundups in 100 000 bets, but im get it every 10k bets, maybe even frequent. how much bets you tested that script?!
|
|
|
|
math.random has 3 possible variations:
math.random() = generates pseudo-random "real" numbers between 0 and 1
math.random(m) = when m is an integer = generates pseudo-random integer numbers in the range [1,m]
math.random(m,n) = when m and n = generates pseudo-random integer numbers in the range [m,n]
So, in your example, it will be generating numbers in the range [45,50]... or in other words, a "random" number selected from 45,46,47,48,49 and 50.
There is no auto-start built into dicebot... you might be able to achieve it using some sort of 3rd-party Windows automation tool, but it isn't possible within the confines of the dicebot
big thanks for answer HCP, its really made me understand that math.random "thing"! |
|
|
|
|
Show Posts
