Hi! Sorry for reviving this post, but I am experiencing this issue again in the new build 1.0.374.0 I have downloaded it today from the website. Thing is everything works fine, the problem is when it tries to enter Ul'dah it starts giving issues, also I have notice that if I stop/start the profile it will toss this info: Code: [12:05:11.816 N] [NavGraph] Path from <358.6379, 74.74335, 163.2019> Western Thanalan(140) to <-94.52972, 6.500001, 39.81079> Ul'dah - Steps of Thal(131) found: [12:05:11.816 N] [NavGraph] Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130) [12:05:11.816 N] [NavGraph] Move to <-119.7715, 11.44033, 9.342945> on Ul'dah - Steps of Nald(130) which leads to <-104.845, 6.984573, 8.872177> on Ul'dah - Steps of Thal(131) [12:05:11.816 N] [NavGraph] Move to <-94.52972, 6.500001, 39.81079> on Ul'dah - Steps of Thal(131) [12:05:11.816 N] [NavGraph] EndPath [12:05:11.974 N] Requesting path on 140 from <358.6379, 74.74335, 163.2019> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [12:05:17.865 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:05.8909999 ms And then it won't do anything it will constatly keep checking gear like this: Code: [12:05:26.603 D] Finished checking gear in 00:00:00.0063118 [12:05:41.659 D] Finished checking gear in 00:00:00.0034989 [12:05:56.672 D] Finished checking gear in 00:00:00.0018578 [12:06:11.785 D] Finished checking gear in 00:00:00.0024087 [12:06:26.921 D] Finished checking gear in 00:00:00.0022234 [12:06:41.952 D] Finished checking gear in 00:00:00.0022136 [12:06:57.004 D] Finished checking gear in 00:00:00.0020511 [12:07:12.150 D] Finished checking gear in 00:00:00.0029648 [12:07:27.200 D] Finished checking gear in 00:00:00.0021782 [12:07:42.304 D] Finished checking gear in 00:00:00.0035081 [12:07:57.428 D] Finished checking gear in 00:00:00.0068230 Here is on of the reports, although the same thing happens wherever the character is and the path is calculated to ul'dah. ZoneName: Western Thanalan ZoneId: I don't know Start Location: <358.6379, 74.74335, 163.2019> End Location: <471.6793, 101.9539, 159.6207> Client: Global or Chinese Code: [11:56:35.595 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1233549 ms [11:56:35.636 N] Requesting path on 140 from <348.3959, 74.74333, 162.306> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:35.761 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1250136 ms [11:56:35.802 N] Requesting path on 140 from <349.4041, 74.74334, 162.4361> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:35.926 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1237976 ms [11:56:35.969 N] Requesting path on 140 from <350.3837, 74.74335, 162.5625> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:36.092 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1234060 ms [11:56:36.142 N] Requesting path on 140 from <351.412, 74.74335, 162.6952> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:36.266 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1237126 ms [11:56:36.306 N] Requesting path on 140 from <352.3951, 74.74335, 162.822> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:36.429 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1225149 ms [11:56:36.469 N] Requesting path on 140 from <353.3681, 74.74335, 162.9476> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:36.593 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1234355 ms [11:56:36.635 N] Requesting path on 140 from <354.3698, 74.74335, 163.0768> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:36.760 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1247913 ms [11:56:36.802 N] Requesting path on 140 from <355.3521, 74.74335, 163.2036> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:36.926 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1241214 ms [11:56:36.967 N] Requesting path on 140 from <356.33, 74.74335, 163.3298> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:37.090 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1228343 ms [11:56:37.135 N] Requesting path on 140 from <357.3457, 74.74335, 163.4608> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130)) [11:56:37.258 N] Received path response to <471.6793, 101.9539, 159.6207> in 00:00:00.1225427 ms [11:56:37.303 N] Requesting path on 140 from <357.9268, 74.74335, 163.5358> to <471.6793, 101.9539, 159.6207> within 5 (Move to <471.6793, 101.9539, 159.6207> on Western Thanalan(140) which leads to <-171.653, 13.99448, -14.04281> on Ul'dah - Steps of Nald(130))
The meshes need to be updated most likely, and given that they reworked many of the quests the profiles will need to be updated as well. Can run the profile again and then post the entire log?
Sure, here it is, I have run a fresh character with it, and it worked up to a certain point. I have a character in girdania, and the profile worked flawlesly up until the character exited the city and then it got stucked again, I restarted the bot, it teleported to the city and went back to the same spot, which is this (see image attached): Causing a 'deadlock' again. Maybe there is something different in the way the character travels to a map transition point? I will keep running the profile in the other character to see if it is such a case EDIT: I have been running the bot for a while now, and again, when a path is required from zoneA to zoneB and there is no teleport location to zoneB available, the bot will enter in the 'checking gear state', here is a case: My character does not have a teleport point in Eastern Thanalan as it has never been in that zone, so the path is calcualted properly since it receives response but somehow it can not reach it. Could it be because the end of the path is a "transition point" ??
I see the issue, with 5.3, many of the zone transition's got updated to be in the air with the enabling of flying, since we scrape this data from the game files i'll need to adjust the zone transitions back down so it can properly path.
I have tried that version and it works flawlesly, it can transition to undiscovered zones no problem. But, sadly, there is another issue now. Right after unboarding the airship, this happens: The path response is recived but the character won't move. The bright side is that after stopping/starting the bot it works again with no problem I have tried travelling from ul'dah to girdania and from girdania to the other main town, the same issue arises.
[14:57:46.375 N] [NavGraph] Path from <692.8753, 21.20929, -144.1295> 雷克兰德(813) to <782.6533, 21.41485, -4.291597> 雷克兰德(813) found: [14:57:46.375 N] [NavGraph] Move to <782.6533, 21.41485, -4.291597> on 雷克兰德(813) [14:57:46.375 N] [NavGraph] EndPath [14:57:46.446 N] [NavGraph] Going to learn Fort Jobb [14:57:46.446 N] RequestingCN path on 813 from <692.8753, 21.20929, -144.1295> to <753.8109, 23.41184, -28.8092> (8) [14:57:46.579 N] Received path response to <753.8109, 23.41184, -28.8092> in 00:00:00.1333507 ms
ZoneId 920 is not working. [19:45:50.153 N] Requesting path on 920 from <167.2023, 2.921999, 190.1253> to <74.47925, 2.522, 211.2306> within 5 (Kill Target) [19:45:51.325 N] Received path response to <74.47925, 2.522, 211.2306> in 00:00:01.1685706 ms
Doesn't dismount when trying to learn this aetheryte Code: [21:36:01.197 D] Targeting aetheryte 0x8898B2 0x24019AA8910 [21:36:01.417 D] Interacting with aetheryte 0x24019AA8910 [21:36:01.417 V] [NavGraph] Interactring with 176 to learn Anagnorisis [21:36:04.431 V] [NavGraph] Did not start learning aetheryte [21:36:04.431 D] Interacting with aetheryte 0x24019AA8910 [21:36:04.431 V] [NavGraph] Interactring with 176 to learn Anagnorisis [21:36:07.451 V] [NavGraph] Did not start learning aetheryte
We've always let the game handle dismounting when learning aetherytes. Probably an issue where it wasn't fully in range.
