First, I came straight out of a match and opened a case, it said loading and then said error occurred, then the case disappeared while it still had the loading sign. I cancelled this.
I then traded up 4 loudouts for sawbonez and got the BL82 Original operative 4 times. I then traded them up in bronze twice, same result. did it again for silver, same result again. I then traded it in for silver, and I got the same card again.
Is this a bug or just extremely bad luck?
One of the mods had a theory about it not being bad luck. I can’t remember who it was or how they explained the system. I think it might have been @Ardez or @Amerika but I really can’t remember. I did 11 trades for Thunder and 10 of them were the exact same card (MA71 I think) in different rarities. I bought 10 expert cases and recieved 3 double ups with 8 of them being Sawbonez. The odds of this happening even once are so slim, but it’s becoming incredibly common lately. I’ve even been having triple up’s in ordinary lead cards as of lately. The other day I opened 12 ordinary cases in a row or something and when I checked my loadouts afterwards 3 of them were the exact same Thunder lead card. The double/triple/quad and higher reoccurances just seem so far fetched given the odds this system gives us.
That was me. RNG systems typically use entropy based seeding to produce random results and it pulls from multiple sources.
I explained my theory better in the other thread in regards to DB but this is some basic info on it - https://en.wikipedia.org/wiki/Entropy_(computing)
There is a chance that whatever system they are using to create random results isn’t producing random results due to a failure with certain types of hardware or some other flaw that would instead produce a consistent result.
An example of a flaw would be a system that is setup to pull a certain amount of entropy from a system to seed results but you don’t give the system enough time to generate enough entropy and instead of making the user wait it insteads repeats previous results. Or, the seeding data is somehow getting cached sometimes as opposed to going stale and replaced which would produce a consistent result.
I honestly have no clue what implementation they use so I’m pretty much just spitballing theories.
