The Seta00 user has crashed.
Join Date: Jan 2010
Recently I've seen the number of unnecessary posts in the Scripting Help section grow fast, and I'm writing this hoping that it will guide users before posting something in Scripting Help, and help them to solve their problems.
The first thing that happens to motivate a new thread: A doubt.
Beyond this point, I'm assuming you've got one, and as everybody, you want it answered.
Tips for new users:
If you created an account in the forum just to solve your problem, you should get to know the forum rules before posting.
- Read the sticky posts, they are stickys for a reason, and are made to help you.
- Explore the forums, learn the layout and find the right places to post.
If your doubt is related to an existing plugin:
If your doubt is related to something you're developing:
- Go to the plugin thread (use Plugin Search), and read the changelog. If someone got the same question answered and it somehow got into the code, chances it will be in the changelog are high.
- Remember: if you want some feature added, the plugin thread is the place to request it, not Scripting Help
- If the plugin's author doesn't maintain a changelog, read the plugin thread looking for questions/answers that may help you.
- If your question hasn't been posted or answered, post it on the plugin thread, and wait for help. Do NOT bump the thread, wait two weeks for your answer. If you haven't got any answer in two weeks, download it's source, and go to the next section. If you can't script, use the Suggestions / Requests forum, and remember to follow this guide.
- If it's a bug, isolate it, use AMXx debugging capabilities for that. If debug mode isn't helping you, comment pieces of your code until you find your problem.
- If it's a feature you're trying to implement, search, search, and search a little more about the matter.
- Whatever you're trying to do, there's something about it on this forum.
- Search on Code Snippets/Tutorials
- Search on Scripting Help
- Refine your search terms based on previous results, and search again
After all, you couldn't find your answer. Sometimes this can happen, and now is the time for you to think about your post.
What you must know before posting:
- This is an English forum.
- If you're posting on Scripting Help, you must have a script.
- If you're not a coder, don't post it before understanding at least the basics of scripting. Maybe you'll find your answer in the process of learning.
The post step-by-step:
- Think on a descriptive and interesting title. Titles like "please help" or "i have some bugs" make possible helpers go away without even reading your post.
- Describe your problem clearly. Provide steps to replicate it.
- Write in plain English. You're not on an istnt mssngr, take time to make sure your post is clear. If you have problems with English, and have to use an automatic translator, at least read and understand it. If you can't understand the translated text, something is wrong. If you think your text wont be able to tell us enough information, post it on the Multilingual Forum, and request someone to post it in English here.
- Provide code. No matter how great your explanation is, nothing explains your code better than itself. As said on the previous section, isolate your problem, post the snippet, and attach the full code.
- If you have a clue of where is your problem, or a possible solution, post it, information is never too much as long as it stays on-topic.
- If you used code from another plugin, post a link to it. If you followed a tutorial from the Code Snippets/Tutorials Section, post a link to it. If you got any messages related to your problem on the server console, post it.
- If your problem is causing any visual feedback, post a screenshot - but remember, while text is a form of visual feedback, you don't need to post screenshots if you can simply paste it on the post.
- Remember: this is a public forum, and we are spending our time helping you for free.
Now that you made your post following these steps, it's time to wait for replies. The following text is meant not only for the post creator, but also to all repliers.
- If you're the post author, and have additional information on the problem, post it on a reply, AND update the original post. It's important to have all the critical information in one delimited location, making the life of your helper easier.
- If you have a possible solution, explain it clearly or provide the code. If you tested your solution, say you did it and provide test results.
- If you have something to say, triple-check if it's needed. Don't start an off topic conversation in the middle of a help request thread.
- If someone made an error, correct it without being rude. Corrections are meant to help, not humiliate.
- If you made an error and saw it after posting, use the edit function, there's no need to post a new reply correcting the old one.
- If the problem is solved, keep your reply for yourself. That way you let the new problems have their space on the forum.
- If no one replied to your post, wait 2 weeks before bumping it, maybe this time the right person will read your post.
For the ones that still don't know what is non-Steam:
Non-Steam is a hacked version of any game that uses the Steam Platform for distribution, activation and/or online play.
Now read this: Final word about No-Steam!
So, If you don't have Steam copy, don't expect support.
I hope this will help you guys to find the answers to your questions. If I made any mistake or typo, feel free to correct me.
Last edited by Seta00; 01-15-2011 at 20:18.
Reason: Changed some minor things before bumping.