Leaderboard

By Czar 99 in one go!!! Multiple 99s in 1 sitting!!!!! Features List - Supports 4 locations, with randomisation options (Randomise all, randomise north-only, randomise south-only) - Supports taking the axe for woodcutting, if not already equipped/held - Supports taking all equipment including Tinderbox, knife, unfinished potions from crates - Prepares for matches early, and waits around the brazier if you selected to light them (For +25 initial points) - Supports waiting at the safezone after winning the match (at 500 points) to preserve food - Supports training agility via the northern agility steppe - Knows exactly which external actions interrupt your current action, and plans accordingly - Identifies cold snaps and either avoids them completely, or randomises between avoiding and tolerating them - Allows you to fletch logs before burning them for a more balanced experience gain - Choose to optionally switch to other sectors if pyromancer is dying - Identifies pyromancer health, brazier repaired, brazier lit at all times - Knows exactly how many points our current inventory holds (in terms of burning logs) - Gets 1-50 firemaking: locked to maximum of 50 firemaking, and locked to Grand Exchange only. - Buys a player-owned-house via the Varrock Estate agent if you don't already own one (Optional) - Identifies if the account has visited Zeah before, and plans ahead. - Will travel to Zeah by ship to unlock it for newer accounts (Highly useful for goldfarming!) - Resupplies food, jewellery and teleports via the Grand Exchange - Teleports to Grand Exchange supported: Ring of wealth, Varrock teleport tab, Varrock spell (runes only!), Amulet of glory, Home teleport (Lumbridge/Edgeville) - Teleports to Wintertodt Camp supported: Games necklace, walking - Allows you to filter and join matches when a certain % of the game is already active, so wait for next match if below X% - Either holds onto crates, banks them or opens them - up to you! - Supports choosing your own food, choosing when to eat (eat %), choosing minimum to leave match for, and amount to withdraw - Upgrades to pyromancer gear when applicable - Identifies when you get a Phoenix pet - Buys warm clothing that your account is able to wear, filters by skill requirement. - Stop notifications tab (similar to Perfect Fighter): allows you to choose when to stop the bot, or when to alert/notify you - Stop the script at ANY moment in time, after X minutes/hours/seconds, after X wins, after X item gained (pet too!), after X experience gained & more! Buying Warm Clothing (4 missing pieces)! Results

This is an AIO (All-in-one) bot that has almost every thieving style except blackjack, ask for a free trial by liking thread or making a post! Vyres and elves are now supported! Both can make solid profit per hour, decent passive income! BIG THANK YOU TO ALL OUR SUPPORTERS! WE ARE THE MOST SOLD THIEVING BOT IN OSBOT HISTORY. MOST REPLIES, MOST USERS, LONGEST PROGGIES #1 Thiever | Most Overall Sales | Most Total Replies | Most Results | 10+ Years Maintained | 'the intelligent choice' by Czar SUPPORTS VYRES 224M made in a single sitting of 77 hours 1.1B made from elves and vyres!! ELVES SUPPORTED TOO! (NEW) 2.1m/hr, 6 crystals in 7 hrs 99 THIEVING MANY MANY TIMES, 35M EXP IN ONE BOTTING RUN!! 99 thieving in ~43k xp (12 minutes remaining)! Just got 99 proggy! Gratz to @iz0n THIEVING PET AT LVL 22 FROM TEA STALLS 11.5 HOURS, WITH PET TOO!! 610k/hr getting 99s on deadman worlds!

Molly's Chaos Druids This script fights chaos druids in Taverly dungeon, Edgeville dungeon and Ardougne. Profits can easily exceed 200k p/h and 60k combat exp/ph, this is a great method for training low level accounts and pures. Buy HERE Like this post and then post on this thread requesting a 24hr trial. When I have given you a trial I will like your post so you will receive a notification letting you know you got a trial. Requirements - 46 Thieving for Ardougne -82 Thieving and a Lockpick for Yanille - 5 Agility for Taverly(recommended) - No other requirements! Though I do recommend combat stats of 20+ as a minimum Features: - Supports eating any food - Hopping out of bot worlds - Recovers from deaths(respawn point must be lumbridge), includes re-equipping items on death - Potion support - Automatically detects and withdraws/uses Falador teleport tabs if using Taverly dungeon - Automatically detects and withdraws/equips/uses glories if using Edgeville dungeon - Supports looting bag Setup: Start the script, fill out the GUI, and be in the general area of where you want to run the script. CLI setup: Proggies: In the works: Known bugs: Bug report form, this is a MUST for problems to be resolved quickly: Description of bug(where, what, when, why): Log: Your settings: Mirror mode: Y/N

- Solves the Tutorial Island from start to finish - Completes in 7 minutes - Generates a random character each time - Can be started from any point - Turns off music and sounds ............................................................................. Download Link: https://github.com/Explv/Tutorial-Island/releases/latest

I mean I am. At no point did I state they need to be faster. I was just providing them the information necessary from logs etc since the previous poster didn't. I thought the whole point is we are supposed to report when bugs happen and make devs lives easier, not just sit on our hands and wait? 🤔

People are intimidated by Task/Node based scripts because they think its difficult to write and understand. Well you shouldn't be scared, because I'm going to cover everything you need to know. Before going on to the tutorial, I'm expecting from you, To have at least basic knowledge of java To have at least basic knowledge of the OSbots API So what are Task/Node based scripts? Well its simply states but in OOP design. Alright, so we are going to make an abstract class for a Task. We will use this code which I will explain in a bit. import org.osbot.rs07.script.MethodProvider; public abstract class Task { protected MethodProvider api; public Task(MethodProvider api) { this.api = api; } public abstract boolean canProcess(); public abstract void process(); public void run() { if (canProcess()) process(); } } Breaking down this code just comes simply to a few things. A constructor which accepts the MethodProvider class, but why shouldn't it accept the Script class? Well because we only want the task to know about the OSbot api, not the whole methods that the Script class can have, like onLoop(), onStart(), etc. protected MethodProvider api; public Task(MethodProvider api) { this.api = api; } An abstract boolean public abstract boolean canProcess(); An abstract method public abstract void process(); And a run method public void run() { if (canProcess()) process(); } When a class will inherit the methods from the Task class, that class will have a constructor, an abstract method and boolean. The boolean canProcess() will be the condition on which the process() method will execute code. So basically we do the checks and processing with the run() method, we would just check if the condition is true and let the process() method execute code accordingly. Now, we got that abstract class Task, we are going to make it do work for us. We are going to make a drop task, the class will extend the Task class and it will inherit the abstract methods which the Task class has. The drop task will have a condition, the condition will be api.getInventory().isFull(), the condition will return true after the inventory is full and let the process() method execute script accordingly, the code will be api.getInventory().dropAll(); Our class will look something like this import org.osbot.rs07.script.MethodProvider; public class DropTask extends Task { public DropTask(MethodProvider api) { super(api); } @Override public boolean canProcess() { return api.getInventory().isFull(); } @Override public void process() { api.getInventory().dropAll(); } } As you can see we declare a constructor public DropTask(MethodProvider api) { super(api); } Now you might ask why the constructor looks a bit differently from the abstract Task class and what super(api) means? the super() keyword invokes the parents class constructor AKA the Task's class constructor. Now going further we see @Override public boolean canProcess() { return api.getInventory().isFull(); } So that is how our condition is handled, we just return the booleans variable based on what the getInventory().isFull() returns. In term, if the inventory is full the condition will be true, if the inventory is empty the condition will be false. Further on we see @Override public void process() { api.getInventory().dropAll(); } This is basically what our custom task will do after the canProcess() is true, aka when the condition is true. If inventory is full -> we will drop the items. ' After we got our custom task done, we need to let our script execute the tasks, now how we will do it? Simply we will open our main class which extends Script, meaning that the main class is a script. We declare a new ArrayList at the top of our class, to which we will add tasks to. Our main class should look like this import java.util.ArrayList; import org.osbot.rs07.script.Script; public class Main extends Script{ //this is our array list which will contain our tasks ArrayList<Task> tasks = new ArrayList<Task>(); @Override public int onLoop() throws InterruptedException { return 700; } } Now we have our ArrayList which we have a non primitive data type in it (<Task>), in term think of it like the ArrayList is inheriting the methods from Task class. All though its a different topic called https://en.wikipedia.org/wiki/Generics_in_Java you can look into that if you want. Alright, so we have our ArrayList, time to add our tasks to it. In our onStart() method, which only executes once when the script starts we simply add tasks.add(new DropTask(this)); So basically we are adding a new task to the ArrayList, by doing that, to the .add() we add a new object of our DropTask by doing .add(new DropTask(this)); our DropTask has a constructor for MethodProvider which we simply pass by doing DropTask(this) the keyword this references this class that contains the code. Now why does it work by referencing this class, its because the Main class extends Script, the Script class extends MethodProvider as its stated in the OSBots API docs. So we added our tasks to the ArrayList, now we need to check the conditions state and execute the code accordingly. We simply add this to our onLoop() method. tasks.forEach(tasks -> tasks.run()); Which will iterate trough all the tasks in the ArrayList and execute the run() method, as we remember the run() method in our abstract Task script simply checks the condition and executes code if the condition is true. After all this our main class should look like import java.util.ArrayList; import org.osbot.rs07.script.Script; public class Main extends Script{ ArrayList<Task> tasks = new ArrayList<Task>(); @Override public void onStart(){ tasks.add(new DropTask(this)); } @Override public int onLoop() throws InterruptedException { tasks.forEach(tasks -> tasks.run()); return 700; } } Now after all this you can start making your own tasks and adding them to the list. Alright for those who want quick pastes you can find them here in this spoiler: So no need to be scared, you just really need to try and do it, hope this tutorial helped.