Skip 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

  1. Czar

    Global Moderator
    15
    Points
    23654
    Posts
  2. Apaec

    Scripter III
    9
    Points
    11174
    Posts
  3. liverare

    Java Lifetime Sponsor
    6
    Points
    1300
    Posts
  4. Alek

    Ex-Staff
    5
    Points
    7878
    Posts

Popular Content

Showing content with the highest reputation on 05/30/18 in Posts

  1. ๐Ÿ‘‘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
  2. Note: this is not how to make a GUI. This is how to implement one. The following is assumed: You have one file that contains your GUI code. You have one file that contains your script code. Your GUI code has a 'start' button which is public or has a getter function. Let's start with your script code: public class TestScript extends Script { @Override public void onStart() throws InterruptedException { } @Override public int onLoop() throws InterruptedException { return 250; } @Override public void onExit() throws InterruptedException { } } Simple code with three routines: onStart, onLoop and onExit. Here's what we're going to do: onStart Check the script parameters and store the values into Atomic variables. I'll explain why later. If we don't have script parameters, we then initialise the GUI and then show it. onLoop If our Atomic variables are empty, then have the script do some afk things (shake the mouse) until we do. If the user closes the GUI and our Atomic variables are empty, then stop the script. onExit If the GUI exists, then dispose of it. Okay, so now let's begin by declaring some variables: public class TestScript extends Script { private JFrame gui; private String params; private AtomicReference<String> treeName; private AtomicReference<String> axeName; private AtomicBoolean powerchop; private AtomicInteger stopAtLevel; @Override public void onStart() throws InterruptedException { initialiseVars(); } public void initialiseVars() { params = super.getParameters(); treeName = new AtomicReference<>(); axeName = new AtomicReference<>(); powerchop = new AtomicBoolean(); stopAtLevel = new AtomicInteger(); } @Override public int onLoop() throws InterruptedException { return 250; } @Override public void onExit() throws InterruptedException { } } Notice how I haven't instantiated the 'gui' variable? This is intentional. GUIs are inefficient and memory intensive. If the user has started the script with script parameters, then just use that. However, if the script parameters are wrong, then use the GUI as backup. Now let's check the script parameters and initialise the GUI. Note: how you check script parameters are valid is up to you. You can check out my CLI Support Made Easy API API, Script File (ini) API, and OSBot File API. public class TestScript extends Script { private JFrame gui; private String params; private AtomicReference<String> treeName; private AtomicReference<String> axeName; private AtomicBoolean powerchop; private AtomicInteger stopAtLevel; @Override public void onStart() throws InterruptedException { initialiseVars(); if (!checkScriptParameters()) { SwingUtilities.invokeLater(this::initialiseGUI()); } } private void initialiseVars() { params = super.getParameters(); treeName = new AtomicReference<>(); axeName = new AtomicReference<>(); powerchop = new AtomicBoolean(); stopAtLevel = new AtomicInteger(); } private boolean checkScriptParameters() { boolean valid = false; // TODO check script parameters // TODO put values into Atomic variables (parse them if need be) // TODO return true/false based on whether the parameters were correct return valid; } private void initialiseGUI() { // TODO gui stuff } @Override public int onLoop() throws InterruptedException { return 250; } @Override public void onExit() throws InterruptedException { } } So, about those Atomic variables. Notice the "SwingUtilities.invokeLater..." stuff? Well, you can read about Swing Utilities here. The short-form is: we're running the GUI on a separate thread. This means the following: The client won't freeze whilst the GUI is open (yay!). The Atomic variables are going to handle all that messy concurrency stuff that is now an issue because we're using a separate thread for stuff. Without Atomic variables, we'd need to add our own thread-safety. Why? Because if your script changes a variable at the exact same moment your GUI decides to update that variable, the script thread and GUI threads will conflict and things break. Praise be to Atomic variables! Also, if you're wondering what the :: is for, you can read about that here. The short and sweet: it's a way of referencing a method. Okay now, let's do GUI stuff! Right, we're going to need to add a method that grabs user input from GUI and stores it into the Atomic references. public class TestScript extends Script { private JFrame gui; private String params; private AtomicReference<String> treeName; private AtomicReference<String> axeName; private AtomicBoolean powerchop; private AtomicInteger stopAtLevel; @Override public void onStart() throws InterruptedException { initialiseVars(); if (!checkScriptParameters()) { SwingUtilities.invokeLater(this::initialiseGUI()); } } private void initialiseVars() { params = super.getParameters(); treeName = new AtomicReference<>(); axeName = new AtomicReference<>(); powerchop = new AtomicBoolean(); stopAtLevel = new AtomicInteger(); } private boolean checkScriptParameters() { boolean valid = false; // TODO check script parameters // TODO put values into Atomic variables (parse them if need be) // TODO return true/false based on whether the parameters were correct return valid; } private void initialiseGUI() { gui = new MySexyGUI(); gui.setLocationRelativeTo(bot.getCanvas()); gui.addWindowListener(new WindowAdapter() { @Override public void windowClosing(WindowEvent e) { TestScript.super.stop(false); } }); gui.getStartButton().addActionListener(this::startButtonClicked); gui.setVisible(true); } private void startButtonClicked(ActionEvent e) { String treeName = gui.getTreeNameTextField().getText(); String axeName = gui.getAxeNameTextField().getText(); boolean powerChop = gui.getPowerChopCheckBox().isSelected(); int stopAtLevel = (int) gui.getStopAtLevelNumberSpinner().getValue(); if (treeName != null && !treeName.isEmpty() && axeName != null && !axeName.isEmpty()) { this.treeName.set(treeName); this.axeName.set(axeName); this.powerchop.set(powerChop); this.stopAtLevel.set(stopAtLevel); gui.setVisible(false); } else { // TODO let the user know there are problems in the GUI } } @Override public int onLoop() throws InterruptedException { return 250; } @Override public void onExit() throws InterruptedException { } } Once we've grabbed the information from the GUI, we need to make sure it's correct. For things such as tree names, axe names, or any other constants, I'd have an enumerator that contains those values and let the user pick out them values from a combo box. It's a safer bet as the user can't pick a "wrong" tree and the enumerator can be used in the checking of the script parameters. If our values are correct, we then store them into the Atomic variables and then hide the GUI. We could dispose of the GUI at this point. However, if the GUI has already been initialised, you may as well keep it around so the user can make real-time changes to the behaviour of the script. I've positioned the GUI relative to the bot's canvas and also added a WindowListener in the form of a WindowAdapter to the GUI that will stop the script if the user clicks on the close button. These are pretty expectant behaviour, so I'd figure I'd add them. To recap, we've achieved the following: onStart Check the script parameters and store the values into Atomic variables. If we don't have script parameters, we then initialise the GUI and then show it. But also, we've achieved this as well: onLoop If the user closes the GUI and our Atomic variables are empty, then stop the script. Because the GUI has a listener that listens to the close button. If that button is clicked, the script will then stop. But we're not done with our onLoop just yet! We're going to want to figure out what values we're currently working with. public class TestScript extends Script { private JFrame gui; private String params; private AtomicReference<String> treeName; private AtomicReference<String> axeName; private AtomicBoolean powerchop; private AtomicInteger stopAtLevel; @Override public void onStart() throws InterruptedException { initialiseVars(); if (!checkScriptParameters()) { SwingUtilities.invokeLater(this::initialiseGUI()); } } private void initialiseVars() { params = super.getParameters(); treeName = new AtomicReference<>(); axeName = new AtomicReference<>(); powerchop = new AtomicBoolean(); stopAtLevel = new AtomicInteger(); } private boolean checkScriptParameters() { boolean valid = false; // TODO check script parameters // TODO put values into Atomic variables (parse them if need be) // TODO return true/false based on whether the parameters were correct return valid; } private void initialiseGUI() { gui = new MySexyGUI(); gui.setLocationRelativeTo(bot.getCanvas()); gui.addWindowListener(new WindowAdapter() { @Override public void windowClosing(WindowEvent e) { TestScript.super.stop(false); } }); gui.getStartButton().addActionListener(this::startButtonClicked); gui.setVisible(true); } private void startButtonClicked(ActionEvent e) { String treeName = gui.getTreeNameTextField().getText(); String axeName = gui.getAxeNameTextField().getText(); boolean powerChop = gui.getPowerChopCheckBox().isSelected(); int stopAtLevel = (int) gui.getStopAtLevelNumberSpinner().getValue(); if (treeName != null && !treeName.isEmpty() && axeName != null && !axeName.isEmpty()) { this.treeName.set(treeName); this.axeName.set(axeName); this.powerchop.set(powerChop); this.stopAtLevel.set(stopAtLevel); gui.setVisible(false); } else { // TODO let the user know there are problems in the GUI } } @Override public int onLoop() throws InterruptedException { String treeName = this.treeName.get(); String axeName = this.axeName.get(); if (treeName == null || treeName.isEmpty() || axeName == null || axeName.isEmpty()) { // TODO go afk } else { // TODO botty stuff } return 250; } @Override public void onExit() throws InterruptedException { } } The 'onLoop' should be happy as long as you programmed your 'checkScriptParameters' function works. Why? Because if the user enters in wrong script parameters, then the GUI should show up to save the day. If the GUI doesn't show up, that's because the user has entered in correct script parameters, so 'treeName' and 'axeName' should both be valid. Now, let's finish this by closing our GUI on the onExit: public class TestScript extends Script { private JFrame gui; private String params; private AtomicReference<String> treeName; private AtomicReference<String> axeName; private AtomicBoolean powerchop; private AtomicInteger stopAtLevel; @Override public void onStart() throws InterruptedException { initialiseVars(); if (!checkScriptParameters()) { SwingUtilities.invokeLater(this::initialiseGUI()); } } private void initialiseVars() { params = super.getParameters(); treeName = new AtomicReference<>(); axeName = new AtomicReference<>(); powerchop = new AtomicBoolean(); stopAtLevel = new AtomicInteger(); } private boolean checkScriptParameters() { boolean valid = false; // TODO check script parameters // TODO put values into Atomic variables (parse them if need be) // TODO return true/false based on whether the parameters were correct return valid; } private void initialiseGUI() { gui = new MySexyGUI(); gui.setLocationRelativeTo(bot.getCanvas()); gui.addWindowListener(new WindowAdapter() { @Override public void windowClosing(WindowEvent e) { TestScript.super.stop(false); } }); gui.getStartButton().addActionListener(this::startButtonClicked); gui.setVisible(true); } private void startButtonClicked(ActionEvent e) { String treeName = gui.getTreeNameTextField().getText(); String axeName = gui.getAxeNameTextField().getText(); boolean powerChop = gui.getPowerChopCheckBox().isSelected(); int stopAtLevel = (int) gui.getStopAtLevelNumberSpinner().getValue(); if (treeName != null && !treeName.isEmpty() && axeName != null && !axeName.isEmpty()) { this.treeName.set(treeName); this.axeName.set(axeName); this.powerchop.set(powerChop); this.stopAtLevel.set(stopAtLevel); gui.setVisible(false); } else { // TODO let the user know there are problems in the GUI } } @Override public int onLoop() throws InterruptedException { String treeName = this.treeName.get(); String axeName = this.axeName.get(); if (treeName == null || treeName.isEmpty() || axeName == null || axeName.isEmpty()) { // TODO go afk } else { // TODO botty stuff } return 250; } @Override public void onExit() throws InterruptedException { if (gui != null) { SwingUtilities.invokeLater(gui::dispose); } } } Boom. If the user stops the script whilst the GUI is open, the GUI will be dismissed. We've used SwingUtilities again because the GUI is still running on a separate thread, so we should avoid the script from interacting with it directly. Have fun! Let me know if there are any problems. I wrote this adhoc so there were a few things I missed out, which include: Showing the GUI on 'initialiseGUI' (lol). Hiding the GUI when you click on 'startButtonClicked', but only once you've validated the input from the GUI.
  3. โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ 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.
  4. Look up how to run Minecraft on YouTube, it's the same process but for OSBot.
  5. 4 points
    u don't need proxifier for the osb client, each window can run seperate proxies by it self while your original Jagex client runs on your home IP. you only want to use proxifier if you need to proxy the Jagex or osbuddy client
  6. View in store $5.99 for lifetime access _____________________________________________________________ Key Features: Progressive mode - The script will traverse the xp-optimum course for your current level; walking to the next course as your level increases. Reliability - The script was developed and rigidly tested with superior reliability in mind. Human replication - Designed around human simulation - behaviour tuned to replicate common rooftop play styles. Alching / Magic Imbue - The script can be configured to High/Low Alch items, or cast Magic Imbue as it traverses the course. Target system - Can be optionally configured with a target. Once this target is achieved, the script will stop. Available targets (variable ฮป): Stop when ฮป agility exp gained. Stop when agility level ฮป reached. Stop when ฮป magic exp gained. Stop when magic level ฮป reached. Stop when ฮป minutes passed. Healing - The script will consume edible items in your inventory to restore health, stopping if you run out of food. Mark of Grace looting - All marks of grace are looted while the script traverses the rooftop. Randomisation - All thresholds (including but not limited to Run energy and Critical Hp) are dynamically randomised. Energy restoration - The script will consume energy restoring items/potions when needed, provided they are available in the inventory. Web-Walking - The script utilises the OSBot Web to navigate the OSRS map, meaning it can be started from almost anywhere. Course detection - If you are on/near a rooftop course before setup, the course will automatically be loaded into the GUI. Error correction - The script will detect when it has made a mistake (e.g. climbed ladder in seers' bank) and will attempt to return to the course. ...and many more! Supported Rooftops: (Level 10) Draynor โœ“ (Level 20) Al-Kharid โœ“ (Level 30) Varrock โœ“ (Level 40) Canifis โœ“ (Level 50) Falador โœ“ (Level 60) Seers' Village โœ“ (Level 70) Pollnivneach โœ“ (Level 80) Rellekka โœ“ (Level 90) Ardougne โœ“ Things to consider before trying/buying: 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. 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 strongly recommend manually navigating your player to/close to the desired rooftop course. Progressive mode - the script features 'Progressive mode' which will cause the script to advance rooftop courses as you level up. Progressive mode relies on the aforementioned web-walking system for inter-rooftop navigation. Consequently, I would highly recommend monitoring the script as it traverses between courses to ensure the web-walking process correctly executes. Healing & Energy restoration - the script will automatically heal or restore run energy when needed. It will do so by consuming items in the inventory - this script will not bank. For optimal exp rates, I would strongly suggest keeping energy restoring items in the inventory (energy/super energy/stamina/fruits/summer pies/purple sweets/...). To prevent the script stopping prematurely, bring a few bites of food along. Using magic - The script supports the periodic casting of a magic spell while traversing a course to maximise experience rates. To determine whether or not you can cast a spell, the script checks your magic level as well as which runes are in your inventory and which stave you have equipped (if any). It is worth noting that, at this time, the script does not recognise any of the following items as rune sources, so avoid using them while running this script: Bryophyta's Staff, Tome of Fire, Rune Pouch. 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 agility experience! If you're interested in a trial, please follow the instructions on my trials thread which can be found here. Gallery: Review (by Eduardino): Start up GUI (Graphical User Interface): Paint (optional, movable and self-generating): User screenshots: Testimonials:
  7. by Czar Buy now (only $8.99!) 143 HOURS IN ONE GO!!!!! update: this bot is now featured on the front page of osbot! More reviews than every other fishing bot combined! 100 hour progress report!!! How to use Script Queue: ID is 552, and the parameters will be the profile name that you saved in setup! This process is really simple, just to save you headache
  8. < Hidden until nerfed >
  9. 2 points
    there's no option for who dis
  10. I've botted for 1-2 hours a day (40-60 mins once in morning and once in evening) for 3 weeks now starting from level 1, I'm now nearly level 80 with no ban. I also use Perfect fighter, perfect magic to alch/enchant necklaces in between. Approx 2-3 hours a day of botting and 30 mins of legit playing (quests/clue scrolls). There's nothing wrong with the script.... you've just got to know how to use it. 3-5 hours a day is a lot for agility - one of the most botted skills. Any time frame for the alching update Czar? Don't worry if not, I know being pestered is annoying!
  11. new phone who dis
  12. 1 point
    Want to buy with OSGP? Contact me on Discord! Detailed feature list: - Account builder mode to level your firemaking to level 50 or even higher. - Equips pyromancer gear option - Chopping and burning logs (base Option) - Relights brazier - Fletch option - Fix brazier option - Make potion and heal pyromancer when down option - Tons of food supported - Brazier swicthing when pyromancer is down - Advanced game settings to skip games, smart caluclate points, afk at certain points, ... - Bank or Open crates - Dragon axe special attack - Fletch at brazier option - Chop in safespot option - Worldhopping - CLI support for goldfarmers 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 909: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 managers you do not need to specify -script 909): -script 909:TaskList1.4515breaks (With breaks) -script 909:TaskList1.4515breaks.discord1 (With breaks & discord) -script 909:TaskList1..discord1 (NO breaks & discord) Proggies:
  13. NEW! Added Gemstone Crab! 81 Hours at Cows Brutal Black Dragon support Sulphur Nagua support Blue Dragon 99 ranged 99 Ranged at Gemstone Crab 81 Range F2p Safespotting Hill Giants Hotkey List // F1 = set cannon tile // F2 = hide paint // F3 = Set afk tile // F4 = reset afk tile // F6 = Set safespot tile // F7 = activate tile selector // F8 = Reset tile selector // F9 and F10 used by the client, EDIT: will re-assign as they are no longer used by client // F11 = Set breaks tile // F12 = Reset breaks tile User Interface Banking Tab Demo (handles everything with banking) You can copy inventory (to avoid adding individual items...), you can insert item names which have Auto-Fill (for you lazy folk!) and you can choose whether to block an item and avoid depositing it in bank, ideal for runes and ammo. Looting Tab Demo (From looting to alchemy, noted/stackable items too) You can choose whether to alch an item after looting it simply by enabling a checkbox, with a visual representation. All items are saved upon exiting the bot, for your convenience! Tasking Demo (Not to be confused with sequence mode, this is an individual task for leveling) You can set stop conditions, for example to stop the bot after looting a visage, you can have a leveling streak by changing attack styles and training all combat stats, you can have windows alert bubbles when an event occurs and an expansive layout for misc. options! Prayer Flick Demo (Just example, I made it faster after recording this GIF) There are two settings: Safe mode and efficient mode, this is safe mode: Fight Bounds Demo Allows you to setup the fight bounds easily! Simplified NPC chooser Either choose nearby (local) NPCs or enter an NPC name to find the nearest fight location! Simple interface, just click! Level Task Switch Demo (Switching to attack combat style after getting 5 defence) You can choose how often to keep levels together! e.g. switch styles every 3 levels Cannon Demo (Cannon is still experimental, beta mode!) Choose to kill npcs with a cannon, recharges at a random revolution after around 20-24 hits to make sure the cannon never goes empty too! Results Caged Ogres: How does this bot know where to find NPCs? This bot will find far-away npcs by simply typing the NPC name. All NPCs in the game, including their spawn points have been documented, the bot knows where they are. You can type 'Hill giant' while your account is in Lumbridge, and the bot will find it's way to the edgeville dungeon Hill giants area! Here is a visual representation of the spawn system in action (this is just a visual tool, map mode is not added due to it requiring too much CPU) Fight Area Example (How the bot searches for the npc 'Wolf') Walking System The script has 2 main walking options which have distinctive effects on the script. The walking system is basically a map with points and connections linking each point. It tells the script where to go, and decides the routes to take when walking to fightzones. Walking system 1 This uses a custom walking API written by myself and is constantly being updated as new fightzones are added. Pros: - Updates are instant, no waiting times - More fightzones are supported Cons: - Sometimes if an object is altered, the changes are not instant - Restarting the script too many times requires loading this webwalker each time which adds unnecessary memory (there is no way to make it only load at client startup since I don't control the client) Walking system 2 This is the default OSBot webwalking API - it is relatively new and very stable since the developers have built it, but is currently lacking certain fightzones (e.g. stronghold) and other high level requirement zones. It is perfect for normal walking (no object interactions or stairs, entrances etc) and never fails. Pros: - Stable, works perfect for normal walking - All scripters are giving code to improve the client webwalker - More efficient when restarting the script since it is loaded upon client start Cons: - No stronghold support yet - Some new/rare fightzones not supported yet - If there is a game-breaking update or an unsupported fightzone, it may take some time to add/repair (less than 24 hours usually) So which system should I choose? Whichever one suits your chosen fightzone best! There really shouldn't be any problems - the sole purpose of these options are for backup and emergency purposes, if the script ever messes up there is always the next option to select. Note: If the script ever fails, there will be immediate updates to fix the walking systems! Script Queue/Bot Manager: Script ID is 758, and the parameters will be the profile name that you saved in the fighter setup! Bug Report templates: New feature request - What is the new feature - Basic description of what the script should do - Basic actions for the script: 'Use item on item' etc. For when the script gets stuck on a tile (or continuous loop): - Which exact tile does the script get stuck on? (exact tile, not 'near the draynor village') - Plugin or normal script? - Did you try all 3 walking options? Script has a logic bug (e.g. dies while safespotting) or (cannon mode doesn't pickup arrows) - What is the bug - How did you make the bug happen - (optional) recommendation for the bug, e.g. 'make the script walk back' or something - Tried client restart? - Normal script or a plugin? - Which exact setup options are enabled? Afk mode, cannon mode, etc etc.
  14. Want to buy with OSGP? Contact me on Discord! Detailed feature list: - Task/progressive based setup - Gem cutting - Amethyst cutting - Glassblowing - Molten glass smelter - Armour crafting - Jewelry crafting/smelting - Jewelry stringing - Battlestaff combinging - Flax picking + spinning - Drift net weaving - Hide tanning - Shield crafting - Birdhouse crafting - Clockwork crafting - CLI support for goldfarmers 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 2024! 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 666: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 666): -script 666:TaskList1.4515breaks (With breaks) -script 666:TaskList1.4515breaks.discord1 (With breaks & discord) -script 666:TaskList1..discord1 (NO breaks & discord)
  15. #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/
  16. 'the intelligent choice' by Czar Buy (only $4.99) Want to buy the bot, but only have rs gp? Buy an OSBot voucher here old pictures
  17. There is a google chart somewhere that compares effective str lvls between getting dditional str lvls and unlocking new prayers and iirc getting 13 prayer instead of additional str lvls is better after like 80str or so and 31 pray is better than getting the same cb lvl from training str after high 80s or so. you dont really need extra hp lvls so higher prayer is generally better, especially with protect item. just check a cb calc with your acc stats and your maxhit and then check how many cb lvls you gain with either unlocking the next boosting prayer vs training str to get to the same cb lvl as you would be with the next boosting prayer and compare maxhits
  18. "it opens up the account to ancients and i spec higher" I dont think theres much more to say.. It is worth the hard decision tho in my oppinion ! Gl
  19. 1 point
    Progressive mode = task system basicly. So I can set the bot to train att untill I get 50 then switch to str untill 50 and then when I got 50 str it will switch to def for example. Agility is known for having high ban rate, although if you bot "safe and smart" the chance of being banned will be reduced. Just don't bot for multiple hours without breaks. Especially for agility I wouldn't do more than 2-3 hours a day if you don't know what you are doing. This is just my personal advice, some might disagree.
  20. 1 point
    You've made some very awesome progress... certainly seems like you've got your moneys worth! As for progressive mode, i'm not sure what you mean by this. Was this the attack style switching system? If so, it's on my 'would like to add' list (and has been for a while). I just haven't found the time or add this as i've been focussing on more pressing updates and rewrites to other scripts in my collection! If you'd like a trial, please let me know!
  21. I know i'm so sorry for delaying the alching update it's really hard to make it flawless, I am still experimenting on it, especially with normal courses Stay tuned guys ^^
  22. Hi can i try out this script please?
  23. buying 100m 07 PP 0.70/m
  24. 1 point
    Botting combat stats has become so insanely easy. Get your accounts ready to certain stats and from there just babysit sometime and let this thing do wonders. Multiple 99's achieved using this, including pures and maxed zerker. def worth the money . Thanks @Fruity
  25. 1 point
    Oh my god. I ran this script 1 time, and it worked flawlessly. Checked it every few minutes. Like damn, this bot even completes the fight caves better than i do. (i always fail at jad)
  26. I'll buy the script today, i want to get only for high alching. Let's see if it's successful p.s. What's the best to train with lvl 66 mage?
  27. Love quests so I wouldnโ€™t mind that. You just had some annoying quests last time.
  28. 1 point
    He clearly said YOUR bond and supplies
  29. $5 says Mald says no
  30. Download: http://osbot.org/devbuilds/osbot 2.5.9.jar The plugins selector is now finished in the client, starting work hardcore on resizable mode. If resizable mode doesn't come to fruition, it's not all lost because at the very least the client will be more future-proof and all the API is getting looked at over again. All that's really left on resizable mode is a few more API classes and working on the client interface. The scripts page will have a list for plugins soon. Changelog: -Plugins tab now functional in Script Selector -Bank API works on resizable -DepositBox API works on resizable -Store API works on resizable -Chatbox API works on resizable -GrandExchange API works on resizable -LogoutTab API works on resizable -Worlds API partial resizable mode support -Greatly improved Worlds API world hopping, a lot more stable on first hop attempt -Worlds API and Logout API dependency cleaned up -Verified store is open before using buy/sell methods -CachedWidget accepts new constructor, which takes in a parent CachedWidget --Allows cached widgets to have predicates based on predicates -Added CachedWidget setParent -Added LogoutTab isOpen() -Added Worlds isOpen()
  31. Ty chris , i will try injection and see how it goes again. Cheers
  32. hi, trial please
  33. I got banned today perhaps because i used jsfishingtrawler to get the angler outfit a few days ago. Never for more than 3 hours.. Botted in lumbridge no problems (5+hrs/day) with this script until 76 several months ago. Logged back in last week Got angler outfit Did barb fishing and got banned at 80 fishing (always using afk mode/2hr breaks 15-20mins). Any ideas on where I slipped up? PS I never used any other scripts besides the two aforementioned :P
  34. I bought the script and loving it so far. Only problem i have countered is when enchanting bolts (emerald). The bot doesnt stop when you run outta bolts or runes, even though the box is ticked. It keeps spamming the enchantebolts icon
  35. @Czar Humidify banking is really buggy. Keeps right clicking the bank then choosing the bank option instead of just left clicking the bank. Can you fix this please?
  36. I haven't had luck replicating it but I've rewrote some of the walking method for walking to the area and am rewriting the code for walking to the bank as well. Hopefully that will prevent the bug from occurring. My hope is that it's just some odd behavior with OSBot's web walker.
  37. Updated to include more constructors
  38. No, but I'm guessing it's worse and all due to the extra letters.

Account

Navigation

Search

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.