Hi all, I'm facing a really weird problem with gatherbuddy. I just recorded a mining path for Twilight Highlands. I started recording and stopped recording after I completed the path above the exact same node near dragonmaw hold. When I activate the path however it says End of path reached, moving to beginning of path and it flies all the way to the grim batol entrance. So I thought: Hmm, maybe it glitched because I zoned out into Wetlands at that point, I'll do it over and make sure I stay in Twilight Highlands. So I recorded a new path and this time it starts flying a totally different path, not even close to what I recorded and the whole path doesnt even make sense as it will try to fly through mountains and what not. I couldn't find anything off in the log but I provided it anyhow maybe someone notices something. Thanks in advance.
I had the same exact problem. I fixed it by switching it to Bounce from Circle. If that doesn't work for you, I'd say try messing with different options. EDIT: On second thought, that doesn't fix it. It seems that the bot goes to the end of waypoints and then goes to the open end of them in a straight direction. It turns out that switching between bounce and circle fixes it in that situation making it more likely to go towards the waypoint and not the endpoint flying straight to eternity. I don't have a real fix for this unfortunately, but then again, I am just some random noob.
I just noticed something else. I recorded yet another path and when I ran it it said Reached point 396, returning to profile start. Now I remember clearly that when I finished recording it said my path had 199 waypoints... Is there any known bug in GB or the auth that causes xml files to override each other? edit Ok now I'm completely lost. I deleted all the XMLs I had on auth and recorded again, this time at the end it said finished recording with 0 path indexes... I was like FUUUUUUUU wasted 15 minutes. I tried running it anyway and it works... Can someone explain please.
make sure before you start the recording that there isnt a profile already loaded on Gb before every recording hit th "Unload path" button
