Thanks. I was thinking after I sent the bug report that it would have been smarter to have played some 1 BTC per game throws, waited until you paid out a few 2-2 and didn't pay out some 2-1 rolls, and then complained that the 2-1 winning rolls didn't get paid out. You would have made good on them I'm sure, and the odds would have been in my favour. Then I thought maybe others would do the same after seeing my bug report. I hope it didn't cause you that kind of trouble.
Thank you for taking the white-hat approach
OK, so you don't need to see the screenshot I just made of being paid 8.75 for winning the "any craps" bet... I played the hand before going out this morning and only just got back to screenshot it. I expect you've fixed that one too now.
Yeah, we've fixed that wager too. The same issue was affecting all of our "Single Rolls" wagers, and we fixed them all.
You're welcome. It's refreshing to have my bug reports appreciated, acted upon, and rewarded.
Your feedback has consistently been incredibly informed and very helpful. You're definitely an asset to the community, and an asset to anyone that listens to your feedback
Edit: your post doesn't seem to explain why 2-2 was being treated as a winning roll when betting the 1-2 bet. I guess that was just a typo, right?
Yeah, that was just a bad typo. Our simulation testing didn't catch it, because the odds were still paying out what was expected, it was just paying out for the wrong rolls. Fortunately, no one had made any real-bitcoin bets on that wager since launch.
It looks ugly to me to see odds written as "7.5 to 1", especially when just below I see "33 to 2". Fractional odds are traditionally written using integers. So instead of "7.5 to 1", we write "15 to 2". Or write everything as "x to 1", so "33 to 2" becomes "16.5 to 1". Mixing the two different forms looks weird.
I don't know if your table is a bitmapped image, or whether you can update the text on the fly, but maybe it would be nice to allow the user to chose fractional or decimal odds. I think different formats are common in different countries. Probably the easiest to understand is "8.5x" rather than "15 to 2" - just writing the multiplier that is applied when you win.
Hm, yeah good point. We originally decided to show the hardways bets as 9.5 to 1 and 7.5 to 1 in order to contrast with the typical 9 to 1 and 7 to 1 payouts. 19 to 2 and 15 to 2 is probably more consistent with the rest of the table now though. I went ahead and updated this.
Fortunately, it's all in HTML, so it was an easy change
I'm no expert either, but I remember reading somewhere that you should never mix serif and sans-serif fonts.
I did a little more looking into this, and it seems that it is generally acceptable if you're trying to create a contrast between different elements - which is definitely what we're trying to do: contrasting the table against the rest of the webpage. So, for now, I think we'll keep it as-is.
$ lsb_release -d
Description: Ubuntu 12.04.1 LTS
$ dpkg -l chromium-browser | tail -1
ii chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04 Chromium browser
I'm also using XFCE4 rather than Unity as my desktop environment, in case that matters. It seems unlikely though.
This is very strange. I have the exact same version of Chromium on linux and I can't replicate the issue in your screenshots. Is the Roulette table still doing a similar thing for you? I saw your Roulette screenshots, and I was able to replicate that and I think I fixed it: The issue was using decimals in the CSS for width and height, which Chromium rounded differently than other browsers. But, now we're not using decimals in the CSS anymore, so I can't figure out why a standards-compliant browser would be off by a few pixels in this way.
Also, did you change the odds in the last few hours? Earlier I was getting 17 to 3 for "any seven" and now I'm getting 29 to 6. That's a drop from 5.666 to 1 to 4.8333 to 1. Ah, it's a 5 to 1 event.
I should have bet it more earlier when you were paying better than breakeven odds for it.
Edit: Oh, I get it. The bug you fixed wasn't that the payouts were wrong - it was that the quoted odds were wrong. You were always paying out the right amount and only the odds printed on the table were incorrect.
Yeah - all the payouts were always 35 for
X, where X is the number of possible winning rolls. We simply converted it into "Y to
X" notation completely incorrectly.
Thanks again for all your help!