DevForum Etiquette: A comprehensive guideline
Introduction
Disclaimer: This is not as strict as the rules, but if you follow these, you will avoid being mass-flagged by on-lookers at the topic. Please think of this as guidelines/tips/advices rather than fundamentals or rules.
You were linked this topic due to following common reasons:
- Topic was in incorrect category
a. Topic was moveable to correct category
b. Topic was not moveable to correct category - Topic was using redundant tag in title
- Topic is a duplicate(without any new details)
- Topic title was too indescriptive
- Topic is too short in description
- Reply is redundant
Explanation
Topic was in incorrect category
Category: Cool Creations
Most common reason for being in incorrect category is another category being overlooked: #help-and-feedback:cool-creations. If your post was moved to this category, this is due to lack of specific technicality in the post in question. If your post was otherwised moved to any other #help-and-feedback, those categories are designated for technical help and sometimes even discussion, while #development-discussion is arguably more suitable for discussion that has significance: either it is towards developers or the art of development(how people do things, introspections).
Bug Reports / Feature Requests
Do not post bugs in #forum-feedback:forum-bugs, even if the category implies bug, this is more for the meta: It’s for the forum itself, whatever feature is failing to work within the forum.
Do not try to post feature request/bug reports in #development-discussion nor any category except #feature-requests and #bug-reports respectively. These categories are locked for regulars only. If you want to request a feature or report a bug, consider this first: https://www.roblox.com/support
If in doubt whether a bug is identified. Do not attempt to post and ask other users if they are experiencing the same issue. For people who read the bug reports, do not try to add replies that do not add new details to the bug. Avoid duplicates, see Topic is a duplicate.
Alternatively, PM the group with the steps below: Developer engagement team - DevForum | Roblox
- Create a topic in #bulletin-board, including all the details on the instructions of formatting correctly. If you don’t have the templates, check the categories’ pinned topics or ask the DET.
- PM the group as aforementioned and address this topic.
- Now you are playing the waiting game. You can continue developing… unless there was a bug hindering you from that, go do something else like playing video games.
Additionally, this group can be PMed to regarding moderation questions.
Avoid reporting exploits through there though. There’s another group specializing this:
https://devforum.roblox.com/g/Exploit_Reports
Moderations: Assets & Account
Uh oh! Your asset was moderated! You are thinking about posting in #help-and-feedback:art-design-support… but stop right there! Check the Community Rules in first hand before you do that! There might be a clarification that is written somewhere there!
If your assets were unjustifiedly moderated, contact a group on DevForum that handles this:
https://devforum.roblox.com/g/Mod_Review_Requests
Additionally, do not wait for too long to PM them. Assets cannot be reversed later.
For other moderation, as the group’s description has provided, please contact Roblox’s official support page:
In any case, avoid callouts. Report using Roblox’s report features than ranting it on #development-discussion, a very common occurrence in the past.
Topic was using redundant tag in title
Feedback / Showcase
These are redundant, as #help-and-feedback:cool-creations category already implies what the topic is for. Aside of this, sometimes post feature GFX, modeling, etc. into the title tag, but that’s not appealing in appearance. Perhaps you should try using the tags like in this screenshot?
It is also common that users add title tags due to its length. To fill the length, please consider creative approaches as in adding adjectives that fit your creation… or describe the topic in a better way for new users to search for them for future references!
If you have decided to title it “Dragon” and the creation is a red, fiery dragon, do not tag the title. Use a more creative approach such as “A Red, Fiery Dragon”.
Solved
Please do not tag the title with solved in any form of it. Consider using the checkmarker icon which marks a reply for solution of the topic. The topic will be visibly solved when searched; they have a checkmark icon to the side. Use it wisely.
No replies to mark solved but you solved it yourself? Make a reply about it first and then mark it as solution. Don’t worry about being egoistic here. Haha.
Help
As aforementioned in Feedback / Showcase, this is redundant as it is already implied by the categories’ descriptions.
Topic is a duplicate
Search Engines
Use all search engines to your disposal to look for help before you try to make a brand-new post on the forum. These things are most of the time reliable for general questions: For instance, Lua experiences, building techniques, etc. Broad questions should be generally be assessed in search engines first before you post, in contrast to specific questions, which are usually very technical. Always consider this first before posting!
Topic title was too indescriptive
“Help!”
You’re asking for help, but never specify exactly what you’re asking for. This leaves many users to check, but get your answer answered a lot later. Try to use a descriptive title next time specifying the problem or issue as much as you can, don’t leave this out!
For instance, do not use “Help with script” in #help-and-feedback:scripting-support. It is way too vague compared to “Table indexes being incorrect upon loop”. In my comments, I believe the common issue to this is due to a lack of jargons that are applicable for new users; they are still learning and adapting to the ethiquette.
Topic is too short in description
Shotgun posting
Avoid this at all cost. If you want to not be flagged, please consider planning your post as you write. Shotgun posting means a post is a stub; it does not have enough information for developers on the forum to find a solution. It’s like a math equation with waaay too many solutions.
Scenario 1
Some scripters are looking for help and they only vaguely stated something, no code and nothing else is added. It is fully understandable that the user is completely new to the ethiquette. It is usually helpful to PM or reply about the insufficient information altogether. If it doesn’t help, flag it.
Scenario 2
Some users genuinely look for general help with anything in one area. The question is waaay too broad with the amount of different ways the user can use to apply for a solution. Like I previously mentioned, it is like a math equation with many solutions. Depending on the method, one solution may be sufficient for them. In this case, ask the OP(original poster) about what method they were looking for specifically. For the posters on the forum, please consider describing the method or visually draw/project it in any media.
Reply is redundant
Good work!
Frequently, this is a common mistake on the forum. Avoid replying short and insignificant comments. There’s a “like” functionality that is better than a reply and helps mitigating spam. #updates frequently get swarmed by these and followed by #help-and-feedback:cool-creations in quantity.
A specific comment about the work/update is more acceptable that the short replies. They give their own opinion while adding up questions to anything.
Questions?
Feel free to PM @Operatik if in doubt of anything. We will also update this post if there’s anything new to add to the guideline.