Skip 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.

Alek

Ex-Staff
  • Joined

  • Last visited

Everything posted by Alek

  1. Oh I get the joke, it's funny because he's still a relatively active staff member.
  2. Well I thought this problem was urgent and couldn't wait 3-4 days (the time it takes to set up a pin). I guess not so perhaps I'll work on something else now.
  3. Anyone have an rs account with a bank pin? Hmm..
  4. First time being banned? Most bans happen this way.
  5. Still looking for an account.
  6. Private message me your RS login, password, and pin to receive 7 days of VIP for free. This account will be used to patch the bank pin solver used by OSBot (which is currently broken due to the recent update). Thanks for your time. -Alek
  7. Alek replied to PhilipJFry's topic in Archive
    I've seen you around and can't wait to start seeing some scripts on the SDN. Welcome to OSBot
  8. This release is aimed primarily at scripters, however I'm sure botters will find a few new useful features as well. Changelog: -Moved all Settings menu options to Settings Interface -Added debug tab to settings menu -GameConstants class now has most of the debugging variables -Renamed "Add Account" to "New Account" -LocalWalker walkPath method toggle run mid-path at 30 energy -Worked on random event activation - thanks @Pug -Added AttackStyle enum to Combat class -Added getAttackStyle method to Combat class - I promised I'd add more API (). The most apparent change is that all the debug options are centrally located in the debug tab of the settings interface. The "Check for updates" button is now located on the About tab. I'm almost done working on random events to a point where I'll hand off the remaining portions to API Developers. Completing random events alone is overwhelming, so for now I highly suggest not enabling them or using the "Dismiss all" option. Also, for a list of upcoming updates please visit: http://osbot.org/forum/topic/61397-official-osbot-todo-list/ Thanks for your support, -The OSBot Staff
  9. The button is Connect/Disconnect in the bottom left and the error message has been updated in 2.2.34. Thanks for the report!
  10. This is more of a fail-safe than anything. I want the botter to stop the client from doing anything for random events in case dismissing random events and solving them both break.
  11. http://osbot.org/forum/topic/60660-osbot-1-scripts-and-osbot-legacy-api/
  12. He's working on RS3 and is pretty much done. I think the only thing left is for Laz to do his part.
  13. I'll definitely work on some API next, promise!
  14. This update was mainly a quick stab at trying to beef up OSBot with some quick optimizations along with a few other quick patches. Some of these optimizations now include: -Only loading random events which you are using (previously it would load all the randoms) -Disabled repaint of bot tabs while the bot panel is hidden -Disabling FPS debug* *It appears that the calculations for determining the current FPS were a bit resource intensive (it was still calculating even if the FPS debug was disabled). At a later time I'll bring back the FPS debug with an option to actually turn it off. The following account settings have been improved: -Removed frog cave random event -Removed strange plant random event -Removed run away from combat random event -Removed loading pause random event -Removed security book random event -"Dismiss All" option now dismisses all random events The following client functionality improvements have been made: -The login button is now called "Connect" when you are disconnected and vice versa -The human input button is now fully functional -The login error message has been updated Sincerely, The OSBot Staff Also give a large, warm, suffocating hug to @Zach for resolving my devastating code merging issues.
  15. I wasn't drunk, the button was originally top left. The big "Login" button at the bottom left of the client should have been relatively easy to find. I'll update the error message though.
  16. A box unchecked means when a random event appears, the bot will not try to solve it. A box checked means that the bot will solve it. If "Dismiss All" is checked and a checkbox becomes disabled, it means that the random event will be "Dismissed".
  17. We do, I posted it at the bottom of my post to you: http://osbot.org/forum/topic/60660-osbot-1-scripts-and-osbot-legacy-api/ It's located in the community forum.
  18. "Dismiss All" is an option for randoms which you can dismiss. You cannot dismiss an experience lamp, dismiss yourself from the frog cave random, etc. A few of the other random events are getting their dismissal code created. You are safe not doing anything with a random event (aka ignoring it). The random event will eventually just leave you alone and disappear.
  19. I deleted the previous posts because I'm the only one (besides the other devs) that is in a position to talk about it. First, I would like to say that I'm sorry you (along with many others) had a short-lived product. However, the scripts you buy are created by third parties (scripters) and sold under our domain. The service you pay for here at OSBot is membership, not the scripts themselves. When we released OSBot 2, all the OSBot 1 scripts became outdated due to a complete re-work of the API. In order for our bot to survive, this change was necessary. We informed scripters many months in advance urging them to update their scripts for the OSBot 2 release. Only a handful of scripters actually did and the remaining scripters went either inactive or created new scripts for OSBot 2. The premium scripts that did get ported to OSBot 2 were allotted to customers who had the OSBot 1 version for 30 days. Why 30 days? Simply because it's unfair to the scripter. As mentioned previously, OSBot went under a huge re-write requiring scripts to follow suit. "Porting" an OSBot 1 script to OSBot 2 wasn't a simple transition and many of the behaviors changed therefore the logic scripters previously used changed as well. This all required a lot of time and by the end of it, the "ported" version was essentially a new script altogether. The transition happened about 7 months ago and I find it astonishing that for some reason the last 4 weeks I get a topic every day about it. Each topic goes something along the lines of "Hey I left botting for a few months and I came back and my scripts are gone". Hopefully this answers all your questions. If not, you can find more information here: http://osbot.org/forum/topic/60660-osbot-1-scripts-and-osbot-legacy-api/
  20. Dial up doesn't get 2MB download or 50 ms pings. I had it for a large majority of my life
  21. This is what happened: http://osbot.org/forum/topic/60660-osbot-1-scripts-and-osbot-legacy-api/
  22. Yep, I think Genie really needs to be its own event.
  23. Frog Cave - Won't dismiss because you can't "Dismiss" once you are already in the cave Frog Queen - All npcs are called "Frog", looking into if there are other npcs besides randoms called "frog" Maze - Already handled by "Mysterious Old Man" (I suppose I could disable this one) Lost and Found - Don't even know what this is, I'll look into it Pinball - I don't know the NPC that asks you if you would like to start the random. A troll maybe? Surprise Exam - I don't know the NPC that asks you if you would like to start the random. Dragon Teacher? XP Reward - Can't dismiss an xp lamp in your inventory Mysterious Box - Solves a mysterious box in your inventory, you can't dismiss it Pillory Cage - I don't know the name of the NPC that asks you if you would like to start the random. Prison Guard?

Account

Navigation

Search

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.