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

      Fix an issue where breaks would stop firing


      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls


      Fix an NPE in the Combat API


      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
        • Like
      • 21 replies
    • This release will:

      Add LG support for Runelite


      Fix NPCChat issues


      Fix a bug where the camera angle setter would just hold down a key for 5 seconds (the timeout)


      Slightly adjust the rotation via keys to be more accurate


      Add the ability for asynchronous camera movement via keys


      Make Camera rotation via mouse more fluid, with more antiban, and work much better in resizable mode


      Add a "Camera#setCamera" method, allowing the rotation and angle to be set in parallel


      Increase the likelihood of using the mouse for camera movements


      Add support for adjusting the camera to positionable entities (Positionable#adjustCameraTo)



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Thanks
        • Like
      • 59 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×