We just pushed out a new update which makes the bet pre-calculation dialog a lot more useful with multipliers which are further from the standard 2.0 multiplier. In parallel to this, values returned by server-side calculations are now without rounding errors.

Enjoy and play it safe.

Can you be more specific about what needs more work? We really try to listen to our player's suggestions and if we think anybody has an idea that's any good, we take note and put it on our Todo-list.

Thanks for any feedback you provide.

There is no difference for tips in terms of horse betting or dice betting. Come find us in chat, tell us that you're using the horse game and we'll gladly help you out with a tip if it's not your lucky day on the horse game.

Well, right now you basically have a 20% win chance when betting on a horse. So on average, if you keep betting on the same horse, you should win every 5th bet (on average!). However, the horse betting game will be substantially improved and upgrade in the near future and will offer lots of exciting options and possibilities.

Thanks, glad you like them. We aim to please 

New version has been published, see the dev post (2nd post of this thread) for details.

Update Notice:

Please note that we'll be pushing a substantial update into production tomorrow morning 9AM CET (Central European Time). There will not be any interruption of service but you'll be forced to reload the page once the update is live (actually pushing the update into production takes < 1 sec).

If you're running our AutoBot, please make sure to stop it before the update in order to avoid getting stuck in a deep loss streak when the update hits (and stops you dead in your tracks).

It would seem that MoneyPot.com is under an large-scale DDOS attack. Now that we know the cause, hopefully we'll be able to get back online soon. We'll update you as soon as the situation is under control again. Thank you for your understanding and patience.

Dear BetterBets.io users,

it seems that we have a networking issue with the Moneypot.com server which processes our bets (and anything else we do on their server). The current situation is that our local services work like a charm, but requests going to the Moneypot server time out.

We have contacted the MoneyPot admins and appreciate your understanding while we investigate and fix the issue. Our most sincere apologies.

Edit: it seems that http://moneypot.com/ and all it's services are down. We're in contact to get this fixed.

Thanks for the info; I'll take your suggestions to heart. I have a beast of a machine (32GB Ram, 256GB SSD, 6TB Disk, etc.) so I sometimes forget to worry about low-end machines or small displays like yours.

You on mobile (or did you just make your window less wide)? Anything you're not happy with?

Asking because I don't really ever use a mobile client on our site.

Yes, come onto https://betterbets.io , get tipped and help us load test our setup.

We've just (about 5 min before Happy Hour starts) pushed out a new build with some bot enhancements. See the dev post (2nd post of this thread) for details.

Enjoy, play it safe and good luck everybody.

We just pushed out a new build which fixes 2 very annoying issues:

1) You should never see the INVALID_HASH error again
2) The annoying multiple chat messages should now also be history

There's a few more changes which are backend related and will hopefully allow us to better diagnose some of the errors we've been seeing but in terms of front-end, those 2 major annoyances should be gone now.

Enjoy and play it safe.

Thank you for your kind words and understanding.

Good suggestion about the bigger font and red letters for such announcements. Will definitely do this next time so people don't miss it.

Hello Everybody,

first of all, allow me to apologize for the extended downtime; we were hit by what I can only describe as a perfect storm of circumstances, of both technical and personal nature. I believe that we have fixed the issues we faced, and in the process discovered 2 nasty bugs which were hiding in our codebase but which were only triggered by a specific set of circumstances.

Since I believe that we owe our users an explanation, rather than just tell you that things are fixed, allow me to explain what happened and why things took so long:

1) Yesterday we experienced some temporary cloudflare issues which caused service interruption for some people
2) Once these were supposedly resolved, the system continued to degrade periodically; the reason for this was not clear at the time it happened.
3) We started digging around and due to the earlier cloudflare issue, departed down 2 false/wrong trails of investigation
4) #3 caused us to waste a lot of time digging around various system components which in the end had nothing to do with the issue
5) Around 6AM, after being awake for like 24 hours, I was starting to fall asleep in my chair and decided that I had to get a few hours of sleep (all-nighters are definitely easier when you're college-aged)
6) At 8AM my wife woke me up with the news that our daughter, who the evening before was only 50% sick, now had developed a fever of 39.5 degrees (103 degrees Fahrenheit for you non-metric folks). So off we were to the doctor.
8 ) I returned back home around 11AM, I looked at the code and within 1/2 hour found the culprit.
9) Did some testing and decided that things now worked OK.

So, it was cloudflare, lack of sleep, my daughter's illness and a stupid coding error I had made, all of which combined to prevent a speedy resolution of the issues we faced. The coding error in question was triggered by the initial cloudflare outage and caused bad hashes to propagate throughout the system; my code attempting to fix this caused an infinite loop which explains the 'death' of the web server once this occurred.

So, I apologize and accept the bulk of the blame for the extended outage. The good news is (as stated above) that this caused us to spot 2 nasty errors in our codebase which are now also fixed.

Anyhow, thank you for being patient during this difficult and messy time. I promise to try to get some more regular sleep in the future which should help with avoiding stupid coding errors.

PS: We still have an open ticket with cloudflare about 1 specific issue which they will hopefully address soon. This addresses a minor issue which should not have a site-wide impact on service.
PS2: I still have to restart some services later today but this should only be an outage of a few seconds.
PS3: If you access our system and you're automatically logged in (using the credentials from your last visit), please log out and then log back in. This should force restoration of your server hash and some other parameters to a sane/valid value.

We believe that we have pinpointed the problem and that it also involves our server configuration. As such, we have put out server into maintenance mode while we try to fix the problem.

Let me make this perfectly clear: We are NOT going anywhere, this is an unexpected problem and we're dealing with it. We'll be back soon and hopefully in better health than ever.

After another short outage, it seems that things now are finally back in working order. If this keeps up we will ditch cloudflare and look for a different solution. We are in communication with them to get to the bottom of this.

We just got a status update from Cloudflare, things should be back in solid working order now. Once again, thank you for your understanding.