Vote Limit Per Developer
At first I was skeptical of how much difference this suggestion would make without unfairly limiting developers with larger libraries or that display more variety, when the main reasoning behind it is to dampen the dominance of only one (which I'm all for, but I want to keep things realistic too). To perhaps quantify the weight of this argument, I went through 2011's voting list and tallied up the number of ballots that contained more than 5 Cave games. What I came up with is somehow worse than what I'd anticipated:
Code: Select all
6 games: x5
7 games: x4
8 games: x8
9 games: x3
10 games: x8
11 games: x1
12 games: x5
13 games: x3
14 games: x3
16 games: x2
19 games: x1
Vote Weight Limit
Some years ago, the maximum voting value was lowered to 25, effectively halving the scoring weight (explanation here) that could be given to a single game. While this was an improvement, it only takes a cursory glance at the "Score" column to realise that 0.5 is still a pretty enormous amount for one vote to give. Following the balancing theme above, I intend to halve that again. To put this in simple terms, it will mean that a ballot must add up to at least four times the value of the highest number present - so on a list starting with a [25], that will round nicely out to 100. I see no legitimate downside to doing this.
Viable Games List
The necessary part. In traditional fashion, the list will be limited to releases up to the end of last year, if that's even an issue yet. Any help categorising the swathe of iWhatever ports and oddball Cave releases since the previous list will be very much appreciated.
If I have one thing I want to take this opportunity to achieve, it's to make the 10th top 25 list the best that I can manage; I would've preferred to have been a little better-known before attempting this but hey, you take what you can get. Based on the level of discussion generated here, I'll probably create the voting thread in a few days.