Topic: bitZino - Bitcoin Casino - Blackjack, Roulette, 3 Card Poker, Slots and more! - page 30. (Read 82361 times)

This site looks and plays great. For me at this point it's pretty much the only game in town after reading that thread regarding dooglus from the operator of Strike Sapphire. What is it about Bitcoin that makes people go crazy?

Anyway, don't mean to get off topic too much. Keep up the good work on bitZino, it's really easy to use and the only complaint I can think of is just that it could use some more games. But it seems like your working on them and adding them, so good stuff. Tried Craps today and it was good, probably my favorite so far.

Another good catch, thanks!

"Or, play with play money" also doesn't give immediate feedback.

I love how each time I find a problem with the site I mention it and it's fixed very quickly.  It's a bit like coding my own site, but without having to do the coding.

That's a good idea. That box is already a little cramped, but I think we can find a way to do this without making the UI too busy.


Yeah, in general, the base currency settings need some re-working, which we are definitely doing. I like your idea of having a "set default" checkbox.


Ah. good catch, thanks!

Ah, yes.  All numbers beginning with 0 are interpreted as octal by javascript.  8 and 9 aren't valid octal digits.


I'd like a "buy in as much as possible" button.  It turns out it was convenient to be able to type '9999999' into the buy-in box and have it replace it with the maximum.  But a "buy-in max" option would be clearer.


I had forgotten that there was a default setting.  That will fix the problem for me, but I think you could make it more obvious.  Maybe have a checkbox on the screen where I set the minimum bet to have it "set as default for all games" or some such.


I think there's a similar issue when you withdraw funds.


Sweet, thanks.

Thanks for all the feedback Dooglus! This stuff really helps us make bitZino a better website.


This was one pretty bizarre! It turns out it was due to the way parseInt is implemented in javascript. We were calling parseInt without the optional second argument (which is the base of the number), and so javascript was trying to parse '08', and couldn't automatically figure out the base of the number. If you just pass the second argument (which is the correct defensive way to code it anyway), then the string is parsed correctly.

We've fixed all our javascript to call parseInt with the correct number of arguments.


Thanks for catching this! We definitely don't want people to accidentally wager for more than they were wanting to.

We've changed the behavior here to just disable the "Cash in" button if the value you entered is invalid. So, now we will never automatically change the value on you.

The default minimum bet on a table will always be the value of your account's "Base currency" (which you can set in your account edit page). I think it may be confusing if we remembered the minimum bet of the last table you cashed out from, rather than using the value you set for your account. I hope that the new behavior of disabling the button should also help to make it clear what's going on.

We don't have the option to increase the maximum bet of an in-progress table, since this would result in a lot of corner-cases usability-wise.

We are still looking at getting rid of the whole concept of "Base currency" though, and possibly having users just always enter the minimum bet when they cash in to a new table. There are just many corner cases and usability issues to consider when making this type of change.

[/quote]
Good catch! We fixed this button so that it greys out when you click it.


Oh yeah, I had forgotten about the notification messages style. I changed the background here to be darker, and also changed the location so that it's not right at the top of the page.

This should make it somewhat better, but we'll probably give the notifications a more comprehensive UI adjustment soon.


I will never get annoyed with anyone's feedback! Keep it coming!

I've added another quarter-BTC to your account, Dooglus to thank you for all the feedback. We highly value useful feedback, so that offer is good for anyone else too!

yikes, I was smashed hard on video poker and blackjack, enough for tonight

I don't know if it's just my eyes, but I find it quite hard to read the green text on a grey background at the top of the screen after withdrawing:

Almost everywhere I click on your site gives instant feedback of some kind, so I know the click registered.  But I just clicked the 'cash out' link in the top right and had to wait a few seconds without knowing whether my click had registered or not.  Maybe darken the text as soon as it's clicked, so I know the click 'worked'?

(and I'm starting to feel like this is too much nit-picking - let me know when the level of my reports becomes annoying please)

A niggle:

I was just playing craps for uBTC.  I cashed out, then went to buy back in.  I hadn't noticed that the units had switched back to uBTC automatically.

I typed "100000" into the amount box and clicked 'Buy in', thinking it was still in uBTC units, not noticing it had been changed on me.  It automatically changed the 100000 to 100 (which is my whole mBTC balance) and bought in for that amount.  I could easily have started playing thinking I was playing for uBTC not mBTC since it (a) changed the units automatically and (b) reduced the amount I asked to buy it for without warning me that it was more than I had.

So I guess I'd prefer it to remember the units I select, until I change them again.  I'm not sure what would be better than automatically fixing the buy-in amount.  Maybe leave it as typed, and just give an error if the user clicks 'buy-in' with an invalid amount in the text field.

Edit: oh, and I don't see a way to change the units back from uBTC to mBTC.  I guess since it defaults to mBTC each time I play, it's not needed the way things are currently set up.

Here's a funny/cool/interesting one:

If I type my bet amount rather than using the mouse, I can't enter any amount that begins with an 8 or a 9.  I can type amounts with 8s and 9s in them, just not at the start.

It's hard to imagine what's special about 8 and 9 that would cause this bug.  I can type 4 then 2x to get 8, or type 7 then +1, but I can't type just 8.

This happens in both craps and roulette, and for both play money and bitcoin play.

The "pass odds" and "don't pass odds" wagers don't have any popups associated with them when there isn't a point established. This is because it yet to be determined what the payout of that wager will be. But, I kinda agree that this is confusing. Maybe we should just show a popup and not show any payout information before the point is established.


Your wish is my command You're right though, the status message was showing up too late, and going away too quickly. We've pushed a fix for this.

Thanks!

It's just a nit-pick, but I'd prefer the status message to appear earlier, before the losing bets start fading, and persist longer, while I'm placing the next bet.

As soon as I click to place my first bet, the status vanishes, and I have to remember the amount for up to 2 seconds!

I notice that the "don't pass odds" and "pass odds" buttons are completely inactive when I first play.  No "less dark background" - just a dead UI element.  Seems a little inconsistent, since the "don't come odds" and "come odds" buttons are always at least slightly active...

We've pushed a fix for this, so now it shows a much more informative status message, including how much was won, lost and pushed on the last roll. Hopefully this make it easier to drink and gamble

We also added a subtle indication as to which wagers are active, and which ones aren't: the inactive wagers have a less dark background on mouseover.

Additionally, we've added the fact that all bets are always working to the rules dropdown.

Thanks for all the feedback everyone, keep it coming!

Ah, that is definitely the issue! It's not a huge issue, since it seems you can't even see the specific problem - but the issue is that all of the wagers have a few pixels of spacing between them, where they should be flush with each other. We'll see if we can fix it so that it looks good at all zoom levels.



This is actually intentional, since we want to allow the user to click and see what the odds of that bet are, and also potentially click and see exactly how much they have wagered. However, I see that this may not be the most intuitive UI - it may be better at least not to highlight the area on hover. I'll play around with the UI here...


Each casino typically does things slightly differently with regard to whether bets are automatically 'working' on the come-out roll. We decided to go with the least confusing option, and always have all visible bets working. From our survey, this is consistent with how other online casinos handle it. Compared to a brick-and-mortar craps game, it's just much easier to quickly remove and re-add your wagers, so it's not really even worth it to have a concept of 'working'. Maybe it would help to have some UI elements to make it clear that all bets are always working though...?

I'm pretty sure there is a problem here...
When the button is 'Off', you shouldn't lose your come bets if you roll a 7. Right?  I also don't think you would lose your place bets either.  In vegas I recall you have to ask for them to be 'working' if you actually want those bets to play on a coming out roll...

When I roll 6-6 on the 'no pass', it's a push.  The result is shown as "win: 1".  I think "push: 1" would be better, to make it clear that 6-6 on 'no-pass' is a push, not a win.

I'd also like to see "lose: 1" when I lose.  At the moment there seems to be no way I can tell how much I lost when I lose once the bet amount has faded out.  That makes it hard to drink and martingale bet at the same time. 

Same for the Pass Line after the come-out roll, I can't add or change that bet but bitZino shows the stake box, with no further interaction though.

Another comment:

In craps, certain bets aren't allowed at certain times.  For instance you're not allowed to make a 'come' bet as your first bet.  You should disable the mouse hover function for bets that aren't currently allowed.  Otherwise when I hover over 'come', it lights up.  I click it, see the stake box pop up, but am unable to interact with it.