Seuntjies DiceBot -Multi-Site, multi-strategy betting bot for dice. With Charts! - page 23.

kodark

jr. member

Activity: 32

Merit: 12

Quote from: seuntjie on August 04, 2019, 03:37:12 AM

Quote from: kodark on August 03, 2019, 09:46:31 AM

Quote from: seuntjie on July 30, 2019, 01:50:40 AM

Quote from: kodark on July 29, 2019, 03:44:57 PM

Where to report bugs?

There is a bug that, when the lua scripts stops for not having sufficient funds, if you deposit more and start again, it will go ahead with the next betting with a higher value or, when changing coins and pasting a new whole script with the correct basebet, it will use the previous basebet and so, you can be bankrupt because of this.

OP, it would be good if this bug would be solved because it cleared my balance at least 3 times before I learned it and thats the main reason I am not donating.

The bot isn't stopped unless it says "stopping" with a reason in the status bar. If you run out of funds, the bot retries the bet every 30 seconds. If you deposit, it will resume within 30 seconds of the funds being available in your account.

If you do stop it and then type start again to start betting, and it bets from where you left off, it's a problem with your script. Your script is supposed to set the starting bet when it's parsed.

See the tutorials on https://bot.seuntjie.com/programmermode.aspx

I do it, use function stop(), see an example:

Code:

if balance < stoplosslimit then
nextbet = basebet
ching()
alarm()
stop()

end

My stoplosslimit is working as I tested it many times, but, when the martingale fails, it does not returns to the basebet.

And really, sometimes I stop it manually. The solution is close the bot and open again with a new script setting the basebet.

This sounds like your script doesn't set the same basebet when it's parsed as what you set when it stops.

Is your primedice nick seuntjies ?

seuntjie

legendary

Activity: 1717

Merit: 1125

Quote from: kodark on August 03, 2019, 09:46:31 AM

Quote from: seuntjie on July 30, 2019, 01:50:40 AM

Quote from: kodark on July 29, 2019, 03:44:57 PM

Where to report bugs?

There is a bug that, when the lua scripts stops for not having sufficient funds, if you deposit more and start again, it will go ahead with the next betting with a higher value or, when changing coins and pasting a new whole script with the correct basebet, it will use the previous basebet and so, you can be bankrupt because of this.

OP, it would be good if this bug would be solved because it cleared my balance at least 3 times before I learned it and thats the main reason I am not donating.

The bot isn't stopped unless it says "stopping" with a reason in the status bar. If you run out of funds, the bot retries the bet every 30 seconds. If you deposit, it will resume within 30 seconds of the funds being available in your account.

If you do stop it and then type start again to start betting, and it bets from where you left off, it's a problem with your script. Your script is supposed to set the starting bet when it's parsed.

See the tutorials on https://bot.seuntjie.com/programmermode.aspx

I do it, use function stop(), see an example:

Code:

if balance < stoplosslimit then
nextbet = basebet
ching()
alarm()
stop()

end

My stoplosslimit is working as I tested it many times, but, when the martingale fails, it does not returns to the basebet.

And really, sometimes I stop it manually. The solution is close the bot and open again with a new script setting the basebet.

This sounds like your script doesn't set the same basebet when it's parsed as what you set when it stops.

seuntjie

legendary

Activity: 1717

Merit: 1125

Quote from: kodark on August 03, 2019, 02:39:57 PM

Quote from: seuntjie on August 02, 2019, 09:37:13 AM

Quote from: deisik on August 02, 2019, 09:26:20 AM

Can I compile it for Linux? What framework is it using (Qt would be fine)?

Yes. It's built using .net standard, there's no GUI for it yet. (It has a CLI that is somewhat limited that's built using .net core)

seuntjie, How do I reset the time running in the stats?
resetstats() does not do the trick.

are you using doormat? iirc doormat creates a new stats object when you reset stats and the time running should be contained in there. so the time running should reset in doormat.

If you're not using doormat, why did you quote a post about doormat to ask me that question?

In that case. Update your bot.

kodark

jr. member

Activity: 32

Merit: 12

Quote from: seuntjie on August 02, 2019, 09:37:13 AM

Quote from: deisik on August 02, 2019, 09:26:20 AM

Can I compile it for Linux? What framework is it using (Qt would be fine)?

Yes. It's built using .net standard, there's no GUI for it yet. (It has a CLI that is somewhat limited that's built using .net core)

seuntjie, How do I reset the time running in the stats?
resetstats() does not do the trick.

kodark

jr. member

Activity: 32

Merit: 12

Quote from: deisik on August 02, 2019, 06:01:34 AM

Hi, guys, I have a quick question

What are the casinos with the fastest API in terms of maximum number of bets per second that the Seuntjies DiceBot works with? I want to test the strategy described in this thread (mostly academic interest but still), and in order to build a big enough sample I need more bets per unit of time. If someone has already tried out what I want to test there (and it didn't work out), let me know, still better in that thread directly (so as not to derail this one)

Duckdice is the fastest.

kodark

jr. member

Activity: 32

Merit: 12

Quote from: seuntjie on July 30, 2019, 01:50:40 AM

Quote from: kodark on July 29, 2019, 03:44:57 PM

Where to report bugs?

There is a bug that, when the lua scripts stops for not having sufficient funds, if you deposit more and start again, it will go ahead with the next betting with a higher value or, when changing coins and pasting a new whole script with the correct basebet, it will use the previous basebet and so, you can be bankrupt because of this.

OP, it would be good if this bug would be solved because it cleared my balance at least 3 times before I learned it and thats the main reason I am not donating.

The bot isn't stopped unless it says "stopping" with a reason in the status bar. If you run out of funds, the bot retries the bet every 30 seconds. If you deposit, it will resume within 30 seconds of the funds being available in your account.

If you do stop it and then type start again to start betting, and it bets from where you left off, it's a problem with your script. Your script is supposed to set the starting bet when it's parsed.

See the tutorials on https://bot.seuntjie.com/programmermode.aspx

I do it, use function stop(), see an example:

Code:

if balance < stoplosslimit then
nextbet = basebet
ching()
alarm()
stop()

end

My stoplosslimit is working as I tested it many times, but, when the martingale fails, it does not returns to the basebet.

And really, sometimes I stop it manually. The solution is close the bot and open again with a new script setting the basebet.

seuntjie

legendary

Activity: 1717

Merit: 1125

Quote from: deisik on August 02, 2019, 09:26:20 AM

Can I compile it for Linux? What framework is it using (Qt would be fine)?

Yes. It's built using .net standard, there's no GUI for it yet. (It has a CLI that is somewhat limited that's built using .net core)

deisik

legendary

Activity: 3514

Merit: 1280

English ⬄ Russian Translation Services

Quote from: seuntjie on August 02, 2019, 06:26:10 AM

Quote from: deisik on August 02, 2019, 06:01:34 AM

Hi, guys, I have a quick question

What are the casinos with the fastest API in terms of maximum number of bets per second that the Seuntjies DiceBot works with? I want to test the strategy described in this thread (mostly academic interest but still), and in order to build a big enough sample I need more bets per unit of time. If someone has already tried out what I want to test there (and it didn't work out), let me know, still better in that thread directly (so as not to derail this one)

If it's for academic purposes, use the simulator built into DiceBot

Thanks for replying, I will try it

But I still want to know how real casinos rank up in terms of the metric described (bet speed). I think it will be interesting to find out. As far as remember, PrimeDice, for example, now limits bets to 1 roll per second, even though their autobet was way faster when they had first introduced it in circa 2014 (back in the day I lost like 1.5 BTC with it, huh). Right now, I'm running autobet at wolf.bet, and it is visibly faster than just 1 bet per second (actually pretty close to 2 bets per second)

Quote from: seuntjie on August 02, 2019, 06:26:10 AM

(If you're looking for more performance and are fairly tech savvy, clone and compile doormat: https://github.com/Seuntjie900/Doormat. It's simulator is much much faster)

Can I compile it for Linux? What framework is it using (Qt would be fine)?

seuntjie

legendary

Activity: 1717

Merit: 1125

Quote from: deisik on August 02, 2019, 06:01:34 AM

Hi, guys, I have a quick question

What are the casinos with the fastest API in terms of maximum number of bets per second that the Seuntjies DiceBot works with? I want to test the strategy described in this thread (mostly academic interest but still), and in order to build a big enough sample I need more bets per unit of time. If someone has already tried out what I want to test there (and it didn't work out), let me know, still better in that thread directly (so as not to derail this one)

If it's for academic purposes, use the simulator built into DiceBot.

(If you're looking for more performance and are fairly tech savvy, clone and compile doormat: https://github.com/Seuntjie900/Doormat. It's simulator is much much faster)

deisik

legendary

Activity: 3514

Merit: 1280

English ⬄ Russian Translation Services

Hi, guys, I have a quick question

What are the casinos with the fastest API in terms of maximum number of bets per second that the Seuntjies DiceBot works with? I want to test the strategy described in this thread (mostly academic interest but still), and in order to build a big enough sample I need more bets per unit of time. If someone has already tried out what I want to test there (and it didn't work out), let me know, still better in that thread directly (so as not to derail this one)

HCP

legendary

Activity: 2086

Merit: 4361

Yeah... I suspect you might be confused by the 4.95% == 0.0495...

In this formula, you need to use a "decimal percentage"... This is basically the percentage you are using / 100. All the values should end up between 0 and 1.

So, if you are using a percentage of 1%, the decimal value is (1 / 100) => 0.01

0.495% => 0.495 / 100 => 0.00495
4.95% => 4.95 / 100 => 0.0495
10% => 10 / 100 => 0.1
56.7% => 56.7 / 100 => 0.567
100% => 100 / 100 => 1

Because the start percentage is for "wins" and we're after "losses"... we then use (1-p) to get the loss percentage... so the formula, for 4.95% should look something like:

=abs(ln(4166576)/ln(1-0.0495))

What site are you using that is given you these 1700-1900 loss streaks? Huh

houseworx

full member

Activity: 319

Merit: 100

Quote from: docthusinh on July 28, 2019, 03:42:10 AM

Quote from: HCP on July 26, 2019, 04:46:25 PM

The best explanation including a mathematical formula I have found is this one:

Quote from: https://www.soccerwidow.com/football-gambling/betting-knowledge/value-betting-academy/learning-centre/betting-terminology/science-calculating-winning-losing-streaks/

Winning and Losing Streaks Formula
The longest expected losing streak (or winning streak) can be calculated using the following formula:

n = number of trials (i.e. total number of bets)
ln = natural logarithm¹
P = probability²
| .. | = absolute value or ‘modulus’

¹ - Suffice to say, explaining what natural logarithm is would be worthy of a series of articles. For the time being, use Excel to calculate this for you.

² - For winning streak calculations use the positive value (i.e. the probability of winning). For losing streak calculations use the negative probability value. For example, if the probability to win the bet is 33% then the probability that the bet loses (negative probability) is 67%.

If you want a formula for Excel or Google Sheets it would be:

Code:

=abs(ln(n)/ln(1-p))

"n" = number of rolls
"p" = needs to be expressed as percentage value between 0-1, so (percentage / 100). ie. 60% = 0.60, 5% = 0.05

You can see it in action here: https://docs.google.com/spreadsheets/d/1T7k5KVUwB606rfyrCrfZNTs8xyVyF7C-0PLlIPzaU8o

It seem incorrect
n = 4166576
p = 0.0495
=> 3358.8 (3359)

While my actual result is currently at 1744 after above "n" rolls (ever seen of 2100-2300++ but not 2400++), it might be correct if above result is not "mean" or "average" but it is "rare", "extremely rare" streak.

you cant get never in reality with probably fair dice game with ~1% HE more than ~400 loses in row on 4.95% winning chance. (even on simalator with 100m bets)!
on 0.495% (half of 1%) you can get this 3,3k loses in row till 4k loses in row.

so your manual calcualted results or whatever from where you get it its totally wrong, please show me proof where you get on ~5% winning change more than 350 loses in row at all in your life!

docthusinh

jr. member

Activity: 225

Merit: 4

Quote from: HCP on July 30, 2019, 05:52:58 PM

Quote from: docthusinh on July 28, 2019, 03:42:10 AM

It seem incorrect
n = 4166576
p = 0.0495
=> 3358.8 (3359)

While my actual result is currently at 1744 after above "n" rolls (ever seen of 2100-2300++ but not 2400++), it might be correct if above result is not "mean" or "average" but it is "rare", "extremely rare" streak.

Are those numbers correct? Huh

I just tried putting them into the spreadsheet...

4166576 rolls, chance @ 4.95% (0.0495 == 4.95% chance)... and I get a max expected streak of ~300...

Yeah, your calculation of 300.25 is correct for the formula, however the real stat collected from real betting is as what I've reported 1744 for current month (1700-1900 range collected stats are few times during that "n"), once get 2367 (after around 20m bets long time ago).

HCP

legendary

Activity: 2086

Merit: 4361

Quote from: docthusinh on July 28, 2019, 03:42:10 AM

It seem incorrect
n = 4166576
p = 0.0495
=> 3358.8 (3359)

While my actual result is currently at 1744 after above "n" rolls (ever seen of 2100-2300++ but not 2400++), it might be correct if above result is not "mean" or "average" but it is "rare", "extremely rare" streak.

Are those numbers correct? Huh

I just tried putting them into the spreadsheet...

4166576 rolls, chance @ 4.95% (0.0495 == 4.95% chance)... and I get a max expected streak of ~300...

seuntjie

legendary

Activity: 1717

Merit: 1125

Quote from: kodark on July 29, 2019, 03:44:57 PM

Where to report bugs?

There is a bug that, when the lua scripts stops for not having sufficient funds, if you deposit more and start again, it will go ahead with the next betting with a higher value or, when changing coins and pasting a new whole script with the correct basebet, it will use the previous basebet and so, you can be bankrupt because of this.

OP, it would be good if this bug would be solved because it cleared my balance at least 3 times before I learned it and thats the main reason I am not donating.

The bot isn't stopped unless it says "stopping" with a reason in the status bar. If you run out of funds, the bot retries the bet every 30 seconds. If you deposit, it will resume within 30 seconds of the funds being available in your account.

If you do stop it and then type start again to start betting, and it bets from where you left off, it's a problem with your script. Your script is supposed to set the starting bet when it's parsed.

See the tutorials on https://bot.seuntjie.com/programmermode.aspx

janggernaut

legendary

Activity: 2366

Merit: 1130

Quote from: kodark on July 29, 2019, 03:44:57 PM

Where to report bugs?

There is a bug that, when the lua scripts stops for not having sufficient funds, if you deposit more and start again, it will go ahead with the next betting with a higher value or, when changing coins and pasting a new whole script with the correct basebet, it will use the previous basebet and so, you can be bankrupt because of this.

OP, it would be good if this bug would be solved because it cleared my balance at least 3 times before I learned it and thats the main reason I am not donating.

Yes, thats true. But i don't think that's a bug, you only need to stop your betting (on LUA) before you make new deposit. Sometimes my bet hit the green when i make new deposit.

kodark

jr. member

Activity: 32

Merit: 12

Quote from: klaaas on July 26, 2019, 07:14:58 AM

Quote from: HCP on July 25, 2019, 06:19:45 PM

In any case, the answer is likely to be a lot higher than you think it should be. At 50% chance, I think I've seen something like ~20-23 losses in a row. At a 10% chance, I think I got it to around ~130 losses in a row... might have been 140.

20-30 is the same range here at 50% where a losing streak finds a winning bet. I go for a reset or lower the payout over that number most of the times. The same for a winning streak where i maxed out on 24 and reset before that number.

Reset, do you mean, resetting seed?

kodark

jr. member

Activity: 32

Merit: 12

Where to report bugs?

There is a bug that, when the lua scripts stops for not having sufficient funds, if you deposit more and start again, it will go ahead with the next betting with a higher value or, when changing coins and pasting a new whole script with the correct basebet, it will use the previous basebet and so, you can be bankrupt because of this.

OP, it would be good if this bug would be solved because it cleared my balance at least 3 times before I learned it and thats the main reason I am not donating.

houseworx

full member

Activity: 319

Merit: 100

finally stable version, without crashing after many running days, even watching "alltime graph" not crushing it after few days Wink

thanks!

docthusinh

jr. member

Activity: 225

Merit: 4

Quote from: HCP on July 26, 2019, 04:46:25 PM

The best explanation including a mathematical formula I have found is this one:

Quote from: https://www.soccerwidow.com/football-gambling/betting-knowledge/value-betting-academy/learning-centre/betting-terminology/science-calculating-winning-losing-streaks/

Winning and Losing Streaks Formula
The longest expected losing streak (or winning streak) can be calculated using the following formula:

n = number of trials (i.e. total number of bets)
ln = natural logarithm¹
P = probability²
| .. | = absolute value or ‘modulus’

¹ - Suffice to say, explaining what natural logarithm is would be worthy of a series of articles. For the time being, use Excel to calculate this for you.

² - For winning streak calculations use the positive value (i.e. the probability of winning). For losing streak calculations use the negative probability value. For example, if the probability to win the bet is 33% then the probability that the bet loses (negative probability) is 67%.

If you want a formula for Excel or Google Sheets it would be:

Code:

=abs(ln(n)/ln(1-p))

"n" = number of rolls
"p" = needs to be expressed as percentage value between 0-1, so (percentage / 100). ie. 60% = 0.60, 5% = 0.05

You can see it in action here: https://docs.google.com/spreadsheets/d/1T7k5KVUwB606rfyrCrfZNTs8xyVyF7C-0PLlIPzaU8o

It seem incorrect
n = 4166576
p = 0.0495
=> 3358.8 (3359)

While my actual result is currently at 1744 after above "n" rolls (ever seen of 2100-2300++ but not 2400++), it might be correct if above result is not "mean" or "average" but it is "rare", "extremely rare" streak.

Topic: Seuntjies DiceBot -Multi-Site, multi-strategy betting bot for dice. With Charts! - page 23. (Read 274841 times)