Lol logging in to a bot client is detectable period... No doubt about that look @ Rs3 for example.

This thread is idiotic, and you're a complete retard if you think a client will always remain undetectable. Just like Jagex updates the game, bot client developers are required to also update their client to reflect any changes (with minimal to zero work effort if they have a good updater in place). One day the client may be undetectable, the next anyone who logs onto the game with it gets instantly banned. Technology is ever changing.

 

If you don't know how something works, don't try to comment on it.

when did i say the client was ever undetectable, i was bashing devs for calling it stealth injection when it isn't stealthy at all lol.

whats wrong with you?

when did i say the client was ever undetectable, i was bashing devs for calling it stealth injection when it isn't stealthy at all lol.

whats wrong with you?

So you'd rather them call it "Somewhat Detectable Injection"?

So you'd rather them call it "Somewhat Detectable In

i would just call it client injection. 

when did i say the client was ever undetectable, i was bashing devs for calling it stealth injection when it isn't stealthy at all lol.

whats wrong with you?

 

So you're saying that you can get banned if you're playing legitimately on OSBot client?

 

Please, go sleep for a while, wake up, drink some milk, eat some fruit and come back. And then, rethink this whole thing. 

So you're saying that you can get banned if you're playing legitimately on OSBot client?

 

Please, go sleep for a while, wake up, drink some milk, eat some fruit and come back. And then, rethink this whole thing. 

You most likely can.

You most likely can.

Someone should get on the OSB client, and try to play exactly like a bot for 6 hours str8 :P

So you'd rather them call it "Somewhat Detectable Injection"?

Well stealth doesn't mean it's undetectable. It means it's hard to detect/difficult to detect. 

You my sir went full retard. Never go full retard.

is it not supposed to protect people from the aids that previous versions of osbot have given?

So you're saying that you can get banned if you're playing legitimately on OSBot client?

 

Please, go sleep for a while, wake up, drink some milk, eat some fruit and come back. And then, rethink this whole thing. 

 

You no comprehendo.

Jagex has a packet that it sends between the client and server where it detects class members and other reflection data. They use reflection techniques like Class.forName and Class.getDeclaredMethods() to detect their own genuine class members and injected/renamed class members like the ones OSBot injects.

 

Want to know how the new stealth injector works on OSBot 1 and 2? We get your Class.class from within the JVM and inject it with code that filters any injected hooks. This modified Class.class file is in your filter_XXXXXX.jar inside your OSBot/data folder. You can decompile if you want and see how it works. 

 

I'm sure Jagex has plenty of other ways to detect bots however. For one, the speed and accuracy of your script may not necessarily be anything like a human's! Scripters need to be smarter about the behavior they're hard coding into the bot.

 

Another method is definitely random events. Why do you think they keep changing them? They have a team dedicated to breaking them and trapping bots in them. Those bots can get flagged for bans.

 

In essence, its a vicious cycle that bot developers have with Jagex. We reverse engineer their client and improve our botting software. They reverse engineer our bot and improve their anti-botting software. 

 

Anyways, the recent bans have inspired me to implement some more fixes into OSBot 1 as it's the only stable bot right now. You'll be seeing improvements to the way your bot selects objects and such!

 

 

Jagex has a packet that it sends between the client and server where it detects class members and other reflection data. They use reflection techniques like Class.forName and Class.getDeclaredMethods() to detect their own genuine class members and injected/renamed class members like the ones OSBot injects.

 

Want to know how the new stealth injector works on OSBot 1 and 2? We get your Class.class from within the JVM and inject it with code that filters any injected hooks. This modified Class.class file is in your filter_XXXXXX.jar inside your OSBot/data folder. You can decompile if you want and see how it works. 

 

I'm sure Jagex has plenty of other ways to detect bots however. For one, the speed and accuracy of your script may not necessarily be anything like a human's! Scripters need to be smarter about the behavior they're hard coding into the bot.

 

Another method is definitely random events. Why do you think they keep changing them? They have a team dedicated to breaking them and trapping bots in them. Those bots can get flagged for bans.

 

In essence, its a vicious cycle that bot developers have with Jagex. We reverse engineer their client and improve our botting software. They reverse engineer our bot and improve their anti-botting software. 

 

Anyways, the recent bans have inspired me to implement some more fixes into OSBot 1 as it's the only stable bot right now. You'll be seeing improvements to the way your bot selects objects and such!

 

Thanks on the input on this, this makes sense.

This thread is idiotic, and you're a complete retard if you think a client will always remain undetectable. Just like Jagex updates the game, bot client developers are required to also update their client to reflect any changes (with minimal to zero work effort if they have a good updater in place). One day the client may be undetectable, the next anyone who logs onto the game with it gets instantly banned. Technology is ever changing.

 

If you don't know how something works, don't try to comment on it.

 

 

i never said it was ever undetectable.

moron.

FUCK IT.! They haven't touched any of my bots that I've ran since the new update so maybe I'm just lucky or I just have reasonable breaks set up

I've been druiding on one acc since 30/30/1 and I'm now 76/84/76 not one ban yet