bcgsmx

I might not have been clear. By client side detection I mean, active detection. Obfuscation, packet encryption and client shielding are passive approaches. I don't agree it ensures they are in the losing side. Actually I've seen many games drastically reduce the amount of bots by introducing active detection. Active detection is not really effective on games which you can just create a new account and keep playing. For MMORPGs that's a different story, there is too much at stake (losing progress as well as thousand of hours gaming). I've seen games using anti-cheats even for passive protection being successful (Ex: Tibia). By successful I mean that they managed to decrease botting significantly. Of course they never completely stopped bots. We can agree that's near impossible. But I agree, that's a cat-and-mouse game and they will spend a lot of money that might not me be worth. Regarding Jagex, I didn't really say they allow botting. But that actually they don't care about small fishes at this point. By that I mean, they prefer to focus on ppl that are massively botting (using multiple accounts and single-handily making significant impact in the game) than banning individuals. Also I'm not saying they are ignoring individuals, it is still possible to get caught even casually botting, but less likely. I'm sorry if my statements were not clear in the last post.

I agree they can, but I don't think that computational resources are the only thing stopping them from doing it. Why? Well, client side detection will not consume Jagex's computational resources, since the resource that plays a whole here is your own computer. I would agree if were talking about engineering resources, since such mechanism would require programmers and an anti-cheat department. After all, client-side anti-cheats require constant maintenance and update. It is possible to detect any third party software touching yours, although sometimes it's not that easy. But I believe that, as of now, they don't even try to client-side detect (In an automated way). To confirm whether my statement is right, we would need to reverse their current client. I haven't had time to do that. Also, my knowledge mostly rely on reverse engineering natively compiled code (asm), but maybe some day I can give Java's bytecode a try. Not sure if our Java reverse engineering Gurus here (Aka Pandemic and Nezz) have analyzed the client in order to identify such a feature. But I think they did at some point. On top of that, bots still bring a lot of money to Jagex. I truly believe they don't really care about ppl who bots casually and NOT in obvious and stupid way. But that's just speculation on my side.

Are you sure about that statement? I think DB also uses injection. However its injection does not changes methods signatures (which I believe is how Jagex detects modified clients). For tha reason DB users are not getting detected so far. @Pandemic Can you confirm that?

Unless Jagex has some kind of client-side detection for injected code, you won't. Dreambot uses the standard client, it's not a custom client. From the server perspective, I believe they cannot tell the difference whether you're playing with dreambot or not. If there's any kind of client-side detection (which I believe there isn't, can't tell for sure though), your accounts are doomed since the first day you started using DB. If Jagex implements some detection in the future, you will eventually get banned. Otherwise you're good.

I believe any bans related to using non-authorized client will be 2 weeks long at first infringement (Unless you've been botting, which is not your case). Perma ban if continued infringement.

What requirements are we talking about? I believe DB3 would take the same approach as DB2 (injection if I'm not wrong) and unless there are some specific mechanism to detect injection, Jagex cannot differentiate DB2 client from their standard client.

For every quest, the first thing the bot tries to do is to pick up my money in the Grand Exchange bank. After that it doesn't do anything.