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 03/14/15 in all areas

  1. Dear community, Today we celebrate the two years existence of the OSBot forums. Exactly two years ago from now the forums were put online for the first time. In a few weeks from now the first release of the OSBot 1 BETA client was made two years ago and from there on the journey of OSBot started. Two years later and many faces have passed the revue, we are determined to get OSBot back to the top spot we once claimed in 2013/2014. Thank you all for being part of OSBot in good and bad times, it has certainly been a blast so far and may the future bring you glory. Happy birthday OSBot, a big thanks to all the developers and staff that have been working hard lately to get OSBot to the top spot again! Regards, The OSBot team
  2. Dear Mirror Client BETA users, I know it is a tempting idea to see how long you can bot for with the Mirror Client before getting banned but this idea is not smart. Eventually you will get banned if you bot 24/7, regardless of the detectability of the new technology behind the mirror client. This will just offer information to their machine learning system about detecting/identifying the bot, which in the long run will benefit nobody. Please bot smart, not 24/7, take breaks and enjoy. Sincerely, The OSBot team
  3. This update contains a patch that was meant to be in the previous release but for some mysterious reason didn't make it to the final build. It should contain a fix for Widgets.isVisible(int rootId). Thanks @Zach and @Mysteryy. On another note, in the coming week you will see some newly introduced API classes and methods. I have hooked the following hooks for which API logic will be written: ------------------------------------------------------------------------ | Friend | -> name | -> world ------------------------------------------------------------------------ ------------------------------------------------------------------------ | Client | -> friends_list | -> friends_count | -> grand_exchange | -> world_count | -> world_array ------------------------------------------------------------------------ ------------------------------------------------------------------------ | PlayerDefinition | -> appearance ------------------------------------------------------------------------ ------------------------------------------------------------------------ | Player | -> skull_icon | -> prayer_icon | -> combat_level | -> definition | -> team ------------------------------------------------------------------------ ------------------------------------------------------------------------ | World | -> id | -> type | -> domain | -> activity | -> location_id | -> population | -> index ------------------------------------------------------------------------ ------------------------------------------------------------------------ | GrandExchangeBox | -> status | -> item_id | -> unit_price | -> amount_to_transfer | -> amount_transferred | -> spent ------------------------------------------------------------------------ Sincerely, The OSBot team
  4. I don't get why you guys are trying to test this bot's detectability so hard. Okay so Jagex doesn't know what client you're using but then a bunch of people start playing 24/7 doing the same thing over and over and you think they won't start to work harder to detect this? Why not bot normally to try and prolong this bot's success rather than going crazy with it before it's even started.
  5. Hi guys! I'm in the process of developing a Ghoul Killer which I plan to release on the SDN for a small fee, to guarentee quality to my customers. The script will train on Ghouls ( west of canifis ), for huge exp/h rates, ranging from 20k - 60k exp/hour. I will be starting the development of this script potentially over the weekend, if not then over easter (w/c 2 weeks time). Once it is sufficiently stable, I will aquire the relevant graphics and release it on the SDN. I will be updating this thread once i've released it to contain the relevant information about the script + screenshots. Happy botting! Apaec
  6. For as long as I can remember, the account database where you store your RS Account details and preferences suffered from potential deletion every OSBot update. The reasons are a little bit technical and although it was possible to patch the old system, I decided to make a new one. Please note that just like the old system, the new system will store your information in plain text locally. Never give anyone your OSBot files (store.dat, accounts.dat, etc). For advanced users, you can directly modify preferences by opening accounts.dat. The format is currently as follows: username,password,pin,exp,breaks,avgInterval,avgBreak,intervalDeviation,breakDeviation,dismiss_randoms So for instance: test1@aol.com,password1,9999,MINING,f,2,2,2,2,t I know there are a few "mega-farmers" out there that would really appreciate this. TL;DR: You will lose all your account data this update, but future updates will not affect the new account database. In addition the Settings API is going under a huge re-work. Soon scripters will be able to enjoy the full functionality of everything in-game settings has to offer. Changelog: -New account management system -Added SettingsTab enum to Settings --Contains Display, Audio, Chat, Controls --Added Settings method open(SettingsTab) --Added Settings method isTabOpen(SettingsTab) Have a great weekend -The OSBot Staff
  7. I'd just like to add a note here, since I know some people are going to read this and say "Okay no bans lemme bot for 5 days straight" and then get upset and bitch when they get banned. While the mirror client might reduce ban rates (hopefully it does), this doesn't mean you can't get banned. If you're gonna bot dumb, you're gonna get banned. Bot safe please.
  8. Want to buy with OSGP? Contact me on Discord! Detailed feature list: - Task/progressive based setup - Supports cleaning all herbs - Supports making all Unf potions - Supports almost every potion (Attack, antipoison, strength, serum 207, restore, energy, defence, agility, combat, prayer, super atk, superantipoison, fishig, super energy, super strength, weapon poison, super restore, super defence, antidote+, antifire, ranging, magic, zamorak brew, antidote++, bastion, battlemage, saradomin brew, ancient brew) - Creation of super combat potions - Upgrade potions (Stamina, Extended antifire, Extended super antifire, compost, antivenom, divine super attack, divine super strength, divine super defence, divine ran ging, divine magic, divine bastion, divine battlemage, divine super combat) - Tar combining - Item crushing (Unicorn horn, chocolate bar, kebbit teeth, birds' nest, desert goat horn, blue dragon scale, lava scale, superior dragon bones) - Amulet of chemistry support Custom Breakmanager: - Setup Bot and break times - Randomize your break times - Stop script on certain conditions (Stop on first break, Stop after X amount of minutes, Stop when skill level is reached) - Worldhopping - Crucial part to botting in 2023! Script queueing: - Support queueing multiple script in a row - All Khal scripts support flawless transitions in between scripts - Start creating your acc in a few clicks from scratch to multiple 99's - Flawless CLI support - Learn more here: How to use CLI parameters: - Example Usage: -script 598:ScriptFile.BreakFile.DiscordFile SAVEFILE = Saved Filename BREAKFILE = Breakmanager Filename - SAVEFILE: Save file can be created in the GUI. Navigate to the tab you want to run and press "Save As CLI file". Please choose your filename wisely (No special characters) - BREAKFILE (Optional): Breakfile can also be create in the GUI, set the breaksettings you wish to use and press "Save new CLI BreakFile". Please choose your filename wisely (No special characters) - Final form (Note that with some bot manager you do not need to specify '-script 598'): -script 598:TaskList1.4515breaks (With breaks) -script 598:TaskList1.4515breaks.discord1 (With breaks & discord) -script 598:TaskList1..discord1 (NO breaks & discord)
  9. So when is it? I want to get a discounted lifetime sponsor halp please
  10. http://www.dumpert.nl/mediabase/6643882/eef886cd/apple_engineer_over_de_nieuwe_macbook.html
  11. It does matter. It's the only reason why when you use a certain script you get banned in a few hours, Jagex compare your movements to other people's movements therefore if you bot a shit ton and play stupid hours they are more likely to receive this information quicker than if you bot say 6 hours per day. If Jagex didn't care then we wouldn't have to constantly create new bots to succeed the older bots.
  12. Our new Mirror Client seems to be doing a good job though, no reports of bans with it so far. It is in BETA testing stage still and still needs performance improvements and bug fixes.
  13. I can't make you guys bot smart, but consider it stupid to bot 24/7. Read this: http://osbot.org/forum/topic/67517-do-not-test-detectability-by-botting-247/
  14. No it's not worth it. Botting is about being smart. Getting yourself banned will just help/teach their system to identify new systems. This is not smart, because you know you will get banned botting 24/7, no living person on earth can do that.
  15. by Czar Now Added Divine potion making!! (Grinding chocolate bars gives no xp) Supports Amulet of Chemistry replenishment
  16. Wiz Khalifa's AIO WoodCutter Intro: Wiz Khalifa's populair WoodCutter is back here in OSBot 2 ! Make sure to try this and gain alot of woodcutting levels or earn alot of money. Locations: P2P Locations: Seers Village: Willows. Maples. Yew tree Magics Sors Tower: Magics. Catherby: Yew tree Willows. F2P Locations: Varrock: Oak Yew tree Draynor: Willows Oaks Logs Falador: Yew tree Grand Exchange: Yew tree Edgeville Yew tree Port Sarim Willow Features: - Bird nest pickup. (Coming soon) - Anti-ban. - Stable. - Lots of locations ! Proggies:
  17. 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:
  18. 1 point
    One of the best SBTV F64s i have heard and its from back in 2010, i remember i was at school when this dropped everyone was so hyped Devlin's bars and flow in this are venomous. Enjoy.
  19. People have been coming in there to spam in the first place. Users who have under a certain post count shouldn't be allowed to come in there since that section is just a talking/spamming section and users can spam 100 post count to sell accounts defeating the point in the post count requirement. Example: *Not saying he is, but yeah.
  20. Script available on the SDN ^_^
  21. Super Mario Bros and Mario Kart! good childhood :P
  22. 1 point
    Thank you very much for your insightful reply, now i'm actually considering this
  23. 1 point
    This is a great script, everything has been running good with it sense the latest client updates.
  24. http://osbot.org/forum/topic/67260-has-anyone-been-banned-using-mirror-client/
  25. Omg.. I can't believe there are people like this knocking about.. Mirror client is the fucking bees knees. It's worth about $5000+ to someone who knows what they are doing with it.
  26. You can use multiple tabs with the Mirror Client. Most scripts work fine with it now. Over the next few updates performance will be further improved and all scripts should work the same as on standard mode.
  27. 42 defence ags pures is where its at atm :P those fkers are strong
  28. @mysteryy Can you use multiple mirror clients per computers? or does it use the 'computers' mouse
  29. Welcome back. Ban rates = high af Mirror client= da boombbbb
  30. i think someone said allocating more memory would fix this. also mgi said he was fixing it for the next patch to be released this weekend i believe.
  31. Is this bug still prevalent on v1.03?
  32. 1 point
    did u get 95 mage on rats lol
  33. 1 point
    Fixed your image...
  34. 1 point
    I'd say 15-20m
  35. 43 hrs, 72 mining. Leggo 85 mining
  36. Impressive We're about to update the client to be compatible with the new update to the mirror client MGI made, fixing most of the current bugs in the mirror client.
  37. You got scammed, sorry for your loss user is banned. I advise no one to pay back for him, as he just charged back over 100+ dollars from another user. I am still in contact with the original owner trying to get the account back. Cinnamon is the user who scammed the account back most likely.

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.