Leaderboard

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've been writing scripts for my own for a short time. I have a fair amount of knowledge in (Java) programming because I major in Computer Science. In the beginning, I didn't know how to write scripts for the OSBot and it took me a long time to understand it. I'll put useful links to other topics and I'll add my own knowledge to this topic. I hope veteran scripters can tell me if I am saying anything incorrect, so I can learn from it. This guide is not to teach you how to program, but it is targeted to people who already know how to program but just don't know how to start. If you want to learn how to program in Java, there are other tutorials for it like this one and that one. [1, 2] I'll be updating this thread when I discover something new or when mistakes have been made as I am a beginner myself. !!! IMPORTANT !!! Everything you need to know about the OSBot API can be found in the Javadocs of the OSBot API. Choosing IDE, importing libraries and compiling Skeleton code Method Provider class Logs Positions and Areas Walking Entities Dialogues ExperienceTracker (Conditional) Sleep and Random Number Generator GUI and Locks MouseListeners and KeyListeners Using resources Sources Edits

efficient & flawless Link: Script now live: Here Features Bypasses Jagex's camera movement bot trap. new! Uses ESC key to close the interface new! Uses the higher xp method (aligns the camera to the target so it closes the menu when it pops up) NEVER gets in combat, 'tower' method of getting out of combat isn't even there (deliberately). Logs out when no money left Equips bronze arrows when necessary Displays 'goal' information, e.g. (at 77 range it will also show details for 80 range, time left, xp left, etc) Automatically equips higher level gear such as d'hide chaps and vambs Runs away just in case of emergency! ................................................................................................................................ With the bots on OSBot, Czar promises to deliver yet another incredible piece to the CzarBot empire. This means you will get to run the script with no worries about bans and xp waste. LEGENDARY HALL OF FAME 100 hour progress report Configuring the bot and the result: Set the npc attack option to 'Hidden' if you want to avoid deaths forever! For extra XP FAQ Why should I use this script when there are millions out there? It is the best script. Simply. Why are you releasing this now? It's time to make it public, it was privately shared with some friends and has been working flawlessly. Instructions There are no instructions. We do the all the work for you. CzarScripting™ Tips If you are low level, you can use a ranging potion at level 33 ranged to get in the ranging guild. Try and have as high ranged bonus as possible. Gallery ANOTHER 1M TICKETS GAINED !!

────────────── 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.

Want to buy with OSGP? Contact me on Discord! Detailed feature list: - Supports all 3 boats - Attack portals, defend knight mode - Repair mode (No HP exp mode) - Potions support - Sets auto casting spell after dying - Use Special attack weapons - Only attack monsters mode (Good for low cb players) - Uses quick prayer (make sure to setup before starting) - Worldhopper - Points spender - 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 589: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 589): -script 589:TaskList1.4515breaks (With breaks) -script 589:TaskList1.4515breaks.discord1 (With breaks & discord) -script 589:TaskList1..discord1 (NO breaks & discord)

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:

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

'the intelligent choice' by Czar Want to buy the bot, but only have rs gp? Buy an OSBot voucher here

Molly's Thiever This script is designed to quickly and efficiently level your thieving! Check out the features below. Buy HERE Features: - Capable of 200k+ per hour and 30k+ exp/ph on mid-level thieving accounts. - Quickly reaches 38 thieving to get started on those master farmers for ranarr and snap seeds! - Fixes itself if stuck. - Hopping from bot-worlds. - Stun handling so the bot doesn't just continually spam click the npc. - Drops bad seeds if inventory is full at master farmers. - Eats any food at the hp of your choosing. Supports: -Lumbridge men -Varrock tea -Ardougne cake -Ardougne silk -Ardougne fur -Kourend Fruit Stalls -Ardougne/Draynor master farmer -Ardougne/Varrock/Falador guards -Ardougne knight -Ardougne paladin -Ardougne hero -Blackjacking bandits as well as Menaphite thugs, this has limitations, click the spoiler below to see them Setup: Select your option from the drop down menu, it will tell you the location where the target is located. Fill out the gui and hit start. Simple setup! Proggies: Proggy from an acc started at 38 theiving:

Molly's Flax Spinner This script spins flax into bow strings at lumbridge, the script easily exceeds 1.1k flax spun per hour. Buy HERE. Requirements: - 10 crafting Features: - Hopping out of bot worlds Setup: Just run the script, no GUI! CLI ID: 861 Proggies:

Hi all, Hope all is well. In the last two months I've been botting OSRS pretty extensively as I've been in-between jobs (left old role for a new role set to start in September) and found myself with a lot of free time. I consider myself to be analytical and I always make a conscious effort to keep my biases in check. In these last few months, I've gathered quite a few insights regarding how Jagex's anti-cheat team operates, which I believe to be accurate and would like to share them with all of you today. To be clear, I have no direct line of contact to anyone working on the anti-cheat team so these are just conclusions I've drawn based on my personal experiences & those of fellow botters. My analysis will only pertain to bans issued manually to accounts that have purchased a membership and are highly diversified (NOT goldfarming) as I have no experience running F2P/P2P botfarms. Those are almost certainly handled by a different stream (RE: Botwatch). *** "Manual Ban" does not refer to a mod teleporting next to you and banning you in-game, but rather someone on the anti-cheat team screening your account (from a log of hundreds - thousands) and making a judgement call as to whether you've broken any rules *** 1) All bans issued on diversified/rested accounts with membership (questing, different skills etc) and don't goldfarm are due to manual reviews by someone on the anti-cheat team 2) The only way for a botted account (that satisfies the conditions above ) to survive is to avoid a manual review at all costs 3) The single most important factor in regards to triggering a manual review is total time online (I've found this figure to be ~12 hours) Total time online INCLUDES the time you spend playing legitimately on the account. ie: if you bot for 10 hours and play legitimately for 4 hours you WILL VERY LIKELY trigger a manual review Once your account gets reviewed, the entire history of your account is available to the anti-cheat team thus any kind of botting that you've done (no matter how long ago) is liable to lead to a ban An account that survives a manual review is not a reflection of the botters knowledge/prowess but the incompetence of the anti-cheat specialist reviewing your account False positives are 100% real as are false negatives (bots that fly under the radar). For evidence on false positives (incorrectly banned accounts) you can do a quick search on google and find mod tweets directly contradicting each other regarding whether the ban was accurate or not I've successfully appealed botted accounts that were played on only 1 IP address that were permanently banned for macroing major. Their response was something along the lines of "we identified unauthorized access to your account" (100% false / impossible). This confirms that bans are at the discretion of a judgement call that the anti-cheat specialist reviewing your account makes. The accounts that were appealed were highly diversified in tasks (quests, combat, skilling, clue scrolls, favour, mini games etc), and botted specific skills up to 4 hours consecutively (20 minute breaks per hour botted) 4) Avoiding hotspots for manual reviews is 100% key to not getting banned. Example of hotspots that are guaranteed to cause a manual review: runecrafting 1h+, Zulrah etc. Even if you do Zulrah or runecrafting legitimately for extended periods of time, your account will be manually reviewed. To reiterate point 3), any kind of botting history will be available to the anti-cheat specialist reviewing your account 5) The primary mandate of the anti-cheat team is to eliminate gold farming & real world trading. These are the primary forms of botting that directly impact Jagex's bottomline and as a [Chinese] financial sponsor owned company, you can be damn sure that is their #1 priority It is my belief that accounts with large amounts of wealth on them (100M+) are subject to more frequent manual reviews when flagged. This is because banning the account becomes a double whammy for Jagex 6) "Anti-Cheat specialists" are NOT data scientists, but regular customer support staff that are trained in that respect. Thus, it is my belief that in their training they are given relatively specific guidelines to follow to identify whether an account is botting or not. It is reasonable to assume that these guidelines are set in accordance to the most popular botting scripts & botted skills This explains why accounts that exploit an unpopular gold farming mechanic through private scripts have very low ban-rates. I personally have botted several accounts using such a script that has crashed very obviously (clicking the same spot for hours due to lack of failsafe) and ALL of them have survived. It is not unreasonable to assume that because of the sheer quantity of data collected on each account, the data scientists will only send a SELECTION of logs to the anti-cheat specialist to review (ie: hey John, please review the following woodcutting/agility logs on account X for the past week) It is my belief that the anti-cheat team is occasionally given unique mandates to follow through on (the recent NMZ banwave is a clear example in my opinion). This falls in line with them pursuing their primary mandate of keeping goldfarmers in check as Zulrah is one of the most efficient gold-farming mechanics in the game and accounts are being farmed EN MASSE to exploit it 7) Many people have reported a substantial improvement in ban rates when using mirror-mode instead of injection. This is a highly controversial topic because Osbot claims injection to be indistinguishable from other third party clients. Personally, I believe this to be unlikely because there have been many reports of tutorial accounts getting instantly locked when logging in from the injection client whereas the normal client logs in fine. Additionally, OSBuddy is confirmed to return a signature to Jagex that identifies it specifically as OSBuddy. It is not unlikely to think Runelite has done the same (I haven't found official evidence of this however) because it would be in the best interest of the owners of these clients to just play ball with Jagex. This, in turn, would make it very easy for the anti-cheat team to flag unidentified third-party clients for high priority review. It is important to stress that although mirror-mode appears to be the safer alternative, it is only one of the many factors Jagex uses to identify bots. If you don't bot responsibly, your account will get flagged all the same due to the aforementioned reasons in points 1 through 6. Concluding thoughts: Although avoiding bans will likely never be an exact science, I think we can make some progress by simply sharing bans we've recently experienced. In my short time here, I've noticed a famine mentality as relates to protocols & best practices to avoid bans. Although I understand why someone who relies on OSRS botting to put food on the table would want to keep to themselves, this attitude is clearly counter-productive to the advancement of botting as a whole. I will be starting my new role in less than 2 weeks and will not be doing much botting anymore, so I wanted to leave you guys with what I learned in hopes to start a collaborative discussion moving forward. Ban Report Example: Client: Mirror Time online the day leading to a ban: 12 hours Activit(es) botted leading to a ban: NMZ/ gold farming technique/ Woodcutting etc. Age of account: days, weeks, months, years etc. Alek's response to this thread: Best, Logicfury P.S. I will try my best to update the thread with any & all well thought-out insights (contradictory or supporting) and give credit where it is due

Just started a 24h trial on your acc - enjoy!

This is great, more diversity on certain small things should add in more antiban to the script. One request I have is can you add an option for ring of wealth charged to be added into the script (Equipped). Most times I prefer to tele to the GE to start next quest instead of fally :). Thanks for the update on animal magnetism.<3

An option to select food is now available on the GUI, while previously it only used swordfish, now you can choose between tuna, lobster, bass, swordfish, monkfish, shark, chili potato & cooked karambwan

The banking part may not work on mirror mode, like many other widget interactions afaik (like dialogues), but it should definitely work if you try on stealth injection What's printed in the logger when it stops? Is it on mirror mode? I have a few accounts almost ready for Animal Magnetism, will be going through it and pushing an update shortly

put your hand into your computer and feel if its very warm or not

Not only is it not allowed, but you are really not knowledgeable on hacking techniques to understand detection. I'm sorry.

@Maxlaxen thanks man! You made it working for me so far at least other then that it seems to run rather flawless

Nice job my friend.

The problem is that you have a ring of dueling as a part of your equipment setup. Simply switch it to a ring of life or something else and it will work.

Just a few areas of improvement: You're not consuming the events in the listeners, so that mouse data is being sent to the game. You do have access to the console for System.out.println walkPath does generate a path if you do not provide it a list of positions, but it's a lot cheaper than generating a web walking path The random number generator is already contained within method provider ConditionalSleep information is misleading. The timeout is 10 seconds, the recheck is every 2 seconds. It doesn't sleep "up to 2 seconds", it sleeps exactly 2 seconds. Also don't waste your time putting random numbers into conditional sleep, you can't iterate a fraction of a cycle. For instance, 10000/2000 = 5. The ConditionalSleep will have 5 cycles, each cycle being 2 seconds on the recheck, for a maximum timeout of 10 seconds. Pretty simple math. "if (getSkills().getDynamic(Skill.HITPOINTS) != getSkills().getStatic(Skill.HITPOINTS)) { //Checks if HP is full.", If you sara brew at full hp, it will say your hp is not full (which it is), use a < sign.

Thank you and yes it was mirror mode on the 2nd issue. Thanks for checking it out

Holy shit I was literally you 9 months ago.

Looks good my dude!

I used a separate thread to poll the status of grand exchange offers and notify the script execution thread of GE updates through the usage of the observer pattern. Hope this code gives an example of what to do. I made 3 files, an interface with a onGEUpdate callback method, a class implementing runnable; this is the code that the separate thread runs, and a utility class that keeps track of observing classes (classes implementing my interface); this class is also in charge of starting and stopping the separate thread. When the runnable class detects a GE update, it iterates through all observing classes and calls the onGEUpdate() callback. This is the class that holds all observing classes and the GE querying thread. It is meant to handle adding and removing Grand exchange observers. You should have something like NPCAnimObservableHandler that keep tracks of al classes that wish to be notified when a certain animation happens. Note that I have a stop method, call this under onExit() of your main script class! Otherwise when your script stops your second thread will never be stopped unless you terminate the client. package Util.GrandExchangeUtil; import org.osbot.rs07.script.Script; import java.util.ArrayList; import java.util.List; public class GrandExchangePolling { private List<GrandExchangeObserver> observers; //subscribed classes to ge offer changes private Thread geQuery; GrandExchangeRunnable queryRunnable; private static GrandExchangePolling singleton; private Script script; public static GrandExchangePolling getInstance(Script script){ if(singleton == null) singleton = new GrandExchangePolling(script); return singleton; } private GrandExchangePolling(Script script) { this.observers = new ArrayList<>(); queryRunnable = new GrandExchangeRunnable(observers, script); this.script = script; } public void registerObserver(GrandExchangeObserver o){ if(!observers.contains(o)){ observers.add(o); script.log(o.getClass().getSimpleName() + " is now an observer"); } if(observers.size() > 0) startQueryingOffers(); } public void removeObserver(GrandExchangeObserver o){ observers.remove(o); if(observers.isEmpty()) queryRunnable.stop(); } public void stopQueryingOffers(){ queryRunnable.stop(); } private void startQueryingOffers(){ if(geQuery == null || !queryRunnable.isRunning()){ script.log("starting ge thread"); geQuery = new Thread(queryRunnable); geQuery.start(); } } } This is my thread that iterates through the GE boxes and checks if any boxes have updated since its last iteration. package Util.GrandExchangeUtil; import org.osbot.rs07.api.GrandExchange; import org.osbot.rs07.script.Script; import java.util.HashMap; import java.util.Iterator; import java.util.List; import java.util.concurrent.atomic.AtomicBoolean; public class GrandExchangeRunnable implements Runnable { private AtomicBoolean running = new AtomicBoolean(false); private Script script; private HashMap<GrandExchange.Box, Integer> amountTradedMap; private List<GrandExchangeObserver> observers; public GrandExchangeRunnable(List<GrandExchangeObserver> observers, Script script){ this.observers = observers; this.script = script; amountTradedMap = new HashMap<>(); } @Override public void run() { script.log("starting ge query thread"); running.set(true); GrandExchange ge = script.getGrandExchange(); for (GrandExchange.Box box : GrandExchange.Box.values()) { if(ge.getStatus(box) == GrandExchange.Status.EMPTY){ amountTradedMap.put(box, -1); } else { int amtTraded = ge.getAmountTraded(box); amountTradedMap.put(box, amtTraded); } } while(running.get()){ for (GrandExchange.Box box : GrandExchange.Box.values()) { if(ge.getStatus(box) != GrandExchange.Status.EMPTY){ int prevAmtTraded = amountTradedMap.get(box); int amtTraded = ge.getAmountTraded(box); if(prevAmtTraded != -1){ if(amtTraded != prevAmtTraded || ge.getStatus(box) == GrandExchange.Status.FINISHED_BUY || ge.getStatus(box) == GrandExchange.Status.FINISHED_SALE){ for(Iterator<GrandExchangeObserver> iter = observers.iterator(); iter.hasNext();){ GrandExchangeObserver obs = iter.next(); obs.onGEUpdate(box); /*if(ge.getStatus(box) == GrandExchange.Status.FINISHED_BUY || ge.getStatus(box) == GrandExchange.Status.FINISHED_SALE) iter.remove();*/ } } } amountTradedMap.put(box, amtTraded); } else amountTradedMap.put(box, -1); } try { Thread.sleep(1000); } catch (InterruptedException e) { e.printStackTrace(); } } script.log("stopping ge query thread"); } public void stop(){ running.set(false); } public boolean isRunning(){ return running.get(); } } Note how my GEPolling class calls stop(). This sets a run boolean to false to allow graceful termination of this thread (it exits the while(run) loop). Finally this is the interface defining a method that observing classes must implement. package Util.GrandExchangeUtil; import org.osbot.rs07.api.GrandExchange; public interface GrandExchangeObserver { void onGEUpdate(GrandExchange.Box box); } I actually coded this and then later realized I don't need to use a GE listener to do what I want, so I currently don't have an example usage. If you need one msg me! Good luck with your project.

you can add me in discord, I can't STANLEGENDRES#8592

An NPC listener is a good idea, but you don't want to go overboard with too many threads for this. I would suggest a single instance of a class that handles all the listening, then all you have to do is tell it what to listen to and tell it what to do when it trigger something. However, anything that involves controlling your character should be handed in the main script loop and not in a separate thread, or things will get messy.

did tut island for me on 8 accs thanks

I thought this was the random section just with a different name.

MMA section instead, must go through a board of Trustees to be given permission to post. No casuals

come to chatbox

CBA still exists? Most useless role just like you nick

I am currently working on adding a custom event for allowing users to do any type of secondary action e.g. fletching or magic, but I need to get it 100% right before I push the update to SDN. I can't risk any complaints, or I can start offering it as a beta (experimental) option and add updates steadily to it Activated trials gl guys Please make sure you read the guide on avoiding rs bans: Agility is a skill which is super easy to over-bot, so please be responsible!