They also fuck with your bet speed if you're profiting to try and throw you out of focus. Proven by using two different accounts on same network. One was betting insanely fast the other was profitting and kept getting disconnected/speed was really choppy. I think they are selective hashing when this is occuring. I have so much to say about this site, will add more later. I'm currently mobile.
Before I switched to the API, I absolutely did notice it. A lot. I even effed up a few bets because of it. Hit the button... nothing happened. Hit it again, then boom, two losses. But never considered that it might be part of the plan.
Please do post more when you can later. I'd absolutely love to read it.
Okay so I wrote a Node.js script just to test out the bet speed using the raw web API.
I noticed a few weird things.
1. Sometimes I will randomly get an "Error: Invalid Request", then It'll send the identical request in 350ms and it'll process fine.
This is fishy to me because that error is usually thrown for a different reason. Aka the backend is denying the request.
I want to reproduce this and see if they are changing the server seed when this occurs. All the other errors are very specific.
If you are betting too fast it will throw "Error: Too Fast" etc.
2. I ran the bot on one account using a shitty method that would most definitely lose. I set the bet speed to 200ms. (5 bets a second).
...I did not get "Error: Too Fast" or "Error: Invalid Request" a single time.
Then I ran it on another account, using a much better method. This time I only set the bet speed to 350ms.
That's only ~3 per second.
Every time I started to profit it would give me a "Too Fast" error, sometimes even disconnecting me completely.
...even though I was using the same bet amount and an even slower bet speed.