Hello Guest

### Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

### Messages - cynik

Pages: [1]
1
##### Bugs and Suggestions / Re: Stake Chance Bug
« on: February 17, 2019, 02:37:00 am »
Seuntjie, can you check if I understood the following correctly?
As I mentioned before, in the PD.cs there's the following in line 675 of PD.cs.

Chance = state.condition.ToLower() == "above" ? 99.99m - (decimal)state.target : (decimal)state.target

Assuming that target is the "last" losing result, that means that on Stake betting on 0.01% chance on high the target should be 99.99.
Which means that chance equals to 0.
The above mentioned line is inside the method ToBet() found in line 670 of PD.cs.
This method is then used in line 299 of PD.cs as follow.

Bet tmpbet = tmp.ToBet()

The object tmpbet is then used in line 301 of PD.cs as follow.

FinishedBet(tmpbet)

Within the FinishedBet() method there's the following in line 141 and line 142 of DiceSite.cs.

Parent.GetBetResult(balance, newBet)

I assume cDiceBot.cs is the Parent as it's the only other class with an AddBet() and a GetBetResult() method.
Within the both AddBet() and GetBetResult() method, and also some other methods, there's the following similar line which is used for determining if the bet is a win or a lose.

(((bool)bet.high ? (decimal)bet.Roll > (decimal)CurrentSite.maxRoll - (decimal)(bet.Chance) : (decimal)bet.Roll < (decimal)(bet.Chance)))

If we assumed as previously mentioned, then the chance in the above line equal to 0.
So if the maxRoll on Stake is 100 and I rolled a 100 for high, the lines could be seen as.

true ? 100 > 100 - 0 : 100 < 0

Which is false, meaning according to the code the bet is a lose when in reality the bet is a win.

2
##### Bugs and Suggestions / Re: Stake Chance Bug
« on: February 16, 2019, 08:49:47 pm »
I don't mind testing the beta. Of course, it'll only be on 0.01% chance.
I'll also try to figure out if I can found out where the problem lies.
At the mean time, could also you double check what the actual target values are when making bets?
If the target is the "last" losing result or the "first" winning result.
That way at the very least an external factor is eliminated.

And in regards to the house edge, what you're saying is true. But if I'm not mistaken technically it's still 1.0% house edge, when you round it to the down to 1 decimal, which means it isn't false advertisement.
Maybe if you brought up with Dan he might consider changing it, seeing as you're a trusted user on Stake.

3
##### Bugs and Suggestions / Re: Stake Chance Bug
« on: February 16, 2019, 06:29:39 pm »
I've attached a screenshot from a recent test of the bug.

And a update.
The bug could actually be that the chance changes from 0.01% to 0.00% when betting high.
I think it might have something to do with line 683 in PD.cs, which is
Chance = state.condition.ToLower() == "above" ? 99.99m - (decimal)state.target : (decimal)state.target
This part of the code doesn't change after Stake.cs inherits it from PD.cs
And 0.01% on high means the target is above 99.99, which I guess means state.target is equal to 99.99.
If that is the case, then that mean that chance ends up being 0.

4
##### Bugs and Suggestions / Re: Stake Chance Bug
« on: February 16, 2019, 02:41:17 pm »
I'm using 3.3.24.1

5
##### Bugs and Suggestions / Stake Chance Bug
« on: February 16, 2019, 02:25:39 pm »
I'm using a script that always makes bets on 0.01% chance.
For some reason on Stake, and maybe any other site that has a result size that's not a exponent of 10, there is a bug that changes the chance from 0.01% to 0% after the first win.
There is no instance of setting the chance value apart of the initial one in the script.
I looked at the DiceBot's code and I'm not exactly sure if the problem lies in DiceSite.cs or PD.cs.
But I think it might have something to do with there still being instances of hard coded values in PD.cs, instead of referring to the value in the maxRoll variable.
And these hard coded values didn't change after Stake.cs inherits from PD.cs

6
##### Bugs and Suggestions / Re: Incorrect bet due to different result range
« on: February 01, 2019, 04:34:46 pm »
Update.
I tried another app similar to DiceBot and made similar test bets like before, to see if the bug really was in Stake or in DiceBot.
Lo and behold, every bets are like they should be. Every bets on Stake's log is how they should be.
So the bug actually is in DiceBot.

7
##### Bugs and Suggestions / Re: Incorrect bet due to different result range
« on: January 30, 2019, 03:12:05 pm »
Small update.
I've tested a few bets each with a different chance on Dicebot v.3.3.23, but all still betting on over.
The result: every bet ended up being different on Stake.
The difference is that the target for Stake is always lowered by 0.01, which makes a big difference when making bets on a very low chance.
Here are some of the bets:
DiceBot vs Stake
33.33% - over 66.67 vs 33.34% - over 66.66
25.00% - over 75.00 vs 25.01% - over 74.99
12.50% - over 87.50 vs 12.51% - over 87.49
0.2% - over 99.80 vs % - over 99.79
0.1% - over 99.90 vs % - over 99.89
0.01% - over 99.99 vs 0.02%- over 99.98
Note: I couldn't figure out what some of the bets actual chance were on Stake, since it didn't read any chance below 1.01%

8
##### Bugs and Suggestions / Re: Incorrect bet due to different result range
« on: January 21, 2019, 04:43:49 am »
I updated DiceBot to version 3.3.23, which now seems to make bets on Stake with the result range of 0-100 in mind. However the bug still seems to exit, where bets of 0.01% chance on over still ends up being bets of 0.02% chance on over when looking at the log on Stake. Which could mean that the bug is actually on Stake.

9
##### Bugs and Suggestions / Incorrect bet due to different result range
« on: January 15, 2019, 07:57:01 pm »
I've been trying a script on Stake that makes bets on 0.01% chance. While it does make bets on 0.01% chance, it only does that on bets for under and not on bets for over. On bets for over it actually ends up making bets on 0.02% chance, when I look at the actual logs on Stake itself.
It seems this is caused by the difference in range of results. DiceBot is making bets with results from 0 to 99.99 in mind, while Stake is actually using results from 0 to 100.

Pages: [1]