Leaderboard

Bruh your Yew cutter was some world class 420 dank kush shit :'c Cya man, glll in College

Arctic's Road to Kick Ass Main Start Date: 13/09/2014 Starting Statistics Skills Goals Quest Goals Wealth Goals Thread under ongoing construction.

Peace out brochacho

Thats why we bot

Oh that is Jagex's own runescape server or some sort, and that is the message that pops up when a Jagex Mod logs into the game. I've seen it say that on livestreams too.

Not going to happen, good luck anyways

saw the skill goals not gonna happen buddy

It's Jacmob

ugly , pls no release

Only you would say that.

I hate when I get diarrhea.

Animal Magnetism for the ava's accumulator. Witch's house if you want 10-24hp boost Horror from the deep for the god book.

i think we have an obvious winner

If you are trying to run a java program on a system that doesnt have java, you cant use the program. Same goes for any language. For example, if you try to give me instructions in german, I will just look at you, because I have no clue how to speak german. ^_^

Disclaimer : post taken from another forum which will not be named. I would like if script writers read this post and express their own opinion, draw their own conclusion and the validity of the statement below. Client detection (client-side): Jagex detects if you're logging in from another client than the original one. How do they detect the client? - Check the title of the window (They did this in 2012) - Checksum of all files are being send to the server and they check if the values are the same (http://en.wikipedia.org/wiki/Checksum) - They count the methods/fields of all files and see if any code (hooks) have been injected like *** does now ("private int getHealth();") - They can check if cookies have been updated and where they're directing from, if there's a valid user agent according to your operating system and standard browser (http://en.wikipedia....Request_Headers) These are the only client detection methods I can come up now but there are definitely more Behaviour Analysis (Server-side AKA BotWatch): This is software running on the Jagex servers. Every action that you do will send a command to the server. If you click the rs-map ingame the client will send a command to the server like this: "Packet Id:137 X:3125 Y:1253" the server will calculate the path and send movement info with animations to the client which will display them. These packets can be used to track all activity on your account. And this is what they use for their BotWatch system How does BotWatch work? Well first of all nobody is sure but there are speculations/theories. I have searched some papers on Server side bot detection written by Profs/Students who are located in some of the best universities in the world. But here are some that I think Jagex applies: - Command timing: This is where they time the reaction time of a player when the server send data to the client. If the delay is too short or the delay is static you are detected. If you ploth this out on a graph you can easily spot out the botters. - Heat maps: They track all your mouse clicks and build heat maps where you clicked on an object / path. If you graph this out over time you will see bots use the same points but randomized by 20 coordinates while real players have different heat maps - Packet patterns: Tracking of all packets with their parameters and running a neural network with heuristics over it to see if any patterns have been detected - Simulation: (Probably used in the very early days of BotWatch) Jagex has a team of people which load whole a player's session (packet recording) in a closed environment and decide if the account looks like a bot. Thus they can watch your acitivity even though several days/weeks have been passed For more technical information on how BotWatch could work please take a look http://asp.eurasipjournals.com/content/pdf/1687-6180-2009-797159.pdf The reason why bots like (R** - cant mention bot name ) aren't so easy detectable is. It uses colors thus no modification (no client detection). It's slow because all it's actions are being sent from their server to the program. If a bot is not very functional the system is less likely to detect it. I can imagine Jagex setting a high enough treshold for their system not to detect any false-positive bots. If Bot's client wasn't decectable and you wrote a slow script with alot of unneeded camera / mouse moves you wouldn't also get detected. What does the future hold? Today bots and Jagex are in a code war, currently their client detection is very strong which we hope to surpass it within several weeks. After that Jagex will try to update their client detection. So you have to think Jagex ALWAYS has to take the first step and then we can anticipate. Eventually Jagex will run out of methods to detect the client and will mainly focus on scrambling data (which will also be killed in a matter of time) and their BotWatch system. If we can fully withdraw our attention from the client we can work on AI behaviour systems. There's no way they can defeat bots unless they can take legal actions or the owners get bored.

Yeah, what this guy said! Because, y'know, where he lives is the ONLY place on the entire Earth!

How do you accidentally chargeback someone? That's not a refund, it's quite the process to open a chargeback dispute. You could have Tool refund the 30 dollars, and send him another 30.

Whoever gives their guide, they won't be making as much so why would they want to tell you or anybody?

trial & error, nobody's going to hold your hand/leak their methods

damn that cat got pj'd hard.

I really like this thread because everyone of your points is valid. However, OSBot features stealth-injection (it modifies internal JVM class files to make it impossible to detect injected methods like Character.getHealth() VIA reflection (the only known technology they use to detect injections). I deobfuscate, fully refactor, and decompile the OldSchool gamecode every couple updates (OSBot's cool updater makes it easy to make their client human-readable, refactored & compilable within minutes!). They haven't changed it one bit. What I can say is that client-based detection is no longer the immediate threat. It's bot-watch and it's macro analysis based algorithms that really hurt. Jagex has even said it themselves that they're abandoning old bot-detection techniques like random events because bots have been smart enough to the point where all these old techniques no longer work efficiently. What's causing the problem is that botters, by nature are very lazy people. Most people are probably using the same script that makes the most amount of money, only training one skill, etc. They're not really playing the game... and this is by far too easy to see. How do we solve this? Well I haven't simply ignored these issues, I've been quite aware that some steps need to be taken to make bots play less like macros, and more like REAL players. Here at OSBot we're currently working on our dynamic web-walker which will be used to be able to schedule scripts around. This is an added plus, since botters are too lazy to switch scripts themselves! The scripts can be schedules in a way that will be almost random but smart. However all this is easier said than done. We're putting a lot of effort and yes these technologies will be available in the future. Again, there are many more things than what I have mentioned to prevent bans. More discussion is definitely welcomed .

LOL, with 3 accounts maybe.