bur4n
Member
 Offline
Activity: 167
Merit: 12
|
 |
November 30, 2018, 12:33:04 PM |
|
I love this bot, thank you! 🍷🍷🍷 |
|
|
|
|
|
|
|
The block chain is the main innovation of Bitcoin. It is the
first distributed timestamping system.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
mydicebot (OP)
|
|
December 01, 2018, 11:53:05 AM |
|
I love this bot, thank you! 🍷🍷🍷 Thanks for supporting. |
|
|
|
|
mydicebot (OP)
|
|
December 03, 2018, 07:39:53 AM |
|
|
|
|
|
DogecoinMachine
Legendary
Offline
Activity: 2871
Merit: 1131
www.Crypto.Games: Multiple Games, Multiple Coins
|
|
December 03, 2018, 12:59:14 PM |
|
Thank you, I know many will like your bot  |
|
|
|
|
mydicebot (OP)
|
|
December 04, 2018, 08:37:54 AM |
|
Thank you, I know many will like your bot Thanks a lot for your supporting. |
|
|
|
|
shield132
|
|
December 04, 2018, 11:40:08 AM |
|
OP don't get it wrong but almost in one month you released v6 version of your bot. I think it would be better if you released a little bit complete version from the begining. On another hand you know people like UI of your bot, it's really nice.
Well, I would prefer a little bit long wait and stable version over weekly releases, you know your job... Wish you success.
|
|
|
|
|
mydicebot (OP)
|
|
December 04, 2018, 12:04:36 PM |
|
OP don't get it wrong but almost in one month you released v6 version of your bot. I think it would be better if you released a little bit complete version from the begining. On another hand you know people like UI of your bot, it's really nice.
Well, I would prefer a little bit long wait and stable version over weekly releases, you know your job... Wish you success.
Thanks a lot for your feedback, 1st version was released 6 weeks ago, so we regularly release one major version per week. Each version is stable and fully tested, and all functions are complete. Major version updating right now is standing for new site integrated, so it has 6 sites been integrated. |
|
|
|
|
|
|
mydicebot (OP)
|
|
December 07, 2018, 01:59:59 AM |
|
Android version of MyDiceBot is under development. * packing into apk is done * install on Android phone is done * launch on Android phone is done * running on Android phone is done TODO * UI adjustment to phone/tablet  |
|
|
|
|
mydicebot (OP)
|
|
December 09, 2018, 06:19:57 AM |
|
|
|
|
|
docthusinh
Jr. Member
Offline
Activity: 225
Merit: 4
|
|
December 11, 2018, 05:46:29 AM |
|
What i see is features which are not as much as needed for gamblers. The casinos like it since it is a gateway to their profits, faster! What I can suggest is focus on strategies, algorithms that works! For the bot these are important and needed to be improved: 1) how many bets per second it can handle, 2) how is it stability for long running session 24/7 for few weeks, will it crash due to memory leak? and the most important thing is algo/math that can win. sorry to let it down but in fact my 2 cents.
|
|
|
|
|
|
mydicebot (OP)
|
|
December 11, 2018, 10:24:16 AM |
|
What i see is features which are not as much as needed for gamblers. The casinos like it since it is a gateway to their profits, faster! What I can suggest is focus on strategies, algorithms that works! For the bot these are important and needed to be improved: 1) how many bets per second it can handle, 2) how is it stability for long running session 24/7 for few weeks, will it crash due to memory leak? and the most important thing is algo/math that can win. sorry to let it down but in fact my 2 cents.
Thanks a lot for your valuable feedback. * bet speed is just depend on dice sites' limitation but not our software (eg. small mount bet will be limited slower on some sites) * strategy/algorithm list is under development, after that, users can select and edit them in software directly * strategy/algorithm themselves, we assume users are smarter than us and we encourage users to share their own best strategies to the community. |
|
|
|
|
mydicebot (OP)
|
|
December 11, 2018, 10:26:08 AM |
|
strategy for primedice official promotion target = 55.55
chance = 98
basebet = 0.000001
bethigh = true
function dobet()
if currentroll == target then
stop()
else
nextbet = basebet
end
end
Script to hunt the current promotion: https://forum.primedice.com/topic/34689-%F0%9F%8F%86-008-btc-masters-of-numbersbingo-challenge/Just put your target rollnumber into "target = xx.xx" Of course choose the currency you want to use for this challenge and change the bet amount according to the currency under "basebet = x" |
|
|
|
markk1
Member
Offline
Activity: 315
Merit: 11
|
|
December 12, 2018, 10:46:25 AM |
|
Hello! Thanks for your DiceBot! Can U please add for me in script one line for auto repeat after stop - if (currentstreak <= -10) then...
Thanks!
chance = 95
basebet = 0.00000100
bethigh = true
lossstreakcount = 0 -- sample: user-defined lossstreakcount.
nextbet = basebet
-- do bet and let's rock
function dobet()
-- some sites limit bet latency due to the low bet amount.
-- enable it and avoid to be banned, just in case.
-- eg. 2 means sleeping 2 seconds
-- sleep(2)
-- adjust the stopping condition of session profit.
if profit >= 0.00001000 then
stop()
end
-- adjust the stopping condition of wins.
if wins >= 1000 then
stop()
end
-- adjust the stopping condition of bets.
if (bets >= 5000) then
stop()
end
-- adjust the stopping condition of loss streak.
-- eg. -10 means 10 loss streak
if (currentstreak <= -10) then
stop()
end
-- if win, reset bet to base amount.
if (win) then
chance = 95
nextbet = basebet
lossstreakcount = 0
end
-- if loss,
-- first loss goes from 95% to 67%,
-- then 57% and then gradually lower and closer to 49.5%.
if (!win) then
lossstreakcount += 1
if (lossstreakcount > 1) then
nextbet = previousbet*2
chance = (1/(((nextbet+(nextbet-basebet))/nextbet)))*100
if chance < 49.5 then chance = 49.5 end
bethigh = !bethigh
print ("LOSE")
print(nextbet)
print(chance)
print(profit)
print(bets)
else
nextbet = previousbet*2
chance = (1/(((basebet+nextbet))/nextbet))*100
if chance < 49.5 then chance = 49.5 end
bethigh = !bethigh
print ("LOSE")
print(nextbet)
print(chance)
print(profit)
print(bets)
end
end
end
|
|
|
|
mOgliE
Legendary
Offline
Activity: 1344
Merit: 1251
|
|
December 12, 2018, 10:48:21 AM |
|
That's a really cool bot you've designed!
Cause most dice sites have autobot integrated but with limited possibilities.
Now we can code the best autobet program in order to... Lose in the end cause nothing can beat the house :p
But at least we'll be able to do it freely and with style while believing we have a chance this time!
|
|
|
|
docthusinh
Jr. Member
Offline
Activity: 225
Merit: 4
|
|
December 12, 2018, 11:38:57 AM |
|
What i see is features which are not as much as needed for gamblers. The casinos like it since it is a gateway to their profits, faster! What I can suggest is focus on strategies, algorithms that works! For the bot these are important and needed to be improved: 1) how many bets per second it can handle, 2) how is it stability for long running session 24/7 for few weeks, will it crash due to memory leak? and the most important thing is algo/math that can win. sorry to let it down but in fact my 2 cents.
Thanks a lot for your valuable feedback. * bet speed is just depend on dice sites' limitation but not our software (eg. small mount bet will be limited slower on some sites) * strategy/algorithm list is under development, after that, users can select and edit them in software directly * strategy/algorithm themselves, we assume users are smarter than us and we encourage users to share their own best strategies to the community. Then there is no benchmark for speed against some specific sites. For your reference: I've screen some from youtube Using Firefox or Google Chrome & javascript can do upto 10-12 bets/sec. Dice sites may impose max requests per second limitation however it should be some benchmark to see if any overhead within the program code itself. And the most important is the stability, risk of crash during long betting session, what if I am using it and the bot crash in the middle of long losing streak happening while I am sleeping? The software contribute itself much much into overhead not only the dice sites, loop/array and javascript memory hook issue itself. For your reference again: with that speed and Google Chrome need to be restarted every 24hours or max 72hours of running nonstop. Did you ever tested this long? i.e: 1 or 2 weeks running 24/24 / total number of bets around 10 to 20 millions within a session. Why I am saying all this? You are not develop the bot for really free (aka: there is donation address ), and to get decent donation that can repay your effort, I am guessing too much, the bot need to be proven. Say an average Joe like me if interested, may be no donation or a very small amount like 1000-10000 satoshi. How many of these? Not much, and to be honest pay effort with no expectation of returns..is not a human being lol. Some suggestion: - Test and prove the performance like I've stated above. - Just limit all the mobiles/ cross platform, blah blah, they are useless, and only take your effort for nothing in return. The more glossy/ good looking program, the more bug and the more memory leak/hook introduced. - Implementing something like market place/ private betting script. You can earn/ get reward / get referal from working one. And certainly they are private/ unable to decode. This may be against most of the users idea here/ selling something. But it is a direction, why they would choose yours over other bots while one of them is long lived and *trusted/used much* at some degree. |
|
|
|
|
|
mydicebot (OP)
|
|
December 12, 2018, 12:10:08 PM |
|
Hello! Thanks for your DiceBot! Can U please add for me in script one line for auto repeat after stop - if (currentstreak <= -10) then...
Thanks!
chance = 95
basebet = 0.00000100
bethigh = true
lossstreakcount = 0 -- sample: user-defined lossstreakcount.
nextbet = basebet
-- do bet and let's rock
function dobet()
-- some sites limit bet latency due to the low bet amount.
-- enable it and avoid to be banned, just in case.
-- eg. 2 means sleeping 2 seconds
-- sleep(2)
-- adjust the stopping condition of session profit.
if profit >= 0.00001000 then
stop()
end
-- adjust the stopping condition of wins.
if wins >= 1000 then
stop()
end
-- adjust the stopping condition of bets.
if (bets >= 5000) then
stop()
end
-- adjust the stopping condition of loss streak.
-- eg. -10 means 10 loss streak
if (currentstreak <= -10) then
stop()
end
-- if win, reset bet to base amount.
if (win) then
chance = 95
nextbet = basebet
lossstreakcount = 0
end
-- if loss,
-- first loss goes from 95% to 67%,
-- then 57% and then gradually lower and closer to 49.5%.
if (!win) then
lossstreakcount += 1
if (lossstreakcount > 1) then
nextbet = previousbet*2
chance = (1/(((nextbet+(nextbet-basebet))/nextbet)))*100
if chance < 49.5 then chance = 49.5 end
bethigh = !bethigh
print ("LOSE")
print(nextbet)
print(chance)
print(profit)
print(bets)
else
nextbet = previousbet*2
chance = (1/(((basebet+nextbet))/nextbet))*100
if chance < 49.5 then chance = 49.5 end
bethigh = !bethigh
print ("LOSE")
print(nextbet)
print(chance)
print(profit)
print(bets)
end
end
end
Hi, do you mean 'auto restart from the beginning' after the stop() condition triggered? |
|
|
|
|
mydicebot (OP)
|
|
December 12, 2018, 12:11:07 PM |
|
That's a really cool bot you've designed!
Cause most dice sites have autobot integrated but with limited possibilities.
Now we can code the best autobet program in order to... Lose in the end cause nothing can beat the house :p
But at least we'll be able to do it freely and with style while believing we have a chance this time!
Good luck and cheers, buddy. |
|
|
|
|
mydicebot (OP)
|
|
December 12, 2018, 12:30:26 PM |
|
What i see is features which are not as much as needed for gamblers. The casinos like it since it is a gateway to their profits, faster! What I can suggest is focus on strategies, algorithms that works! For the bot these are important and needed to be improved: 1) how many bets per second it can handle, 2) how is it stability for long running session 24/7 for few weeks, will it crash due to memory leak? and the most important thing is algo/math that can win. sorry to let it down but in fact my 2 cents.
Thanks a lot for your valuable feedback. * bet speed is just depend on dice sites' limitation but not our software (eg. small mount bet will be limited slower on some sites) * strategy/algorithm list is under development, after that, users can select and edit them in software directly * strategy/algorithm themselves, we assume users are smarter than us and we encourage users to share their own best strategies to the community. Then there is no benchmark for speed against some specific sites. For your reference: I've screen some from youtube Using Firefox or Google Chrome & javascript can do upto 10-12 bets/sec. Dice sites may impose max requests per second limitation however it should be some benchmark to see if any overhead within the program code itself. And the most important is the stability, risk of crash during long betting session, what if I am using it and the bot crash in the middle of long losing streak happening while I am sleeping? The software contribute itself much much into overhead not only the dice sites, loop/array and javascript memory hook issue itself. For your reference again: with that speed and Google Chrome need to be restarted every 24hours or max 72hours of running nonstop. Did you ever tested this long? i.e: 1 or 2 weeks running 24/24 / total number of bets around 10 to 20 millions within a session. Why I am saying all this? You are not develop the bot for really free (aka: there is donation address ), and to get decent donation that can repay your effort, I am guessing too much, the bot need to be proven. Say an average Joe like me if interested, may be no donation or a very small amount like 1000-10000 satoshi. How many of these? Not much, and to be honest pay effort with no expectation of returns..is not a human being lol. Some suggestion: - Test and prove the performance like I've stated above. - Just limit all the mobiles/ cross platform, blah blah, they are useless, and only take your effort for nothing in return. The more glossy/ good looking program, the more bug and the more memory leak/hook introduced. - Implementing something like market place/ private betting script. You can earn/ get reward / get referal from working one. And certainly they are private/ unable to decode. This may be against most of the users idea here/ selling something. But it is a direction, why they would choose yours over other bots while one of them is long lived and *trusted/used much* at some degree. Some suggestion: - Test and prove the performance like I've stated above. mydicebot:
good suggestion.- Just limit all the mobiles/ cross platform, blah blah, they are useless, and only take your effort for nothing in return. The more glossy/ good looking program, the more bug and the more memory leak/hook introduced. mydicebot:
reserve our opinion, as many users requested this cross-platform feature, it's not a requirement imagination by ourselves.- Implementing something like market place/ private betting script. You can earn/ get reward / get referal from working one. And certainly they are private/ unable to decode. This may be against most of the users idea here/ selling something. But it is a direction, why they would choose yours over other bots while one of them is long lived and *trusted/used much* at some degree. mydicebot:
* market place is on our plan list. some tricky parts we are still trying hard to figure out.
* private script is not on our plan list, at least at this moment.
* other bots are our brothers but not competitors, we are open to all of them. We respect all of them. |
|
|
|
markk1
Member
Offline
Activity: 315
Merit: 11
|
|
December 12, 2018, 01:31:36 PM |
|
Hello! Thanks for your DiceBot! Can U please add for me in script one line for auto repeat after stop - if (currentstreak <= -10) then...
Thanks!
chance = 95
basebet = 0.00000100
bethigh = true
lossstreakcount = 0 -- sample: user-defined lossstreakcount.
nextbet = basebet
-- do bet and let's rock
function dobet()
-- some sites limit bet latency due to the low bet amount.
-- enable it and avoid to be banned, just in case.
-- eg. 2 means sleeping 2 seconds
-- sleep(2)
-- adjust the stopping condition of session profit.
if profit >= 0.00001000 then
stop()
end
-- adjust the stopping condition of wins.
if wins >= 1000 then
stop()
end
-- adjust the stopping condition of bets.
if (bets >= 5000) then
stop()
end
-- adjust the stopping condition of loss streak.
-- eg. -10 means 10 loss streak
if (currentstreak <= -10) then
stop()
end
-- if win, reset bet to base amount.
if (win) then
chance = 95
nextbet = basebet
lossstreakcount = 0
end
-- if loss,
-- first loss goes from 95% to 67%,
-- then 57% and then gradually lower and closer to 49.5%.
if (!win) then
lossstreakcount += 1
if (lossstreakcount > 1) then
nextbet = previousbet*2
chance = (1/(((nextbet+(nextbet-basebet))/nextbet)))*100
if chance < 49.5 then chance = 49.5 end
bethigh = !bethigh
print ("LOSE")
print(nextbet)
print(chance)
print(profit)
print(bets)
else
nextbet = previousbet*2
chance = (1/(((basebet+nextbet))/nextbet))*100
if chance < 49.5 then chance = 49.5 end
bethigh = !bethigh
print ("LOSE")
print(nextbet)
print(chance)
print(profit)
print(bets)
end
end
end
Hi, do you mean 'auto restart from the beginning' after the stop() condition triggered? Yes |
|
|
|
|
