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

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

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.

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:

nope

Hello, I have completed a Zeah House Favour bot that needs to be beta tested. The bot is fully functional aside from minor issues that I need volunteer beta testers to weed out. Learn More About this Script: https://extra.funshinestudios.com/doku.php?id=scripts:extra_house_favour If you're interesting in achieving 100% House Favour for free, get in touch! Discord: Brandon#9592

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

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

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:

Want to buy with OSGP? Contact me on Discord! Detailed feature list: - Banks at Ferox enclave - Teleports Salve graveyard (Teleport tab OR Runes) - Teleports Drakan's medallion (Slepe) - Supports multiple locations in the swamp & Slepe - Swaps location is location is already taken - Hop world to avoid players - Use Quick prayer option to block ghoul damage option - GE support to sell Mort myre and restock new supplies 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! 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 1108: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 1108): -script 1108:TaskList1.4515breaks (With breaks) -script 1108:TaskList1.4515breaks.discord1 (With breaks & discord) -script 1108:TaskList1..discord1 (NO breaks & discord)

Want to buy with OSGP? Contact me on Discord! Detailed feature list: - Melee/Ranged mode - Tons of food support - Multiple ways to travel to forthos dungeons and bank - Herb sack supports - Loot alching support (Rune pouch possible) - Potions support - Weapon special attack support - Quick prayer support - Custom loot lists generation - Loots and banks - Loot item above X price option - Loot and equip arrows - Humanlike idles 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 1081: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 1081): -script 1081:TaskList1.4515breaks (With breaks) -script 1081:TaskList1.4515breaks.discord1 (With breaks & discord) -script 1081:TaskList1..discord1 (NO breaks & discord) Proggies:

Project AIO Hunter I will be releasing a completely re-written, brand new, version of Project AIO Hunter that will be replacing the current one on the SDN. Still packed with the features that made it great in the first place, you will now have access to even more advanced features with things that were not found in the previous version! I've re-written Eagles Peak and Varrock Museum as well, so it isn’t just hunting that got a big update. I've created an all new trapping system designed to work specifically on mirror mode. I've lowered the CPU usage and increased the overall stability in the script. I've got new logic for black chinchompas as well for people who enjoy the high risk, high reward lifestyle! Nothing has been taken over from the old version of the script. I wanted to give back to the community who has supported me since the beginning. With all this being said, please stay tuned to my threads for more new and information about the upcoming release! While I don't have an exact ETA for the new release, expect it to be somewhat soon. The new script is in testing now and will be released as soon as it is ready! If you currently own Project AIO Hunter, or buy it before the release of the new version, you’ll still get the new one for free. It will just be replacing the old one, so you will not have to repurchase anything. - Project

So I've been banned for Botting in November 2017. Its a maxed osrs/rs3 account created in 2008 and never botted on it, before the offence in 2017. I send Jagex an appeal a week ago telling them I'd like to apologise. Does anyone know how long they take to reply? It's been a week since the appeal. And has anyone had succes in getting their accounts back by telling them u're sorry? Also should I send multiple appeals since I have been waiting for over 7 days to get a response? Or just wait another week because of corona etc? I'd like to get some advice on how to approach this. Thank you

Enjoy!

Can i get a free trial please?

After using this for abit now i can say i love this script for training my range and getting some side cash :D! Got me from 80-91 Range so far and few extra mill in my pocket..

Enjoy the trial, Just get a proper connection ?

Will add some improvements to the rogue maze, update coming up. Same applies for dropping items, and hosidius (inside). I am starting to think that far away (max) camera zoom may not be ideal since it can click a bit far away (when screen-walking), maybe fiddling with the zoom so it's not too far and not too close? I will be making some more changes to this ASAP. @dmrfc92 will check that out, did you get that interface image online or screenshotted from the bot? it should only show one of those square thingy's, regardless I will improve that area too. Also for the 28 coin pouch, yep please make sure to leave a few inv. spaces free otherwise the bot will think it has full inventory of profit/loot and will always try bank - so when pickpocketing make sure you don't have a full inventory. In the meantime I will add an exception to the coin pouch banking part, thanks! As for running away (stalls): which stall? Please confirm, I will add more run-away paths. Also note: if you have enabled fight back then it will not run. I will also be investigating this option to make sure it fights back, especially for Guard dogs in Ardy/Hosidius. As for trials, will activate double trial so you can test the current version and the next upcoming version, gl!

Interested, looks very awesome and helpful, would love to beta for you

Gz on release

told to repost

Hey bud! Just purchased the fishing script, flawless! Can I grab a trial on this please?

enjoy your trial!

The only people I don’t buy scripts from are those who don’t have cute girls as profile pics UwU

Awesome, can't wait

Just wanted to say this scripts is fantastic - I havent tested every single thing but within reason I've had 0 issues when setup properly - great job and thanks!

Packet bots

There seems to be a bug where it gets stuck when trying to reenter hill giant area under varrock (with brass key). For me it got stuck somewhere in front of the door. Could be from setting combat tiles inside -> banking -> attempting to go back. Otherwise great script! One suggestion I would make is to add an option to bank when > inventory full or low health and no food. There seems to be two separate options which would work nice if they were combined

hey man, im free to test this tomorrow, added your discord

I'd give you 10m just for the fact it has a cute lil rocky

Sure thing. Trial granted .

"How did I get banned botting on runescape! It wasn't Monday or Thursday!" I just don't have the words.

Yeah as pointed out, you don't have a bad rep, but you don't really have a good one either. Being a member for 7 years is great but still not something people really take into account when purchasing accounts due to the risk involved.

Can I have a trial please? @FrostBug

@asdttt I'm not sure this is relevant to this topic but I remember years and years ago when botting in OSRS was still in its infancy (first 12 months) there was a client that upon booting up the client, users could opt in to help their mouse algorithm by doing a quick 1 minute clicking test (similar to the ones used to build click accuracy). Once done, it would save a file to the users Documents folder and then there was a thread for the users to upload the document to. All of this was used to help develop human mouse movement for their client. If OSbot implemented this, would this solve the problem?

This is gold. I've been wondering why my mouse recorder used correctly results in virtually 0 bans vs. Injection and even Mirror, even on flagged proxies. By the way, I'm pretty sure the random lag spikes on Mirror skews the mouse data a bit as well, which might be why it tends to result in fewer bans. They can only reliably get this data on the client-side, right? That means if they use mouse movements as a detection vector (they aren't collecting this data for no reason), this is their only way to do so - transparently. It's kind of odd people are contesting this despite you literally proving it with the deobfuscated code and demonstrating detectable patterns, but at the end of the day...What works is what works. Honestly, the only ways they can determine you are a bot are: Your script breaks and gets stuck for hours, dead giveaway. Creating patterns from your inputs and likely comparing them to other bots. Detecting scripts/bot client. Everyone claims the client is not detected, but you never know. They don't have to load classes or dlls for this, they can probably determine whether you're using a specific bot client or running a script on a certain client by checking your behaviours against all of the data they've gathered over time, and mouse movement evidently factors into this. There are plenty of people who play 15 hours a day farming Vorkath or something and never catch a ban, to say that you can never figure out a way to bot that long is obviously wrong. They aren't deciding who is and isn't a bot out of thin air. This is clearly one of the factors if not the most significant one, next to IP type and other patterns, like keyboard patterns if they gather that. After all, you have to move the mouse to play the game at all.

This is an interesting topic. If Jagex collects mouse movement - they don't do it "just because", there's a purpose for it, highly likely botwatch related. If Osbot manages to improve it's mouse movement and eliminate the obvious patterns - this could give a huge 1up against competion. Even if accounts survive a couple days longer with Osbot than with other bots - this will provide a significant business boost as word spreads around.

My own belief is that while things like third-party clients probably do contribute; detection is massively based on whether your account has similarities to other accounts (including banned accounts) - basic machine learning. Similarities including but not limited to delays and timings, account progression and so on. Reports probably trigger the server side AC system. Maybe large disparity trades do too. Is common information at SRL and has been for years. There was never a dll called jaclib.dll in oldschool runescape. That one only exists in RS3 so they couldn't remove it from oldschool since it never existed there to begin with. NXT actually has hard detection. jaclib.dll still exists in rs3 java client last i checked.

Are you keeping up with the flow of the conversation? I was stating why Alek's point is bad because they don't do that specific type of detection (hooks through SetWindowsHookEx) and Naked asked me for proof. It has nothing to do with other types of detection or other types of input. All types of input are detectable but not being detected (Integrity isn't being tested anywhere). Logitech's driver software isn't a MouClass.sys replacement. It's what you would call a filter driver. Lives at a higher level than MouClass.sys but it is still under Win32K.sys so it is in kernel space. All these methods are easily detectable unless your AC is running in userland. I will state it again; This type of detection doesn't exist anywhere in the game client. They don't test the integrity of mouse/key events anywhere in the oldschool runescape client. You can check for yourself but i can tell you that there's nothing nefarious in any native code in oldschool runescape.

You want me to provide proof of something that isn't there? Here, i'll just teach you how to do you yourself. Write a SetWindowsHookEx hook/detour and place it in a DLL which installs our hook in DLLMain. You can copy and paste any basic 32bit trampoline function. WinAPI functions all come with a standard useless 2 byte hotpatch point (mov edi, edi). This includes SetWindowsHookEx. The hook will notify us if any process (which has our DLL loaded into it's address space) invokes SetWindowsHookEx. Start oldschool runescape in a suspended state. Inject your DLL. Resume oldschool runescape so it is no longer in a suspended state. If the process calls SetWindowsHookEx then it has tried to create a hook. That's how you would detect windows hooks. Extra: You can grab the params which have been passed to SetWindowsHookEx. Including a function pointer and manually navigate to the code in memory (can use any decompiler) if you happen to find that hooks have been installed.

Got me gut laughing. I was in two minds about joining this discussion since I rarely take a front seat to these types of discussions but this one was way too fucking funny to resist. Shit, you can search memory for an array? OMG, you can use a disassembler?? bypassing DRMs??? Teach me how to be like you bro. Imagine belittling someone but being too ignorant or stupid to actually check if they even use the detection method. There is no low level native mouse or keyboard hook in oldschool runescape for the context of detecting injected input. It simply doesn't exist. Anyone with 5% of the experience you so humbly bragged about could easily check that before making a baseless claim on the detection of SendInput and contributing to the shit show here on this thread. Outstanding job pal. Keeping the discussion civil. It doesn't matter if you use SendInput or regular java event dispatching in the context of detecting the validity of input since there's isn't any differing integrity tests on input events anywhere in the client. Bytecode or native. While they're both detectable, neither are being detected. Keynoting that this says nothing about the timings, and delays of those events.

This is indeed a little disheartening to see, to be honest I didn't read through the github sample's to see how the code is getting sent, and I have no idea about what SendInput is, but it seems like that argument just distracted from the main point. Anyways, from I take you are saying, cut me some slack here, is that Jagex is taking mouse data collected at like 50ms, they slam that shit together, and then run simple stats on it, you called it mouseDelta or whatever the flip. Why is this unreasonable? I don't understand why this is insane, like if what you are saying is true that it can fit into 1mb for 3 hours, that's not that bad. Right? @Alek you stated previously that bot detection most likely stems from play time, skills trained ect. Wouldn't it be really easy to set a threshold, right, get the least amount of false negatives as possible, then we run the analysis on them to the point where it's like 99.9999% likely they are a bot. Is this unreasonable, why is this impossible. Honestly your responses haven't cleared up anything and your responses to asdttt have been very lackluster. Why wouldn't Jagex do this? I thought I'd look at your initial post Antiban doesn't matter - plain and simple. If you do any research into official claims made by Jagex, you can see why. They claim that both autoclickers and simulated mouse keys are detectable, and yes people do get banned for using them. For an autoclicker, the mouse doesn't move at all (don't get me started on pseudo number random generators for sleep time). So you state auto clickers and simulated mouse keys are detectable, maybe they have other behavior that makes them detectable. Gary's Hood and AutoHotKey are detected, both which use SendInput - which is Windows API. My thoughts are that they are just checking the stacktrace of mouse events and determining their source. So you think they are using SendInput... Ok that's great, asdttt has laid our proof and evidence towards his theory, you just state this without anything backing it at all. Additionally a while back they determined that HD clients are indistinguishable from botting clients, which also makes me believe they are looking at the garbage collector. Ok fair enough maybe they are but that doesn't have to do with the argument at hand But of course, go play around with antiban like everyone else has for the last 15 years - I'm really pessimistic in your results (nothing personal, but it's really a naiive approach). Then you insult him saying he's taking a naive approach. But isn't that just following Occam's razor? Then later on you guys get into a argument that made me want to jump off a bridge and die, and made me realize that I was wasting my time on a forum when I could be playing awesome games with cool hentai girls that like me for who I am ( btw I am cool and am 21 and can drink and drive [ not the driving part ] ) Oh sorry did I get off topic? My bad... Sorry to waste your time anyways... Because you're using SendInput... all Windows API functions can be hooked and detected. Look into JNI/JNA (Java). Please don't say something is undetected/hardware call when you're using a usermode public Windows API function call. You kept saying.. Ugh... Gary's Hood is literally using SendInput as well. Yes your mouse is detected because you can hook onto the windows hook chain and monitor for input thats generated by a real device vs those injected by application code - aka using SendInput directly like you are then he gives you a counter argument There's ZEROO evidence Jagex checks mouse clicks from a low level point. BUT, there is evidence they do from a HIGH level point. That point being the delay between press and release, and a few other minor details. (Which the majority of autoclickers have a delay of 0) Response Your. Autoclicker. Is. The. Same. As. Most. Autoclickers. You. Are. Using. SendInput. After that you no longer replied. He gave evidence, counter arguments, and in the end you just said the same thing over and over getting caught up about auto clickers being detectable by SendInput ( Again I don't know what the heck that is ). So to wrap up into a conclusion, can you argue his intial claims atleast can you explain why they are untrue, you just stated that they most likely detect using SendInput, why? He has code, he has evidence, can you give us that. Can you give a counter-argument, because just insulting him and going haha no stupid it's this other thing, why are you suddenly right? The truth is your not, you've done nothing to back up your claims. The only real arguments you gave were Jagex claimed they can catch autoclickers and simulated mouse keys. He gave responses to this and then you got caught up in the argument about SendInput ( what is that anyways?). Really what you need to do is disprove or make some sort of counter argument why his data is incorrect, or that Jagex does not use mouse movement as a factor in bot banning. If you are going to say that anti-ban is useless you need to be able to back it up, why should I blindly trust you? Additionally you could make a argument how Jagex detect's SendInput, if they are, is it in the code like asdttt showed with his mouse capturing. I would be more keen to believe you then, because yes, then capturing mouse movements would be pretty useuless if they could just detect fake mouse inputs, then it's pretty easy to detect a bot now isn't it, no need to grab data ect. I get what your going for but you do nothing to help your case at all. Lastly I want to say that if Jagex has the code, why not use it? Maybe they are tracking SendInput, but why not also just use the mouse tracking code as given here, asdttt gave us anecdotal evidence that it worked for him, I mean if you trust him it's pretty likely that it had a effect based on just the statistics he stated, it would be really lucky for some reason for him not to get banned after making only changes to the mouse movement. So I think that's everything I really hope you read what I have said and can try and make me understand your side because honestly I can't help but agree more with asdttt with the evidence, and better arguments laid out in this thread. edit: cut out the meat edit2: Don't hate me please edit3: Oh and bro I don't think it's a good idea to host RS's decompiled java code on your github, pretty sure they don't like that haha.

Well for starters, let's accept the fact that Jagex sends mouse movements to the server for analyzing, AND I myself was able to very very easily pickup on OSBot's using basic math using the exact same data they're sent. There's serious flaws in the movement, mostly the last bit where it ends. Please review my research so you too will actually see these flaws. I have no idea how you find this to be naive, especially since a fairly large amount of anti-cheats rely on mouse DPI movements to detect certain hacks - even aimbot. OSBot's mouse movement is flawed, as simple as that. If you dispute that fact, please give me insight because I'd love to see you defend that obvious pattern... FYI, many anti-hacks actually use 50MS tick sampling. Hell, minecraft's servers RUN on 20 TPS. It's a great number for anything but visual rendering. To Next, I've searched through the runescape source numerous times and yes. To say we're not ever able to bypass is a bit absurd considering WE are feeding them the data. You need to remember that even though Jagex made the client, they're still on a virtual machine. Java is VERY VERY manipulable on purpose due to how high level it is, and the nature of how it's deployed on many platforms - which I'm sure you already know. Autoclickers are easily detected because, as you said, they do not execute the same click as a mouse would. Although an internal autoclicker, as far as they know, does not produce the same flaws and you're then in control of nearly every factor including press/hold timings (Assuming you don't create flaws...). They also do not do any stracktrace checks from what I've seen, although tomorrow I'll be sure to search for that. If you'd like me to provide hard evidence on click sampling, I'll do so tomorrow. It's hard to elaborate without providing at least something to back me up. So for example: https://github.com/zeruth/runescape-client/blob/master/src/Client.java#L3371 That's where they send the timings of the mouse, and here's where they track the mouse input/timings (Using normal Java events)... https://github.com/zeruth/runescape-client/blob/master/src/MouseInput.java Also if they did detect all autoclickers, that wouldn't explain the HUGE amount of people using them on their mains and never getting banned. As for the garbage collector... Your actually absolutely correct on this one. Jagex at ANY time can request a sample of your garbage collector. IMO a garbage collector simply can't be enough to distinguish a bot client from an official client, but they could probably detect a difference between a non-official client and official. Although I could be wrong as I myself haven't personally tested the garbage collector timings, oldGen size, newGen size, or frequencies between collections. This would be banning solely on assumption though which I doubt Jagex would do. Here's the nearly-de-obfuscated code for that: https://pastebin.com/FzdBmKPL It's just measuring the actual collection events rather then memory consumption. Still though, this is a very unstable measurement and I doubt they'd ban us soly based on this. However.. There is one other thing they could possibly use to directly detect a bot, although I still kinda doubt they'd go to this extent. They have a class checker which they, like the GC info, can request at anytime. https://github.com/zeruth/runescape-client/blob/master/src/Client.java#L4315 Weird right? I'm sure they use it for debugging purposes and possibly client compatibility/version checking, but you can't deny they couldn't use that to snoop around the JVM and find some bot classes. Especially considering how specific java packaging is. And this isn't anti-ban. The whole "anti-ban" thing makes 0 sense. There's no such thing as some magical thing that makes you unbannable. It's a combination of your bot's ABILITY that lead to a ban, not checking skills, not taking breaks, and not talking in chat. For instance, mouse movement, button hold times, mouse click-rate (Yes IMO they take account for this), mouse hold-time, and so on. There's no SINGLE check on their anti-hack, so implementing new mouse movement wont suddenly make OSBot 100% undetectable. Although, it's a major step in the right direction. Not sure if you're aware of this, but there is a LAAARGE amount of people who bypass.. Not going to name any groups because of how censoring you guys are on here, but Ik that you know they exist so please stop pretending bypassing is impossible. Not to mention, I've still yet to be banned..? If you'd like to discuss this in private, I'd love to show you a much better way of moving the mouse without generating patterns. -- Oh and just to close this, who really cares what Jagex says..? You really think they'd give critical detection information out to the public? I doubt they'd even tell their own moderators what they use to detect the majority of bot clients. Personally, I think they purposely spread false information just to fool botters.. I mean come on, this company couldn't even do dead man mode correctly without killing everyone. Edit: Eh I made something quick with JavaFX to further display what I meant by autoclicker flaws (Press->Release): My normal mouse: ->> Mouse press timings (MS): 78 ->> Mouse press timings (MS): 63 ->> Mouse press timings (MS): 59 ->> Mouse press timings (MS): 70 ->> Mouse press timings (MS): 75 ->> Mouse press timings (MS): 87 Autoclicker: ->> Mouse press timings (MS): 0 ->> Mouse press timings (MS): 0 ->> Mouse press timings (MS): 0 ->> Mouse press timings (MS): 0 ->> Mouse press timings (MS): 0 See? When you use that windows event, you have a delay of 0. This is also true if you make an internal autoclicker, but don't delay your events. Jagex is sent this data which they collect using the JVM's event's. Edit2: Also please at least give me some level of respect. I'm not some random moron shouting at potential super cool anti-ban features. I'm a fellow programmer trying to help this community by finding flaws in OSBot. Many reject me simply based on my account age, but I'm not full of shit. At least read what I have to say and test it for yourself before tossing it out the window like it's meaningless.

How many bots do you think I've tested with...? 5...? No.. Well over a hundred. How many miner bots am I using right now? 3, simply because it uses lots of ram/cpu. Although when I'm not using my PC, about 10-13 max Let's move onto the actual subject, and then hopefully this argument will be over. I sampled the same data as Jagex, on the same interval. I found that not only is OSBot's mouse movement very robotic, but it also has constant flaws. I posted the sample comparing it to a humans mouse movement so everyone could see the major flaw. Now onto my "sample size" of banrates after changing my mouse movement. Been running miner bots, each for 6 hours a day, each on it's own paid proxy IP, each at the same exact mine. How many bans have I gotten? 0. How much profit? Surprisingly not that much because iron is fucking worthless. Minerbot results (Not including my other bots scripts): Before implementing new mouse movement: 56/56 bans - Each bot lasting exactly 1 day After implementing new mouse movement: 0/12 bans (Only have 12 accounts because there's no need to make more) Now banrate samples ARE NOT to be taken as evidence, but rather reference. These can very easily be inaccurate for all I know. What you CAN however take as factual evidence is the samples of OSBot's mouse movements. That's consistent, and you can see for yourself the output.

I'm not sure it's fair to say nobody knows how to fix this. A straightforward solution would be to record a couple thousand mouse paths of varying distances and base your script's mouse movements off these. Example: I need to move my mouse 70 pixels, I grab from my thousands of human mouse paths some that are around 70 pixels, say between 40-100. I grab one of those paths, stretch it or shrink it, add some noise to it and use that path to move the mouse. The downside to this is it requires a fair amount of work recording that many mouse paths and realistically is easier to do and probably better for not being "detected" if done by each scripter individually for their own scripts.

Solution is to implement better mouse movement that doesn't produce the same flaws (Although using OSBot's mouse + your own mover is fine too). I can't hand you all my own mouse mover or then I'd have to be worried about Jagex finding flaws in my own mouse mover and banning my ass. Just take what I've said, and fix it yourself. You're all knowledgeable with Java, and all have scripting experience. And maybe hopefully they'll implement better/different mouse movement on OSBot and then we'll only have to worry about the other ban checks.

I think the important thing to take away here is that they do at least send the mouse data to their servers, it doesn't look very human, and if they wanted to they could use this as one of many metrics to detect bots. That alone should be enough to encourage a change, whether it be in the way OSBot itself handles mouse movements or by us scripters to handle movement ourselves.

Here's a utility to sample mouse deltas: public class MouseDebugger { private int tick = 0; private int lastMouseX = 0; private int lastMouseY = 0; private boolean endedMovement = true; private int noMoveTicks = 0; private Script script; public MouseDebugger(Script script) { this.script = script; } //Run this on a 50MS tick, or whatever you want to sample on public void tick() { final Point mosePosition = script.mouse.getPosition(); if (lastMouseX != mosePosition.getX() || lastMouseY != mosePosition.getY()) { double actualDistance = Math.sqrt((lastMouseY - mosePosition.getY()) * (lastMouseY - mosePosition.getY()) + (lastMouseX - mosePosition.getX()) * (lastMouseX - mosePosition.getX())); if (actualDistance > 0 && actualDistance != Double.NaN) { script.log("Delta: " + actualDistance + " Tick: " + tick); } endedMovement = false; noMoveTicks = 0; } else { ++noMoveTicks; //Change according to how long you pause until making another mouse movement if (noMoveTicks >= 6) { if (!endedMovement) script.log("--Mouse movement ended"); endedMovement = true; } } lastMouseX = (int) mosePosition.getX(); lastMouseY = (int) mosePosition.getY(); ++tick; } }