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/12/15 in Posts

  1. ok it is pretty shite
  2. MALDESTO HAS SPOKEN! LIKE THIS POST!!! Pls no banarino.
  3. Then the heavy artillery comes in. Thank you @Dex.
  4. Lately OSBot has seen an increase in activity as we have reached a new stage, which is why I'd like to thank our developer team and script writers for their hard work. But without our community all of this wouldn't have been possible, which is why I decided to host this event for all of you OSRS players and botters! The event is an interactive happening and will take place in Oldschool Runescape. As the title says, this will be a riddle event. Let's explain how it will work. First of all, when the event starts, I will post a riddle on a locked thread so you can check the riddle whenever you want to. Secondly, the hard work is for you. You will have to solve the riddle and it will lead you to a specific location in Runescape. @Oliver will be my accomplice on this as he will be the one hiding. The first person to find him, receives a point. The exact procedure on how to win a round, will be explained later on. There will be a total of 5 riddles (don't bother searching for them on the internet because you won't find them, I made them all up myself). Make sure to have your teleport necessities, possibly some food and other supplies ready before the event starts! After you've found @Oliver, you have to complete this procedure in order to gain the point and win the round. The first thing you have to do is, find @Oliver. You then need to take a picture on which I can see both the answer/action when you've reached the correct location he'll be there somewhere and will have registered the rs name of the first person to tell him the correct answer or execute the correct action, you can take a picture using Gyazo/Puush/.... Forward the picture to me (@Dex) using the PM system. We will compare and if we deem the picture to be legit, you will be the winner of the round. Keep in mind that only the first person to give @Oliver the correct answer/action ingame will receive a point, after that he will be moving to the next location. Date: 26 April 2015 Time: 20:00 (8 pm) Timezone: GMT+1 Click here to see the time of the event on your location If you win a round, you will be awarded with a point. The prizes will be rewarded as followed: 1 point: 3 months of 2 points: 6 months of 3 points: In addition to this @Eliot will be granting you a 60 day auth for a DreamScript script of your choice for users with one or more points. This is how a riddle will look like. It will contain the information which will lead you to a specific location in Runescape. (this is just an example) Question: what is Martin Luther King's most known sentence? If we take this one as an example (the actual ones will be more difficult), the answer to this riddle is the essence mine in Varrock. The answer to the question is 'I have a dream'. You'll have to say the "I have a dream" when you reach @Oliver ingame and take a screenshot of it with your rs name still visible. Some people might think that there will be a mass ban when you participate in this event. I have also taken this into account upon creating the event. Because we do not have one specific location (e.g.: Warrior's Guild) it will be harder to even impossible for Jagex to bust us. OSBot cannot be held responsible for any bans/mutes during/after the event! We hope to see YOU at the event! ~The OSBot Team
  5. Because you are banned from the chatbox.
  6. i removed some stuff similar to my logo (edit: remove this post plz i didnt read about transparency)
  7. 4 points
  8. Hello sjmabs, Follow those steps and you will be VIP in no time. Step 1_ Click Here Step 2_ Find VIP Step 3_ Click IT! Step 4_ Click RENEW And enjoy your Smexy Purple Name. and of course the extra Features! Kind Regards, YoussefSalmo Credits to this guy as well... Verified
  9. My VIP runs out on like May 5th or so, so please add it before that.
  10. Ever been banned? Banned even using the most premium of scripts? Banned while only botting for a couple hours? Well, I have a theory as to how JaGex is distinguishing humans from bots apart from injection. Before I go further, let me brief you on something most programmers know and most others don't. Let's say you're cutting maple logs at Seers. The moment that tree is cut down, I have a feeling JaGex takes note of the time that action was completed as such: 21:59:46: Your tree was cut down. (completed action) JaGex may also take note of the time you begin your next action and what it does. Then you click on the next tree available, or in this case, the same tree after it respawns: 22:00:16 Player begins cutting another tree. (new action initiated) We find that the difference in time the action was complete and the next action was initiated is 30 seconds (21:59:46 + 00:00:30 = 22:00:16). Imagine doing this for hundreds of hours and that difference between completed action and next action is ALWAYS 30 seconds. Pretty predictable and bot-like, wouldn't you say? To counter this, most programmers would know to wait a random duration after the completed action before starting the next one. The code in bot scripts have something along the lines of "Sleep(1-6);". What this entails is the bot to wait anywhere from 1 second to 6 seconds before starting the next action. In theory, this would make it harder for JaGex to spot a pattern; however, it's just as easy to spot a bot-like pattern. Throw a 6 sided dice 100 times. What's the probability that 1 was rolled? It'll be roughly the same as 2, 3, 4, 5, and 6 (~0.17 x 100 = ~17% chance for a number to be rolled) As expected because rolling a dice should be random. The probability of each face of that dice should be the same as the next face of that dice. Nonetheless, human behavior is not nearly as related to the randomness of throwing a dice. Humans are inclined to lean a particular way. So when it comes to time between completing tasks and beginning another, it's not going to look like the graph of 100 dice rolls. It may look more like this: All while the graph of a bot might look like this: I'm not much of a programmer myself, but this theory does have some merit to it. If you can add to this, please do so below. If you think this is a bad theory, please let me know why. Also, let me know what you think JaGex does to distinguish humans from bots. What's the fix? How do you program "human behavior" into code? That's difficult; however, there may be an easy, temporary solution. Random numbers in the Java code currently are thrown through a Math method called a random number generator. Perhaps we could roll 2 dice instead of one and get something that looks a little more human-like:
  11. http://s73.photobucket.com/user/mainmenu685/media/20150412_134808%201.jpg.html Picture states enough ;)
  12. I will gather you a list of themes. And maybe something to motivate more people to participate in the competition.
  13. I'm not sure you understand the question. Are you asking how to check the ID of an object ? if so go into settings and open the 'Entity Debugger'. Then hover over the entity in question and it will tell you the id. Or.... Did you mean how do you get the id of an entity dynamically in the code? Entity e = objects.closest("name"); int id = e.getId(); Apaec
  14. Guys if you don't wanna pay what he is selling the account for then don't buy it. Otherwise just bid or leave.
  15. Lol dex. I vote scotty's
  16. Awaiting the hammer --> Avoids macroing ban on rs --> Gets banned from the botting client instead That'd be so lol
  17. Should be proud or concerned? The plot thickens (Not Paid Actors)
  18. isVisible doesn't work for game objects, interactions with objects seem slower
  19. 2 points
    Just bought this, testing it out on my main, I'm looking it so far! Literally I can let this run and watch porn and fap fap fap for hours and hours. But in all seriousness I'm gonna try and test this by running it for 500 hours with no breaks. Wish me luck! -- I'm a in-game mod to ;D
  20. Hey! I've been working on some independent projects recently, so I haven't been able to be part of the community. I finally have some free time, so expect more guides and info For those wanting to contact with me during these "independent" stages, feel free to add me on skype! sincerely.vince I've mentioned before, I'm not a botter (or even a bot scripter), but I'm very experience in terms of computer science, so let me know if you wanna expand you programming knowledge!
  21. Its like dog poop vs golden nuggets.
  22. 1 point
    Holy shit that made me laugh so hard
  23. 1 point
    I love my country
  24. Pretty sure this went really well the first time, plus I helped take a screenshot with Dex!!!!!!
  25. Wew pls pick places that require no quests , kthx. Very nice giveaway doe ^_^
  26. Cheers for this script mate, works great. Thanks for adding all the features i've suggested too ^ got me 50-85 strength with this without any problems.
  27. thanks range xp is showing up now but the camera keeps going up and down continuously very botlike when there isn't a monster nearby edit: and now range xp is not showing anymore again after i restarted the bot.. Did u put me as bought script or trial maybe im not getting the right updates now when i restarted the bot the range xp shows again its just the camera keeps going up and down i think its very botlike
  28. <3

    1 point
  29. Im using a toxic blowpipe but it still tracks my strength xp and doesn't recognise my ranged xp and it keeps doing camera up and down when it cant find the experiment continuously instead of clicking on minimap..
  30. Alright i guess it's still the path issues, don't worry i will fix waterbirth :P
  31. http://gyazo.com/ed24b8a31ef4dac8c9d0799ec1cf8d0a
  32. 1 point
    You either have flagged IP or used bad scripts. Also I recommend using mirror client instead of the standard one(VIP required).
  33. looks like I'm going to buy it DAMN YOU CZAR. Cant wait to use it :P
  34. 1 point
    You want getLocationOnScreen(). getBounds() returns the locatiom of the component relative to it's container, not your screen
  35. Does - Using pre-loaded locations from the list and not interactive world map work for banking atm? Or only for powercutting too? Great work Czar, now only if you can make a perfect agility one :P
  36. GAve you 24 hours Ya sure, gave you 24 hours ^^ Yep, use previous version of osbot, the newest version of osbot has bugs. Granted you a 24 hour trial Khaleesi
  37. 1 point
    Nice. I just need a better video card tho.
  38. 1 point
    Just get the 45def. Its not a big deal when pking at all.
  39. 1 point
    Not anymore.
  40. TBH I just cleared everything (deleted jagex cache, random.dat all those myths), changed my ip (again, possibly another myth) and created a new account for mirror mode. Seems to be working brilliantly for me i'm currently on day 11 with 80 80 80 combat stats.. But then again I use private scripts so..
  41. 100% you didn't get banned from 3 hours of use, you got banned for botting previous and you got delay banned.
  42. Dear community, Prepare for a long but awesome read! I feel like giving you all an insight in what has been happening behind the scenes of OSBot lately and what is to come. We have been working hard in the last couple of months to get the bot back where it used to be in the summer/autumn days of 2013. Fixing issues with the API and the bot is one part of that. The other part exists of creating new innovations and adding new features to keep up with other bots or to make OSBot unique and innovative. These were things we were doing quite nicely back in the days and it's time to reclaim this glory. Many of you must have noticed that MGI was added to the team as a developer. With this promotion we also promised to find a solution for the high ban rates that we, but also other bots, are facing. Ban rates. Detection of bots can be divided in two main strategies. The first strategy is detection on a low level, this means detection of the modified RS client. The second strategy is by analysing behaviour of players. Both can be extremely efficient at what they do. Combined they do a pretty good job, considering the banning rates some people are facing on any bot they use. The first strategy is done by detecting whether the RS client that runs is modified or not and whether it is running in it's natural environment. The way current way most bots work is by downloading the RS client and modifying the client to be able to communicate information of the game with the bot engine. There are ways around it, but the way RS currently has their system set up means that battling their strategies to detect bots on a code level are meant to break and would require a lot of updating. Basically using a bot these days or for example RSBuddy (a runescape helper, not a bot) just plain out tell RS that they are bots. The second strategy is behavioural analysis. By having intelligent systems that compare behaviour of players/bots and compare it to statistics they have of players that are proven to be bots, they spin an entire web of intelligence that could recognise bots. This they can't obviously do for every player, so they most likely have different monitor levels, where each level higher means that the behaviour is analysed in more detail. Those two strategies are then probably combined, where the first strategy is probably the main flagging system to be upgraded to monitor tier 1. Monitor tier 1 then monitors on a global big picture view. Botting times, activities, quests being done, experience gain, trading activity etc. If monitor tier 1 suspects suspicious behaviour, your account will be moved in to monitor tier 2 which might analyse mouse behaviour or other more in depth and resource intensive analysis. From there there might be more tiers until you get banned. This of course is speculation. Having good scripts does lower the chance on detection by a lot. Changing scripts, having different behaviour on the same scripts by two different users, intelligent and human like action etc can all make a difference. But these won't make a difference if a bot basically says it's a bot based on a technical level of the code. So what is the solution? The theoretical solution seems simple. Come up with an idea that has no possible detection on a code based level. The implementation of it however is far from easy. Now to the interesting part: MGI has been working on an idea conceived several months ago and is nearing its completion. We call it the mirror system. The mirror system should tackle strategy one completely. OSBot's new Client Mirror System. Before blabbing about all kinds of technical details here is a picture of what it looks like. A picture is worth a thousand words they say. MGI called this feature the Client Mirror System. It leaves NO trace in the RS client of our bot and is by no means visible on the JVM. The RS client runs in its own environment which makes it even better. You still have all the controls you had in the past. This could potentially knock out the initial flagging system that takes your account in to monitoring. We don't know for sure how their system works though, but this completely diminishes the detection on a code level base. This feature does require additional CPU, so the future will have to show how much of an impact it will have if you use this for big bot farms. We will however provide you with the option to use the old injection system or the new Client Mirror System and they will be able to be used in a mixed fashion if you prefer. In any way, the performance overhead might be worth it for everyone in the end. Work is still being done on finishing the entire feature including optimizations. Other planned features. OSRS update handling. We will provide a system that will handle with OSRS updates. Once the bot recognises there is an update about to happen, it will log your account out or wait for the disconnection. After that it will wait for the new hooks to become available on the server and reboot the RS instance. The moment when this reboot happens will of course be randomised so that not all OSBot users log back in to the game at once. After the reboot the script will continue where it left of. Grand Exchange API. With the GE released we will be providing an API for scripters to use the GE. OSBot client chat. I have written a server module that will be able to route chat traffic to and from the server and supply it to the forum's IP.Chat module. Users will be able to chat with the people on the forums and vice versa. We hope this feature will increase traffic to the forums and give people something to do when they choose to baby sitting their bots. I hope you had an interesting read , Sincerely, The OSBot team UPDATE:

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.