[Bug] THE Skydeep Cenote

[Delky91]

What happened?

doing The Skydeep Cenote i get stock in after the second boss, first it keep looking to the correct path then al the intrucction on the path get pass until the las one which indicate Boss [100.08, -191.99, -439.29], then the character try to run to the boss where he keep hiting the left wall until they pull the 3 enemy closes, the problem is that when this fight end the AD think that the duty waws compelte and leave the duty 2 pull a far from the last boss of the dung.

i put one img of the log.

in some dungeons work flawless but in every 2 of 3 dun i run i have some error, the dun before this one have the problem before the 2 boss.

Version Number

0.0.0179

Steps to reproduce the error

mode: support
other option: none

select the skydeep Cenote dungeon
and run

u can select any of the path 4 currently and u have the same result

Relevant log output

00:07:33.661 | INF | [AutoDuty] Running AutoDuty in The Skydeep Cenote, Looping 2 times
00:07:33.661 | INF | [AutoDuty] Running The Skydeep Cenote 2 Times
00:07:34.653 | INF | [AutoDuty] AutoEquip - Started
00:07:34.955 | INF | [AutoDuty] AutoEquip Finished
00:07:35.078 | INF | [AutoDuty] Queueing: Support: The Skydeep Cenote
00:07:38.878 | INF | [AutoDuty] Done Queueing: Support: The Skydeep Cenote
00:07:45.628 | INF | [AutoDuty] Starting Navigation
00:07:45.635 | INF | [vnavmesh] Queueing move-to <32.350, -35.460, 1.860>
00:07:45.671 | INF | [vnavmesh] Pathfinding complete
00:09:04.213 | INF | [vnavmesh] Queueing move-to <32.350, -35.460, 1.860>
00:09:04.329 | INF | [vnavmesh] Pathfinding complete
00:09:14.341 | INF | [vnavmesh] Queueing move-to <-104.280, -52.660, -84.070>
00:09:14.456 | INF | [vnavmesh] Pathfinding complete
00:10:25.197 | INF | [vnavmesh] Queueing move-to <-104.280, -52.660, -84.070>
00:10:25.313 | INF | [vnavmesh] Pathfinding complete
00:11:30.041 | INF | [vnavmesh] Queueing move-to <-104.280, -52.660, -84.070>
00:11:30.158 | INF | [vnavmesh] Pathfinding complete
00:12:48.685 | INF | [vnavmesh] Queueing move-to <-104.280, -52.660, -84.070>
00:12:48.801 | INF | [vnavmesh] Pathfinding complete
00:12:51.740 | INF | [vnavmesh] Queueing move-to <-105.080, -52.000, -158.500>
00:12:51.855 | INF | [vnavmesh] Pathfinding complete
00:13:03.079 | INF | [AutoDuty] Starting Action Boss: Feather Ray
00:16:11.729 | INF | [vnavmesh] Queueing move-to <-104.780, -51.950, -208.890>
00:16:11.846 | INF | [vnavmesh] Pathfinding complete
00:16:20.419 | INF | [vnavmesh] Queueing move-to <-156.680, -51.710, -208.910>
00:16:20.533 | INF | [vnavmesh] Pathfinding complete
00:16:28.706 | INF | [vnavmesh] Legacy mode is now disabled
00:16:30.393 | INF | [vnavmesh] Legacy mode is now enabled
00:16:31.380 | INF | [vnavmesh] Queueing move-to <-84.250, -209.910, -62.040>
00:16:31.495 | INF | [vnavmesh] Pathfinding complete
00:16:38.279 | INF | [vnavmesh] Queueing move-to <-84.250, -209.910, -62.040>
00:16:38.394 | INF | [vnavmesh] Pathfinding complete
00:18:01.126 | INF | [vnavmesh] Queueing move-to <-84.250, -209.910, -62.040>
00:18:01.242 | INF | [vnavmesh] Pathfinding complete
00:19:16.398 | INF | [vnavmesh] Queueing move-to <-84.250, -209.910, -62.040>
00:19:16.516 | INF | [vnavmesh] Pathfinding complete
00:22:11.545 | INF | [vnavmesh] Queueing move-to <-75.800, -210.000, -65.220>
00:22:11.662 | INF | [vnavmesh] Pathfinding complete
00:22:17.670 | INF | [vnavmesh] Queueing move-to <-85.140, -210.000, -154.640>
00:22:17.784 | INF | [vnavmesh] Pathfinding complete
00:22:31.583 | INF | [AutoDuty] Starting Action Boss: null
00:25:52.106 | INF | [vnavmesh] Queueing move-to <38.560, -210.000, -155.220>
00:25:52.165 | ERR | [vnavmesh] Failed to find a path from <-80.67899, -210.00003, -151.96246> (100000140023F) to <38.56, -210, -155.22> (0): failed to find polygon on a mesh
00:25:52.223 | INF | [vnavmesh] Pathfinding complete
00:25:52.398 | INF | [vnavmesh] Queueing move-to <101.950, -189.900, -227.820>
00:25:52.456 | ERR | [vnavmesh] Failed to find a path from <-80.67899, -210.00003, -151.96246> (100000140023F) to <101.95, -189.9, -227.82> (0): failed to find polygon on a mesh
00:25:52.514 | INF | [vnavmesh] Pathfinding complete
00:25:52.630 | INF | [vnavmesh] Queueing move-to <100.220, -189.900, -230.670>
00:25:52.688 | ERR | [vnavmesh] Failed to find a path from <-80.67899, -210.00003, -151.96246> (100000140023F) to <100.22, -189.9, -230.67> (0): failed to find polygon on a mesh
00:25:52.745 | INF | [vnavmesh] Pathfinding complete
00:26:01.761 | INF | [vnavmesh] Queueing move-to <100.390, -194.900, -363.660>
00:26:01.780 | ERR | [vnavmesh] Failed to find a path from <-80.67899, -210.00003, -151.96246> (100000140023F) to <100.39, -194.9, -363.66> (0): failed to find polygon on a mesh
00:26:01.798 | INF | [vnavmesh] Pathfinding complete
00:26:09.535 | INF | [vnavmesh] Queueing move-to <100.080, -191.990, -439.290>
00:26:09.573 | INF | [vnavmesh] Pathfinding complete
00:28:31.407 | INF | [AutoDuty] Starting Action Boss: null
00:28:31.444 | INF | [vnavmesh] Queueing move-to <100.080, -191.990, -439.290>
00:28:31.481 | INF | [vnavmesh] Pathfinding complete

Other relevant plugins installed

vnavmesh, vbm

Plugin config file

AutoDuty.json

[Delky91]

sorry at that moment was running 0.0.0178 no the 179 i update the addon but the error continue

[erdelf]

couldn't really replicate it.. but improved some of the pathing on normal and w2w in #747