SqueezeTheorem

The only meaningful advice I can offer not already given here is that high-intensity activities like agility, runecrafting, and some kinds of combat have significantly higher banrates than relatively AFK things like fletching, NMZ, etc. I don't know what you're botting, but try out some AFK stuff for a while and see if it helps.

I've had this happen to very old accounts that I botted. I know for a fact they were botted, and should have had some stats, but instead I logged into tutorial Island. Not banned, it was just like Jagex's servers had no record of the accounts ever existing.

I have thought about better image recognition libraries, but I'm more interested in a proof of concept ATM. TensorFlow is the only library that I'm aware of that will work, but I'm sure there are others.

Writing a Color Picker Bot An idea I've had floating around for a while is writing my own private color recognition bot from scratch, and I finally got around to starting it today. It might seem like a lot of effort to essentially just re-invent the wheel, but there are a few distinct advantages a color picker bot offers over injection/reflection: Color bots don't interact with the JVM whatsoever, meaning any of Jagex's detection efforts that rely on observing things at the JVM level won't work Color bots generally won't break with updates. There's no need to deobfuscate new code, or remap memory values each time the gamepack changes. Having complete control of a bot client from the bottom up means you can alter low level code like mouse movement to see if any of the conspiracies about detection are actually true. I'll be addressing what low level features I plan to pay special attention to later as the client becomes more developed. This bot WILL NOT be released on OSBot or any other website. I am not trying to profit from this, nor advertise my own service. I just thought it would be something the community might be interested in and may shed some light on how Jagex detects botting, if successful. I've read that a lot of people have had a fair bit of success avoiding bans using mouse recorders and AHK, and I'm basically making a more sophisticated version of AHK/a mouse recorder. Screenshots/proggies coming soon. The first script I'm going make will be woodcutting/fishing/mining. Technology Used For this project, I'm only using Java and the native Java libraries. This might sound fairly restrictive, but I don't think it'll be a significant obstacle given the ImageIO, BufferedImage, and Robot classes built in the language. This bot will only interact with the game client by scraping colors and using the Robot class to left/right click. It's very primitive, and that's the point. Progress Log November 5, 2019: The basics of the client are up and running. The bot can determine when it's on the login screen, login in using a hardcoded username/password pair, click the red login button in the game lobby, and adjust its camera angle on login so scripts can be made under the assumption that the camera angle is constant. It's fully scriptable at this point. November 10, 2019: I've got the script set up where it can accurately determine the state of a fletching rotation, ie what the bot should do next. Click the bank, use the bow string, press space bar to craft, Etc. Planned Features Movement/pathing using the minimap. Inventory API Randomized, normally distributed sleeps on most actions that incorporates a fatigue system Next Goal function prototype script, even if the antiban is shit still.

Feel free to PM me, I have a lot of ideas floating around but don't wanna clog up this thread on theory crafting.

In theory, modern bot clients are undetectable, as they read memory locations in your computers RAM (reflection), instead of modifying the game client directly (injection) like some used to. Because of this, mirror mode isn't worth the computing resources involved IMO, unless you're botting on an account you really can't stand to lose (but if that's the case, don't bot it period)

Anti-ban is largely bullshit, and a marketing ploy. Based on what I can tell, the current bot detection system uses a combination of machine learning, statistical analysis, and even manual review to catch bots. However, there are some legitimate anti-ban techniques that can help you avoid being banned, but a lot of what you see is nonsense. The most promising form of anti ban (based off of my own experience) seems to be: Anti-pattern (not taking the same path every time, varying delays between actions, etc) Novel behavior (Doing weird shit to accomplish a common task, not doing a task in the most efficient or straightforward way) I once made a mistake with a f2p mining script, and left out one of the tin ore IDs, so the bot only mined roughly half of the ores at barb village. To my surprise, I was able to suicide bot up to ~60 mining without a ban as a level 3. I have my suspicions that my mistake of leaving out some of the ore IDs was such a bizarre behavior that BotWatch had no comparable behavior to compare it to. I'm doing some experiments with this sort of stuff right now trying to find out what's the most effective approach.

I should clarify that I don't expect control of reaction times by itself to be the best anti ban technique there is. I have a few other techniques in mind I've not seen widely implemented that I'd like to try. As far as I know from the research into other games I've done, reaction times, pathing, session length, and a few other things bots perform in very rigid fashion are the biggest giveaway to bot detection systems. Reaction times are just one piece of that puzzle. OSBot's API supports predefined paths and the A* pathfinding algorithm, which is great, but over many trips back and forth, a bot ends up revealing itself. A low-ban script that involves movement would need some kind of pathing that's more dynamic than A* or predefined paths, and that's what I'd like to attempt working on next. The end goal is to emulate human behavior extremely well for one particular task, and not tasks in general.

It's relatively simple to make a script with multiple tasks built into it, and have it switch between tasks when a certain condition has been reached (ie, lvl 50 fishing, or 25 woodcutting, or whatever). AFAIK there's nothing on the market ATM that can switch between separate scripts, but a homebrew option could work in theory.

The cache shouldn't, in theory, have any identifiable data inside it. The only thing you should worry about clearing is the random.dat file in the Jagex folder on your PC, but OSBot already manages that for you. There's speculation that clearing the cache helps, so if you really wanna be paranoid, go ahead, but it shouldn't make a difference. If Jagex did decide to hide identifiable information inside it, they could and we probably wouldn't know.

Anecdotally, the odds of the account getting banned are much higher. If you don't want to lose that account, quit botting on it. Eventually, you will be caught again, and it'll be a permaban.

I'm back to OSRS and OSBot after a long hiatus. When I left, I was planning a rather ambitious script that would auto mule, set up new accounts automatically, etc. I have another slightly less ambitious and more realistic plan this time around, but I'll spare the details for another post. The point is, I want to make a script with a low banrate. So, I put a lot of thought into how to make a script more human-like in relevant ways. One question that came to mind was "If you plot human reaction times in RuneScape on a graph, does it look like a normal distribution?" So, I wrote a small Java application to track the milliseconds between clicks when I spam clicked for a particular activity in game. Lo and behold, the time between clicks appears to be a normal-ish distribution. The x axis represents milliseconds, and the y axis represents the number of times that particular delay happened. So, if the black dot in the middle is, say, 125 ms, then that was the most frequent delay length (mode). Edit: More data Because I'm paranoid, I adjusted the the default size of this graph and hid the axis tick marks, but my experiment confirmed my suspicions that human reaction times would follow a normal distribution. My motivation for this scripts behave in a way that too consistent and too perfect. They make zero mistakes (when well written), their reaction times are predictable (typically following an even distribution), take the same path over and over again, etc. My aim here is to create an API built on top of OSBot that allows for more human-like behavior in areas that other MMOs typically use to catch bots. I know for a fact that other titles have used reaction times and analysis of player pathing to catch bots, and so I'm starting there first. I'll be gathering more data and updating this post, or creating a new one with more information that I uncover.

Based on experience, they're likely flagged.

About a month or two ago, 07 gp was $0.9 - $1.1/m, if I remember correctly. Now the standard is ~$0.7/m. Is there anything noteworthy going on in the RMT market causing the price decline, or is it just standard fluctuation?

Do you agree with the Requirments (included paying a deposit): I agree to the terms and conditions What tasks are you willing to do - Combat and skilling Skype - live:776bb962c928bb09 How long a day you can be online to do services - depends, but at or above the minimum of 2 hours Have you done other services before - No

What?

Yeah. Weekends used to be almost entirely safe, then you'd be banned Monday morning. So everyone started suicide botting on weekends, and now they've got weekend staff to counter that. We're kinda fucked. Jagex is getting pretty good at warding off bots now.

Yeah, I'd assume they use machine learning of some sort. The botting community is at a bit of a disadvantage though, since I've not seen anyone use machine learning to combat detection.

From the research I've done into how MMO's, and RuneScape in particular, detect macros, it seems clear to me that one of the primary reasons bots get banned is because they're flawless. Unlike humans, they don't make mistakes. After enough time has passed, analysis software can see a very clearly defined pattern of behavior an account is following, and know with near absolute certainty it's a bot. With that being said, is there any legitimacy to "anti-pattern" techniques? And if there is, what kinds of pattern-disrupting behavior should a scripter try to add to a script? The traditional "randomly examine an object" and "misclick once in a while" doesn't seem to be enough.

Multiboxing is a common form of macroing in other MMO's, but it's never really been a huge thing in RuneScape. Basically, you control one account, and all your other accounts copy the first account's actions. I wrote a primitive multiboxing client using OSBot that mimics mouse clicks. It's a proof of concept, but I'm not 100% sure if I'll be investing more time into its development just yet. The use case within RuneScape is fairly limited.

I will once I'm done recovering from alcohol poisoning lmao

Removed video due to name leak

If you had a long enough recording for a relatively simple task like fletching, I don't see how you'd even be able to get banned, since it's a recording of a human. I was interested in making something like this myself, but I'll definitely give this a shot. If this script combined with a long recording doesn't reduce bans, then Jagex's system is more complex than we probably imagined.

It'll be live soon. I'm gonna do my first large scale test by grinding chocolate dust in f2p on like 5 accounts. There's a few issues right now, like the camera angle needing to be manually adjusted. The API might allow me to do that automatically, but I'm not sure yet. It also doesn't currently support shift clicking. The current dev version can mimic right and left clicks -- nothing else. This means it requires that all accounts have the same camera angle (clicking the compass is the best way to set that up) and the same zoom distance. It seems to work best for bank standing skills. Resource gathering is a bit of a stretch except for fishing (since it's non competitive), and agility won't work due to the potential to fail courses, leaving accounts out of sync. Walking is a bit of an issue if you don't pause in-between clicking locations due to the slight delay. I also don't think this version would be allowed on the SDN for both quality control reasons and the nature of the script, but I can publish it on the forums. I'd like to post a video at some point going over the uses of the script, the caveats, and the benefits. I wrote this script because I have a suspicion it will prevent bans for botting since it's not botting, it's multiboxing. Whatever systems they use to track botting probably won't detect this, since it is still a human controlling it. It's also incredibly inefficient in terms of computing resources and relies heavily on the file system of the host machine, so all accounts involved have to be controlled on the same machine. So yeah. It'll be out soon, but it needs a little more work and definitely has its share of issues. I'd like to attempt a version of this script that doesn't mimic mouse clicks precisely, but instead finds whatever objects/npcs you click and copies that behavior instead.

Now if only I can find out what to do with it ahaha. I'm thinking herblore/fletching? Have like 10 accounts making unfinished potions lmao