Jump to content
darkblades

When to Bond your new Bots

Recommended Posts

So I'm coming back to botting after a year or so Hiatus. I'm curious... from experienced botters, when do you feel it safe to bond your new bots that you are implementing into your farm? I understand that bans are inevitable, but I'm going for longevity of my accounts rather than 24/7 suicides. Should I hand play them for a bit, quest and spread some skills around prior to bonding them and moving to money making skills? How have you guys found success?

  • Like 1

Share this post


Link to post
Share on other sites

I'm new to the botting scene, but I have found some success after several weeks of experimenting with long-term botting accounts. If you are using proxies that are flagged, make sure to level up combat stats and a variety of other stats (mining/fishing/woodcutting/some quests). I  botted the combat stats and the quests to get above 20 combat and 7 quest points.  For the first week of each account, I heavily use breaks and limit my playtime to very few hours a day. After creating an account with a good baseline set of stats, I feel much safer against bans. Of the accounts that I have leveled up this way on flagged proxies, one out of four have been banned compared to 9/10 being banned before leveling a variety of stats.

 

I hope others in the community will give their perspectives since I am still very new to botting.

Edited by fenkiluno
  • Like 1

Share this post


Link to post
Share on other sites

I made two cannon ball bots. The first account was gonna be a barrows bot, but I wasn't bothered questing that much on it. I botted 40+ range and 70+ magic on it before I quit trying to finish it. I let that account rest for like a week and then I played on it myself for a bit, did Knights Sword and some other f2p quests. I got 35 smithing on it and then waited again. While I was waiting I made another account which I hand played untill I was 35 smithing and like 16 combat. I waited till Thursday before bonding them since I've heard that Jagex don't work on Fridays. During the weekend I made back what the bonds cost and they the bots still haven't been banned as of yet (I run still run them 7-8 hours a day). I also had an account that I handplayed till 75 WC. I've currently botted 14m+ xp on it without using LG and using a free WC script. I think that hand playing them at first plays a huge role in reducing bans.

  • Like 2

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

  • Our picks

    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
        • Thanks
        • Like
      • 22 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
        • Thanks
        • Like
      • 30 replies
    • This release includes:

      More 3rd party libraries for script writers to use


      Apache Commons Codec


      Apache Commons Collections


      Apache Commons Configuration


      Apache Commons IO


      Apache Commons Lang


      Apache Commons Math


      GSON


      Guava


      JFoenix




      Hint arrow API


      Game#getHintArrowX


      Game#getHintArrowY




      Fix player hooks including Player#getSkullIcon and Prayer#getPrayerIcon
        • Thanks
        • Like
      • 49 replies
    • This update includes:

      Fix broken hooks


      Fix login bot for the message "No reply from login server. Please wait 1 minute and try again."


      Fix bug relating to which bot tab is sent human input


      General#randomLong bug fix involving negative numbers


      Fix GE API



      Please note: There are still some issues with the login bot due to a change in the game mechanisms handling the login screen. We're working on a fix and will upload it when ready.
        • Thanks
        • Like
      • 37 replies
    • This release will:

      Fix key event handling issue


      Fix other event handling issue


      Fix RSServer hook


      Update world hopper to have it use OCR, thanks to Todd


      Use proper disposal of old Graphics objects


      Reformat code


      Rearrange code


      Organize code imports


      Apply around 8000 automated code refactorings


      Make preparations for Java 9


      Fix 11 various bugs


      Add more reliable debugging support


      Fix mouseEntered/Exited event dispatching bug


      Fix minimap walking bug where it opens the map


      Fix broken hooks for today's game update
        • Thanks
        • Like
      • 100 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×