Sk1nyNerd
2013-05-09 18:41:07
Hey everyone! This guide will show you how to properly tell a Scripter about a problem you experience while using their Script.
It'll give a three step procedure on what to do so you can get back to botting ASAP.
If their isn't a problem and the script runs flawless for you, write it in the thread!!! :D There is no worse feeling then looking at your thread and only seeing people post problems and nothing good. Scripting is hard so give credit for the effort! Doing so will also increase the Reputation of the Scripter as people read through the thread and see that it is a good Script. Although Reputation may mean nothing to you, it means a lot to them as they continue to gain experience and make their path. :biggrin:
Now! If you do find an error in the script:
1) If the script doesn't compile, or run, that means there is an error in the script that can be found in the debugging box (see below picture). If the error displays something like
C:\Users\[urname]\[filelocation]\
you may not have something installed that you should to run that script. Often Scripters will put the links to find the essential files you need on the front page or tell you what files you need. If not, then it is okay to ask where the file can be found after you try finding it yourself.
A syntax error means there is a problem with the syntax of the code. This could mean two things. 1) you did not input info where need or 2) the scripter made an error somewhere in the script. If Simba brings you to the error take a look and see what it is, something simple try to look it up or fix it! Simba is a learning community :). Even so, you should report the problem so they can fix it and others don't experience it.
2) Take a screen shot of the Clients window AND a screen shot of the debugging box. Often Scripters will write messages to themselves or for you to see that notify the status of the script. Sometimes these display that something went wrong. Why do you need to include this? It will help the Scripter pinpoint the problem. Here is a picture I found in c0h3n's THE beginner's Simba Tutorial.
3) Now that you have a picture you need to describe the problem. To do this requires great detail. The popular "this script doesn't work" is not helpful to the Scripter WHAT SO EVER. If the script missclicks, tell where it missed clicked. If the script is just standing still, give it a minute. Still standing still? Report what it was doing before it stopped working properly. If the debugging box doesnt say what procedure the script was in report what procedure the script was in. Get the idea? What will doing these steps do? Just like above, they will help the scripter pinpoint the problem so they can fix it fast and get you on your way.
These three steps are very essential to report a scripts bug/error. They demonstrate a logical user and not someone who is there to leech therefore encouraging the user to give a friendly response and fix that error.
Other things to keep in mind are to give the script a few tries before going straight to the thread. That way you might find more errors and don't cloug up the thread. Also post what version of the script you were using for clarification.
Give the scripter suggestions on how to improve the script or compliment them on a job well done. The script was designed for your use so if you don't like something, suggest something else to improve it and accomandate the community.
Thanks :)
It'll give a three step procedure on what to do so you can get back to botting ASAP.
If their isn't a problem and the script runs flawless for you, write it in the thread!!! :D There is no worse feeling then looking at your thread and only seeing people post problems and nothing good. Scripting is hard so give credit for the effort! Doing so will also increase the Reputation of the Scripter as people read through the thread and see that it is a good Script. Although Reputation may mean nothing to you, it means a lot to them as they continue to gain experience and make their path. :biggrin:
Now! If you do find an error in the script:
1) If the script doesn't compile, or run, that means there is an error in the script that can be found in the debugging box (see below picture). If the error displays something like
C:\Users\[urname]\[filelocation]\
you may not have something installed that you should to run that script. Often Scripters will put the links to find the essential files you need on the front page or tell you what files you need. If not, then it is okay to ask where the file can be found after you try finding it yourself.
A syntax error means there is a problem with the syntax of the code. This could mean two things. 1) you did not input info where need or 2) the scripter made an error somewhere in the script. If Simba brings you to the error take a look and see what it is, something simple try to look it up or fix it! Simba is a learning community :). Even so, you should report the problem so they can fix it and others don't experience it.
2) Take a screen shot of the Clients window AND a screen shot of the debugging box. Often Scripters will write messages to themselves or for you to see that notify the status of the script. Sometimes these display that something went wrong. Why do you need to include this? It will help the Scripter pinpoint the problem. Here is a picture I found in c0h3n's THE beginner's Simba Tutorial.
[ATTACH=CONFIG]21168[/ATTACH]
If the debugging box goes blank when you start the script that is not an error! that is just a function used to clean up what is being displayed.
If the debugging box goes blank when you start the script that is not an error! that is just a function used to clean up what is being displayed.
3) Now that you have a picture you need to describe the problem. To do this requires great detail. The popular "this script doesn't work" is not helpful to the Scripter WHAT SO EVER. If the script missclicks, tell where it missed clicked. If the script is just standing still, give it a minute. Still standing still? Report what it was doing before it stopped working properly. If the debugging box doesnt say what procedure the script was in report what procedure the script was in. Get the idea? What will doing these steps do? Just like above, they will help the scripter pinpoint the problem so they can fix it fast and get you on your way.
These three steps are very essential to report a scripts bug/error. They demonstrate a logical user and not someone who is there to leech therefore encouraging the user to give a friendly response and fix that error.
Other things to keep in mind are to give the script a few tries before going straight to the thread. That way you might find more errors and don't cloug up the thread. Also post what version of the script you were using for clarification.
Give the scripter suggestions on how to improve the script or compliment them on a job well done. The script was designed for your use so if you don't like something, suggest something else to improve it and accomandate the community.
Thanks :)