Leaderboard

I believe so, and OSBot already uses them. But their logic is flawed (Unless this is their intended behavior?) This is OSBot's current clicking. Reason it looks like this is because they turn negative random guassians into positive, which defeats the purpose of using them unless you are purposely trying to create this downward graph? Obviously this is EXTREMELY easy to detect still, as they're hitting the minimum far too often This is their current "flawed" code for generating randoms for the mouse events. Might be used all over, I only verified that they use it for clicking. public static int gRandom(int iIiiiiiIIiIi, double d) throws IllegalArgumentException { double d1 = Math.abs(random.nextGaussian()) * d + iIiiiiiIIiIi; d = iIiiiiiIIiIi + d * 3.0D; if (d1 > d) d1 = d; return (int)Math.max(0L, Math.round(d1)); } Instead of that, they could do something like this public static int gRandom2(int iIiiiiiIIiIi, double d) throws IllegalArgumentException { double mod; double result; do { double guassian = random.nextGaussian(); if (guassian < 0) iIiiiiiIIiIi += d; mod = d * guassian; } while ((result = (iIiiiiiIIiIi + mod)) < 35); return (int) result; } This code is not perfect, it's just more of an example of a direction they could try. That code produces this

Script Factory Pro Edition has now been added directly into Script Factory 2.0! Checkout the purchase link below to grab the newest copy of Script Factory! Current list of features: 1. Click to Script 2. Fatigue mode 3. Randomized mouse profiles 4. Advanced debugger 5. Ability to increase method numbers by 'X' 6. Method number debugger 7. Autosave 8. Failsafe auto logout 9. Method Number Formatter (new) 10. Observer Mode (new) 11. Stat Tracker Export (new) ------------------------------------------------- Click to Script: - Build the entire base of your scripts by playing the game instead of scripting! Automatically generate checks and actions without ever having to input any information. The intelligent filter system is able to detect specific entities such as RS2Objects, NPCs, GroundItems and Players, as well as handle Inventory and widget interactions! Choose between Click to Script registering data by name, or id with a simple checkbox! Enable/disable Click to Script on the fly without ever skipping a beat. Finally, the future of scripting is here! Demonstration of 'Click to Script' in real time: Fatigue mode - A form of anti-bot detection that simulates human fatigue characteristics that are randomly generated for each account you run. No two accounts will have the same play-style. Data generated is based on real analytics collected from multiple credible sources, which including multiple university studies. This feature is designed to mimic the fatigue humans feel when performing a task over time. Randomized mouse profiles - Mouse data is a known variable that is tracked by Jagex. This feature is designed to randomize each of your account's mouse characteristics so none of them will be similar one another. You have total control over how random your profiles should be. Advanced debugger - Designed to make your job simple when creating scripts. Find all information you need in one place, without having to hover any Entity like OSBot's debugger requires. Auto cache, populate and update entities on the fly. Track in real time the data for your entity so you can do more scripting and less time debugging. Quest configs, Projectile configs as well as Animation configs have been added to make finding data even easier! Ability to increase method numbers by 'X' - Instead of being forced to increase/decrease method numbers by 1, you may now set a custom amount. This is very useful for users who would like to space out their scripts so they have wiggle room if they ever needed to add another method in later on. Method Number Debugger - Now specifically pin point any issues with your script in real time with the Method Number Debugger. It displays which checks are passing, failing, or are unreachable for any given method number so you may quickly fix any issues! Passed = Check was successful Failed = Check was unsuccessful Incomplete = Check was not validated due to the failure of a prior check Autosave - Say goodbye to losing your work! Now you may customize how often you want autosave to run. Your scripts will be backed up and stored on your computer for easy access. Failsafe auto logout - You will now be able to set a time threshold before your player logs out due to inactivity based on player movement, exp gained or player animations. You will also have the ability to take screenshots before logging out to help debug any issues that could have potentially occurred with your script(s) or public scripts. This will be very beneficial in preventing your account from logging in and out for hours on end, which should reduce bans caused by script malfunctions drastically! Method Number Formatter - Stop worrying about how pretty your script is while you are writing it. Constantly adding new methods, removing old methods, or even shifting things around causes your method numbers to become scrambled. Now, you may simply paste your script in the Method Number Formatter and have it prettify your code immediately! Observer Mode Control an unlimited amount of accounts via one client, and watch them mimic your actions. Harness the power of Click to Script with the new Observer Mode. Stat Tracker Export - Save all of your account's progress in a text file within your OSRS Script Factory folder! Whenever an account logs in, or levels up, their Stack Tracker profile gets updated. This is very beneficial to keep track of your accounts progress without logging in, as well as being able to hook up 3rd party applications to OSRS Script Factory and extract account data. More coming soon!

This is part two of my findings, although this time I created an entire 3D imaging software to bot with. Previously I was banned using a randomized alching macro script, paired with a HID device completely indistinguishable from a normal mouse in terms of appearance to native programs - although it took around two weeks of near constant alching. The software... Similar to how colorbots work, but based on imaging physical objects due to all the free libraries all over, computational speeds, and the simplicity of 3D objects in-game. I created a new software to control my HID device using a COM's port (Which it then translated to natural HID input). My mouse mover was a very advanced algorithm I worked on when I used to use OSBot, including a trained neural network portion which aided in speed/translations/overshoots/deviation/whatever. Multiple hours trained using my movements in-game to insure Jagex wouldn't be able to establish a difference between my movement, and the bots movement. The HID device was then seeded by https://www.random.org/ as generated a seed on a device is incredibly difficult due to the simplicity of the OS and overall hardware obviously. The bot, although somewhat slow at times, was very similar to my own movements. It's job was to simply mine for around 10 hours a day, then turn off. Then turn on the next day. Surprisingly this bot managed to net 3 million GP mining tin, in the course of about 1-2 weeks, with some days off. That compared to MirrorMode on OSBot is a MASSIVE increase in botting time. Sadly, it was just banned for Macro Major.. Ban cause speculation This ban bothers me. The software, undetected, the physical "mouse", undetected, the mouse movement, exactly as my own.. I'm really thinking, what pattern could possibly be this blatantly obvious that they would ban my poor bot permanently? No way it's the mouse movement? The pattern in mining, doubt it as it was based on my own (once more), and is simply too basic to detect a pattern. The timings? Should of been very random, with unbounded lengths (Meaning a random integer between 1-100 could result in 20,000 randomly), but still not ruling this out. Then lastly, the ban time frame.. It matches the alch bot near-perfect. A bot that did nothing but click a mouse, which didn't rely on software on the computer at all.. Is it possible that... Mouse down -> Mouse UP timing (A record I've already shown they logged), is responsible for these bans? Is it possible they're brute-forcing our seeds or using some type of algorithm which eventually learns our random patterns and can predict the next random number in the sequence (Given our randomizers use pseudorandom chains). Since we all use a static range of numbers between Mouse Down/Up, they will eventually detect regions of time of where our click events contain a constant, say 50-200MS between bound. Theoretically, given enough time, most numbers between these given bounds will result in the near-same number of uses. Writing an algorithm to detect a randomness pattern between the up/down (Or in other words, time it takes to click) would not be difficult, it would just require a lot of data. Furthermore, the ban rates tend to reflect mouse clicks. Agility for instance, requires clicking every 2 seconds. Essentially my conclusion: Randomization is a double edged sword. May appear random, but given enough time, creates a perfectly symmetrical shape. Instead of a horizontal random number picker, perhaps we need to look into more "human-like" randomization. Plans going forward... What I plan to do now, for anyone who cares, is to graph some of this data to visualize the data Jagex is being sent just to see how "random" looks. My next plan is to once more bot the living FUCK out of some rudimentary task, but this time with mouse delays based on my own timings. If I'm still banned, I'm just going to assume Jagex carelessly bans anyone who is doing a task for too long and this whole thing is a waste of time lmao The reason I focused on the mouse click delay in this thread is because it's the easiest input to track. No matter what bot, script, or macro you use, they all have randomized clicking. This is also the easiest pattern as it's consistent throughout all botting tasks

Done gl guys please join my discord for quicker responses

Update: Resolved. The issue seemed to be that I was unable to pick which Java version I wanted to use. I had to remove all versions using the following terminal commands; sudo rm -rf /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin sudo rm -rf /Library/PreferencePanes/JavaControlPanel.prefPane sudo rm -rf /Library/Application\ Support/Oracle/Java/ sudo rm -rf /Library/Java/JavaVirtualMachines Then I had to install a JDK 8 ARM version from Azul. This can be found here: https://www.azul.com/downloads/?version=java-8-lts&os=macos&package=jdk My java now looks a little funky but it works >.>

can i have a Pest control trial please

looking to try out the winterdot script have 3 scripts from you and love them!

Thanks for the reply! I was offline yesterday so didn't get to trial it but I'm sure it's pretty solid.

The hardware mouse is broken for me on my M1 MacBook air (Java 8 JDK, OSBot 2.6.42) the actually hardware mouse moves but the in-game paint mouse doesn't align to the hardware mouse causing it to click forever on nothing until i move the actual mouse it realigns causing it to click, however that defeats the purpose of using the hardware mouse as it shouldn't require me to constantly be moving the mouse for it to interact. I've tried the latest Dev build and to no avail, I've achieved no results. I need help please