Ban Coincidences - My findings (how to proceed)

So over the past month I've gotten quite a few high TTL accounts banned doing very mundane tasks that I've never been banned for on suicide bot accounts. That's fine -- expected even. I was lucky enough to have a bank of accounts available with a range of TTL's ranging from Max melee NMZ accounts with 1 everything else to max skillers, basically everything from 600 TTL - 1700 TTL available, so I decided to try and do some testing on ban rates, what I found was quite strange. I plan on using this post to outline my findings and see what people think. I will be excluding the name of specific scripts bots but include the general activity.

The general setup:
15 accounts total, different range of TTL.
Each one started with 1 bond of membership.
10 accounts were running with proxy.
3 accounts were running with VPN's to different locations.
1 account was run at my office
1 account was run at my house.

The Initial tests (based on what I was banned for previously):

Rock crabs - 3 accounts TTL ~ 600/900/1300 -- Suicide botted for 3 days straight no ban on any Account.

NMZ - 3 accounts TTL 500/750/1400 -- Suicide botted for 3 days straight no ban on any account.

Woodcutting - 3 accounts TTL 500/800/1100 -- Suicide botted for 3 days straight. 800 account permed (no priors)

Fishing - 3 accounts TTL 600/700/1500 -- Suicide botted for 3 days straight. 600 account permed.

Mining - 3 accounts TTL 500/800/1000 -- suicide botted for 3 days straight. 500 account permed, 1000 permed (both no priors).


The inital bans were somewhat expected, although I actually expected more bans. However, upon checking the logs I noticed something strange, all 4 banned accounts threw an exception that was consitent with bot breaking rather than being unable to login within 1 second of recieving a message to the account that it was banned for macroing. And all bans were at random times of the day.

I thought that was odd, so I started playing around with more tests, doing different activities from Wintertodt to Pest control, to Guilded altars, etc.

The guilded altar script bot is where I found my next "hmmmmmm" moment. While running it, I was sitting at my PC watching it on a 2nd monitor and I thought Ok let me give this account a break, so I hit stop on the bot, and instead of normally stopping it threw an exception. I also noticed at this exact time I hit stop the account logged out (not exaggerating). So I was like okay maybe it threw some wierd exception that interacted with the client. Tried logging back in and to my suprise was banned. I checked the message center and saw the message at the exact same second mark as the exception was thrown that I was suspected of macroing. I though this was very coincidental so I wanted to try and force this.

I loaded up 6 accounts with dragon bones/wyvern bones -- wasn't cheap. And started them all doing guilded altar. Every couple minutes I would try different ways of stopping the script bot. Either killing the processes, hitting stop, hitting the X, command line, etc. No exceptions were thrown for the first 2 hours and I tried every 15-20 mins or so.

Then it happened. On one account I hit Stop and an exception was thrown and the account was logged out. Banned, message center at same time as exception.

I tried again for another hour and same thing occurred.

Then I switched activites. I took 2 accounts to rock crabs and tried the same thing. One account was banned within 30 mins and I decided to stop my tests.


So.. I'm not pointing fingers here, but this was so coincidental and repeatable that I found it very odd.
Just to make it clear -- I am going to continue to bot appropriately, I don't encourage people to take the same approach I did -- but I thought this would be a neat experiment.

Any opinions here?

 

This is the part that is driving me insane. There is no errors/exceptions thrown in ANY log. The script bot's log just ends, as in the previous line was written but there is no graceful termination of the script bot, it's just an abrupt termination.
The Runemate log doesn't appear to have anything correlated to the error, the last line is:
[Biostatistics] An error of type FileNotFoundException occurred while trying to retrieve the movements of clouse pack dedF
[Clouse] Downloaded 989 human mouse movements selected for you by Clouse.

IMO that's unrelated.

The Runescape.log has some errors but IMO not correlated as well (there's no timestamps), but I see this error :
Java.rmi.RemoteException: Unable to retrieve the value of ej.o for 24735784; nested exception is:

That Java error could be thrown at launch of client, which would make it unhelpful.



To better clarify -- if you've ever hit STOP on a script bot and seen the script bot freeze and then rather than seeing a "Please Leave a Review" you see an Exception Window popop (doesn't terminate runemate - just the script bot), That is exactly what happened.

Just to confirm, this could be an issue with how this script bot works. I ran a quick test of starting and stopping the bot gracefully and no errors were thrown but the log does not actually log a graceful termination either which is incredibly unhelpful for this scenario.

 

So I just wanted to test around that error as well, I wanted to confirm it was NOT an error thrown at launch every time, since thrown at launch vs. seeing an error 2 hours later doesn't correlate.

I found that this specific error is not thrown every time the game launches. This leads me to believe it is one of these things:


1-The exception means absolutely nothign
2- The exception alerts jagex to activity and the account is automatically banned.
3- The exception was indeed thrown at launch, somehow alerts jagex the game is being modified, and once the account logs out it is immediatly banned. (less likely).

Personally -- I am incredibly confident that more than 95% of bans are not manual bans - they don't have the manpower to do this. But they are automated bans that are based off of something, such as catching a JVM exception or something.

--- Double Post Merged, Oct 25, 2019, Original Post Date: Oct 25, 2019 ---

If Anyone can clarify what this line means prior to an exception in Runescape.log:
Received command: zap

In every Runescape.log that I have that line is seen prior to an exception being thrown -- regardless of the exception.

 

Personally I don't believe runemate in itself is detectable, but leaning more towards what Savior had mentioned in that certain exceptions are detectable. Now these exceptions can be quite rare and I may have just stumbled upon a way of reproducing them out of sheer effort. Like I said in the Original post, it took me multiple hours of trying to stop the bots in strange ways to actually get an exception thrown.