Jump to content

TRiBot AI Antiban Testing

Recommended Posts

For nearly the past two weeks, I have been working on creating an artificially intelligent antiban system, which is currently ready to be tested. The system works by analyzing how the script performs, the patterns that form, when the player is idling (and the length time), and the triggers which make the script perform certain actions. After doing the analyzing, the system will make decisions on when to perform antiban actions, when and where it should hover the mouse, and when to rotate the camera to face a certain object.


This system works in conjunction with ABC (Anti-Ban Compliance), and character randomization (creating unique profiles for every different bot). In doing so, the antiban system is able to make the bot seem more human-like.


Currently the antiban system is automatically able to apply the following ABC elements:

  • Checking XP
  • Examining Random Objects
  • Randomly Rotating the Camera
  • Mouse Leaving the Game
  • Picking Up the Mouse
  • Random Mouse Movement
  • Random Right Clicking
  • Response Time to New Object
  • Response Time to Switching Objects
  • Hovering Objects
  • Using Closest Objects vs Using Objects Which Aren't the Closest
  • Moving to the Anticipated Next Object Location
  • Delay Between Item Interaction

Through my testing, the system works well. Now I'm asking the public to test the system, and tell me if it screws up the script. More thorough testing will be commenced when it's confirmed that the system does not break any scripts.


To test the antiban system: At the "TRiBot Login" interface, select "Development Release." Doing so should make TRiBot Dev 9.200_0R1 boot up. When you run a script, the antiban system will automatically run in the background.


Other things to note with the dev release:

  • If the bot house control over the mouse, human mouse input will be blocked unless the user moves the real mouse over the bot mouse.
  • Like 14

Share this post

Link to post
Share on other sites

So if I have made a script without any form of antiban or ABCL implementation this would be sufficient?


Just wondering.


For the most part, yes. I'd say it's best to have the script also implement ABC since the antiban system could take a few minutes to kick in as it's learning how the script performs, or in case the system has problems identifying things.




Im using erickhos autobuyer, im not logged in for more than 15 seconds at a time. Would it be worth testing this or should i just ignore?


Testing it would help.

Share this post

Link to post
Share on other sites

THIS IS AMAZING! So glad to see this. There are only 3 things missing. You need to add a system that takes the current level of fatigue and slightly decreases mouse accuracy, or clicks similar looking items(Attentional awareness), and the microbreak system I was talking about. This system will help loads, but it wont help at all with bans if people are still running scrips 24/7, or use the crappy break handler(its okay but, not dynamic enough) So the last thing it needs is a microbreak system as i've explained in my suggestions, which has different systemic levels which go up randomly but realisticly for hunger, thirst, tiredness, and then takes a break for an appropriate amount of time for that activity, and if its a nap it will decrease the delays and accuracys and make them fast and good again. You could make it so the levels increase randomly for each runescape character or tribot account(account profiling) and with this I think bans will basically be non-existant.


Examples on break times, for thirst, 2 - 8 minutes, for hunger 10 - 45 minutes, and for naps 30 minutes to 6 hours possibly, all up to you. If these systems are implemented you will have done every idea I have came up with, and I think bans will be non existant. Thanks, please let me know of your input on if you will do anything with these ideas TRiLeZ I think these systems will help dramatically on top of this ai system.

  • Like 1

Share this post

Link to post
Share on other sites

How would this affect scripts with ABC already implemented and in the future once finished, should we remove the code for it?

This is best added on top of ABCL 10 methods.


This should'nt be seen as a replacement, but another brick.


@TRiLeZ I am noticing some difference, as I have been botting for almost an hour with ZERO randoms so far.

Share this post

Link to post
Share on other sites

The antiban overrides the mouse cursor even when a script isnt loaded, which is getting annoying when u trying to trade people but disables mouse very quickly.


Anyway to make it only activate when a script is loaded or will that undermine it?

Edited by lawlz1
  • Like 1

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 update will:

      Fix GE inventory item positioning bug

      Fix broken object hooks
        • Like
      • 21 replies
    • This release will:

      Fix some ClosedChannelException bug

      Fix bug in RSObject#getAllTiles

      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug

      Fix game object location bug

      Fix small layout bug making the client shift up and down

      Fix client crashing bug where loading the client with a small display area will cause the client to crash

      Fix annoying Linux bug relating to painting events and peers

      Fix settings saving bug where settings are saved to disk more often than they should

      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people

      Drop Java 1.7 bytecode version for 1.8

      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).

      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening

      Fix the incorrect object positions bug

      Fix and re-enable the LG Objects API Accelerator

      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client

      Slightly improved login bot

      Removed final access modifiers from API classes

      Added RSServer hook wrapper to get the client's cached list of server/world info

      [NEW] Bug fix for intelligent banking

      [NEW] Improvement to the stability of LG over time

      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client

      [NEW] Fix LG login problems

      [NEW] Fixed re-sizable mode container bug

      [NEW] Fixed re-sizable mode mouse bug

      [NEW] Use of public constants in the Banking API

      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR

      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.