Hi Tony, so tonight suddenly all my farmers stopped moving anymore and only in rare occasions seem to farm for a short period before going back into standing still. These are the logs of a complete fresh install. View attachment 14108 2017-03-08 17.38.txt View attachment 12396 2017-03-08 17.39.txt View attachment 8920 2017-03-08 17.37.txt View attachment 1628 2017-03-08 17.34.txt Hope u can help me out, seeing the mesh bugs in suramar are trying to get fixed this problem tilted me a bit X)
Your bot is on a spot, which cannot navigate to your next profile hotpoint. Try changing to other profile or so.
This means nothing, since its gathering profiles, while they follow predefined path, their goals - ores and herb nodes are with semi-random spawn spots. [16:41:58.901 D] [Flightor] Failed ground nav from <1429.201, 4439.649, 119.0527> to <1514.714, 4421.791, 123.0733> with status PathGenerationFailed [16:41:54.787 D] [Flightor] Failed ground nav from <1398.793, 4421.819, 125.3995> to <1514.714, 4421.791, 123.0733> with status PathGenerationFailed [16:41:54.380 D] [Flightor] Failed ground nav from <1436.313, 4463.979, 120.8189> to <1514.714, 4421.791, 123.0733> with status PathGenerationFailed Got the pattern? All of your toons (probably on the same realm) are tryin to reach a very same hotspot, which cannot be reached by the bot. It could be a node underground or underwater, same stuff - un-navigable, so the bot fails on it. Thats the reason Tony classified it as profile issue.
thanks alot for the clarification aion! They are all on different realms, i really want to know what i could possibly do to avoid this issue besides changing profile which btw also didnt help.
I doubt this is serverside profile issue - if so, this would fail on each random hotpoint or so. Can you port a bot to different zone and start different zone profile, then see how it goes. Out of the 3 logs, I seen the profiles starting and farming several nodes then stuck on the very same hotpoint.
I removed the certain hotspot 1514 one out of the profile now and after a full restart it seems to work again, thanks alot for the help As it seems the other profile had this certain hotspot inside too X) and the reason it happened is i believe the mesh issues i keep reporting ^^