I'm unable to login into Primedice, is there any ongoing issue with the website?
same problem here , primedice and stake stopped : "we do not operate this country"m i got this on dicebot, any issue with german vps?
Topic: Seuntjies DiceBot -Multi-Site, multi-strategy betting bot for dice. With Charts! - page 6. (Read 274497 times)
August 31, 2020, 09:57:47 PM
same problem here , primedice and stake stopped : "we do not operate this country"m i got this on dicebot, any issue with german vps?
August 27, 2020, 03:33:02 AM
I'm unable to login into Primedice, is there any ongoing issue with the website?
Where you able to log in before or is it your first try?
August 27, 2020, 02:53:27 AM
I'm unable to login into Primedice, is there any ongoing issue with the website?
August 22, 2020, 05:30:17 PM
Quote
Looking at your code... the only time it will end up as chance=49 is when the lastBet.Roll was <3.3 or > 96.7 AND it was a loss...
The "if !win then... else..." block you have means that if it was a win... it sets nextbet = balance /1024 and then chance is set to 97.2549.
So currently, will only work if it is < 3.3... as you're betting "high" to start by default, if the roll is over 96.7 you'll win and the chance won't change.
I appreciate all the help! I will try to implement that and see how it runs. Much appreciated!
EDIT:
Seems to do exactly what I wanted it to do, but I'm still not rich :/ (that's a joke)
Thanks again for all the help HCP.
August 22, 2020, 04:33:15 PM
Quote
basebet = balance / 1024
nextbet = basebet
chance = 97.2549
function dobet()
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
if !win then
nextbet = previousbet*2
else
nextbet = balance / 1024
chance = 97.2549 <-- This is where it is resetting your chance
end
end
Looking at your code... the only time it will end up as chance=49 is when the lastBet.Roll was <3.3 or > 96.7 AND it was a loss...
The "if !win then... else..." block you have means that if it was a win... it sets nextbet = balance /1024 and then chance is set to 97.2549.
So currently, will only work if it is < 3.3... as you're betting "high" to start by default, if the roll is over 96.7 you'll win and the chance won't change.
Try something like this:
Code:
basebet = balance / 1024
nextbet = basebet
chance = 97.2549
function dobet()
if (!win) then
-- loss, martingale
nextbet = previousbet * 2
else
-- win, reset
bethigh = true
nextbet = balance / 1024
chance = 97.2549
end
if (lastBet.Roll < 3.3) then
bethigh = true
chance = 49.1089
elseif (lastBet.Roll > 96.7) then
bethigh = false
chance = 49.1089
end
print("LastRoll: " .. lastBet.Roll)
print("Chance: " .. chance)
print("bethigh: " .. tostring(bethigh))
end
nextbet = basebet
chance = 97.2549
function dobet()
if (!win) then
-- loss, martingale
nextbet = previousbet * 2
else
-- win, reset
bethigh = true
nextbet = balance / 1024
chance = 97.2549
end
if (lastBet.Roll < 3.3) then
bethigh = true
chance = 49.1089
elseif (lastBet.Roll > 96.7) then
bethigh = false
chance = 49.1089
end
print("LastRoll: " .. lastBet.Roll)
print("Chance: " .. chance)
print("bethigh: " .. tostring(bethigh))
end
All the "ususal disclaimers" apply... I haven't thoroughly tested this, so run at your own risk
Also, based on your pseudocode, I'd suggest you read this: https://steemit.com/dicebot/@seuntjie/dicebot-programmer-mode-tutorial-02-process
It gives you an idea of how the "flow" works... you can't run "innerloops" like the while() statement you have. Essentially, after a bet is placed and result received, dobet() is called...
At this point, you can then process the received result and make changes to your bet amount, high/low, chance etc... then when you get to the end of the dobet() function, a bet with the new parameters is sent to the server and the bot waits for the new result.
Again, once the result is received, dobet() runs again... and the process repeats until the script is stopped (manually, by stop() command in script, or an error is received from server).
Quote from: https://bot.seuntjie.com/ProgrammerMode.aspx
Basic overview of script lifecycle
Here's a small overview of the lifecycle of the script, how and in which order everything is executed
1) bot starup - loads basic functions (withdraw, invest, tip, stop, runsim etc)
2) start() or runstim() is executed. the script in the code box is executed once. Thus functions are registered, variables are created and assigned.
3) place starting bet: the bot places the starting bet: no script executed
4) bet result returned: 4.1) variables (balance, profit, wins, lossess etc) are updated.
4.2) dobet() is executed.
4.3) local variables are updated to new varibable from the bot (chance, nextbet, high)
5) next bet is placed. On bet result, go back to step 4.
Here's a small overview of the lifecycle of the script, how and in which order everything is executed
1) bot starup - loads basic functions (withdraw, invest, tip, stop, runsim etc)
2) start() or runstim() is executed. the script in the code box is executed once. Thus functions are registered, variables are created and assigned.
3) place starting bet: the bot places the starting bet: no script executed
4) bet result returned: 4.1) variables (balance, profit, wins, lossess etc) are updated.
4.2) dobet() is executed.
4.3) local variables are updated to new varibable from the bot (chance, nextbet, high)
5) next bet is placed. On bet result, go back to step 4.
August 22, 2020, 09:23:15 AM
You'll have to show your full script... there is obviously something elsewhere in your script which is overriding your chance setting that is done in the if (< 3 or > 97) block...
There is no way it should have reset to 97% unless there is another code branch setting the chance somwhere.
There is no way it should have reset to 97% unless there is another code branch setting the chance somwhere.
Maybe it would be easier to state my end goals for this. I figured I would try to solve each problem as I try to implement it, but we'll see if this clears things up.
I want to run high on 97.2% chance until it rolls under 3 or over 97. If it rolls under 3, it should change to 49% chance and do a basic martingale until a win, which would reset it. If it rolls over 97 I want it to do the same thing, but switch it to rolling low instead. Here's thejumbled c++/lua logic I could come up with for that but am still trying to implement. i can't seem to figure out how to do branches in the if statement like this in LUA:
Code:
dobet
if lastBet < 3.3
{ chance = 49.5;
while (!win)
{nextbet = previousbet*2;}
}
elseif lastBet > 97.6
{switch low;
chance = 49.5;
while (!win)
{nextbet = previousbet*2;}
}
else
{ nextBet = balance / 512;}
if lastBet < 3.3
{ chance = 49.5;
while (!win)
{nextbet = previousbet*2;}
}
elseif lastBet > 97.6
{switch low;
chance = 49.5;
while (!win)
{nextbet = previousbet*2;}
}
else
{ nextBet = balance / 512;}
August 22, 2020, 08:57:17 AM
You'll have to show your full script... there is obviously something elsewhere in your script which is overriding your chance setting that is done in the if (< 3 or > 97) block...
There is no way it should have reset to 97% unless there is another code branch setting the chance somwhere.
There is no way it should have reset to 97% unless there is another code branch setting the chance somwhere.
Everything else seemed to run fine, other than right there. But here's my full thing:
Code:
basebet = balance / 1024
nextbet = basebet
chance = 97.2549
function dobet()
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
if !win then
nextbet = previousbet*2
else
nextbet = balance / 1024
chance = 97.2549
end
end
I know it's a super complex code, but I just don't see where else it would be going wrong.
August 22, 2020, 05:52:55 AM
You'll have to show your full script... there is obviously something elsewhere in your script which is overriding your chance setting that is done in the if (< 3 or > 97) block...
There is no way it should have reset to 97% unless there is another code branch setting the chance somwhere.
There is no way it should have reset to 97% unless there is another code branch setting the chance somwhere.
August 21, 2020, 10:57:47 PM
Yeah... I'm an idiot... but, in my defense, I've been doing mostly Python programming lately!! 
The correct the syntax for "combining" multiple outputs for a print() statement in LUA is ".." not "," 
Try:
The correct the syntax for "combining" multiple outputs for a print() statement in LUA is ".." not "," Try:
Code:
function dobet()
print("Roll: " .. lastBet.Roll)
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
print("Roll: " .. lastBet.Roll)
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
Lol, i probably could have just looked up how to do a print function, but it all looked good to me so I didn't. Lemme try that one.
So I was fortunate to hit both sides withing a few bets of each other and all within a couple bets of starting. Here's what I got:
Betting 0.00046871885 at 97.2549% chance to win, high
Roll: 0.775
Betting 0.0009374377 at 49.1089% chance to win, high
Roll: 91.807
Betting 0.000469670937109375 at 97.2549% chance to win, high
Betting Stopped!
Roll: 96.689
Betting 0.00046970763046875 at 97.2549% chance to win, high
You can see that on the low end (first roll there), it works fine and the payout changes. But the last shown roll is 96.689 and should have made the next bet go to the 49%, but it didn't
August 21, 2020, 10:54:05 PM
Yeah... I'm an idiot... but, in my defense, I've been doing mostly Python programming lately!! The correct the syntax for "combining" multiple outputs for a print() statement in LUA is ".." not ","
Try:
The correct the syntax for "combining" multiple outputs for a print() statement in LUA is ".." not "," Try:
Code:
function dobet()
print("Roll: " .. lastBet.Roll)
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
print("Roll: " .. lastBet.Roll)
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
Lol, i probably could have just looked up how to do a print function, but it all looked good to me so I didn't. Lemme try that one.
August 21, 2020, 07:22:43 PM
Yeah... I'm an idiot... but, in my defense, I've been doing mostly Python programming lately!! The correct the syntax for "combining" multiple outputs for a print() statement in LUA is ".." not ","
Try:
The correct the syntax for "combining" multiple outputs for a print() statement in LUA is ".." not "," Try:
Code:
function dobet()
print("Roll: " .. lastBet.Roll)
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
print("Roll: " .. lastBet.Roll)
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
August 21, 2020, 06:54:34 PM
Tried that and it wouldn't read the print fuction, even after fixing the "lasbetBet" mis-type
As in, it created a syntax error and the script didn't run or it just didn't print anything out into the console window? 
Also, my bad with the typo!
It created some sort of error. And it's all good on the typo. I just wanted to point out that I fixed it so nobody would comment that that was my problem.
Here's the error:
[string "chunk"]:1: invalid arguments to method call
August 21, 2020, 06:51:47 PM
Tried that and it wouldn't read the print fuction, even after fixing the "lasbetBet" mis-type
As in, it created a syntax error and the script didn't run or it just didn't print anything out into the console window? Also, my bad with the typo!
August 21, 2020, 05:10:38 PM
I don't see anything obviously wrong with the code. 
The only thing I can think of is that the site you're using the bot with is setting the roll value to some bizarre value?
Maybe add a "print" statement in to debug what the value of lastBet.Roll actually is. It should output to the Bot's console window.
The only thing I can think of is that the site you're using the bot with is setting the roll value to some bizarre value?
Maybe add a "print" statement in to debug what the value of lastBet.Roll actually is. It should output to the Bot's console window.
Code:
function dobet()
print("Roll: ", lastBet.Roll)
if (lasbetBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
print("Roll: ", lastBet.Roll)
if (lasbetBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
I'll look into it. Will that print an output different than the bet output that is being shown in the display?
Edit:
Tried that and it wouldn't read the print fuction, even after fixing the "lasbetBet" mis-type
August 21, 2020, 04:57:59 PM
I don't see anything obviously wrong with the code.
The only thing I can think of is that the site you're using the bot with is setting the roll value to some bizarre value?
Maybe add a "print" statement in to debug what the value of lastBet.Roll actually is. It should output to the Bot's console window.
The only thing I can think of is that the site you're using the bot with is setting the roll value to some bizarre value?
Maybe add a "print" statement in to debug what the value of lastBet.Roll actually is. It should output to the Bot's console window.
Code:
function dobet()
print("Roll: ", lastBet.Roll)
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
print("Roll: ", lastBet.Roll)
if (lastBet.Roll < 3.3 or lastBet.Roll > 96.7) then
chance = 49.1089
end
...
August 21, 2020, 04:08:20 PM
I don't know LUA, but I have a bit of c++ experience. I have a problem where I'm trying to get it to switch payouts if lastbet was below a certain number or above another, but it only reads the below portion. Please help.
function dobet()
if lastBet.Roll < 3.3 or lastBet.Roll > 96.7 then
chance = 49.1089
end
I also tried the following and it didn't work either.
function dobet()
if lastBet.Roll < 3.3 then
chance = 49.1089
elseif lastBet.Roll > 96.7 then
chance = 49.1089
end
Again, regardless of which on I try, nothing changes unless a number under 3.3 is rolled.
Code:
function dobet()
if lastBet.Roll < 3.3 or lastBet.Roll > 96.7 then
chance = 49.1089
end
I also tried the following and it didn't work either.
Code:
function dobet()
if lastBet.Roll < 3.3 then
chance = 49.1089
elseif lastBet.Roll > 96.7 then
chance = 49.1089
end
Again, regardless of which on I try, nothing changes unless a number under 3.3 is rolled.
July 17, 2020, 07:52:54 AM
seuntjie is scam who works with casinos, bot sends red signal and your balance gets busted!
if you like truth, visit our telegram:
free partnership!
if you like truth, visit our telegram:
free partnership!
Prove it.
Edit: I'll make it easier for you:
Here's DiceBots source Code: https://github.com/Seuntjie900/DiceBot
Here's a decompiler so that you can look for differences between the published source code and published binaries: https://www.jetbrains.com/decompiler/ (spoilers, there aren't any)
You have all the resources you need to prove that the bot sends a "red signal", now show us where and how it does so.
July 13, 2020, 04:45:35 AM
before that there were similar problems. When the primedice were updated, there were problems with authorization or with changing the seed, the dicebot update came out almost immediately. When there were problems with the bet counter on the bitvest, because of which the bot stopped, the dicebot update immediately came out. With similar problems causing any inconvenience, an update for dicebot has always been released. Now this is just a similar problem, but the new version of the bot has not been released for a long time, so I decided to ask what the reason for the delay was, and whether there would be a dicebot update at all. If this problem cannot be solved, then let the developer respond so that it is clear
I've been very busy. I'll update the bot when I have a chance.
July 10, 2020, 03:56:29 PM
before that there were similar problems. When the primedice were updated, there were problems with authorization or with changing the seed, the dicebot update came out almost immediately. When there were problems with the bet counter on the bitvest, because of which the bot stopped, the dicebot update immediately came out. With similar problems causing any inconvenience, an update for dicebot has always been released. Now this is just a similar problem, but the new version of the bot has not been released for a long time, so I decided to ask what the reason for the delay was, and whether there would be a dicebot update at all. If this problem cannot be solved, then let the developer respond so that it is clear
July 07, 2020, 06:23:03 PM
That could be a problem with the site and not the dicebot.
After their upgrade, it would appear that Bitvest have modified the API and possibly removed the ability to change the seed... there is nothing the Dicebot can do if the site doesn't support the functionality.
Ask Bitvest if their API still supports changing the seed
After their upgrade, it would appear that Bitvest have modified the API and possibly removed the ability to change the seed... there is nothing the Dicebot can do if the site doesn't support the functionality.
Ask Bitvest if their API still supports changing the seed
Jump to: