Don't Play Stake Crash for now.

[Enzo]

I wanted to warn everyone of what can only be called a bug within Crash.

So we all know the basic premise of crash? You set your desired cashout and click bet. Watch the numbers rise and hope it doesn't bust. Well you would think, if you're given 2 decimal places to write a cashout number. You wouldn't need more? You'd be wrong.

Apparently on stake, you can have crashes that aren't flat 1.24 or 1.25, they can be 1.2470946464607078 or some bullshit.

You can see in the image I had auto cash at 1.25, therefore, based off the fact that any reputable site with a %1 house edge would give you this as a win, i would assume that this is a winning bet. Somehow it's not the case on Stake's version of crash.

It's made clear when you click "Verify Bet" and you're taken to the calculations for the result.

There you will see what the ACTUAL crash was. Which in my opinion is dishonest. If we're gonna have this added edge I think we should know about it and be given a way to counteract it.

I've already left a few messages with Eddie regarding this topic and I hope to have an updated outcome for you all.

[Thepug]

In a circumstance like this, I can imagine that you will have a chance in getting your money back. It is just a bug on their behalf and hopefully your bet can help them solve this. This probably hasn't happened for a long time, so it is lucky that we have you to show them a bet like this!  

[lisinjo]

Wow great topic for letting us now thanks a lott budd

[nuuuitsjdragon]

I think this is not unique to crash as there are other payouts (e.g. Mines) with many decimal places that are rounded up/down to the second decimal place. 

In your case, since it was 1.247*******, the number shown was 1.25x because of the rounding technique. 

This definitely needs to be changed as regardless of rounding, there should be an indicator of what that exact multiplier is instead of being stashed away in the “verify results”.

 

[jerrahmaya]

if the display number is rounded to 1.25 then the payout should be done at 1.25 too

[Ali saher]

I think crash is very risky game I try some time but not get good results but I see so many people's when creash release they got very big payouts on crash game.

I think every time every game not give you good results maybe when you play this time game not play good

[xdddddddddd45]

Noticed this when i played earlier

[Wakiee]

Thx for the tip! Good to know! IT really crashed haha jk they Will fixed iT soon! Stake is fast with iT! Thats why i love stake 

[CntryBoy]

Thanks for bringing this up.  I also noticed a similar thing happen, though my bet lost either way.  Hopefully Stake will take this into account and get it fixed...

[wyj1306]

9 hours ago, Enzo said:

I wanted to warn everyone of what can only be called a bug within Crash.

So we all know the basic premise of crash? You set your desired cashout and click bet. Watch the numbers rise and hope it doesn't bust. Well you would think, if you're given 2 decimal places to write a cashout number. You wouldn't need more? You'd be wrong.

Apparently on stake, you can have crashes that aren't flat 1.24 or 1.25, they can be 1.2470946464607078 or some bullshit.

You can see in the image I had auto cash at 1.25, therefore, based off the fact that any reputable site with a %1 house edge would give you this as a win, i would assume that this is a winning bet. Somehow it's not the case on Stake's version of crash.

It's made clear when you click "Verify Bet" and you're taken to the calculations for the result.

There you will see what the ACTUAL crash was. Which in my opinion is dishonest. If we're gonna have this added edge I think we should know about it and be given a way to counteract it.

I've already left a few messages with Eddie regarding this topic and I hope to have an updated outcome for you all.

Wow this is something strange, but it is true these extra decimal places may end up disrupting at some point, I do not play this game, since they released bet a maximum of 10 bets in it.

[FotisNt]

Well, thats kinda weird. I would actually ask a support member or something to give me a reason for that.xD Anyways, even if its not a big loss, it still seems kinda unfair.

[jualid]

Not only crash but also on limbo too, cmiiw. iirc, support explained about this thing a few monts ago, i forgot where is the post. Sorry this happened to you, it sucks.

[DCYuma]

It did happen to me also I was auto cash out at 1.3 then I notice im not auto cashout and the crash keep rising Then I thought it was lag so I refreshed after I see the log so that I will know what the crash multiplier is it waa crashed at 1.45 and my auto didnt do his thing maybe because Im lag

[iamsheikhadil]

14 hours ago, Enzo said:

I wanted to warn everyone of what can only be called a bug within Crash.

So we all know the basic premise of crash? You set your desired cashout and click bet. Watch the numbers rise and hope it doesn't bust. Well you would think, if you're given 2 decimal places to write a cashout number. You wouldn't need more? You'd be wrong.

Apparently on stake, you can have crashes that aren't flat 1.24 or 1.25, they can be 1.2470946464607078 or some bullshit.

You can see in the image I had auto cash at 1.25, therefore, based off the fact that any reputable site with a %1 house edge would give you this as a win, i would assume that this is a winning bet. Somehow it's not the case on Stake's version of crash.

It's made clear when you click "Verify Bet" and you're taken to the calculations for the result.

There you will see what the ACTUAL crash was. Which in my opinion is dishonest. If we're gonna have this added edge I think we should know about it and be given a way to counteract it.

I've already left a few messages with Eddie regarding this topic and I hope to have an updated outcome for you all.

Oh man that must be frustrating for you!

Indeed it's sad to see a bust that close to the winning amount.

Maybe if we are given to choose more precisely, we can have a control on it.

I hope you recover your funds and good luck on future games!

[Etude]

In my case I rarely do play Crash due to facing performance issues on my devices both phone and laptop which is rather to up to the present day standards which makes me face lag so I guess I will still take note of this discovery though.

[Dan]

There is actually nothing wrong with this result, other than perhaps a lack of explanation. I'll show you why and hopefully explain it, well enough for people to understand.

Something to also consider, before I start, is that all game events use Math.floor() (results are rounded down) to the required denominator. So with Limbo, you would actually see the same thing, because we show the full result of the game event, rather than the rounded result.

Here is code example:

// Game event translation with houseEdge of 0.99 (1%)
const floatPoint = 1e8 / (float * 1e8) * houseEdge;

// All our game events are rounded down to the required denominator
const crashPoint = Math.floor(floatPoint * 100) / 100;

 

If you look at all our games provable fairness, you will actually notice rounding down is consistent across the entire site, despite our current choice to show the entire float calculations.

[niki014]

meh in all the crash websites it is liek that 
tho i dont like crash i never play it cuz its slow  and it is boring 

[SovietDoggo]

It has been insanely laggy and hard to cash out, i've tried everything to see if it was me or not but I think it's just Stake at this point. It's decent but at that point i'd rather play limbo and go for an instant hit at a selected multiplier. 

[firewolf7876]

what you mean bug,but when you do 1.25x it would be.. 80% and becouse of 1%house edge. that like <79.20 and if you get 79.40 you would say its a bug too? or when you get >1  (99x) but  its 1.. its a lose. it has to be number over that.

[sheenazbay]

in my opinion this is a good topic, I came to understand more for some things why I didn't hit my multiplier, apparently there are decimal numbers that make us not hit on that multiplier, thank you for sharing

[wngo123]

Wow actually this happened to me in the past but with much , much slower amount so I didn't care, but I was wondering why I crashed if I actually reached the target. Now I understand and really don't like it.