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

Max Time To Bot

Recommended Posts

what would you say is the longest amount of time you would bot and feel safe about not getting banned ? { for example if you are wood cutting how long would you leave the bot cutting before having it brake and you play on the account manually } im curious what everyone's experience has been. im looking to run a bot maybe 5 hours a day to help lessen xp waste during when i work but am quite scared of getting banned. thoughts ?

Share this post


Link to post
Share on other sites
18 minutes ago, gandalf29 said:

what would you say is the longest amount of time you would bot and feel safe about not getting banned ? { for example if you are wood cutting how long would you leave the bot cutting before having it brake and you play on the account manually } im curious what everyone's experience has been. im looking to run a bot maybe 5 hours a day to help lessen xp waste during when i work but am quite scared of getting banned. thoughts ?

Firstly, and most importantly, don't bot an account you're not willing to lose.

After this, any amount of time you bot risks the chance of a ban. Woodcutting is often a popular botting skill and as such is often watched. If you are purely doing it for XP make sure you are dropping the wood (doing a low gp method) and try and find a secluded place. Whatever script you use to make sure it has good anti-ban, paid scripts (ideally private) are always preferable to free as they tend to be better quality. 

Across these forums, there are guides on how to bot smartly. I would also recommend investing in VIP-E - the human-mouse data, in my opinion, makes a huge difference to ban rates. Looking glass is also a good feature (but its effectiveness is up for debate, but cannot hurt in reducing ban chances). Also, VIP-E lets you try trials of scripts which is useful for finding which one works best for you.

Do quests on the account, play legit still. This will also, in my opinion, lower the chance of a ban (as long as you are not doing gold farming methods).

Again tho, don't bot an account you're not willing to lose.

Share this post


Link to post
Share on other sites
5 hours ago, gandalf29 said:

Thanks i think im going too lightly bot maybe 4-5h max per day non gold farming methods, assuming its a first offence what is the likely hood i would receive a 2day vs perm ban roughly?

Depends on your account.

If the account is older and has higher stats it´s probably getting a 2 day ban. If you bot instantly on a new account you´re probably getting a perm ban.

Share this post


Link to post
Share on other sites
3 hours ago, CyberWizard said:

Playtime is not part of the macro detection system. Breaks are a waste of time. I bot all my accounts 24/7 and you should too. If you're going to get detected, you're going to get detected. Just take the best precautions you can.

this

Share this post


Link to post
Share on other sites
On 1/16/2019 at 5:21 AM, CyberWizard said:

Playtime is not part of the macro detection system. Breaks are a waste of time. I bot all my accounts 24/7 and you should too. If you're going to get detected, you're going to get detected. Just take the best precautions you can.

Not in my experience, suicide botting combat is a sure fire way to get banned. Perhaps it may be different for other skills.

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