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

[Updated][Critical Announcement] Client Detection

Recommended Posts

Explain to me why I got banned for macroing.

I got banned after 15 minutes of gameplay,

made a fresh account, tutorial island by hand, I DIDN'T EVEN START A SCRIPT.

 

And no my ip is not flagged. Even if it was flagged explain to me why other legit account still alive...

Did you try setting your client to wumbo? helped me

Edited by PatricioP
  • Like 1

Share this post


Link to post
Share on other sites

@TRiLeZ I'm still only lasting a day with accounts. Im using LG osbuddy, making real acc with real emails. Doing tut island by hand only botting one or two hours and then leaving for a day or two. Changing my Ip after every 2nd account made. All banned. The client is still detectable

Edited by xicitx

Share this post


Link to post
Share on other sites

@TRiLeZ I'm still only lasting a day with accounts. Im using LG osbuddy, making real acc with real emails. Doing tut island by hand only botting one or two hours and then leaving for a day or two. Changing my Ip after every 2nd account made. All banned. The client is still detectable

 

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.

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.

Vouch, haven't had a single ban since the client was officially made undetectable again.

  • Like 1

Share this post


Link to post
Share on other sites

@TRiLeZ what's the probability off the client becoming detectable all over again and you taking three weeks to four weeks to notice? Do you update the client every thursday after an update to make sure nothing is detectable(how long should we wait before we make sure no new update made the client detectable, and give you enough tiime to check)? Is this the first time jagex does something to detect the client? 

Edited by Enano25

Share this post


Link to post
Share on other sites

@TRiLeZ what's the probability off the client becoming detectable all over again and you taking three weeks to four weeks to notice? Do you update the client every thursday after an update to make sure nothing is detectable(how long should we wait before we make sure no new update made the client detectable, and give you enough tiime to check)? Is this the first time jagex does something to detect the client? 

 

Let's say TRiLeZ's friend Jagex comes over to TRileZ's house to play hide-and-seek. As they first start playing, Jagex does a pretty good job of hiding; there are plenty of closets, cupboards, etc that Jagex can hide in. At the beginning TRiLeZ is having a pretty hard time finding Jagex, but as time goes on, he starts to get better.

 

Now let's fast-forward 5 years. All those really good hiding spots that Jagex came up with when they first started playing have been used, and TRileZ now not only knows about them, but has rigged them with motion sensors and other high-tech spy equipment! At this point, TRiLeZ is very confident that there is no way Jagex will be able to hide without him knowing about it instantly.

 

However, lately Jagex has been getting really frustrated with TRiLeZ. It's been almost 4 years since Jagex has hid from TRiLeZ successfully, and he's getting impatient. Hide-and-seek isn't even fun for Jagex anymore because TRileZ always finds him right away! Jagex thinks long and hard about how he could possibly hide without TRiLeZ finding him, but he can't think of anything. There are just no good spots left!

 

But then Jagex comes up with an idea: He stops trying to hide entirely, and instead disguises himself as one of TRiLeZ's family members. It works! Jagex's plan works! Jagex is able to walk right into TRiLeZ's house without him even realizing it. Jagex snickers and laughs as he stands right next to TRiLeZ for almost a month without being noticed.

 

However, in the end, TRiLeZ does find Jagex, and WOW is he angry! There is no way TRiLeZ is going to let Jagex do something like that EVER again!

/analogy

 

That incredibly cheesy analogy is designed to show you how Jagex's detection system works. Jagex can't just "detect the client" out of nowhere without TRiLeZ realizing it. They have to do something really sneaky and clever in order to detect the client, and even when they do, TRiLeZ can figure it out. And especially now that Jagex has done something sneaky like this, TRiLeZ is even more on the lookout for things like it.

 


 

tl;dr: The chances of the client being detected again is basically 0%.

Edited by TacoManStan
  • Like 2

Share this post


Link to post
Share on other sites

/analogy

 

That incredibly cheesy analogy is designed to show you how Jagex's detection system works. Jagex can't just "detect the client" out of nowhere without TRiLeZ realizing it. They have to do something really sneaky and clever in order to detect the client, and even when they do, TRiLeZ can figure it out. And especially now that Jagex has done something sneaky like this, TRiLeZ is even more on the lookout for things like it.

 


 

tl;dr: The chances of the client being detected again is basically 0%. 

 

 

After an update how long do you think we should give trilez to check the client so we can feel/be safe again, one to two days?

 

I guess it doesn't really matter, if jagex manages to become a table next then how will trilez find the table if he is looking for family members plus all the hiding spots off 5 years? He won't find the table till everyone is banned. or maybe he will if he looks hard enough at the furniture for 1 to two days?

 

Does trilez need a little bit off time to check after each update so that after each update he can declare the client safe, yes he has systems to detect any anormality but he can't detect jagex being a table.(just following ur analogy)

 

And yes now he is on the lookout for things like jagex hiding as tables even more, but that won't be immediate as you state, there has to be a time for trilez to check.

 

 

tl:dr: do you think waiting 1 to 2 days before botting on the client again after an update is necessary, or should you just start up immediatly after like 15 mins after an update?

 

how much time after an update does trilez need to check for client detection updates?

Edited by Enano25

Share this post


Link to post
Share on other sites

After an update how long do you think we should give trilez to check the client so we can feel/be safe again, one to two days?

 

I guess it doesn't really matter, if jagex manages to become a table next then how will trilez find the table if he is looking for family members plus all the hiding spots off 5 years? He won't find the table till everyone is banned. or maybe he will if he looks hard enough at the furniture for 1 to two days?

Jagex might be able to pass off as TRiLeZ's cousin, and Jagex might be able to hide under the table, but I'm fairly sure TRiLeZ would notice if Jagex tried to pretend to be a table.

 

Let me emphasize that the purpose of the analogy was to help people understand that it takes a lot of time and resources for Jagex to come up with a new way to hide new client detection code. They've tried it before, and TRiLeZ has caught it and silently updated the client in less than 24 hours. Most of the time that isn't even necessary because the system automatically catches and then patches it.

 

This isn't the first time Jagex has tried to detect the client, and it won't be their last. I place emphasis on the word try: it doesn't mean the client is going to be detected again any time soon, if ever. There's a reason this is the first time it has happened since the release of the client.

 

how much time after an update does trilez need to check for client detection updates?

I honestly don't know. I personally wait until I see TRiLeZ online for any length of time, or ~2 days, whichever comes first. This is almost certainly not necessary, but I do it because I don't want to risk it. @TRiLeZ might be able to shed some light on whether that is actually necessary or not (99% of RS updates don't contain any new detection attempts of any kind anyways).

Edited by TacoManStan

Share this post


Link to post
Share on other sites

 

After an update how long do you think we should give trilez to check the client so we can feel/be safe again, one to two days?

 

I guess it doesn't really matter, if jagex manages to become a table next then how will trilez find the table if he is looking for family members plus all the hiding spots off 5 years? He won't find the table till everyone is banned. or maybe he will if he looks hard enough at the furniture for 1 to two days?

 

Does trilez need a little bit off time to check after each update so that after each update he can declare the client safe, yes he has systems to detect any anormality but he can't detect jagex being a table.(just following ur analogy)

 

And yes now he is on the lookout for things like jagex hiding as tables even more, but that won't be immediate as you state, there has to be a time for trilez to check.

 

 

tl:dr: do you think waiting 1 to 2 days before botting on the client again after an update is necessary, or should you just start up immediatly after like 15 mins after an update?

 

how much time after an update does trilez need to check for client detection updates?

 

0 days, 0 seconds.

Share this post


Link to post
Share on other sites

Just got banned. Wasn't botting at the time, and I think it was because I logged on with the client earlier today (didn't use it though, switched to OSB right after). Seems like it's still detectable. They can just keep changing whatever code they use to see whether a third party client is being used or not. Fixing it one day wouldn't fix it forever, if I'm not misunderstanding.

Edited by buggylemon

Share this post


Link to post
Share on other sites

@buggylemon

Just got banned. Wasn't botting at the time, and I think it was because I logged on with the client earlier today (didn't use it though, switched to OSB right after). Seems like it's still detectable. They can just keep changing whatever code they use to see whether a third party client is being used or not. Fixing it one day wouldn't fix it forever, if I'm not misunderstanding.

You weren't banned because of the client. Delayed bans can take up to a month to take effect. You were banned because you botted.

  • Like 2

Share this post


Link to post
Share on other sites

 

After an update how long do you think we should give trilez to check the client so we can feel/be safe again, one to two days?

 

I guess it doesn't really matter, if jagex manages to become a table next then how will trilez find the table if he is looking for family members plus all the hiding spots off 5 years? He won't find the table till everyone is banned. or maybe he will if he looks hard enough at the furniture for 1 to two days?

 

Does trilez need a little bit off time to check after each update so that after each update he can declare the client safe, yes he has systems to detect any anormality but he can't detect jagex being a table.(just following ur analogy)

 

And yes now he is on the lookout for things like jagex hiding as tables even more, but that won't be immediate as you state, there has to be a time for trilez to check.

 

 

tl:dr: do you think waiting 1 to 2 days before botting on the client again after an update is necessary, or should you just start up immediatly after like 15 mins after an update?

 

how much time after an update does trilez need to check for client detection updates?

 

 

Client detection is a rare thing for Jagex to do, which is why it took me so long to notice it; I wasn't actively checking the client for it (excluding some automatic checks which are always performed). But now I'm actively checking the client every release for new detection code. I can scan the client for detection code very quickly, so if I don't make any comments within 24-48 hours after a client update, you can assume it's safe. And if new client detection becomes a regular thing, I'll make it so TRiBot won't load RuneScape after client updates until after I've manually scanned the client for detection code.

 

I won't let Jagex get away with client detection. I'll make sure your accounts don't get banned because of it.

  • Like 1

Share this post


Link to post
Share on other sites

Client detection is a rare thing for Jagex to do, which is why it took me so long to notice it; I wasn't actively checking the client for it (excluding some automatic checks which are always performed). But now I'm actively checking the client every release for new detection code. I can scan the client for detection code very quickly, so if I don't make any comments within 24-48 hours after a client update, you can assume it's safe. And if new client detection becomes a regular thing, I'll make it so TRiBot won't load RuneScape after client updates until after I've manually scanned the client for detection code.

 

I won't let Jagex get away with client detection. I'll make sure your accounts don't get banned because of it.

Good news all around.

 

I can assure everyone that the client is not detectable it's not just propaganda unlike competitors may have tried to convince you. I called it out the first time we were told it was safe and it wasn't, but ever since Trilez did the second update its been 100% undetectable.

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 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
      • 50 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
        • thonking
      • 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
      • 21 replies
    • This release will:

      Add LG support for Runelite


      Fix NPCChat issues


      Fix a bug where the camera angle setter would just hold down a key for 5 seconds (the timeout)


      Slightly adjust the rotation via keys to be more accurate


      Add the ability for asynchronous camera movement via keys


      Make Camera rotation via mouse more fluid, with more antiban, and work much better in resizable mode


      Add a "Camera#setCamera" method, allowing the rotation and angle to be set in parallel


      Increase the likelihood of using the mouse for camera movements


      Add support for adjusting the camera to positionable entities (Positionable#adjustCameraTo)



      Upcoming updates:

      Improved CLI support


      Much more



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

    No registered users viewing this page.

×