That terrain really needs a navmesh so you may be better off using gb2. I'm considering an idea for you recording your own repair path but its very hard to provide a decent user interface so you can spot errors, why it fails, etc.
For me its every mob that it pauses on before attacks. (edit: after testing with other toons and coming back to this one for the farm for day. I noticed on some mobs it had no delay. will keep watching find out why if can) Here is 1 did real fast in outlands to make a log for ya. Was shaman with Lightning shield. Helps lil bit some attackers will die from shield alone.
Tried DK in uldum. Looked like did fine no delay while watched it. Have seen it delay before, but ofc for testing doesnt wanna show itself. Tried again, same profile. Using Druid in flight form. (log attached) Watched waited till got in first fight then stopped it. Looks like only took about 4 seconds to start fighting. Lil delay. Will keep posting logs if it helps. Would like to see the delay in attacking fixed also.
I've got the same problem with my druid. Posted the log already in http://www.thebuddyforum.com/support-issues/21149-gb-long-pauses-between-actions.html
I had an idea. If the long pause is not happening to all. Could it be a computer issue, where with slow computers its making the pause. I know before it didnt put in log the "looking for possible attackers out of 146 objects" thing. Then it goes through list of each mob around it. Till finds one who is attacking. Maybe the process of writing all that to the log is whats making it pause. Assuming it did this before in background without writing it to log. Just my thoughts. Maybe the how fast it writes to log is whats making it pause. Slower hard drives, increase time on writes. Creates pause. maybe maybe.. I dont know
This user had a WoW combat bug; there was no attacker and GB was thus unable to get out of the combat loop.
^ I had that bug a BUNCH yesterday, kept spamming core combat and I'm like wtf, but then I noticed my toon was genuinely in combat without a mob to show for it.. I had to make him run a long ass time and it worked.. kinda amazing how people just debug it and think its the bot's fault.. the mob was clearly not there but the toon in combat.
/agree Also this is only version where I've gotten the whisper "are you a bot? iam going to report you" Assuming they was watching me not attack back on mobs right away. Dont know for sure.
Tested on 85 Shaman, elemental. In Uldum. So far every fight I see he hits back in good time, no pause. Working awesome so far will keep watching. 2nd test with DK 85, blood. In Vash Combat good. Would like to see the ascend taken off for Vash. 3rd test with DK 85, blood. In Twilight. Where I die most seems. So will see how it goes. Ah died. But don't think its GB fault. With them elementals that do the ground spikes that come up. I would say with my testing that the pause with combat is fixed.
it skips some nodes for no reason: Maneuvering towards Twilight Jasmine: ( -4351.3, -4751.1, 139.718 ) Moving to node... Maneuvering complete. Patrolling...Twilight Highlands 2.0 m+h
