Another twist on the 39.6% script. This time it's a straight martingale. Every bet counts, but, it also does a reverse martingale in a win streak. once it hits 2 base bet wins, it increase by 1/2 of the previous wins profit. So when the win streak ends, your always in profit, and it increases with each win. Table bet driven, and it will bust eventually. I know this for a fact...... Prints the total balance needed to run all bets at the very beginning. Could add a check to make sure your balance is enough to cover all bets, but I know I need around 1.6 clams for these bets. Also this is not meant to be the ultimate strategy, this is just something I'm playing around with. But it does show some stuff you can do with the bot. You can use this as a base and chance it as you see fit. chance = 39.6
winbets = {.0000010,
.00000200,
.00000400,
.0000100,
.0000400,
.0001000,
.0004000,
.0008,
.0016,
.0040,
.01,
.04,
.1,
.2,
.4,
.8}
maxbets = #winbets
basebet = .0000005
totalneeded = basebet
Indx=0
for Indx = 1,maxbets do
totalneeded = totalneeded + winbets[Indx]
end
print(totalneeded)
startbalance = balance
nextbet = basebet
savefactor = 1.25
target = .01
targetbalance = balance + target
bethigh = true
low = 0
high = 0
losecount = 0
stopnow = false
totallose = 0
wincount = 0
nextwinbet = 0
function dobet()
if (lastBet.roll < chance) then
low += 1
end
if (lastBet.roll > (100 - chance)) then
high += 1
end
if (win) then
if (high > low) then
bethigh = true
else
bethigh = false
end
wincount += 1
totallose = 0
newbalance = balance
nextbet = basebet
if (stopnow) then stop() end
nextwinbet = 0
losecount = 0
if (currentstreak > 2) then
nextbet = basebet + (lastBet.profit /2)
end
if (balance > targetbalance) then
invest((balance - targetbalance)+target)
targetbalance = targetbalance + target
newbalance = targetbalance
end
if (newbalance > startbalance * savefactor) then
invest(balance-startbalance)
targetbalance = startbalance + target
startbalance = startbalance * savefactor
end
else
nextwinbet += 1
losecount += 1
print(losecount)
if (nextwinbet > maxbets) then stop() end
nextbet = winbets[nextwinbet]
wincount = 0
totallose = totallose + 1
end
end
|
|
|
|
Mind uploading these to bot.seuntjie.com/scripts.aspx?mode=new ? You'll need to register an account, but it only needs a username and password.
I added them, I forgot to title the first. And when I submitted the second I'm not sure if it took or not. If you don't see it let me know. I saved the update just in case. |
|
|
|
New bot program I wanted to share. This does a lot of advanced stuff, but the gist of it is. Start betting with .00000001 at 39.6% (2.5X) once you win increase the bet using the multiplier. if you lose cut the multiplier in half and wait for 2 loses in a row. Once you hit at least 2 in a row, on the next win try the big bet using the new multiplier. Keep doing this till you either win a big bet or run out of funds. Since we're always dividing the multiplier in half eventually is gets small enough that you large bets start getting smaller and will not cover your loses. once it gets below 1.85, it will always use that. That will cover your loses. There is also a Target value and a savefactor value. Once the balance increase to more then the target value, the difference gets invested. And the new target gets set. The balance will continue to build but you will be saving some of your funds. The savefactor is the same idea on a larger level. The bot saves your starting balance and once your balance reaches the startbalance * savefactor, it invests everything over your starting balance. It's currently set to 1.25 If I start with 10 coins, once I reach 12.5, it will invest 2.5, and I'll be back to gambling with 10. There is a variable called stopnow. If you issue stopnow = true on the console, the bot will stop once you've won a big bet. This keeps you from stopping in the middle of a series. chance = 39.6
martimulti = 40
basebet = .00000001
startbalance = balance
nextbet = basebet
savefactor = 1.25
target = .01
targetbalance = balance + target
bethigh = true
low = 0
high = 0
losecount = 0
stopnow = false
totallose = 0
wincount = 0
nextwinbet = basebet * martimulti
go = false
set = false
function dobet()
if (lastBet.roll < chance) then
low += 1
end
if (lastBet.roll > (100 - chance)) then
high += 1
end
if (win) then
wincount += 1
totallose = 0
newbalance = balance
if (high > low) then
bethigh = true
else
bethigh = false
end
if (wincount == 1 and go) then
nextbet = nextwinbet
go = false
set = false
else
nextbet = basebet
end
if (wincount == 2 and previousbet != basebet) then
if (stopnow) then stop() end
martimulti = 40
nextwinbet = basebet * martimulti
set = true
losecount = 0
if (balance > targetbalance) then
invest((balance - targetbalance)+target)
targetbalance = targetbalance + target
newbalance = targetbalance
end
if (newbalance > startbalance * savefactor) then
invest(balance-startbalance)
targetbalance = startbalance + target
startbalance = startbalance * savefactor
end
end
else
if (wincount == 1 and previousbet != basebet ) then
nextwinbet = previousbet * martimulti
martimulti = martimulti / 2
if (martimulti < 1.85) then martimulti = 1.85 end
losecount += 1
print(losecount)
else
end
wincount = 0
totallose = totallose + 1
if (totallose == 2) then go = true end
nextbet = basebet
end
end
New updated version to use a table to place the bets. Bot will stop once the table has been run. IE all bets in the table have lost. Also changed so now 2 wins or 2 loses will enable the next bet from the table on a win. Values in the table are just for my own amusement and don't mean anything. Also your mileage may vary.... chance = 39.6
winbets = {.00000040,
.00000400,
.00000800,
.00001600,
.00032000,
.00064000,
.0020,
.0040,
.01,
.04,
.1,
.2}
maxbets = #winbets
basebet = .00000001
startbalance = balance
nextbet = basebet
savefactor = 1.25
target = .01
targetbalance = balance + target
bethigh = true
low = 0
high = 0
losecount = 0
stopnow = false
totallose = 0
wincount = 0
nextwinbet = 1
go = false
set = false
function dobet()
if (lastBet.roll < chance) then
low += 1
end
if (lastBet.roll > (100 - chance)) then
high += 1
end
if (win) then
wincount += 1
totallose = 0
newbalance = balance
if (high > low) then
bethigh = true
else
bethigh = false
end
if (wincount == 1 and go) then
nextbet = winbets[nextwinbet]
go = false
set = false
else
nextbet = basebet
end
if (wincount == 2 and previousbet != basebet) then
if (stopnow) then stop() end
nextwinbet = 1
set = true
losecount = 0
if (balance > targetbalance) then
invest((balance - targetbalance)+target)
targetbalance = targetbalance + target
newbalance = targetbalance
end
if (newbalance > startbalance * savefactor) then
invest(balance-startbalance)
targetbalance = startbalance + target
startbalance = startbalance * savefactor
end
end
if (wincount == 2) then go = true end
else
if (wincount == 1 and previousbet != basebet ) then
nextwinbet += 1
if (nextwinbet > maxbets) then stop() end
losecount += 1
print(losecount)
else
end
wincount = 0
totallose = totallose + 1
if (totallose == 2) then go = true end
nextbet = basebet
end
end
|
|
|
|
New bot program I wanted to share. This does a lot of advanced stuff, but the gist of it is. Start betting with .00000001 at 39.6% (2.5X) once you win increase the bet using the multiplier. if you lose cut the multiplier in half and wait for 2 loses in a row. Once you hit at least 2 in a row, on the next win try the big bet using the new multiplier. Keep doing this till you either win a big bet or run out of funds. Since we're always dividing the multiplier in half eventually is gets small enough that you large bets start getting smaller and will not cover your loses. once it gets below 1.85, it will always use that. That will cover your loses. There is also a Target value and a savefactor value. Once the balance increase to more then the target value, the difference gets invested. And the new target gets set. The balance will continue to build but you will be saving some of your funds. The savefactor is the same idea on a larger level. The bot saves your starting balance and once your balance reaches the startbalance * savefactor, it invests everything over your starting balance. It's currently set to 1.25 If I start with 10 coins, once I reach 12.5, it will invest 2.5, and I'll be back to gambling with 10. There is a variable called stopnow. If you issue stopnow = true on the console, the bot will stop once you've won a big bet. This keeps you from stopping in the middle of a series. chance = 39.6
martimulti = 40
basebet = .00000001
startbalance = balance
nextbet = basebet
savefactor = 1.25
target = .01
targetbalance = balance + target
bethigh = true
low = 0
high = 0
losecount = 0
stopnow = false
totallose = 0
wincount = 0
nextwinbet = basebet * martimulti
go = false
set = false
function dobet()
if (lastBet.roll < chance) then
low += 1
end
if (lastBet.roll > (100 - chance)) then
high += 1
end
if (win) then
wincount += 1
totallose = 0
newbalance = balance
if (high > low) then
bethigh = true
else
bethigh = false
end
if (wincount == 1 and go) then
nextbet = nextwinbet
go = false
set = false
else
nextbet = basebet
end
if (wincount == 2 and previousbet != basebet) then
if (stopnow) then stop() end
martimulti = 40
nextwinbet = basebet * martimulti
set = true
losecount = 0
if (balance > targetbalance) then
invest((balance - targetbalance)+target)
targetbalance = targetbalance + target
newbalance = targetbalance
end
if (newbalance > startbalance * savefactor) then
invest(balance-startbalance)
targetbalance = startbalance + target
startbalance = startbalance * savefactor
end
end
else
if (wincount == 1 and previousbet != basebet ) then
nextwinbet = previousbet * martimulti
martimulti = martimulti / 2
if (martimulti < 1.85) then martimulti = 1.85 end
losecount += 1
print(losecount)
else
end
wincount = 0
totallose = totallose + 1
if (totallose == 2) then go = true end
nextbet = basebet
end
end
|
|
|
|
|
Is the bot working with JD now? I can't seem to log in.
|
|
|
|
no thats from our regular electrum server. the contest is for pasting the welcome screen
of the DOGED Tor Electrum server, that shows up in the electrum wallet once you connect.
Sorry I'm on a little tablet, and I was getting errors trying to load it up, I'll run and grab my laptop and have it up in like 10 max if no one got it yet no ones got it yet.. a cool 100,000 DOGED are waiting for the winner. Hmm, you could at least start your sentence with a capital.. Hmm, you got me worried now lol. is it a one man team, or a kid team? i hope thats a joke... It must be. He forgot to capitalize the first letter in his last sentence.  |
|
|
|
People complaining about Spots are mostly people that did not read the threads and notices and did not follow the set rules and lost out because of their own laziness/incompetence. I agree that some of Spots' decisions could have been done better especially applying a weighted avg on the last merge. However, those that followed the threads and interpreted the planned moves and coin specs properly, made tons because one could see the impact from a mile and could prepare accordingly.
Spots just takes no-nonsense and sticks to his guns. It is never possible to please everyone in this game. Remember that crypto currently is very much like the Wild West of the 1860s and everyone follows the best middle road they can. When you are moving through a jungle clearing bush with a machete, no-one can really be blamed for going left or right since there is no map for what lies ahead and at least from experience people that then follow will know don't go left there or don't go right there. At some point better generally accepted rules and regulations will form that governs things like merges, swops, new coins and the likes. In the mean time sometimes you win and sometimes you lose and anyone that does not already write off any money invested in crypto should rather go buy government bonds. This place is lawless, but necessary to produce innovation for a digital future. In that sense I like some of Spots' experiments, especially on the high POS. High POS sounded like a good idea but was not economically viable and it had to be reigned in. Bringing it into one stall was a good idea not necessary executed perfectly but taking a hair cut is much better any day than being abandoned outright.
You can love Spots or hate him and it is possible to say many pros and cons about his actions, but he is still around, taking the flack on the chin and moving forward despite all the attacks and animosity. He is sticking to his guns so far on his middle road and is much more that can be said about most other devs that disappeared, produced infected wallets, dumped premine and ran, coded hidden premine or any other blatant scamming that went on elsewhere.
[soapbox] I'm one to complain about spots. Personally I don't think he was out to scam anyone. But by his actions, he's caused a few half way decent coins to collapse. If the group wants to take them over, I say more power to you. The problem I've noticed is spots is bi-polar. He's also manipulative. Throws childish temper tantrums when people don't agree with him. Then he deletes posts, including his own. At one point during vary testing the people in BTCtalk were the best because everyone was testing out his new stuff. now, he hates everyone of them and there all fools. Someone asked for help with a conf file. Conf files are for shit coins to make them able to run. 4 posts later, add maxcon=999 to the conf file... At one point he was the greatest developer to ever live, only he could understand everything. later he admits he just started coding and didn't care for it very much. No coin control in his earlier coins, because he didn't want people gaming the system. later he explains how to do things you could easily do with coin control to game the system. I think the problem was, he didn't know how to make it work. Never a bug in his code. The whole thread is filled with him, releasing fixes. Not to mention the problems with 9 hour block times, that just had to work themselves out... I don't know if he ever fixed the problem with Stakes not reporting while maturing. His solution was to close the wallet and reopen. Or go look at getinfo the info is correct there. It's his coin, and he's going to do whatever he feels is best. Everybody was complaining so I had to change it. My whole problem with his coins. He can't seem to stick with anything for very long. Something new comes along and there is a hard fork. Things not working exactly as expected, create a new coin and merge things. The great and powerful spots couldn't figure out how to make a coin that would just use a snap shot of the old chain and assign the new coins to addresses based on that. AKA Clams. Would have saved all of the bullshit, send me your keys/wallet and you only have 60 mins for this offer.... He slams Hyperstake every chance he gets. At least that coin has stuck to it's guns, and after some interesting inflation, seems to have settled down. Plus it has a hella development group. He's had some interesting idea, It's to bad he felt the need to change things and have them come crashing down. [/soapbox] |
|
|
|
I've probably mentioned this before, but I've never seen an orphan.
Over 3 headless clients (of varying versions) I have minted more than 500 blocks over the past year, but not one of them shows an entry for an orphan.
I don't know whether it's just pure luck that all my generated blocks went through, or if there have been orphans, and for some reason they have not been recorded as such. The former seems unlikely.
I don't know if the headless client keeps track of the blocks it staked that were later orphaned. Most (if not all) of the other clients I use list orphans, so I don't understand why CLAM wouldn't. A block which is subsequently orphaned starts as a valid transaction, right? So the client would actually have to delete the transaction from the wallet, rather than just changing its status from immature to orphan. Another possibility is that 'listtransactions' simply ignores orphans, but ListTransactions in rpcwallet.cpp does refer to entry.push_back(Pair("category", "orphan")). Does the QT client show orphans? If so, why is the behaviour different with the headless client? The Qt client shows the orphans under transactions. I run a headless client for staking, and then a QT client for monitoring. The QT shows the orphans, even though they are generated by the headless guy. They have 2 different copies of the same wallet. Just stating the facts. I have no idea why it seems to work. I always thought the wallet just had your addresses and Keys. The rest is figured out from the block chain and stored in the database files. For some reason an orphan on one machine is showing up in the transaction history of another client. |
|
|
|
Thank you Friends for the kind words..I just updated asset sheet on the most part, just need to ask Chilly if our clams have grown this month
Done. Ellie, I sent you a PM with the info. I've made another donation to the clams stockpile. We're now at 51.89 clams and climbing. |
|
|
|
Do you guys recommend combined the blocks after each stake my balance is 633 right now. They are staking, should i combine them or leave them as is?
what do you suggest for having better luck when it comes to staking?
I've tried blocks of 50 and blocks of 5. I'm currently using splitsize = 5 and combinelimit = 5 . These are set in the clam.conf file. After watching my staking info in the debug log, and now tracking it for a bit, I'm finding that looking at one days data is not the way to go. And at your number of clams, I would think you'll need to look at, at least 2-3 weeks data to get an idea how your doing. One day you might get 2-3 stakes and the next few days get nothing, and think something is wrong (at least I did). Also an interesting point. I usually end up staking when the network weight is on the high side. I would expect my staking to go up as the weight decreases but thats not the case. I'm doing this more to help the network, then to try to beat Just-dice. As long as I'm "somewhat" close I'm happy. |
|
|
|
Would the orphans % be number of orphans / total stakes (valid + orphans)
Yes. for the last week.
date Starting balance Stakes Percentage orphans. orphan %
7/13 2546 5 .1963
7/12 2540 6 .2362
7/11 2537 3 .1182 1 25%
7/10 2532 5 .1975 1 17%
7/09 2531 1 .0395 1 50%
7/08 2531 0 0
7/07 2527 4 .1583 1 20%
7/06 2519 8 .3176
I guess 2500 is too small a number to quickly get an idea of the orphan rate, but that looks like 4 orphans out of 36 stakes, or 11% so far. The variance is huge, with your daily orphan rate ranging from 0% to 50%... Went back and looked at Mar/Apr and May. I didn't have the patience to calculate how many Clams I had on each dates, so I just looked at the total stakes Vs orphans. March 131 stakes 5 orphans. 3.7% April 124 stakes 8 orphans 6% May 141 stakes 0 orphans April was interesting. There were 5 orphans between the 5th and 7th. I don't remember anything going on, on my end at that time... Then just for giggles I went back to Oct. This would be before JD came online Oct 61 stakes 3 orphans. 4.7% So I don't think the 15% orphan theory is really holding up. I'm guessing I end up averaging about 4-6% orphans. And that hasn't really changed since JD started. I was going to look at Nov, but the 11th was he hard fork, and I ended up on the wrong chain for a little while. 24 orphans in 3 hours... not good for the statistics. |
|
|
|
If he goes much longer without getting payments to people, I'm going to go ahead and report he and his partner to the local authorities. This has been stretched out long enough and if nobody is getting paid, there's no reason to keep the hounds at bay anymore.
pff i doubt that they will do anything about it will they? they will say that they did not use real money thats why it was not a real crime, though its just my opinion about it Also thats false. Bitcoin is property, one also has to pay taxes on it since it is recognized by the irs. So yeah stealing property last time i checked is a crime. Freejack i suggest you dont wait much longer. "Bitcoin is property" in some places. Not sure where Mr arbs lives but I have a feeling, you will have to somehow, get to his local authorities. I know locally the police act like secretaries for the insurance company's. They don't plan on solving a crime, unless something drops right in their lap. Please keep us informed, even if you seem to get no where. I'd be interested in what you try and what they can do for you. |
|
|
|
If he goes much longer without getting payments to people, I'm going to go ahead and report he and his partner to the local authorities. This has been stretched out long enough and if nobody is getting paid, there's no reason to keep the hounds at bay anymore.
pff i doubt that they will do anything about it will they? they will say that they did not use real money thats why it was not a real crime, though its just my opinion about it However, they actually DID use real money...they also accepted deposits in USD. Realistically, .05 BTC every couple of months isn't doing it for me anymore either...I haven't reported them, after having confirmed their identities (at least two of them) because it seemed like there was still a chance people would get paid back. The effort to do so has been SERIOUSLY lacking, though - so I'll probably send the collected info to the authorities, unless we see some serious movement soon. I won't miss the $15 or so every two months and these guys need to answer for what they've done. Keep us posted, and let us know if we can also be added to the complaint. Not sure that you can report anything other then what you personally are owed. |
|
|
|
This is one of the risks self staking carries...
Indeed, although of course there are risks with pooled staking too. Dates Start Balance Stakes Avg/Day Percentage Orphans
6/22- 6/28 (7 days) 2456 37.0027 5.2861 2.15% 2
6/29 -7/5 2493 26.0005 3.7144 1.49% 2
7/6 - 7/12 2519 27.0009 3.8571 1.53% 4 - I think 2 of these were due to my own network issue.
The percentage would be better as a per-day number, and it would be interesting to see orphans as a % too. Did you stake 31 times most recently but only 27 survived? Or 27 times and only 23 survived? Either way, that's about a 15% orphan rate isn't it? The stake number is actual stakes, not including orphans. Would the orphans % be number of orphans / total stakes (valid + orphans) for the last week. date Starting balance Stakes Percentage orphans. orphan % 7/13 2546 5 .1963 7/12 2540 6 .2362 7/11 2537 3 .1182 1 25% 7/10 2532 5 .1975 1 17% 7/09 2531 1 .0395 1 50% 7/08 2531 0 0 7/07 2527 4 .1583 1 20% 7/06 2519 8 .3176 |
|
|
|
So to effectively stake I should invest my CLAMs at Just-Dice? Is there any real downside to that?
I had thought they would constantly stake, but I only have my computer on for a few hours a day, so guess it isn't going to be worth it in the clam wallet.
I updated to the new wallet and now it says I should stake in 1 day! A big difference!
If you invest at Just-dice you will make more money, but you will be contributing to CLAM being centralized. I had to see how this played out. from 6/22 - 6/29 I staked 41.0029 clams the starting size was about 2450 So 7 day at an average of 5.8576 per day. Would give .00239 % I always see .002% just staking on JD. which would be 4.9 clams per day. So in my case staking alone is much better an extra 6.7 clams in 7 days. or 350 clams a year. This was a small sample and your mileage may vary. But it does show that staking solo can be done and can compete with JD. There were 2 orphans in the sample. And I believe one was when I was staking a new block of 250 clams and splitting the output into blocks of 5. I think that took 2 tries. Try this again. Dates Start Balance Stakes Avg/Day Percentage Orphans 6/22- 6/28 (7 days) 2456 37.0027 5.2861 2.15% 2 6/29 -7/5 2493 26.0005 3.7144 1.49% 2 I'll try to keep this up for another 2 weeks, to see how variability comes into play. My stakes have been all over the board from a low of 2 per day to 8 per day. So over times we should see how it levels out. This week I lost almost 48 hours of staking due to a self inflicted power problem / internal network issue. This is one of the risks self staking carries... Dates Start Balance Stakes Avg/Day Percentage Orphans 6/22- 6/28 (7 days) 2456 37.0027 5.2861 2.15% 2 6/29 -7/5 2493 26.0005 3.7144 1.49% 2 7/6 - 7/12 2519 27.0009 3.8571 1.53% 4 - I think 2 of these were due to my own network issue. |
|
|
|
We can start by using the basic Martingale script from the reference site. chance=49.5 multiplier=2 base=0.00000010 function dobet()
if win then
nextbet=base
else
nextbet=previousbet*multiplier
end
end
The 3 statements before the function statement will be executed BEFORE the first bet is made. chance is a variable that will be used by the bot. multiplier and base are internal variables just used by the script. After each bet is placed function dobet is called. In this case, if the bet won, the variable win will be true and the script will reset the nextbet variable to the base bet. nextbet is a variable used by the bot when placing a bet. If the win variable is false, then we lost the bet. The script will execute the else path. This will set nextbet equal to the previous bet (previousbet) times multipler. In this case X 2. The structure LUA uses for if/then/else requires an end statement. And the function requires an end statement. A few things I would add to the initialization section. I would set nextbet = base so the first bet is base on my script not what is filled in the bot's panels. Also set bethigh Make it true if you want to go high, false if you want to bet low. It's as easy as bethigh = false So my really basic script would be. chance=49.5
multiplier=2
base=0.00000010
nextbet = base
bethigh = false
function dobet()
if win then
nextbet=base
else
nextbet=previousbet*multiplier
end
end
To execute this script, in the programmer mode section click on the console tab at the top. This opens the LUA console. The upper section is the output and the lower section is for input. In the lower section you would type start() to start your script. And stop() to stop it. You can also use the built in simulator to see how your script will run. Either from the built in simulator panel (click view, then simulate) ir by typing runsim (X,Y) into the console. X is your pretend starting balance Y is the number of bets to place. Note: Don't start your bot with a large balance. A small error could cause you to lose everything. Always start with a small amount just to test out all of your functions. Of course use the simulator to flush out as much as you can. So we left off with the basic martingale bot setting the correct first bet. But there is no way to stop this other then issuing the stop() command. This is where we can use one of the neat things about LUA. You can set variables from the console. So were going to initialize a variable called stoponwin to false. Then check this in our win path. The variable will always be false till we change it on the console. So our new code will not be. chance=49.5
multiplier=2
base=0.00000010
nextbet = base
bethigh = false
stoponwin -- new variable
function dobet()
if win then
if (stoponwin) then stop() end -- check new variable.
nextbet=base
else
nextbet=previousbet*multiplier
end
end
so now if we wanted to stop the bot once a series is finished we can issue "stoponwin = true" at the console, and the bot will stop the next time it wins. |
|
|
|
It's close. Any idea what would give this error "input:18: unexpected symbol near '!'" ? So it looks like "(!win)" is the opposite of (win). But when I run it in the Lua demo ( http://www.lua.org/cgi-bin/demo) it doesn't like it. I thought in order to do the opposite we just do "not" so instead of "!win" it would be "not win" but if I do that it just bets the same bet over and over instead of doing martingale. The problem wasn't the !win. Lua was expecting an end for the "if win" Statement. I was trying to leave your logic the same but missed that end statement. So the code is
chance=49.5
multiplier=2
base=0.00001000
resetseed()
profitsincelastcycle = 0
function dobet()
profitsincelastcycle += lastBet.Profit
if (win) then
if (profitsincelastcycle == 0.00004000) then
sleep(300000)
profitsincelastcycle = 0
else
nextbet=base
end
end -- Missing end statement
if (!win) then
nextbet=previousbet*multiplier
end
end
Personally I would have handled the !win part in an else path. But to each there own, and it's better that you understand what it's doing then I. Should I be able to see the simulator pause or stop with the "sleep(300000)" command in there? Or does that only work when it's running real bets? When I run the sim, martingale works correctly but I don't see any sleep. Did you cut/paste the above script? Simulator will wait/loop. It actually hangs the bot with the spinning circle thingy.... Are you incrementing profitsincelastcycle? Are you checking the same variable? You can check things out on the console. type "print(profitsincelastcycle)" no quotes, to see what that variable contains. |
|
|
|
|
I've been playing around with a few more options of the bot.
It seems when you run the simulator and it ends, the profit reported is the total profit from the stat's info. I was expecting it to just be the profit from the current run.
The same thing with the profit variable. It's not set to zero when you start() your script. I believe bets, wins, and loses are also from stats.
I'm not sure whether or not you should clear it. But maybe making a resetstats() function in the programmer mode function could be an option. I personally would always call that at the beginning of my script. But some might like the way it behaves now.
|
|
|
|
It's close. Any idea what would give this error "input:18: unexpected symbol near '!'" ? So it looks like "(!win)" is the opposite of (win). But when I run it in the Lua demo ( http://www.lua.org/cgi-bin/demo) it doesn't like it. I thought in order to do the opposite we just do "not" so instead of "!win" it would be "not win" but if I do that it just bets the same bet over and over instead of doing martingale. The problem wasn't the !win. Lua was expecting an end for the "if win" Statement. I was trying to leave your logic the same but missed that end statement. So the code is
chance=49.5
multiplier=2
base=0.00001000
resetseed()
profitsincelastcycle = 0
function dobet()
profitsincelastcycle += lastBet.Profit
if (win) then
if (profitsincelastcycle == 0.00004000) then
sleep(300000)
profitsincelastcycle = 0
else
nextbet=base
end
end -- Missing end statement
if (!win) then
nextbet=previousbet*multiplier
end
end
Personally I would have handled the !win part in an else path. But to each there own, and it's better that you understand what it's doing then I. |
|
|
|
Isn't this info already in the bot.seuntjie.com website? I thought discussion might be more productive. Do you actually know how to make a good pause/rest/wait function into this bot or were you just teasing me?
Why would you want to pause/rest/wait at all? The time of the bet has no influence on the result of a roll? I really don't see a point to using something like this but since you're asking for it, you can just use sleep(milliseconds:int) Awesome, thank you. Well, the rationale is that I think the timing of the bets actually is important so I'd like to test my ideas and I'd like as much flexibility as possible to test every idea I might have until one of them actually works. I'm a little dismayed at such doubt and would just like the freedom to explore different ideas even if they are known failures it could generate a better idea later. I hope folks can understand this. So this "sleep(milliseconds:int)" Since I suck at syntax and tried/failed as soon as I saw it posted... can you elaborate on how this would actually work in a script? For example, my intent was to stop every 10K satoshi profit for "sleep(300000)" or 'five minutes' but my code looked like this and when I ran the simulator I didn't notice any pause. Will I notice a set 5 minute pause in the simulator? also, I want to send a resetseed every 5 bets (I know... I know... it won't reset every 5 seeds... please enough with the Questions...) Can you tell me how to fix this code below? Actually, can anyone answer my original question, "How do you make it pause after a certain level of profit and then make it start backup automatically after the pause and restart the profit counter?" Here is the code I tried: chance=49.5
multiplier=2
base=0.00001000
resetseed=5
function dobet()
if win & profitsincelastcycle == 0.00004000 then
sleep(300000)
else
nextbet=base
end
if not win then
nextbet=previousbet*multiplier
end
end
Lua is a fickle language. Your problem is not with the sleep. resetseed is a function. Your treating it as a variable. If you really want to reset the seed just code resetseed() It doesn't take a parm. I think there was a discussion about passing in the client seed at some point but not yet. also profitsincelastcycle is an undefined variable. Lua throws up on those too. Try this
chance=49.5
multiplier=2
base=0.00001000
resetseed()
profitsincelastcycle = 0
function dobet()
profitsincelastcycle += lastBet.Profit
if (win) then
if (profitsincelastcycle == 0.00004000) then
sleep(300000)
profitsincelastcycle = 0
else
nextbet=base
end
if (!win) then
nextbet=previousbet*multiplier
end
end
The only thing missing in the above code is what to set nextbet to when you hit your profit cycle. Currently it will just end up being whatever it's set to. And I made the mistake of doing the sleep(30000) and running the simulator. It hung for 30 seconds each time it hit that. Basically hung up the bot. So thats not a true sleep. More a loop for that many seconds. |
|
|
|
|
Show Posts
