In my mind and the mind of many cheaters, I am the furthest along in cheating for Runescape 2. My knowledge is the most vast there is for now. I'm your most valuable resource as a community. I'd use my knowledge to your benefit... If I say something other than flamage, you should probably listen. (yeah I can be a dick at times, can't we all? lol) Semaphore was making option-pushing bots when I found him. I told him my concept of a bot, gave him my basic framework and he ran with it. Excelled, he even listened when I told everyone that they log mouse and focus actions, yet no one else listened until he posted more in depth information about it. (Oh yeah, you can ignore my flamage. I suggest you do that, as an "emo" I tend to have a bit of a vendetta against lives...)
Semaphore is gone, I can contact him because I have a real-life-relationship with him. But I'm not going to contact him to badger him when I can answer you myself... Which makes sense when you put into perspective that we were partners and shared source codes of practicly everything.
Anyways, to answer some inevetable questions, YES. I have xscar's sources well sources from early on in the project. Anyways, if any of you
remember, xscar is just the third generation of the thing I started (Scar-J [the java to scar communicating client]), which I abandoned due to lack of interest. If your memory is SUPERB you'll remember that before aryan, regex also worked on a project like this :-p. He too abandoned it. Just know xScar wasnt as good as it seemed... kkay?
BACK ON SUBJECT NOW.
I'm bored out of my mind. I've found more detection routines than anyone to date. I've shared most of them, not directly: I shared with semaphore, and he shared with public. (He figured you guys would listen, I figured you wouldnt so I never shared... He has more faith in people than myself though sooooo yeah.) Anyways, we should learn basics of things... There's an architecture that's been used for automated self-maintenance in server infrastructures for years, I forget the details but it applies very much so to bots nowadays.. Here I'll uml it.
bot -------------> updater
\ |
\--------------- bytecode
\ |
\--------------- regex
\ |
\------ dynamic memory
\ |
\_____ assumptions
Not too hard to understand in my mind, simply you have the Bot, it decides it's broken, it calls the updater, and the updater decides how it is broken, and applies one or all of the (4) methods of updating. They update accordingly and return the bot. Bytecode is of course bytecode, regex is of course regexing the source... Dynamic memory is what I outlined on how to do and then deleted half the article. Assumptions is my fiddle-stick "artificial intelligent" (as krichkovskoy says... lol) updater. Assumptions is the fastest updater, dynamic memory is the second fastest, regex the fourth, and bytecode the third.
We all know the first 3, the fourth one is too complex unless you're majoring in the field of mathematics or quantem mathematics... Because it's the use of datamining and complex algorithms to find patterns fast as shit.
Anyways, peace.