Ericthecmh

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.

Awesome

I'm definitely excited to use this in OSBot 2. Will this be usable in legacy scripts, or do we have to move to OSBot 2 scripts? Eric

Some of those requirements, like the graph theory algorithms, aren't really Java related... And doesn't Alek already have the while/black glow thing? :P Eric

Ah clever. You should send me your banking methods ;) Eric

I've just sent this @Zach, and when @Laz and @Maxi come online to Skype, I'll send it to them too, just in case they don't already know :P Eric

The setRunning method by OSBot is fixed. In fact it was fixed in 1.7.68 when I tested it, but I guess Maxi decided to push another update just in case, which is fine. If the script doesn't turn on run properly, it is because the scripter is using his own method. You should post in his/her thread asking him/her to update their method. Eric

And don't forget the new interface child ID for the setRun method! Eric

Aww keep in touch. Hope yeu get your personal things resolveh quickly and you'll return soon. Best of luck with life. Eric

The same way holding a strike works? The admins have paid on time recently, so I don't have any complaints personally. I'm just defending Toph's decision since it appears he's having problems with the administration. Eric

Would you be happy if your employer withheld your paycheck? I think not. In the current payment system, we can't even see how much we're due to be paid, and a lot of scripters complain about being underpaid. It's a really shady system. Tell me then, what should happen? Should the scripters continue working without being paid? I definitely sympathize with you and the other customers on the loss of service, but we don't have much of a choice... And BTW I don't speak for Toph; just myself and other scripters who have directly expressed this viewpoint.

Wow, this is a really clever idea. You should have release this sooner now OSBot 2 is gonna come out

1

It's understandable that you customers are annoyed, but like I said, the payment issues aren't a recent thing. Toph's provided the service for a while even despite payment issues, and as a fellow scripter I respect his decision to stop updating his scripts since he's not being paid.

For everyone who is raging at Toph because he's not updating his script until his payment issues are cleared up, try to think about it from his view... He's providing a service that he expects to be paid for. If he's not receiving his money for his work, he has every right to stop working until he receives the money due to him. The payment issues have been going on for us scripters for months. There are signs of a new payment system coming in to place soon, but that hasn't been put into action yet.

You should get a refund. I'm going to ask Alek to remove this script. Eric

RSBot and RSBuddy never got taken down...The RSBuddy team moved on...RSBot is still up today... No! They should be forced to be instanced. I agree with you 100%. I kinda agree with you,but the OSBot devs need to be more active for what they're getting atm. This should be the same for Premium scripts as well. But I have a feeling that you're just making this thread to try and make more money from your premium scripts I have to agree with Pikachu here (mostly). Sorry Swizzbeat :P I can totally understand the point you are trying to make, but the idea of taking away a scripters right to determine what to do with his or her own script is bad bad bad... I like the idea of instancing better, It's like a compromise.

I'm asking Alek to remove this script from the SDN. I no longer have the time to update or maintain this script. Eric

Ur signature made me look and almost cry lmfao! Wut?

glad it served you well. Be careful in the future :P and good luck Eric

Your a moron, Erics scripts are very high quality compared to the other crappy scripts that sell on the grand exchange. GO ahead and use 5uck's scripts. Hope you had your account info stolen noob from his script. If you bot another acct the same day one is banned your an idiot. They do monitor IP addresses. Ive been using this script for past 4 months and no issues from this script. Your a clown... Appreciate the defense. So, would I be right in saying that currently, the only broken thing is the book of knowledge? I've been told that the strange box has been fixed? Eric

Awesome. So excited to see what OSBot 2 brings Eric

http://scriptersunion.invisionzone.com/index.php?/topic/20-book-of-knowledge/ You should submit bug reports to forum.cmhscripts.com I'll see them much faster that way. Eric

That's not very useful... posting more details would be nice... where does it mess up? Also, please post bug reports to http://forum.cmhscripts.com Eric

Hmm... I'll probably put the recovering thing into the OSBot 2 version, but the second problem is pretty serious, so I'll look into that right now. I have a check to see if it's under attack, but I'm guessing it happened so that the ankou started attacking just when the script passed the check. I'll go add a failsafe though. EDIT: I've added the failsafe into version 2.5.3, though I haven't tested it. It shouldn't make anything worse though :P let me know if it works. Eric