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.

Leaderboard

  1. Maldesto

    Administrator
    24
    Points
    19230
    Posts
  2. Dylan

    Trade With Caution
    14
    Points
    2949
    Posts
  3. Simon

    Trade With Caution
    14
    Points
    1241
    Posts
  4. Bug

    Trade With Caution
    13
    Points
    1262
    Posts

Popular Content

Showing content with the highest reputation on 02/01/14 in all areas

  1. Is removed Like dis post. Don't really care if you have a lot of likes, it doesn't make your e-peen bigger. Rule gone.
  2. PL0x someone like this for no reason
  3. swapping likes for likes!!!!!!!!!
  4. In that case.. where's the dislike button?!
  5. amg pls like i'l like you tooo xxxx
  6. I think that is common sense, there shouldn't need to be a rule to keep people from doing this.
  7. So I can make a new account, and go like all my shit... Make>Like>SignOut>Repeat?
  8. like this for no reason lulululul
  9. my comment never gets any thumbs up shit wrong site
  10. must be sad to do that---like this
  11. You've been bashing our bot for a while now, i think it was just a way for you to get out. You kept logging in daily, you have 48 hours to pay back. You went offline without replying to his chat. He messaged you 5 times and you went offline and didn't reply. So no I was not fast to ban you, you are just a scammer.
  12. Overview: Many users are unaware of how to properly submit bug reports, a vital communication tool between users and scripters. Bug reports provide scripters with the information they need to fix bugs and issues in their scripts. I've decided to create this short guide to teach everyone how to submit an effective bug report to ensure minimal downtime of their favorite scripts. This guide may seem obvious to some, but it has become evident it is necessary. Before Submitting Report: Before even submitting the bug report, make sure the following statements apply to you completely. I am exactly following the scripts instructions. I am using the newest version of the script (if local download). I am using the newest version of the OSBot client. I am using the newest version of Java. I am NOT using low CPU mode. If and only if you answered yes to all of the above questions should you submit a bug report. Do not submit a report about anything related to random events, these are not controlled by the script. What to Include in Report: Include at a minimum the following in your bug report: Client version Script version Date Low CPU mode? What caused the bug to occur/when did the bug occur? Where was the character when the bug occurred? Screenshot (if applicable) Providing all of the above information will allow the scripter to quickly assess the issue and fix the bug. Do not post anything vague in your report as this only leads to confusion. Where to Submit Report: When submitting your bug report either post it in the script's thread or send the script writer a private message. Posting a bug report anywhere else is entirely useless. Example Template: Client Version: Script Version: Date: Low CPU Mode (yes/no): Bug Description: Bug Occurs When: Where Bug Occurs: Screenshots (if applicable): Examples of Good Reports: Examples of Bad Reports: Thank you for following this guide, Eliot and the OSBot scripters thank you!
  13. 2 points
    I'll buy, add me on skype: probemas
  14. 2 points
    “I'm selfish, impatient and a little insecure. I make mistakes, I am out of control and at times hard to handle. But if you can't handle me at my worst, then you sure as hell don't deserve me at my best.” - Marilyn Monroe
  15. And nobody cares about a skid with a booter.
  16. That moment when i remove the like rule just for 10 mins to get likes then add it back hahahahahah
  17. Anyone wants to trade scripts for likes :3?
  18. WTF? Remove this shit so I can like everyone's comments....
  19. Buying likes 100k
  20. Give me a like kthx
  21. yeah nice nice ^.^
  22. I've never heard of this game.
  23. Overnight 60 attack pure proggy: http://puu.sh/6FO1X.jpg
  24. We aren't your parents to hold your hand when you need to study, request denied. * Locked * Archived
  25. Updated for OSBot 2's API! Hello future script writers and other OSBot members! This will be my first OSBot script writing tutorial, and it's geared toward beginners with at least some understanding of Java (however, I'll still be covering some fundamentals). So, let us begin. Step I: Getting the IDE An IDE (integrated development environment) is software that makes programming much easier on you, the programmer. There are many Java IDE's to choose from (IntelliJ, NetBeans, Eclipse, and many more), but for this tutorial, we'll be using Eclipse. You can download Eclipse here. Simply choose the Eclipse Standard and download the version for your computer (32 or 64 bit). Once downloaded, use a program to decompress the archive, and move the eclipse folder to wherever you'd like (C:\, your desktop, it honestly doesn't matter). To open Eclipse, go into that folder and open the Eclipse application. Congratulations, your one step closer to making OSBot scripts! Step II: Basic Java Fundamentals Java, like C++, PHP, and Javascript, is a high-level programming language, which simply means it's very readable by humans (we use English while programming in these languages) and therefore much simpler to write code. If you're an absolute beginner, with no background in programming at all, this is going to go by extremely fast, and I will likely skip over some important topics. If you fall into this category, you absolutely NEED to read these tutorials by Oracle. I'm not sure about most of you, but I feel that a great way to learn something is to dive right in, and worry about the little things after you've started to understand the bare essentials. With that in mind, let's take a look at a simple HelloWorld class: public class HelloWorld { public static void main(String[] args) { System.out.println("Hello World, I'm learning Java!"); } } Now looking at that might be intimidating if you're new to this, but believe me it's very simple! I'll break down some of the common words used above: public: This could be public, private, protected, or default. It simply states the visibility of this class/method/variable. Public items can be seen from outside of your package, private items can't be seen by other classes in your package, protected items can only be seen by the subclasses of your package, and default can only be seen by your package. class: A class is like a blueprint from which objects are created (Oracle). static: This is a keyword that simply means that only one instance of it will ever exist, even if you recreate it infinitely. void: This is the return type of this method. Void methods return nothing, int methods return integers, String methods return strings, and so on. String[]: This is an array. Arrays are just containers that hold a specific number of items (of one type). For example, this method takes an array of strings as a parameter. System.out.println: This is just a method that prints a message to the console and then prints the newline character. ;: Semi-colons are used at the end of any Java statement (note: conditionals and loops do not count as statements), without them, your compiler will give you errors. { }: These curly braces are used to surround/contain the contents of a class/method/etc. This is all of the Java basics I will teach, simply because there are already many resources out there (see above). Step III: Setting up a Java Project Setting up a Java project in Eclipse for making OSBot scripts is simple, just follow these steps: Step 1: Press File>New Java Project and name your project, then press finish Step 2: Add the OSBot .JAR file to your build path Step 3: Add a class to your new project And you're ready to actually start script writing! Step IV: Creating Your Script Now here's where we actually start making your script! For this example, we'll be creating a very simple mining script that will mine and drop everything once the inventory is full (please note: this example is hardly usable for a script, but it shows the basics. With a real mining script, you'll want to replace the object name with the ID(s) of the rocks, so you don't try mining empty veins). Here's the full source: import org.osbot.rs07.api.model.RS2Object; import org.osbot.rs07.script.Script; import org.osbot.rs07.script.ScriptManifest; import java.awt.*; @ScriptManifest(author = "You!", info = "I made this script!", name = "Basic Miner", version = 0, logo = "") public class BasicMiner extends Script { private enum State { MINE, DROP }; private State getState() { if (inventory.isFull()) return State.DROP; return State.MINE; } @Override public void onStart() { log("I can't believe script writing is this easy! I love learning!"); } @Override public int onLoop() throws InterruptedException { switch (getState()) { case MINE: if (!myPlayer().isAnimating()) { RS2Object vein = objects.closest("Rocks"); if (vein != null) { vein.interact("Mine"); } } break; case DROP: inventory.dropAll(); break; } return random(200, 300); } @Override public void onExit() { log("Thanks for using this wonderful script!"); } @Override public void onPaint(Graphics2D g) { } } Now most of that will be confusing, but don't worry, I'm here to help you! I'll break this down for you. import org.osbot.rs07.api.model.RS2Object; import org.osbot.rs07.script.Script; import org.osbot.rs07.script.ScriptManifest; import java.awt.*; These lines import other classes for their use in your script. @ScriptManifest(author = "You!", info = "I made this script!", name = "Basic Miner", version = 0, logo = "") This is the script manifest, which simply tells OSBot your script's author, info, name, and current version (for use in their class loader). public class BasicMiner extends Script { ... } This just defines our class, and extends OSBot's Script class, so we can use all of their fancy API methods. private enum State { MINE, DROP }; private State getState() { if (inventory.isFull()) return State.DROP; return State.MINE; } Here we make an enum (collection of constants) called State which holds two states: mine and drop. Then we have a method that's return type is State (so it returns a State, which we just made). If your inventory is full, this method will return the dropping state, otherwise it will return the mining state. @Override public void onStart() { log("I can't believe script writing is this easy! I love learning!"); } This method is part of OSBot's Script class (which we're extending from). The onStart() method is only called once, and is called at the beginning of the script. This is where you should define some variables that only need defined once (the start time, start experience/level, etc.). @Override public int onLoop() throws InterruptedException { switch (getState()) { case MINE: if (!myPlayer().isAnimating()) { RS2Object vein = objects.closest("Rocks"); if (vein != null) { vein.interact("Mine"); } } break; case DROP: inventory.dropAll(); break; } return random(200, 300); } This is another method from OSBot's Script class (see that @Override?). onLoop() returns an integer, or how many milliseconds to wait before doing onLoop() again. We then use a switch statement to see what we should be doing. If we're to mine, we check if our player is currently animating (mining). If we aren't, we find the closest rock to mine, if that doesn't exist (or is null), we stop right there. But if it isn't null, we interact with the rocks by pressing "Mine". If we're to drop, we simply drop everything in your inventory (you did have your pickaxe equipped, right?). @Override public void onExit() { log("Thanks for using this wonderful script!"); } @Override public void onPaint(Graphics2D g) { } onExit() and onPaint(Graphics g) are two more methods from the Script class. onExit() is called once your script is stopped, and onPaint(Graphics g) is called every time the screen is updated. Step V: Exporting Your Script The final step to this tutorial will be exporting the script we just made so we can actually test it out! Step 1. Right click your project and press Export... Step 2: Choose JAR file Step 3: Choose your OSBot's scripts directory and export it! Well that's all for this tutorial, thanks for reading! You can find Part II here! Also: post suggestions for future tutorials, and I'll definitely consider it!
  26. Hey all, I've just opened my own teamspeak client that I planned to use to manage my AIO service workers, I thought instead I would open it to all of the OSBot community. Come and join in! Try earn yourself some cool ranks and be part of the OSBot Teamspeak client EVERYONE IS WELCOME Server adress: austs1.gameservers.com:9560
  27. 1. Pictures of the account stats http://gyazo.com/99315127202054bd3911d15af7f6b861 <--- eoc stats http://gyazo.com/29309e27ae2675db5fd709545e880898 <--- 07 stats 2. Pictures of the login details http://gyazo.com/6a8e80884cddca0abe8076abbf91e561 <----07 log-in http://gyazo.com/5667da797aee1454f38a6d69fbd0c521 <----eoc log-in I have no idea how to delete recovery questions so whoever buys we can screen share on skype or something and you can show me how to delete them, also email will be changed to yours on purchase. 3. Pictures of the total wealth (if there is any) http://gyazo.com/71046934a9d2ce645b53c64c893fdd94 <---eoc pic 4. Pictures of the quests completed Waterfall - lost city - rune mysteries - was only meant for staking and green drags - 07 http://gyazo.com/77b85549e447e521d84c8af6e5e8374f --- eoc http://gyazo.com/ffe7f06dfe89a9a3a86caacf3485432d --- eoc 5. The price you will be starting bids at 10m 07 - 100m eoc 6. The A/W (Auto-win) for your account 50m 07 - 500m eoc 7. The methods of payment you are accepting 07 gold or eoc gold 8. Your trading conditions I'll only go first to trusted members with reasonable amount of feedback. 9. Account status 39 days of membership letft 10. Original/previous owners AND Original Email Address I'm the only owner. Never shared the account before. Email will be switched to yours on purchase
  28. post on here or add my skype "L3reed"
  29. 1 point
    With 11 Posts and 0 Feedback? -- Gl not going first LMAO
  30. 1 point
    Use the break system. Also moved to correct section.
  31. 1 point
    How can you add -lolmanden When the whole quote was used be christ knows how many people "u must b fun at parties" incoming
  32. 1 point
    Some guy I know sells them and they're real tough some police even came asking to stop selling them as they weren't happy with em
  33. Don't take it wrong, but if I can the same offer from a guy who has 170+ successful trades and no negative ones, who would I choose. Start off with smaller trades to get rep And don't dare question my mama
  34. sup

    1 point
    Hi and this is me.
  35. Hahahaha, well played sir.
  36. Naruto... 1 episode a week -.- it's driving me nuts. I like you're art work, you're clearly talented you should create a manga! I wish you luck.
  37. Doesn't hurt to give a little hand to others, let's play nice.
  38. I know you were warning us, and I was telling you to post a dispute so other members don't get caught by the same thing and we can ban the user that scammed you. Don't get all aggressive.
  39. 1 point
    I think this will further ruin the game.. They tried so hard to cover up for their failing action (EOC) and made OS, now that everyone has trained their stats.. they want to bring this whole new legacy shit.. I say nawwhhhhhhhhhhh
  40. Could you like, add a decent setting explorer? (or configs as you call it >_>) because this one is.... well... bad.
  41. public void toggleRun() throws Exception { if (currentTab() != Tab.SETTINGS) { openTab(Tab.SETTINGS); sleep(300+random(700)); } client.getInterface(261).getChild(34).interact(); } quick fix until the hook is updated in the api.

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.