Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
TetanicBoot

Does jagex track IP or account for hours/day?

Recommended Posts

Title may be a bit confusing so allow me to explain. I like to bot somewhat safely so I only bot 2-4 hours a day, with breaks every hour or so. My question is, if I ran the bot on a  different account on the same IP for another 2-4 hours later that day, would that appear sketchy to jagex? Pretty much, when it comes to play time, are they watching IP or accounts?

Share this post


Link to post
Share on other sites

We don't know what they track specifically when determining how to ban bots however playtime is definitely a strong indicator. Data has shown the more hours/day you bot the more likely you are to be banned. However there are some exceptions and sometimes you can get away with 24/7 no breaks for a while.

Share this post


Link to post
Share on other sites
1 hour ago, godspower33 said:

We don't know what they track specifically when determining how to ban bots however playtime is definitely a strong indicator. Data has shown the more hours/day you bot the more likely you are to be banned. However there are some exceptions and sometimes you can get away with 24/7 no breaks for a while.

Does separating how much you bot into two separate accounts make any difference? Say instead of botting 6 hours a day on one account I bot 3 hours on two separate accounts but not at the same time?

Share this post


Link to post
Share on other sites
55 minutes ago, TetanicBoot said:

Does separating how much you bot into two separate accounts make any difference? Say instead of botting 6 hours a day on one account I bot 3 hours on two separate accounts but not at the same time?

Just bot both of them for 6 hours each :)

Share this post


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

Title may be a bit confusing so allow me to explain. I like to bot somewhat safely so I only bot 2-4 hours a day, with breaks every hour or so. My question is, if I ran the bot on a  different account on the same IP for another 2-4 hours later that day, would that appear sketchy to jagex? Pretty much, when it comes to play time, are they watching IP or accounts?

Botting safely doesn't exist, every time you run a bot you risk your account. Don't bot on accounts you care about.

Running two bots on one IP and PC increases the risk of them getting linked and chain banned at the same time. That is, if botwatch flags one account, chances are both will be banned.

Share this post


Link to post
Share on other sites

Honestly in my experience you only get banned when you get reported as of recently having the client undetected. Jagex only have so may employees and god knows they dont have the time to run around tracking single accounts etc. They just hit you with the ban hammer and move on. I realised this when I was botting 2 accounts overnight one time using the same script on both accounts. One for whatever reason got stuck, reported & banned and the other was completely fine. I sat there thinking why the hell didnt anyone do an IP lookup on their database or anything at all..?
You see on the bot busting streams jagex do, people hit with billions of gp and there just like "oh haha" and move on the thousands of other accounts.

This is just my experience tho. I have definitely heard of chain flagging IP's etc

Edited by dezina

Share this post


Link to post
Share on other sites

Breaks or time botted is irrelevant in the automatic detection system, the only time that playtime becomes a variable is when you're talking bot busting, not macroing major/minor. A bot busting ban is from a manual account review, which either way imo you're fucked if you botted and manual reviewed. Bot 24/7 or don't bot at all that's my motto. If you look at my post history, my botting methods currently have me an account with 100m xp total botted and around 5 99's all 24/7 botted. If you need some simple tips ama

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
Sign in to follow this  

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


      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
        • 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.

×