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.

Leaderboard

Popular Content

Showing content with the highest reputation on 04/30/13 in Posts

  1. Hey guys, I've had this 1.22$ sitting in my paypal for months. No need for it. Figured I would let one of you put it to use. Simply pick a number 1-10, and I will pick a random number by using random.org. Rules: Must have 10 post count or greater. Must 'Like' this thread. 1.Link 2.specops5000 3.Angel 4.Medic 5.Brett 6.mhmd21 7.Wiz 8.zweetkonijn 9. Xerion 10.Kyle CONGRATS TO BRETT! PM me with your paypal!
  2. 2 points
    OSFletcher - by Daniel Current Version: 3.0 (06/21) - Supports OSBOT 1.7.X Price: FREE Status: Running perfectly Feel free to donate to me if you love this script. Welcome to OS Fletcher! This script supports all type of bow fletching, from regular shortbows, to magic longbows. This script will run for hours on end with no glitches or problems. To use, simply add OSFletcher to your scripts on the store and run it from your remote free scripts on OSBot 1.6.x. If not running on 1.6.x, download the jar file at the end of the post, add it to your script folder (no unzipping or copying/pasting necessary) and run the bot from any bank in Runescape! - I would suggest running it in the Pest Control bank, however, since there are no randoms. Have fun and enjoy the script! Remember to leave an progress report! IF FLETCHING START WITH KNIFE IN INVENTORY. MAKE SURE YOU'RE ON THE LATEST OSBOT VERSION (1.4.2) Report any problems and I'll get on them ASAP. I can't stress this enough. I can't improve this script unless people explain errors with as much detail as possible. Update Log: V1.0: Release - Known issue with banking, bot failsafes and it works anyway though - just slows it down a bit. Will fix next release. V1.1: Fixed banking issues V1.2: Added a method to deal with leveling up V1.3: Stringing is now supported. V1.31 Theoretical fix for leveling up problem. Also switched from zip to jar. V1.32 Some bug fixes, stringing should be flawless now (with double clicks). V1.40 Fixed xp/hr on the paint and now continues on level up. V1.41 Fixed magic bows not fletching. V1.42 Really fixed magic bows. Also added a lot of speed improvements. V2.0 Support for OSBOT 1.4.1 added. Massive amounts more of xp/hr. Support for every bank booth added. Updated paint slightly too. V2.01 Fixed withdrawing bowstring issue. V2.02 Fixed level up on last log/bow. V2.10 Massive speed improvements on stringing. V2.20 Updated to support fletching regular shortbows and longbows. V2.21 Addressed banking issues. V2.30 Addressed more banking issues. V3.00 Completely re-coded, fixing banking and knife issues. (Bot currently says 2.0 not 3.0). Current problems: None To do: Add more anti-ban More sophisticated paint (will do on next bot update)
  3. It has come to the attention of the OSBot Team that the main developer of vInsert, Discardedx2, was involved with logging all usernames and passwords of his community. We'd like to warn anybody who was registered with vInsert and used the bot at all to change their passwords immediately. We'd also like to state that OSBot is a professional operation. We are soon going to be a registered company in the Netherlands and that we would never engage in something as low as hacking our own members. However, due to the recent hacking, we are going to be increasing the security we have implemented in the OSBot client itself to make sure that a situation such as this one would never be able to happen on OSBot. This includes implementing multiple styles encryption such as MD5 and RSA to protect your passwords. Moreover, to reassure your security, all of your passwords are encrypted and salted using MD5 on our database. This means that we do not know anybody's passwords, rather, when you are logged in, the MD5 hashes are compared for authentication. The developers of OSBot, Maxi and I, are reputable members of Rune-Server. I'ed like to say that honestly hacking our own members accounts would not benefit us in anyway. We hope that now that vInsert is dying, OSBot will become the #1 bot for OSRS. tl;dr: Change your password if you've ever used vInsert. Sincerely, Laz and the OSBot Team.
  4. its cool. If you keep people informed then i doesn't matter if the update get delayed... And we understand that the personal life have an impact on the bot...
  5. I'm sorry for the delay of this release. I have spend more time than initially calculated to do a couple of these updates, and today and yesterday our country was completely in party mode because of the crowning of the new king, an event I of course had to attend. I will work as hard as possible to get this release out within 2 days.
  6. 1 point
    works great, brilliant coder tyvm needed this!
  7. 1 point
    Looks cool I'll be using the withdraw method thanks
  8. Here's a method I wrote: public int experienceForLevel(int level) { double total = 0; for (int i = 1; i < level; i++) { total += Math.floor(i + 300 * Math.pow(2, i / 7.0)); } return (int) Math.floor(total / 4); } You can then use this to get the xp to level: int currentAttLevel = client.getSkills().getCurrentLevel(Skill.ATTACK); int currentAttLevelXp = client.getSkills().getExperience(Skill.ATTACK); int nextAttLevel = currentAttLevel + 1; int nextAttLevelXp = experienceForLevel(nextAttLevel); int xpToLevel = nextAttLevelXp - currentAttLevelXp; And then just a simple xp/hr if you need it. int attExpHour = (int) ((3600000.0 / runTime) * attExp); int defExpHour = (int) ((3600000.0 / runTime) * defExp); int strExpHour = (int) ((3600000.0 / runTime) * strExp);
  9. I developed some paint for a friends script, suggestions on what to do with it to make it better would be much appreciated. V2:
  10. I will destroy you.
  11. How long did the transaction take? About 10 minutes. Service Completed/Item Bought: Membership. Payment Method: OSGP Would you suggest me to others? Yes. Very quick and trustable. He went first.
  12. 1 point
    Please someone make one that works....
  13. I noticed that a few people have been complaining that the scripts have to be written in Groovy. Groovy is based on the Java Virtual Machine so that means that you can use the same syntax as you could with Java and place it inside the groovy file. This simply means that you would take a normal Java Class file and create a regular script such as the demonstration below and you would simply change the extension on the file from .java to .groovy. The downside of this is that you will obviously not be taking advantage of the additional features that Groovy has but Java does not. The only file that needs to be a groovy file is that file that is a subclass of org.osbot.script.Script. Below is the old tutorial beacuse I wrote it in two seconds. This will be a simple short tutorial since people are complaining about how we have to write scripts in groovy and blah blah blah. Groovy uses the Java Virtual Machine so obviously almost ALL Java syntax will work correctly with groovy. Now basically what you will want to do is create a groovy file. and have something like this inside of it import org.osbot.script.ScriptManifest;import org.osbot.script.Script; @ScriptManifest(name="ScriptTest", author="Billy", info="An awesome test script.", version=1.0d)public class ScriptTest extends Script { @Override public int onRun() { return 0; }} You can use normal java syntax and create additional class files that are used inside of it. The only file that has to be a groovy file is the file that is a sub class of org.osbot.script.Script otherwise it doesn't matter. Sorry this is in a rush I'll add more to it later.

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.