Add a FAQ on what you need to know when posting in Forum Feedback

Forum Help
#1

I personally find it annoying that every time I suggest something, I get directed to meta.discourse.org. To help others to not make unnecessary posts too, I would suggest to add a FAQ to this category on what can and what cannot be changed by Roblox on the DevForum.

Example

What can be changed by Roblox?

  • Category restrictions
  • Moderation system
  • Trust levels
    What cannot be changed by Roblox?
    Core Discourse features, such as the flag system, the way posts work or other stuff. To recommend a change to the core components of Discourse, go to meta.discourse.org.

I have ended up at least 3 times having my post directed to Meta and others would surely like to avoid that too.

5 Likes
#2

There is no reason to do this. Here is what can be changed by ROBLOX:

  • Customization
  • Roles
  • Categories
  • Badges/Trust Level Requirements
  • Settings
  • User Profile

Here is what can’t be changed by ROBLOX:

  • Any functionality of the forum. (The way the forum works.)

I may be leaving a thing or two out, but if I can describe this in one short post, there doesnt need to be a FAQ.

1 Like
#3

But people can ignore those posts if they aren’t pinned.

#4

So? There is no need to make a FAQ because everything on my previous post is common sense to any Discourse user.

I see no issue with someone requesting something and getting a ‘go to meta.discourse.org’. Then, the user will learn if they didn’t know already.

1 Like
#5

Not technically correct; a lot of forum functionality was changed by Roblox lol

This post by @wevetments should (imo) be pinned because it makes it clear to any new user how to identify bugs with Discourse vs Forum

6 Likes
#6

Explain?

Customization is not changing the functionality.
Functionality is:

  • Posting Topics/Replys (And Formatting)
  • All of the Buttons on These (Edit, Flag, Bookmark)
  • The Moderation System Itself (Not how moderators moderate, but the code behind what they do.)
1 Like
#7

Post approval, op-only-reply in bulletin board, following, etc. aren’t customization; they’re plugins.

There’s a lot more plugins (for things like extending TL2 requirements) which, no, aren’t customization.

1 Like
#8

Plugins and forum functionality are two hugely different things.

(If you wish to continue this move to messages.)

#9

I think the point that most people don’t read the guidelines has already been proven, adding more stuff for people to read isn’t going to solve the issue.

This specific issue is one that I personally would consider unsolvable unless you could add a filter to posts before they are released and make a popup saying that it is believed this issue is a discourse one.

#10

We can change anything organizational regarding the forum such as categories and groups and other Discourse settings. We are also fully capable of making plugins and functionality changes (including category posting behavior, how flags work, etc.). The issue is that it is not justifiable for Roblox to use its own engineering resources on the forum for changes that are not Roblox-oriented or specific to our domain.

For example, Post Approval is highly specific to our domain; it’s the largest plugin we have to my knowledge and is critical to keeping categories that engineers look at and use regularly informative and useful.

Something that is too general and not specific enough to our forum might be adding new poll options. You would ask on meta.discourse.org about something like this. Forum bugs are also not our domain unless they’re with a plugin we have developed.

However, if you find a third-party plugin that’s already been built and you think it would solve a significant problem on the forum, you’re welcome to suggest us using it.

1 Like