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 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.

×