Leaderboard

Hey everyone! It's been a while since the last blog post. With everything going on in the past year, there hasn't been much room for development outside of just catching up. For a while, the biggest efforts have been largely experimental and exploratory as we work to revive the Looking Glass feature. For those unaware, Looking Glass (LG) was originally Tribot's "mirror client" where Tribot ran by delegating all its functionality to a separate client (Runelite, OSBuddy, Vanilla client, and even the web browser at one point long ago). This feature has had many ups and downs until eventually Runelite became the only official Java client and they changed so much that Looking Glass as it was became quickly unviable. During the experiments for a new Looking Glass, we started developing a way to run Tribot X inside Runelite instead of mirroring between processes. This was more stable and gave us more flexibility in how everything was implemented. However, it still had several pain points that I wasn't completely satisfied with. The thing is, both Tribot X and Runelite each have their own ways of getting certain data, doing calculations, and setting up what is essentially a runtime. Often times both components would be duplicating work, or worse, fighting with each other causing more inefficiencies than we want. Tribot X's Looking Glass was feasible, but I think we deserve something even better. This led us to an idea where instead of trying to adapt Tribot X to Runelite's environment, we could port Tribot X's functionality into Runelite's standard ecosystem. Introducing Project Echo Project Echo is next-generation version of Looking Glass. It runs directly in vanilla Runelite - no custom builds, no dev mode, no modification whatsoever. But unlike Looking Glass, it's made for Runelite. Without going into too much detail, this means: More efficient model calculations Compatibility with the GPU and HD plugins, menu swappers, etc More efficient input operations Better UI/UX Overall, way more stable While this is a distinct project from Tribot X, there is still tremendous overlap. Pretty much everything we developed for Tribot X is being utilized for this project and by the end of it there will be complete parity. Input Mechanisms Project Echo will utilize human-mouse input in the exact same way as Tribot X. Every account will have its own unique profile, and all inputs will utilize actual mouse movements/clicks within the game environment. Tribot Scripts All current scripts will be compatible with project Echo. This is what is going to take us the longest amount of time to implement and test, but so far we think scripts will have to make little-to-no adjustments to ensure compatibility with Project Echo. Spoofing Project Echo makes very few adjustments to the overall environment and does not need much spoofing. What spoofing we do, we do without modifying Runelite or the game itself. Project Echo will include random.dat spoofing and HWID spoofing like Tribot X, ensuring that your accounts can't be linked with those methods. A lot of the experiments in the past few months gave us insight into how little modification we can get away with. The goal here is to be as vanilla runelite as possible, and so far I'm very happy with where we've ended up on that goal. Tribot Launcher / Bulk Launcher / CLI Integration Project Echo will be fully supported by all of Tribot's ancillary tools, like CLI. You'll be able to easily spin up Echo clients the same as Tribot X clients, with full support for Jagex accounts, legacy accounts, etc. There will be no need to manually setup runelite or use the Jagex Launcher. What about Tribot X? Tribot X isn't going anywhere. The current plan is to offer Tribot X and Project Echo, both, as first-class products. Tribot Echo will likely be gated behind Tribot Premium, but will otherwise be available in the same way Tribot X is. New features that can be developed for both projects will be, and both will be maintained with the same high priority. Project Echo Roadmap The current plans are: May (now): Finish concept and implement bot runtime, script loading, mouse/keyboard, and basic API for scripts (done) June: Add Tribot Launcher support, repo connection, and port over Tribot X core APIs July: Finish script API bridge. Alpha testing + scripter testing + potentially close-beta testing August: Open beta release With any luck, I may be able to get these milestones done sooner. Luckily, a lot of this work was already accomplished by Tribot X and just needs refactored such that we can use it in both projects. Please let me know your thoughts in the comments. I'll be here to answer any questions. Thank you and happy botting!

another update AIO almost fully supported on Echo

Experience the most advanced Temple Trekking script for OSRS available! Activate the script here. Currently free! So enjoy! ✨ Core Features 🎒 Advanced Supply Management Smart Restocking - Automatic Grand Exchange integration Emergency Bailout - Mid-trek banking when supplies run low Stamina Support - Optional stamina potion management with advanced thresholds ⚔️ Combat & Gear Configuration Gear Requirements System - Set equipment for each slot Nail Beast Handling - Choose to fight or evade nail beast encounters Lumberjack Outfit Collection - Automatically loots valuable outfit pieces Combat Gear Restocking - Ensures proper equipment is maintained 💰 Reward & Profit Optimization Reward Preferences - Choose XP Tomes or loot rewards Token Banking - Optional banking for Reward Tokens Tome Usage - Smart XP tome consumption Profit Tracking - Real-time profit tracking 🎨 Professional Interface 🔧 Advanced Settings System Access to comprehensive advanced settings including: 🔄 Mini-Breaking - Configurable micro-breaks for human-like behavior 😴 AFK Simulation - Realistic idle periods with configurable behaviours to emulate real AFK 🌍 World Hopping - Smart world switching based on population/ping 🎯 Stopping Conditions - Runtime limits, level goals, trek counts 📱 Discord Notifications - Real-time progress updates via webhooks 📸 Camera Management - Automatic zoom and rotation control 🎮 Client Options - Display mode, audio settings, and more 🚀 Performance Features ⚡ Reliability & Safety Emergency Teleport - Configurable safety teleports when needed Supplies Validation - Ensures adequate resources before starting Death Recovery - Built-in death handling and recovery Human-like Behavior - Advanced antiban with player profiling 🛡️ Safety & Anti-Ban Features ✅ Advanced Antiban - Player profiling with human-like behavior patterns ✅ Flexible Breaking - Multiple break systems working in harmony ✅ World Hopping - Avoid crowded worlds and high-ping servers ✅ AFK Simulation - Realistic idle periods with random activities ✅ Camera Management - Natural camera movements and zoom levels ✅ Fatigue Emulation - Gradually slower reactions over time 🚀 Getting Started Launch the script Configure Trek Settings - Choose route, difficulty, and rewards Set Up Supplies - Configure food, gear, and restocking options Adjust Safety Settings - Set emergency teleport and combat preferences Fine-tune Advanced Options - Optional: Access 50+ advanced settings Save Your Profile - Quick setup for future sessions Start & Monitor - Watch the live paint overlay track your progress 🎁 Bonus Features Profile System - Save/load multiple configurations Discord Integration - Get notifications on your phone XP Tracking - Visual progress bars for all skills Loot Collection - Automatic pickup of valuable drops

We all bot for our own reasons whether that is for lack of time, lazy, greed, or just a sense of accomplishment...no judgment here. I have Personally botted over 200 accounts (80 of them maxed with infernal) over the last 8years of my life. I have had my fair share of accounts banned which is always devastating but I got to noticing patterns in how Jagex catches players botting off their automated system. Here is the 4 rules I personally bot by to prevent detection and hopefully they will work for you Aswell. Of course these rules apply differently to everyone, there will always be that guy who claims he bots 24/7 and doesn't get caught. That may very well be, its all percent chance and some get caught on their first attempt at botting. First Rule: Reflection Having a consistent schedule that can reflect human nature and habits. I personally only bot maybe 2-4hours at a time then rest the account for and hour or more, depending on the activity and my desperation to hit the next threshold. Not botting during your time zone sleep hours, not many humans that I know of can play games all day and all night 24/7 without sleep of some kind, even the sweatiest among us have to rest at some point even for a few hours. Resting the account for 8 hours or even letting it park for a day can greatly reduce risk of detection. Mixing up the activities for which you bot can make it seem more human... who on their own can sit in motherlode mine for 2 weeks straight? Go do something else for a moment, just to spread your account out. Sometimes just playing the game for yourself and doing some prep work for the next few bot projects, talking to the lovely people of W301, or flexing your favorite fashion scape can help reduce detection. Second Rule: Dumping I cant begin to tell you how many maxed accounts I lost to dumping items and here is what I mean. How Jagex detects bots is by using a series of "Trip Wire Code" or TWC for short. This greatly applies to the Grand Exchange for all accounts use the G.E in some way excluding irons. TWC is laid in everything you do on the G.E from selling to buying, but mainly....selling. Selling all your bot gained resources or expensive drops from world totaling over 50M+ will activate a TWC. This means your account will be scanned next time you log in at random intervals. Thousands of accounts are scanned every hour with this stealth code. The best way to prevent it, is to sell your items in slices. Never exceed that 50M threshold. Last account I maxed non stop from botting and got Infernal cape. I rested the account then botted the Gauntlet and got the "Enhanced weapon Seed" Worth somewhere north of 100m+. I sold it of course on the G.E and caught my Ban the very next day half way through a botting event. (this has happened a total of 11 times with maxed accounts of mine). Big ticket items over 50M plus are best Sold to other players not the G.E, why do you think there are so many players selling High Value items in W301? other than the price being over max cash, some items cant be sold if botted because Soley to do with TWC. Third Rule: No Clans This one seems simple and thats because...it is. Clan chat will have notifications on for every 5-10 levels, rare drops, pets, max level, achievements, and quests completions. This means people will prompt you to respond to their "Gratz" or "where did you get that pet?" or "how long did it take to get that drop?". Not responding to this chat every time your actions ping the chat will quickly make enemies out of friends. I know we all long for the chat of friends and people to play with, but you must reserve that for after your done botting or you could just be soliciting for unnecessary reports on your account witch will get your account scanned if to many players report you. Fourth Rule: No Provoking This rule is very optional, I know how easy it is to verbally flex on people and to verbally attack some player that is running their mouth at your favorite fishing spot. Turns out this may be a bad idea, even if it feels good. Calling people out and creating a scene draws attention to you and your account. People may even like you and want to add you for shutting that loser up, but your never online and if you are..your non responsive...I wonder why. People may even toggle your account and look at your stats with Runelite and see you have 3000 Zulrah kills but no other boss kills, hmm thats no suspicious at all. The point of botting is to progress your account and be Low Key about it. Your stats can easily, reflect bot activity and they have plugins now to help identify bots. This again, will solicit reports to your account that could have easily been avoided. Humans are spiteful and a lot hate that you have progress in a skill they cant manage to train, some people report just because they don't like a player. The point of botting is to avoid detection. I hope these Rule Boundaries help keep your account safe from the fire, of course you are all free to make your own decisions and can choose to keep on how you are currently. I have great admiration for the scripters and this community and want to see us all grow.

Just Tempoross Plays the tempoross mini-game for points, profit and xp View in Store Features Cooks fish Avoids fires Avoids waves Grabs up missing or lost tools Requirements 35 Fishing If you have any suggestions or issues, please contact JustJ#0519 on discord or send a private message. View in Store

Developed by SickBrains and Dentist Store Link ( Click Here ) Recommended: ✔ Attack 70+, Strength 70+ recommended , Ranged 70+, 43+ Prayer Key Features: ✔ Duo support ✔ Fully Customizable ✔ Muling – Automated gold/item transfer for efficiency. ✔ Bonding – Seamless handling of account membership. ✔ Gear Repair – Automatically fixes broken equipment. ✔ Restocking – Keeps supplies replenished for continuous farming. Advanced Anti-Ban System Each bot operates with unique behaviors, preventing patterns that could trigger detection.

Having script trials would give customers self-service to determine if a script fits their needs (think about how much you hate using software that doesn't have some sort of self-service). This improves customer experience and reduces support required for scripters to answer basic questions about script functionality. It would also likely reduce refund requests. Trials should be customizable by the script author, they should be able to choose the duration, or even choose to not offer trials at all. Trials should ideally also be locked behind TRiBot VIP. The trial system on the original repository before the Shopify switch worked great and fit all needs.

CrazyDent Magic Arena The Ultimate Mage Training Arena Script for TRiBot. Purchase it click here Automate the entire Mage Training Arena from level 7 Magic all the way to Infinity rewards. Fully AFK. Zero babysitting. Full MTA Automation Supports all four rooms Telekinetic Theatre Alchemy Room Enchantment Room Graveyard Room The script rotates rooms based on points, fatigue, and reward goals. Progressive Training Automatically unlocks higher level spells Adapts casting strategies as you level Reward progression Bones to Peaches → Wand → Book → Infinity No reconfiguration needed as your account grows. Automated Supply Handling Grand Exchange and Ironman supported Auto buys runes, and teleports Rune pouch support and gear detection Smart banking and full self supply handling Human Like Behavior Seeded fatigue system Micro pauses and reaction delays Account unique casting behavior Long session safety logic No two accounts behave the same.

I vouch for this script...got my diary done in 1 day... I couldnt be more thankful! Bones to peaches FTW

I used it during BETA and it was flawless, finished green log today before actual release so worked out in my favor 😄

Congrats on release!

mixology works great, cheers

Hey, sorry about that. They've done something really weird to the tempoross island in preparation for saling. It's fixed now

Hands down, i aint going no where ❤️. wish the forums were more active but you guys got a GREAT client... ~! Shout out to @Dentist @Ark yall amazing

interesting. i used a mule. bought straight up items like tumeken, scythe from eldorado. used the mule to trade to main. been a month already nothing.

i can add those next month since i am verysick and busy af till the end of this month :(

Hey, it's been a decade since I've played this game. I'm looking to start fresh, hope to relive some of that nostalgia of the old days. With limited time, I figured I can get some robotic assistance.

lite version is fixed, ultimate will be fixed shortly

Buying OSRS gold can have many different applications such as helping speed up account progression, recovering lost gains from getting hacked, or simply stepping your account up to the next leveling buying those unreachable items for those who don't like to raid. Gold is essential to an OSRS account for all those reasons and more and I want to share my 3 personal rules on how to Perm Gold safely and throw off Jagex's Auto clear if your caught buying gold. Rule 1: Blending Buying gold from a gold selling source will usually tell you to meet them somewhere in the world either in F2P or P2P. You have the option to meet somewhere a little more private. If privacy isn't an option then when you go to the trade spot, don't wear your flashy gear especially in F2P. Many accounts draw attention if someone in full Bandos with a fire cape is just Standing there waiting for a mule. If anything, wear nothing or wear some iron armor. Always trade the mule items. like 200 Lobster and some runes. Even advertise for a few minutes before the seller arrives. Yelling, "Selling random junk, I need gold please" This phrase will make some possibly trade you, but when a mule trades you, no one will be the wiser. Rule 2: Realistic Expectations When buying gold for the reason you want, always buy an amount that isn't ridiculous for the trade volume. How many random players trade you and buy your "junk" items for 500M? Its perfectly okay to make a few purchases for 20-50M to keep the trade volume low from Jagex's detection system. Always Buy gold from a trusted source and do research before purchasing. Also consider Alternatives like buying Bonds to satisfy some quick safe gold. The most important part of this rule is that, you still MAY be caught trading gold in some way, meaning we have to Perm the gold with the next rule in this list by hiding the gold Rule 3: Hiding the Gold If or when you get caught buying gold, Jagex has an automated wiping system to take all "Gold Coins" and all "Platinum Tokens" and any bulk items worth a substantial amount. A couple of ways of hiding gold from this detection system is: NMZ Coffer, Tip Jar POH, Kingdom of Misc, Shilo Furnace Coffer, Blast Furnace Coffer, POH Servant's Pouch, LMS Coffer, Looting Bag, and even Deaths Coffer (Wouldn't Recommend) I personally use NMZ coffer and Shilo Village Furnace Coffer. You have a minigame teleport straight to the NMZ coffer for cash with a bank nearby Stashing the bulk of your cash will keep it safe from jagex in the event of a wipe, heck I bet hackers wouldn't even think to look in these as well There may be a few more options with new content releases and changes for hiding gold, just use your best judgment and Never tell anyone you buy gold. Hope these rules can help you safely purchase gold, I know they help me. If you come up with anymore ideas on how to hide gold and Perm it from Jagex, let us know below!

Its my pleasure!

Introduction @Dentist's AIO Account Builder is TriBot’s crown jewel! Over the past three months, I launched three fresh accounts, and this script transformed them into powerhouses, each surpassing 1650+ total level with multiple 99s, including my dream of 99 Construction. From quests to minigames and skilling, this script is a botter’s ultimate weapon. After two months of relentless use, I’m hooked—this script is pure fire! 🔥 Script Thread 🔗 Functionality and Features This script is a versatile beast, handling most OSRS skills and a wide array of quests. Standout features include Questing, Construction, Nightmare Zone (NMZ), Pest Control, Farming, Wintertodt, and Dragon Defender grinding. Questing saves hours of manual grind, while Construction crafts epic POHs. NMZ and Pest Control rack up combat points lightning-fast, and Farming and Wintertodt deliver XP and loot effortlessly. The customizable profile builder is the star, letting you tailor every detail for unique account builds. With so many options, there’s still more for me to explore! Performance AIO Account Builder is a 24/7 workhorse, requiring minimal oversight. I ran it for days, pausing only for game updates or to switch tasks. Its stability kept my three accounts humming, and the antiban system is pure magic—marathon sessions, zero bans. Whether grinding overnight or tweaking goals, AIO performed flawlessly. Usability The interface is a botting command center—complex at first but intuitive with practice. New users should spend an hour exploring its robust options. The profile builder lets you fine-tune gear and tasks, with settings saved in your TriBot folder. Pro tip: use AI like Grok to craft setups in minutes (my NMZ builds were a breeze!). Dentist’s Discord (https://discord.gg/XqjGt45Fqp) is a goldmine of support, making even complex setups approachable. Personal Experience Using AIO Account Builder for two months has been a thrill. The script’s seamless flow made botting a joyride, letting me relax while my accounts soared. Dentist’s Discord community was a lifesaver, with quick tips and fixes from Dentist himself turning me into a confident botter. I’m already planning my next big wins! Suggestions The script is near perfection, but adding more diary support would elevate it further. It currently handles some easy diaries, but expanding this would be a game-changer. Proggies More to come (need to find the screenshots) Rating and Recommendation 11/10! AIO Account Builder is a must-have for new botters, account sellers, or anyone tired of OSRS’s grind. It transforms accounts into high-level legends effortlessly. Dentist's genius and support make this a TriBot masterpiece—jump in and dominate!

Update 2.3 released: fixes a bug where the mould would be set when we have a stored preform, causing the next preform to be run with an incorrect mould adds logic to mould selection which prioritises cumulative points, resulting in more points/xp per hour when you unlock moulds

Large update (2.0) released: - Rewrote timing mechanism and is now utilising the game ticks; resulting in a significantly higher accuracy - Created a new and improved quest framework to be more maintainable - Fixed a number of long standing issues - Added in items! You can now choose to use items instead of bars; this is the most heavily requested feature - Improved cannonballer mode - Added a new paint

Introduction "Just Tempoross" is a script by @JustJ for the Tempoross minigame. This fishing-based activity requires a minimum Fishing level of 35. This opinion piece aims to help newer botters learn more about the script, providing insights to inform their purchase decision. 🔗Just Tempoross Thread How It Works The "Just Tempoross" script automates key tasks in the Tempoross minigame, including: Catching Fish: Automatically catches fish to contribute to subduing Tempoross. Cooking Fish (Optional): Cooks fish if the user chooses, helping to weaken Tempoross and earn points. Extinguishing Fires: Attempts to put out fires to prevent tool loss, but it’s not very efficient, often failing to act quickly or appropriately. Tool Retrieval: Grabs missing tools (e.g., harpoons, ropes, hammers) from crates as needed. Avoiding Waves: Dodges colossal waves to avoid losing items and points. However, the script has notable limitations: Tribot Echo: The script still needs work for it to run like it does on "X". No Dragon Harpoon Special Attack: The script does not utilize the Dragon Harpoon’s special attack, which could boost fishing efficiency. No reward collection: The script currently does not collect rewards it self. Proggies I’ve been using this script for about a week and a half, running it with both cooking fish and fire extinguishing enabled. Starting with a Fishing level in the 50s, I’m now close to hitting 99 Fishing within the next 24 hours, showcasing significant progress. The script has been run for multiple 24-hour sessions, with the current session exceeding 60 hours, demonstrating its ability to handle long botting periods reliably. However, the experience per hour is a notable drawback, capping at 62k Fishing XP per hour, which is lower than other methods. In terms of rewards, this mini game gives out good rewards and will be helpful to anyone looking to get the pet. Author’s Responsiveness JustJ can be reached through the Tribot Discord or via private messages on the Tribot forums. I’ve contacted JustJ to provide feedback on issues such as adding Dragon Harpoon special attack support. I’m currently awaiting their response and further interaction to fairly assess their responsiveness. 7/24/25: Author does not respond much so warning to all in the future. Script works as of now but this could change. It also does not work great on Echo currently. Happy to update if I get any word back. 🙂 Price Evaluation Priced at $3.99, making it affordable compared to other premium scripts ($5–$20). I consider the price a steal, as the script runs good enough to automate the Tempoross minigame effectively, supporting long sessions (up to 60+ hours) and delivering significant Fishing level gains. Ironman Support I have not yet tested the script on an Ironman account, but I believe it should be capable of supporting Ironman players, as the Tempoross minigame is self-sufficient and does not require trading or external resources. The script’s ability to catch fish, retrieve tools, and navigate the minigame should align with Ironman restrictions. I plan to test this in the near future to confirm its compatibility and effectiveness for Ironman accounts, which could make it particularly valuable for players seeking to earn rewards like the Fish Barrel Rating I rate the "Just Tempoross" script 8.5/10, primarily due to its ease in helping me reach 99 Fishing and its reliability in running for long hours (up to 60+ hour sessions). If JustJ addresses concerns in the coming weeks, such as adding support for Tribot Echo or improving fire handling and Dragon Harpoon special attack integration, the rating could increase further.

This is absolutely wild to see, y'all are doing some fantastic work over here 🙂

Update The project is coming along well. Scripts are now generally runnable and the API is nearly fully implemented. Even repo scripts are capable of starting up. It seems that scripts will naturally be fully compatible with Echo, but we'll see once we start really testing. As of now, we're way ahead of schedule. It's possible that we'll have a beta by early July. Sneak peek:

Project Echo is now in open beta for Premium Tribot subscribers. You can find it as a tab on the latest version of the Tribot Launcher. Please be aware that this project is still in beta. We'll be collecting bug reports in the Discord. Enjoy!

@Forgegp Discord server links are not allowed in the selling section. If you wish to open a shop on tribot, you must be a premium subscriber and use the shop section. You may sell individual accounts in this section, but cannot be used to advertise your shop/business/etc.

have run it for a few hours and cannot complain!! loving the all in 1 package!!

could be keen to give this one some feedback soon will be the next purchase. cheers

added pushed update

This is a Tribot error. As stated in the error all you can do is try to terminate the instance as instructed or wait about 15 minutes for the instance to expire. I have no control over how Tribot handles instances

This script can't complete prep in corrupted gauntlet. I ran it for around an hour off and on. The 2 that it did complete, I had to do the prep. Does alright at the boss but prep is VERY slow and clunky. Is there a way to get a refund on this??

this is yes if u set the farming task priority to max like 2000 it will do it as soon as possible for now for GOTE it only do it with tridents i will change how that work soon to make it support normal runes etc

WOW wicked cool release thats dope. Elon youve been killing the game lately

Yup

Bulletproof script. I’ve ran this on a maxe iron with a previous tempt ban. Ran it 24/7 and have gotten 40 purples, duplicates of everything but unfortunately no shadow. Going legit from here, but thank you it was very enjoyable watching the bot rinse level 5 Zebaks and waking up to purples. Shoutout to the boys in the discord. Highly recommend this script.

Scripts will be required to not rely on RL plugins to function, as they must all continue to work with Tribot X. If you're developing locally, you'll just have to remember to setup the plugins for yourself.

This script is very good, ran it on 2 iron man accounts for 100's of kc for 20+ hour stretches without a ban over about a month. No bans Got the shadow on my accounts 🙂

As one can never simply quit RS, I think I am going to start a fresh account and track the progress in videos I'll post on forums and discord. Wish me best of luck, going to start with your AIO script as I have had great gains with your other scripts in the past. 🙂

Absolute amazing script with technology that seems to be bombproof. Amazing.

i purchased this, got 72-99 herb zero issues, i am however curious on banrate.

I should be able to get it added tomorrow. I'll message here again when it is added.

I recommend joining my discord everyone is helping each other with this in general chat my discord link: https://discord.gg/fRgDwkb (Theres some preset gears already made up as well you can try in the GUI as well or use them as a guide then make your own with the Get In Game Gear Button)

Incredible script — it’s wild how well it works. With a bit of RNG, you could be a billionaire within 24 hours, haha. Seriously impressive. Definitely a game-changer.

Been running 405 invos in ~45 minutes with this consistently. Highly recommend, this thing prints purples.

Hey ya'll this will likely be a long post so hang in there! I have been playing around with behavior trees and state machines over the past few days and have formed some ideas around how to combine them to have really nice clear and clean logical structure. I assume you have read the primer Nullable has written and have a cursory understanding of behaviorTrees. This post is mainly to lay out my ideas, and is not a definitive "this is how you should do things" by any means. It is simply another approach and tool in your toolbox! Let's Talk Behavior Trees Behavior trees are super cool. They allow you to have resilient and reactive logic that is composable and inherently good at dealing with failed conditions. Nullable has a fantastic primer on it (READ THE LINKED ARTICLE) here. I highly recommend you go check it out. A simple example Behavior Tree for Fighting & Banking for example val tree = behaviorTree { repeatUntil(BehaviorTreeStatus.KILL) { // High-level selector to decide between banking or fighting selector { // Banking Sequence sequence { condition { Inventory.isFull() || !Inventory.hasFood() } perform { bankNode() } } // Fighting Sequence sequence { // Eating Subtree selector { condition { isHealthAboveThreshold() } perform { eatFood() } } // Looting Subtree selector { condition { isNoLootAvailable() } perform { lootItems() } } // Fighting Action perform { performFighting() } } } } } tree.tick() // Executes the tree This nice and simple structure will reliably go between Banking and Fighting with eating and looting. Now what do we need to do if we want to add a 3rd thing we want our bot to handle. Let's say for example that we want to generate our own food. To do that we need to fish and then cook what we fished. selector { // Fishing Sequence: Fish until you have X raw fish sequence { condition { !isFishingComplete } // Only fish if fishing is not complete, otherwise we will keep going into this sequence after cooking our fish condition { getRawFishCount() < targetRawFishCount } // Check if raw fish count is less than the target perform { performFishing() } // Mark that fishing is complete for now } // Cooking Sequence: Cook until no raw fish is left sequence { condition { isFishingComplete } // Only cook if fishing is complete condition { hasRawFishInInventory() } // Ensure there is raw fish to cook perform { performCooking() } perform { updateFishingCompleteFlag() } // Update the flag when done cooking } // Fighting Sequence: Do our existing tree fightAndBankNode() } The problem with this approach is there is a bunch of tedium in storing and tracking state around "have we fished". That honestly kind of sucks, what are a couple of ways to solve this? Way #1 Repeat Until A simple way to solve this is to make sure our fishing and cooking sequences repeat until they meet a threshold. The downside is that we lose a little bit of our reactivity in the behaviorTree since we are locked in until we meet that condition without specifically breaking out of it. So our sequences now look like sequence { repeatUntil { getRawFishCount() >= targetRawFishCount } { condition { getRawFishCount() < targetRawFishCount } // Check if raw fish count is less than the target perform { performFishing() } // Mark that fishing is complete for now } } and sequence { repeatUntil { getRawFishCount() <= 0 } { condition { hasRawFishInInventory() } // Ensure there is raw fish to cook perform { performCooking() } perform { updateFishingCompleteFlag() } // Update the flag when done cooking } } Way #2 What about State Machines? State Machine Primer In case you need a refresher or haven't yet learned about what state machines are, here is a brief primer on them i highly recommend you read! The code Another way we could go about dealing with this is by using a State Machine to define our top level state and have each state's action be a behaviorTree to robustly execute that state. val fishingState = createState { tree { behaviorTree { performFishing() } } } val cookingState = createState { tree { behaviorTree { performCooking() } } } val fightingState = createState { tree { behaviorTree { performFighting() } } } createStateMachine { initialState = fishingState fishingState on { getRawFishCount() >= targetRawFishCount } to cookingState cookingState on { !hasRawFishInInventory() } to fightingState fightingState on { Inventory.getFoodCount() <= minimumFoodThreshold } to fishingState } The big benefit here is that we can completely move all the "what should we do" code from the "how should we do it". It should allow us to add more high level behaviors without mucking up our behaviorTrees with a bunch of transition logic, thus keeping them smaller, focused, and more efficient. If this interests you, I wrote the framework for state machines that includes transitions, priorities, and global transitions here. I also re-implemented most of the behaviorTree framework so I could visualize it! All the code is in the framework module in that repository Viz Example Conclusion if you made it this far, thank you for reading! I hope I generated some thoughts while reading. This is the result of only around a week of tinkering around, so there is definitely a lot for me to learn in this area. I would love to hear any of ya'lls thoughts on shortcomings of my approach or other ways you would tackle this!

People will comment when they have issues, not so much when they don't. Here's a proggie from earlier today: Tribot has a refund policy - I suggest having a read through it if you have any questions. https://tribot.org/refund-policy

I'm sorry about your poor experience with ArceuusTabMaker, I offered you a full refund due to the fundamental changes to the script required to cater to your needs and the fact that I have been thinking about taking the script down so wasn't looking to spend significant time on one of my worst performing scripts. Unfortunately due to reasons outside of my control it has taken a little longer than normal for the refund to be issued to you. You were banned after having several (4) tantrums in my server, but don't worry - this does not mean you won't be able to get your refund. I won't keep having this discussion with you, especially on an unrelated thread. Thank you for your understanding.