Thanks for pointing out that first bug, it is in fact an error in the averaging calculation. It has been fixed and should be pushed by the time you read this.

This is a really interesting topic for sure. I have thought about the disconnect between people's lack of voting standards and it's still something I am actively researching based on what I remember from statistics. There's a great Tom Scott video here on the topic about how averages can settle in on large datasets. Of note is that part about lottery numbers. You can't find an accurate answer when there is none. Level ratings fall in between fact and randomness because they are subjective. So whatever average the site falls on would be representative of the "GD Forums rating index" or how the average GD Forums user rates this level. This is something we don't really get to choose and how useful this number is, will be up to us. Of course this needs a large quantity of active users to smooth out the bumps. I hope to gain some users once the site is in a stable state and I can feel confident sharing it with friends and submitting it to GD Today for example. But I digress...

Making sure there is an even distribution of ratings on levels is my job to encourage users to be active and thoughtful with their submissions. However, there is another trick we can pull...

The system used for rating tags and screenshots uses Bayesian averaging. What this lets us do is anticipate an average ahead of time. If you go right now to add a tag to a level you might notice the score (which is between 0-1 or 0% to 100%) you will get 0.3 or 30%. Why is this? You are the only person voting for that tag so it should be 1/1 100%. Well, the ratings are weighted to a standard which becomes weaker the more people vote on a tag to offset this weighting. There is a downside which is that it requires someone to choose a "default" or "expected" value. So I cannot implement this for levels at this moment. This would be changing the rating totals so they weren't plain averages and maybe I can add a switch to toggle which you see. But basically I need to wait for the "GD Forums rating index" or whatever to develop itself. Once there is enough data, we can draw conclusions such as "A demon level with this star rating and this amount of reviews gets this average score" and we can pick good values that weigh level reviews to their expected rating even when there are a low amount of people rating those levels. This hopefully mitigates, even if it doesn't solve, the A/B group problem. It's not a perfect solution and there are many other I have not yet explored but I felt it I owed it to share where my plans lie in regards to this whole thing.