How Jagex will do it.

[Above All]

They will not do it, simple.

They've lied in the past. They still lie. They will continue to lie.



Tuesday - The day jagex fall.

 

[JaminB]

Lets hope so!

 

[naggiii]

This is a great post. I really enjoyed reading it, and I got a sense for how this is all going to go down (if it is), rather than just "bots are going down, yo." Thanks a lot.

 

[RAW BslAyA]

Great post, very informative

 

[Thor12]

Jagex has a history of failing lol. They will probably add to that history.

 

[JaminB]

Yeah, but I doubt they would announce something like that unless they were pretty confident it would work. I don't want to play the devils advocate but, they have people more knowledgeable about how bots function than most of us here on Sythe.

I think there weakness lies in the fact that most bot developers have put to much time and money into their clients to just let Jagex win.

 

[Yenthe666]

"ClusterFlutterer works against reflectios bots, which are in fact close to all of the bots in the game. What "reflection" bots do is take the packets sent by the RuneScape server and decide what to do based on what information they receive; they "reflect" on the information they get. Now what ClusterFlutterer will do so take the packets, (clusters) and change around the way they are sent randomly, much like encrypting it. By doing this the bots will not be able to read the packets and therefore cannot operate.

An example is the way a bot can bot Frost Dragons. It knows where they are located from the packets the servers are sending your game client so it can tell when the orb is circling your way. Now with these encrypted packets they cannot tell when the orb is coming.

"Injection" is the way that reflection bots load. They inject "hooks" into the game, and retrieve the packets. These packets they receive will be encoded, rendering them useless.

The other 2% of the bots (yes 2%) are pixel color bots. These bots use the colors of the pixels on your screen and click on them then. This means you can make a bot that picks flax - by clicking on green pixels. But this makes it impossible to bank or enter your pin.

So yes, Jagex has found a permanent solution to botting, that is, until the bot coders decode the packets. And once that happens Jagex just encrypts them differently."

This is taken from a forum, and describes alot well.

 

[DMR]

After reading the quote above, I have a sense that JaGeX know what they are doing... it just really makes sense. I'm neutral on if this should happen or not... I want it to happen as the economy is shit but I also want to make my bills.

 

[rsz_belgium]

Very learnfull post,,, glad you shared it. Time well decide what is going to happen

 

[ifh]

If we're back to colour and pattern recognition jagex should release flax coloured armour

Really looking forward to this if it's really a permanent solution.

 

[septicon]

Change to Required Java Version -> "It gives us many more options in the fight against bots." They WILL use Java.

 

[Dipshoe]

they use prg called xeofex made by zynga people who did farmville and etc....
it will block all duplicated clicks... and and multiple clicks on spots .

 

[JaminB]

they use prg called xeofex made by zynga people who did farmville and etc....
it will block all duplicated clicks... and and multiple clicks on spots .

No, they won't use that method because they have already tried to use it in their macro detection software. Bots are too smart for this now a days. Most modern bots have a "pixel radius" from which they draw a central point and then click on pixels around that point...thus no bot clicks the same place twice ever.

 

[Dipshoe]

No, they won't use that method because they have already tried to use it in their macro detection software. Bots are too smart for this now a days. Most modern bots have a "pixel radius" from which they draw a central point and then click on pixels around that point...thus no bot clicks the same place twice ever.

ye the xeofex has other stuff

 

[Emperor Nero]

I was looking at the post about the 'encrypted' packets, if you look at it - encryption is pretty simple. You just have to find the algorithm and I am fairly certain you could probably pretty easily reverse engineer it - or find a leak in the jagex staff.

 

[Dipshoe]

guys i just got word that this is not just one program this is multiple programs

 

[Emperor Nero]

guys i just got word that this is not just one program this is multiple programs

When you know whatever you hell you are talking about, you can come back - but posting this retarded stuff isn't making this thread better.

OT: It shouldn't be too long after the update that the bots will be back up though.

 

[JaminB]

I was looking at the post about the 'encrypted' packets, if you look at it - encryption is pretty simple. You just have to find the algorithm and I am fairly certain you could probably pretty easily reverse engineer it - or find a leak in the jagex staff.

Actually most encryption algorithms now a days are pretty advanced, and knowing the proper algorithm will not bi-pass the encryption you need the key. But encryption of this type is really irrelevant because reflection/bcel takes place after data is sent between server and client. These methods get data directly from the RS client so any encryption between server and client (if any) has already been decoded client side.

Now they may try to encrypt the client with "classguard" which would make it impossible for reflection and bcel to work. However, Jacmod and other developers have actually broken classguard encryption before so if they do choose to do this it's really nothing that new.

 

[mercatres]

Re-write the client in a NOT Java language.
I though they said they will update their java version? (Prob JRE 7)
They might also use their own Java (Jagex has a lite version of java wich holds just what runescape needs, this opensource and comes with the desktop client). But still, they wont stop using Java


Mix-up item IDs on a regular basis.
They did this 1 week ago (change all ID's of the randoms).
Its not going to work as most scripters use names of objects/items rather then its ID's

This is what TRileZ said:

Here's a list of possible upcoming methods:

• Returning null when a bot tries to load a class from the client. (Using the stack trace, and having their own classloader.)
• Tracking where the Canvas.getGraphics() method leads to.
• Looking through the loaded threads or thread groups of the jvm.
• Looking through the loaded classes of the jvm.

Since this only affects reflection bots, the first possible method would be my best guess.

 

[Mr Slaughter]

Very interesting. Everybody has their own views, but only time will tell i suppose.