FNV316

14 Sep 2018 20H14.log.html

Another one

14 Sep 2018 20H14.log.html

By the way, trying to reach a coordinate at Thorium Point results in these logs, regardless of where the bot is located:

[N] 17:53:39 - [Path-Finding] FindPath from -11,46249 ; 3,063801 ; 80,71931 ; "None" to -6513,62 ; -1183,78 ; 309,2551 ; "Flying" (Azeroth)
[D] 17:53:40 - [PatherServer] Select server 1
[N] 17:53:40 - [Server] [RD]  Could not found To PolyRef
[N] 17:53:40 - [Server] [Path-Finding] Cannot find path: -11,46249 ; 3,063801 ; 80,71931 ; "None" (Azeroth_31,99426_32,02149) to -6513,62 ; -1183,78 ; 309,2551 ; "None" (Azeroth_34,21959_44,21304)
[N] 17:53:44 - [Path-Finding] Path Count: 2 (15,95924y, 4933ms)

Which leads to bot running at the point in a straight line, ignoring any obstacles, because he is unable to calculate a path.

I might start a series for this. Places with broken meshes or pathfinding:

-Thorium Point (entirely broken)

-Stonetalon Peak (entirely broken)

-Booty Bay (partially broken)

-Silverwing Grove (entirely broken)

-Warlock trainers in Stormwind (entirely broken)

-Auberdine (partially broken)

Using offmesh connections sometimes helps, but they are way too unreliable and take too long to trigger (if they are triggered at all). Hopefully the announced update helps to fix these issues

13 Sep 2018 19H53.log.html

Try to figure out which product exactly is causing that issue and contact the related seller (like me, I use that authentication system in my Quester product). It's not related to wRobot itself