Remove New Members' ability to reply in bug reports

What people want to feel is inconsequential. They are either helping a bug be solved or are making it harder to find the former. If they are unable to prevent themselves from contributing to the latter, then they should refrain from posting at all until they are able to contribute constructively.


As much as we’d all like for this to happen, it’s unlikely. I personally think restricting new members in bug reports would be extremely beneficial, as compared to the current system of:

  • Bug report posted
  • Spammed with “its happening for me too”
  • Post locked

A secondary option would be allowing sages/CPA/whoever just instantly flag & hide nonconstructive posts on these threads.

People might have important or relevant information to share, such as steps to reproduce the bug, so locking the thread can be detrimental.

So like the post. It gives you the satisfaction of leaving input on the thread with 100% less clutter, guaranteed or your money back!

1 Like

I too, am a new member. I don’t think excluding us is going to help. I’ve feel, well, discriminated. You don’t have to reply to everything and I don’t. The Dev forum already doesn’t allow most of its members to reply, so I think we’re good. If something was to happen then it’d be a zero strike warning.


I’m a new member, and i always try to be someone honest and never lie.

My suggestion: Make another forum: Public bug reports and the normal bug reports.

Every new member can post in there until a mod selects you to post in bug reports, but they can’t post on BUG REPORTS .

Some mods will be able to select a player to post in the BUG REPORTS forum with the other people who takes this forum more seriously, leaving other new members who as said Elliott, they just do:

They will post on PUBLIC BUG REPORTS.

I hope moderators/admins or anybody else who can fix something look this. Thanks for reading

Maybe instead of just restricting new members ability to reply in bug reports, increase the character limit for bug reports (maybe to around 100) This would hopefully keep people from just stating can confirm unless they have something to actually contribute


I think it’s been proven that character limits have very little effect other than lowering the quality of the reply.

Additionally, even if that wasn’t an issue, it’s not hard to extend a meaningless reply to 100 characters:


Instead of all-or-nothing, there’s smarter things we can do to reduce noise on high-traffic topics.

For example, we’re trying out a thing here where TL2+ has the permissions to reply to top-level (uncategorized) platform feedback topics, and I moved this one there:

I think doing this is much less invasive on normal forum usage than fully restricting TL1 from replying to all bug reports. We just need to watch out with the robloxcritical ones and other high-traffic ones.


I don’t agree with this. We should be able to post in bug reports, from me a New Member.

Ok let’s get serious now,

Why do I not agree?

  1. Some other people may not know the bug.

  2. Roblox should be accepting all bug reports, and delete spammy ones.

  3. Is it really that hard to just accept it? No, just go with it.

  4. Bugs are serious, not silly. I can guarantee you 99% are real, serious ones.

  5. Cricital Bugs are even more serious, so I can guarantee you 99.9% of those are real, super serious.

  6. This post won’t help the community at all, please stop. (Not saying I’m a mod.)

This won’t keep people from making useless topics, they can still spam topic till they reach 100 or over, maybe 250 - 500? That is much bigger, and copy pasting a fake bug won’t work either because that takes a long time to actually write it, so they likely give up.

1 Like

Why is confirming a bug report deemed a bad thing? It’s an easy way for newer members of the community to get their voices out there and also lets others know that the bug is not a hoax/faux call.

1 Like

If you have no new information to add, and you do not provide additional use cases for why the bug is important for you to have fixed, you should put a Like on the post rather than replying, to keep the bug report concise. Otherwise it makes things harder to get through for Roblox engineers and developers who have a stake in the bug being fixed.

1 Like

This isn’t a bug report, it’s a discussion, I’m pretty sure that as long as I’m staying on topic, I’m following the regime of a discussion.

Yes… I was responding to the question you put in your previous post. :stuck_out_tongue:


Oh, right, I thought I was being reprimanded. Sorry, that’s completely my fault. However, is there not something else the forum could put in place in order to let New Members contribute to something? Maybe not just bug reports but something like for all reports, i.e: bug reports - vouch button to let Roblox know how widespread the issue is, studio features - vouch button to let Roblox know what features are wanted the most etc.

We have Likes as a rough statistic for that. Liking = agreeing to or respecting a post. Is there a reason why you would want another button over the Like button?

1 Like

The like button is a general case idea for “good post”, having specific buttons helps reduce this margin of “do the community think it’s a good post, or do they actually want this feature?”. It’d be kind of like retweeting but a bit less obnoxious. Maybe add their own reasons so, if Roblox wanted to, they could read other users’ opinions on the matter without it clogging up or bumping the thread, pushing others out the way.

1 Like

There are already alot of restrictions on new members. What about the new members who actually have something important that they need to report? Also, FYI the only way to become Regular is to do bug reports, so you are taking away our promotion.

Not bug reports only. Also feature requests. You don’t need to specifically reply to existing bug reports, you can make your own provided one doesn’t already exist.

I am honestly sick of “can confirm” replies and it makes it very hard to read an entire thread.

1 Like


Because they are (to paraphrase the founders of Discourse) new, they are sandboxed to protect themselves and the full community from spam and bad content.

I’m not going to repeat incapz’s point in response to your other argument.


The post approval team already has alot of work. Throwing this task on them would mean they would need to expand their very selective team of trusted members to a rushed team of people that might not be so trustworthy. I can personally name a few mobile bugs that could help mobile players if I caught them on video. But adding extra security is not the way to go. Instead we can just flag the post, as that is the purpose of flaging.

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