Jump to content
View in the app

A better way to browse. Learn more.

OSBot :: 2007 OSRS Botting

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Laz

Suspended
  • Joined

  • Last visited

Everything posted by Laz

  1. That's a common misconception amongst the botting community of RuneScape. Injection is equally just as safe when implemented properly. That is to say, some bots do not support the techniques we've implemented in OSBot to prevent detection and may or may not be vulnerable to detection. Also, the information that can be extracted with reflection is identical to the information that can be extracted by injection. The only difference is that reflection is slower and uses more CPU. Additionally, reflection requires less effort to work.
  2. Variables like areas to avoid when walking will be able to be set before running the bot on the account. Also our mapdata will attempt to include as much information about the danger and requirements for survival in certain routes. I'm not saying that it will be perfect at release, but our mapdata will be very accurate once introduced.
  3. We don't support reflection because it's extremely slow and has too much CPU overhead. Our bot has to access many variables like model vertices and triangles at real-time, especially in situations where we're interacting with a moving entity. Reflection would only force us to make the bot less accurate to compensate for the CPU overhead and would only further increase the ban-rates due to less-human like behavior. Also, we've implemented injection in OSBot very securely and stealth-like. We modify the client and JVM at runtime to make detection of our injections impossible!
  4. Hello community, I present to you OSBot 2.1.12 which features more human-like interactions and point-selection, improvements with starting, stopping, and interrupting scripts and randoms. Mouse now exits the canvas when a script is exiting or being paused. Multi entity interactions like (item on item, item on object, spell on entity, etc) have been fixed! Bugs with equipment tab have been fixed. Download: http://osbot.org/osbot2_beta/OSBot-packed-2.1.12.jar API: http://osbot.org/osbot2_api/ API (.zip): http://osbot.org/osbot2_api/Docs.zip Thanks, Sincerely, Laz and the OSBot Team. More bug-fixes coming soon and web-walking will be released with OSBot 2.2.X. NOTE: Remember, on June 16th, 2014 OSBot will no longer keep selling OSBot 1 scripts! We will keep maintaining OSBot 1 for current customers. Also, the OSBot 2 SDN is ready and we're awaiting script submissions.
  5. Laz posted a topic in Releases
    Hello community, this release features some tweaks to the mouse algorithm, a new startup loader, a patched script executor, and more. I've also patched the OSBot 1 script emulator. Download: http://osbot.org/osbot2_beta/OSBot-packed-2.1.11.jar API: http://osbot.org/osbot2_api/ API (.zip): http://osbot.org/osbot2_api/Docs.zip Thanks! Sincerely, Laz and the OSBot Team. P.S. Web-walking is coming soon
  6. Laz replied to Laz's topic in Releases
    Equipment injection is slow. We're going to optimize it. It does not get stuck however. We'll be working on a more stable release today.
  7. Laz posted a topic in Releases
    Hello OSBoticans, I managed to improve the way mouse positions are picked and how the bot randomizes its movements. It's still a work in progress but it's great improvement from the previous releases' random spazzing on complex objects. Additionally some built-in painters have been modified aesthetically. Here's the download: http://osbot.org/osbot2_beta/OSBot-packed-2.1.10.jar API: http://osbot.org/osbot2_api/ API (.zip): http://osbot.org/osbot2_api/Docs.zip Thanks, Sincerely Laz and the OSBot Team. P.S.: The official OSBot2 Repository will be opening soon!
  8. By the way scripters, instancing/selling tabs will be available on the OSBot 2 SDN. This means most scripts will be dirt cheap for one tab and relatively moderate in cost for gold farmers running many bots.
  9. If the actual developer releases the OSBot 2 script, you'll simply be given full access to the new equivalent.
  10. It is right now and will always be. Free scripts and local scripts will be available for OSBot as well.
  11. I don't appreciate your narcissistic attitude and the SDN will have plenty of scripts. Many script developers already have began converting and writing new scripts.
  12. We'll be releasing bug-fixes throughout the transition period. We know there are still problems with interactions on OSBot 2 and are working to fix all the bugs which have been reported. On a more important note however, OSBot 2 is nearly finished. The current bugs are small and are easily fixed.
  13. They can be emulated but we don't want to sell unstable software. Scripts can be converted easily so it shouldn't be an issue to the script developers, especially if they're being paid.
  14. Hello dear botters and script developers. We feel it's becoming time to announce that OSBot will begin officially transitioning over to the OSBot 2 platform along with commencing the start of the new SDN. Today's message is simply a reminder and fair warning to every script developer that the SDN will no longer be selling OSBot 1 scripts starting 2 weeks from now (aka June 16th)! What does that mean? Well if you paid for an OSBot 1 script, you will still be able to use it on either OSBot 1 natively (as the script was designed) or on the emulator which OSBot 2 provides. Transition Date: June 16th, 2014 For customers: If a script is deemed equivalent to your OSBot 1 script and added onto the OSBot 2 SDN, you will be granted access to the OSBot 2 version as well! If you paid for a script that does not renew ever (aka a lifetime script) and an OSBot 2 equivalent script is available, you will only have a free-trial of 30 days for the OSBot 2 version! You may decide freely whether to keep using OSBot 1 scripts for botting or the OSBot 2 equivalents. For script-developers: OSBot 1 scripts will no longer renew or be sold on our store! In order to keep your customers and status as a developer on the SDN, you will be required to convert your scripts to the OSBot 2 platform and ensure their quality and standards. It does not take very long to convert scripts, OSBot 2's API is simply a little bit different with additional features. There is no reservations for certain scripts (i.e. AIO fighters, merchers, etc.). It's a free-for-all. Only the best scripts will be accepted for premium sales. Additionally, any script which is to be sold on the OSBot 2 SDN/Store will have to meet certain standards of quality and reliability. What to expect after OSBot 2 is released: We've been developing OSBot 2 for a long time now and we're close to getting a fully operational dynamic web-walker. OSBot 2.2.X will feature a bot scheduler which takes full advantage of web-walker API being written currently. Additionally, the API will be added so that developers may use web-walking in their scripts as well! The next generation scripts for OSBot will feature requirement logistics and starting points on the map. The built-in bot scheduler will allow you to load up an unlimited amount of compatible scripts concurrently and and allow the bot to transition between the loaded scripts freely and randomly based on certain probabilities and configurations done before-hand. This new style of automatic scheduling will allow your bots to behave more human-like during long periods of time by constantly having a pool of different available behaviors. How are we doing it?: Here in the development line we're creating tools which facilitate the analyzation of the game's maps and object spawns. Much of the logic behind the proposed web-walkers and bot schedulers is easily automated when data from the game is analyzed properly and efficiently. Conclusion: We want to start seeing lots of script submissions for the OSBot 2 SDN! OSBot 1 scripts will no longer be sold on June 16th. Newly added OSBot 2 scripts will replace our current repository with better, more reliable scripts! The OSBot 1 client will still be supported for several months and will be discontinued once the OSBot 2 repository is satisfactory! Thanks, Sincerely Laz and the OSBot Team!
  15. Laz replied to Maxi's topic in Releases
    We use techniques to avoid the detection of injection. Jagex only has one method of detecting injection in the client and it's via reflection (checking for non-authorized member insertions like methods or fields). Our loader has a feature which injects your runtime JVM and xboots the modified classes to prevent detection via reflection. So in essence, injection isn't causing people's bots to be detected, it's the behavior which the bot exhibits that Jagex is able to profile. This is why script writers should be writing more complex, human-like scripts instead of simply getting it to work as efficient as possible. Additionally, we've already started developing features that would make the profiling of bots more difficult and random such as the proposed bot scheduler in conjunction with web-walking.
  16. Laz replied to Wrecks's topic in Spam/Off Topic
    Add me, thisbelaz
  17. Hello community, as of this morning we were experiencing some downtime as a result of certain unexpected network maintainence. As a result traffic could not reach our content servers. The problem has been fixed by rerouting traffic to a new line. Hooks for OSRS update #49 (May 27th 2014) were pushed this afternoon and should allow OSBot 1.8.11 and 2.1.7 to load the latest RS client. Equipment API is still broken however and we have been developing a fix within the next couple hours. Sorry for our recent down-time, we've established plans to move OSBot to more reliable cloud-servers in the future and to redesign the SDN infrastructure so that the bots spend less time connecting to remote servers. Thanks, Sincerely the OSBot Team.
  18. I havent had time to fully finalize the anti-ban system since it's still experimental. I can assure you a method to stop them all at once will be added but for now you can do a simple for loop on the enum values of BehaviorType.
  19. Hello community, the previous OSBot 2.1.4-5 was not perfect in that it was experimental. Tonight's build features an improved interaction method which effectively combines accuracy, precision, speed, and randomness. In combination with the built-in anti-ban's random mouse mover/shifter and effectively randomized mouse points in our new more optimized design, the this build features interactions which seem more human-like now. The hardest part about interactions is successfully combining speed with accuracy and human-like behavior. Also anti-bans have been made less probable as it seemed the previous configuration was too high in frequency. Download (OSBot 2.1.6) : http://osbot.org/osbot2_beta/OSBot-packed-2.1.6.jar JavaDocs : http://osbot.org/osbot2_api/ JavaDocs (.zip) : http://osbot.org/osbot2_api/Docs.zip Thanks, Sincerely, Laz and the OSBot Team.
  20. Most OSBot 1 scripts will run fairly well. I may be exaggerating but you should try to see if they do. OSBot 1 scripts emulated by the OSBot 2 engine benefit from the superior bot-platform in a number of ways (performance, behavior, speed, etc.)
  21. Seems I left a nasty one-line bug in this release. Pushing OSBot 2.1.5 as a minor hotfix.
  22. Hello community, I hereby present you with OSBot 2.1.4/5. OSBot 2.1.4/5 is a major milestone in terms of stability, human-like behavior, and performance. In order to have optimized interactions on moving entities like NPCs or players, we had to implement various optimizations within the model callbacks and mouse movement destinations. The mouse now uses bounding boxes for moving entities, making the interactions more human-like (by allowing for over-shooting/missing) and also faster now. Bot-like 100% success-rate interactions have been eliminated in favor of more human-like trial and error behavior. The system was written by Maxi and optimized further by me. Additionally an integrated anti-ban has been added to the bot which runs seamlessly on all scripts. At the moment it cannot be disabled except through the API within scripts. A feature to toggle certain behaviors on/off and to change their probabilities dynamically will be added to the bot soon! Many minor bug-fixes which were not mentioned above were also fixed. For example script/random executor context switches are now much smoother and will no longer freeze. Additionally a few classes were repackaged within the API and some additions can be found. OSBot 2.1.4/5 behaves more human-like now but CPU usage may or may have not increased slightly from previous builds. We are still optimizing our new interaction systems! LINK (v2.1.5): http://osbot.org/osbot2_beta/OSBot-packed-2.1.5.jar API JavaDocs: http://osbot.org/osbot2_api/ API JavaDocs (.zip): http://osbot.org/osbot2_api/Docs.zip Thanks! Sincerely, the OSBot Team. EDIT: OSBot 2.1.5 has been pushed as a hotfix for a major bug. Regardless, the build features experimental features which have not been extensively tested... Good luck
  23. I'm starting a fresh new farm. Have had the bot do tutorial island, bot chickens, and now its doing flax-picking. Going to bot cows later and then start spinning and start setting up more accounts. At the moment I'd recommend babysitting your bots every ~5 minutes as they've been breaking some randoms and banning people. I have a couple randoms fixed which I will release later tonight. The joy of being an OSBot developer is that you bot but you're not actually botting because I'm always staring at it haha.
  24. Check out the spoiler I just put on the main-post more progress on web-walking will be coming out soon.

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.