The Webwalker is clicking in wrong places, then it needs to walk back to where it was. This is very inefficient and I can't understand why it does this. Is there a fix to this? A fix to the web walker backing out on itself and keep going the wrong direction?

 

Here is a common example of the WebWalker running outside Lumbridge Castle.

It keeps clicking outside the building.

 

 

After some walking back and forth (very bot-like) it finally walks inside and reaches the stairs.

 

Edited June 26, 20187 yr by RuneCooper

I’ve made a comment about the in the scripter chat, and a lot of others were experiencing this as well. Hopefully the Devs will look at this.

 

Also, you should remake this post in the Bug reports section

Edited June 26, 20187 yr by ProjectPact

someone is making/using a 7qp script it seems

42 minutes ago, ProjectPact said:

I’ve made a comment about the in the scripter chat, and a lot of others were experiencing this as well. Hopefully the Devs will look at this.

 

Also, you should remake this post in the Bug reports section

Thank you

 

This is good to know that it's  a WebWalking error. Hopefully gets fixed soon. Kinda bot-like the way it goes the wrong way and walks back on itself.

I've got the same problem, hopefully it gets fixed but if not I just use my own pathing for now. 

I'd expect that the issue is the (3?) tile randomisation that's used when walking with webwalking.

Figure I'd give this topic a bump. I'm facing this same issue, nearly 2.5 years later, when webwalking to Lumby Upper bank. 

Any good fixes?

Extremely botlike behaviour.

 

Had similar issues near edgeville furnace, and some other spots.