Jump to content
TRiLeZ

[Updated][Critical Announcement] Client Detection

Recommended Posts

Hello community,

 

Update: The detection patch has been released! TRiBot is once again safe to use, so feel free to continue botting.

 

After some investigation into the RS client, I have noticed a new piece of code in the RS client which could potentially flag users of 3rd party clients as botters. So I did some more investigation/testing and found that Jagex does use this piece of code to ban accounts. I am 100% confident that this new detection method has led to the increase in bans. Further, all botting clients which have not already patched this detection method are affected. So please be cautious when using other botting clients, because if they haven't patched this detection method, you will be banned.

 

But do not let this worry you about the future of botting. I am working diligently on a patch for this detection method, which should be released within the next few days.

 

I advise everyone to stop using non-LG TRiBot until I release the patch, unless you don't care about your account. Once again, I also advise everyone to be cautious when using other botting clients, for the reason stated above.

 

Due to the nature of Looking Glass (LG) and the nature of the detection, this detection method has limited to no effect on botters using LG. I haven't had any accounts get banned solely from using LG, but for the same reasons this detection method is capable of getting legit players banned, I am going to say that this detection method has a limited effect.

 

This isn't the only [possible] detection method in the client. I usually silently release a patch for detection methods so that it takes Jagex some time to release that we know of the detection method. But since I am 100% confident this detection method leads to bans, and that many people have been hit by this, I am writing this to inform everyone on the situation.

 

I'll keep everyone updated on the status of this patch.

 

Thanks,

TRiBot Staff

Edited by TRiLeZ
  • Like 38

Share this post


Link to post
Share on other sites

but for the same reasons this detection method is capable of getting legit players banned,

 

Yep, my legit main got banned yesterday. I have literally never botted on the account, but it shares the IP with my looking glass "main" which is completely botted. The LG acc has a 2-day ban. So yesterday, I saw that post about swiftkit being better than OSB, so I logged into the game through Swiftkit for the first time, and my legit account gets logged out and banned. Like what the fuck Jagex lmao

Edited by fatdoobie2

Share this post


Link to post
Share on other sites

JaGex won't usually ban you simply because you're using a TriBot client, but I'm sure they use the evidence as one more reason to ban you if you're already suspect.

From recent events, it's been shown that they'll ban you JUST for being on a botting client. As well, they have publicly said this.

 

 

 

Were back in business boys!!!!

 thanks to the man Trilez  ;)

 

Not yet.. the work around hasn't been implemented yet. Like TRiLeZ has stated, it's highly recommended not to bot using non-lg atm.

Edited by erickho123

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • This release will:

      Fix key event handling issue


      Fix other event handling issue


      Fix RSServer hook


      Update world hopper to have it use OCR, thanks to Todd


      Use proper disposal of old Graphics objects


      Reformat code


      Rearrange code


      Organize code imports


      Apply around 8000 automated code refactorings


      Make preparations for Java 9


      Fix 11 various bugs


      Add more reliable debugging support


      Fix mouseEntered/Exited event dispatching bug


      Fix minimap walking bug where it opens the map


      Fix broken hooks for today's game update
        • Thanks
        • Like
      • 40 replies
    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 27 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×