ColinMac, what is happening to the MLB Contest?

There's  no legitimate winner in sight, the entire contest is in shambles, and gets  worse by the day!

Interesting to see what happens when the season ends, and who collects the $3000 first place prize money

Hi! Sorry for the headaches.  Colin's advised me that he's looking into this, and hopefully will have an update soon!  I'm pretty confident it will be all sorted well before season end. :) 

Hi @poppyg, the product team has been made aware of the leaderboard issues and will be working on a solution. Thanks for your patience as we sort this out.

@ColinMac

 I can tell you what all is incorrect (in case it helps). 

The Consensus MLB Leaderboard is correct except it has not voided the Aug 3 5 inning O/U picks. They were only voided in the Leaderboard. In our history, it still shows the record of the picks, even though they were voided. This is fooling some into believing they were not voided, but they were in the Leaderboard.

The Leaderboard is correct except that on Jul 14, it rolled back 2 weeks. I was alerted when I saw that I lost 3800 points overnight without making any picks. I saw that others who had done well in the past 2 weeks had those points taken away and those who had lost points in those 2 weeks had their points restored.

Some have had their scores recently get rolled back to about the beginning of the season. This only happened on the leaderboard, not the Consensus board.

Hope this helps.

One last possible clue. I was in first place in all leagues by far and suddenly I am in 8th place with around 40,000 fewer points. The mollydog shot way up. The fact he shot way up makes me think it might be correct now, as I was surprised how low his score was. Makes no difference to me, but it might be a clue.

@DeaconBlues2525

 Thanks for the details - that always helps!

@debi

 It's the Computer Science Professor in me. lol

@DeaconBlues2525 Congrats on a great season so far.

I guess I'm missing something here because I don't understand, for example how DaBoss80 is ranked #5 overall, but when you look at the breakdown he has negative 81,705 units. He's followed by Theritter18 who supposedly has 19,470 units but if you look at the profile he actually has negative 8,425 units and is in 2,733rd place. This doesn't look like it's a matter of a missed update or two, it's way off. How is Theritter listed in 6th place when drilling down to the detail he's behind 2,733 other players?

@Goobiton

 Thanks, I appreciate that.

See above for my detailed analysis of all that is wrong. During the 2 weeks prior to Jul 14, TheRitter18 lost a lot of points. Those points were restored on Jul 14 when the entire leaderboard dropped all results from the prior 2 weeks (estimate). This did not happen on the Consensus board or our Profile pages. That is why you see that huge difference.

Thanks for the explanation DeaconBlues2525. But I don't get why covers is unable to set it up so it works. it's really too bad they can't simply track results so we're able to see how we're actually doing against others, and so there's some motivation to participate beyond finishing first and collecting whatever the prize is - if there is one. 

Now I see you've disappeared from the rankings completely. I guess I shouldn't be surprised given how convoluted the whole thing is. What's the point of having "overall rankings" that's just a random list? Why even have the contest BS at all?

Hi everyone, thanks again for your patience as we diagnosed the cause of the leaderboard inaccuracies. We found that there existed records for post-season games in the middle of June. After a lot of digging, our product team found issues that defaulted a number of games to post-season games in error. Our product team is currently working on a fix and is aiming to have this resolved before the end of the regular season.

@ColinMac

 Thanks, Colin.

@Goobiton

 The leaderboard is now correct. WOOOOOOOOOOOOOOOOOOOOOOOOOT! Thanks Colin.

Hello everyone, the issue effecting all King of Covers leaderboards has been resolved. Thank you all for reporting this and providing feedback. Cheers to our product team for their hard work in identifying the cause of this issue and working on a fix.

That is amazing - thanks for staying on top of this Colin!