Leaderboard

Fixed gave you the script + set you at $0.00 at you would have had 4.00 left, but you charged back a script 1 year ago. So I took the credit.

Hey guys, I was just letting every one know, that if you are VIP + you can change your display name to someone else that is banned or that has been inactive for 1 year or more. For example if you want the name "zap" you go to this http://osbot.org/forum/index.php?app=members and search for his name, http://osbot.org/forum/user/1030-zap/, see that he hasn't logged in since 2014. You can PM if you have VIP + and I will give you that display name! Thanks, @Maldesto

CzarScripts #1 Bots LATEST BOTS If you want a trial - just post below with the script name, you can choose multiple too. Requirements Hit 'like' on this thread

i want to kill myself anyway

Goodbye OSbot, I really enjojed my time here. But unfortunately, the time has come for me to disembark. Many new chapters will soon be unfolding in my life, and I no longer have the time needed to devote to OSbot. During my time here Dragons were fokin slayed Human hours were saved xp was gained I will really miss you guys, wish you luck with wherever life takes you. Best Regards, -Gold Scripts *Gold Scripts has left the chat*

I think these lives matter things are causing more trouble than they are helping.

Before buying, please ensure you check-out with the correct script. Swapping scripts is not possible. View in store $4.99 for lifetime access Features: All spawns - Supports every multi-crab spawn point both along the south coast of Zeah and Crab Claw Isle All combat styles - Supports Ranged, Magic and Melee combat training. The script will not bank runes of any type Saving GUI - Intuitive, re-sizeable and fully tool tipped GUI (Graphical User Interface) allowing you to tailor the script session to your needs, with configuration saving / loading Human replication - Designed with human simulation in mind - multiple options to replicate human behaviour available in the GUI Setup customiser - Inventory customiser allows you to visually see your trip setup CLI support - The script can be started from the command line All potions - Supports all relevant potion types (including divine potions!), multiple potion types simultaneously and varying potion ratios Healing in a range - Dual slider allows you to specify a range within which to consume food. Exact eat percentages are calculated using a Gaussian distributed generator at run time Healing to full at the bank - When banking, the script will eat up to full hit points to extend trip times Safe breaking - Working alongside the OSBot break manager, the script will walk to safe place approximately two minutes before a break starts to ensure a successful log out Anti-crash - Smart crash detection supports multiple anti-crash modes (chosen in the GUI): Hop worlds if crashed - the script will walk to a safe place and hop worlds until it finds a free one, at which point it will resume training Force attack if crashed - the script will fight back and manually fight pre-spawned sand crabs until the crasher leaves Stop if crashed - the script will walk to a safe place and stop Ammo and Clue looting - Clue scroll and Ammo looting system based on a Gaussian-randomised timing scheme All ammo - Supports all OSRS ammo types and qualities Spec activation - Special attack support for the current weapon to maximise your exp per hour Auto-retaliate toggling - The script will toggle auto-retaliate on if you forget Move mouse outside screen - Option to move the mouse outside the screen while idle, simulating an AFK player switching tabs Refresh delay - Option to add a Gaussian-randomised delay before refreshing the chosen session location, simulating an AFK player's reaction delay Visual Paint and Logger - Optional movable self-generating Paint and Timeout Scrolling Logger show all the information you would need to know about the script and your progress Progress bars - Automatically generated exp progress bars track the combat skills that you are using Web walking - Utilises the OSBot Web alongside a custom local path network to navigate the area. This means the script can be started from anywhere! Safe banking - Custom banking system ensures the script will safely stop if you run out of any configured items Safe stopping - Safely and automatically stops when out of supplies, ammo or runes Dropping - Drops useless/accidentally looted items to prevent inventory and bank clutter All food - Supports pretty much every OSRS food known to man. Seriously - there's too many to list! ... and many more - if you haven't already, trial it! Things to consider before trying/buying: Mirror mode - currently there appear to be some inconsistencies with behaviour between Mirror mode and Stealth Injection meaning the script can behave or stop unexpectedly while running on Mirror. I would urge users to use the script with Stealth Injection to ensure a flawless experience! Since Stealth Injection is widely considered equally 'safe' to mirror mode and comes with a host of other benefits such as lower resource usage, this hopefully shouldn't be a problem. Using breaks - the script supports breaks and will walk to a safe place ready to log out approximately two minutes before a configured break starts. However, upon logging back in, your spot may no longer be open. If you configure the crash mode to be either 'Hop if crashed' (default) or 'Stop if crashed', this will not prove to be a problem. However if using 'Force attack if crashed', the script will attempt to take back the spot by crashing the occupying player and manually attacking spawned sand crabs. Be aware that players have a tendency to report anti-social behaviour such as this! Avoiding bans - while I have done my utmost to make the script move and behave naturally, bans do occasionally happen, albeit rarely. To minimise your chances of receiving a ban, I would strongly suggest reviewing this thread written by the lead content developer of OSBot. If you take on board the advice given in that thread and run sensible botting periods with generous breaks, you should be fine. That being said, please keep in mind that botting is against the Oldschool Runescape game rules, thus your account will never be completely safe and you use this software at your own risk. Setting the script up - I have done my best to make the GUI (Graphical User Interface) as intuitive as possible by making all options as self explanatory as I could, however if you are not sure as to what a particular setting does, you can hover over it for more information. If that doesn't help, just ask on this thread! Web-walking - alongside a network of paths, the script moves around with the OSBot web-walking system, using it when in unknown territory. While it has proven very reliable, there are naturally some areas for which the web-walker may struggle. As a result, prior to starting the script, I would highly recommend manually navigating your player close to the sand crabs bank, however in practice, anywhere on Zeah should be fine. Script trials: I believe that trying a script before buying is paramount. After trying the script, hopefully you will be convinced to get a copy for yourself, but if not you will have gained some precious combat experience! If you're interested in a trial, please follow the instructions on my trials thread which can be found here. Gallery: Start up GUI (Graphical User Interface): Paint (optional, movable and self-generating): User screenshots: Recent Testimonials: Starting from CLI: This script can be started from the command line interface. There is a single parameter, which can take two (and only two) values: 'gui' or 'nogui'. 'gui' will start the script and show the gui, 'nogui' will skip the GUI setup and start the script using your save file as the configuration. To start from CLI with 'nogui', the script requires a valid GUI save file to be present - if you haven't already, start the script manually and configure the GUI to suit your needs. Then hit 'Save configuration' and in future starting from CLI will use these configured settings. The script ID is 886. Example CLI startup: java -jar "osbot 2.4.137.jar" -login apaec:password -bot apaec@example.com:password:1234 -debug 5005 -script 886:nogui

1 year? 365 days without logging in one time?

Osbot is way better then any other botting client imo. also best community

Still listed as a development build, please test and let me know how it works. Version 2.4.72 Changelog: -Patched Web Walking not teleporting (reported by @Khaleesi) Version 2.4.73 Changelog: -Patched Web Walking item requirements (reported by @Token) -Patched CLI proxy authentication requiring user/pass -Patched GrandExchange not detecting offer price of 1 coin (reported by @Explv)

Thank you everyone for all the support and feedback, this script officially is the most sold magic script on the market! Since 2015 it has been continually updated all the way to 2025! #1 SOLD MAGIC SCRIPT #1 MOST FEATURES MAGIC SCRIPT ESC MODE, HOVER-CLICK, NEAREST ITEM CLICK, FLAWLESS JMod nearby and we still alive. Anti-ban and Optimal script usage Anti-ban: - Don't go botting more than 3 hours at once, take breaks! Otherwise the ban-rate is highly increased! - Bans also depend on where you bot, for the best results: bot in unpopular locations Banking-related spells are the lowest ban-rate (spells which require banking or can be casted near a bank, e.g. superheating, maybe alching, jewelry enchanting etc etc) since you can just go to a full world and blend in with other non-bots (humans), for example: world 2 grand exchange If casting spells on npcs, then unpopular locations reduce the banrate by alot, So make sure not to go to botting hotspots otherwise you may be included in ban waves. - Some good areas used to be (until some got popular): grizzly bear, yanille stun-alching, any overground tiles (upstairs etc) but once the areas are overpopulated, try to go to another location which is similar to the aforementioned locations. This is a very popular thread with many many users so if a new location is mentioned, the location will be populated very quickly so I can only suggest examples of good locations - Don't go botting straight after a game update, it can be a very easy way to get banned. Wait a few hours! If you ever get banned, just backtrack your mistakes and avoid them in the future: you cannot be banned without making botting mistakes. Keep in mind you can be delay-banned from using previous scripts, so don't go using free/crap scripts for 24 hours then switching to a premium script, because the free/crap previous script can still get you banned! For more anti-ban information, see this thread which was created by an official developer: http://osbot.org/forum/topic/45618-preventing-rs-botting-bans/

PPOSB - AIO Hunter Brand new trapping system just released in 2024! *ChatGPT Supported via AltChat* https://www.pposb.org/ ***Black chinchompas and Black salamanders have been added back*** Supports the completion of Varrock Museum & Eagle's Peak OR CLICK HERE TO PAY WITH 07 GOLD! The script has been completely rewritten from the ground up! Enjoy the all new v2 of the script JOIN THE DISCORD CHAT FOR QUESTIONS/ SUPPORT/ CHATTING/ UPDATES! New GUI: Features: Click Here Current functioning hunter tasks: (green - complete || yellow - started || red - incomplete) Screenshots: Progressive Leveling: 1-19 --> Crimson swift 19-43 --> Tropical wagtail 43-63 --> Falconry 63+ --> Red chinchompas Updates How to setup Dynamic Signatures Report a bug CLI Support - The script now supports starting up with CLI. The commands are given below. Please put in ALL values (true or false) for CLI to work properly. Make sure they are lowercase values, and they are each separated with an underscore. The script ID for the hunter bot is 677. Parameters: EnableProgression_EnableVarrockMuseum_EnableEaglesPeak_EnableGrandExchange Example: -script 677:true_true_false_true ***Don't forget to check out some of my other scripts!*** OSRS Script Factory Click here to view thread LEAVE A LIKE A COMMENT FOR A TRIAL The script is not intended for Ironman accounts. It still works for Ironman accounts, but you must have all equipment, gear, and items.

Original image: http://i.imgur.com/uH5voeT.jpg And here is my edit,

shitpost

http://osbot.org/forum/topic/102394-bye-guys/

yo give me taylor swift

Moved to Stable Build.

Just from my few days here I can already see the difference in the community

@Jams will have to refund 40m + 5 bonds. Considering he mentioned going off to work he'll have 24 hours to do so.

I'll save this, so when you beg to come back I can laugh at you.

You did a service with access to the script required to do the service. Unless you can provide proof you didn't bot, screen shots of the waves + firecapes, you are responsible.

This tutorial will cover everything required to write your own OSBot scripts. Although it is quite lengthy, don't let this put you off - it shouldn't take more than a couple of hours to follow through, at the end of which you will have learned the scripting basics and will have your very own tea thieving script which you can modify to your liking. Good luck! Previous required knowledge: None Knowledge of basic java helps but is not required! What this guide covers: Downloading your code editor (IDE) Basic programming concepts A quick guide to java Writing a script with the OSBot API Running your script Downloading Eclipse: Setting up your project: Language basics: Java basics: Script backbone: Compiling the script: Writing the script: Best practices and conventions: Completed Tea thieving source code: That's the end of this tutorial, hopefully it was useful and concise enough. As I mentioned earlier, remember to ask LOTS OF QUESTIONS! Also remember that google is your friend! ? Although it may seem OSBot scripting is a niche use of java, many questions can translate to more widely adopted counterparts - use this to your advantage. If you have any questions do not hesitate to post as a reply below. Since I follow this thread, I will receive a notification if you do and will do my best to get back to you ASAP! - Apaec

Hi, I've been wondering for a while if it is possible to improve the performance/stability of multiple OSBot instances, more particularly stealth injection. I am currently running 4 dedicated servers with each having around 20 clients sitting at 70-90% CPU load, however some clients tend to randomly freeze (Black screen) after a few hours of runtime, this seems to be dependent on the amount of running bots, 10 usually don't cause any issues. I've tried both Linux and Windows with the same results, however linux struggled with more than 10 clients In terms of resource usage, my dedi boxes run at around 60% memory usage, 512mb dedicated to each instance so that doesn't seem to be the issue - Abuse

He aint TWC that fo sho.

1.5m i'll take it @ a/w

Yes

Do you mean 8760 hours?

Why would we allow someone to be inactive for 1+ year and hold hostage a name someone would be active with? Most of them made the names and never came back. I've removed 10+ names this month that had 0 online time and 0 posts 3 years old. They are allowed to come back to osbot, with a different name and if they do, we allow them to pick a new name.

Sounds like a more than plausible service to offer IMO. It's surprising how many people struggle with MM without prayer, the same with DT.

Its already planned whenever I touch the server stuff again.

Authed

Doesnt it have anything to do with java permission? Although this script is the only one which doesnt start.

Hello, would like to try Thiever and Figher please

Authed

make sure you changed your ip.

guilty

Authed

poor excuse for photoshop nice remove though. He needs to post here and let you know.

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: