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

[Updated][Critical Announcement] Client Detection

Recommended Posts

i dont undrstand what trillez means can someone explain? is it safe to bot mining? haha

Botting without looking glass is like botting with jagex knowing your using tribots client. We are waiting for a patch that hides the fact that we are using tribot. LG-Looking glass is basically a client inside a client but the main client is Runescape web browser. So when they look to see which browser we are playing on it will always be runescapes so you can bot on lG now. but currently jagex can determine if we are using tribots client until Trilez updates. then we can bot without looking glass and jagex cannot immediately determine what client we are using. Currently if we use tribots client without LG its kinda like going to lava dragons lol 

Share this post

Link to post
Share on other sites

I got permanently banned on my main account that I haven't botted on just because I logged on it with the client to trade coins to my other account.. Client detection confirmed. It doesn't feel fair, I haven't even got any experience or money since over a year ago.. Do you think Looking Glass will eliminate their client detection?

Share this post

Link to post
Share on other sites

My 2 cents worth of input:


I botted yesterday after the update and the accounts I botted on are still alive. That leads me to believe that Weath or someone else needs to manually approve the bans. Either my accounts are queued for inspection or they will not be inspected at all beacuse nobody did that while they were logged in.

Share this post

Link to post
Share on other sites

For the people who don't believe or want "evidence" as mentioned before.

All my accounts I made & used on tribot without LG got instantly banned, even fresh new accounts made on new proxies etc. It's client detection guaranteed.

Buddy of my who RWT's got disabled with ~$900 worth due to using tribot, all his RWT accs got banned. So there is no denying that there isn't client detection, it's there atm.

Looking Glass should do the trick for now. For people asking questions: Looking Glass allows you to run osbuddy or the osclient via Tribot (so you can use a proxy or script forinstance with the original client or osbuddy).


@TRiLeZ Will it be possible in the future to bot again without Looking Glass? 


Thanks for doing the work Trilez much <3


- iWnB

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:

      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
      • 19 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)




      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
    • 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
        • Like
      • 34 replies
    • This release will:

      Fix an issue where breaks would stop firing

      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls

      Fix an NPE in the Combat API

      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
        • Like
      • 21 replies
  • Recently Browsing   0 members

    No registered users viewing this page.