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

TRiBot Botting Guidelines

Recommended Posts

In this thread, we're going to aim at discussing some of the known techniques and practices towards safe botting. While it is impossible to prevent a ban, you can use some of these suggestions towards your botting to help mitigate risks towards your account. Most of this is all well known, we just wanted to organize these tips into a thread to help get you in the mindset of how to practice safer botting.


Your goal should be to emulate a normal player in game, we can do this through several ways but these three are the major ones that you as the player have an impact over.

1.   Session length   -   Thinking like a normal player, you should set up your bot for average lengths 1-3 hour sessions with breaks built in. And while a normal player could play for longer than that, just realize if you choose to bot for a 8 hour session you're adding more exposure to your account in game which could result in getting caught. A safe practice would be to set a total time you would expect to play during the week, and divide your sessions up so your total game time does not exceed that value. (i.e. 30 hours in a week, split across five 6 hour sessions +/- 2 hours)


2.   Location changing   -   Your goal should be to minimize your account's exposure in game and location changing can really help you with that. If the Script supports other locations, consider moving your account to another location for less exposure. If other locations are not possible, consider changing up your botting pattern by switching to another Script that performs in a separate location.


3.   World Hopping   -   Changing worlds is a great way to limit your exposure to other players, and continue performing the same task without changing locations in game. A player who sees you at the same spot, performing the same task, for several hours at a time will become suspicious and likely report you. Keep this in mind when botting.


4.   Activity   -   The activity you perform in game can also highlight you as a bot. If you only chop trees and your account's stats reflect that, a player directly competing with you for those trees will grow suspicious of your behavior and will likely result in getting reported. If possible, try to switch up the activities you perform on your account so that you are exposed for a less amount of time at each activity.




As for the obvious, the script should also be considered as that impacts your player in game.

1.   When botting it is important to recognize what task your player is performing in game. For example, if you are executing a Script that collects items that are in direct competition of other players in game; you can expect to bring more attention and potential player reports than if you were doing an activity that kept your player to itself. This is important to consider as this may play a bigger factor and stress the importance of the Overview and Other Factors listed above.


2. While it is the author's goal to create a Script that executes the task efficiently in game, sometimes performance can become a bigger focus than safe practice. If that is the case, it is important to bring this to the attention of the author to have the Script perform the task as a player would. This applies to the Developers as much as it applies to the user.



Other Factors
Some other things to consider are what a normal player's account looks like compared to the average botter.


1.   Appearance   -   Your appearance in game, should reflect other players who are performing the same task. The bots that stand out are regularly targeted during bot busting events and should be considered at all times.


2.   Combat level & overall stats   -   Your combat level can also highlight you as a bot or not. A level 3 chopping yews is commonly picked off as a bot and will be targeted during bot-busting events. If you are looking at increasing your accounts longevity, put in the work by leveling your account's combat level up to a respectable level based on the activity your player is performing to help blend into the crowd.


3.   Name   -   Your name in game should be chosen to reflect a normal player. While it is common to name your bot farms in sequential order (i.e. yewchopper1, yewchopper2, etc.) your account unfortunately will stand out among other players and a quick highscores search will result in another player confirming that you are a bot. Try selecting a normal name that does not relate to your other accounts.


4.   Conversation in game   -   For those concerned about your account, popping in and engaging in small chat every once and a while could prove your legitimacy if other players are conversing. TRiBot's built-in autoresponder (default: OFF) can be turned on to help with this, or you can manually talk in game once and a while which may help your player.



In the end, it all boils down to player reports and your account's activity in game. If you can reduce player reports on your character through these safe botting techniques and change up your activities in game regularly, you stand to better protect your account overall in the long run.
*If you'd like to suggest an addition to this thread, please post it below and it may be added.
TRiBot Staff

  • Like 9

Share this post

Link to post
Share on other sites

You hit the nail right on the head! I've always suggested these tips to the people that say botting is gonna get you banned. But if you do exactly what your guideline says you have a wayyyy less chance of getting banned. But then again a lot of people think they can just setup a bot and it's gonna do all the work for them. Can't just setup a bot, gotta be smart about it too.

  • Like 1

Share this post

Link to post
Share on other sites

Tribot isn't working... I can't find an exe ANYWHERE in the DL files. i can't open it. I can't get to the loggin screen. Can somebody Tell me WTF to do. I would have made a different post but i don't have access to post making on the forums i made an account for >.> WTF

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

    No registered users viewing this page.

  • Create New...