Leaderboard

Its because we are using advanced antiban technologies. ABCL v69 - prevents all bans (not subject to refunds).

Why does OSBot use more memory than XYZ Bot? Most bots set a jvm argument indicating the max heap space, "-xmx". This usually limits the jvm from going over a certain amount of heap space. At OSBot, we don't set the max heap space, we let Java naturally allocate the resources that it wants to. How much memory the jvm naturally wants should not be an issue, unless you are running a serious bot farm - which I know for a fact that most botters aren't. This matters because smaller heap space means that the jvm has to GC more and is usually more prone to memory exceptions. If you have 16GB of RAM, I'm sure you can spare 1-2GB unless you are farming. I set -mem in CLI but it uses more! Why? -mem is a wrapper for -xmx, a stupid idea on my part. Remember, xmx indicates max heap space, and the stack space allocation is something you cannot set. So although you set your heap space for 512mb, your stack space will increase the total memory usage. This has absolutely nothing to do with the client or botting. What is the stack and heap? I don't understand! Don't set -mem or -xmx if you are unfamiliar with these terms. You are playing around with settings that you probably shouldn't be. Once again, if you absolutely have a requirement to set max heap space, then do so.

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

Karma is a bitch ain't it, fuck off kid.

He is the chosen one, he is our god. @Token Edit: RIP @Tom

fuck me tom4cba

Just logged into this. Well I can't complain, although I would have liked to go longer, I certainly am not stopping here. I started in 2014 and lets just say im between 3-5 bans now (to nervous to show exact amount cause of LURKERS) I am past the 2k milestone which is fantastic, esp for botting since a lot less chances for reports! Botting your main is a risky endeavor but honestly do it right, and be patient and I know you guys can keep getting your accs up there. How I got banned: I wasn't playing much scape / wasn't around much the entire week before my ban, and the only scripts I used were: Czars fisher, agility and I think I did some herblore in there aswell. an hour in the morning hour at night. I am 99% sure it was agility that got be smashed as thats what I was botting last and logged into a ban from. Despite asking czar multiple times to fix it, I still take responsibility as I should have just held off / bought another agility script that was being more closely maintained. Either way still got lots of XP using his script and a few others. HAPPY BOTTING ! See you all next summer :p

Post in the clowns and circus forum (botting and bans), not scripting help.

────────────── PREMIUM SUITE ────────────── ─────────────── FREE / VIP+ ─────────────── ──────────────────────────────────────────────────────────── ⌠ Sand crabs - $4,99 | Rooftop Agility - $5,99 | AIO Smither - $4,99 | AIO Cooker - $3,99 | Unicow Killer - £3,99 | Chest Thiever - £2,99 | Rock crabs - $4,99 | Rune Sudoku - $9,99 ⌡ ⌠ AIO Herblore - FREE & OPEN-SOURCE | Auto Alcher - FREE | Den Cooker - FREE | Gilded Altar - FREE | AIO Miner - VIP+ ⌡ ──────────────────────────────────── What is a trial? A trial is a chance for you to give any of my scripts a test run. After following the instructions below, you will receive unrestricted access to the respective script for 24 hours starting when the trial is assigned. Your trial request will be processed when I log in. The trial lasts for 24 hours to cater for time zones, such that no matter when I start the trial, you should still get a chance to use the script. Rules: Only 1 trial per user per script. How to get a trial: 'Like' this thread AND the corresponding script thread using the button at the bottom right of the original post. Reply to this thread with the name of the script you would like a trial for. Your request will be processed as soon as I log in. If i'm taking a while, i'm probably asleep! Check back in the morning Once I process your request, you will have the script in your collection (just like any other SDN script) for 24 hours. Private scripts: Unfortunately I do not currently offer private scripts. ________________________________________ Thanks in advance and enjoy your trial! -Apaec.

Mio's Water Sheep A simple script that shears sheep and banks the Wool for you. Features: -Shears Sheep -Walks to the bank -Walks back to the sheep -Makes money I guess, how much? The world may never know Requirements: Shears A RuneScape Account The OSBOT .jar Java Installed A computer Internet Connection An OSBOT account To start the script, just make sure your inventory just has Shears in it, and when you start it will automatically walk to the Sheep south of Varrock. When your inventory is full, it will automatically walk to the East Varrock bank to deposit all of the Wool. Only supports the Sheep pen south of Varrock and Varrock East bank because why not. This script was written purely for fun, and it makes some okay money, so I thought I would share it.

Nice run, you should have requested a refund for the script or reported it to me.

Brought to you by the #1 most sold script series on the market. Come and see why everyone's choosing Czar Scripts! This is the most advanced Agility bot you will find anywhere. BUY NOW $9.99 NEW! Added Both Wyrm Courses! SCRIPT INSTRUCTIONS Optimal Setup for the bot: Please set the mouse zoom to far away (to the left, like below) so that more obstacles can be seen in the view, and so the script can be more stable and reliable Also, make sure to have roofs toggled off (either go to settings tab or type ::toggleroof) for optimal results

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

lul Czar has the audacity to name his scripts "perfect", nice run though man, always fun to start anew though

Needs to be trained legitimately; no use of bots. Will need to be done on an ironman. Requirements: Not to be a moron called @Kalphite Queen Skype: live.sincere

Firstly, fix the two errors that Chris stated above, but it's likely that the actual method has an issue. Secondly, grab your wildy level outside of the loop (no need to repeatedly call it when chances are that your wildy level will not change in the span of < 50ms). Thirdly, I would recommend making this into a method like shouldLogOut(), instead of having your log outs inside of a loop like that. Fourthly, it should be easy to remake that method if it's giving you problems (issue a bug report though, is my recommendation). Check if the widget displaying the wilderness level is there, and if it is and it's visible, that means that you're in the wilderness (so otherwise return 0). From there, parse the text from the widget and you'll get the wildy level

Dear OSBot Moderators & Adminstrators Today, I was a victim of aboose by one of your moderators called @Decode. This young lad, banned me from the chatbox, even though I specifically, I repeat specifically asked to get banned by @Imateamcape as a sacrifice, as well as being the first person to get banned by @Imateamcape. I do not tolerate this kind of aboose from this moderator, and as a paying customer, I demand justice for the actions of @Decode. I'd like the administrators to investigate this case, and act on it. These actions won't be tolerated, and I'm already lawyered up, and planning to sue every admin and moderator on this site. I come from a rich family, with very smart people, and expertise in things like this. We also have close connections to some of the best lawyers in the city. Welcome to hell, see you in court. This is a joke, Decode is my guy bffs

Stream Staking session incoming

CURRENT RECORD: 201 HOURS RUNTIME NEW: Sandstone mining + hopper support Humidify/water circlet/bandit unnote Ardy cloak tele support Setup Screen Preview Results 84 HOURS ON NEW LEVEL 20 ACCOUNT Suicided account with mirror mode near rock crabs, 81 mining! I will probably go for 99 Even supports Ancient Essence Crystal mining! Preview: Mine 1 drop 1 item drop pre-hover feature:

I designed & animated a google design/template. I wanted to see how it would be like to use a hamburger menu to promote simplicity and a sleek look. The theme is to promote peace/calm/tranquility. I thought it's nice to start a search with that theme.

@Drewyboyo @Acerd

czar is a good scripter I think but his scripts seem shitty on purpose if that makes sense lol. btw I did that to you mald and you never refunded. however, I'm still open to one! have a script I never use.

i have to say thank you again token, had 40 accounts needing mith gloves and your script came through for me again with 0 bans. thanks bro keep up the good work

A hamburger for 4 links is a big no no in my book, especially considering all the space you have at your disposition. Hidden navigation = takes more time to use, takes more work to learn, makes content less discoverable. While your stuff usually looks quite ok aesthetically, you tend to over-complicate things which hurts the UX. https://en.wikipedia.org/wiki/KISS_principle

almost new Position(2618, 3444, 0).hover(getBot())

thats one hell of a run

source on the barrel scene?

I did varrock-falador-seers, didn't have the barcrawl miniquest to do barbarion. I'll try that on these new accounts though

Perfect other than what Dex said!

Hey, Can I get a trial please? Ty

Would make the search bar a little bit more distinguishable, other than that I really like it.

@Get Rekt I'm sure this guy will offer a reasonable price with a good time-frame.

unlucky for that person

@Visty

muffins is still bae

@Alek I think ur bot has a memory leak. No honestly it does. Its using 1.5gb on windows. WINDOWS. Thats something I only expect from a @Czar script bro somethings def off

Could I get a trial please ur free one is awesome, but id love to try other locations ! thx

Am working on it as we speak, but i've had other projects going on lately and have had to prioritise them. I can't give an ETA as I truly don't know, the re-write is a lot of work and it's hard to put a time-frame on it. Hopefully soon! (: Apa

Sup @DWrizzlez

holy shit m8

wait 1 year before botting or it will be permed

A lot of scripters on here are going to teach you bad practices, and you're going to learn bad programming. The official way of initializing MethodProvider in your own API is to exchange context, not passing the Script instance. For whatever reason, someone figured out some hacky solution ages ago and everyone learned from that. The correct way: Pass "Bot" to a new class. Have this class contain a new instance of MethodProvider or have it extend MethodProvider. Now use "exchangeContext(Bot)". Alternatively you could just pass the bot instance and call your methods directly, aka "bot.getMethods().getCombat().method()". Second, "this" keyword is used for disambiguation. You only use it for something like this: class test { boolean x = true; test(boolean x) { this.x = x; } If you're using it as a personal preference/coding style, then don't. A lot of try hards who are new to programming do "this". As for task/node/whatever, a lot of scripters completely disregard all optimization when using this style. For instance there will be some "should activate" method, and then in the executor the same code exists. For instance: shouldActivate() { Objects obj = objects.closest("Tree"); return obj != null; } execute() { Objects obj = objects.closest("Tree"); obj.interact("Chop"); } In this example "Tree" is being searched for twice which is very inefficient. You can avoid these bad practices, but you should really spend time understanding programming first. State logic would be a good stepping stone.

Welcome all TopBot Members! It has been announced that another Oldschool bot is now closing. While it is sad to see a fellow bot close, we'd like to welcome the members of TopBot and give all of the TopBot users the easiest transition from TopBot to OSBot as possible for script writers, dedicated botters, casual botters and the community members. Feel free to introduce yourselves here and divulge into the community! TopBot Script writers read here: We will be expediting the script approval process for the next month to make the transition as easy as possible. Below are some resources to help you adjust to the script creation process on OSBot: Check out the Script Rules here. Request an OSBot git account using the announcement here and post in the SDN Upload Requests subforum Check out the OSBot API here. Check out the programming sub-forums and utilize scripting help section for help along the way! 1 Week Sponsor and VIP Discount: Discount on VIP - $7.99 instead of $9.99 Discount on Sponsor - $39.99 instead of $55.99 Discount on Lifetime Sponsor - $100 instead of $124.99 Check them out in our Store here! Also, don't forget to checkout our official OSBot chat here! Read more on TopBot's Closure here: https://topbot.org/forum/index.php?/topic/7953-farewell-closure-of-topbot/

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:

Hello, There is a small bug: When withdrawing X, and the 'Enter amount' interface shows up, it types the amount before the interface shows up, so the sequence is: - right-click item - withdraw-x - types 20 (amount) veryy fast - interface shows up - stuck on interface.. This only happens using the code: ctx.getBank().withdraw(itemId, am); The way to reproduce this bug would be to withdraw X an amount which is not already on your preset options, e.g. if i took out 23 shrimp before, it will say Withdraw-23 shrimp, and to reproduce, you would do withdraw(shrimp, 5) while the 23 is there if that makes sense.