I lost even though I won in limbo can someone explain ?

[natah3]

https://stake.com/provably-fair/calculation?game=limbo&serverSeed=292b7009ad1f8590afdb8039fb43a91d9b582d4604b56fea1b24d55fab779299&clientSeed=wCwZyxlTDW&nonce=3980

[ozcelik06]

Interesting. It must be winning bet. But isnt.

[quaviment]

wow 

very silly thing

[ROkenTratENsaV]

Target payout must be below the limbo result to win

[kingnayim2]

i querid the bet and target multiplier is 1.14x 

but somehow in preview it shows 1.13x

if you did bet targeting 1.13x then you must report this

I just tried to bet targeting 1.14x and when i preview the bet it displayed my target as 1.13x

so it seems like limbo target multiplier not displayed correctly on client side 

[Drpepper22]

Lmfaooo

 

[alexmir89]

Wow, this is unusual 

[natah3]

UPDATE 

they muted me

[centaxfn]

Very strange

[alexmir89]

Also extra unusual when bet is not even big, have you tried contacting live support? Or any mods can answer this @Tristan

[pascalwl3]

Mods seem to be on holidays.

[WE5TCOA5T]

I know that on dice the result must be over the target... So maybe that's the case here? As far as getting muted for spam.... Were you spamming about it in chat? Or was it during a tg challenge(so wrong bet etc) 

[pascalwl3]

Its limbo @WE5TCOA5T

It doesnt have to go over otherwise 1% house edge is not correct

[Anthra]

Also had the same at Dice

My X was on 0.08 and the Dice goes to 99.92 - was an Fail round and dont got the Multiplier

[natah3]

UPDATE 

they changed my target multi 

 

 

 

[iamback1992]

Jesus .. what a scam to mute you first and then went in changed the target multiplier.  At first I thought it's because of the house edge 

[natah3]

On 1/5/2022 at 10:24 PM, Ghostnipple said:

the number result shown to you is rounded up but only 2 decimal places are shown, but the actual result is 12 digts long

1.1369408843872

which is greater than your target of 1.13

 

well you lost 1.94 cents.... so put it down as educational expenses.

Do you think the important thing here is $2? if you think so I had bets that I lost with higher bets before, maybe they had such mistakes too

[unrealltv]

Weird

[Oilfieldtrsh88]

Dang that sucks man sorry

[BiggClay]

On 12/26/2021 at 11:23 AM, natah3 said:

UPDATE 

they muted me

Ohhhh no, contact live support when they get back from holidays. It’s on their house game so they should be able to fix it unlike slots or evolution games

[natah3]

8 hours ago, Ghostnipple said:

did you understand my point? I just told you the final result has 10 digits after the decimal point. The game displays only 2 places, the number displayed in the game is rounded for convenience, but the number used to determine the win is the 10 digit number. If you want to see the full number from the result you need to change seed and verify the bet.

https://stake.com/provably-fair/calculation?game=limbo&serverSeed=292b7009ad1f8590afdb8039fb43a91d9b582d4604b56fea1b24d55fab779299&clientSeed=wCwZyxlTDW&nonce=3980

 

 

 

1.1354678181511668

[dupeddonk]

9 hours ago, Ghostnipple said:

did you understand my point? I just told you the final result has 10 digits after the decimal point. The game displays only 2 places, the number displayed in the game is rounded for convenience, but the number used to determine the win is the 10 digit number. If you want to see the full number from the result you need to change seed and verify the bet.

The final result only has 2 places after the decimal.  Whatever the first two digits after the decimal are used as the final result.  The third and following digits have no influence over the final result.  The mistake is in their bet verifier, there's no need to show the extra digits.  I've already explained this to you many times though.

[dupeddonk]

3 hours ago, Ghostnipple said:

incorrect. the final result is the final result. that's why it is indicated as the final result.
 

 

Except only two digits after the decimal are used, all the other digits are irrelevant to the outcome of the bet.

This is an incredibly petty argument you've made over and over, but I'll try to explain again so that people who didn't witness any of the previous times will be less likely to just assume you know what you're talking about and cry scam.

That number they display as final result in the bet calculator is the variable labeled floatPoint below.  

As you can see there are two more steps.

Step 2 we declare const crashPoint , which is the same as const floatPoint , except it's been stripped of all the digits following the second after the decimal.  That's what the Math.floor() function is doing.  Remember your outrage when you learned they were 'rounding down', and I explained over and over that this was proper, because rounding down is the same as simply ignoring any digits after.  When you round down, the final digit is never changed, unlike when you round up.

Step 3 we declare const result , which is identical to const crashPoint as long as it's greater than 1.  If it's less than 1, than const result = 1.  That's what Math.max() is doing, it just returns the largest number (crashPoint or 1).

That's why the result is never below 1, and never has more than two digits after the decimal.  

 

 

[dupeddonk]

57 minutes ago, Ghostnipple said:

I don't know what you have written there because I didn't read it.

 

No worries, it was a bit technical.

To summarize - I was just explaining for you and anyone else that's interested  that despite what's displayed in the outcome calculation breakdown, each limbo outcome only goes to two digits after the decimal.  The rest of the numbers are ignored.  

[Narchy]

On 1/8/2022 at 10:52 PM, Ghostnipple said:

did you understand my point? I just told you the final result has 10 digits after the decimal point. The game displays only 2 places, the number displayed in the game is rounded for convenience, but the number used to determine the win is the 10 digit number. If you want to see the full number from the result you need to change seed and verify the bet.

Stake uses Math.floor function, which basically means the number is always rounded to the lowest number, example: if the number was 1.139 it would be rounded to 1.3 not 1.4, as the guy above me said, probably is an error on the display target in which probably is set to 1.14 but it shows 1.13