Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
TRiLeZ

[Updated][Critical Announcement] Client Detection

Recommended Posts

Is there a link for LookingGlass so I can learn more about it? Also, is it safe to bot using just the client, or would you recommend using LG? I have a really nice pure (botted) that I want to continue to bot, but i really dont want him to get banned if i use the client rather than LG

Share this post


Link to post
Share on other sites

Is there a link for LookingGlass so I can learn more about it? Also, is it safe to bot using just the client, or would you recommend using LG? I have a really nice pure (botted) that I want to continue to bot, but i really dont want him to get banned if i use the client rather than LG

Looking Glass is for VIP-E users, I don't think you have access to much info about it until you become VIP-E but there is a forum dedicated to it. It is currently safe to bot with the client, but that doesn't mean it will always be safe. This was the first time they've added client detection in a long time according to TRiLeZ, and he says he will be checking thoroughly within 1-2 days of every update from now on and disabling the client temporarily if any flags are thrown.

Share this post


Link to post
Share on other sites

No, it's not detectable. You aren't even using the TRiBot client, so how would you get detected by it?

 

You are getting banned because of something you are doing, or something which you are failing to do.

 

@TRiLeZ u fuckin srs???

 

Im using LG and osbuddy. So yeah I am using the tribot client. I was using runemate but it was shit so I came here where every promised LG doesn't ban but ive only had one account survive so far. Seems anything over 10h is getting banned.

Share this post


Link to post
Share on other sites

@TRiLeZ u fuckin srs???

 

Im using LG and osbuddy. So yeah I am using the tribot client. I was using runemate but it was shit so I came here where every promised LG doesn't ban but ive only had one account survive so far. Seems anything over 10h is getting banned.

 

The client you use refers to the program you used to run RuneScape. In this case, you used OSBuddy to run RuneScape. You then used TRiBot to bot. All that I'm saying is that Jagex didn't detect you from how RuneScape was loaded. They caught you via behavior analysis.

 

By botting 10 hours, do you mean 10 hours straight?

Share this post


Link to post
Share on other sites

@TRiLeZ u fuckin srs???

 

Im using LG and osbuddy. So yeah I am using the tribot client. I was using runemate but it was shit so I came here where every promised LG doesn't ban but ive only had one account survive so far. Seems anything over 10h is getting banned.

 

you're not logging into RS from tribot, so it's not client detection, it's heuristics. Bot smarter.

Share this post


Link to post
Share on other sites

LG doesn't make you invincible. After about a week of monitoring my paid fletching bot 6-8hours a day, I received a 2 day ban on an account that I had created the week 07 came out. 

 

Let's be honest, you're never 100% safe and upgrading to LG is not going to prevent you from getting banned. Just keep that in mind before you guys start to bot longer periods of the day consistently as I did. 

 

Cheers and goodluck.

Share this post


Link to post
Share on other sites

LG doesn't make you invincible. After about a week of monitoring my paid fletching bot 6-8hours a day, I received a 2 day ban on an account that I had created the week 07 came out. 

 

Let's be honest, you're never 100% safe and upgrading to LG is not going to prevent you from getting banned. Just keep that in mind before you guys start to bot longer periods of the day consistently as I did. 

 

Cheers and goodluck.

 

Yes obviously you still need to bot smart, but with LG I'm able to get accounts over 1500 total level easily, just don't bot the same thing for more than a few hours at a time, always mix things up.

 

 

No idea if this has been asked already. If your account was "flagged" by being logged in to tribot, is there a chance it is still flagged? I know since the account isn't banned they probably have looked it over and it's most likely safe but I want a second opinion.

 

I'd guess they've put a note on your account

Share this post


Link to post
Share on other sites

Could you provide more details? I am assuming that something else must have gone wrong aside from them detecting you through looking glass. It seems like everyone who was using LG has been safe from client detection. Is it possible that you may have been flagged in the past month(s) and banned only recently? Is it also possible that a bad script (or any script running for too long) could have been behind this? 

 

That message doesn't mean they detected any clients, Jagex are able to catch botters from analyzing heuristics collected from all the hours you bot. They probably look at things such as time between clicks, areas of the screen clicked, reaction times, and if there is any kind of overall pattern to what they are doing which is too consistent for a human to maintain. Eg, if you run a script which takes 10 seconds to do X action and has 20% randomness built in, all you're doing is building a pattern where you take 8-12 seconds to do the action. A human could only keep this up for so long before they would inevitably take longer or less time to do the action - statistical outliers. Poor scripts will not produce these ever.

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 update features:

      Fixed broken hooks from today's update


      Fix wilderness level with RuneLite (Thanks @Todd)


      Add support for Kotlin .class files in scripts (Thanks @wastedbro)


      Overhaul Inventory API (Thanks @wastedbro)


      Add List support for common methods


      Change method grouping to make more sense (by functionality)


      Refactor methods to utilize Java 8 streams instead of cumbersome loops




      Recognize chatbox minimization (Thanks @JoeDezzy1)


      Fix Screen#isInViewport when NPC chat is open (Thanks @JoeDezzy1)


      Fix login bot bugs (Thanks @erickho123)


      Fix hint arrow return values (Thanks @Encoded)


      Fix depositAllExcept functionality (Thanks @wastedbro)


      Change containing box interface bound and adjust for Y values (Thanks @erickho123)
        • Like
      • 102 replies
    • 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.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 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.
        • Thanks
        • Like
      • 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
        • Like
      • 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
        • Like
      • 68 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...