------ READ FIRST ------
Setup Instructions
- Equip desired gear and withdraw desired inventory
- Press "Load Setup", then "Save Setup"
- Select:
– POH Restoration method
– Teleport to bank method
– Combat method
– Minimum resources - Choose whether to enable Direct Input
– If DI is disabled: Slayer Staff is recommended - Start the bot at your chosen banking location for best results
– If starting elsewhere, ensure house teleports are in inventory or standing near a bank
– Starting at Ungael with full gear + enough resources will make the bot begin killing Vorkath immediately; otherwise it banks first
– If using Quiver, equip Quiver and bolts before starting
Requirements
• Standard spellbook
• Player-owned house with an Altar or Ornate/Fancy Pool
Teleports & Spells:
• Bring House Teleport tabs, Runes or Cons. cape
• Your setup must include Crumble Undead runes
– Runes may be in inventory or rune pouch
– The bot does not validate these runes
Bot Behavior Overview
• Before each fight the bot validates Minimum Resources.
– If insufficient, it will bank.
– If food or prayer runs out mid-fight, it teleports out.
• Supports bolt swapping:
– Ruby Dragon Bolts (e) ↔ Diamond Dragon Bolts (e)
– Ruby Bolts (e) ↔ Diamond Bolts (e)
• If using a Dizana’s Quiver, bolts must be equipped before starting. Bot does not equip bolts into the quiver slot when withdrawing equipment from bank.
– Depending on chosen Spec weapon it will either spec at the start of the fight or when it has enough special attack
Deaths & DI Behavior:
• NEW: 1.1.1 Added death walking, the bot will attempt to withdraw House tabs or runes and fetch items
• Bot can be run without DI, but this is not recommended
– Without DI, the bot will eventually die
• With DI enabled the bot should not die, but lag or poor connection may still cause deaths
Supported Consumables
• Shark
• Manta Ray
• Dark Crab
• Tuna Potato
• Cooked Karambwan
• Sea Turtle
• Anglerfish
• Cooked Dashing Kebbit
Potions:
• All antifire types
• All antivenom types
• Antipoison and Superantipoison
• Prayer potions
• Super restores
Ranged Potions:
• Ranging Potion
• Divine Ranging Potion
• Bastion Potion
• Divine Bastion Potion
Melee Potions:
• Super Combat Potion
• Divine Super Combat
• Super Strength
• Super Attack
Ranged Weapons:
• Toxic Blowpipe
• Dragon Hunter Crossbow
• Armadyl Crossbow
• Dragon Crossbow
• Rune Crossbow
Melee Weapons:
• All melee weapons are supported
The bot DOES NOT validate:
• Runes or Rune pouch contents
• Dizana’s quiver bolts
Additional Notes:
• If the bank runs out of required resources, the bot soft stops for 5 minutes and then stops entirely
• Bot automatically sets quick prayers and auto-cast for Slayer Staff
• Pausing and Playing will effectively reset the bot and make it start from fighting or banking depending on the location of the player and resources. Do not attempt to manually move the bot around, it will not alter current state.
Please report any bugs or issues you might run into,
either by DM, discussion or in my Discord.
Join discord here
Change Log:
1.1.7
- Added a slow internet mode (could help in acid phase)
- Enhanced Special attack and weapon detection systems,
increased logging to catch any future issues faster
1.1.5
- Fixed a potential issue where the main weapon ID could get mutated during runtime
1.1.4
- Fixed zombified spawn handling when not using slayer's staff
- Added more guarding to death walking
1.1.3
- Fixed an issue where slow connection would break melee woox walk
- Fight mechanic improvements
1.1.2
- Fixed an issue where setup couldn't be loaded when bot was paused
- Fixed an issue where pausing and resuming didn't refresh as intended
- Added support for Slayer's staff (e)
- Added validation to check that Slayer's staff isn't accidentally saved as main weapon
1.1.1
- Added deathwalking
- Fixed Cons. cape teleport
- Fixed Lunar Isle banking getting stuck and other banking issues
- Tightened Fireball handling
- Introduced an option to disable woox walk
- Added PlayerSense to delay profiles
- Other antiban improvements
- Other minor fixes

Could you send logs from the runs where it got stuck banking? I haven't heard about this issue or experienced it myself, I would like to fix it if there is a bug.