- Game Name
- N/A
- Anticheat
- N/A
- How long you been coding/hacking?
- 7 years
- Coding Language
- N/A
Most Important
99% of questions are answered in the Beginner's Guide, do it before asking a question.
If you ask a question that is answered by doing the Beginner's Guide, you're a garbage farmer.
No Hack Requests. Post in the correct section. Search the forum first. Read the rules.
How to make a good post:
We want to answer your question!
But we don't want to help lazy, immature or stupid people.
Hackers have a reputation for meeting simple questions with what looks like hostility or arrogance. It sometimes looks like we're reflexively rude to newbies and the ignorant. But this isn't really true.
People who do not do their homework before asking questions are lazy. We do not respect lazy people.
If you post a good question, you will get an answer.
Blame yourself before blaming anything else - 99% of problems are user error
Before You Ask
Describe the goal, not the step
What are you trying to do, and why are you trying to do it? You might be doing it 100% wrong.
When you ask
While you ask questions make sure you take care of the following:
If at all possible, provide a way to reproduce the problem in a controlled environment.
Add the source code of where your problem is
Don't ask others to debug your broken code without giving a hint what sort of problem they should be searching for. Posting a few hundred lines of code, saying "it doesn't work", will get you ignored. Posting a dozen lines of code, saying "after line 7 I was expecting to see <x>, but <y> occurred instead" is much more likely to get you a response.
source https://www.catb.org/esr/faqs/smart-questions.html
99% of questions are answered in the Beginner's Guide, do it before asking a question.
If you ask a question that is answered by doing the Beginner's Guide, you're a garbage farmer.
No Hack Requests. Post in the correct section. Search the forum first. Read the rules.
How to make a good post:
- Thread title must be descriptive
- Write in clear, grammatical, correctly-spelled language
- No 1 sentence posts, use full sentences
- Fill out the form correctly
- Tell us the game name & coding language
- Post everything we need to know to help you
- Ask specific questions, be descriptive
- Post errors, line numbers & screenshots
- Post all code snippets using code tags
- If it's a large project, zip it up and attach it
We want to answer your question!
But we don't want to help lazy, immature or stupid people.
Hackers have a reputation for meeting simple questions with what looks like hostility or arrogance. It sometimes looks like we're reflexively rude to newbies and the ignorant. But this isn't really true.
People who do not do their homework before asking questions are lazy. We do not respect lazy people.
If you post a good question, you will get an answer.
Blame yourself before blaming anything else - 99% of problems are user error
Before You Ask
- Search the forum
- Look up the topic in our guides
- Read the documentation
- Try to find an answer by inspection or experimentation.
- Try to find an answer by reading the source code.
- Describe the symptoms of your problem or bug carefully and clearly.
- Describe the environment in which it occurs (machine, OS, application, whatever).
- Describe the research you did to try and understand the problem before you asked the question.
- Describe the diagnostic steps you took to try and pin down the problem yourself before you asked the question.
- Describe any possibly relevant recent changes in your computer or software configuration.
- If at all possible, provide a way to reproduce the problem in a controlled environment.
Describe the goal, not the step
What are you trying to do, and why are you trying to do it? You might be doing it 100% wrong.
When you ask
While you ask questions make sure you take care of the following:
- Describe your problem as much as possible, with much words etc
- Describe the symptoms of your problem or bug carefully and clearly.
- Describe the environment in which it occurs (machine, OS, application, whatever). Provide your vendor's distribution and release level
- Describe the research you did to try and understand the problem before you asked the question.
- Describe the diagnostic steps you took to try and pin down the problem yourself before you asked the question.
- Describe any possibly relevant recent changes in your computer or software configuration.
If at all possible, provide a way to reproduce the problem in a controlled environment.
Add the source code of where your problem is
Don't ask others to debug your broken code without giving a hint what sort of problem they should be searching for. Posting a few hundred lines of code, saying "it doesn't work", will get you ignored. Posting a dozen lines of code, saying "after line 7 I was expecting to see <x>, but <y> occurred instead" is much more likely to get you a response.
source https://www.catb.org/esr/faqs/smart-questions.html
Last edited: