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

Babysitting bot?

Recommended Posts

is it possible to not get banned(in this specific context) if a jmod teleports you away because of suspecting you of botting? What i mean is if you are constantly babysitting and that does happen, can you you be quick enough to pause the script and respond like a normal human being?

 

P.S. blah blah bots get banned i know this already and there's nothing to garuantee not getting banned i was just wondering for this specific circumstance. 

Share this post


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

i still cannot figure out what happned

Most likely a game bug.

The process of bot detection is (almost) fully automated, and it mainly relies on heuristic analysis. Babysitting your bots does not alter the script's input, and will have virtually no effect on the ban-rate.

 

Share this post


Link to post
Share on other sites
1 hour ago, zealfaith said:

I guess what I'm trying to say is if a player reports you what do the jmods look at to ban that account

Yes, player reports will definitely hasten the process of your account being banned, but the system does not rely on them.

Otherwise, botting within instanced areas (such as Player Owned Houses) would have a ban-rate of 0, because nobody would be able to report you.

 

Share this post


Link to post
Share on other sites

I don't believe jmods manually teleport you to themselves, other than when they make those "bot busting" streams.

Only case where I believe this could happen is if your account has very very high levels and Jagex has some filters set up to not autoban people who are grinding hard. Other than that everything probably happens on movement/reactions/delays/patterns/etc tracking level and require no mod participation to disable account.

Share this post


Link to post
Share on other sites
1 hour ago, turbo_ said:

I don't believe jmods manually teleport you to themselves, other than when they make those "bot busting" streams.

Only case where I believe this could happen is if your account has very very high levels and Jagex has some filters set up to not autoban people who are grinding hard. Other than that everything probably happens on movement/reactions/delays/patterns/etc tracking level and require no mod participation to disable account.

i wonder what days they bot bust the most?

Share this post


Link to post
Share on other sites
1 hour ago, zealfaith said:

i wonder what days they bot bust the most?

well if bot busting is mainly an automated system like most of us believe it is - then it is monitoring game 24/7, computer algorithms do not need to rest. you should understand that bans are not triggered in 1 second(unless you have flagged IP) when you do something botlike once - it is probably a chain of your actions that lead to account ban. read Trilez post and his theory on bot detection:

I believe it is pretty accurate.

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