Has anyone else Experienced this ?

[Durp]

So i Fired up an old Gathering account for lol's and Using an old profile which i made mabye a year ago that Gathers Herbs and Ores in the Jade forest.

Now strange thing is that the bot collects herbs fine but whenever it approaches a Ghost iron deposit it starts to do the old Unstuck movements as if it's Moving around a tree. now it does this even if a Node is in the open lol, after about 20 seconds it just moves on without harvesting

 

[Dreadlord]

So i Fired up an old Gathering account for lol's and Using an old profile which i made mabye a year ago that Gathers Herbs and Ores in the Jade forest.

Now strange thing is that the bot collects herbs fine but whenever it approaches a Ghost iron deposit it starts to do the old Unstuck movements as if it's Moving around a tree. now it does this even if a Node is in the open lol, after about 20 seconds it just moves on without harvesting

The most recent update has caused a lot of these weird errors to pop up, right now my druid is shifting out of cat form to perform a melee strike then catform to finish the fight.

 

[Durp]

The most recent update has caused a lot of these weird errors to pop up, right now my druid is shifting out of cat form to perform a melee strike then catform to finish the fight.

that Comment sent a light bulb off in my head. I tried different revisions of HB and Version .750 works like a boss. picking up no worries

 

[wearloga]

I will try to see if I can get the .750 to work on my machine.

But this is exactly what I came here for. I, too, have this issue with GB2, especially with mining, but to a lesser extend also with herbalism. While the general navigation is just like it's always been, as soon as GB2 starts to approach a node it bugs out. By this I mean that it starts moving for a few inch in different directions in rapid succession, which, of course, screams "botter at work". It seems like HB2 thinks that it is stuck (even though there is no reference to that in the log, which just repeats "approaching <type> node at <coordinates>") even when there is no obstacle in sight.
Also I noticed that it sometimes while trying to approach a node first takes off in a random direction before actually approaching the node. This means that it will occasionally fly beyond the range at which it detects a node and then just move on without harvesting it.
And finally I also observed, though this happens a lot less, that it sometimes doesn't register a node which is actually present in the world (I've been monitoring HB2 while it was doing my herb gathering for me for about 2,5 hours) and doesn't blacklist under water nodes.
I hope this info is of some help to someone who might be able to fix this