What's the difference between the following variables?
Profit
currentprofit
tmpprofit
At the top of the code tab, in programmer mode, there is a list of available variables. profit and curentprofit are listed there. That is a list of variables already defined for your script. RO can only be referenced RW can be changed. I believe profit is your current session profit from the last resetstat call. currentprofit is the profit from the last bet. both could be + or -. tmpprofit is not used by the bot, but could be defined in your script. a lot of time you may want to do something till you hit a set profit. At the beginning of you script you could have tmpprofit += currentprofit. That would now keep a running total of you profit since tmpprofit was set. Later you might check, if (tmpprofit > 4) then withdraw 3 and tmpprofit = 0. Setting tmpprofit to zero starts your profit calculation over. So if I were to have if currentprofit=-0.00000050 then it would mean that once I have a negative value of 50 satoshi I would want the script to do something? if currentprofit == -0.000000050 then <---- This is saying check the last bets profit and if it's equal to -50 satoshi's then do something. (notice the double equal signs, you want to tell LUA this is a compare and not an assignment) I normally have resetstats() above the function dobet() Then you could have if profit == -0.00000050 then To do something if my profit for this session has dropped to -50 satoshi's so... currentprofit is the last bets profit and profit is the sessions profit |
|
|
|
What's the difference between the following variables?
Profit
currentprofit
tmpprofit
At the top of the code tab, in programmer mode, there is a list of available variables. profit and curentprofit are listed there. That is a list of variables already defined for your script. RO can only be referenced RW can be changed. I believe profit is your current session profit from the last resetstat call. currentprofit is the profit from the last bet. both could be + or -. tmpprofit is not used by the bot, but could be defined in your script. a lot of time you may want to do something till you hit a set profit. At the beginning of you script you could have tmpprofit += currentprofit. That would now keep a running total of you profit since tmpprofit was set. Later you might check, if (tmpprofit > 4) then withdraw 3 and tmpprofit = 0. Setting tmpprofit to zero starts your profit calculation over. |
|
|
|
LUA ERROR!!
assignment statement expected, got 'function'
chance=49.5
multiplier=2
base=0.00000010
nextbet = base
bethigh = false
stoponwin
function dobet()
if win then
if (stoponwin) then stop() end -- check new variable.
nextbet=base
else
nextbet=previousbet*multiplier
end
end
end
The function mentioned in the error, is the dobet() function. So look at the statement just before it. stoponwin is not valid for an assignment statement. You need to tell LUA what stoponwin is equal to. I think you want stoponwin = true |
|
|
|
Update, still not working. I tried this if profit <= -0.000500 then
nextbet=basebet
resetstats();
resetseed();
end It resets the stats but it keeps going with the same bet, the nextbet doesn't return to basebet. (I have basebet variable determined) Please help me out, thanks! can you post your whole script and explain what your'e trying to do? Thanks for replying! This is the whole script - Pluscoup by chilly2k and grendel25 (I got it from your website). basebet = 0.00001000
nextbet = basebet
roundprofit = 0
chance = 49.5
minbal=balance-0.0300000
maxbal=balance+0.01500000
function dobet()
roundprofit += currentprofit
if (win) then
if (roundprofit < 0) then
nextbet = previousbet + basebet
print ("WIN")
print(nextbet)
else
nextbet = basebet
print ("WIN")
print(nextbet)
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
if roundprofit > 0 then roundprofit = 0 end
end
if (!win) then
nextbet = previousbet
print ("LOSE")
print(nextbet)
end
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
end
end What I am trying to do is this: when the profit (not whole account profit, just the session before resetstats) goes lower than 0.0005 for example, at fist I wanted the bot to stop and then restart but you told me it's not possible, so now I want it to reset the bet to basebet and also resetstats. I tried with this: if profit <= -0.0005 then
nextbet=basebet
resetstats();
end ... and it's not workin, it resets the stats but the bet doesn't go to basebet, it stays where it was. Thanks for your time and I hope we figure it out! Your not saying/showing where you put that code. If you put it just before the last end statement, I think it should work. If you were trying it at the top, nextbet would get reset further in the code. Just for educational purposes, the last end statement close the dobet() function. Hi, thanks for jumping in. I tried placing the code at the end of the script, right before the last end that closes the dobet function and now it doesn't even resets the stats like it used to... it just keeps going like the code it's not even there. This is my whole script exactly as I use it in the bot (the only things I added to it are the two IFs at the very end): basebet = 0.000001000
nextbet = basebet
roundprofit = 0
chance = 50
minbal=balance-0.0300000
maxbal=balance+0.01500000
function dobet()
roundprofit += currentprofit
if (win) then
if (roundprofit < 0) then
nextbet = previousbet + basebet
print ("WIN")
print(nextbet)
else
nextbet = basebet
print ("WIN")
print(nextbet)
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
if roundprofit > 0 then roundprofit = 0 end
end
if (!win) then
nextbet = previousbet
print ("LOSE")
print(nextbet)
end
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
end
if profit <= -0.0001000 then
nextbet=basebet
resetstats()
end
if profit >= 0.001 then
withdraw(profit,'BTC ADDRESS')
nextbet=basebet
resetstats()
end
end Try this. I think there were to many end statements. I formatted it a little better to match up if's and ends. I don't have the bot available on my new computer, otherwise I would have tested it out. basebet = 0.000001000
nextbet = basebet
roundprofit = 0
chance = 50
minbal=balance-0.0300000
maxbal=balance+0.01500000
function dobet()
roundprofit += currentprofit
if (win) then
if (roundprofit < 0) then
nextbet = previousbet + basebet
print ("WIN")
print(nextbet)
else
nextbet = basebet
print ("WIN")
print(nextbet)
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
if roundprofit > 0 then roundprofit = 0 end
end
if (!win) then
nextbet = previousbet
print ("LOSE")
print(nextbet)
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
if profit <= -0.0001000 then
nextbet=basebet
resetstats()
end
if profit >= 0.001 then
withdraw(profit,'BTC ADDRESS')
nextbet=basebet
resetstats()
end
end |
|
|
|
Shout out to all bagholders!
I currently have one peer connection 24.67.160.232:49787
Please run your wallets for a day or so, we need to secure our network, and get a new peer list for your wallet.
I run all of the time. I've got 2 connections. 72.190.133.196 and the one you have above. |
|
|
|
Update, still not working. I tried this if profit <= -0.000500 then
nextbet=basebet
resetstats();
resetseed();
end It resets the stats but it keeps going with the same bet, the nextbet doesn't return to basebet. (I have basebet variable determined) Please help me out, thanks! can you post your whole script and explain what your'e trying to do? Thanks for replying! This is the whole script - Pluscoup by chilly2k and grendel25 (I got it from your website). basebet = 0.00001000
nextbet = basebet
roundprofit = 0
chance = 49.5
minbal=balance-0.0300000
maxbal=balance+0.01500000
function dobet()
roundprofit += currentprofit
if (win) then
if (roundprofit < 0) then
nextbet = previousbet + basebet
print ("WIN")
print(nextbet)
else
nextbet = basebet
print ("WIN")
print(nextbet)
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
if roundprofit > 0 then roundprofit = 0 end
end
if (!win) then
nextbet = previousbet
print ("LOSE")
print(nextbet)
end
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
end
end What I am trying to do is this: when the profit (not whole account profit, just the session before resetstats) goes lower than 0.0005 for example, at fist I wanted the bot to stop and then restart but you told me it's not possible, so now I want it to reset the bet to basebet and also resetstats. I tried with this: if profit <= -0.0005 then
nextbet=basebet
resetstats();
end ... and it's not workin, it resets the stats but the bet doesn't go to basebet, it stays where it was. Thanks for your time and I hope we figure it out! Your not saying/showing where you put that code. If you put it just before the last end statement, I think it should work. If you were trying it at the top, nextbet would get reset further in the code. Just for educational purposes, the last end statement close the dobet() function. |
|
|
|
im a newb, how can i start script?
i just past the code, and now? how i start the bets?
just type start() in the console and hit enter. stop() stops the script. |
|
|
|
|
Just throwing out a few ideas.
a) Any thoughts to a facebook tip bot? It seems like you have most of the tech sites covered, but something more main stream, could really do wonders getting us out to the masses. Can you imagine if each person tipped a couple thousand verge to each of their friends. They would all want to see what it is they got. It could go viral...
b) Any way to make the install include I2P or Tor automatically, and have it configured, so non technical people can click once and have a verge wallet with I2P or Tor? I'm pretty tech savvy, but I'll admit I'm not using either I2P or Tor. I installed I2P once, got it working, but never used it again. I'm not sure but I think it was interfering with other things I had running.
Along these lines, if you can easily automatically install I2P or Tor, eliminate the clear net option. This way VERGE is anonymous, not just if you configure it correctly...
c) Does coin2pay keep a vendor list somewhere. In theory all of their vendors accept verge, would be nice if you could point the website to that list.
Love the coin, the idea and all of the work that has gone into this. Now we need to move it from the exchanges into the real world.
|
|
|
|
Can you post your script? and at which site are you betting at? This doesn't look like a programmer mode problem, but the bot doesn't use XML anywhere either, so I'm not sure what's causing your problem.
as for the other questions:
bot does it on its own after 30 seconds then again every 2 minutes if the bot can get a connection again
where possible, the bot already tries to reconnect. bitdice, betking and fortunejack should be the only ones that doesn't reconnect automatically
the bot already does that
i'm testing elmobet66 strategy -- Set Win Chance
chance= 66.0
-- Set BaseBet
base=0.00000005
nextbet = base
initbalance=balance
first = true
second = false
secondwin = false
third = false
betcount = 100
resetstats();
-- Before you START, check your Stop Conditions and ZigZag Settings in the Advance Mode
-- Set Stop Conditions and Zigzag Settings Enabled = true Disabled=false
enablezz = false
enablesrc = false
-- set profit target here
profittarget= 999.00100000
function dobet()
if betcount == 100 then
betcount=0
resetseed();
else
betcount=betcount+1
end
if (balance) >= profittarget then
stop();
print(balance)
print("TARGET ACHIEVED!!!")
print("You Won")
print(profit)
print("for this Session")
end
done = false
--Randomizer
r=math.random(2)
if r == 1 then
bethigh=true
else
bethigh=false
end
if win then
if(first) then
nextbet = base
end
if(second) then
secondwin = true
second = false
third = true
done = true
end
if(third and !done) then
if (secondwin) then
nextbet = base
else
nextbet = previousbet * 7
end
third = false
first = true
end
else
if(first and !done) then
first = false
second = true
done = true
end
if(second and !done) then
secondwin = false
second = false
third = true
done = true
end
if(third and !done) then
third = false
first = true
print("GOING 4 THE WIN!!!")
if (secondwin) then
nextbet = previousbet * 7
else
nextbet = previousbet * 12
end
done = true
end
end
if (initbalance)/2 < (nextbet) then
stop();
print(balance)
print("Emergency Stop")
print("Large Bet Amount Occurred!")
end
end
yes seuntjie, it's really great, but if it can be set lower that 2 mins it will be greater if not, it's ok, because it's my personal problem, vps i rent always disconnected, thank you very much For the error posted above try changing if (initbalance)/2 < (nextbet) then to if ((initbalance)/2 < (nextbet)) then The parens might be messing with the parser. Just my wild ass guess... |
|
|
|
chance=90
multi=10
minbet=0.0000001
minhigh=0.0001
losecount = -2 -- change this to -3 or whatever you want for the lose streak.
nextbet=minbet
rawr=minhigh
highbet=false
fl=false
function dobet()
chance = 90 -- set default chance
if win then fl=true end
if highbet and !win then
rawr=rawr*multi
highbet=false
fl=false
end
if highbet and win then
rawr=minhigh
highbet=false
fl=false
end
nextbet=minbet
if !win and fl and (currentstreak == losecount) then <--- This is the block of code that is going to make the high bet
nextbet=rawr
highbet=true
fl=false
chance = whatever you want to set it to...
end
end
could you help me to add change chance? like prerolling on chance 90% after currentstreak==losecount it will change the chance and put bet, repeat if loss
exp for 2 streaks loss
win,win,loss,win,win,loss,loss,BET (change chance)
thanks
I tried running that code, and it was doing the high bet after 2 losses in a row. Anyway.. I've put an update in red above. |
|
|
|
it gave me first 2 lost, not the streaks..
if i set lostcount = -2 it just starting script after 2 lost...what i mean is preroll for 2 lossstreak then start the script/ strategy
like lose,lose then start, repeat if lose
thanks
I'm not understanding. What is the difference between starting the script after 2 losses and pre-rolling for a 2 loss steak and then starting? after reading your comment for the 10th time I think it sunk in. Your saying the betting starts after 2 losses, not necessarily in a row. Based on the code I gave you it shouldn't start until you have 2 losses in a row. The variable currentstreak is for streaks. If you lose it gets set to -1 if you then win it will be 1 if you lose again it's -1. It won't be -2 until you have 2 losses in a row. I didn't write the original script so sometimes it's hard to understand what someone else was trying to do. It looks like the script needs to have one win, and then a loss to start betting. Then after a loss it increases the bet and waits for another loss before betting higher. I copied the code in the last code segment and it seems to do what your asking for. Keep betting the min bet until you get a 2 loss streak and then do the high bet. |
|
|
|
so anyone could help me with my betting sequence?
is that possible to make it?
This seems to work. Change the top 4 variables as you like Let me know if there are any issues & how your system works out for you chance=90
multi=10
minbet=0.0000001
minhigh=0.0001
nextbet=minbet
rawr=minhigh
highbet=false
fl=false
function dobet()
if win then fl=true end
if highbet and !win then
rawr=rawr*multi
highbet=false
fl=false
end
if highbet and win then
rawr=minhigh
highbet=false
fl=false
end
nextbet=minbet
if !win and fl then
nextbet=rawr
highbet=true
fl=false
end
end anyone can help me with this script? instead of after 1 loss pre roll, i need i want it 2 or 3 loss streaks before placing bet...so it can adjusted thanks There is a variable provided called currentstreak. The trick to using it for loses, is realizing it's a negative number for loses. So you could change the code like this. chance=90
multi=10
minbet=0.0000001
minhigh=0.0001
losecount = -2 -- change this to -3 or whatever you want for the lose streak.
nextbet=minbet
rawr=minhigh
highbet=false
fl=false
function dobet()
if win then fl=true end
if highbet and !win then
rawr=rawr*multi
highbet=false
fl=false
end
if highbet and win then
rawr=minhigh
highbet=false
fl=false
end
nextbet=minbet
if !win and fl and (currentstreak == losecount) then
nextbet=rawr
highbet=true
fl=false
end
end |
|
|
|
banano no fud, just fooled by dev trying to downplay innovations, so it is hard to believe that they have developed a mini computer with built in CryptOS banano will dip a toe in at these levels, because no other coin but IOTA has developed a coin simply because the hardware being developed requires it. It seems that WBB and IOTA put egg before chicken. maybe that's what dev meant when he said no innovation, or maybe he just is being modest by acknowledging that he is just standing on shoulders of giants WBB to the moon! oops, and sorry to brake forum rules to not mention other coins (did not read that far at first)  I really don't get, what you try to achieve! Btw, no rules about not mentioning other coins, just a suggestion. Here were too much talking and comparing with ETH, LISK, etc. Chilly says Banano correct. Sorry I couldn't resist. If you read the OP way down the page it has ---------- What special technical spec will this coin have? Well, it will be an honest straight forward mining coin in scrypt algo made for mining. The coin is as it is, simple and honest starting with block #1 at launch. --------- This was probably there from day one and never updated. Banano, Don't make your entire investment decision based on the OP. 98% are just empty promises. Make it a point to read the last 20 or so pages to see where the coin currently stands. |
|
|
|
Hi! Thanks a lot for help. 1) Yes, the multiplier is suppose to be the chance. I thought those two commands can be used interchangeably. 2) On lose nothing changes. I just keep betting the same amount on the same side until it runs dry (which I prefer to avoid, that's the part when LUCK comes in  ). 3) I made two slightly changes to code: chance = 1.98 nextbet = 0.00000004 bethigh = false wincount = 0 function dobet() if win then wincount +=1 if (wincount==2) then nextbet = previousbet + 0.00000002 bethigh=!bethigh wincount=0 end end if balance > 0.02 then stop() end end I figured out, that resetting wincount on lose would only make bet increase and side switch when two wins IN A ROW happens and that's not my idea. I also change 'balance = 0.02' to 'balance > 0.02', because it returned error 'then expected got =' and because it's rather unlikely that it will be exactly 0.02, so it wouldn't stop after reaching it. Anyway, it works great now and I'm really grateful for help! Still, I'm newbie to dicebot programmer mode and any suggestions will be very appreciated. Thanks again!  Ah one of the joys of programming. You're better off checking for > Greater then .02 then it it Equals .02. If your win made your balance go from .01999999 to .02000001 it would never equal .02 and the bot would run forever. But if you truly only wanted to stop when it was .02, you need to have == to compare 2 numbers. = is used to assign a value. |
|
|
|
I wish i could offer some sound advice but I am curious what you ended up sorting up regarding your inquiry.
-mobile
Would you please be so kind and help me instead? I want to make a function in dicebot that goes under these conditions: 1) basebet = 4 satoshi, multiplier = 50x, betting low at the start (<1.98) 2) every TWO wins (so if total wins amount is even) betamount = previous betamount + 2 satoshi, betting switches to other side (low/high) 3) if balance reaches 0.02 btc, it stops betting. I made sth like that: multiplier=50 <---- Should this be chance? nextbet = 0.00000004 bethigh=false wincount = 0 <------ Counter for the wins. function dobet() if win then wincount += 1 -- Bump the wincount(er) if (wincount == 2) then nextbet = previousbet + 0.00000002 <---- Use the previousbet instead of nextbet bethigh = !bethigh <---- This just switches bethigh end else -- lose wincount = 0 end if balance = 0.02 then stop() end end but it obviously has many errors and I can't seem to make it right. Any help would be really appreciated! See the changes I made above. Note: should the multiplier actually be the chance? And what are you doing if you lose? |
|
|
|
HI, OK it is time to put you all out of your misery on guessing As you all know we are working on something over the last few month which will make WBB something special. We are working on to remove all overheads of the client system and in the same time simplify the usage and speed everything up. In the same time we try to ensure fraud on the blockchain and bloat is removed to ensure in the long term WBB does not slow down but gets better over time. What we also looked at is how businesses really can benefit from crypto (apart from accepting some crypto coin as payment only). Also we looked at how can bigger businesses save money by using WBB and it's setup / infrastructure. The other part is the pain of loading / downloading the blockchain. To download a blockchain and sync a wallet takes time and is always a pain to say the least, also if your data gets corrupt (which can happen) you would to download again and start sync from scratch. This is totally unacceptable to businesses and also not reliable. For this reason let me show you what WBB will become and where we go with it all. WBBOS and WBB is undergoing a transformation to say the least. It is a long way but we are getting closer ever day to our goal. At the moment we run cluster tests on a test genesis-block of WBB and V5. This progress takes time and is complex to say the least but we are not far of it. Once this work is completed we will fork WBB in to the new way and open the path for business all kinds to utilize WBB in a proper manner. WBB with this change is open for Data storage companies, Music industry, Banks, Security companies and many more business sectors. The usability is endless the way in can be used after this change. Due this new way the speed of WBB is increasing and the WBB Wallet will become a Blockchain free wallet which does not need to download the blockchain and thus will be in sync within seconds from a fresh install. Every WBB client is still private and there is no need to login to a web or have some password and so on to access the Blockchain. The WBB Wallet you use like you used before for sending and receiving. New of course is the asset insertion (like mention on some businesses above). Of course with insertion there is/are fee's per KB in WBB apart from a basic network fee for sending payment. Network fee will stay the same for sending payments. When we go live with this then we start meeting a few people here in swiss and introduce WBB to them. Groundwork's are done but now we need to wait till we have our work done before we see anyone of them. Enough talk, here is the graphical how the wallet / blockchain part will work when we release V5. We tried to simplify the image so everyone can get some understanding how it would work as the exact handling would be to complex to show.  We will provide you from now on with updates how all runs and where all is going. This is are exiting times as we could be away maybe another 2-3 weeks to run the first BETA version of V5 with clients. We can not rush this part as it needs to be done step by step. There are still things which go wrong but we aim to fix each of them one by one. Hopefully you like this and have a better understanding where we aim with WBB / WBBOS ecosystem. Thanks Peter Peter, Great work. As usual. This almost sounds like the Electrum client/server model. With super nodes added to the server side. Could you explain what the BGC acronym stands for? RDT would be the redundant database tabulator ... That might help a little. Also can you explain where/who will be in control of the BGC/RDT's? I was imagining a user able to start the client in full function mode. It would connect with the network and be assigned a task as either a BCG or RDT based on it's performance. That's just my own pie in the sky idea based on your update. Congrats again. Can't wait to hear more... |
|
|
|
Might I ask which 'Spots' project is a even semi-success story?
From what I understand he did well on several. ~BCX~ I'm sure he did well on all of them. Doing well and being a scammer are not the same thing. ~BCX~ True, And him doing well and the coin being a success are not the same either. |
|
|
|
Might I ask which 'Spots' project is a even semi-success story?
From what I understand he did well on several. ~BCX~ I'm sure he did well on all of them. |
|
|
|
I'm getting this error on my script...can't figure out where the problem is? [string "chunk"]:32: attempt to compare number with nil Here's the script: basebet = balance/500
nextbet = basebet
roundprofit = 0
chance = 87.79
maxbal=balance+0.01500000
ProtectedProfit = .0003
reset = false
firstgame = true
function dobet()
roundprofit += currentprofit
if (win) then
if(profit > (ProtectedProfit*1.2)) then
ProtectedProfit = ProtectedProfit*1.2
end
if(profit <= (ProtectedProfit/4)) then
ProtectedProfit = ProtectedProfit/2
if(ProtectedProfit < .000150) then
ProtectedProfit = .000150
end
end
if (roundprofit < 0) and (!reset) then
nextbet = previousbet + basebet
print ("WIN")
print(nextbet)
end
else
nextbet = basebet
print ("WIN")
print(nextbet)
reset = false
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
if roundprofit > 0 then
roundprofit = 0
end
if (!win) then
nextbet = previousbet
print ("LOSE")
print(nextbet)
end
if balance<minbal then
stop()
end
if balance>maxbal then
stop()
end
if(!firstgame) then
if(nextbet >= ProtectedProfit) and (profit > ProtectedProfit) then
nextbet = basebet
reset = true
end
end
firstgame = false
end I believe you forgot to define minbal. Also from the error message "[string "chunk"]:32: attempt to compare number with nil" The 32 looks to be the 32nd non=blank line in the script. I just noticed this, so that may or may not be the correct way to get to the failing line. |
|
|
|
at least it is obvious, first the coin was hyped with anon-features to a certain price level, then algo was improved to make the coin more profitable for mining.
Miners take profits and causing the sell pressure now.
It is all a bit shady, especially when you ask yourself who profits from the recent tech updates. But I blame nobody.
If this coin has a future? Time will tell after several rounds of halving.
Until then I have no significant hope for an upward price movement.
(sorry when I appear to be a troll but I am not, just a bit disentchanted)
Coins been around over 2 years, with anon features. It was rebranded from DOGED to VERGE. People got excited, and some people thought they were going to get rich. Obviously you haven't read much about the coins or the new multi-algo. It was done to solve a problem. The user is ultimately the one that profits since now the block chain is moving on a timely schedule. As for the halving and price decline etc... That's all a good thing. When the price goes up, switch pools jump on the coin while the difficulty is low. They then dump the coin at the best price, and convert to BTC. They don't care which coin they mine as long as it's the most profitable. The halving should help in this aspect too. Now we need to get this coin circulating. |
|
|
|
|
Show Posts
