Over the past few months, I’ve seen many posts that are bad practice or straight-up spam. I’m going to talk about each section briefly, and what you shouldn’t and should be doing. Keep in mind that I might get some things wrong, and correct me if I do:
Basic forum knowledge
1. Use google and the search bar before making a thread
2. Don’t make a thread in an instant if you run into a problem
3. Refrain from using emojis in your title
4. No clickbait titles
5. Don’t delete your post once it’s solved
6. Don’t make duplicate threads, no matter the situation
7. Don’t reply “Thank you for helping”, that’s what the like button is for
8. Don’t post for likes
9. Don’t repeat posts
I’ve seen this a lot, especially in the announcement categories, where people just say “OMG THANK YOU FOR THIS” when clearly 100 other people said it.
Scripting Support
I’m going to start with the most corrupted category of all, scripting support.
1. Don’t post screenshots of code
This one is very self-explanatory: if you post screenshots of code, it is much harder to debug your code, because instead of copy and pasting, we have to type some 100 lines out.
2. Don’t bump your threads
Bumping your thread is against the rules. Stop replying to your own post, edit the OP instead.
3. Don’t make spoon feed topics
By far the biggest problem of all. People just post their code and expect us to fix it. It doesn’t work like that, although, simpler solutions could be “spoon-fed” because there is just one spelling error, bigger problems, like “How to make a piggy game”, should not be spoon feed topics. Instead, you should try it out, and any problems you encounter shall you post in script support, regarding the fact that we’re here to guide you, not give you answers.
4. Stop blaming people for not reading your post
Although sometimes they don’t read your actual problem, most of the time they do. You might think your post makes a lot of sense, it does, for you only. But some other people might not understand. You might want to get your problem over with as fast as possible, but having a vague, unexplained thread will worsen matters.
5. Don’t reply if you don’t know the answer
If you don’t know the answer, refrain from replying to minimize post bloat. No one wants to read false posts. If you accidentally post something, there is always the delete button
Other feedback Categories
1. Use Cool-Creations for feedback
Building support and art design support is used for problems, while cool creations is used for feedback, there is a clear difference. This issue is getting better but still happens.
2. Code review is for reviewing code only
Don’t put scripts that don’t work in this category, that’s what scripting support is for. Code review is for already working code that you think can use some editing for efficiency
3. Use game design support for problems, support, or other things regarding development
I’ve still seen some people posting in scripting support building support, and other support categories not knowing it’s the wrong category to. Posts such as “Are syringe images allowed on roblox” does not belong in art design support, but game design support.
Recruitment categories
1. Please use proper capitalization in your portfolio titles
I’ve seen a lot of portfolio titles like:
[for hire] gfx designer for hire
Properly capitalize it:
[For Hire] GFX Designer for Hire
2. Don’t say “Experienced” and whatnot in your portfolio titles
These should be said in the description of your thread.
3. Don’t make threads in portfolios if you don’t have much experience
This one will be a bit harsh on some people, but bear with me. People who make portfolios before even half a year of expertise have almost no skill that that subject. not to be rude, but, it’s true. Unless you have enough experience, don’t post in portfolios.
Here’s an example of a good portfolio:
4. Recruitment threads should be well explained and pre planned
Plan what you are going to make before making a recruitment thread. Don’t just say:
Hi, we’re so and so studios, and we are hiring a scripter for our game
Explain it well, here is an example of a good recruitment thread:
Resources
1. Don’t just post models
2. Make sure that your resource has not been made before, and if it has, make sure it is better
3. Make sure your resource is well explained
Here are some threads regarding the resources category:
Hopefully, this thread can change how the forum is run.
Thank you for reading!
