So, we’ve just finished investigating what happened. The suspicion was correct, we didn’t credit multiple eliminations. But the good news is that we kept records of all the eliminations, so we were able to find all the multiple ones, and find out who was owed carrots. In total 144 players had multiple knockouts and they’re owed between 1 to 4 extra carrots per player. We’re updated the leaderboard now to reflect the final results, that way we can be sure everything is 100% accurate. The gold, silver and bronze carrots will then be awarded shortly afterwards.
Apologies for the mixup over the multiple knockouts, this is the first time we’ve run a contest based on knockouts and we overlooked the possibility of knocking out more than one player at once. Needless to say we’ve update our system to take this into account, so if we run a similar contest again, it’ll run like clockwork.
Also I realise we had a problem with the leaderboard not updating yesterday. We’re not sure yet if this was on our end or leaderboard.com, the service we used to run the leaderboard. We’re still investigating and will post an update shortly. However whilst the leaderboard wasn’t updating all the carrots were correctly tracked and when we updated the leaderboard this morning, everything was updated properly.
Jacksonteller was the overall winner having knocked out a total of 74 players this weekend, impressive! The gold carrot worth 1 million chips is thoroughly deserved!
Wigolferguy and Baldeagle tied for second (after the multiple knockout adjustment), so we’ve awarded you both half a silver and half a bronze carrot = 200,000 chips.
The rest of the Top 10 players each get a bronze carrot worth 100,000 chips - congratulations!!!
If anyone is interested in what effect the multiple knockout update had on the scores, we’ve got a spreadsheet with a list of all players who weren’t credited the carrots owed to them, and how many:
Ah we found out the reason why the leaderboard jammed and didn’t update. Apparently the leaderboarded.com site has a maximum number of refreshes of the leaderboard, and we hit the maximum. Unfortunately nobody was a round on Sunday to spot the problem which was easily solved by manually updating it. Oh well, better luck next time!