Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
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

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.


  • Similar Content

    • By undertheradar
      I want to buy two bonds for 2 of my botting accounts. I have around 6 new accounts that have all done some killing of chickens.
      I understand that I can accept traded items/gold on Fresh account A but I then cannot transfer it off the account to anyone because I do not have 18 hours in game or 7 Quest Points?
      So my plan is to buy 6mil with real money on Fresh account A and then give 3mil each to Fresh account B and Fresh account C, so they can buy bonds at the GE.
      Will I be able to trade the 3 mil from Fresh account A to Fresh account B and Fresh account C? 
       
    • By exitpoint
      I have 2 $25 prepaid cards for sell, osrs gp or paypal accepted.  add my skype, alex234323
       
       


    • By rsproject
      I'm going to buy a bond on my new main that I'm botting on. I bot using a proxy, so if I buy bonds of jadex do I need to use the same ip to buy the bond or do they not monitor that?
  • 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
      • 59 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)


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

    No registered users viewing this page.

×
×
  • Create New...