Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
TRiLeZ

Tutorial for Safe Botting

Recommended Posts

I just got reported by two people while training at Warriorguild with a premium script..what do i do now?

 

You have probably already found out if a ban was coming or not. After being reported, accounts are most likely watched by Jagex for signs of botting. Either stop botting or, at the very least, bot very, very carefully (no more than 8 hours a day, with breaks).

Edited by DeriveSoHard

Share this post


Link to post
Share on other sites

I've been hearing around the block recently that now, more than ever, fresh accounts are getting targeted quite quickly, and it's best to lightly play legit on the account for 1-3 days before starting to bot it.

 

Would be interesting to see how effective this really is in practice.

  • Like 1

Share this post


Link to post
Share on other sites

I've been hearing around the block recently that now, more than ever, fresh accounts are getting targeted quite quickly, and it's best to lightly play legit on the account for 1-3 days before starting to bot it.

 

Would be interesting to see how effective this really is in practice.

I'm going to try and bot one of my old level 3's with 74 WC on it. See how it fairs. I've played a few days legit so will see how it goes.

  • Like 1

Share this post


Link to post
Share on other sites

I don't know what runescape have atm, they got some super anti bot-watch riot going on.

They are banning accounts like hell now, they haven't never banned accounts this fast.

 

The proxies doesn't work, paid "good antiban" scripts doesn't work.

I'm gold farming with a lot of accounts, but the bans are ruining my business.

I don't know what's going on now, I can barely bot 7-8h on a 1 bot without getting banned straight away.

Share this post


Link to post
Share on other sites

I have a good feeling they are banning a lot based on time play. Well atleast they are flagging that. My accounts banned recently I think have been because they have been playing too long. I have botted for about 14 hours on one and got ban while I was watching it. So I think I will start botting only 4-6 hours a day and be more patient.

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.


  • Our picks

    • 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
      • 61 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
    • 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...