Our Picks

We've heard your complaints - the TRiBot API could be much easier to use. We've been dedicating our time to improving the scripter experience here and spent the past year working on a new and improved API - the TRiBot Script SDK.

 

The TRiBot Script SDK is an easy-to-use library for building TRiBot scripts. It is the recommended approach to building scripts moving forward over the old TRiBot API. It contains all the core things you need to build a script, and a ton of additional helpful stuff to get you using your scripts quicker. See the documentation section for everything offered, and check out the brief overview link too.

 

The SDK was announced in preview here:

 

It is now officially released. The official release guarantees we will support backwards compatibility for some period of time. See the 'backwards compatibility' section below for more info.

 

How to use:

There is multiple options, listed in the order they are recommended.

1) Use the gradle template mentioned below

2) Obtain through gradle

Add this dependency: api("org.tribot:tribot-script-sdk:+")

Add this repository: maven("https://gitlab.com/api/v4/projects/20741387/packages/maven")

3) Take from your local filesystem in your .tribot/install folder. For example, on windows, you'd find it at "C:\Users\[user]\AppData\Roaming\.tribot\install\tribot-client\lib\tribot-script-sdk-[version].jar"

 

Documentation:

Java docs: https://runeautomation.com/docs/sdk/javadocs/index.html?overview-summary.html

Kotlin docs: https://runeautomation.com/docs/sdk/kdocs/index.html

 

Backwards compatibility:

We will be following a deprecation schedule whenever we perform a possible breaking change. We will deprecate the respective methods or classes and announce it in a topic. It will remain deprecated for some period of time (weeks or months), and then removed. This will give you time to fix anything, if we need to make a breaking change.

 

Gradle template:

Easily build scripts with a new pre-configured scripting gradle template

 

Users of the current API:

There is no plans to remove TRiBot API. It will still be available. However, non-critical bugs probably won't be fixed. The SDK does depend on some of the API so fixing some things in the SDK will indirectly fix the API. However, bugs that have existed in the API for awhile will likely not be fixed. It's recommended to use the SDK moving forward. Let us know if there's something the SDK is missing.

 

Brief overview of the changes:

 

Bug reports:

Post bug reports in the bug reports section of the forums

 

 

Let us know what your thoughts are! If you have questions, feel free to ask below or in discord.

 

Support for the gradle launcher is being dropped. Read more about the new launcher here.

What to expect from TRiBot moving forward.

TRiBot 12 Release Candidate

The TRiBot team has been hard at work creating the last major version of TRiBot before the TRiBot X release. We've noticed many problems with TRiBot 11 with a lot of users preferring TRiBot 10 over 11. We've heard you, so we took TRiBot 10, added the new features introduced with 11, introduced some other new things, and created TRiBot 12. So without further adieu, here's TRiBot 12.

Gradle is a build tool used to accelerate developer productivity.

We recently setup a Maven repository (TRiBot Central) to make it easier for scripters to create scripts. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-central/-/packages

Furthermore, we've released a simple Gradle project to make it easy to run TRiBot and develop scripts for it. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-gradle-launcher

The goals of TRiBot Central are to:

Deliver updates to TRiBot faster


Better organize TRiBot's dependencies (AKA dependancies)


Make it easier to develop scripts for TRiBot


Make it easier to use and run TRiBot


Note: TRiBot won't be able to run scripts from within this project until TRiBot's next release.

Hi everyone,

I'd like to thank everyone for their patience in this transition period. Since last week, we've worked out the remaining bugs with this integration.

Some users have still been having issues with connecting their forums account to their Auth0 account. To resolve this, we've imported all forums accounts into Auth0.

Unfortunately, the accounts which were imported today were using an unsupported password hashing algorithm. Hence, random passwords were set during the import.

What does this mean for me?

If you've previously linked your forums account to your Auth0 account, you don't have to do anything. Nothing changes for you.


If you haven't logged in via our new login yet,

Try logging in with your forums email address and the last password you used


If you are unable to login, please use the "Forgot password" tool on the login page:
Follow the instructions to reset your password
 

Hello everyone,

Last week we tried to roll out Auth0 Login, but we lost that battle. Now it's time to win the war!

Important changes

When logging into the client, you'll now have to enter your Auth0 account credentials instead of your forums credentials

Note: 2FA is still handled through your forums account (for the time being)



Changes for existing users

You'll have to link your Auth0 account to your forums account here: https://tribot.org/forums/settings/login/?service=11


Auth0 accounts have been created for most existing users. Please use your forums email address and password to login.



Important notes

Make sure to verify your email address upon creating a new Auth0 account


When we mention your Auth0 account, we mean your account used for auth.tribot.org as displayed below

To better support the upcoming changes (TRiBot X, new repository), we're switching our login handler to Auth0. Instead of logging in with the standard form, you'll now be required to login through our Auth0 application.

All existing accounts which have been used within approximately the past year have been imported into Auth0 using the same email and password combination which has been stored on the forums.

What does this mean for users?

Your account credentials are now even more securely stored


You'll be able to login via Facebook, Google, and others in the future


Is there anything users have to do differently now?

Existing users: You'll have to login with the standard login, open your Account Settings, then link your Auth0 account


New users: You'll be redirected to our Auth0 app (auth.tribot.org) where you'll be able to create an account


Why was this change made?

The new apps we are creating (such as the new repository) aren't able to use the forums to handle user logins


To centralize all user accounts in one area


To ensure that the client login doesn't go down when the forums are having problems


To speed up our development


Other considerations

There's no documentation or official support for using Invision Community combined with Auth0, so there are still a few kinks we're working out


We're in the works of creating an account management panel specifically for Auth0 accounts (ETA August)


It's not possible to change email addresses for the time being (this will be resolved this August)


Changing passwords is a weird process for the time being. To change your password, you'll have to use the "Don't remember your password" tool on the Auth0 login page

Over the past month, we've been working hard on TRiBot's new repository - a much needed update. This change has been deemed necessary for TRiBot X, and will allow us to really speed up development of all aspects of TRiBot.

Today we are going to share what we've been working on!


Now you must be wondering what kind of features the new repository will have.... well, you'll have to be patient for a little while longer. We're still figuring out various technical aspects so we can't provide answers to all possible questions. We're also focusing on development rather than writing about it so that everyone can get access to our latest developments at lightning speed. I will however answer a few users' questions.

We're planning on a release of this early to mid August, giving users some goodies before TRiBot X's release.

Thank you all for being patient. I hope everyone is excited as much as I am!

Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.

TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.

Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.

So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).

Love, 

RileyZ

Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!

Why?

Increased reliability - less server errors


Increased availability - less downtime


Increased security - keeping us and you secure


Increased capacity - ability to serve you better


Increased speed - less waiting for things to load


Faster development - server and service updates will come faster


What are the changes?

Move from a single AWS EC2 instance to AWS ECS (Elastic Container Service)


Distributed computing


Load balancing


Git management of server files and filesystem


Redis caching


How?

AWS ECS (with 10 EC2 instances)


AWS ElastiCache (Redis)


AWS Load Balancing


AWS EFS (Elastic file system)


Please bare with us as I continue to tune the server for maximum performance. Slow loading speeds may occur temporarily. I thank everyone for their patience.

Please post on this thread if you experience any issues other than slow loading times.

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.

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.

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

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

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

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

This release will:

Add LG support for Runelite


Fix NPCChat issues


Fix a bug where the camera angle setter would just hold down a key for 5 seconds (the timeout)


Slightly adjust the rotation via keys to be more accurate


Add the ability for asynchronous camera movement via keys


Make Camera rotation via mouse more fluid, with more antiban, and work much better in resizable mode


Add a "Camera#setCamera" method, allowing the rotation and angle to be set in parallel


Increase the likelihood of using the mouse for camera movements


Add support for adjusting the camera to positionable entities (Positionable#adjustCameraTo)



Upcoming updates:

Improved CLI support


Much more



Note: If you are using LG, please restart both the RS client and TRiBot

This update will:

Allow for clicking through the chat box when possible (Thanks @Todd)


Fix Combat#selectIndex (Thanks @Encoded)


Ensure worlds stay sorted and added a check to avoid misclicks in the in-game world hopper (Thanks @erickho123)


Fix out-dated Options API interface indices (Thanks @Todd)



Upcoming updates:

Break handler bug fix


Improved CLI support


Much more



Note: If you are using LG, please restart both the RS client and TRiBot

This release will:

Fix login bot after today's game update (Thanks @JoeDezzy1)


Fix latest in-game world hopping issues (Thanks @erickho123)


Compact Settings UI and set location relative to TRiBot (Thanks @JoeDezzy1)


Fix an older implementation of GrandExchange#getWindowState (Thanks @JoeDezzy1)


Improve the preformance of NPCChat by only searching in certain interface parents (Thanks @JoeDezzy1)



Upcoming updates:

Break handler bug fix


Improved CLI support


LG support for RuneLite


Much more



Note: If you are using LG, please restart both the RS client and TRiBot

This release will:

Fix bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


Fix NPE caused by non-null value in GE API (thanks @erickho123)


Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


Add Entrana area to Ships API (thanks @erickho123)


Fix raid prayers index/settings in Prayer API (thanks @erickho123)



Upcoming updates:

Break handler bug fix


Improved CLI support


Much more



Note: If you are using LG, please restart both the RS client and TRiBot

This update will:

Implement better canvas locking/synchronization mechanism


Fix small Login API bug


Remove the requirement for xbooting Java classes


Use ExecutorService to perform canvas work in parallel


Add "Account Management" game tab to GameTab API (thanks @Encoded)


Fix NPCChat#getMessage (thanks @Encoded )


Fix NPCChat#selectOption (thanks @Encoded )


Fix Banking API after today's update (thanks @Encoded )


Fix in-game world hopper after today's update (thanks @Encoded )



Upcoming updates:

Break handler bug fix


Improved CLI support


Much more



Note: If you are using LG, please restart both the RS client and TRiBot

This release includes:

Fix updater bug which was causing a bunch of issues


TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


Hooked login fields


Improved the login bot


Ability to recognize the banned/locked messages again


Ability to read the current input for username and password fields


If the username or password is already entered correctly, it won't be erased


If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





Coming soon:

Skull icon fix


Improve screen rate and responsiveness of the RS client (both regular client and LG)


Much more

This release includes:

Fix shift clicking option selecting


Fix high paint delay settings saving


Update prayer IDs for the quick select menu


Remove RS3 support


Fix hooks



RS3 Support Removed

The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.