Anon

Yeah and its idiots like you that make it that much harder. Telling us that the random event is broken DOES NOTHING. (We become aware of it but that is it).. Giving us an account stuck in a random that is broken FIXES IT. No idea why people still don't understand this.. You can't just come on the forums and post "Frog random broken" and expect it to be fixed the next day, You need to come on the forum message Maxi, Laz, Zach, or Kati and give them your account details THROUGH PM (DO NOT give it over skype for obvious hacking reasons...) and wait for them to come on and fix the random (Sometimes it is almost less than 10 hours other times it is like 1 day... but guess what you are helping the community out by allowing the fix for that random so the wait is worth it, unless you are an asshole that just wants to leech (Most people)...). The run away from combat random is their problem so you have every right to flame about that one.. but you have to remember the bot developers have lives... They do the best they can on working with randoms but we as a community need to do better by giving them accounts stuck in those randoms (Freaky forester, maze, frog cave, etc.. are all huge ones..). So next time just hop on the forum, DO NOT make a thread about it.. just pm an admin.. But like i said you may have to wait a little bit for them to respond but the wait is worth it, for helping the community fixing it, god knows how many leeching morons are on this site and never help fixing randoms, the simply complain and complain and complain about them. They also have a lot of other things to dev: SDN improvments, Automatic payment for scripters, Bot client memory leak (this is really a huge issue and is quite annoying...), randoms, etc... The admins can't always be on runescape running accounts 24/7 trying to get randoms.. they need us.. /thread

Yeah, until you fully understand how memory leaks occur and when they can happen you will realize that OSBot has HUGE memory leak problems that are not only affecting memory utilization but cpu utilization as well.. I personally believe who ever developed the client (The threading and class loading parts anyways..) personally sucks and needs to go back to school to learn how to properly close things...

Not a glitch.. you probably had a script running and accidentally resumed it... There is no other way this could happen...

In which case you used Advertising other bots isn't allowed. to test this with? Are you sure OSBot usernames and passwords are also send in plaintext? That was a mistype i fixed it.. I meant to say osbot

My friend has an open wifi network at his house and when i came over the one day i connected to it.. **Edit**.. So i decided to start up Wireshark, for all of you who doesn't know what wireshark is it is a complex tool (easy to use but when you understand what you can actually do with it... WOW) used for packet analyzing.. So anyways.. I opened it and start sniffing packets from my default wifi interface.. Seconds later my friend decides to open OSBot and start 2 of his bots.. Then wireshark received several packets to analyze from his computer to OSBot's server (and from OSBot's server back to him..) I decided to follow the TCP stream and see what i could find and wouldn't you believe it! I found in PLAINTEXT his osbot username and password! lol! (His password was very disturbing ). tl;dr Lock your wifi network (with WPA blah blah), cause you never know... Also don't play rs on OSBot over a public unlocked network. I know it is a 1 in a million chance that someone will actually connect and see that you are using OSBot but it is better to be safe than sorry. If you ever want to get back at a friend...

Its a VIP/Sponsor only thing.

All you have to do is delete OSBot folder and restart client... This is a very common error.

You should have it as a keep-alive jFrame for the options so that it can run more than once without having to restart the script... extrememly easy to do... just keep the jframe alive and allow them to enter a new item id and amount to withdraw everytime and make them press a button "Withdraw"... Anyways you also could add the ability to withdraw multi items just making them space the id's apart and when you parse just use the split method.. Also you can add it so you can withdraw as a note... Which is all extremely easy to do.

Offical RS Forums

Well only thing you have to do is delete OSBot folder and restart client... This is an encryption error and usually occurs when you force close the client or upgrading to a new version..

Try deleteing OSBot folder and trying again.. (restart client..) Also wrong section of the forum buddy...

Nah, just delete your OSBot folder and restart your client it will work then..

I have been botting on a VPS and still have 20 accounts going good. No one ever listens to poor old Anon when he says "DO NOT bot on a VPS, in which the provider is specfic in offering RS botting services for that VPS". Jagex WILL flag the IP and you WILL be ban, only a matter of time. I use an unknown host provider (known but not know to anyone else in the community) and I am paying $10 a month for a VPS that can actually run 20 accounts (5 clients...) **8 cores 2.27 ghz dedicated and 16GB RAM (a little excessive.. but I went with the highest plan..). Once again, there are PLENTY of vps providers out there that offer HUGE discounts and everything.. The vps i used was discounted 90% from a promotion (FOR LIFE!!) **They no longer offer this promotion so don't message me..**. If you are interested in finding these amazing discounted VPS's visit: Dedicated Hosting offers : http://www.webhostingtalk.com/forumdisplay.php?s=478c7205b6ac09285f70e440b0efc647&f=36 VPS Hosting offers: http://www.webhostingtalk.com/forumdisplay.php?s=478c7205b6ac09285f70e440b0efc647&f=104 Enjoy the savings and back to normal ban rate **As in you won't get caught because of a flagged IP**. Some things to note when chosing the right provider: 1. Ensure that they have good reviews... Some vps providers just oversell and turn out to be pretty shitty... (Check google for reviews or some other source..) Try to make sure you grab A non-shared CPU vps.. Some providers **most** share cpu with the other vps's in its cluster... You won't really as much have to worry about this unless you are planning on running a huge gold farm.. Huge gold farm requires multiple clients in which will overwork the CPU and possibly get your VPS account suspended (Once again, make sure you check their policies on this..). Also try to make sure they offer some sort of a refund (3 day Full refund or something like that) just in case the VPS you bought does turn out to be shit, you can just open a ticket, ask for a refund, state some excuse..., and bam you are done. Move on to the next provider and go.

I have been botting on a VPS and still have 20 accounts going good. No one ever listens to poor old Anon when he says "DO NOT bot on a VPS, in which the provider is specfic in offering RS botting services for that VPS". Jagex WILL flag the IP and you WILL be ban, only a matter of time. I use an unknown host provider (known but not know to anyone else in the community) and I am paying $10 a month for a VPS that can actually run 20 accounts (5 clients...) **8 cores 2.27 ghz dedicated and 16GB RAM (a little excessive.. but I went with the highest plan..). Once again, there are PLENTY of vps providers out there that offer HUGE discounts and everything.. The vps i used was discounted 90% from a promotion (FOR LIFE!!) **They no longer offer this promotion so don't message me..**. If you are interested in finding these amazing discounted VPS's visit: www.webhostingtalk.com (search the forums until you find a subsection called: VPS hosting offers and click on it...) Enjoy the savings and back to normal ban rate **As in you won't get caught because of a flagged IP**.

You will most likely have to PM an admin (Laz or Zach possibly) your account.

I'll release mine right now ;)

Nice try, but no. just no.

Yeah, I am pretty sure it is part of anti-bot... They seem to be stepping it up.

1. You access a VPS through SSH protocol, i recommend using putty to do this but if you already use linux you can just do it from your computer.. and in order to install the Graphical interface you need (the desktop.. and such..) i suggest you follow a guide, there are plenty around. To view the graphical implementation of the VPS you should probably use VNC-Viewer.. 2. No. Complete waste. 3. Hmm.. Max 2-3gb of RAM and atleast 2.3 > on the processor 4. Yes, as long as you buy it from a site that is trustworthy (I do not suggest you go and buy it from a site that offers services specific to RS botting as they will most likely hack you.. Also don't buy a VPS if someone offers it to you in a PM (**cough** ^^ **cough**) 5. OSBot has a built in function for that now where they actually inject their custom made random.dat files with rs client and you will be able to multi log.

Already aware of this problem they should probably call: deselectItem method they made lol

1. I think you mean VPS... and yes.. 2. I can get one that can run 15-20 bots for $10 a month (90% off deal though soo it will be hard to find..) But you can easily get one that can run 4 bots for 15$ a month.. 3. 24 hours.. 4. Once again i think you mean VPS, and you can save on electricity, also knowing that the vps might be a more protective thing to use so if you ever get keylogged your accounts won't go along with it.. 5. N/A

Pressing the pause button will completely pause the random solver thread in OSBot and will not activate on any other randoms.. I suggest you go to the settings menu and go unclick the box for Frog random...

For linux users: apt-get install recordmydesktop (or yum install..) then run it through linux command line: "recordmydesktop --no-sound" (No "")

Welcome, and have fun selling gold, hopefully legitly..

OSBot already has support methods for scrolling.. why did you make your own... if(!this.client.getBank().isSlotVisible(this.client.getBank().getSlotForId(item))) this.client.getBank().scrollToSlot(this.client.getBank().getSlotForId(item)); this.client.getBank().withdrawX(item, amount); It looks good otherwise...