Jump to content
TRiLeZ

[Updated][Critical Announcement] Client Detection

Recommended Posts

@TRiLeZ since when is the client detectable? possible that it is over a month already?

All started on 18 november, I got 16 accs banned using regular client, 19 november 45 new accounts banned, than I 20 novemeber 40 new accounts banned all using regular client, since that I am using looking glass and no bans.

Share this post


Link to post
Share on other sites

Why is tribot being targetted? This issue only seems to only be effecting us rather than botters as a whole.

 

I suppose if you want to make a statement you go after the client that prides itself on being the most undetectable one. If RuneMate's statement is anything to go by it's possible they were aware of this specific piece of detection code before TRiLeZ was.

Share this post


Link to post
Share on other sites

Has it been determined whether our client information is logged to Jagex and they go through and investigate the account then ban it?

 

Or does it need to be manually looked into?

There is no way of knowing.

 

Why is tribot being targetted? This issue only seems to only be effecting us rather than botters as a whole.

All botters are affected; not just ones using TRiBot.

Share this post


Link to post
Share on other sites

Thanks for the annoncement, i assumed as much. I ran a little experiement myself in the past, 2 accounts botting fishing, in barb village. both same levels, leveled together at the exact same time.

I used Looking glass on one, and just the normal client on the other.

 

And the account i wasn't using LG with got banned.

The other is untouched, non-member too.

 

Both at the exact same time, in the same world.

Edited by rek

Share this post


Link to post
Share on other sites

Up until this detection method, there was no evidence of Looking Glass doing anything to prevent bans, as stated by Trilez many times since its release. 

I agree, I have been absolutely fine without LG for a very long time. Only recently have I been forced to start using it, and since then my banrates are back to normal. Ofc I lost a couple of mules first... but that's how it goes!

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 includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
      • 22 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
        • Thanks
      • 30 replies
    • This release includes:

      More 3rd party libraries for script writers to use


      Apache Commons Codec


      Apache Commons Collections


      Apache Commons Configuration


      Apache Commons IO


      Apache Commons Lang


      Apache Commons Math


      GSON


      Guava


      JFoenix




      Hint arrow API


      Game#getHintArrowX


      Game#getHintArrowY




      Fix player hooks including Player#getSkullIcon and Prayer#getPrayerIcon
      • 49 replies
    • This update includes:

      Fix broken hooks


      Fix login bot for the message "No reply from login server. Please wait 1 minute and try again."


      Fix bug relating to which bot tab is sent human input


      General#randomLong bug fix involving negative numbers


      Fix GE API



      Please note: There are still some issues with the login bot due to a change in the game mechanisms handling the login screen. We're working on a fix and will upload it when ready.
      • 37 replies
    • 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
      • 100 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×