Hello, with the latest HB build i'm seeing some issues with the Archaeology botbase.
First, the bot sometimes runs far out of digsite boundaries. Happened to me with two digsites in Jade Forest, where the bot just mounted and ran all the way somewhere to the middle of Valley of the Four Winds, where was no digsite at all. Have tried to clean the mesh folder to let them download again, didn't help though.
Second, in the Gong of Hope digsite in Jade Forest there's a bridge just above the digsite. Sadly, the bot runs up and down trying to find artifacts above on the bridge instead of under it. Seems to be a digsite-specific issue, but I don't see a way to blacklist a pandarian digsite as of now.
Third, the buddy does not recognize when the digsite is depleted and tries to do all its 6 digs on that site. I.e. happens when I need to restart buddy when some artifacts have been digged up already and less than 6 remains.
Also I'm seeing loads of "System.AccessViolationException:" errors when running buddy since the first alpha release before MoP, I kinda got used to them because everything usually works, but I'm sure they shouldn't be there.
The log should contain all issues mentioned.
First, the bot sometimes runs far out of digsite boundaries. Happened to me with two digsites in Jade Forest, where the bot just mounted and ran all the way somewhere to the middle of Valley of the Four Winds, where was no digsite at all. Have tried to clean the mesh folder to let them download again, didn't help though.
Second, in the Gong of Hope digsite in Jade Forest there's a bridge just above the digsite. Sadly, the bot runs up and down trying to find artifacts above on the bridge instead of under it. Seems to be a digsite-specific issue, but I don't see a way to blacklist a pandarian digsite as of now.
Third, the buddy does not recognize when the digsite is depleted and tries to do all its 6 digs on that site. I.e. happens when I need to restart buddy when some artifacts have been digged up already and less than 6 remains.
Also I'm seeing loads of "System.AccessViolationException:" errors when running buddy since the first alpha release before MoP, I kinda got used to them because everything usually works, but I'm sure they shouldn't be there.
The log should contain all issues mentioned.
Last edited:
