Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

In my particular scenario, the reputation audit says

rep cap was exceeded on 152 days

Shog9's GreaseMonkey says I'm at 148, but it's been documented that there are many discrepancies and inconsistencies in how {Epic} and {Legendary} are calculated.

Regardless, I reached 150 a couple of days ago and I waited the extra few days (as these badges aren't calculated daily, we're told), but I've still yet to receive my {Legendary}.

This was also the case with VonC which got up to 154 (and more) before receiving the badge. Others have been in much worse situations based on anecdotal evidence, with some still waiting for the badge after months of delay, perhaps with no clear explanation.

For the benefit of all, I'd like the {Epic} and {Legendary} badges rules to be further clarified and enforced, but in my localized case, I'd like to know what else do I need to do to get my {Legendary} badge. Because I will do them.

share|improve this question
It shows me at 167 days now and I still don't have mine :( – Joel Coehoorn Aug 27 '10 at 4:16
@Joel: I feel your pain, though obviously in much lesser degree. StackOverflow encourages competition, but this is just straight up unfair. Broken, even. – polygenelubricants Aug 27 '10 at 4:25
I just bountied VonC's question. For the second time. Feel free to close this question as a dupe, make it vanish like Joel's or whatever. Just provide quality authoritative answer to the question, please. Isn't that what we're all about? – polygenelubricants Aug 27 '10 at 4:33
@poly I agree that it seems broken, but you sound almost hysterical; your comments make it seem like you're about 10 seconds away from driving to California and knocking on Jeff's door demanding badges. I'm sure you'll get it; nobody will deny you your rightful Legendary status – Michael Mrozek Aug 27 '10 at 5:08
Actually, I got mine at 161 rep "cap exceeded" and 96 "cap reached". I still have no idea why that particular score triggered that badge. Btw, congrats in advanced for your Legendary badge! You got it in 6 months! It only took me 22 months... ;) – VonC Aug 27 '10 at 6:10
@Joel you got it! (And you, too, Poly :) – Jarrod Dixon Aug 28 '10 at 7:55
@Jarrod: Thank you, thank you, thank you. You don't know how much this means to me. – polygenelubricants Aug 28 '10 at 7:56
@Jarrod - awesome, you rock! – Joel Coehoorn Aug 28 '10 at 14:08
@VonC: well isn't that obvious? 96=6*16, 161, the numbers are symmetric, 161 can be factored as (1+6)*(16+1+6)... The numbers just added up, the time was right! – sehe Oct 25 '11 at 21:48
@sehe: I had forgotten about that question! I am now at 226 (upvotes only) and 373 (at least 200 rep). Can I have another badge? – VonC Oct 26 '11 at 7:32
@VonC: Aw, you just missed the mark for 7*37 vs. 373... I would aim for 329=7*47 vs. 474 (having the added bonus of 7*47 being the prime factors). However, these targets are tough to miss and it will take you at least till 2012-02-04 ... (but that will give you some more time to request the new badge for the occasion :)) – sehe Oct 26 '11 at 7:50
@sehe: darn it! 331 and 463. I missed your mark... On the plus side, it didn't took me as long as you said. Of course, this helped (…), and restored some rep. – VonC Mar 6 '12 at 7:09
up vote 5 down vote accepted

There's an issue with how the badge is calculated - it uses the TargetRepChange field on the votes table to aggregate the total rep gained for a day.

TargetRepChange is a denormalized representation of how much an individual vote is worth to receiving user. For example, an up vote on an answer could record 10 in the field. If the receiving user had reached the rep cap for the day, 0 would be recorded.

Things can get messy when a user's posts are deleted - because TargetRepChange is set when the vote is cast, a deletion on a future day could cause the rep cap to no longer be reached, even if there were more votes garnered.

Your /reputation report does not use this field when summing rep for a day - we rerun all the logic for an accurate report, using the most current ruleset.

So we can fix the data. We haven't done a lot of it yet, because it's a very expensive operation: almost 10 million votes and all the accompanying logic behind them have to be run for a global fix.

But for an individual user, I'm adding integrated adjustment of TargetRepChange when a moderator recalcs a user's rep. I think in the future, we're going to allow users to recalc their own reputation (time-limited, of course :), so you'll be able to help sort out issues on your own.

share|improve this answer
So I do still have more days to go or do I actually deserve it already but the bug makes it not so? What do I have to do to get this before September? – polygenelubricants Aug 28 '10 at 2:17
I'll be working on this tonight and tomorrow, so hopefully you'll get your badge this weekend. Cash would speed this process considerably - how much is your Legendary worth to you? :) – Jarrod Dixon Aug 28 '10 at 3:10
with all that VC money, why not just have one of your servants do it for you? :-D – George Stocker Aug 28 '10 at 12:22

I've posted a similar question before: Possible bug in legendary badge calculation. Jeff marked it Status-Completed at 17 august without notification. Further, the last one who earned the badge on Stackoverflow was Oded. He earned it before 14 august.

Probably Jeff actually changed something at 17 august which caused the legendary badge rewarder to behave differently or to be completely broken.

Jeff is the only one who can reasonably investigate and answer this.

share|improve this answer
Jeff did change something, I believe in response to this premature {Epic}… ; the fix is alluded to in a comment… ; previously, deleted posts still counted toward the badges, but this was then (supposedly) fixed. – polygenelubricants Aug 28 '10 at 3:16

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .