We changed it because we felt like our dev possibly messed up and leaked the server seed when the same roll incident happened. What we should have done is just ask him to change it himself so he knows it is 100% random and he's not given a seed which gives him more high or low numbers
(Which wouldn't make sense anyway since he has no pattern, he bets hi/lo randomly)
The issue isn't you changed the server seed, that's not a problem at all. But if you do change the server seed you should do three things:
a) Show the previous server seed (so past bets can be verified)
b) Prove you've committed to a server seed (i.e. give the hash of it)
c) Allow the user to pick their own client seed.
So from the sounds of it, the lack of a) is the biggest issue here. Is there a way for unibtc to verify his previous rolls? But changing a server seed while keeping the users client seed the same is another big mistake, but something separate and mitigated by his unpredictable playing.
Unibtc isn't happy with our mod "BTC" because BTC watched Uni win over and over and change from hi to lo perfectly as well as know when to bet higher and win. Which I can't do anything about, everybody is entitled to their own opinion.
Well, pretty much all lucky winners look like they're cheating. You might as well assume they the best, as if they're legitimate players you risk driving them away. And if they're cheating, they're really not going to care if a mod is being rude.
As for Uni ending his session in a losing spree, That wasn't the case at all. The whole reason we changed it after that session was because he was constantly winning.
Completely understandable. It sounds like that was the right thing to do, but steps a) b) and c) just need to be done as well
