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

Question on expired bans

Recommended Posts

After a year of having a 2 day ban, and then that ban is stated as "expired" a year later - is it safe to bot? Will I receive a 2 day ban or perm ban if I receive another ban? I've botted before on 2 accounts and both of the first bans were 2 day bans so I'm assuming from experience your first ban won't be a perm for botting. Sorry if this has been asked before, used the search bar and found no topics on it.

Share this post


Link to post
Share on other sites

From what I've read on previous discussion threads, the jagex twitter, and from personal experience, 2 day botting bans are not a guarantee (even for "main" accounts that aren't used for gold farming or rwt). If you do get one, you only get one, after which you're liable to get a permanant ban (even if it expires). If you'd like to still bot on that account, I would recommend testing script/script settings out on a throwaway account before using it on the account you care about. Good luck!

  • Like 1

Share this post


Link to post
Share on other sites
26 minutes ago, gyrate said:

From what I've read on previous discussion threads, the jagex twitter, and from personal experience, 2 day botting bans are not a guarantee (even for "main" accounts that aren't used for gold farming or rwt). If you do get one, you only get one, after which you're liable to get a permanant ban (even if it expires). If you'd like to still bot on that account, I would recommend testing script/script settings out on a throwaway account before using it on the account you care about. Good luck!

This is the answer I was looking for, thanks.

Share this post


Link to post
Share on other sites

in my experience it's random. I've had the same thing happen to me where I let an account sit for over a year with an expired ban, start botting on it and get another 2 day ban. I've also just been perm banned on main accounts with no prior bans. I suggest you use a proxy to bot the account and in case it gets banned again, you can send in a ban appeal request and theres a chance you will be able to get the ban quashed.

  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, alfonsobravo said:

I'll be talking from personal experience here.

Every single account I've gotten a 2 day ban on was given another 2 day ban after getting caught when the initial temp ban had expired. 

When the 2 day ban expires, it drops your ban meter all the way back to 0. 

Have you used proxies? I haven't because I didn't think I'd get banned but I know the purpose of using proxies

Share this post


Link to post
Share on other sites
12 hours ago, Jason277 said:

Have you used proxies? I haven't because I didn't think I'd get banned but I know the purpose of using proxies

Nope, all were on my home ip. I have found that you could create your account on your home ip, change password and bot a proxy. After you get caught on that proxy, attempt to recover your account using your home IP. Doing this will get your account unbanned as it shows jagex that you were "hacked" as you botted on a foreign ip, and therefore they unban you. Again, from personal experience. 

One thing I'd like to note is that you should be cautious when choosing who hosts your proxies. Some proxies/countries are flagged and could cause a fast ban.

Edited by alfonsobravo

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