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

Sell OSRS Gold
Sign in to follow this  
kikipaz

When playing legit, does the client matter

Recommended Posts

Hello everyone.

 

So I'm writing this because one of my mates told me, that if you're botting you should be using the bot client even when you're playing legit. Because they can detect if you like play legit everytime you on this client, and botting when you're on the other one.

 

Does anybody have a qualified answer on this? :)

 

- Love Kikipaz

Share this post


Link to post
Share on other sites

I use both bot client and browser with all my accounts. Of course all my accounts that bot constantly, eventually are banned.

In my opinion though the only thing that makes you a target is constant bot like clicking/walking patterns or if you play completely different from

the bot your legit pattern would be completely off to the bot play pattern. (I'm pretty sure this is more of an rs3 thing though.

 

I can't guarentee anything because I don't work with/for Jagex but it's more likely to me.

 

 

Edit:

 

I don't know about that but I was wondering if you can get banned for playing legit on a client just because you're on a botting client.

 

 

Client is not detectable

Edited by J M C

Share this post


Link to post
Share on other sites

No, they cannot detect external clients. It's somewhat simple to load RS on different programs such as Orion, Tribot, or any webbrowser you make yourself or isn't popular.

 

I've seen an official post from a Jagex mod that stated Jagex can't confirm certain clients or recommend any (because of the virus risk), however he said it's not against the rules. So even if they could detect your client, it would be impossible to tell the difference between a legit one and botting one.

Share this post


Link to post
Share on other sites
Guest

Jagex has no way of detecting what client you are using. You are still connecting using the same IP address which is all that matters.

Share this post


Link to post
Share on other sites

Some bot clients make injections therefore I'd definitely avoid using them to play legitimately on.

 

Besides, back in 2013 when they had the bog ban waves, I had several accounts banned within 5 mins of just logging into bot clients.

 

So in my opinion it would be foolish when it's feasible to use the official client.

Share this post


Link to post
Share on other sites

Some bot clients make injections therefore I'd definitely avoid using them to play legitimately on.

 

Besides, back in 2013 when they had the bog ban waves, I had several accounts banned within 5 mins of just logging into bot clients.

 

So in my opinion it would be foolish when it's feasible to use the official client.

 

 

TRiBot doesn't use injection.

Share this post


Link to post
Share on other sites

Tutorial island is able to detect tribot client now for some reason. I tried a bunch of clean IP's and legit/script. It seems to be undetectable outside of there.

 

Normally when people express theories or opinions, they say so. I suggest you do the same.

 

If scientists accepted theories as facts because of small correlations, then we would live in a seriously messed up world.

 

I think the client is not detectable, and even if it was, it wouldn't matter. I've stated the same thing above, with actual logical evidence.

Share this post


Link to post
Share on other sites

Normally when people express theories or opinions, they say so. I suggest you do the same.

 

If scientists accepted theories as facts because of small correlations, then we would live in a seriously messed up world.

 

I think the client is not detectable, and even if it was, it wouldn't matter. I've stated the same thing above, with actual logical evidence.

 

Only on tut island. Try it yourself if you don't believe it.  Scientific method is the best.

Share this post


Link to post
Share on other sites

Only on tut island. Try it yourself if you don't believe it.  Scientific method is the best.

 

That's fine. But have you ever thought that the script you use is detected? Maybe the system instantly bans anyone even remotely connected to a banned account (IP, hardware, password). Maybe the system is so harsh that legits can barely get by it.

 

You need to learn the difference between theories, correlations, evidence, and facts. I feel sorry for anyone going to you for support.

Share this post


Link to post
Share on other sites

That's fine. But have you ever thought that the script you use is detected? Maybe the system instantly bans anyone even remotely connected to a banned account (IP, hardware, password). Maybe the system is so harsh that legits can barely get by it.

 

You need to learn the difference between theories, correlations, evidence, and facts. I feel sorry for anyone going to you for support.

 

Obviously it's just my opinion.

 

I did use a network+computer not connected to botting to check, btw.

Share this post


Link to post
Share on other sites

Jagex apparently can detect client like things just created this acc to notify.

Created account in the morning, used epic of client for a few quests and basic starter things not even used a script for 30mins. Logged out 3hours later logged in and 0.1seconds after I logged in It kicked me off the server and I got banned. So it appears it just knew I was on the epic of client without looking to botting patterns or not.

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.

Sign in to follow this  

  • Similar Content

    • By DaFukWasDat
      I suspect Jagex is using a technique called browser fingerprinting, this means they can give your browser it's own fingerprint/ID even if you change proxies or delete your cookies they will still know it's you.
      Multiloginapp is free, however they offer a premium version which you don't need, basically it will create a new browser with it's own new fingerprint.
      This website will show you how easily you can be tracked: https://amiunique.org/fp
      Ever seen an ad follow you around the internet and wondered how they do it? Browser fingerprinting is your answer.
    • By IceKontroI
      Hello, everyone. Recently I've been interested in how Jagex's pattern detection works. I ran a simple easily detected script which opens the GE, buys 1 lobster at 100 GP, waits 30 seconds, then cancels the offer and closes the GE on a loop with tribot's AI antiban turned off. After a few minutes of runtime some abnormal things started happening. Most commonly my input to the game was blocked, meaning I could move my mouse around, but the game server never accepted my input, and as a result my account's actions had no effect on the game world. I've been able to semi-reliably recreate this scenario multiple times on different accounts and IP addresses. It's worth noting that players and NPCs continue their normal action while my account's been frozen, which also indicates no connection errors. The input blockage happens fairly often to the point that it's very unlikely it has anything to do with my network connection or Jagex servers. I believe this is Jagex's first line of defense against bots (or at least one of them).
      Real players will typically try to perform various actions in-game like arranging inventory, clicking on random tiles or objects, world hopping, and even restarting the client. Bots may repeatedly click the same action (big red flag) or do nothing (moderate red flag) I have no doubt that botters/scripters with more experience than me have noticed this, but this is not a thread about Jagex input blocking, it's about preventing it from happening through pattern breaking.
      Pattern breaking is centered around the imperfections and variability of the human mind and judgment. Regular player activity does form patterns to some degree, but typically it isn't as pronounced as those of bots. There are two categories of pattern breaking:
      Large scale More useful for public scripts or large farms Focuses on creating differences between accounts through account preference Different methods of performing tasks Different subsets of antibans per account Each account may be only able to use 7 out of 12 generic antibans available for the script This increases the longevity of the script by allowing less opportunities for Jagex to group accounts via similar actions Different frequencies of antibans per account Account A may perform one antiban more frequently than account B Changes in sleep and delay times per account Accounts all have different run times This is mainly for farm detection, not for public scripts Different accounts running the script in different worlds/locations if possible Unique break patterns per account Different muling cycles Small scale Focuses on preventing accounts from producing patterns through their actions Changes the order of sub-actions within a larger action when order does not matter More useful when incorporated as part of a complex script process Avoid hardcoding script processes as first A, then B, finally C Instead use fluid condition checks to see what action should be performed Then use account preference and probability to determine which of several actions it prefers over the others Action[] actions = getActions(situation); // This should perform action condition checks and return only relevant actions boolean performed = false; for (action : actions) { if (accountPrefers(action) && accountProbability(action)) { performed = performAction(action); if (performed) { break; } } } if (!performed) { performAction(action[General.random(0, action.length)]; } While this may seem excessive, this is how players decide what to do next in a sequence of events
      Antiban is a large part of pattern breaking Performing actions you don't usually do is an effective way to break patterns Misclicking can be seen as a form of antiban as it's infrequent but deviates from your normal activity Avoid randomization Randomizing everything from antibans to sub-actions within a larger action schedule may seem like an appealing idea While it's likely to work to some degree, it will make accounts on the large scale appear too similar to each other We're trying to get our accounts to operate in the grey area between a well defined pattern and no pattern at all If all accounts operate in this grey area their patterns will be loosely defined but dissimilar from each other The idea of pattern breaking shows promise, however it has many requirements. One of which is account preference which is something Tribot has some support for, but this support is limited. For example a scripter has no way of applying Tribot preference to custom made functions. The solution is to make your own preference system where the account's username and a seed value is used to derive a value from 0 to 100. Below is my own way of doing so:
      /** * Performs a probability check on the input value. Input a percentage (0 - 100). */ public boolean chance(double chance) { return General.random(0, 100) <= chance; } /** * Scales a value based on its original range so that its position in that range is in the same position in the new range. */ public double normalizeValue(double value, double oldMin, double oldMax, double newMin, double newMax) { double percentage = (value - oldMin) / (oldMax - oldMin); return newMin + percentage * (newMax - newMin); } /** * Generates a username based preference value for the given seed (0 - 100). */ public double preference(double seed) { try { String hash = Double.toString(Player.getRSPlayer().getName().hashCode() * Math.sqrt(seed)).replaceAll("[^\\d.]", "").replaceAll("\\.", ""); String int1 = Character.toString(hash.charAt(hash.length() - 1)); String int2 = Character.toString(hash.charAt(hash.length() - 2)); String int3 = Character.toString(hash.charAt(hash.length() - 3)); return normalizeValue(Double.parseDouble(int1 + int2 + "." + int3), 0, 99, 0, 100); } catch (NullPointerException e) {return 50.0;} } /** * Generates a username based preference value for the given seed, but normalized to match the provided range. */ public double preference(double seed, double min, double max) { return normalizeValue(preference(seed), 0, 100, min, max); } /** * Performs a probability check on a preference value normalized to match the given range. */ public boolean preferenceChance(double seed, double min, double max) { return chance(preference(seed, min, max)); } Hopefully I've included all the necessary functions for the above to work. If you for example wanted to test an account's preference for performing Action A over Action B, you could take the hashcode of each actions, remove all non-integer characters from each, input them into the functions above, and receive a preference for each. I recommend using custom ranges like preference(100, 15, 85), where 100 is the seed, 15 is the min chance, and 85 is the max chance. That way the preference range will always be within 15% and 85% and you won't ALWAYS or NEVER perform that action above other actions. It should also be mentioned that you shouldn't be using these preferences to determine which actions to do, only to determine which actions should be performed above other actions. All actions should be performed as long as they're part of your script.
      This post ended up being much longer than I originally wanted but it's good to get your thoughts out in writing so I'm glad I spent the time. Going forward I would appreciate a healthy discussion, please add to the thread with your comments rather than just taking up space with pointless nay saying.
  • Our picks

    • Hello everyone,

      Last week we tried to roll out Auth0 Login, but we lost that battle. Now it's time to win the war!

      Important changes

      When logging into the client, you'll now have to enter your Auth0 account credentials instead of your forums credentials

      Note: 2FA is still handled through your forums account (for the time being)



      Changes for existing users

      You'll have to link your Auth0 account to your forums account here: https://tribot.org/forums/settings/login/?service=11


      Auth0 accounts have been created for most existing users. Please use your forums email address and password to login.



      Important notes

      Make sure to verify your email address upon creating a new Auth0 account


      When we mention your Auth0 account, we mean your account used for auth.tribot.org as displayed below
      • 64 replies
    • To better support the upcoming changes (TRiBot X, new repository), we're switching our login handler to Auth0. Instead of logging in with the standard form, you'll now be required to login through our Auth0 application.

      All existing accounts which have been used within approximately the past year have been imported into Auth0 using the same email and password combination which has been stored on the forums.

      What does this mean for users?

      Your account credentials are now even more securely stored


      You'll be able to login via Facebook, Google, and others in the future


      Is there anything users have to do differently now?

      Existing users: You'll have to login with the standard login, open your Account Settings, then link your Auth0 account


      New users: You'll be redirected to our Auth0 app (auth.tribot.org) where you'll be able to create an account


      Why was this change made?

      The new apps we are creating (such as the new repository) aren't able to use the forums to handle user logins


      To centralize all user accounts in one area


      To ensure that the client login doesn't go down when the forums are having problems


      To speed up our development


      Other considerations

      There's no documentation or official support for using Invision Community combined with Auth0, so there are still a few kinks we're working out


      We're in the works of creating an account management panel specifically for Auth0 accounts (ETA August)


      It's not possible to change email addresses for the time being (this will be resolved this August)


      Changing passwords is a weird process for the time being. To change your password, you'll have to use the "Don't remember your password" tool on the Auth0 login page
        • Like
      • 11 replies
    • Over the past month, we've been working hard on TRiBot's new repository - a much needed update. This change has been deemed necessary for TRiBot X, and will allow us to really speed up development of all aspects of TRiBot.

      Today we are going to share what we've been working on!


      Now you must be wondering what kind of features the new repository will have.... well, you'll have to be patient for a little while longer. We're still figuring out various technical aspects so we can't provide answers to all possible questions. We're also focusing on development rather than writing about it so that everyone can get access to our latest developments at lightning speed. I will however answer a few users' questions.

      We're planning on a release of this early to mid August, giving users some goodies before TRiBot X's release.

      Thank you all for being patient. I hope everyone is excited as much as I am!
        • Like
      • 17 replies
    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 50 replies
    • Come give us feedback on the next version of TRiBot!
        • Thanks
        • Like
      • 86 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...