You make good points but however, lots of people use this forum as a resource more than a showcase. While yes, many people still do like to show their work and receive feedback on it, lots of the community here is built around helping others learn. Many people (such as I) have learned heaps of knowledge from this place, and it may even be what got some people into developing games in the first place! It should be treated as a place to learn and grow your skills. Adding a manual acceptance, whether it be showing your work to get accepted in or applying in some sort of interview, will create a barrier between player and developer. Now you may make the argument of “Well the API documentation and YouTube exists”. While yes, the API documentation is something you can learn lots from, and yes, you can learn from watching YouTube or tutorials, but most of it is usually relegated to one topic or isn’t specific enough for what you want to achieve. In the DevForum, you can easily make a post asking about your problem or error and in a short time, there already is a response that most likely will solve your problem.
Now from here, I’ll be spitting out most of the topics and points other replies already stated out.
The workload on the Roblox staff for manually accepting each application will be sky-high. The sheer total amount of applications will be daunting and will most likely take longer to get accepted than just normally reading topics and getting accepted. The automatic acceptance is a good system since you have the chance to learn from others and become knowledgeable about developing before you get accepted in.
Oh, there are trolls or bots? No problem. Flag the post for deletion and move on with your life, you’re not going to die.
Defending, literally attacked people by those trolls is also not the best option, because, to “avoid” rules I will be called out in private messages with serious accusations, such as being a kid, and something to get rid of Roblox because I am defending someone. Therefore, manual acception should be the best option, mainly because of trollers.
Not a good idea since there has always been a problem with showcasing scripts since everyone has a different way to write scripts (everyone formats code differently) and in order to test code would take quite a bit of time rather than just looking at an image of a build.
The currently marked solution on this topic seems like a joke, I hope you’re not actually thinking the reason for not doing manual acceptance is because of profits…?
The real reason, which multiple product managers and DevRel people have pointed out before, is that Roblox is all about accessibility for creators. A manual acceptance step with weeks/months wait times and arbitrary review processes is totally not in the spirit of Roblox as a platform and inhibits creator engagement.
Sample staff response exemplifying the above: (read rest of the post as well)
cc @blitzahon I recommend not spreading naive “big bad corporation is bad” stories going forward and basing yourself on factual information and staff responses.
You explicitly call out the main reason is that it would be too costly in terms of manpower, and that’s the point I’m addressing. It’s totally off.
Roblox has no issue hiring hundreds of manual moderators (see their moderation system, they have 2000+ manual moderators enlisted to moderate roblox.com). Time or money is not the issue here. The real reason is as I explained above, it’s a conscious product decision not to have manual acceptance on this forum.
Hey folks, thanks for all the responses here. Closing out this old feature request since we will not be implementing this feature request.
We want the forum to be accessible to all creators so that everyone can contribute to and benefit from the categories here, comment on updates, and give us feedback on our creator-facing products. This is entirely unrelated to budgeting.
We acknowledge that there is a need to find content that better aligns with your own interest (e.g. matching your level of skill or area of expertise, not just being fed content in order of last posted). This feedback is well-known internally and we’re thinking about how we could address this better in the future.
I encourage people to file posts on the specific issues you see on the forum along the feature request template: How to post a Feature Request (focusing on the core issues you are seeing, rather than specific proposed solutions like the one in this thread)