Troubleshooting:

 

Banking isn't working - Eg: the script fails to withdraw items from the bank or it seems to open and close the bank over and over

Try this: Move everything that might be needed by the script (food, rings, items, etc) to the VERY TOP OF THE BANK. This means that if you open your bank with your scrollbar at the very top, all the items should be in the first two rows. If you run the script and it needs to go scrolling up and down your bank, fix it.

Explanation: Banking problems are not always associated with the script. The client (OSBot v1.7.78 at the time of writing), has some glitches in the banking method that causes it to fail to scroll to an item.

 

Ran the script, but nothing shows up

Try this: Restart the client.

Explanation: Rarely, the OSBot client will mess up, and refuse to start a script. Look at the OSBot log. If it does not say "Script started: FOO", then the problem is with the client. If the script does start but doesn't get past your GUI, then post a screenshot of your GUI in your bug report so that others can see what's wrong.

 

Script doesn't show up

Try this: Just wait for a while. 10 minutes, 1 hour. Also check your subscription.

Explanation: Sometimes, the bot server might be having technical difficulties. (It reboots itself every once in a while as well). If scripts don't show up, it's most likely a problem with the bot server. Additionally, check your subscriptions to make sure that you are indeed still subscribed to the script (if it's paid).

 

I GOT BANNED

Try this: Learn to accept that fact. You're botting.

Explanation: None needed.

 

I'll keep posting as time goes on and I think of more. Feel free to post your own.

 

Think before you post:

 

Honestly people, please think before you post something on a thread. Read the other posts, use your common sense. Don't just start posting the second you see something wrong with a script. I know some of you find it hard to accept this fact, but it might be your fault for not setting up the script correctly. Every script that goes into the SDN must be accompanied by a 6 hour proggy, or be tested by a selection of script testers.

 

Please don't make posts like "THIS SCRIPT IS BROKEN FIX PLS." Honestly, what is the use of that? Why waste your time posting if you're just going to say that? At least provide some detail about how the script is broken, so that the scripter can fix the problems...

 

Please don't make posts like "THIS SCRIPT GOT ME BANNED." Every script gets people banned.

 

Please don't make posts like "I'M PAYING FOR THIS SHIT." It's a premium script. Of course you're paying if you're using it... Think the script is shit? Try to get a refund.

 

Please make sure that you know what the script is supposed to do before posting a "bug report."

 

If you are going to post a question like "Does this script support XXX?" Read the original post first.

 

Script writers appreciate well written, detailed bug reports. It makes them happy . Happy script writers and good bug reports means quicker and more frequent bug fixes, which in turn benefits the script users.

 

Before leaving a negative review:

 

Before leaving a bad review of the script, first try to contact the scripter in order to get an overview of the situation, or receive help... Often it might be that you're not setting up the script correctly.

Edited February 4, 201411 yr by ericthecmh

Thank you for this hopefully people actually read it!

i couldn't agree more with you this should be pinned 

Thank you Eric like swizz said hopefully some people read this.

Nice thread.

 

I GOT BANNED

Try this: Learn to accept that fact. You're botting.

Explanation: None needed.

 

 

XD

Thank you for this hopefully people actually read it!

they won't tho

Also, add to the thread:

 

Before leaving a bad review of the script, first try to contact the scripter in order to get an overview of the situation, or receive help...

 

I can't count, how many times people have left me 1/5, 2/5, 3/5, because they don't understand simple things / can't setup properly.

You're the official #1.

Pin this thread.

Also, add to the thread:

 

Before leaving a bad review of the script, first try to contact the scripter in order to get an overview of the situation, or receive help...

 

I can't count, how many times people have left me 1/5, 2/5, 3/5, because they don't understand simple things / can't setup properly.

 

Added. Good suggestion

Thanks for taking your time to write this, gotta link this thread

Hopefully people read it and not overlook it like everything else.

Good read

 

Any news on if u looked into that blastfurnace?

Useful m8, thanks.

Good read

 

Any news on if u looked into that blastfurnace?

 

Nope, still don't have the skills... Let's keep personal conversation off this thread though.

Edited February 5, 201411 yr by ericthecmh

Nice post, Eric. It goes along nicely with this:

http://osbot.org/forum/topic/35777-guide-how-to-report-a-script-bug/?p=395925

 

Edited February 5, 201411 yr by Eliot

not getting past "waiting on GUI" not really sure what that even means and how to fix it?