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

Should you bot at night?

Recommended Posts

To sum up what i previously had down quickly: Is it safe to bot during jagex working hours (9am-6pm [5pm-2am my time]), and is it safe to bot throughout the night? Does this look suspicious having a player bot for an hour or two on and off during the night?

thanks for any input ❤️

Edited by fidgetwhistler

Share this post


Link to post
Share on other sites

It's mostly speculation that the time period you bot during increases ban rate. I've yet to see any hard evidence that proves or even suggests that.

Now I HAVE seen proof that botting for long durations leads to bans, but whether this is because Jagex watches play time or because it accelerates the account's lifespan remains unclear.

@fidgetwhistler

Edited by IceKontroI

Share this post


Link to post
Share on other sites
15 minutes ago, IceKontroI said:

It's mostly speculation that the time period you bot during increases ban rate. I've yet to see any hard evidence that proves or even suggests that.

Now I HAVE seen proof that botting for long durations leads to bans, but whether this is because Jagex watches play time or because it accelerates the account's lifespan remains unclear.

@fidgetwhistler

I can attest to this, I have a small farm going 24/7 and it's not affected by when I bot them. Everything you said is spot on, especially the increased chance of bans when botting for long durations. From personal experience, anything over 4 hours can flag Jagex's system (even on premium scripts) and once you start hitting 8+, unless the script is amazing, your chances of a ban have skyrocketed. Again, this is from my personal experience. 

Edited by itstoms

Share this post


Link to post
Share on other sites

My theory is based on statistical analysis.

Say Jagex applies one factor to narrow down the audience, raising the probability of players in this audience botting from 0% to 10%. Then they apply another factor to narrow the audience and increasing the probability to 25%. Then introducing another factor to narrow the audience and increase the probability to 50%. Then another factor to raise the probability to 90%. Then another to 99%. Then another to 99.999%. Jagex could then ban all of these people. Not all of these people may be botting, but it'll be damn close. It's known that Jagex does falsely ban people for botting.

So the question is, does factor X narrow down any audience which your RS character may be apart, which increases the statistical probability that your RS character is botting?

Having done a lot of statistical analysis of current bots and their behaviours, mouse movement analysis, analysis of human playing data, and reading many scientific studies published in academic journals, I can say this is definitely possible, and a very effective way to determine whether a player is botting. It also explains why Jagex has had numerous job postings for big data scientists.

Jagex would also not rely on just one set of factors. They could have tens or even hundreds of sets of factors. They are also not limited to factors which clearly determine a player is botting. All they need is a factor which could increase the likeliness that a player is botting. That increase could also be minuscule - it could increase the probability by just 1%, but that could be significantly larger when paired with other factors.

In my personal opinion, I believe you should bot during the same time the majority legit players play the game within your local region.

  • Like 1

Share this post


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

It's mostly speculation that the time period you bot during increases ban rate. I've yet to see any hard evidence that proves or even suggests that.

Now I HAVE seen proof that botting for long durations leads to bans, but whether this is because Jagex watches play time or because it accelerates the account's lifespan remains unclear.

@fidgetwhistler

I see. Do you think I can bot overnight?

Share this post


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

My theory is based on statistical analysis.

Say Jagex applies one factor to narrow down the audience, raising the probability of players in this audience botting from 0% to 10%. Then they apply another factor to narrow the audience and increasing the probability to 25%. Then introducing another factor to narrow the audience and increase the probability to 50%. Then another factor to raise the probability to 90%. Then another to 99%. Then another to 99.999%. Jagex could then ban all of these people. Not all of these people may be botting, but it'll be damn close. It's known that Jagex does falsely ban people for botting.

So the question is, does factor X narrow down any audience which your RS character may be apart, which increases the statistical probability that your RS character is botting?

Having done a lot of statistical analysis of current bots and their behaviours, mouse movement analysis, analysis of human playing data, and reading many scientific studies published in academic journals, I can say this is definitely possible, and a very effective way to determine whether a player is botting. It also explains why Jagex has had numerous job postings for big data scientists.

Jagex would also not rely on just one set of factors. They could have tens or even hundreds of sets of factors. They are also not limited to factors which clearly determine a player is botting. All they need is a factor which could increase the likeliness that a player is botting. That increase could also be minuscule - it could increase the probability by just 1%, but that could be significantly larger when paired with other factors.

In my personal opinion, I believe you should bot during the same time the majority legit players play the game within your local region.

Well written, worth the read. 

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