Turns out Im kinda blind and mostly stupid... Not sure why I thought it was Spanish other than Im kinda burnt out today.
No worries! Would you be interested in us adding Spanish 21? We haven't heard any demand for it, but maybe we could add it to our todo list. Hell yeah! Honestly, I probably thought it was Spanish because that is all I really play when I go to the casino (which is far too often...). I dont know how many other people would be interested, or how many actually know what it is, but I would def. be interested. Alright, cool! We'll add it to the list. I imagine it won't be as much work to build because of its similarities to blackjack. Keep on the lookout! |
|
|
|
Turns out Im kinda blind and mostly stupid... Not sure why I thought it was Spanish other than Im kinda burnt out today.
No worries! Would you be interested in us adding Spanish 21? We haven't heard any demand for it, but maybe we could add it to our todo list. |
|
|
|
Congrats on your amazing growth!
Thanks! Why cant you double after taking a card? Is this Black Jack or Spanish 21? If the latter, then this is the first time Ive ever played with these rules.
We don't offer Spanish 21, only Blackjack. Blackjack does not typically let you double after hitting. In fact, many varieties of Blackjack only let you double if your initial total is 9, 10, or 11. The fact that we allow doubling on any two cards is more liberal than most rule-sets. |
|
|
|
Hey! I just noticed my bonus for playing near the 10 millionth hand! THANKS!!!! Bitzino is the best.
You're welcome! Enjoy  |
|
|
|
We have just surpassed our 10 millionth hand played! We created some pretty charts outlining our gameplay breakdown, which you can see here: https://bitzino.com/about/numbers/10_million_handsAlso, in celebration of the 10 millionth hand, we're giving away bitcoins! We gave the lucky player who played hand number 10 million a 1 BTC prize. We also gave every player that was actively playing during the milestone hand a 100 mBTC runner-up prize. We also gave every single active player over the past 2 days a 10 mBTC bonus. Thanks to all our players for an amazing 10 million hands! |
|
|
|
Love the site and the new additions that keep coming. That cool off feature would have been nice after I went on some big runs then gave it all back (and more!) I will never go back to traditional online gaming sites, that is for sure. Can tell you care about reputation, which is important. Hopefully your hard work along with the recent run-up in BTC has served you well! Any update on the loyalty program? Hopefully it will be somewhat retroactive, but either way I look forward to it. I agree with others who suggested that the deposit bonus system that traditional online casinos (wow can't believe that is a term now) used is not ideal - it is subject to abuse on both ends. Thanks for the kind words! I love the differentiation you make with us an traditional online casinos The rewards program is still in the works, but we are planning on rolling out 3-card poker as our next big release. After that we'll hammer out all the details and get the reward program ready to launch. I know I said the same thing before launching Slots, but sometimes it can be hard to get the exact timelines right, so sorry about that! I can tell you that it will be worth the wait! |
|
|
|
Just a small thing: the 3 day and 7 day periods are in the options now, but gives an error when I try to enable.
Sorry about that! We have now fixed this issue, so any cool-off time is allowable. Thanks for letting us know about the problem! |
|
|
|
- We made the Roulette history slightly darker. We spent a lot of time experimenting here with different changes, but the change we ended up making is relatively subtle. Let me know if it helps with the eye strain!
It's a little bit better. Or maybe I am just used to it, I can't tell. Thanks for the feedback regarding this, and please let us know if there's any other color issues you see (or any issues at all!) I've added a comp to your account to thank you for helping us make bitZino a better place to play! I love the cool-off period! Seriously. If there is any additional request I would make is to add 3 days and 1 week options.
Glad you like it! We just went in and added a 3-day and a 7-day option as well. |
|
|
|
After running with an increased passphrase timeout for the past few days, we have not seen any problems. No more bitcoind crashes, and no more "code: -4, 'Transaction creation failed'" errors. Specifically, we are now running the code: walletpassphrase <passphrase>, 60
sendmany "", {"<addr>": <amount>, ... }
We noticed that sometimes the sendmany command was taking close to 20 seconds, so to be on the safe side, we increased the timeout to 60. We couldn't seem to find and existing bug report on this issue though. We're planning on collecting some more data, and then submitting a proper bug report. |
|
|
|
We've pushed a handful of changes which address some of the issues recently discussed: - We made the Roulette history slightly darker. We spent a lot of time experimenting here with different changes, but the change we ended up making is relatively subtle. Let me know if it helps with the eye strain! - You can now set a self-imposed maximum bet from your settings page. This helps prevent you from accidentally betting more than you intended to. - You can now enable a self-imposed "Cool-off" period. During the cool-off period, you won't be able to make any real-bitcoin wagers from your account. This hadn't been discussed on these forums yet, but we've gotten some user feedback regarding it, and it fits in well with the self-imposed maximum-bet feature. We want our players to have fun, so hopefully this feature can help make sure it stays fun. I am somewhat surprised that you would choose blue as your main color. Research has shown that color has a huge effect on emotions, and considering that your main source of revenue is people staring at your color scheme for hours on end, I would guess this effect is accentuated tenfold. Would a bright, cheerful color scheme not be better suited to motivate risktaking?
Our strategy has always been to maximize players' playtime. That's why we have small house-edges and tiny minimum bets. We'd rather you play for hours with a single deposit, than have you take a few crazy risks and end up feeling like you didn't really have any fun. We intentionally chose a soothing color scheme to match this goal. We've also started work on the advanced roulette features as well as keyboard shortcuts. Keep the feedback coming! |
|
|
|
Thanks for the links! Also, as long as you're taking feature requests, I would like the ability to do self-imposed betting limits. I cost myself a lot of money one time when I played and didn't move the decimal far enough to the left. Gambling addicts could also find this useful to mitigate their problem.
We are working to add this feature as well. Now that we've increase the max-bet for most of our games to such a large amount, this feature will be nice for someone that knows they never want to wager that high. |
|
|
|
In that case... keyboard shortcuts!  Yes please, and keyboard shortcuts!
Sorry it's taken so long to implement this! Keyboard shortcuts have always been on the backburner, but it seems like we keep finding a reason to push them off. We'll stop pushing it off, and get it implemented soon. Here are some roulette features that I would find useful. I am not a gambler, and this is really just a matter of personal taste, so take it with a grain of salt.
1) I am colorblind, so red kind of glows against the ever-so-slightly greenish blue history backdrop. Not a HUGE deal, but after a few hours it becomes noticeable.
We always do try to take color-blindness into account, basically by trying not to rely on color, or at least using highly contrasting colors when possible. However, we don't actually have any colorblind people to test with, so this feedback is very valuable! I wonder if there is anything subtle we can do to alleviate this issue, or if it's minor enough that it's not worth a change? Please do let us know if there are any other color issues that you notice! We have thought about adding a colorblind mode, but ideally we'd just make it work right for all users by default. 2) Introduce empty roll feature (no bet). Roulette brings out superstitious tendencies in even the most rational people, and I think that if you keep roulette logs you will probably find a lot of single unit dummy bets.
We'll think about this... 3) Single repeat+spin button would be nice, instead of having to click each button separately (but I guess this can clutter the interface a bit). If not, then at least swap the double and repeat buttons, so that one can repeat, double and spin in one motion (left to right).
I agree about not wanting to clutter the interface, but this may fit well under an expandable "advanced" section. 4) Invert bets feature. This is the most useful addition that I can think of. If a superstitious gambler (i.e. most roulette players) see 18,27,18,27,18,18 then naturally the desire is to be on everything except 18 and 27. This involves clicking on each number repeatedly. (Unless the numbers are on the same row or in the same dozen, in which case you can bet 12 on each row/dozen and fill the other numbers with a single unit, and then multiply through by some scalar.) Either way it's a pain to do this each time. It would be great if you could either fill all outside bets in one click (with the base bet amount) OR place bets wherever you like (e.g. 18 and 27) and then invert bets by betting on everything but the selected numbers. This would save more time for scenarios like the one I described. More time saved by gamblers = more spins per minute ... PROFIT??
This is a great idea! We see a lot of wagers where the board is completely covered except for a few numbers, and I'm sure that clicking that many times is very tedious. Anything we can do to help make it easier to wager is definitely a good thing! 5) Half button beside the double button. Blackjack already has this, so why not roulette? Sometimes a betting strategy reaches its limit, and you only win half your money back, then one may decide to take a few steps back and keep trying, rather than reset to the starting bet. The other reason is that sometimes you might be trying to distribute the max bet equally among a bunch of different odds. For example, if betting on everything but 19-24, one would place 12 on first dozen, 18 on 19-36 and 1 on zero, and then double through until it gets to the limit. With a 1000 unit bankroll, you end up with 384, 576, 32, respectively. But now suppose you also wanted to bet a separate line on red, but you only have 8 units left. It would be convenient to be able to half, and then place the remaining bets.
Adding a "Halve bets" button does make a lot of sense. We'll work on adding this. 6) Insurance feature. Insurance on even bets would be basically placing a bet on zero. But the size of the bet depends on the even bet wager, and requires a calculator if you want a fixed payout. This can be pretty annoying. For example, for a 200 unit bet on red, the insurance would be 200/18 = 11.11 (say 12), which would pay 12*35 = 420 if the even bet (200*2 = 400) loses.
This could also fit nicely under an advanced panel. We'll see if we can make this work. This is probably a lot of extra buttons! So maybe you can add an "advanced" panel or something. Good UI design is definitely an art, and it's hard to say what works well without trying it out for several hours.
Anyway, I am not sure how much of this is useful feedback. Just some stuff that caught my attention after messing around with your website.
Thanks for all the advice! I definitely like the idea of an advanced area which could house a lot of these option, and just make it easier for power-players to make their wagers more efficiently. We'll be pushing out some other updates soon, and then we'll get to work on these! Thanks again for the feedback, and keep it coming! |
|
|
|
Are you interested in hearing suggestions/feature requests?
Absolutely! We're still in active development, and we encourage our players to let us know exactly what they want, so that we can make the best product possible. |
|
|
|
In your case, I'm happy to help you out if you just send me a PM here (in this case it will probably be easier than opening up a new support ticket).
It wasn't for my account, it was my (imaginary) girlfriend's. She emailed your support address and got a pretty quick response. I was just surprised not to find anything about resetting the password when she got it wrong. Even a "please email us if you've forgotten your password" would help I think? Good call. We'll add some more explicit messaging around this. The UI up there is a little cramped, but we'll find a way to make it work - better than having confused users. |
|
|
|
Do you have any kind of 'password reset' functionality? I'm looking for it and not finding it.
We don't have this functionality exposed, due to security concerns. Since it's possible for people to store large amounts of BTC with us, we want to be able to manually look at each password reset and ensure everything looks good. So, the typical way you can get your password reset is just by email us at our support email, via https://bitzino.com/support. In your case, I'm happy to help you out if you just send me a PM here (in this case it will probably be easier than opening up a new support ticket). |
|
|
|
When you begin to accept LTC? many people are waiting for this step...more than you can imagine $$
We don't have any plans to add support for LTC right now. The main reason for this is we haven't really seen any demand from our players. I'd also be concerned about making the interface more confusing for people: it's nice to be able to show a single deposit address for players when they are getting started. |
|
|
|
Please let me know if there is anything I can do to help make this more useful.
What can I say? Rebuid your bitcoind without stripping the debug symbols. The default makefile.unix already has "-g" to enable debugging. Sounds good! I will recompile bitcoind with debug symbols included, and try to get a better backtrace. In the meantime, I will continue to leave things running with a longer wallet unlock timeout for the next few days, or until another crash occurs, since that does seem to be a promising lead. Thanks again for the help! |
|
|
|
Thanks for the prompt reply, that is very helpful.
According to your stated rules, I have calculated the house edge to be 0.398% when using basic strategy.
What did you both use to calculate the house edge? I'd be interested in something open source, because some sites have some very strange rules which the wizardofodds calculator doesn't know about. We just ran monte-carlo simulations on our game in order to get a house edge. We also corroborated this number with the wizardofodds calculator. |
|
|
|
Thanks for the prompt reply, that is very helpful.
According to your stated rules, I have calculated the house edge to be 0.398% when using basic strategy.
Glad to help! That's the same house-edge we get when we calculate it as well, so I'm glad we're on the same page! |
|
|
|
I just got a core dump. Unfortunately, my bitcoind isn't compiled with debugging symbols. So, when I run the gdb command, I see this message: Reading symbols from /usr/bin/bitcoind...(no debugging symbols found).
The backtrace I get is: (gdb) bt
#0 0x00007f0033c22425 in raise ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f0033c25b8b in abort ()
from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007f003457469d in __gnu_cxx::__verbose_terminate_handler() ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x00007f0034572846 in ?? ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4 0x00007f0034572873 in std::terminate() ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5 0x00007f003457296e in __cxa_throw ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6 0x00000000004298d3 in ?? ()
#7 0x0000000000561ec9 in ?? ()
#8 0x000000000059fdbe in ?? ()
#9 0x00007f00347c4e9a in start_thread ()
from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007f0033cdfcbd in clone ()
from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000000000 in ?? ()
As you can see, not too useful :/ Please let me know if there is anything I can do to help make this more useful. I'm pretty sure bitcoind crashes when "walletpassphrase" timeout while "sendmany" is doing it's job.
I can't test it right now, but as far as I remember then 0.7 had this problem (and I don't think it's fixed in 0.8 ).
That would actually make a lot of sense, given the fact that we usually see crashes during high traffic times - which would probably be when bitcoind would take longer to respond. We will try increasing the wallet unlock time from 5 to 20 and see if the crashing behavior is fixed. Is there a bug report that you know of for this bug, so we can track it? Thanks! |
|
|
|
|
Show Posts
