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

Bot Smart - What it is, and how to do it.

Recommended Posts

Around the forums you may see the phrase "bot smart," this is a guide with various steps for you to follow while botting to reduce the chances of a ban. It should be said, botting is against the rules and by doing so there will always be a risk involved.

These tips are not intended to be used with goldfarming setups or accounts, most of this is speculation based on my own personal testing and data gathering.


Botting Rules (If you intend to bot smart)

You must follow these steps, else you will not bot smart.

  1. Do not bot on an account you can not stand to lose. Botting is inherently risky and a ban is always going to be possible. You must decide whether what you stand to gain from botting is worth the risk. Only you can make this decision.
  2. Do not bot on fresh accounts. A fresh account refers to any newly registered account, or any old account which has not been played regularly in recent times. Fresh accounts are watched much more closely, likely as they pose more of a risk to the economy as they are used for gold farming a lot. Hand train the first 300~ levels and do some quests!
  3. Botting should supplement your game play. Botting is no longer supposed to get you from 1-99 Agility, running a bot this long will just about guarantee a ban. You must switch up what and where you are botting and don't bot the same skill for multiple hours.
  4. You should play legit, its easier to determine a human than a bot. As supplementary info to the above: you should play legit, Jagex knows when accounts are 90%+ botted and will permaban these accounts without a warning ban, if you play legit some then often your bans will only be 48 hour temp bans. Like I said why are you playing RuneScape if you're not here to actually play it?
  5. Understand the ban routine, and what it really means. When your account gets banned, it does not mean you just got caught and banned. It really means they caught you at some point, likely within the past 7 days, and waited some time to collect more data (such as how your character acts) which could help them detect other bots in the future. Do not bot on an account coming off a temporary ban or it will be permanent next time.
  6. Join in on chats going on around you. If you're at your PC while botting (maybe you're doing some work) then you can participate in clan discussions, and respond to people ingame. An account that randomly talks whilst botting is still less likely to get permabanned than if you never interact at all. Also enable Auto-Responder in TRiBot settings and it will respond to level inquiries, etc.
  7. Don't always pick the optimal spots. Are you woodcutting? Perhaps doing it at Draynor village with 20 other people isn't the best place. Assuming 15 of those other people are bots, the 5 legitimate people will get very annoyed and report all of you for slowing their XP down. You should pick a spot where your XP might be slower, or the bank might be a little further, but you have less people around to worry about.
  8. Do not use RSBot/Epicbot ever! Jacmob and Mod MMG specifically stated that their botwatch system is specifically tailored to RSBot and Epicbot which are both based on old RSBot 4 code, most of their interactions or hooks are outdated and they don't have any active API work being done. In short: it is much more easy to get caught botting using RSBot and Epicbot.



Miscellaneous Rules

Here are some further tips:

  1. Never post your RSN on a botting website. Jagex Staff and Player Mods will frequent these boards and have been known to ban people if they have sufficient proof.
  2. If you've just had a 2 day ban, the next one will be permanent. AND your account will be watched closer. You should not continue botting this account.
  3. If you're botting on a VPS you should use a VPN. No one is playing on a VPS legitimately, and it's not hard to figure this out from the IP alone. Providing you're not on a Windows VPS your operating system should not be too much of a giveaway. However, the fact you're playing on a machine without a monitor attached is probably not hard for them to notice either.
  4. Do not click Runescape links on forums. When you click a link it will send data of the page you came from, also known as tracker cookies.


Banned? Clean yourself off

Got banned? Clean yourself off before you continue. What we mean by this is, you need to wipe down anything that Jagex may use to associate your new account with your previous one. However, this is speculation and may not help.

  • Clear your Jagex Cache ( support.runescape.com/hc/en-gb/articles/205842582-How-to-clear-your-RuneScape-Cache-on-a-Windows-PC )
  • You can clear browser cookies and attempt to acquire a new IP address but these likely won't help unless goldfarming.
Edited by Led Zeppelin
updated highlight to make it easier to read
  • Like 3
  • Haha 2

Share this post

Link to post
Share on other sites

Nice of you to post such a detailed post.

In my experience it's all to do with RNG, some would say your tribot account.

Been banned on the same IP and the next day i carry on botting my max mains.

Just don't send pictures with your stats indicating you bot, most likely there are some Jagex mods patroling the forums/Discord.

Then again, my tin-foil had does have a hole in it.

  • Like 1

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.

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

    • 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
      • 150 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)

      Improve banking API (Thanks @Encoded)

      Adds methods for returning and using Java Lists, rather than arrays

      Slightly randomizes some hardcoded behaviour

      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable

      Other back-end improvements

      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 replies
    • 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
      • 28 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)




      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
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...