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 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
      • 34 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
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      Bug fix for intelligent banking


      Improvement to the stability of LG over time



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 10 replies
    • - Updated the banking API to use the game item cache instead of interfaces. This will result in less delay, greater efficiency, and greater reliability. LG will especially benefit from this update.
      - Fixed a bug with the Grand Exchange API relating to searching for items.
        • Like
      • 5 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×