SRL Archive - Bot Information and Spottings

Hey, Hey. We all know Jagex always tries to detect our botting. Sometimes succesfull, other times they fail. Now most people think Jagex looks only to things like exact same clicks, doing the same procedure a lot, being on for very long periods BUT I think they got other ways as well, including :

- Whenever you fail to solve a random Jagex priority to track you increases a bit (explaining people being banned after failing randoms like mime and mordaut a lot)

- Jagex might look if your name is called by someone in chat, and how many times it has been called, and how many times you did or did not respond ( they do this only after suspecting you I think)


So this were a few of my idea's Jagex uses to track us. any other additions would be greatly appreciated :)

i think that first one is true..
the chatting one isn't i think..
would be huge work.. and that costs time:rolleyes:
tough.. this has been told for a lot of times now..
your not the first one:p

@ the first one.
Our autoing accounts log-off if they find them selfs in a unsolvable random.
It then goes to the next player then after it has finished autoing we then go back can do the random ourself.

From: smithsps
@ the first one.
Our autoing accounts log-off if they find them selfs in a unsolvable random.
It then goes to the next player then after it has finished autoing we then go back can do the random ourself.

i think that is what rs checks for.. loggin off when you get an unsolvable random:rolleyes:

Yea and the second one only will be used IF they already suspect you ( a computer could do that i guess)

Yeah, I'm sure Jagex is able to see when people log out while having a random.. So the randoms are a pretty big problem :P

About calling your name, that isn't a problem at all, since it isn't hard to write a script that just says 'Hello' when your name is called..

There seeing if you say the same thing everytime

or just say a same group words
1st Time: Hello
2nd Time: Hey
3rd Time: Ello
4th Time: Hello
5th Time: Hey
ect…

It can be bigger but if they keep asking…

Jagex says in their own rules that you shouldn't report someone for macroing for simply not replying since they can have their chat on private. I know many scripts that put all chat on private to start with, but even if they don't a lot of high levels feel the need to ignore anyone below 100 so that isn't part of their macro-detection system. Logging out during a difficult random just means you are sick of it and running out of time. I guess they can increase their watchfulness of you but that alone wouldn't be enough for a man, I think.

From: lakerzz8
Jagex says in their own rules that you shouldn't report someone for macroing for simply not replying since they can have their chat on private. I know many scripts that put all chat on private to start with, but even if they don't a lot of high levels feel the need to ignore anyone below 100 so that isn't part of their macro-detection system. Logging out during a difficult random just means you are sick of it and running out of time. I guess they can increase their watchfulness of you but that alone wouldn't be enough for a man, I think.

But what if a mod comes across? You can always read a moderator's messages even if you have your chat on private.

Methinks scripts need to logout when a moderator comes nearby, to prevent them from detecting you.

{*******************************************************************************
function FindMod: Boolean;
by: Stupid3ooo
Description: Results True if a mod is found, then it waits 10-20 mins and logs back in
*******************************************************************************}

function FindMod: Boolean;
var
  tx, ty: Integer;
begin
  if (not UseFindMod) or (not LoggedIn) then exit;
  if (BmpMod = 0) or (BmpAdmin = 0) then
    LoadSRLBitMaps;
  if (FindColorTolerance(tx, ty, 14737632, MCX1, MCY1, MCX1 + 40, MCY2, 15)) or
       (FindColorTolerance(tx, ty, 589815, MCX1, MCY1, MCX1 + 40, MCY2, 15)) then
    if (FindBitmapToleranceIn(bmpMod, tx, ty, MCX1, MCY1, MCX1 + 40, MCY2, 15)) or
     (FindBitmapToleranceIn(bmpAdmin, tx, ty, MCX1, MCY1, MCX1 + 40, MCY2, 15)) then
    begin
      Result := True;
      WriteLn('******** FOUND MOD ********');
      WriteFileString(TheFile, '******** FOUND MOD ********' + Chr(13));
      TakeScreen('Found mod');
      Mods := Mods + 1;
      SaveToChatLog;
      Players[CurrentPlayer].Rand := 'Found Mod';
      repeat
        Logout;
        Wait(1500 + Random(500));
      until not (LoggedIn);
      Wait((60000) + Random(60000));
      LoginPlayer;
    end;
end;

You do not think.

Scripts already do that :p It is include in findnormalrandoms.

From: hylian_loach
But what if a mod comes across? You can always read a moderator's messages even if you have your chat on private.

Methinks scripts need to logout when a moderator comes nearby, to prevent them from detecting you.

Lee beat me to it but I was going to say, scripts do log out when mods come round.

Wow, cool.

I've never really botted long enough to encounter a moderator in-game (Because of the Morduat random), but I'm glad there's one less thing I'll need to worry about when creating my own scripts.

I would try using a world that you cant speak in. Since the quick-chat you cant speak in some worlds and Jagex might not know that you didn't know about the quick-chat.