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

Something definitive regarding multiple accounts on 1 IP

Recommended Posts

I've wanted to run several accounts on one IP for obvious reasons but I also haven't for obvious reasons. But does anyone have confidence that running multiple accounts on IP at the same time doing the same thing won't lead to more bans (up to a point). If not or if so, give me some of your anecdotal experiences with it.

Share this post


Link to post
Share on other sites

The theory is running accounts on different IPs reduces the amount of chain bans. Chain bans is the idea of if one account is caught, all the others botting at the time on that associated IP will also be banned. This has been twisted throughout the years and many people will claim if you get banned on an IP, that IP is now flagged and you have a higher chance of being banned if you continue to bot on that IP. In my experience and many others, this is not true. 


With that being said, I have ran multiple accounts on the same IP and had only one of them banned and not all of them chain banned so it pretty much comes down to your own experiences and what you think is truth or not.

Edited by Encoded

Share this post


Link to post
Share on other sites
29 minutes ago, Encoded said:

The theory is running accounts on different IPs reduces the amount of chain bans. Chain bans is the idea of if one account is caught, all the others botting at the time on that associated IP will also be banned. This has been twisted throughout the years and many people will claim if you get banned on an IP, that IP is now flagged and you have a higher chance of being banned if you continue to bot on that IP. In my experience and many others, this is not true. 


With that being said, I have ran multiple accounts on the same IP and had only one of them banned and not all of them chain banned so it pretty much comes down to your own experiences and what you think is truth or not.

I've encountered that too, had 4 accounts on the one computer and only one got banned.

Share this post


Link to post
Share on other sites
20 minutes ago, boatsb4hose said:

does anyone have confidence that running multiple accounts on IP at the same time doing the same thing won't lead to more bans (up to a point)

The more accounts that connect from the same address, the higher the probability that the said network is used to run a bot farm. We cannot know for sure which factors are taken into account for identifying bots, but it's safe to assume that the number of accounts per address is definitely one of them. It's the easiest thing to track (besides the average time spent in game), and it could also provide useful insight because after a certain number (i.e. 50), it becomes painfully obvious that you are running a bot farm.

That doesn't mean that you will get banned solely for this, but every additional account that you run from the same address is taking you further and further away from the average legitimate RuneScape player that only runs 1 account for no more than 2 hours every day.

 

Share this post


Link to post
Share on other sites

Knowledge about account suspension procedures is an internal Jagex secret, nobody here will give you a conclusive answer. All we can do is speculate and run empirical tests.

In my experience, there are multiple simultaneous factors that go into increasing account ban risk. While accounts probably don't get banned solely on IP blackmark, it does increase the likelihood of chain bans. As most people have experienced, bans don't always get chained, but they do happen more often on one-IP farms, especially if that IP is hosted in a datacenter.

Share this post


Link to post
Share on other sites

If you have multiple potentially sick people (bots that could possibly get banned) in the same room (IP address), the possibility of an outbreak (chain ban) increases as you add more people. Splitting the people into different rooms (using multiple IP addresses) reduces the risk of an outbreak as the number of rooms increases, until there's no risk of outbreak at 1 person per room.

@boatsb4hose

Edited by IceKontroI

Share this post


Link to post
Share on other sites
8 hours ago, IceKontroI said:

If you have multiple potentially sick people (bots that could possibly get banned) in the same room (IP address), the possibility of an outbreak (chain ban) increases as you add more people. Splitting the people into different rooms (using multiple IP addresses) reduces the risk of an outbreak as the number of rooms increases, until there's no risk of outbreak at 1 person per room.

@boatsb4hose

Very colorful analogy, but it works in this case.

How's the weed? :)

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

    • Today marks a big day for TRiBot! To make it easier for users to use TRiBot, we've created installers available for every platform! These installers are all bundled with the latest version of OpenJDK 1.8 (Java 😎, which is LG compatible.

      Using TRiBot is now easy. Simply download the installer for your platform, install TRiBot, and run it. The TRiBot Loader will correctly identify the bundled JDK so there's no need to change the Java selection.

      Windows

      EXE installer: TRiBot-windows-x64-4.0.3.exe


      MSI installer: TRiBot-windows-x64-4.0.3.msi


      Portable version: TRiBot-windows-x64-4.0.3.zip


      Mac OS

      Installer: TRiBot-macos-4.0.3.dmg


      Portable version: TRiBot-macos-4.0.3.tgz


      Unix/Linux

      Installer: TRiBot-unix-4.0.3.sh


      RPM installer (CentOS/Fedora): TRiBot-linux-4.0.3.rpm


      DEB installer (Debian): TRiBot-linux-4.0.3.deb


      Portable version: TRiBot-unix-4.0.3.tar.gz


      Platform Independent

      JAR file: tribot-loader-4.0.3.jar


      Note that this jar file does not include the bundled JDK.



      Windows and Mac OS users may notice a warning message stating that the installer/application is un-recognized or un-trusted. Please ignore this message and proceed with running the installer/application. We need to acquire a code signing certificate so that we can sign the installers letting the operating system know that these files can be trusted. It will take a week or more to acquire one, so please hold tight.

      Other notable changes to the TRiBot Loader:

      Support getting the version from OpenJDK distributions


      Add check for bundled JDK


      Copy OpenJDK tools.jar to the bundled JDK if not present


      Set the current java as the first available list entry


      Ignore Java versions which are symbolic links


      Make the bundled JDK the preferred Java version


      Update icon images


      Reduce the number of HTTP calls
        • Like
      • 11 replies
    • TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.

      Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.

      So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).

      Love, 

      RileyZ
        • Like
      • 7 replies
    • Hello TRiBot,

      Today we have a significant release that has been in the works for the last month addressing several key issues, features and bugs in the backlog.

      With these changes, we are also including a new TRiBot Loader which will allow you to select any version that is released. This adds the flexibility of allowing you to revert to a previous version should an issue arise, run development only builds, view an accurate change log between versions etc. we are very proud to offer this feature and think it will add a lot more functionality down the road as we continue to release new versions.

      These changes include 80+ commits by our development team, a list of them is summarized below and also available for your viewing pleasure in the new TRiBot Loader.

      In addition, we have taken additional steps to improve as a development team by adding continuous integration and deployment into our workflow to assist in delivering timely releases such as bug fixes as well as new features on a weekly basis depending on our development cycle.
        • Thanks
        • Like
      • 39 replies
    • Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!

      Why?

      Increased reliability - less server errors


      Increased availability - less downtime


      Increased security - keeping us and you secure


      Increased capacity - ability to serve you better


      Increased speed - less waiting for things to load


      Faster development - server and service updates will come faster


      What are the changes?

      Move from a single AWS EC2 instance to AWS ECS (Elastic Container Service)


      Distributed computing


      Load balancing


      Git management of server files and filesystem


      Redis caching


      How?

      AWS ECS (with 10 EC2 instances)


      AWS ElastiCache (Redis)


      AWS Load Balancing


      AWS EFS (Elastic file system)


      Please bare with us as I continue to tune the server for maximum performance. Slow loading speeds may occur temporarily. I thank everyone for their patience.

      Please post on this thread if you experience any issues other than slow loading times.
        • Like
      • 51 replies
    • 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
      • 151 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...