Jump to content
Sign in to follow this  
ligriV

Chain ban

Recommended Posts

Hey everyone, I am interested in setting up a bot farm in the near future. I have some older experiences with botting and am looking forward to the trial and error of getting it to work.

While I am fixing things out, figuring out what works and for how long... I am trying to avoid a chain ban. I have a main account that I've never botted on before and I don't want to risk losing it. What steps should I take to protect it from the work I plan on doing.

Thanks everyone.

Share this post


Link to post
Share on other sites

well, idk..ppl are more scared then they should.

You wount get banned if you don't bot. Now, if you run massive f2p suicide farm on same IP you are playing with your main, then it can be GG to your main at some point. 

If you bot here and there on few acc's and play your main, no one will ban your main.

If you want to bot on one a and at a same time play with main - use proxy for that acc.

If you want to bot 3 acc's on PC = use proxifier with OSBUDDY and play on that osbuddy with main.

 

Share this post


Link to post
Share on other sites
Posted (edited)
On 3/2/2018 at 5:18 PM, Adventure_Time said:

Don't let the account interact with any of your bot accounts in any way/shape/form and you should be fine. You can also utilize proxies on your bot accounts if you want another degree of separation.

@Adventure_Time Sorry for the @, but would you mind elaborating on this? 

If I bot farm to sell GP, but also want to have some for my main, how would I safely transfer funds over? Would it work to buy expensive items, and then kill one of the accounts in the wilderness? Or get a trust third party to take the items to then give to your main? If I give some friends the GP, would they have the potential to get red flagged? 
In conclusion.......Mind defining what a proxy is sonny? Old men aren't great at scripts and computers off the bat xd

Edited by GrouchyOldMan
typo

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 includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
        • Thanks
        • Like
      • 15 replies
    • 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
      • 25 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×