Thom27: I agree, and have spent an inordinate amount of time analyzing results here.  (I wish it were easier to do, or that the flaw was ALWAYS evident, or the underlying pattern easier to discern.)  I'll continue playing less and less here, until it's remedied.  (I want to spend more time playing and studying--not investigating an unusual system flaw.)  I'm generally an outspoken skeptic of various "dice cheating" claims, but what's happening here is too much of an outlier to be dismissed cavalierly.

I also tried (unsuccessfully) to identify WHEN this skewness began.  I hoped that by doing so, I might help the powers-that-be to identify some code or procedural change that might have triggered it.

wetware: The dice is a total joke on this website. It just doesn't feel right. I have never been one to whinge about backgammon dice before playing on Brainking. I know it is supposed to be random but it just isn't, it is skewed.

moistfinger: However, it is quite surprising because BK uses a very sophisticated system to generate the dice. :)
http://www.youtube.com/watch?v=7n8LNxGbZbs

Pedro Martínez: Great machine, and here was i thinking they paid 1000 people to sit at their cubes and roll dice!

If there is a defect it would seem not to be the random number generator but that the code doesn't use the generator in the particular case mentioned, but instead just gets the last number... sounds like a caching problem?
I wonder if those games were played with 2 people on the same computer? moves happening very quickly? We need more of this type of data most likely, in order to replicate the problem.

Pedro Martínez:
LOL

Thom27: That's a wierd bug... increasing the odds of the second roll equaling the first? What kind of twisted algorithm would cause that?..?..

Unless you wrote code that generated a random number first, then used that to determine whether to roll or just use the first result, ... but why write that sort of code?? It just doesn't seem like a plausible defect.

Any ideas?