Laz

This is pathetic.... we don't mine bitcoins on your machines. We've setup OSBot to allow the JVM to optimize graphic performance. The JVM automatically chooses whether or not your GPU is used or not. If your GPU is used, it's sole purpose is to save CPU processing power. The only process within OSBot which makes use of the GPU is when we copy image buffers around to render the canvas and loading screen which you've screenshotted. OSBot requires double-buffering on every client and this may lead to your GPUs powering up. Double-buffering allows us to render graphics on-top of the RuneScape canvas in a synchronized fashion. We could make way more money by simply making OSBot browse ads in the background or some other bullshit but we don't. I'm disappointed that the community has come to such a conclusion.... -.- It's funny cause you're comparing GPU usage at the loading screen of OSBot 2 to the GPU usage of OSBot 1 on the loaded RS client. Obviously your profiling methods are not accurate anyways.

Login screen is an RS issue I believe (although I may be wrong). Try loading the login screen on the browser and see if its any difference (on the same start-up world).

Hello community, this is a quick hotfix which eliminates the lag/errors when loading new tabs. RuneScape seems to have implemented some sort of protection which denies very quick successive HTTP requests. As such, this version will no longer have the issue and will start faster than ever before. Sorry for the inconvenience of re-downloading another update. I did not expect 99% of the community to experience the bug. Thanks, Sincerely, Laz.

If your client doesn't load use the world selector. A better explanation has been posted in the OP.

Has been fixed. Please reload your bots! The hooks were outdated on the server.

Be careful using other clients to bot as well! Just because their script run doesn't mean it won't get detected like this either!

RuneScape has updated today to revision 50 but our updater is fine. No hook identifiers were broken during the process. We could theoretically update the bot right now but as an effort to prevent further bans, I'm going to be evaluating certain bugs which occur during random event solvers. Nearly all our random event solvers have been tested but there seems to be certain conditions under which they do not activate. We do not believe this is simply a trivial bug but an effort on part of Jagex's bot-watch campaign to efficiently detect players who use injection and/or reflection bots. The idea of having random events that some how bypass our random event solver queues is definitely a quick way to identify bots. These techniques can all be prevented and that is why I'm delaying the release of the #50 revision update until we fix the issue (which will be today for sure!) I'm the only active developer at the moment but no worries! The fix won't take long. Additionally, we're going to add some extra injections to accurately detect invisible NPCs and/or players (specifically moderators/admins). Sorry for the inconvenience but this wait works to everyone's benefit. We don't want to have bans occurring when they can EASILY be prevented by us. Thanks, Sincerely Laz.

You should read the OSBot 2 SDN announcement that we posted. Once the scripts become premium (after a week) you may request the free 30 access for it.

The way our wrapper system works is simply to wrap the client's reference of the entity. Unfortunately because of the way the RuneScape game engine works, there exists the situation which you have described. If it's a player or npc, you can call .getIndex() to get the player or npc's index on the client's global list. For objects you can do .getUID() to get the unique hash of the object.

Expect another release tonight. I just started University so I've been busy moving in and getting settled. The development team is going to crank up some more updates soon.

Hello community, the OSBot development team is proud to present OSBot 2.1.15 with updated random-solvers, stability bug-fixes, and API fixes. This is the first release which features updates from actual script developers like ericthecmh, Alek, Xerion, Xavier, Notorious and more. The most crucial bug-fix present in this release was an update that fixed an issue with random solvers never activating and/or crashing your script. OSBot has officially transitioned over to the more advanced OSBot 2.X client. REMEMBER TO TAKE ADVANTAGE OF THE ONE-TIME FREE ALL WEEK ACCESS TO THE ENTIRE OSBOT 2 REPOSITORY! YOU CAN ADD ANY SCRIPT (PREMIUM/NON-PREMIUM) FOR FREE FOR THIS WEEK ONLY! If you are stuck in a random event, please pm @Ericthecmh with the account name and password. Do not complete the random event. OSBot 2.1.15 download: http://osbot.org/get/index.php or you can use the download button from now on. OSBot 2 SDN: http://osbot.org/mvc/sdn2/scripts/ Latest JavaDocs can be found at http://osbot.org/api/ or http://osbot.org/api/javadocs.zip Thank you very much! I'm very proud of the community and all the developers/moderators for their hard-work. Sincerely, Laz and the OSBot Team.

I love my XBox One. They dominated at E3 :p.

Guys thank you so much. We've been able to fix many random solvers so far and now Ericthecmh will be accepting accounts as well. I will be forwarding your submissions to him every once in a while.

OSBot 2 technically was always working so we were kinda still online haha ;)

Hello community, I present to you OSBot 2.1.14 which features many fixes to several random solvers including: Maze (thanks to EvilTwin) Mysterious Box (thanks to Elliot) Pinball (thanks to Jack) Freaky Forester (thanks to led) Evil Bob (thanks to Xerion) Lost and Found (thanks to Maxi) and additional API bug-fixes have fixed errors with random solvers activating and their interactions. Additional API bug-fixes/features have been added including: Map.canReach(...) has been patched see (http://osbot.org/osbot2_api/org/osbot/rs07/api/Map.html#canReach(org.osbot.rs07.api.model.Entity)) Map.realDistance(...) has been patched (see http://osbot.org/osbot2_api/org/osbot/rs07/api/Map.html#realDistance(org.osbot.rs07.api.model.Entity)) New Model ID Filter API (see http://osbot.org/osbot2_api/org/osbot/rs07/api/filter/ModelFilter.html & http://osbot.org/osbot2_api/org/osbot/rs07/api/filter/ContainsModelFilter.html) <-- VERY POWERFUL TOOL; BREAKS MUCH LESS OFTEN THAN NORMAL IDS! Radius for randomization of walking has been lowered due to complaints by script writers (the ability for script writers to walk precisely will be added to the API soon) Finally, I am proud to announce that more developers will be helping the cause to fix and stabalize the OSBot 2 API as well as the built-in random event solvers! More features that script developers want will be introduced and tested at a much faster rate and updates will occur even more frequently! The official transition to OSBot 2 is coming June 16th. We have already canceled all OSBot 1 script renewals and will no longer keep selling OSBot 1 scripts on our store after the aforementioned date. Download: http://osbot.org/osbot2_beta/OSBot-packed-2.1.14.jar API: http://osbot.org/osbot2_api/ API (.zip): http://osbot.org/osbot2_api/Docs.zip P.S. I am aware our users are experiencing issues with OSBot 1. We will be releasing some updates today for OSBot 1 to fix these issues.

Yes please. Send it.

I have given out 2 VIPs so far, keep the accounts coming. Remember to please let them remain in the random event after PMing me for 24 hours! I most-likely will handle it sooner though!

We need as many accounts as possible stuck in ANY random event which OSBot 2 has trouble completing! You can PM me (@Laz), or @Ericthecmh the account details via private message on the forums and rest assured that we will not steal your accounts. Please allow the account to remain in the random event for up to 24 hours so that we have enough time to test them. We will PM you whether or not we will use your account. If we use your account, you will be given an extra 30 days of free VIP privileges. Once we are done using your account, it will no longer be in the random event. No further botting/activity will occur on it and you will be free to change the password. Again, we need as many accounts as possible especially for the ones that don't work! Thanks, Sincerely, Laz and the OSBot Team!

Ill buy via PayPal.

Trust me, the transition will go great .

It works for all of my scripts.

Hello community. I've managed to revamp our mouse algorithm to make less random glitches, sleep more during loops making fast directional changes slower, interactions are evaluated better now, the bot no longer gets stuck on a selected item or spell, ground items now show up on the entity hover debug. Download: http://osbot.org/osbot2_beta/OSBot-packed-2.1.13.jar API: http://osbot.org/osbot2_api/ API (.zip): http://osbot.org/osbot2_api/Docs.zip This is one of the most stable releases yet. More stability updates coming soon, especially with randoms. Thanks, Sincerely, Laz and the OSBot Team.

Sorry for the new bugs. Please feel confident, these issues ill be sorted out today with a new release.

My scripts don't experience this bug with clicking on the minimap. Let me know if it is an issue on your side.

We will be fixing these issues shortly. Thanks for your input.