Allow members respond to Feature requests in Platform feedback

Users who are more experienced on the Devforums are granted privileges for their dedication to improving its quality and making Roblox a better place. I do not understand your political comparison there.

There are no categories locked away, almost all important ones have a post approval system. The ones that don’t are unnecessary and merely privileges, not rights.

There is not any kind of prejudice towards members at all. Remember that Discourse (the software this forum uses) has a concept of trust levels. "Visitor, “Member”, “Regular”, “Editor”, and “Leader” (as they are called here) are trust levels. Visitor is TL0, Member is TL1, Regular is TL2, Editor is TL3, and Leader is TL4. The higher trust level the more stuff you can do. Members have a lower trust level, so they are just not trusted with more access to the forum yet. An approval system was necessary; otherwise the newer ones making mistakes (as we all do; we’re humans therefore imperfect) would hurt the browsing experience for other readers, and most importantly, Roblox engineers, since they are the ones actively looking at #platform-feedback and taking feature requests into consideration and fixing bug reports that get reported.

If there wasn’t an approval system, the less knowledgeable members (which unfortunately is a lot, like, a lot) would just post garbage on that category. This has been seen in #development-discussion and #resources, but I guess that is expected. Or, they would post feature requests with only a proposed solution and no use cases, or post bug reports without repros which don’t help engineers at all with considering why a feature should be added or how to fix a certain bug when they don’t even know how to get it to happen for themselves.


Umm… no. We don’t want another influx of irrelevant and/or garbage replies flooding Platform feedback. Plus regulars are more trusted to file quality feature requests, that follow the correct instructions and ect. Therefore there’s really no need to reply to a feature request when the feature request itself has been provided.

As a disclaimer, I obviously don’t speak for DevRel or anyone but myself. But, I’m in constant communication with the Community Sages and was a member of the Community Post Approval team for most of its lifespan. As a result, I have a decent amount of insight into this discussion that nobody else has had so far.

I can get more into it if you want, but the gist is that the signal to noise ratio would be too high if members were given unrestricted reply access to feature requests. We found that members were very quick to grasp what was required in bug reports, but we also found that they often reported bugs that weren’t real. As a compromise, members were given permission to post replies on bug reports with no restriction, but not allowed to make topics to prevent not-bugs from being posted. The same wasn’t true of feature requests, so that compromise couldn’t be made.

In case you were wondering, we were getting over a thousand posts into Post Approval a month by the end of the program. The fact that the badge was only awarded to 600 people across the entire program’s existence should hopefully be informative.

This is a relic from back when the forum was effectively a private club – Lounge should probably be deleted, and it would never have come into existence under the current forum’s leadership.


If a person is experienced aren’t they supposed to get more stuff???

1 Like

While I do agree that replies to feature requests should be unlocked (at least until new system comes in place, I’m not THAT patient to wait for over a month), I don’t think that making new topics in PF and opening Lounge to members is a good idea. A lot of people would post bugs in their code to engine bugs, and there’s kind of a special atmosphere in Lounge that I don’t want to be ruined.
Since even discussion was fully unlocked to members, I see no point in feature requests’ replies to be locked.

1 Like

You used to never be allowed to post into those categories as a new member. I was a new member for nearly a year.

I was paitent and got promoted because I had proven I could be trusted to contribute.

Maybe if you were paitent, you’d be promoted too?

I said that I’m not patient enough to wait for a new PA replacement, not the original PA queque length.

Roblox engineering creates and manages plugins, not Sages anymore. Just happened to be that sages were contracted to make a couple of them before.


Forum Feedback is for feature requests and bug reports for the Developer Forum so these address Developer Relations. This part of your response here is not desirable – let people give their opinion.


I don’t see what was wrong with the post approval system? I mean, Roblox makes a point to say that to become a regular; you must prove that you’re capable of creating well-made, constructive topics and discussion. How are we supposed to prove we’re capable of doing that if Members can barely post on the forum at all?


This is something we’ve gone over a number of times in threads related to the removal of Community Post Approval. If you’d like a summary:

  • Does not scale well. PA is a manual process and we had to sort through hundreds of messages every now and again. Largest backlog I’ve helped handle is 500+ messages.

  • Mentally exhausting. There was no quota to fulfill and if we weren’t constantly on the ball, then the inbox would fill right up and we’d have to go through all those requests sooner or later. CPA was comprised of volunteers. We don’t get paid to go through that inbox, we do it because we wanted to.

  • It’s better if paid staff handle these kinds of processes while encouraging us developers to focus on our own development and activities, not to cast away several hours digging through that inbox. Topping it off with impatience and negative language both on and off the forum for not going through the inbox made those hourly trade offs not too worth it.

There was enough wrong with PA. Change was requested and we volunteers followed up on our end. Developer Relations has not.

For your specific concern, please check out other threads discussing the removal of post approval and related responses about the mental burden it placed upon us.


I suppose that makes things more clear.

Is there any plans in the future for a more efficent / less mentally-draining PA system or is this going to be a permanent change?

That’s a question for Developer Relations. We cut our ties with the process and it’s no longer our problem nor something we’re worrying about.


tl1 users shouldn’t be able to do it on their own as it would result in chaos. The lack of communication from devrel is severely disheartening but there is still hope that we will get any response from them.

1 Like

Good concept, bad attempt to fix it. You make it seem like everyone who is Regular are “entitled” and anyone who faces your post is “evil”, but that’s not true. Yes, they should be open but fighting like my parents (lol) isn’t really gonna fix it.

What is the point of ranks anyways?

Regulars don’t use PA (Post Approval, which is gone) when they rank up. They also get access to #lounge.

Let’s say you look at someone’s rank and sees that it is Regular. They will think, “Oh, so that must mean they did a lot of contributions,” since to rank up to Regular, you needed to use PA a lot. It doesn’t matter about stats. Everybody gets this wrong for some reason.

I trying to say that why are people valued on ranks, I mean it so apparent, if a Regular makes a recruitment post everyone goes with that person.

It used to work like this. There was a major spam issue in the category, which is a big issue since the category is meant to be a resource to Roblox engineers and product to give a slice of what the developer community and userbase want from the platform.