This is taken from a forum, and describes alot well.![]()
This was not posted by a mod?
Also, if you'd randomize the packets how is the client going to read the packets?
This is taken from a forum, and describes alot well.![]()
Thread should be called "how jagex thinks they will do it"
you guys dont need to freek out just dont bot tomorow bots will be fine I'm guessing by the 26th (wednesday)
Examing the name, I now believe they will be implementing a regular ID change to ALL items in rs.
words
Quote Mod John A:
We write in a scripting language called RuneScript, which our Game Engine team has created specifically for making RuneScape content. The Java-based game engine then reads this RuneScript code and makes it all work. RuneScript is constantly being changed and expanded as we add new features to it to allow it to do new things.
They've been moving code into native binaries for some time. If they are intelligent they will continue to do this, including perhaps moving some game logic into dlls.
If I were designing the system I'd look at pushing the connection and communication code into the binaries. Then, you could probably have for example a hashcheck thread (running on the binary side) to watch the JVM's classloader for any changes to the client class files. And if it detects any then it fails to grant a connection.
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:
They've been moving code into native binaries for some time. If they are intelligent they will continue to do this, including perhaps moving some game logic into dlls.
If I were designing the system I'd look at pushing the connection and communication code into the binaries. Then, you could probably have for example a hashcheck thread (running on the binary side) to watch the JVM's classloader for any changes to the client class files. And if it detects any then it fails to grant a connection.
Jagex said:The project, code-named the ‘ClusterFlutterer’, will be launched as part of the RuneScape game update on Tuesday the 25th October permanently preventing “reflection” bots from working again.

