Gatherbuddy sometimes fails to dismount when its trying to land a node, especially when the node is placed on a cliff or wall. When flying towards the node it will try to land, fail and then fly away a few yard and then back to node again, if it fails to land the node for about 3 times the bot blacklist the node. Getting the message "[17:31:18.174 D] (Singular) [CombatLog] SPELL_CAST_FAILED Mining#74517 failure: 'Can't do that while moving'"
I disabled randombuddy and created a new profile for testing purpose, now the problem is mutch less frequent but still exists. Getting messages in log: [20:14:37.610 D] (Singular) [CombatLog] SPELL_CAST_FAILED Mining#74517 failure: 'You are mounted.' [20:35:07.854 D] (Singular) [CombatLog] SPELL_CAST_FAILED Mining#74517 failure: 'Can't do that while moving'
yea, i saw it doing it as well, the devs are checking it. while it looks kind of bad it shouldn't prevent you from using GB2, i wouldn't worry about it too much just keep an eye out for the next release.
im sorry but I cant believe you would say to not worry to much about it, this has been happening to me as well and this will get you reported so quick you might as well name your character iamabot.....this issue needs to be taken care of asap.
as far as gathering goes, your toon will still gather fine, the times it does do it is few and far between NOT EVERY NODE. if you want to take the risk then do so. the devs are working on it, no one said they arent.
if about 1 out of 25 nodes is far and few between then yeah far and few(my numbers might be a little off). But to downplay a issue of such that would scream BoT to others is crazy, as far as taking the risk yeah im gathering on 3 accounts as we speak but I really don't care about being banned, its an inconvenience is all and yeah im sure they are working on it I never said they were not but I just hope this is something that is priority to fix because it is sketchy. I do appreciate all the hard work the devs do I know its not an easy task to keep up with everything and continue to try to say a step ahead of blizz so thank you for that!
After a few days of testing i found that switching from singular and using TuanHA routine instead almost have solved the problem. It seems like the lag and stuttering problems you get with the current version of singular makes the bot having a hard time to calculate when to dismount and therefore misses the node.
