Laz

Sorry guys I had to re push it to OSBot 2.2.20 because we forgot to merge our changes. (I'm still getting used to having Alek as a developer )

Expect more updates too! We might be having more than just daily builds from now on (except for maybe weekends sometimes).

Hello community, this release is full courtesy of @Alek although I'm releasing it on his behalf. It seems that all the remaining bugs left in the ItemContainer APIs were patched and a new Quest API has been added! @Alek's changes: -Added Quest API --Quest.isCompleted(Quest quest); --Quest.isMembers(Quest quest); -Fixed an issue with ItemContainer isFull() returning incorrectly after logging in. -Made some small improvements to FreakyForester -Updated ItemContainer isEmpty() Sincerely, The OSBot Team! P.S.: JavaDocs are being regenerated right now to highlight the new Quest API. EDIT: It seems Alek never pushed the Quest API! Sorry it will be released later today! EDIT2: NVM, I deeply apologize for another double update today. I forgot to merge his changes with mine. OSBot 2.2.20 has the Quest API and all the actual changes. Again sorry!

Hello community, We're pleased to announce that we've promoted @Alek to the official developer rank. He will be working directly alongside @Laz, @Zach, and @Maxi! Please give him a round of applause and congratulations! Alek is very dedicated and will definitely sharpen up our development! Sincerely, The OSBot Team!

Interesting, can you elaborate more accurately what's happening? After an update what exactly happens?

It might be but I didn't think I had compiled it with Java 8. Try re downloading the jar. It's probably just corrupted. Let me know kk? EDIT: @Swizzbeat has confirmed it works fine for Java 7. Just redownload and you'll be fine :p.

Hello community, Last night's release was definitely a step forward but there was a small bug left unnoticed in the Bank API that has been patched! It has been tested too! Also some fixes from the API devs were not included in the last release because their changes were not merged correctly and we have fixed the small issue. These changes include the quick-prayer updates, strange plant fixes, grave digger fixes, etc. Expect more updates soon! AND IF YOU DIDN'T KNOW, WE NOW SUPPORT JAVA 8! Sincerely, Laz and the OSBot Team. EDIT: We just discovered a small bug that involves the saving of your settings/preferences. It's minor but it deletes all your stored accounts each update. This has been patched and will be released tonight for 2.2.17. The bot itself should work fine after you re-add your accounts/settings. Sorry for that inconvenience!

We've been working on randoms. I'll try spinning some flax and fix the strange plant today.

I really like this thread because everyone of your points is valid. However, OSBot features stealth-injection (it modifies internal JVM class files to make it impossible to detect injected methods like Character.getHealth() VIA reflection (the only known technology they use to detect injections). I deobfuscate, fully refactor, and decompile the OldSchool gamecode every couple updates (OSBot's cool updater makes it easy to make their client human-readable, refactored & compilable within minutes!). They haven't changed it one bit. What I can say is that client-based detection is no longer the immediate threat. It's bot-watch and it's macro analysis based algorithms that really hurt. Jagex has even said it themselves that they're abandoning old bot-detection techniques like random events because bots have been smart enough to the point where all these old techniques no longer work efficiently. What's causing the problem is that botters, by nature are very lazy people. Most people are probably using the same script that makes the most amount of money, only training one skill, etc. They're not really playing the game... and this is by far too easy to see. How do we solve this? Well I haven't simply ignored these issues, I've been quite aware that some steps need to be taken to make bots play less like macros, and more like REAL players. Here at OSBot we're currently working on our dynamic web-walker which will be used to be able to schedule scripts around. This is an added plus, since botters are too lazy to switch scripts themselves! The scripts can be schedules in a way that will be almost random but smart. However all this is easier said than done. We're putting a lot of effort and yes these technologies will be available in the future. Again, there are many more things than what I have mentioned to prevent bans. More discussion is definitely welcomed .

Yes, if you wish to use proxies, you will have to open a whole new window. IP cross-linking is still just as dangerous. We are implementing proxy-per-tab botting soon however. It's more difficult to implement but not entirely impossible :p.

Hello community, I know a lot of our users have been unable to run our bot because one of our dependencies was not compatible with the newer JVM. Thankfully, we've fixed the issue and now Java 8 users can run OSBot safely with full stealth-injection support! Additionally as a way to combat bans, we're forcing everyone to select an account prior to starting a tab. Why such nonsense? Jagex is able to track the identity of computers based on a file called "random.dat". Although OSBot has always patched the client to use different files for EACH tab, we've figured out its smarter to do it based on username to prevent cross-linking of gold-farming accounts! Don't worry, we're not here to steal any RuneScape accounts! More bugfixes listed here: Bank now updates items successfully after withdrawn! calling Item.interact() should now work for Item instances initiated directly from our API. and here are the changes credited to the API developers: OSBot 2.1.15 @Alek's changes: -Updated Freaky Forester random event to dynamically grab pheasant ids (less chance of the random event breaking after an RS update). -Added Inventory method "isEmptyExcept(String... strings)" - suggested by . @Ericthecmh's changes: -Fixed Gravedigger random and improved various methods in the solver. @Swizzbeat's changes: -Added new method unregisterAllBehaviors() for anti-ban. We hope you enjoy this release! More updates will be coming out faster than ever before! Also, OSBot 2.3.X will be the first version of OSBot to support web-walking! We're almost done with many of the anti-ban features we've promised! Thanks, Sincerely, Laz and the OSBot Team!

Event solvers, sorry I didn't mention.

Hello community, although we have not been releasing many updates lately, we've been working heavily on our software privately as we're developing many features that are soon to be release. Courtesy of the API team, (mostly Alek & FrostBug for this build), I present to you OSBot 2.2.14 (we skipped 2.2.13). The download link is on the navbar and the homepage! Thanks, Sincerely, Laz. JavaDocs will be updated soon. Many random event solvers were patched ***

The the inflation rate in the RWT market definitely correlates heavily with botting activity. Unfortunately Jagex has been making botting more expensive. That's not to say we're not working on improving the conditions for botting and making selling gold more profitable.

Hello community, I'm apologizing deeply for ignoring one of our most important members of this community, our free user base. Believe it or not, our free user base allows us to sell advertising spots on the client on our website. We've had a bug which prevented our free users to bot on OSBot 2 & 1 after the new server updates we released because of a very small bug in our server backend. This type of stuff happens often unfortunately and its because of a fault in our debugging strategies involving communicating with the community to get feedback on our products! I am very happy to announce that we've FIXED the MULTI-LOGIN BUG for FREE USERS! Zach and I finally figured out how prevalent it was and decided to crunch it down. We hope something like this does not happen again. In-fact we've been working privately in the backend of things with our servers and OSBot infrastructure. We will be promoting more free scripts and stuff to attract new users soon. Thanks, Sincerely Laz, Zach, OSBot Team.

I'll look into this as your right it most likely is broken. It's just a small bug we didn't notice, we'll fix it.

I approve of an organized list which could benefit the developers by narrowing down what we're looking for to debug!

Regardless, it's still fast as shit haha! What processor?

Doubt the processors can reach full capacity when their threads are constantly processing data I/O. Either that or its strategically designed to be capped at 90% so that the user can still operate on his/her machine.

Fuck him man! I live in Miami and this is a disgrace! #HeatFan

sigh... hope you come back.

It's very low ban rate imo. You should still take precautions though, the tab market is easily saturated and Fagex doesn't like that.

Hello community, as an effort to raise awareness of OSBot since we're no longer growing too fast. You can follow us on Facebook and Twitter to view stay-in-touch. Not everybody likes posting on a forum and there's plenty of people on Facebook & Twitter. Like us on FaceBook: http://facebook.com/OfficialOSBot Follow us on Twitter: http://twitter.com/OfficialOSBot or @OfficialOSBot We'll be requesting proggies and such so that you can we can repost/retweet them! If you want to help us grow you can also invite you friends to join as well! Thanks, Sincerely, Laz and the OSBot Team!

The warnings are no big deal. OSBot & OSBot 2 have the same protection against injection detection. That's why OSBot 1 now uses OSBot 2's loader. OSBot 1 simply is still printing the debug messages which I left in there months ago! I left them there because they were not being called as it depends on Jagex sending a specific packet to search for the methods of a class. The good thing is though is that they only see the code that THEY wrote AND NOT the code WE INJECTED. The debug mesages are kinda just showing off the protection feature by printing which methods Jagex COULD'VE DETECTED! I however advise you to not bot on OSBot 1 any longer. Even though the random solvers may or may not work, I'm pretty sure the latest RS update broke an injector that OSBot 1 had for detecting the positions of interfaces/widgets. This will cause multiple symptoms of scripts failing. I suggest for you to use OSBot 2. It's already proven more stable and has a better API.

Appreciate don't depreciate.