Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
      • 76 replies
    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
      • 28 replies
    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
      • 64 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 68 replies
    • This release will:

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 34 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...