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

Experiences with botting after 2 day moderate ban?

Recommended Posts

I recently got the moderate two-day ban on my new main. I accidentally fell asleep and ran the bot overnight. I was using a premium agility script, without VIP extended (so no human mouse movement or looking glass).

Do you guys think that by using VIP extended, being careful not to bot ridiculous hours, and using premium scripts, I am okay to continue botting yet?

If any of you have any experience with this I would appreciate some insight!

Thanks

Edited by reinstalled
typo

Share this post


Link to post
Share on other sites
2 minutes ago, reinstalled said:

I recently got the moderate two-day ban on my new main. I accidentally fell asleep and ran the bot overnight. I was using a premium agility script, without VIP extended (so no human mouse movement or looking glass).

Do you guys think that by using VIP extended, being careful not to bot ridiculous hours, and using premium scripts, I am okay to continue botting yet?

If any of you have any experience with this I would appreciate some insight!

Thanks

You're not safe. You're already very lucky to only receive a 2-day, stop botting on that account if you are care about it.

Share this post


Link to post
Share on other sites

Very unfortunate I'm in the same spot but I did get 1-99 agility on 2 accounts without getting any bans using aAgility but you really need to play with the entire settings. I got hit with a 2 day moderate 2.5 weeks after getting 99 agility and I'm 100% sure it wasn't that. It was the fact that I left the Nightmare Zone script on overnight after playing legit during the day, about a total of 2 hours running before I got slammed with the RS update.

From personal experience, I've been able to max out mele on a 2 day banned account back in 2014 using the NMZ script and have been able to run the barrows script for 10+ hours daily for about 1 month before it being perma'd (Did about 5k barrows chests before it was gone).

That being said, never bot during Jagex working hours and always use Looking Glass + Human Mouse Movements. I don't suggest botting agility since you seem to not know what you're doing and you'll get perma'd for sure unless you want to risk your account.

I've done 50M+ botting experience before I got hit with a 2 day but I'll play legit for a little and go back to maxing out in Nightmare Zone doing about 8 hours daily with 1-2 hours legit playing time. Shouldn't be in no risk and I feel that I was unlucky since NMZ isn't really a high ban rate place and is very AFK BUT I will be testing it on a new account first.

 

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