Automated verification badge wave failing to detect all eligible experience contributors

There appears to be a bug in the automated logic used to distribute the Verification Badge to experience contributors. I am a developer for Tiny Wheels. Another developer on this project received the verification badge in the most recent wave. However, despite being part of the same group payout structure and meeting all individual account requirements, my account was skipped.

  • I have over 10% game earnings payout (not group payout) and the game has >1M playtime hours in the last 90 days (detailed info in private content)
  • I’m ID Verified and have 2FA (with authenticator app) on my account
  • I have not changed my name recently
  • I’ve been active in the last 180 days

Expected behavior

Since the game itself is clearly eligible (given that the other dev was verified), I am ID verified and have 2FA set up as required with an authenticator app, I was expecting to be included in this wave

A private message is associated with this bug report

12 Likes

I am experiencing the same issue. I am the lead developer of our game Obby Champion.

I have a 10% game payout, yet the system did not grant me the badge. I also have ID verification completed and 2FA enabled on my account. No recent username/display name changes either.

5 Likes

The same thing happened to me, I meet all the requirements yet I was not verified roblox needs to look into the issue

7 Likes

Same here aswell, the Main Problem u wont know if Ur Account is eligible or not so u wont know where the problem is

1 Like

Same issue. My group has been verified for ages yet my account isn’t. It doesn’t make sense to me.

1 Like

Same for me, I’m sure my account is egible

2 Likes

That’s really odd, over at verified badge faq, they list the following criteria (aside from the precise developer / ugc creator / public figure requirements):

  • being ID verified
  • having authenticator app 2FA set up on your account: email doesn’t work, but the “very secure” hardware security keys do not seem to be necessary
  • being active in the last 180 days

Assuming you ticked all these boxes, there’s no reason for only the group to get verified, skipping your account. Unless they check for other things that they do not publicly mention - the situation that I and many others may be in.

The only hidden criteria I could think about is a player’s past bans/warnings. Although I have not had a single one of those in over 2 years, and before that there was only a minor thing that I received a warning for.

2 Likes

I haven’t had any significant warnings aside from one time uploading a decal that wasn’t allowed (in 2018). Everything else has been appealed and removed, and even then they were insignificant. I meet all of the requirements and I am the owner/holder of the group and have been since its inception.

I’m so confused

1 Like

I failed to recieve it as well while the group/group owner has recieved it both. I meet all criteria.

1 Like

I am also in the same situation even though I meet the requirements.

1 Like

Also people are buying and selling the badge while the people that are trying to get it through development and other stuff aren’t getting it.

3 Likes

I also had the same issue. I had 10% on an eligible experience I work for, but did not recieve the badge.

2 Likes

To be fair, there probably isn’t much that can be done about people selling badges. Developers and companies buy percentages of other games, and it would take a lot of evidence for somebody to be exposed that they are, in fact, selling the badge, and not accepting a perfectly fine business offer.

It is a bit of a shame though that some of the people who are qualified to receive the badge legitimately get skipped :melting_face:

4 Likes

I posted a reply in the private thread attached to this bug report, hoping a staff member might see it :slightly_smiling_face:

Yeah, I’m also eligible but it keeps skipping me :pray:. Roblox gotta fix this system

As I have just gotten verified, this issue can be considered fixed. I would assume this was an automated action, although if the staff team had any implication in this, thank you!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.