Hi Doog... Thank you for founding those problem!
That's very good observation. It does related to rounding but not exactly because of round down / up problem. It is because the server reject an unavailable payout. Here's our explanation.
We have fixed this issue now, the payout will now change to the nearest possible payout automatically when the H.E. changed.
Done! We don't have a bug bounty program, but may reward it in an ad hoc manner. Many thanks for all the reports and suggestions so far Doog
Lol, luckily you won those bet
Edit3: I think the problem is that when the payout multiplier is fixed, and you calculate the chance from it, you're rounding up instead of down, giving a slightly lower house edge than intended, which the server then rejects. When I'm trying to bet 0.04 to win 2x, the chance is set to 49.662%, but if I put 49.662% in the chance box, the payout is a little under 2x. I ended up editing the chance to 49.661%, the payout went a little over 2x, and it let me bet. I suspect you can fix this by rounding down instead of up when calculating the chance from the payout multiplier.
That's very good observation. It does related to rounding but not exactly because of round down / up problem. It is because the server reject an unavailable payout. Here's our explanation.
- When the user manually set the payout, browser will round the payout to the nearest possible payout (because roll number / win chance is actually a discrete number) after the user is done editing
- With variable H.E. the payout can change in realtime. When the H.E. changed, browser changes the win change according to the user payout.
- However, the payout still remain the same, and those exact payout doesn't always available (remember that roll number is discrete).
- When the user rolls, SD's server check the roll integrity and found that the submitted payout slightly missed, therefore the safety mechanism rejects the roll (our log literally wrote "impossible payout" ).
We have fixed this issue now, the payout will now change to the nearest possible payout automatically when the H.E. changed.
Is there a bug bounty on this site? If so, please credit it to my on-site balance.
Done! We don't have a bug bounty program, but may reward it in an ad hoc manner. Many thanks for all the reports and suggestions so far Doog
Edit4: The variable house edge feature works pretty well (other than the error I reported above). Here's a screenshot showing how the site got me betting against a 5% house edge - something I would normally never even consider doing.
Lol, luckily you won those bet