xhannyah

That first statement is just not correct. A detection process isn't as cut and dry as simply sending a request, getting an output, and poof they magically know. What kind of data do they need to have the system make these determinations and how do they obtain it? (Eg. How do they get it from the end user). Let me use botting as an example, since they make these determinations through the same process. When we access their server by playing rs, they already have some basic info on our system. Nothing useful on its own. Now, the kind of client we use and how we use it -- that's the useful part. Even small things like how the applet is loaded plays a role in designing a process in order to make these determinations automatically. On an injection client, the system can analyze the injected code and cross-reference with the data already in their database (which does take additional computational resources, as opposed to what you wrote). On injection clients this can happen in real time, and there are instances where you get banned minutes into botting on an account that wasn't flagged and/or botted before. This also means it takes less resources than with reflection, but it does still take resources or you would get banned seconds into logging in. Is much more complicated on a reflection client. The system has to collect all sorts of data. This includes data stored in the ram. Once an account gets flagged by the system for whatever reason, the system pretty much "targets" the account -- collecting and analyzing more data over the next few days until it automatically reaches a conclusion. This generally happens 12-24 hrs after the initial flag but it can take more time. As with injection, it also needs to cross-reference with their databases, which is why private clients and sometimes private scripts don't get banned that easily. All of this takes resources and more often than not, manual work. This also means that, if you're using a true mirror client, you're not botting, and your account isn't flagged, it is highly unlikely that you will ever get banned in this situation. @bcgsmx

They're issuing Macroing (major) account bans for the use of unapproved clients on accs that already had a previous, active Macroing offence.

Jagex can detect all non official clients that are publicly available, including true reflection bots that reflect clients externally. Why won't you get banned by just logging into a botting client (although, they did ban a bunch of open osrs users who weren't using illegal plugins) is simple: Computer resources. It would take a ridiculous amount of resources to monitor each and every account at all times. Therefore, Jagex's system uses specific criteria to flag accounts, monitor them somehow (This can include obtaining data from your ram), then the system automatically determines if it should ban or not.

Is this still available for purchase somehow?

I make 5k usd a month from botting (gp + accs).

Long story, short: My current username is also my generic gaming related username and I wanted a different identity for botting. Change it to: FushigiBot (F and B capitalized if possible)

It happened again. It seems to happen randomly. Trying to run the script multiple times will eventually launch it. Log: 6:11:25 PM: [INFO] Account successfully set to ***********@gmail.com! 6:11:28 PM: [INFO] Now loading Sub Quester - Advanced Lifetime... 6:11:28 PM: [INFO] Saving client settings... 6:11:28 PM: [INFO] Client settings saved successfully! 6:11:28 PM: [INFO] Successfully saved client settings! 6:11:38 PM: [INFO] Connecting to server... 6:11:38 PM: [INFO] You have successfully been logged in as xhannyah! 6:11:38 PM: [INFO] Your current rank(s): [MEMBERS] 6:11:38 PM: [WARN] This script had a problem starting. Check the console for more info. 6:11:38 PM: [WARN] This error usually happens if it's an instanced script and you're running too many instances. 6:11:38 PM: [WARN] If you think this is incorrect, please try waiting a couple minutes and try again. 6:11:39 PM: [INFO] Toggled console!

It's somehow working now, lol.

Can't launch the quester or builder after yesterday's update. :x