Khaleesi

🍳 Khal Cooking (All-in-One) 🍳 🔥 OverviewKhal Cooking is a fully automated, all-in-one cooking script that takes care of everything from basic fish to advanced cooking content. Designed for efficiency, it handles multiple cooking locations, supports wines, and ensures your account cooks with minimal supervision. ⚙️ Features🐟 Cooks All Fish/Meats/PiesAutomatically cooks all types of fish, meats and pies Counts burnt fish and successfully cooked items Smart location selection for efficiency 📍 Multiple Cooking LocationsSupports all major cooking ranges and fires Efficient pathing and banking for high-level training Missing a spot? Request it! 🍷 Wines SupportFully supports Jug of Wine Supports Wine of Zamorak Handles all wine-making steps automatically 🚀 Why Choose Khal Cooking?Fully automated all-in-one solution Works for AFK or active play Efficiently handles high-level cooking content Smart inventory & banking logic 📌 Planned / Future UpdatesGUI improvements for task customization Additional wine types and cooking locations Efficiency & anti-ban improvements 💬 Feedback & RequestsHave suggestions, bug reports, or location requests? Drop them below — they help shape future updates.

🌊 Khal Tempoross 🌊 🔥 OverviewKhal Tempoross is a fully automated script for the Tempoross minigame, designed to maximize loot, efficiency, and safety. It handles all key mechanics including fishing, totem repair, and dodging hazards, while offering AFK-friendly options and world hopping for optimal rewards. ⚙️ Features🐟 Fishing & CookingCook fish option Supports barehand fishing and harpoon special usage 🏗️ Totem & Fire ManagementRepair totems option Douses fires automatically to protect your ship/team ⚡ Safety & EfficiencyDodges lightning and waves Optional skip games when not enough players Hop worlds for better rewards and faster queueing 🎁 Loot & TrackingLoots rewards pool automatically Tracks loot obtained in loot tracker 🚀 Why Choose Khal Tempoross?Fully automated all-in-one minigame solution Optimized for loot, efficiency, and safety AFK-friendly with smart hazard handling Handles advanced mechanics like totem repair and harpoon special 📌 Planned / Future UpdatesImproved hazard avoidance algorithms 💬 Feedback & RequestsHave suggestions, bug reports, or minigame tips? Drop them below — they help shape future updates.

❄️ Khal Wintertodt ❄️ 🔥 OverviewKhal Wintertodt is a fully automated script designed for the Wintertodt minigame, optimized for maximum Firemaking XP, loot, and safety. The script focuses purely on efficiency, survival, and rewards while keeping you AFK-friendly. ⚙️ Features🔥 Firemaking & FletchingPre-levels Firemaking until 50+ for minigame entry Fletches logs, repairs and relights braziers Lights braziers at the start for smooth minigame entry ❄️ Safety & SurvivalDodges snowfalls and breaking braziers Option for safe chop positions Uses Rejuvenation potions to heal — no food required 🌍 Efficiency & BankingHop worlds to maximize participation and rewards Option to bank gear at start for full preparedness 🎁 Loot & TrackingLoots Reward Wagon automatically Tracks valuable drops and rewards for easy monitoring 🚀 Why Choose Khal Wintertodt?Fully automated, all-in-one minigame script AFK-friendly with full healing & safety support Optimized for maximum XP and loot Handles all Wintertodt mechanics efficiently 📌 Planned / Future UpdatesAdvanced anti-ban improvements 💬 Feedback & RequestsHave suggestions, bug reports, or minigame tips? Drop them below — they help shape future updates.

🏹 Khal Fletching (All-in-One) 🏹 🔥 OverviewKhal Fletching is a fully automated, all-in-one fletching script that handles everything from bows to bolts and darts, providing maximum XP rates with minimal supervision. Designed for speed and efficiency, it supports multiple fletching options and includes advanced mechanics like turbo click mode. ⚙️ Features🏹 Bow FletchingCut and string all types of bows Smart task handling for optimized XP 🏹 Arrow, Bolt & Dart FletchingFletches all types of arrows Fletches all types of bolts Fletches all types of darts ⚡ Turbo Click ModeTurbo click mode for insane XP rates Optimized for AFK and active playstyles Safe and fast automation 🚀 Why Choose Khal Fletching?Fully automated all-in-one fletching solution Works for both AFK and active players Smart task system for maximum XP Turbo click mode for record-level efficiency 📌 Planned / Future UpdatesGUI enhancements for task customization Additional fletching items support Improved turbo click algorithms

To keep a long story short, models are cached and some models could have a strange area due to it's animation. How to fix these: Custom bounding boxes. Example issue: Let's create a custom bounding box for this specific object Go to debug -> Tools -> Bounding box -> Show -> Select entity typ and enter ID or Name You can match the object by change offets and size to ge this result: How to use: Copy the values to the clipboard for QOL reasons interact with an object and set the bounding box in the interact args, this will take priority over the model if let Some(object) = objects_find_closest_by_name(OBJECTS_INTERACTABLE_OBJECT_FLAG, "Retort"){ if object.interact_args(InteractArgs::default().set_bounding_box((0,0,0),(95,55,150)), "Concentrate-potion"){ utils_sleep_conditional(5000, 250, || local_player_is_animating()); } }

The store was closed as the current products won't be working anymore sadly.

it uses whatever is the shortest path, from where to where are you trying to traverse and how do your inventory/equipment look?

Requirements: OSBot VIP C++ rank or higher is required to run local scripts. Rust project setup I will be using Rustrover as IDE, feel free to use VSCode or whatever you feel comfortable with. So make sure you have rustrover installed (Free license): https://www.jetbrains.com/rust/ 1. Start a new project 2. Give the project a proper name ("test_setup" for my case) Should be your scripters name No capital letters No spaces, replace spaces with an underscore 3. Toolchain = stable-x86_64-pc-windows-msvc 4. Project template = Library Result should be something like this: 5. Remove the "src" folder 6. Create a new folder with your script name (test_script) No capital letters No spaces, replace spaces with an underscore 6.1 Create a new folder called “src” in this folder 6.1.1. Create a new Rust file called “lib” inside the script “src” folder 6.2 Create a “Cargo.toml” file inside the script folder (or copy paste it from below) 7. Open up the Root “Cargo.toml” file (Bottom one in the image) 7.1 Empty the file and insert this code block: [workspace] members = [ "test_script"]8. Open up the scripts “Cargo.toml” file (the one under test_script) 8.1 Insert this code block: [package] name = "test_script" version = "0.1.0" edition = "2021" [dependencies] osbot_api = { git = "https://github.com/OSBotNative/stub_api", features = ["script"] } [lib] crate-type = ["cdylib"] 8.2 Refresh your Cargo, this should look like this (If this is not the case remove all in there and add your project, “test_setup” in this case and press refresh) 9. Adding a skeleton to your script, Open up the “lib.rs” file in your scripts folder and add this code block: use osbot_api::api::script::script::Script; use osbot_api::api::script::script_metadata::{ScriptCategory, ScriptMetadata}; use osbot_api::log::info; #[no_mangle] pub extern "C" fn metadata() -> ScriptMetadata { ScriptMetadata { name: "Test Script".to_string(), author: "Khaleesi".to_string(), version: 1.00, info: "Test script - My First Script".to_string(), logo: "https://i.imgur.com/QkTUq3l.png".to_string(), category: ScriptCategory::Other, } } #[osbot_api::script_exports] pub struct KhalTest {} impl Script for KhalTest { //Constructor in case you want to initialize some variables defined in the struct fn new() -> Self { Self {} } //Method called on script start fn on_start(&mut self, params: Option<String>) { info!("Starting {} V{:.2} - {}", metadata().name, metadata().version, metadata().author); } //main script loop fn on_loop(&mut self) -> i32 { info!("Running {}", metadata().name); 50 } //Method called on script start fn on_stop(&mut self) { info!("Stopping {}", metadata().name); } //Required for Message listener, you can define what messageTypes to listen for fn get_chat_message_types(&self) -> Vec<ChatMessageType> { vec![ChatMessageType::Game, ChatMessageType::Spam] } //Message listener if needed fn on_chat_message(&mut self, chat_message_type: ChatMessageType, chat_message: &RSChatMessage) { } }10. Using dependencies between your scripts to minimize code duplication 10.1 Create a new folder on root level "script_dependencies" (No other names allowed) 10.2 Create a "src" and "Cargo.toml" file just like your script setup 11.3 Open up the "Cargo.toml" and add this code block: [package] name = "script_dependencies" version = "0.1.0" edition = "2021" [dependencies] osbot_api = { git = "https://github.com/OSBotNative/stub_api", features = ["script"] } 11.4 Open up the Root level "Cargo.toml" and add "script_dependencies" to the members block: [workspace] members = [ "test_script", "script_dependencies" ]12 How to use the dependencies folder 12.1 create some folder to group certain helper functions, utils, ... 12.2 Rust is using a module system (kind of like maven) so you will have to some mod.rs files inside those folder to expose your modules 12.3 Inside the mod.rs files, expose your helper files inside that folder pub mod interation_utils; 12.4 Update the lib.rs file inside the "script_dependencies" folder to expose your modules you just created pub mod interaction; pub mod inventory; pub mod utils; 12.5 Update scripts "Cargo.toml" to use the dependencies project Add the script_dependencies under [dependencies] together with the osbot_api [package] name = "test_script" version = "0.1.0" edition = "2021" [dependencies] osbot_api = { git = "https://github.com/OSBotNative/stub_api", features = ["script"] } script_dependencies = { path = "../script_dependencies" } [lib] crate-type = ["cdylib"] 13. so if you want to start creating a new script, create a folder just like before Create scripts folder. src folder with lib.rs and Cargo.toml file Add the script module to [workspace] Cargo.toml file 14. Building your script, this will be done on a build server that runs in the cloud: If you do not have an builder account yet, make a request here: https://osbot.org/forum/forum/253-builder-access-requests/ 14.1 The whoe process explained below can be automated by reading this: https://osbot.org/forum/topic/203533-native-automated-compiler/ 14.2 To be able to build your script or scripts we will need a zip file of your project, target folder excluded! There is a maximum set on the server so it should fail automatically when you try this, but don't! What to include: every script folder + script_dependecies folder + cargo.toml (the top layer one) 14.3 go to the script builder website and login with your account. 14.4 Here you will be able to upload the zip file you just created, after uploading press the rebuild button and it should start rebuilding. 14.5 You can also see how busy the server is by check the Queue. 14.6 While the build is running you can click on the Logs button to check what's going on. 14.7 Refresh the page, your script will show up soon if your build was successfull, else you can check the logs why the build failed 14.8 After that just download your script or all of them with the download all button 14.9 Places the dll files in your osbot/scripts folder and it should be visible inside the client after a refresh

Enjoy!

Just equip it ...

Enjoy!!

Released

Enjoy!

Nope, just ran a few accs and works fine for me. idk what you mean by "Crash" but that would mean the client shuts down, so please provide some proper explanation or screenshots on discord about the problem you are having. no, you need a way to repair them else it's not worth using pouches

Legend

Enjoy! Enjoy!!

Pretty sure hopping is disabled in the script due to being a minigame and being instanced nowadays

Enjoy!

No sorry, I could take a look to add it!

No, won't be added either