Im having an issue with my barb constantly standing still for 4-5 secs after it kills a mob group causing it to die standing in fire...etc. Anyone have a fix for this please? Im using the most current avdenturer and trinity 2.
Untick "Use Furious Charge OOC" under barbarian settings, this prevents the bot from waiting for Furious Charge cooldown.
Whether it's the nav servers or not is up for debate -- if you look at trinity behavior logs you'll see that right when it sits still for a while, the log is usually just running OOC buffs etc but not moving anywhere. As soon as it starts moving, you can see an entry in the log like this: Code: 19:49:35.797 DEBUG MainGridProvider New scene found: a1dun_Leor_01_Filler Then it starts moving again. Here's a little more context from the log: Code: 19:49:29.556 DEBUG TrinityDebug [Trinity][Behavior] Waiting for loot to drop, delay: 150ms 19:49:29.557 DEBUG TrinityDebug [Trinity][Behavior] Selected new power=Barbarian_Whirlwind pos=x="1037" y="826" z="0" acdGuid=-1 preWait=0 postWait=1 timeSinceAssigned=0 timeSinceUse=91.0846 range=20 charges=0 19:49:29.558 DEBUG TrinityDebug [Trinity][Behavior] Object in Range: noRangeRequired=False Target In Range=True stuckOnTarget=False npcInRange=False power=Barbarian_Whirlwind 19:49:29.558 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree from HandleObjectInRange ForceTargetUpdate CPowerShouldWaitAfter=66 power=Barbarian_Whirlwind pos=x="1033" y="814" z="0" acdGuid=-1 preWait=0 postWait=1 timeSinceAssigned=94.0874 timeSinceUse=0 range=20 charges=0 19:49:29.583 DEBUG TrinityDebug [Trinity][Behavior] Waiting for loot to drop, delay: 150ms 19:49:29.584 DEBUG TrinityDebug [Trinity][Behavior] Selected new power=Barbarian_Whirlwind pos=x="1037" y="826" z="0" acdGuid=-1 preWait=0 postWait=1 timeSinceAssigned=0 timeSinceUse=26.024 range=20 charges=0 19:49:29.585 DEBUG TrinityDebug [Trinity][Behavior] Object in Range: noRangeRequired=False Target In Range=True stuckOnTarget=False npcInRange=False power=Barbarian_Whirlwind 19:49:29.585 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree from HandleObjectInRange ForceTargetUpdate CPowerShouldWaitAfter=66 power=Barbarian_Whirlwind pos=x="1033" y="814" z="0" acdGuid=-1 preWait=0 postWait=1 timeSinceAssigned=121.1123 timeSinceUse=0 range=20 charges=0 19:49:29.634 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Failure to tree from CurrentTargetNull2 ForceTargetUpdate CurrentTargetIsNull CPowerShouldWaitAfter=18.9568 power=Barbarian_Whirlwind pos=x="1033" y="814" z="0" acdGuid=-1 preWait=0 postWait=1 timeSinceAssigned=168.1555 timeSinceUse=47.0432 range=20 charges=0 19:49:31.618 DEBUG TrinityDebug [Trinity][Behavior] Selected new power=Barbarian_Sprint pos=x="0" y="0" z="0" acdGuid=-1 preWait=0 postWait=0 timeSinceAssigned=0 timeSinceUse=4188.9552 range=0 charges=0 19:49:31.618 DEBUG Logger [Trinity][Behavior] Using OOC Buff: Barbarian_Sprint 19:49:35.797 DEBUG MainGridProvider New scene found: a1dun_Leor_01_Filler 19:49:35.889 DEBUG TrinityDebug [Trinity][Behavior] Selected new power=Barbarian_Sprint pos=x="0" y="0" z="0" acdGuid=-1 preWait=0 postWait=0 timeSinceAssigned=0 timeSinceUse=4270.3858 range=0 charges=0 19:49:40.091 DEBUG TrinityDebug [Trinity][Behavior] Selected new power=Barbarian_Sprint pos=x="0" y="0" z="0" acdGuid=-1 preWait=0 postWait=0 timeSinceAssigned=0 timeSinceUse=4202.452 range=0 charges=0 19:49:41.199 DEBUG Logger [Adventurer][Navigation] Moving to <868.75, 888.75, 0> (Distance: 85.03107) 19:49:41.554 DEBUG TrinityDebug [Trinity] Target changed to 77796 // demonTrooper_A (Unit) Adding ShouldIgnore=False nearbyCount=3 radiusDistance=70 hotspot=False elitesInRange=False hitPointsPc=1.0 summoner=False quest=False minimap=False bounty=False IsTrash MinWeight 19:49:41.561 DEBUG TrinityDebug [Trinity][Behavior] Selected new power=Barbarian_FuriousCharge pos=x="823" y="819" z="0" acdGuid=-1 preWait=1 postWait=1 timeSinceAssigned=0 timeSinceUse=13289.2713 range=32 charges=1 19:49:41.562 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree from Whirlwind ForceTargetUpdate CPowerShouldWaitBefore=64.9998 power=Barbarian_FuriousCharge pos=x="823" y="819" z="0" acdGuid=-1 preWait=1 postWait=1 timeSinceAssigned=1.0002 timeSinceUse=13290.2715 range=32 charges=1 19:49:41.607 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree from Whirlwind ForceTargetUpdate CPowerShouldWaitBefore=19.9586 power=Barbarian_FuriousCharge pos=x="823" y="819" z="0" acdGuid=-1 preWait=1 postWait=1 timeSinceAssigned=46.0414 timeSinceUse=13335.3127 range=32 charges=1 19:49:41.634 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree from Whirlwind ForceTargetUpdate 19:49:41.698 DEBUG TrinityDebug [Trinity] Target changed to 282789 // x1_SkeletonArcher_Westmarch_A (Unit) Adding ShouldIgnore=False nearbyCount=4 radiusDistance=87 hotspot=False elitesInRange=False hitPointsPc=1.0 summoner=False quest=False minimap=False bounty=False IsTrash Ranged 19:49:42.602 DEBUG TrinityDebug [Trinity] Target changed to 282789 // x1_SkeletonArcher_Westmarch_A (Unit) Adding ShouldIgnore=False nearbyCount=5 radiusDistance=28 hotspot=False elitesInRange=False hitPointsPc=1.0 summoner=False quest=False minimap=False bounty=False IsTrash Ranged You can see how no movement occurs from 19:49:29 to 19:49:35. That's the "4-5 secs" the OP is talking about. This isn't the cause of the pausing 100% of the time, but I see it a lot in the logs, enough that's certainly some kind of issue.