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

I don't mind suggestions, but please listen to my responses and requests as well.

I can't use the original balance - new balance as profit, as on many sites I have to calculate the new balance manually and deposits/withdraws/tips/bets made outside of the bot influence balance and will thus influence profit as well to display incorrect profit.

Seriously, I have general idea of where the issue is and the tests I suggested will narrow it down a lot.

I know.. That's why I said Last but one..  You may use surrogate keys as primary key and change BetID and Site-Name to unique keys to resolve this.

The balance will be the same since it's received from the site after every bet. The profit for each bet I have to calculate manually, thus rounding errors can occur.

Last but one,  3.1.7..  I did not pay much attention as connectivity in my area is a bitch.  Connectivity can cause this.  But when do you save bet in database?  If you create new record in bet database before placing a bet and at completion/end, update that record accordingly, then we can track this type of error.  Because there will be a record of bet even if that bet has not been successfully executed/placed.   By record status we can know if bet placed, result received(win/lose), statistics updated, txn committed ..etc..  Just thinking loud..  let me know.

The latest version is 3.2.0, not 3.1.7. Bets are committed to the DB once the result is received. At this stage, the bot is not capable of committing a bet to the DB before sending it to the bot (the betID and site name are used as primary keys, committing a bet before the betid is known is going to crash things). This is a good idea though and will be looked at for v4 of the bot.

bet size is not odd.  it is more than 8 satoshi.  Scripts calculates expected profit greater than 1.  chance is 88 so all the bets are more than 8 satoshi.  Yes, rounding will affect but balance is always correct.  Before placing a bet, I roundup to nearest satoshi.  Attached screen shot was specifically for this message for short duration hence graph/chart is off by few satoshis.  I have run this for few hundred bets and I get bigger difference in long run.   If we calculate profit by taking difference between old and new balances, any rounding error will not affect chart/graph.  If we calculate profit independently, then rounding will definitely impact.    Once, I get back to betting, will test run for longer duration and higher amount..

No big deal..  we can live with this behavior..   :-)

Not sure if only me...

I noticed that chart is not getting displayed with correct profit.  Attached screen-shot shows chart after logging in 999dice/btc with 1740 satoshi balance..

screen shot:
http://internet-earning.cu.cc/mlm/dicebot-chart-start.jpg

error screen shot:
http://internet-earning.cu.cc/mlm/dicebot-chart-error.jpg


My balance went south by 20-30 satoshi and recovered by 30-35 satoshi making balance more than starting balance of 1740.  But still graph shows current profit line in negative / below zero. 

I have noticed this for many sessions with different sites.

Note:  As I can not upload any image/file on dicebot site, I am posting this bug here.. 

Yes, I have faced this issue with 999dice.  I was in programmer mode running my script..  Within script, it was reset condition (meaning there was series of winning bets and I had recovered previous losses and nextbet was supposed to be basebet or starting bet and although bet history shows all green bets (wins), balance was reduced by my last bet amount and chart too showed dip for last bet amount. 

I thought may be something wrong with my script, spent about 30 minutes debugging console logs, bet history and my script.. but could not justify..  later on I just left it there and moved on..  I remember that bet as well.  It was 88% chance low bet. and result was 7.8**  and that was 9th or 10th winning bet in the series..

I tried to check on 999dice.  My balance was reduced there.. That bet was correctly processed by bot (meaning I checked provably fair means and bet outcome was same on site and in bot)  Since, 999dice site does not show bets placed by dicebot under "My Bets" page, we can not verify what was that bet.  but it looks like dicebot indeed placed a duplicate bet to 999dice site (meaning repeated last bet). 

Could it be internet connectivity issue?  Think about this scenario:  1) dicebot places a bet. 2) you loose connectivity for some time 3) mean while site sends result 4) dicebot misses that communication 5) you get your internet connectivity back 6) dicebot gets updated balance (may be low/high)

In above case, that bet will not show up in bet history.  It all depends on when dicebot logs bet and when does it get lastbet.ID.  If it is only in response (which dicebot may miss because of connectivity), there is not way we can know for sure for one way or other..

I hope this helps.

SR.

Someone can post some strategy working good for me?

Thx

Again, can you make a video of it happening please? and send me your labouchere list in PM or something. I didn't change anything on labouchere so it should still work identically.


Is there anyone else experiencing this problem?