Molly

When this happens, is the bag already full? Does it successfully deposit the loot then get stuck afterwards? Edit: I may have found what's causing this, I pushed an update which is live in v2.0, let me know if the problem persists as I'm not 100% sure what the cause of the issue is.

Just posting to confirm you two both received trials.

Yes

I'll rewrite the method for handling that this Saturday. It should not be doing this as there is a check to make sure they are stunned before pickpocketing. Sure, you have one.

I just removed it, should be live next SDN update. Anti-profiling is an anti-ban feature I have implemented into all my scripts, it randomly cycles sleep timers in the script to simulate a player becoming more focused for x amount of time, or less focused. For example rather than ALWAYS performing a certain action after sleeping for say 300-700ms the window of sleep time will vary based on the currently loaded "profile", which is changed every so often. You are free to disable this feature on the gui. Disabling it will lower the sleep times in the script, making the script perform more efficiently, but it will also look more bot-like.

You both have trials. Authed you another trial, pushing an update now to fix the issue with the pots, as far as the second issue I wasn't able to replicate it, the bot worked fine for me. The update will be live in v8.3.

That won't affect CPU usage, I have it intentionally spamming the logger so I can debug looting bag if there is an issue. The only time looting bag will be used is when it isn't in combat, this means the chaos druids must not be aggressive, this takes roughly 15 minutes of being at the druids.

Like the OP for a trial.

Like the OP for a trial if you guys haven't already, pro I just authed you one manually.

Did this just happen once? There is no part of the code that calls for the bot to deposit gear. This might have been caused by lag and the bot accidentally clicking the deposit worn items button.

You probably don't have one of the required items, post what the logger says.

Pushed a fix.

This is web walking related. The dev for web walking posted today that many issues will be addressed shortly, this will hopefully be one of them. If you use falador teleport tabs this issue will not arise and your exp/profit will increase as well.

That's a great suggestion! Thank you, I really appreciate it.

Like the OP for a trial.

Happy to see that, you got 99 with this script? You have a trial now.

Spoke with this user the day he posted via PM, as he also messaged me. I told him what the issue was but he never responded, I assume that means the solution worked for him. Just posting now for clarity as it doesn't look good his post being the last on this thread with no reply.

Not really. It will teleport if it's below the hp to eat and does not have food, it will also regear and head back to Edge if it does die. The problem with anti-pk support is there's no real proper way of adding it from what I can tell. What I would need to do is add a check to see if a player is interacting with you, and if true then you teleport away. The issue with that is if a player clicks you and selects "follow" that check will throw true and will cause you to teleport away. I feel this could not only cause issues with botting at Edgeville becoming inefficient but it could also lead to more bans. Another player simply following you and you teleport away looks very bot-like whereas a pker killing you, likely fairly quickly, does not.

Those are both web walking related. The issue with the wilderness warning can be resolved by manually entering and exiting the wilderness a bit and then the interface will have an option to permanently disable it. I'll see what I can do as far as adding custom behavior into the web walker to solve these issues.

Reverted to old walking method until I have some time to write a better work around for using the alternate route in Taverly dungeon. The walkPath method seems to perform inconsistently so I'll write my own.

Like the OP for a trial guys.

They're being displayed correctly on my end. Sure, just gave you one.

Just gave you a trial.

Added a work around for Taverly dungeon walking, should now take an alternate route. This will be live in v1.7, pushing now.

Yes. The issue is fixed in v1.6, which I have pushed. It does not look like the SDN has been updated yet, that however is not within my control, we just have to wait for the SDN manager to push updates. Addressed above.