Token

F2P mode doesn't use any teleports at all so it will not buy/withdraw runes.

There's currently a bug in OSBot's webwalker where it cannot leave the draynor manor so that may be possible. I did implement a temporary fix (which only works when f2p mode is disabled as I previously stated) but I'll check if there's something wrong with that. Could you be more specific? I added lots of debug messages in the logger which tell you the exact context. Plague City, Priest in Peril, Ernest the Chicken and Animal Magnetism are the latest quests I added so there might be some minor issues with those that I'm going to address in the next update.

Authed It is a beta. The point of this is to find bugs in order to fix them. As I have told many other beta testers you are supposed to select a food before adding quests. That error happens when you don't have any food selected. In the instructions it says you need to enable f2p mode before adding quests. The way I designed this script was being able to run certain quests on f2p mode while others without f2p mode and some with a certain food and that's why I stated in instructions you have to select food, gear preset and if you want f2p mode before adding the quest. But since most errors beta testers found so far (which were not errors) were related to not using the gui like I said in the instructions I'll remove the possiblitiy of restraining f2p mode and food to individual quests and I'll make it a global setting. Other than having problems starting the script, most people managed to run all quests but I'll take a look at those particular cases.

Authed

Authed

Authed

Can you post an image of the ge tab + logger when its sitting there doing nothing? Added some instructive gif videos on the first post if anyone is having trouble starting the script.

You already have it since I authed you, just refresh your scripts.

Done

The banking process is repeated when it fails to withdraw all items (because OSBot banking is quite unstable and I'll have to make it failsafe). The messages about failing to withdraw an item are displayed in the logger though. What was the quest you tried?

Was that attempted on a F2P world? Did you let the script buy items? From the logger it results that you stopped the script while it was attempting to buy items.

Authed

Authed, please let me know what bugs you find so I can fix them

Script is up let me know if you wanna test it (got too many pms even from 1 month ago and I might have missed them when authing).

#WAITINGFORALEK I pushed an update which will either fix it or give more info about the error but gotta wait for it to be uploaded :tears:

It got to the SDN few hours ago, but there might be an error which I believe is caused by obfuscation as it only happens on the SDN, the local version works fine. Should be fixed soon.

Bid noted thanks PS: Leading

Bid noted thanks

I doubt the WebWalker was updated since there hasn't been an OSBot update but posting relevant code may help in getting the issue fixed.

Gotta love the states vs tasks fight. Big boys write everything in onLoop() :ph34r: :ph34r: :ph34r:

I'm in a relationship with someone and they don't even know about it. Could it be worse? :ph34r:

You cannot implement a behaviour for each individual random event using the OSBot random solving api (as in actual runescape random events, not the login screen and other stuff in there). RandomEvent is an enum having no fields for each random event, only the DISMISS_RANDOM field which is used for every event. Each event has a RandomBehaviourHook that describes how the bot will behave if it should activate. So you may be able to use the OSBot random event api to write your own behaviour that applies to all random events but not to an individual one. If you insist to create your own behaviour for every random event in runescape then you can proceed to unregistering the hook for DISMISS_RANDOM so the bot will no longer react to randoms. Now you can define a custom behaviour when a given random is present (context detected using objects/npcs) and you may write your solvers just like any other script functionalities. Finally, create a new RandomBehaviourHook with the solving code and register it using RandomExecutor for the DISMISS_RANDOM field of RandomEvent.

SDN Manager just changed so might take some time :tears:

Price is not yet decided but I'm pretty sure I'm going to go for a low renewal fee, that way people who only wish to complete quests on like 5 accounts can simply cancel the renewal if they are not that much into botting and won't create new accounts in the near future. The script itself was designed for people who want to make their bots much less detectable though, as jagex is a lot less likely to target accounts which have lots of quests and many levels in random skills (from quest rewards) with their bot detection, hence it will aquire every single required item and can do all quests with only 1 run, allowing for quick creation of accounts with lots of quests completed. It can also be used to give bots access to various perks such as being able to smith cannonballs, wearing ava's accumulator or (soon) mithril gloves for pures.