1. OSBot Version (do NOT put "current version", be specific)

version osbot 2.4.147

2. A description of the issue. Include relevant logs.

Multiple issues

Users are reporting that the webwalker has been failing and leaving them idle at different areas. 

1) Missclicks due to async cameraevent + minimap destination clicks.

2)  Fatal cycle errors at certain locations
 

3. Are you receiving any errors in the client canvas or the logger? 

Cycle errors cause errors @ falador crumbling wall. making it run to different areas of falador.

[INFO][Bot #1][12/03 06:34:34 PM]: WebWalkingEvent; Fatal error! Cycles threshold reached on Walk => [x=2946, y=3369, z=0]

4. How can you replicate the issue?

getWalking().webWalk();

5. Has this issue persisted through multiple versions? If so, how far back?

Not that I know of.

 

Note: I will try to gather more information after finals. If anyone else has more information on the topic please post below.

I really need a bit more information to go off of. Where exactly they got stuck at and where they were going so I can test myself. Thanks for the report, I hope we can get more detailed information specific to this problem.

Wanna add something up to this problem. I didn't notice any of the issues he talked about but chartering boats at for example Catherby is also not working. It opens the charter interface and does nothing.

Edited December 8, 20178 yr by The Undefeated

I also have the same thing as well but very rarely. If it does happen it happens when the bot misclicks the stairs and thinks it has gone up. If I click the stairs manually to go up them it continues on perfectly, if not it gets stuck on the same error that chris said.

I've been having issues webwalking to ardougne from anywhere, it will either

1. throw an error for webwalking area not found.

2. Not do anything

3. Get stuck on charter ships in port sarim to any other port.

17 hours ago, IDontEB said:

I also have the same thing as well but very rarely. If it does happen it happens when the bot misclicks the stairs and thinks it has gone up. If I click the stairs manually to go up them it continues on perfectly, if not it gets stuck on the same error that chris said.

Had the same issue, restarting the script didn't do anything. It would walk to the exact same tile, but instead of z=1, it went to z=0. Walking upstairs and downstairs again fixed the problem.

It sounds like a plane issue, is this the same issue Chris is having?

On 12/9/2017 at 2:24 AM, Alek said:

It sounds like a plane issue, is this the same issue Chris is having?

Not exactly. I'm receiving idling issues at certain points in taverly dungeon / brutal dragons pathing areas. It is very random with sometimes no logger info. I'm currently trying to record any information I find. But for now, I will be implementing WalkEvent in the meantime to my SDN versions.

Taverly dungeon is pretty big with a lot of obstacles in there. I'm going to close this for now until you can further investigate. In the meantime Ill look at general web walking patches. Thanks!