Sadly, the anti-cheat is not something I'm too knowledgeable in. Half of the story is visible in the client: which data is tracked, and when (as well as some visual adjustments to defeat older colour-recognition bots such as SCAR) - as well as the data scrambling I mention in the article, though this was more likely meant to break all third-party clients and packet sniffers.
Knowing how Jagex used this data once they'd tracked it isn't something I have much of an idea about, though.
On the wink: I wrote this article by hand over a couple of weeks back in May; I used AI to provide wording review on some of the more technical sections, and to create the SVG diagrams from my specs.
Hi, I'm the author - no it's not an analysis of the Lost City codebase (though I am a contributor to LC).
Most of the knowledge came from my refactor of the #317 RS2 client (https://github.com/Jameskmonger/317refactor) though I looked at some other decompiled versions while writing this blog post.
Sadly, the anti-cheat is not something I'm too knowledgeable in. Half of the story is visible in the client: which data is tracked, and when (as well as some visual adjustments to defeat older colour-recognition bots such as SCAR) - as well as the data scrambling I mention in the article, though this was more likely meant to break all third-party clients and packet sniffers.
Knowing how Jagex used this data once they'd tracked it isn't something I have much of an idea about, though.
On the wink: I wrote this article by hand over a couple of weeks back in May; I used AI to provide wording review on some of the more technical sections, and to create the SVG diagrams from my specs.