What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Trinity 2.9.1 and QuestTools 3.4.19

I dont seem to be able where the setting to leave the game after my character dies is. At the moment my bot is wasting a lot of keys because of this setting. DB "Death Handling" parameter is set to "Ignore". Could you help me with this?

Thanks in advance!
 
have old issue Ai not focus bloodthief and sometime didn't pick bloodshard
 
Wizard combat serious bug.

Because of this the spells that come after meteor arcane dynamo were not being cast.

Line 131 original

Code: 
if (!Player.IsIncapacitated && !arcaneDynamoPassiveReady && CanCast(SNOPower.Wizard_Meteor, CanCastFlags.NoTimer) && !ShouldWaitForConventionElement(Skills.Wizard.Meteor) &&

fixed

Code: 
if (!Player.IsIncapacitated && arcaneDynamoPassiveReady && CanCast(SNOPower.Wizard_Meteor, CanCastFlags.NoTimer) && !ShouldWaitForConventionElement(Skills.Wizard.Meteor) &&

rrrix if you ever make a credits roll file, add my name :D
 
gexstar said:
You can manually tell Questtools which gem to upgrade. Just put the ones you want upgraded higher on the list than the ones that are maxed at 50. I dont see the problem ?
Click to expand...
The problem is that when there's a gem of lower level, it always tries to upgrade that. SO, when all the gems are 51 minus the ones that max out at 50, it will continue to try to upgrade the max level ones regardless of priority.
 
trophywife said:
I dont seem to be able where the setting to leave the game after my character dies is. At the moment my bot is wasting a lot of keys because of this setting. DB "Death Handling" parameter is set to "Ignore". Could you help me with this?

Thanks in advance!
Click to expand...

self-answer:

<TrinityMaxDeaths questId="1" max="77" />

fixed the problem!
 
chime said:
DH Is completely broken at the moment also.. might be all ranged.. stand in the middle of trials and face tank.. min kite disatance dosent seem to help.. UE set dumps all Disc with smoke screen even tho spam smoke is off.. its kind of a joke actually.... unplayable..
Click to expand...

What build are you using?

Diablo III Builds - Diablo Fans

I'm running Nats set, working fine.
 
TwoCigars said:
Any ideas why my Barb does stutter steps all over the place, even against rift guardians?

It's not constant but it happens half a dozen times per normal rift.

Looks like it's starting the run animation but doesnt actually go anywhere. Once the enemy he was apparently targeting dies, he starts moving again.

EDIT: It seems like IgnorePain is being spammed like crazy in my log. I have turned off the ignore pain option in DB. Not sure why it is doing thins. I do not use ignore pain.
Code: 
19:57:53.083 DEBUG DefaultNavigationProvider Generated path to <804.8742, 1051.611, 6.031567> (p1_LR_Ghost_B 56 yds Elite=False LoS=False HP=1.00 Dir=S) with 4 hops.19:57:53.213 DEBUG TrinityDebug [Trinity] Target changed to 5758 // trDun_Cath_FloorSpawner_01 (Container) 
19:57:53.214 DEBUG DefaultNavigationProvider Navigator.Clear
19:57:53.214 DEBUG DefaultNavigationProvider Generating path to trDun_Cath_FloorSpawner_01 64 yds Elite=False LoS=True HP=-1.00 Dir=S - <818, 1073, 0.1000019>
19:57:53.217 DEBUG DefaultNavigationProvider Successfully generated path from {X=235,Y=302} to {X=237,Y=327} in 00:00:00.0006884 with 26(4) hops
19:57:53.222 DEBUG DefaultNavigationProvider Client path generated.
19:57:53.222 DEBUG DefaultNavigationProvider Generated path to <818, 1073, 0.1000019> (trDun_Cath_FloorSpawner_01 64 yds Elite=False LoS=True HP=-1.00 Dir=S) with 4 hops.
19:57:53.563 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=100 IsBossOrEliteRareUnique 
19:57:53.579 DEBUG Logger [Trinity] Used Power Furious Charge (97435) at x="867" y="1058" z="0" dist=101 Range=65 (Spender Offensive) Delay=50/50 TargetDist=101.2536 CurrentTarget=p1_LR_Ghost_B charges=1
19:57:53.917 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=93 IsBossOrEliteRareUnique CloseRange10f  MaxWeight 
19:57:53.919 DEBUG Logger [Trinity] Used Power Sprint (78551)  Range=0 (Other Offensive) Delay=50/50 TargetDist=1334.553 CurrentTarget=p1_LR_Ghost_B charges=0
19:57:54.022 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <843.75, 1068.75, 0> as visited, distance 20/30, IsVisited=False
19:57:54.035 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 80 nodes in 13ms
19:57:54.044 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=100 IsBossOrEliteRareUnique 
19:57:54.201 DEBUG Logger [Trinity] Used Power Furious Charge (97435) at x="823" y="1131" z="0" dist=68 Range=65 (Spender Offensive) Delay=50/50 TargetDist=68.9725 CurrentTarget=p1_LR_Ghost_B charges=1
19:57:54.421 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <831.25, 1106.25, 0> as visited, distance 29/30, IsVisited=False
19:57:54.434 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 79 nodes in 13ms
19:57:54.445 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=89 CloseRange 
19:57:54.473 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <806.25, 1106.25, 0> as visited, distance 28/30, IsVisited=False
19:57:54.488 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 78 nodes in 14ms
19:57:54.558 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=100 IsBossOrEliteRareUnique 
19:57:54.663 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <831.25, 1143.75, 0> as visited, distance 26/30, IsVisited=False
19:57:54.664 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <806.25, 1143.75, 0> as visited, distance 30/30, IsVisited=False
19:57:54.677 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 76 nodes in 12ms
19:57:55.158 DEBUG DefaultNavigationProvider Generating path to p1_LR_Ghost_B 45 yds Elite=True LoS=False HP=0.98 Dir=W - <804.8953, 1073.302, 0.1000019>
19:57:55.161 DEBUG DefaultNavigationProvider Successfully generated path from {X=254,Y=329} to {X=237,Y=322} in 00:00:00.0006755 with 18(4) hops
19:57:55.164 DEBUG DefaultNavigationProvider Client path generated.
19:57:55.165 DEBUG DefaultNavigationProvider Generated path to <804.8953, 1073.302, 0.1000019> (p1_LR_Ghost_B 45 yds Elite=True LoS=False HP=0.98 Dir=W) with 4 hops.
19:57:55.181 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=89 CloseRange 
19:57:55.294 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=94 IsBossOrEliteRareUnique 
19:57:55.393 DEBUG Logger [Trinity] Used Power Furious Charge (97435) at x="870" y="1047" z="0" dist=79 Range=65 (Spender Offensive) Delay=50/50 TargetDist=79.26995 CurrentTarget=p1_LR_Ghost_B charges=2
19:57:55.510 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=89 IsBossOrEliteRareUnique CloseRange10f  MaxWeight 
19:57:55.636 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=90 IsBossOrEliteRareUnique 
19:57:55.960 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 94 nodes in 16ms
19:57:56.215 DEBUG Logger [Trinity] Used Power Furious Charge (97435) at x="918" y="1066" z="0" dist=78 Range=65 (Spender Offensive) Delay=50/50 TargetDist=78.09621 CurrentTarget=p1_LR_Ghost_B charges=2
19:57:56.359 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <881.25, 1068.75, 0> as visited, distance 27/30, IsVisited=False
19:57:56.376 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 93 nodes in 15ms
19:57:56.384 DEBUG TrinityDebug [Trinity] Target changed to 141194 // demonTrooper_B (Unit) Adding ShouldIgnore=False nearbyCount=2 radiusDistance=0 hotspot=False elitesInRange=False hitPointsPc=0.0 summoner=False quest=False minimap=False bounty=False IsTrash CloseRange10f 
19:57:56.446 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=86 IsBossOrEliteRareUnique 
19:57:56.551 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <918.75, 1068.75, 0> as visited, distance 23/30, IsVisited=False
19:57:56.567 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 92 nodes in 15ms
19:57:57.327 DEBUG Logger [Trinity] Used Power Furious Charge (97435) at x="814" y="1027" z="0" dist=70 Range=65 (Spender Offensive) Delay=50/50 TargetDist=70.30762 CurrentTarget=p1_LR_Ghost_B charges=2
19:57:57.553 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <853.75, 1031.25, 0> as visited, distance 29/30, IsVisited=False
19:57:57.571 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 91 nodes in 17ms
19:57:57.601 DEBUG Logger [Trinity] Used Power Wrath of the Berserker (79607)  Range=0 (Other Buff) Delay=50/50 TargetDist=1364.46 CurrentTarget=p1_LR_Ghost_B charges=0
19:57:57.814 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=18 IsBossOrEliteRareUnique LowHPElite CloseRange10f  MaxWeight 
19:57:57.836 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1344.646 CurrentTarget=p1_LR_Ghost_B charges=0
19:57:59.873 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=83 IsBossOrEliteRareUnique 
[B]19:58:02.605 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1343.777 CurrentTarget=p1_LR_Ghost_B charges=0
19:58:02.716 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1341.093 CurrentTarget=p1_LR_Ghost_B charges=0
19:58:02.832 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1337.238 CurrentTarget=p1_LR_Ghost_B charges=0
19:58:02.942 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1335.566 CurrentTarget=p1_LR_Ghost_B charges=0
19:58:03.056 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1337.438 CurrentTarget=p1_LR_Ghost_B charges=0
19:58:03.186 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1340.761 CurrentTarget=p1_LR_Ghost_B charges=0
19:58:03.299 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1344.106 CurrentTarget=p1_LR_Ghost_B charges=0
19:58:03.411 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1345.062 CurrentTarget=p1_LR_Ghost_B charges=0[/B]
19:58:03.868 DEBUG TrinityDebug [Trinity] Target changed to 418918 // p1_LR_Ghost_B (Unit) Adding shouldIgnore=False hitPointsPct=23 CloseRange 
19:58:05.231 DEBUG TrinityDebug [Trinity] Target changed to 5758 // trDun_Cath_FloorSpawner_01 (Container) 
19:58:06.031 DEBUG TrinityDebug [Trinity] Interacting with trDun_Cath_FloorSpawner_01 Distance 11 Radius 6.9 Attempt 0
19:58:06.033 DEBUG TrinityDebug [Trinity] Unable to find skill for power Axe_Operate_Gizmo
19:58:06.257 DEBUG TrinityDebug [Trinity] Interacting with trDun_Cath_FloorSpawner_01 Distance 8 Radius 6.9 Attempt 1
19:58:06.258 DEBUG TrinityDebug [Trinity] Unable to find skill for power Axe_Operate_Gizmo
19:58:06.476 DEBUG TrinityDebug [Trinity] Interacting with trDun_Cath_FloorSpawner_01 Distance 7 Radius 6.9 Attempt 2
19:58:06.476 DEBUG TrinityDebug [Trinity] Unable to find skill for power Axe_Operate_Gizmo
19:58:06.589 DEBUG TrinityDebug [Trinity] Target changed to 301283 // Console_PowerGlobe (PowerGlobe) 
19:58:06.706 DEBUG DefaultNavigationProvider Navigator.Clear
19:58:06.706 DEBUG DefaultNavigationProvider Generating path to Console_PowerGlobe 52 yds Elite=False LoS=False HP=-1.00 Dir=S - <878.7715, 1060.247, 0.5000019>
19:58:06.709 DEBUG DefaultNavigationProvider Successfully generated path from {X=235,Y=331} to {X=232,Y=352} in 00:00:00.0007188 with 22(4) hops
19:58:06.712 DEBUG DefaultNavigationProvider Client path generated.
19:58:06.713 DEBUG DefaultNavigationProvider Generated path to <878.7715, 1060.247, 0.5000019> (Console_PowerGlobe 52 yds Elite=False LoS=False HP=-1.00 Dir=S) with 4 hops.
19:58:07.887 DEBUG TrinityDebug [Trinity] Target changed to 5390 // SkeletonSummoner_D (Unit) Adding ShouldIgnore=False nearbyCount=7 radiusDistance=54 hotspot=False elitesInRange=False hitPointsPc=1.0 summoner=False quest=False minimap=False bounty=False IsTrash Ranged 
[B]19:58:07.888 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1368.487 CurrentTarget=SkeletonSummoner_D charges=0
19:58:07.982 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1370.732 CurrentTarget=SkeletonSummoner_D charges=0
19:58:08.094 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1372.985 CurrentTarget=SkeletonSummoner_D charges=0[/B]
19:58:08.196 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <881.25, 1031.25, 0> as visited, distance 30/30, IsVisited=False
19:58:08.212 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 90 nodes in 15ms
[B]19:58:08.226 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1375.568 CurrentTarget=SkeletonSummoner_D charges=0
19:58:08.355 DEBUG Logger [Trinity] Used Power Ignore Pain (79528)  Range=0 (Other Buff) Delay=50/50 TargetDist=1377.512 CurrentTarget=SkeletonSummoner_D charges=0[/B]
19:58:14.769 DEBUG Logger [QuestTools][ExploreDungeonTag] Nodes [Unvisited: Route:90 Grid:90 | Grid-Visited: 72/162] Box:15/0.01 Step:MainBehavior PP:30 Dir: SW Current: 904, 1031, 0
19:58:14.769 DEBUG DefaultNavigationProvider Navigator.Clear
19:58:14.770 DEBUG Logger [QuestTools][ExploreDungeonTag] New Nav Target=904, 1031, 0 Dir=SW Dist=37
19:58:14.770 DEBUG DefaultNavigationProvider Generating path to Dungeon Node 904, 1031, 0, Dir=SW - <903.75, 1031.25, 0>
19:58:14.772 DEBUG DefaultNavigationProvider Successfully generated path from {X=232,Y=352} to {X=221,Y=361} in 00:00:00.0006837 with 14(6) hops
19:58:14.776 DEBUG DefaultNavigationProvider Client path generated.
19:58:14.777 DEBUG DefaultNavigationProvider Generated path to <903.75, 1031.25, 0> (Dungeon Node 904, 1031, 0, Dir=SW) with 6 hops.
19:58:14.794 DEBUG Logger [QuestTools][ExploreDungeonTag] Nodes [Unvisited: Route:90 Grid:90 | Grid-Visited: 72/162] Box:15/0.01 Step:MainBehavior PP:30 Dir: SW Current: 904, 1031, 0
19:58:14.994 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <903.75, 1031.25, 0> as visited, distance 29/30, IsVisited=False
19:58:15.010 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 89 nodes in 15ms
19:58:15.022 DEBUG Logger [QuestTools][ExploreDungeonTag] Nodes [Unvisited: Route:89 Grid:89 | Grid-Visited: 73/162] Box:15/0.01 Step:MainBehavior PP:30 Dir: W Current: 881, 994, 0
19:58:15.023 DEBUG DefaultNavigationProvider Navigator.Clear
19:58:15.023 DEBUG Logger [QuestTools][ExploreDungeonTag] New Nav Target=881, 994, 0 Dir=W Dist=60
19:58:15.023 DEBUG DefaultNavigationProvider Generating path to Dungeon Node 881, 994, 0, Dir=W - <881.25, 993.75, 0>
19:58:15.027 DEBUG DefaultNavigationProvider Successfully generated path from {X=229,Y=354} to {X=205,Y=352} in 00:00:00.0002811 with 33(5) hops
19:58:15.032 DEBUG DefaultNavigationProvider Client path generated.
19:58:15.032 DEBUG DefaultNavigationProvider Generated path to <881.25, 993.75, 0> (Dungeon Node 881, 994, 0, Dir=W) with 5 hops.
19:58:15.050 DEBUG Logger [QuestTools][ExploreDungeonTag] Nodes [Unvisited: Route:89 Grid:89 | Grid-Visited: 73/162] Box:15/0.01 Step:MainBehavior PP:30 Dir: W Current: 881, 994, 0

UPDATE: There is a support ticket for this with logs here: https://www.thebuddyforum.com/demon...669-stutter-movement-attacks.html#post1958005
Click to expand...

Been looking into this - I think I fixed it, but, could you actually post one of your own logs?

The thread you mention, no one actually uploaded any useful logs. Most of them the guy actually has ignore pain equipped, or posted logs for a Monk, or the log file was empty (why did he even bother posting it?)
 
voidx said:
Wizard combat serious bug.

Because of this the spells that come after meteor arcane dynamo were not being cast.

Line 131 original

Code: 
if (!Player.IsIncapacitated && !arcaneDynamoPassiveReady && CanCast(SNOPower.Wizard_Meteor, CanCastFlags.NoTimer) && !ShouldWaitForConventionElement(Skills.Wizard.Meteor) &&

fixed

Code: 
if (!Player.IsIncapacitated && arcaneDynamoPassiveReady && CanCast(SNOPower.Wizard_Meteor, CanCastFlags.NoTimer) && !ShouldWaitForConventionElement(Skills.Wizard.Meteor) &&

rrrix if you ever make a credits roll file, add my name :D
Click to expand...

Thanks, fixed.
 
MyTee said:
I'm having an issue between rifts. The normal behavior after porting to town at the completion of a grift seems to be:

1: Kadala
2: Close Rift
3: Run to Stash
4: Wait for Close Rift Timer (looping QuestTools logs here, including "Skipping TownRun")
5: Do Town Run stuff once rift finally closes (not always!)
6: Open next grift
Click to expand...

Are you using the absolutely latest R-Rift? I don't put version numbers on the profile, but, I fixed that.
 
So, no update on the WD ? The two main builds, Carnevil/Poison Dart and pet doctor, are still broken. Always running into melee range and totally broken dodging of ground effects. Arcane torrent or molten explosion is 90% permadeath at higher rifts.

Builds look like this:

Zuni SMK G50+ Solo [2.2] - Witch Doctor - Diablo III Builds - Diablo Fans

[2.2] Carnevil Dagger of Darts 50+ GRIFT Build - Witch Doctor - Diablo III Builds - Diablo Fans

rrrix said:
Are you using the absolutely latest R-Rift? I don't put version numbers on the profile, but, I fixed that.
Click to expand...

I got the same problem. Using the R-Rift provided by EZUpdater.
 
Last edited:
gexstar said:
So, no update on the WD ? The two main builds, Carnevil/Poison Dart and pet doctor, are still broken. Always running into melee range and totally broken dodging of ground effects. Arcane torrent or molten explosion is 90% permadeath at higher rifts.

Builds look like this:

Zuni SMK G50+ Solo [2.2] - Witch Doctor - Diablo III Builds - Diablo Fans

[2.2] Carnevil Dagger of Darts 50+ GRIFT Build - Witch Doctor - Diablo III Builds - Diablo Fans



I got the same problem. Using the R-Rift provided by EZUpdater.
Click to expand...

Since no one has posted an actual log file showing they're broken, they're going to stay broken until I can get a Dagger of Darts so I can actually see what's happening.
 
Code: 
13:42:50.049 DEBUG DefaultNavigationProvider Generating path to Scavenger_B 17 yds Elite=False LoS=True HP=0.81 Dir=NW - <1965.138, 4221.666, 0.1000018>
13:42:50.065 DEBUG DefaultNavigationProvider Successfully generated path from {X=302,Y=191} to {X=297,Y=186} in 00:00:00.0000767 with 6(2) hops
13:42:50.096 DEBUG DefaultNavigationProvider Client path generated.
13:42:50.096 DEBUG DefaultNavigationProvider Generated path to <1965.138, 4221.666, 0.1000018> (Scavenger_B 17 yds Elite=False LoS=True HP=0.81 Dir=NW) with 2 hops.
13:42:50.377 DEBUG TrinityDebug [Trinity] Kite movement failed, cancelling for 1500ms
13:42:50.377 DEBUG TrinityDebug [Trinity] Unable to find skill for power Weapon_Melee_Instant
13:42:50.377 DEBUG Logger [Trinity] GetSkillInfo found no SkillMeta for 
13:42:50.424 DEBUG TrinityDebug [Trinity] Kite movement cancelled for -1453ms
13:42:50.439 DEBUG TrinityDebug [Trinity] Unable to find skill for power Weapon_Melee_Instant
13:42:50.439 DEBUG Logger [Trinity] Used Power  (-1)  on -2127363709 Range=0 (Other Other) Delay=50/50 TargetDist=4667.479 CurrentTarget=Scavenger_B charges=0
13:42:50.564 DEBUG TrinityDebug [Trinity] Target changed to 5236 // Scavenger_B (Unit) Adding ShouldIgnore=False nearbyCount=0 radiusDistance=1 hotspot=False elitesInRange=False hitPointsPc=0.1 summoner=False quest=False minimap=False bounty=False IsTrash LowHPTrash CloseRange10f 
13:42:50.564 DEBUG TrinityDebug [Trinity] Kite movement cancelled for -1313ms
13:42:50.564 DEBUG Logger [Trinity] Used Power Haunt (83602)  on -2127298487 Range=0 (Spender Other) Delay=50/50 TargetDist=4661.843 CurrentTarget=Scavenger_B charges=0
13:42:50.751 DEBUG DefaultNavigationProvider Navigator.Clear

He tries to melee a mob... and always casts haunt with 0 range. Do you need a full log ?

View attachment 3992 2015-05-23 10.32.txt

I thought it was because of Grave Injustice passive. The combat routine checks for that and tries to stay in range for it, but the result of the min function should never be zero. Tried editing out that part, didnt change anything. And the problems with dodging arcane torrent or molten explosions are probably a completely different matter.
 
Last edited:
It happened several times now that the bot was running around on an empty map, searching for the rift guardian, while the guardian had spawned on the level before. I always wondered how that happens and now i saw him go full retard. He took a conduit shrine while waiting for the guardian to spawn and suddenly just ran through the map, entered the next level and left the rift guardian behind.

So, there might be something wrong with the bot behavior after taking conduits. Bot should still check if the rift guardian has already spawned. Or generally check if the guardian has spawned before entering a new level.
 
so can anyone tell me WHY im getting these messages
[Trinity][Performance] Execution of CacheManagement.RefreshCacheMainLoop took 1137.69340ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache.UpdateBlock took 1139.08790ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache took 1142.90140ms.
[Trinity][Performance] Execution of HandleTarget took 1150.07620ms.
and how do i fix it
 
How can I make the bot ignore elites? It takes too much time to kill them in higher greater rifts (and yes, I have enabled the "ignore elite pakcs").
 
You must log in or register to reply here.
Back
Top