Jump to content

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

      Fix updater bug which was causing a bunch of issues

      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects

      Hooked login fields

      Improved the login bot

      Ability to recognize the banned/locked messages again

      Ability to read the current input for username and password fields

      If the username or password is already entered correctly, it won't be erased

      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.

      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.

      Coming soon:

      Skull icon fix

      Improve screen rate and responsiveness of the RS client (both regular client and LG)

      Much more
        • Thanks
        • Like
      • 25 replies
    • 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.
        • Thanks
        • Like
      • 25 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
        • Like
      • 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




      Hint arrow API



      Fix player hooks including Player#getSkullIcon and Prayer#getPrayerIcon
        • Thanks
        • Like
      • 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.
        • Thanks
        • Like
      • 37 replies
  • Recently Browsing   0 members

    No registered users viewing this page.