Jump to content
Qtulu

When botting, adopt the broken glass mentality.

Recommended Posts

THE THEORY

When goldfarming, it is crucial to stay on top of the game and especially ahead of the Jagex staff.

However, bans will happen. It doesn't matter if you botted for 4 hours or 4 months, doesn't matter whether you lost or made money. What matters is that the ban is inevitable and WILL happen. If you adopt the broken glass mentality, you will be prepared for the day your accounts get swiped and will be able to rebuild more effectively.

What is the broken glass mentality? It's a zen buddhist approach to everything you come across in life. Allow me to introduce you to the story which inspired me to write this post:

One day some people came to the zen master and asked ‘How can you be happy in a world of such impermanence?' The master held up a glass and said ’Someone gave me this glass, and I really like this glass. It holds my water admirably and it glistens in the sunlight. I touch it and it rings! One day the wind may blow it off the shelf, or my elbow may knock it from the table. And I say, ‘Of course.’ When I understand that the glass is already broken, every moment with it is precious.'

All your accounts are already banned. This helps you get over the emotional tsunami you get when you try to login and the screen says: sorry mah niggah, your account has been removed. Everytime you login to the game, you expect this. Or the famous freeze and connection lost right after you log into the game. When this DOESN'T happen, you praise the Seven gods. When it DOES, what does it matter? You expected this.

What do you do when you expect all your accounts to be banned?

You think ahead and get yourself some back-up accounts, even if you just created and hand-trained your precious flax picker team. For every account you currently use in the game, you have one without membership waiting in line to be deployed (you can utilise the same approach with IP's, if you have the money and calculate the loss to gain ratio).

THE CYCLE

If your accounts survive the 14-day membership purchased with a bond, you let them chill in F2P and deploy your back-up ones. It's ideal to have 3+ groups of account you cycle, two groups active, one not active. Sometimes, mix the groups together and let some accounts go botting OR chilling 28 days in a row.

This is something I have been practicing with my farms and it seems to lower the ban rate (at least for me).

Good luck with your automated adventure.

  • Like 2

Share this post


Link to post
Share on other sites
 

@Qtulu

It's hard to keep ur mentality, what keeps you motivated?

Formlessness. Whenever your accounts get swiped, it means your method is not 100% effective. Time to adjust it so your account last longer; trial and error. See it as an inevitable part of the process, because that's exactly what it is.

Share this post


Link to post
Share on other sites
 

Formlessness. Whenever your accounts get swiped, it means your method is not 100% effective. Time to adjust it so your account last longer; trial and error. See it as an inevitable part of the process, because that's exactly what it is.

Yes my friend but that doesn't explain how you keep motivation?

Share this post


Link to post
Share on other sites
 

Yes my friend but that doesn't explain how you keep motivation?

It does indeed; if you assume the current state of your farm is your end goal, you lose your motivation. If you assume the current state of your farm is merely a part of a process, you can stop bullshitting yourself and get working on the process. You gotta get stuck in a positive loop, which I admit is hard with goldfarming since bans are unpredictable and unpleasant. Accept that and the fact that gold farming is not a steady income. I highly suggest you take up programming in Java and write your own scripts if you haven't already, because when you stop gold farming (and you will at a certain point in your life), you will at least have some useful knowledge and not just cash you most likely already spent.

Edited by Qtulu
fixed a typo
  • Like 1

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 update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
      • 23 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
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×