Can Jagex detect your bot client? (can jagex detect what client youre using)

[gillyjamie314]

On the stream where Ronan was killing bots, he asked Wealth if they were a bot. So they must have some kind of way to know if they are a bot or not.

 

[Iamramon]

On the stream where Ronan was killing bots, he asked Wealth if they were a bot. So they must have some kind of way to know if they are a bot or not.

Thats true. However he could of checked other things like log in times, and how long they were repeating the same skill etc.

 

[Sempiternally]

What about RID bots?

 

[Iamramon]

Their botwatch can detect what client your using what makes me belive this is because I had been botting with topbot about a week then one morning I login my acc with topbot client and get insta dced and 2 day banned

Nah that isn't enough proof. I logged in on osbuddy client and got banned instantly on log in. It was because the night before I was botting. They do that sometimes.

 

[EKOx REACTZz]

Their botwatch can detect what client your using what makes me belive this is because I had been botting with topbot about a week then one morning I login my acc with topbot client and get insta dced and 2 day banned

Ya that's called a ban lol that could of meant anything, same thing can happen with tribot, osbot, powerbot etc.

 

[EKOx REACTZz]

Thats true. However he could of checked other things like log in times, and how long they were repeating the same skill etc.

They cant possibly ban people like that, If I go on 8 hours a day doing agility only they cant ban me for that, unless they ban legit players too. Plus people get banned for botting an hour a day lol

 

[TBotting]

They really don't ban you because of your bot choice, they ban you because of the interactions of the script. All a bot can do is make it easier for the script developer to make good scripts. They have a system that builds profiles around users, and if multiple profiles match they will ban the users with those profiles, this is also the reason that if you test your script with only 1 account, you barely get banned. So the key to good antiban is not 'humanlike actions' but rather UNIQUE actions. And no, a simple random will not give you 'unique actions', because in the long run there will be an average from the random. Bots tend to behave very consistent while players are very inconsistent in their behavior (get tired after a while, random distractions like facebook etc).

 

[TBotting]

Lets re -structure that...

They have code inside the client which could be used to check whether any game code has been modified however whether or not they are using it for this purpose is unknown.

I would assume TriBot would xboot the Canvas considering that's what he's done in the past from what I know.

As for your class loader I'll admit that's probably the truth however I haven't seen any proof that Jagex is doing this.

I really don't think that you needed to 're -structure' that, especially since your 're -structure' didn't make any sense at all. XBooting is generally a bad idea since they can just check the JVM arguments that the game is being run with. That there is no proof that Jagex is doing this does not mean that it doesn't/won't happen, they might enable that within any minute, because it's all serversided. The clientsided part is already there.

 

[TBotting]

Their botwatch can detect what client your using what makes me belive this is because I had been botting with topbot about a week then one morning I login my acc with topbot client and get insta dced and 2 day banned

This is no proof at all, I'm 100% sure that they did not detect the TopBot client, since I know exactly what the client is capable of and what not. They just detected the patterns of the script that you were using (or/and you have been botting for retarded amounts of time).

 

[Trent!]

Why would you do it on a script level?... that's idiotic. Maybe ditch the idea of scripts? Who knows just you don't leave it up to the scripters.

Chill brah, I was just asking for clarification.

Also, how would one prevent profiling from the client-level?

What about RID bots?

Well RiD does not use a client; it controls your mouse and keyboard and requires a virtual machine to minimize it. Therefore, it's impossible to detect the program itself. Essentially, with the way it's designed, it's not possible to associate any RiD botter specifically with RiD software. For any bans that could occur, Jagex would have no way of determining what software was being used in those situations. Also, since it can't be profiled, any bans would be on a case-by-case basis, since mass bans wouldn't be possible from profiling.

 

[TRiLeZ]

On the stream where Ronan was killing bots, he asked Wealth if they were a bot. So they must have some kind of way to know if they are a bot or not.

If they weren't able to detect which people were/are botting, bans wouldn't exist. But they aren't necessarily detecting the client.

I really don't think that you needed to 're -structure' that, especially since your 're -structure' didn't make any sense at all. XBooting is generally a bad idea since they can just check the JVM arguments that the game is being run with. That there is no proof that Jagex is doing this does not mean that it doesn't/won't happen, they might enable that within any minute, because it's all serversided. The clientsided part is already there.

I could just xboot the class that has a method which returns the JVM arguments to hide the fact that xbooting is occuring.

There may not be code in the client to check for xbotting, and yes, they could use their reflection mechanism to call certain Java methods and return values (all server-sided). But according to my logs, they only use their reflection mechanism for the client classes.

Though, there are a lot more ways other than xbooting checking to detect a non Java web plugin is running the client.

 

[iJava]

Chill brah, I was just asking for clarification.

Also, how would one prevent profiling from the client-level?



Well RiD does not use a client; it controls your mouse and keyboard and requires a virtual machine to minimize it. Therefore, it's impossible to detect the program itself. Essentially, with the way it's designed, it's not possible to associate any RiD botter specifically with RiD software. For any bans that could occur, Jagex would have no way of determining what software was being used in those situations. Also, since it can't be profiled, any bans would be on a case-by-case basis, since mass bans wouldn't be possible from profiling.

To do it on a client level you need to incorporate unique features for each user; random breaks, mouse movements, different skill training etc.

 

[GrinderScape]

Nah that isn't enough proof. I logged in on osbuddy client and got banned instantly on log in. It was because the night before I was botting. They do that sometimes.

That could be coincidence as if you get a 2 day ban/perm ban then when you log in you will insta DC And get banned, they arent actually detecting the client.

 

[Jayzz]

They can. I got a friend that got banned, simply for logging into a bot client.

 

[TBotting]

If they weren't able to detect which people were/are botting, bans wouldn't exist. But they aren't necessarily detecting the client.



I could just xboot the class that has a method which returns the JVM arguments to hide the fact that xbooting is occuring.

There may not be code in the client to check for xbotting, and yes, they could use their reflection mechanism to call certain Java methods and return values (all server-sided). But according to my logs, they only use their reflection mechanism for the client classes.

Though, there are a lot more ways other than xbooting checking to detect a non Java web plugin is running the client.

I think that our best bet for now is hiding that we are a BOT, not necessarily hiding that we are a separate client. I'm glad that you perfectly know how their reflection mechanism works . I think it's good if we share our thoughts about these things, even though we are 'competition'.

 

[QUIT07RS]

use tribot