Laz

Because it's nearly bug-free and behaves more human-like. OSBot 2 will definitely have lower ban rates, especially on well-designed scripts.

Hello community, OSBot 2.1.X will be released this weekend with many bugs and performance enhancements. Proxy support will have been added as well as other features that have been proposed. Additionally we've decided to not release the API's source code but simply provide the source code to certain items on request. This decision was made on behalf of the fact that we're trying to combat RuneScape's botting profiling techniques. Having an open source API will not benefit that cause and will not benefit the end-users of our botting software. Nearly all random event solvers will have been implemented successfully on the OSBot 2.1.X release. Following this release, our script developers will commence the development of brand new, higher-quality scripts. Also, OSBot 2.1.X is supposed to succeed OSBot 1 as the botting core being used to run scripts. OSBot 2.1.X has a brilliant script emulator which allows it to run OSBot 1 scripts like any other script. Once this feature is working flawlessly, we will fully discontinue development on the original client. Not only are we going to be releasing a brand new botting engine, we are also planning on adding MANY new features and services to the website. We're expecting these features to become highly popular and competitive. Thanks, Sincerely Laz and the OSBot Team! P.S. The administration team has been rather unorganized lately. We've done various reorganizations within the development team of OSBot. Expect much more frequent updates and better service!

Hello fellow scripters, you know that "int onLoop()" method you guys like to use a lot? Well depending on how much logic you handle within this method call, you could be making your bot use more CPU. The best way to reduce this CPU usage is to raise the value given to it. In essence, you shouldn't be looping at less than 150 ms because it's a complete waste of CPU power and makes your script more detectable! Do you really think your brain makes concious decesions about the game your playing at 20 times a second (assuming your using return values of 50 ms)? No... in fact heres some data: http://www.humanbenchmark.com/tests/reactiontime/ They're median response time for humans on their study is 215 ms. I'm not exactly sure to what extent some scripters do this, but the more instructions you run per second, the more power your CPU needs to allocate to the script. Additionally, if your script for some reason needs to spam click or something, then make sure that your script doesn't execute many instructions when its looping at higher speeds. In essence, if you made it only do this... public int onLoop() { return 50; } ... than your not going to be using much CPU. But if you have an onLoop() method FILLED with hundreds of if-statements and conditionals everywhere, you're going to be using MUCH MUCH more! So tl;dr; Use a sleep time like gRandom(215, 80). That method uses a mean of 215 with a standard deviation of 80ms. Additionally, RuneScape's servers loop exactly every 600ms. What does this mean? It means that for every step you take in RS while walking, it takes roughly 600ms. If you're running, the steps get sent twice every 600ms. When you click on an object, it takes approximately 600ms for it to open. Etc. Etc. Thanks, Hopefully you guys learned something.

That works too. Remember that filter jar is specific to your JRE. It gets automatically generated by the stealth loader.

For now instead of doing java -jar, do java -cp OSBot 1.8.1.jar org.osbot.engine.Main. This will disable the stealth loader. I will however add proxy support on the next OSBot release!

Closed - OSBot 1.8.1 has been released!

I'm pleased to announce the fix for today's update. This 1.8.X release features several bug-fixes and additions: Client downloader no longer crashes or require relaunching Interface callback injector has been patched (fixes walking for new update). A new boot loader with stealth injection ported from OSBot 2 (this should combat a technique that's possibly used for insta-bans) When the client is offline, CPU usage doesn't skyrocket. Local scripts are now loaded before remote scripts. Download: http://osbot.org/get/index.php Happy botting! Thanks, Sincerely, Laz and the OSBot Team. Edit: 1.8.6: Camera rotation bug (thanks Eliot for confirming). 1.8.5: More work on facing stuff. 1.8.4: Timeout of rotateCameraToAngle() infinite loop. Partial fix for ArrayIndexOutOfBoundsException in Character.getFacing(). 1.8.3: (not version dependent) Fixed hook for lowest pitch. Reverted change to Molly and Pinball because the hook problem was solved. Added timeout for rotateCameraPitch(). 1.8.2: Anti-randoms (Molly, Pinball) fixes by @Divinity for the camera problem I'm tracking down.

Hello community, I'm currently debugging as to why the walking on OSBot has stopped working. The fix containing the patch should be released sometime today. Sorry for the inconvenience! Sincerely, Laz and the OSBot Team. EDIT: The problem has been identified. The interface callback injector has been broken. This is the second time its broken and it will be patched to not break again with similar updates. Please be patient, a patch should be released very soon!

theres not that many features being implemented here in the post. The hardest part will probably be proxy support haha.

Hello community, because OSBot 2 has not reached our standard as of yet. I've decided to change it's development strategy. Here are the list of changes that I am planning: Revamped event system for increased performance and stability Open-sourced API available to everyone for faster bug-fixes and feature implementation Open-sourced random event solvers for better random event support Other various API changes/enhancements/implementations Improved camera functions Improved walking functions Proxy support Although we'd love to release the open-source API now, it's going to take some time to restructure the bot into two separate modules (one open-source, and another closed-source). This isn't going to take too long though, I expect all these changes to be implemented within at least two weeks. Beware, the API changes might cause any current OSBot 2 scripts (if they even exist) to break. We're taking advantage of the fact that barely any scripts have been written to implement these enhancements. Hopefully with our new, future open-source model, OSBot will excel in development and features. Thanks, Sincerely, Laz and the OSBot Team.

Any errors printed?

Looks like the legacy emulator is incomplete. I will patch this on the next release. Thanks for the bug report.

If its not in this list, it definitely doesn't work. Note, not all of these may be working fully! Try updating your java. I'll look into this tomorrow with my spare monitor.

Yes there is. Inventory extends ItemContainer. http://osbot.org/osbot2_api/org/osbot/rs07/api/util/ItemContainer.html

You won't get any ads while in-game, which are the more annoying ones. This bug will be patched for VIPs and Sponsors soon.

Currently theres a bug with the hooks that I'm patching up. If you can't login in with it, it will work in a few minutes. Edit, fixed! No redownload is necessary!

Hello community, due to the lack of bug reports for OSBot 2 and the lack of scripts being developed for it. I've decided to release OSBot 2.0.16 which contains many added random solvers and bug-fixes. OSBot 2 can now be used by anyone just like OSBot 1! Also many OSBot 1 scripts are compatible with OSBot 2. There are still some bugs present in OSBot 2 as well as some unfinished random solvers (not that many). The more bug reports that I get for OSBot 2, the faster this community can start using a more advance bot and lower ban rates. JavaDocs (for scripters): http://osbot.org/osbot2_api JavaDocs (for scripters) (.zip download): http://osbot.org/osbot2_api/Docs.zip OSBot 2.0.16 (.jar): http://osbot.org/osbot2_beta/OSBot-packed-2.0.16.jar Thanks, Sincerely, Laz and the OSBot Team. NOTE: All script developers should be testing their OSBot 1 scripts periodically with OSBot 2. OSBot 1 will not be supported for long!

Ladies and gentlemen, I'm pleased to announce that I've been working very hard on OSBot's successor, OSBot 2. Many bugs have been fixed, the updater has been enhanced, and a wide new array of previously needed hooks have been added. Along with all this progress, we've developed quite a number of working randoms event solvers for OSBot 2. However progress isn't going as fast as we want it to go. I want to announce that we have plans for making the API open-source along with our random event solvers. Hopefully some of the scripters can add the features they want or still don't have. I am currently aware that OSBot 1 has a couple of unworking random event solvers. These will be fixed within the upcoming days. Sorry for any inconvenience this may cause. Hopefully this open-source transition happens by next week as well as a public release for OSBot 2. Thanks, Sincerely, the OSBot Team.

Hello community, this is my first OSBot 2 release in a bit. I've managed to stabilize many parts of the software and fixed some issues with legacy scripts and so on. Patched the random event handler because it was broken. The release features some refactoring with RandomBehaviourHooks and how they are identified. They now use enums in OSBot 2 instead of simple generic IDs. The Script & Account selectors can now be closed by the X button on the top-right. Improved CPU performance amongst random event solving. Enhanced some inefficient code within the API and fixed bugs with bot contexts. Fixed many issues with the OSBot 1 script emulator. Try and see if your OSBot 1 scripts work now! Download: http://osbot.org/osbot2_beta/OSBot-packed-2.0.15.jar API: http://osbot.org/osbot2_api/ API (.zip): http://osbot.org/osbot2_api/Docs.zip Thanks, Sincerely, Laz and the OSBot Team.

This won't be that big of a deal when OSBot 2 is fully out because I've already optimized its interactions so well.

Already implemented in all OSBot 2 builds. Any OSBot 1 script running on OSBot 2 will be using it automatically too.

Hello, this version of the bot features a fix where resources weren't being disposed of correctly when a user closed a bot. The result? A huge memory leak and CPU usage. This version of OSBot 2 fixes that issue. This version of the bot also features a couple new (untested) additional random event solvers: Link: http://osbot.org/osbot2_beta/OSBot-packed-2.0.10.jar Thanks, Sincerely, Laz and the OSBot Team. EDIT: If you downloaded the bot right when this thread was created, redownload the new 2.0.10. There was a bug in the previous build I released.

Release 2.0.9 which features a fix for the connection class. Also I believe theres a memory leak where if you open one tab and you close it, the client stays running in the background. I would advise against closing tabs on OSBot 2 until this issue is fixed!

I released 2.0.8 which contains a hotfix for the client injector. Not sure if it fixed the issues however. With OSBot 2 however, daily builds will be released every day.

OSBot 2 is actually fairly stable with actual OSBot 2 scripts. The problem is that the emulator for OSBot 1 scripts is still very experimental.