Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
jkilla7

(Finally) received a 2 day ban after 95m ~ XP and hundreds of mills farmed. ​​​​​​​

Recommended Posts


I just wanted to say, thank you tribot for the massive gains on my ironman. I definitely WILL NOT be botting that account anymore wouldn't want to risk a perm. 

 

I initially started botting in November. I wanted to make gains but I had finals. I didn't want to risk my 2k+ total main, so i botted a fresh ironman. I started with just agility and wintertodt,  thinking "oh, i'll just bot graceful.. nothing serious just an early game grind. If i get permed at least i didn't invest any time into this account". (I didn't bot with the intentions of gold farming, I botted with the intention of eventually receiving a 2 day). 

Soon after, I found myself botting all resource gathering skills since i'm an iron, some skills cannot be automated.My goal was to make it to 2k total with 200m fm and 200m thieving.My downfall was that i got extremely greedy. I broke the rules i set for myself and I know exactly which script specifically got me banned. I got lazy. Fellow botters stay safe, don't get greedy and you can't potentially bot for a very long time.

Further more, I've experimented with many scrips on here enough to know without a doubt that there are some GODLYYYY scripts on here in which, the only bans are due to user mistakes (no breaks, long hours in a single place, very repetitive "schedules" etc).

I have no regrets. 22$ total invested for 95m XP, a lot of gp, pet's etc. That's essentially hundreds of hours saved. 

 

Just as a disclaimer: Jagex if you're listening, I don't advocate botting i'd rather not get permed Lol..

 

 

 

Screen Shot 2019-06-10 at 3.30.33 PM.png

  • Like 1

Share this post


Link to post
Share on other sites
4 hours ago, Jackasia said:

Same here .. I'm 9 levels away from max cape and 100's of mills on my main all from botting 14 hours a day using tribot. No ban so far.

Impressive brother. 

 

1 hour ago, Priscilla said:

Nice progress!
What did you do for the hunter portion?

 

red chins to 98, black chins to 99.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Our picks

    • This update features:

      Fixed broken hooks from today's update


      Fix wilderness level with RuneLite (Thanks @Todd)


      Add support for Kotlin .class files in scripts (Thanks @wastedbro)


      Overhaul Inventory API (Thanks @wastedbro)


      Add List support for common methods


      Change method grouping to make more sense (by functionality)


      Refactor methods to utilize Java 8 streams instead of cumbersome loops




      Recognize chatbox minimization (Thanks @JoeDezzy1)


      Fix Screen#isInViewport when NPC chat is open (Thanks @JoeDezzy1)


      Fix login bot bugs (Thanks @erickho123)


      Fix hint arrow return values (Thanks @Encoded)


      Fix depositAllExcept functionality (Thanks @wastedbro)


      Change containing box interface bound and adjust for Y values (Thanks @erickho123)
        • Like
      • 151 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 replies
    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Thanks
        • Like
      • 28 replies
    • 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
      • 64 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...