What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Gatherbuddy2 not moving anymore

Svenstar123

Member
Joined
Dec 24, 2012
Messages
584
Reaction score
24
Last edited:
How would i find out how exactly to fix it best tony :S ?
Your bot is on a spot, which cannot navigate to your next profile hotpoint. Try changing to other profile or so.
 
i used the profile for weeks straight now and it was fine
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.
 
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 ^^
 
Last edited:
Back
Top