How to use:
- start the bot near shipwreck(s), the bot will not currently navigate the boat at all
- have a salvaging hook on your boat
- select desired options and click "Run"
- Hooks salvage from nearby shipwrecks, with intelligent prioritization of hooks and crewmembers
- Drops salvage by default, but also supports the on-boat salvage sorting facility (if available)
- Optional: worldhopping to find fresh salvage
- Optional: ability to keep or drop stackable loot, if sorting salvage on boat
- Optional: ability to alch loot, if sorting salvage on boat
- Optional: crewmember support on a second hook
- Optional: supports Crystal extractor for extra XP
- Optional: 1.5 tick tick manipulation on double hooks, using teak logs or guam tar
- for teak logs: requires teak logs + knife + 46 fletching. Bot will automatically drop extras to operate properly
- for guam: requires guam leaf + swamp tar + mortar and pestle. Bot will automatically clean extra grimy guams if it messes up ever
- Optional: kitten support! Bot will feed kitten (Raw karambwanji), and pet it to keep it happy
- Optional: Seed box & herb sack support
- Optional: Supports filling Soul bearer if in inventory
- Saves settings from last session, even when you close Runemate. Jump right back in next time!
- Customizable break handler, to log out for a little while every X minutes, and the option to hop to a random world after break.
- Customizable stopping handler: to stop the bot after a selected amount of time.
- Customizable Fatigue handler: to slow down interactions over time & reduce fatigue with idling/breaks
- Intelligent delays between actions.
- Progress log with a bunch of info.
- My own custom, robust traversal system written from the ground up. Doesn't rely on the Runemate "web" to work!
Bot Settings:



Just to mention, are you sure it actually got stuck that long? As the bot has two different AFK failsafes: lack of clicks from the bot & lack of XP gained. It might have still been clicking, and even gaining XP from crewmates, but once the cargo filled it should have stopped gaining XP and timed out shortly after... So it might not have been stuck that long.
Either way, again, sorry about that and this issue should be entirely fixed now.