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 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
      • 45 replies
    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
      • 27 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
      • 22 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×