Leaderboard

About OSTracker is a Client-Server implementation designed to track important data from people using your scripts. It has been designed in a way that allows multiple clients (scripts & users) to upload and store data to one server which runs standalone from OSBot and utilises MySQL 8. OSTracker is allowed on the SDN. Tracked Data (per user) Experience gained for all skills Items Received, Lost, or Spent (e.g. arrows and runes) Time ran Error logs (if setup) Future Data Script configurations Requirements For the server, you will need the following Java JRE 8+ (Download) MySQL Server 8 (Download) Ability to build the jar using maven A server to run OSTracker on OSTracker-Server code (Download) For the client, you will need the following A script The OSTracker client code within your script OSTracker-Client code (Download) Installation MySQL Server The MySQL 8 Server is the place all the user data is stored, and is required by OSTracker to function. MySQL Server should ideally be installed on the same server that the OSTracker server will run on, however that is not a requirement and it will work remotely with the correct setup on your end. If you are using a Linux based operating system, I would recommend looking up specific instructions for setting up MySQL Server. If you are using Windows, you can see the instructions below. OSTracker Server To run the OSTracker server, you will need a Windows/Linux-based server to run it on. Depending on your users, having a server is ideal as it will allow you to track data 24/7. Implementing the Server is quite easy using the instructions below. OSTracker Client The client implementation goes directly into your script, specifically into the onStart and onExit(), but you will need the entire OSTracker Client project source within your script. Instructions: Accessing the data There is no easy way to explain this, but you will at least need some experience with SQL to reliably view your data in the most accurate and effective way. Once you have connected to your MySQL Server, whether its through terminal or a third party software such as MySQL Workbench, you gain access to powerful queries that will allow you to view the tracked data in all sorts of ways. I have included some example queries below. Viewing all items received by all players in the last 24 hours SELECT username, itemname, status, sum(amount) AS cnt from `osbot-client`.`users` inner join `osbot-client`.`scriptitems` on `osbot-client`.`users`.id = `osbot-client`.`scriptitems`.user inner join `osbot-client`.`items` on `osbot-client`.`items`.id = `osbot-client`.`scriptitems`.item inner join `osbot-client`.`itemstatus` on `osbot-client`.`scriptitems`.itemStatus = `osbot-client`.`itemstatus`.id where status = "Received" and date > date_sub(date, INTERVAL 1 DAY) group by status, itemName having cnt > 1; Viewing Total Time Ran for all users in milliseconds SELECT username, sum(duration) from `osbot-client`.`runtimes` inner join `osbot-client`.`users` on `osbot-client`.`users`.id = `osbot-client`.`runtimes`.user group by username; Viewing Total Experience Gained for each user for a specific skill SELECT username, skillName, exp from `osbot-client`.`experiencegained` inner join `osbot-client`.`users` on `osbot-client`.`users`.id = `osbot-client`.`experiencegained`.user inner join `osbot-client`.`skills` on `osbot-client`.`skills`.id = `osbot-client`.`experiencegained`.skill WHERE skillName = "STRENGTH" group by username; Advanced Error Tracking It's possible to track and upload things such as Stacktraces which allows scripters to get ahead of issues quickly before users even report it, see the example below. In your onLoop, you could have something like the following try { // Logic Loop } catch (Exception e) { if (tracker != null) { StringWriter sw = new StringWriter(); PrintWriter pw = new PrintWriter(sw); e.printStackTrace(pw); tracker.getSessionTracker().getSession().addLog(sw.toString().replaceAll("\r", "").replaceAll("\n", "")); tracker.getSessionTracker().getSession().setVersion(getVersion()); } }

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

Most likely yes, other scripters that may be interested already have 10+ scripts, and may not be able to maintain them if they take over too many

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

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.

Setup Screens Smithing Mode Results & Show-off

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

PPOSB - AIO Fisher 1-99 in a single click! Click here to purchase! * Now supports CLI See all updates here: https://pposb.org/forums/forumdisplay.php?fid=1 Features: * Simple to use GUI * Progressive leveling or selective leveling * Advanced algorithms for object detection as well as predictions * Choose pre-defined locations or create your own * Choose between banking or dropping (shift-dropping supported) * Progressive mode automatically detects safe areas based off aggressive NPC's * Automatic detection for the best equipment you can use, or define specific equipment to use * Pre-hovering next interaction * Custom mouse and interaction handling system * Advanced paint display * Fail-safe's to make sure your player does not get stuck * Supports tele-tabs and well as traveling on ships * World hopping supported * GUI automatically updates locations available for your desired resource * Infernal items supported with special attack features * Takes a screenshot and logs out if you receive a pet drop * And much more! Script Details: Example CLI arguments: Script IDs: Project AIO Fisher: 1066 -script 1066:bank=true#grandExchange=true#altchat=false If using mirror mode, please make sure you set your Reaction time to 50ms! (To do so, hold Shift and press F4 until the Reaction time reaches 50ms) ** To reduce the risk of your bot getting stuck, please disable rooftops in your settings **

Thank you for providing fantastic support for your scripts can't wait to use again.

New Update (v113) - Added a patch for deposit box mode -- No longer gets stuck near the hopper trying to deposit ore Update will automatically go live within 24 hours, in the meantime please turn off deposit box mode in the Behavior tab (setup window), just until this update goes live ^^ Thanks all, and good luck, happy botting Special thanks to @takeovertheworld and @Fiji for help.

Have it set to mine in certain sector,,Multi-ore not enabled, used both repair strut every time and randomize strut repair, and no hammer will grab one then drop after repair. Regardless if strut repair is randomized or not bug will occur. Used both injection and Mirror mode I keep an eye on the bot and just pause and resume after banking myself and it will work for about an hour before happening again.

Confirmed double usage is fixed. Thanks a lot!

Let me give that another go, what is your settings used? Multi-ore mode and hammer to repair the sack or no hammer? Please confirm so I can get an accurate test. In the meantime I will try both and see if I notice anything which require updating. Stay tuned for upcoming update.

I have similar issues. [INFO][Bot #1][11/02 03:31:53 PM]: Idle timer reached, inventory not full, attempting to mine nearest ore! [INFO][Bot #1][11/02 03:31:53 PM]: TARGET POSITION IS: [x=3722, y=5649, z=0], is upstairs: false [INFO][Bot #1][11/02 03:31:53 PM]: Using route false to position [x=3722, y=5649, z=0] (35) tiles away [INFO][Bot #1][11/02 03:31:53 PM]: NoOb: in mlm [INFO][Bot #1][11/02 03:31:53 PM]: no obstacle found, try find the nearest rockfall! [INFO][Bot #1][11/02 03:31:55 PM]: "available_ore" changed to "0"

V1.16 Has been pushed. - Fixed double usage of bottomless compost bucket - Fixed displayed breaking time in paint

@RUNGOLD you will need to refund @woops you die the full service amount. We've come to this decision due to the admission of the use of proxies while training the account and claiming it is safer or to prevent this. Trading gear back and forth (if you were) and especially playing in general on an IP owned by a data center (99% of proxies) and if that proxy was being used by many more accounts is most likely the culprit of the ban, be it a chain ban from other accounts being trained and traded or trading items to this account specifically. It's hard to tell exactly but I highly recommend not using proxies to trade and train on users accounts of higher value due to this sort of risk.

i have joined ur discord , maybe we can chat and try fix it when ur next online mate =]

Definitely would love an update as well :). For anyone interested, still running now 10 accounts (4 bh only, 4 bh and farmruns 2 are played regularly) Ive received 3 farming pets now. Broke 90 hunter and farming this week as well. Thanks Token!

update us if you start, was gonna buy it if i liked it after trial but i guess i cant trial it now lol

Updated again to handle locked accounts

The kill count problem I noticed was with slayer mobs. I don't think I had wait for my loot option enabled

EDIT: Just realized the problem, I will post another update in a few minutes, so sorry guys! It should be back to normal in a few moments In the meantime, please enable the following options: - Make sure to choose a custom sector, I chose south-east as an example - Enable the option 'force stay in the sector' And it will work very well ^^