Nullable

Download Windows MacOS (Apple Chip) MacOS (Intel) Linux (x64) Download the CLI app that matches your system and unzip it somewhere. Open a terminal and run: .\tribot.exe --help Replace ".\tribot.exe" with "./tribot" on non-windows systems. This will bring up the documentation. This CLI tool has subcommands which also have documentation. So for example, you can run ".\tribot.exe run --help" to see all the arguments for the "run" subcommand. This CLI auto-updates itself. It can run without the launcher, but you must have logged into the tribot launcher at least once. Troubleshooting VCRUNTIME140.dll was not found This happens when your windows installation doesn't include a certain system file. You can fix it by downloading and installing this: https://aka.ms/vs/17/release/vc_redist.x64.exe After that, things should work

Hello everyone, Many who have read my discord messages or forum blog posts know that I've been working on a big client rewrite a good bit in the past year. A couple months ago we reached a milestone where we could actually run current Tribot scripts on it and since then I've been working with scripters to get Tribot X in a state where it closely matched the behavior of the current client so that we could have a smooth transition. Today we're at a point where most (but not all) scripts work fairly well and I think it would be helpful to get more people using it so we can really move forward on this project. So as of today, you all have access to use Tribot X. Before we begin, please understand that this is an open beta and that there WILL be bugs. Launching Tribot X In order to launch it, you need our new launcher which is also in beta: Once you have that installed and running, you simply need to login, click your username/email in the top right, and click "Show Tribot X": After that, new tabs will appear. The "X Clients" tab will let you launch tribot x clients very similar to how regular ones work. There is also a bulk launcher tab, which does technically work but is a pretty new feature we're still working on. How you can help When using Tribot X, please follow these general guidelines: Report script issues to script authors, not me. They will investigate their code and help me figure out what needs adjusting in the client. Right now we're mostly focused on getting scripts to work. We don't mind general feedback/suggestions/etc, but there are many features not quite far enough along to really need feedback. For example, the current logging window is not done, nor is bulk launching, so feedback on those features are likely not going to apply to the final product. Report UI issues, problems with instancing, bad error messages, etc in the discord. A new section will be open for bug reports. Please try not to add duplicates. Please be very descriptive of any bugs you encounter. If you find a bug already in the discord and you found some new info that might help, feel free to add it to the thread. Notable Tribot X Features Fully function tabs Unlike our current client, Tribot X's tabs are recommended to use. Not only do they prevent cross-tab bugs, they can each run separate jagex accounts and have fully isolated spoofing. Improved resource usage Tribot X is more efficient in a lot of ways, making it generally use fewer resources than regular tribot. This is highly augmented by the use of tabs. Better performance The current client tends to have a lot of FPS problems in-game, especially under high load. Tribot X performs much better and is able to sustain consistently higher FPS with similar resource usage. More accurate, less bug-prone mouse Tribot X's new mouse code is a lot more basic, but as a result we're able to avoid a lot of issues with the old mouse code which has been around for 9+ years. As Tribot X develops, we will be adjusting it a lot to better emulate human behavior and vary them across bots. But for now, we're focusing on correctness. Improved Spoofing Current Tribot uses some older spoofing techniques, which work fine, but with Jagex reducing what clients are "official", it's a good idea to move to a different approach. Current Tribot still has completely valid spoofing, but X tends to gravitate to showing Jagex the same data as Runelite users in particular. Tribot X Future Work Better bulk launcher Break manager + selector Import/export tools CLI support Better logging/error reporting nRestocker support LOTS of antiban additions that need done to better avoid profiling. Many more automation tools Conclusion This project has been a journey. A Tribot rewrite has been something we've toyed with for many years now, and it's awesome to actually see it come to life. A ton of work was put into this so far. Calling it a "rewrite" is no joke, we actually rewrote everything. We re-coded the implementation of the legacy API in its entirety and bridged it to the current API definitions so that scripts could still work. I appreciate everyone who tries it out and provides feedback. Thank you all!

Fixed

Fixed

It is fixed now

We had some unexpected downtime. Things are resolved now.

Tribot does not use the Legacy Java Client, but we make sure we "look" like it. We'll switch over to doing the same for Runelite.

@gaming07rs Please use the new beta launcher:

This was due to an outage on Jagex's end. It is resolved

Yes. The Tribot launcher supports jagex accounts. There is a button for it when you open the application.

@05151560 @Aftab Aslam @scaper103 @fozi1993 The client is now updated. If you have any further issues, please contact the author of the scripts you're using.

You may request a refund via the support ticket section or by emailing [email protected] I am shutting down this script permanently LAN Thiever has received an update and is now re-enabled

As some may or may not know, in the background of everything else going on, I've been rewriting Tribot from scratch. I know, I know, a lot of you have heard that one before. "Good one, Nullable, now fix script download issues". I get it. I even still use the project codename created in 2017 for the first of many supposed "rewrites". But this is real and the best part is that I am still prioritizing development for what you use right now. So at the very least, no harm done. That being said, I am making a lot of progress and I figured some would like to get some details. Injection? Reflection? What are these things? The current version of Tribot is a Reflection bot, for reference. What is Reflection in terms of botting? Reflection refers to the programming mechanism of the same name. It's where, during runtime of the program, code can examine the contents of itself. Since the game runs in the same process, we can use this mechanism to "examine" the game memory and read data. This is allows us to know where the objects and npcs are and stuff like that. The upside of this is that it doesn't modify game bytecode. The downside is that it can be slow. Tribot uses a lot of intelligent caching, though, making it one of the most efficient reflection bots created for the game. Nowadays, we're one of the only reflection bots out there. And Injection? "Injection" refers to the technique of modifying the game bytecode as it loads it. It "injects" friendly names and interfaces into the game's classes so that it can simply call them directly and receive game data. The upside is that it's fast and direct. The downside is that it modifies bytecode. The problem with modifying bytecode is that it's legally dubious and has the potential to be reflected itself. While there is no indication of any sort of reflection-based anti-bot, and patching it would be possible for injection clients, it's always a possibility. So what is Tribot X? Tribot X won't be using either. It will use Compile-Time Wrappers. Not a very catchy name, admittedly. While developing the basis of the new bot, I realized we could have the best of both worlds for how we interact with the game. This technique is actually really simple. The game is just a jar like any other, and can be programmed against. So we do that! public int getSomeValue() { return client.obfuscated_name * multiplier; } And now when we compile and run this, we get the value. Of course, this has lots of problems. I would need a ton of these to get all the data and I would need to change them every time the game updates. Also, there are various other roadblocks that I won't go into for getting this to actually run. We solve the main problem by generating code and compiling it against new game updates. These generated classes act as wrappers and give us the same functionality as injection without needing to inject anything. As such, they are just as fast and require no game modification. We've already written a complete generator for doing this automatically. More details! Since this is my first post on Tribot X, I'll give some one-liners over some of the other random technical details I may not write full posts about. Tribot X has a lot more flexibility in terms of spoofing, and includes the spoofing of runtime information that could be used in the future for bot detection (even though it isn't currently). Tribot's mouse has been completely swapped out and is astronomically more efficient and less prone to error. The current tribot uses an event queue mechanism while the new one uses a single thread with locking to enforce thread safety. By doing so, we reduce the number of threads and overhead. Every method for manipulating the canvas has been optimized. Faster code, less CPU, less RAM. It supports tabs! But really properly this time with perfect isolation and spoofing. The GUI of Tribot X uses Jetpack Compose. The entire bot is written in Kotlin. For really CPU intensive tasks or to share code with our launcher, we have a way to interop Kotlin and Rust code in the client. The architecture of the bot has been entirely changed. Plugins separate from scripts are now a possibility.

Check out the beta for the launcher here:

Script queues will eventually be entirely replaced by a full script automation system.