Settings and activity
1 result found
-
25 votes
Thank you for your detailed submission and articulating the usefulness of the badge for game developers. We agree with the sentiment and additional context can be found in the deprecation announcement. You are correct that there was an increase in requests to verify organizations. This process is also used to gain access to other features such as Drops campaigns and game analytics. Product updates to limit requests for a global badge and remove confusion, such as enabling the badge only on a matching category as you mention, will take considerable time while continuing to block new developers from using these organization features. This change will reestablish the 1-week SLA for organization requests and an improved implementation of the game developer badge can be considered in the future while we enable new game developers to onboard.
An error occurred while saving the comment 
LordPhrozen
supported this idea
·
I vote #2 Here.
The badge has been incredibly helpful to us indies who have a game *still* in development, as we engage with creators, their communities, etc. The badge has come up in chat many times, and provided us with legitimacy instead of skepticism.
Having it ONLY in the category we made, is... better than nothing I suppose. And does benefit teams communicating with players playing their game. But for small indie studios, with an in-dev title, you're taking away a great tool from us, and a great tool for creators, and their chat, to verify claims being made.