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

New Premium Script Standards - Working to Reduce Bans

Recommended Posts



As many of you are aware, Jagex has taken a more aggressive stance on bots. In response, I have been improving TRiBot in many areas to prevent bans, mostly with Anti-Ban Compliance (ABC) for scripts, and character randomization. In case you don't know what ABC or character randomization is, here is a quick explanation.


Character randomization means that every different RuneScape player using TRiBot will be given a different "botting profile." This botting profile will hold tons of characteristics about how the bot will play the game, and react to different circumstances, including, but not limited to: mouse movement styles, move movement speeds, mouse clicking speeds, typing speeds, delay time before clicking objects, npcs, items, etc, when the bot should activate run, when the bot should eat, when the bot should hover over the next object, when and where the bot should move to when waiting for an object to spawn, how often to check xp (and if it should), and tons more. We have over 300 variables used to randomize botting profiles. By using these botting profiles, TRiBot is able to effectively make each bot more human-like by seperating it from all of the other bots, making its style unique, and by giving it a consistent playing style across multiple scripts.


ABC is character randomization, which is to be used by scripts. It will give each unique bot different logic in how items, objects, npcs, interfaces, etc are interacted with. ABCL is the ABC score for the script, ie. how much of TRiBot's character randomized antiban methods the script uses. ABCL 0 means ABC actions are not performed at all. ABCL 10 means the script applies ABC actions to the max, giving it the most human-like botting style possible. Personally, I think that if you don't want your account banned, you should never use a script which isn't ABCL 10. Traditional antiban methods (which are not ABC) are ineffective against fighting bans, and may even make your bot more bot-like, thus increasing your account's chance of ban.


Over a month ago, I stated my plan to the premium scripters to incorporate ABC in all of their premium scripts, and to make them all ABCL 10 (except for traders, questers, and mules). July 01, 2014, was the date at which all premium scripts were required to have made their script ABCL 10. Scripts which do not meet the requirement of having ABCL 10 will have their sales disabled until they meet the requirements. If those scripts do not meet the requirements for the second defined deadline, they will be released for free.


Just recently, I disabled the sale of 34 premium scripts which had ABCL 0, meaning no attempt was made to implement any of TRiBot's Anti-Ban Compliance standards to those scripts. When those scripts implement ABC, their sales will be re-activated again.


We have another date later in the week to disable the sale of all scripts which don't have ABCL 10, not just the ABCL 0 scripts. At the moment, only a few scripts have a perfect implementation of ABC. We plan to make all scripts have ABCL 10 within the next week or two.


Here at TRiBot, we are committed to reducing the ban rate, and making bots seem as human-like as possible.




  • Like 7

Share this post

Link to post
Share on other sites

Thank you TrileZ, an absolutely fantastic decision.

I was very disappointed to see many premium scripters not using abcl in their scripts, hopefully now we can see the change.


Seeing as you have the balls to actually disable premium script sales for the people that did not even bother to implement ABCL in their scripts is a very nice and rare sight to see, thank you.

Edited by Ratz241
  • Like 1

Share this post

Link to post
Share on other sites

If the script is released for free, then what happens to those who just bought it? Bit unfair to them isn't it?

I think that is unfair but you are also supporting the people who make it. What I dont understand is why they would do that then the bot will be eventually worthless because of so many people using it.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • 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
      • 19 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)




      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
    • This release will:

      Fix an issue where breaks would stop firing

      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls

      Fix an NPE in the Combat API

      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
        • Like
      • 21 replies
  • Recently Browsing   0 members

    No registered users viewing this page.