Trinity 1.8.28

codeseg · Apr 27, 2014

rrrix said:
It should get used on elites - how would you like it used?

In most builds you probably just want to use Explosive Blast on cooldown when you're in combat. Especially if you have a Wand of Woh. But maybe it can just be a checkbox to use on cooldown, sort of like with Fetish Army?

Oksehode · Apr 27, 2014

rrrix said:
The dungeon explorer was not reset:

Code:

05:21:43.442 INFO Logger [QuestTools] Player died! Position=<1296.062, 927.7783, 0.1> QuestId=312429 StepId=2 WorldId=288454 05:21:43.443 INFO ProfileOrderManager ProfileOrderManager.OnPlayerDied, Resetting caches. 05:21:43.443 DEBUG ProfileOrderManager Resetting current behavior. 05:21:43.444 INFO BrainBehavior Clicked revive at corpse button 05:21:48.756 INFO ProfileManager Loaded profile Rift Bot Optimized Explore 05:21:48.962 INFO ToggleTargetingTag ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80 05:21:48.963 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 8c279044-aa4f-432a-a9a4-d1090f4492d7

Can you please turn this on, and all others off?

The logs will clearly state if the dungeon explorer is being reset on death.

I will do as you say but look at this:

Code:

Line 170493: 05:21:24.462 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:180 Grid:180 | Grid-Visited: 106] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: SW 
	Line 170494: 05:21:24.483 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:180 Grid:180 | Grid-Visited: 106] Box:20/0,05 Step:MainBehavior PP:30 Dir: SW 
	Line 171492: 05:21:27.909 INFO  Logger [Trinity][ProfileTag] Marking unvisited nearby node as visited - Node <1273.75, 973.75, 0> is within path precision 28/30
	Line 171493: 05:21:27.932 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:179 Grid:179 | Grid-Visited: 107] Box:20/0,05 Step:MainBehavior PP:30 Dir: SW 
	Line 177283: 05:21:36.945 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1273.75, 923.75, 0> - Node <1273.75, 923.75, 0> is within PathPrecision (23/30)
	Line 177284: 05:21:36.945 INFO  Logger [Trinity][ProfileTag] Marking unvisited nearby node as visited - Node <1323.75, 923.75, 0> is within path precision 28/30
	Line 177285: 05:21:36.946 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:177 Grid:177 | Grid-Visited: 109] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: S 
	Line 177286: 05:21:36.946 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:177 Grid:177 | Grid-Visited: 109] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: S 
	Line 192238: 05:22:17.735 INFO  Logger [Trinity][ProfileTag] Minimap Explored Nodes Disabled
	Line 192241: 05:22:17.735 INFO  Logger [Trinity][ProfileTag] Initialized TrinityExploreDungeon: boxSize=15 boxTolerance=0,55 endType=FullyExplored timeoutType=Timer timeoutValue=1800 pathPrecision=30 sceneId=0 actorId=0 objectDistance=40 markerDistance=60 exitNameHash=0
	Line 192242: 05:22:17.736 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:0 Grid:0 | Grid-Visited: 0] Box:15/0,55 Step:PostInit PP:30 Dir: NW 
	Line 192244: 05:22:17.738 INFO  Logger [Trinity][ProfileTag] Box Size or Tolerance has been changed! 15/0,55
	Line 192246: 05:22:17.739 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:0 Grid:0 | Grid-Visited: 0] Box:15/0,55 Step:BrainBehavior.DungeonExplorer.Reset PP:30 Dir: NW 
	Line 192247: 05:22:17.739 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:0 Grid:0 | Grid-Visited: 0] Box:20/0,05 Step:SetBoxSize+Tolerance PP:30 Dir: NW 
	Line 192250: 05:22:17.805 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:286 Grid:286 | Grid-Visited: 0] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: N 
	Line 192251: 05:22:17.810 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1273.75, 973.75, 0> - Node <1273.75, 973.75, 0> is within PathPrecision (26/30)
	Line 192252: 05:22:17.810 INFO  Logger [Trinity][ProfileTag] Marking unvisited nearby node as visited - Node <1323.75, 973.75, 0> is within path precision 25/30
	Line 192253: 05:22:17.811 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:284 Grid:284 | Grid-Visited: 2] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: NE 
	Line 192254: 05:22:17.811 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:284 Grid:284 | Grid-Visited: 2] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: NE 
	Line 192255: 05:22:17.827 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:284 Grid:284 | Grid-Visited: 2] Box:20/0,05 Step:MainBehavior PP:30 Dir: NE 
	Line 192325: 05:22:18.303 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:284 Grid:284 | Grid-Visited: 2] Box:20/0,05 Step:MainBehavior PP:30 Dir: E 
	Line 192361: 05:22:18.428 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:284 Grid:284 | Grid-Visited: 2] Box:20/0,05 Step:MainBehavior PP:30 Dir: NE 
	Line 192479: 05:22:19.037 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1273.75, 1023.75, 0> - Node <1273.75, 1023.75, 0> is within PathPrecision (30/30)
	Line 192480: 05:22:19.037 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:283 Grid:283 | Grid-Visited: 3] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: E 
	Line 192483: 05:22:19.070 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:283 Grid:283 | Grid-Visited: 3] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: NW 
	Line 192484: 05:22:19.088 INFO  Logger [Trinity][ProfileTag] Current node was already marked as visited!
	Line 192485: 05:22:19.088 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:283 Grid:283 | Grid-Visited: 3] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: N 
	Line 192486: 05:22:19.103 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:283 Grid:283 | Grid-Visited: 3] Box:20/0,05 Step:MainBehavior PP:30 Dir: N 
	Line 192487: 05:22:19.127 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:283 Grid:283 | Grid-Visited: 3] Box:20/0,05 Step:MainBehavior PP:30 Dir: NW 
	Line 193424: 05:22:25.016 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:283 Grid:283 | Grid-Visited: 3] Box:20/0,05 Step:MainBehavior PP:30 Dir: N 
	Line 193468: 05:22:25.460 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1223.75, 973.75, 0> - Node <1223.75, 973.75, 0> is within PathPrecision (30/30)
	Line 193469: 05:22:25.460 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:282 Grid:282 | Grid-Visited: 4] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: NE 
	Line 193470: 05:22:25.461 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:282 Grid:282 | Grid-Visited: 4] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: NE 
	Line 193471: 05:22:25.477 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:282 Grid:282 | Grid-Visited: 4] Box:20/0,05 Step:MainBehavior PP:30 Dir: NE 
	Line 193615: 05:22:26.959 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1223.75, 1023.75, 0> - Node <1223.75, 1023.75, 0> is within PathPrecision (30/30)
	Line 193616: 05:22:26.959 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:281 Grid:281 | Grid-Visited: 5] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: E 
	Line 193617: 05:22:26.961 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:281 Grid:281 | Grid-Visited: 5] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: E 
	Line 193618: 05:22:26.975 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:281 Grid:281 | Grid-Visited: 5] Box:20/0,05 Step:MainBehavior PP:30 Dir: E 
	Line 193766: 05:22:28.798 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1223.75, 1073.75, 0> - Node <1223.75, 1073.75, 0> is within PathPrecision (30/30)
	Line 193767: 05:22:28.799 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:280 Grid:280 | Grid-Visited: 6] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: E 
	Line 193768: 05:22:28.799 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:280 Grid:280 | Grid-Visited: 6] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: E 
	Line 193769: 05:22:28.815 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:280 Grid:280 | Grid-Visited: 6] Box:20/0,05 Step:MainBehavior PP:30 Dir: E 
	Line 193988: 05:22:30.843 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1223.75, 1123.75, 0> - Node <1223.75, 1123.75, 0> is within PathPrecision (30/30)
	Line 193989: 05:22:30.844 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:279 Grid:279 | Grid-Visited: 7] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: E 
	Line 193992: 05:22:30.875 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:279 Grid:279 | Grid-Visited: 7] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: NW 
	Line 193993: 05:22:30.888 INFO  Logger [Trinity][ProfileTag] Current node was already marked as visited!
	Line 193994: 05:22:30.889 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:279 Grid:279 | Grid-Visited: 7] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: SW 
	Line 193995: 05:22:30.904 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:279 Grid:279 | Grid-Visited: 7] Box:20/0,05 Step:MainBehavior PP:30 Dir: SW 
	Line 194065: 05:22:31.651 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1273.75, 1073.75, 0> - Node <1273.75, 1073.75, 0> is within PathPrecision (30/30)
	Line 194066: 05:22:31.652 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:278 Grid:278 | Grid-Visited: 8] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: SE 
	Line 194067: 05:22:31.653 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:278 Grid:278 | Grid-Visited: 8] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: SE 
	Line 194068: 05:22:31.669 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:278 Grid:278 | Grid-Visited: 8] Box:20/0,05 Step:MainBehavior PP:30 Dir: SE 
	Line 194093: 05:22:31.766 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1273.75, 1123.75, 0> - Node <1273.75, 1123.75, 0> is within PathPrecision (30/30)
	Line 194094: 05:22:31.766 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:277 Grid:277 | Grid-Visited: 9] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: E 
	Line 194095: 05:22:31.767 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:277 Grid:277 | Grid-Visited: 9] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: E 
	Line 194096: 05:22:31.782 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:277 Grid:277 | Grid-Visited: 9] Box:20/0,05 Step:MainBehavior PP:30 Dir: E 
	Line 194315: 05:22:33.324 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1268.75, 1168.75, 0> - Node <1268.75, 1168.75, 0> is within PathPrecision (30/30)
	Line 194316: 05:22:33.325 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:276 Grid:276 | Grid-Visited: 10] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: E 
	Line 194317: 05:22:33.325 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:276 Grid:276 | Grid-Visited: 10] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: E 
	Line 194318: 05:22:33.341 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:276 Grid:276 | Grid-Visited: 10] Box:20/0,05 Step:MainBehavior PP:30 Dir: E 
	Line 194453: 05:22:34.117 INFO  Logger [Trinity][ProfileTag] Marking unvisited nearby node as visited - Node <1223.75, 1173.75, 0> is within path precision 28/30
	Line 194454: 05:22:34.135 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:275 Grid:275 | Grid-Visited: 11] Box:20/0,05 Step:MainBehavior PP:30 Dir: E 
	Line 194641: 05:22:35.779 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:275 Grid:275 | Grid-Visited: 11] Box:20/0,05 Step:MainBehavior PP:30 Dir: SE 
	Line 194668: 05:22:35.885 INFO  Logger [Trinity][ProfileTag] Marking unvisited nearby node as visited - Node <1223.75, 1223.75, 0> is within path precision 26/30
	Line 194669: 05:22:35.902 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:274 Grid:274 | Grid-Visited: 12] Box:20/0,05 Step:MainBehavior PP:30 Dir: SE 
	Line 194670: 05:22:35.934 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1256.25, 1233.75, 0> - Node <1256.25, 1233.75, 0> is within PathPrecision (30/30)
	Line 194671: 05:22:35.935 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:273 Grid:273 | Grid-Visited: 13] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: NE 
	Line 194674: 05:22:35.966 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:273 Grid:273 | Grid-Visited: 13] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: NE 
	Line 194675: 05:22:35.982 INFO  Logger [Trinity][ProfileTag] Current node was already marked as visited!
	Line 194676: 05:22:35.983 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:273 Grid:273 | Grid-Visited: 13] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: E 
	Line 194677: 05:22:35.997 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:273 Grid:273 | Grid-Visited: 13] Box:20/0,05 Step:MainBehavior PP:30 Dir: E 
	Line 194731: 05:22:36.253 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:273 Grid:273 | Grid-Visited: 13] Box:20/0,05 Step:MainBehavior PP:30 Dir: NE 
	Line 194782: 05:22:36.815 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1226.25, 1256.25, 0> - Node <1226.25, 1256.25, 0> is within PathPrecision (30/30)
	Line 194783: 05:22:36.816 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:272 Grid:272 | Grid-Visited: 14] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: N 
	Line 194784: 05:22:36.816 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:272 Grid:272 | Grid-Visited: 14] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: N 
	Line 194785: 05:22:36.832 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:272 Grid:272 | Grid-Visited: 14] Box:20/0,05 Step:MainBehavior PP:30 Dir: N 
	Line 194812: 05:22:37.044 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:272 Grid:272 | Grid-Visited: 14] Box:20/0,05 Step:MainBehavior PP:30 Dir: NE 
	Line 194965: 05:22:38.409 INFO  Logger [Trinity][ProfileTag] Marking unvisited nearby node as visited - Node <1173.75, 1223.75, 0> is within path precision 28/30
	Line 194966: 05:22:38.425 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:271 Grid:271 | Grid-Visited: 15] Box:20/0,05 Step:MainBehavior PP:30 Dir: NE 
	Line 195048: 05:22:39.296 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1161.25, 1263.75, 0> - Node <1161.25, 1263.75, 0> is within PathPrecision (30/30)
	Line 195049: 05:22:39.296 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:270 Grid:270 | Grid-Visited: 16] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: NE 
	Line 195050: 05:22:39.297 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:270 Grid:270 | Grid-Visited: 16] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: NE 
	Line 195051: 05:22:39.310 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:270 Grid:270 | Grid-Visited: 16] Box:20/0,05 Step:MainBehavior PP:30 Dir: NE 
	Line 195174: 05:22:40.674 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1123.75, 1273.75, 0> - Node <1123.75, 1273.75, 0> is within PathPrecision (30/30)
	Line 195175: 05:22:40.674 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:269 Grid:269 | Grid-Visited: 17] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: E 
	Line 195176: 05:22:40.675 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:269 Grid:269 | Grid-Visited: 17] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: E 
	Line 195177: 05:22:40.691 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:269 Grid:269 | Grid-Visited: 17] Box:20/0,05 Step:MainBehavior PP:30 Dir: E 
	Line 195319: 05:22:42.328 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1123.75, 1323.75, 0> - Node <1123.75, 1323.75, 0> is within PathPrecision (30/30)
	Line 195320: 05:22:42.329 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:268 Grid:268 | Grid-Visited: 18] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: E 
	Line 195321: 05:22:42.329 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:268 Grid:268 | Grid-Visited: 18] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: E 
	Line 195322: 05:22:42.346 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:268 Grid:268 | Grid-Visited: 18] Box:20/0,05 Step:MainBehavior PP:30 Dir: E 
	Line 195512: 05:22:44.298 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1113.75, 1373.75, 0> - Node <1113.75, 1373.75, 0> is within PathPrecision (30/30)
	Line 195513: 05:22:44.298 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:267 Grid:267 | Grid-Visited: 19] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: NE 
	Line 195516: 05:22:44.330 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:267 Grid:267 | Grid-Visited: 19] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: SW 
	Line 195517: 05:22:44.345 INFO  Logger [Trinity][ProfileTag] Current node was already marked as visited!
	Line 195518: 05:22:44.345 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:267 Grid:267 | Grid-Visited: 19] Box:20/0,05 Step:BrainBehavior.DungeonExplorer.Update PP:30 Dir: NW 
	Line 195519: 05:22:44.361 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:267 Grid:267 | Grid-Visited: 19] Box:20/0,05 Step:MainBehavior PP:30 Dir: NW 
	Line 195560: 05:22:44.831 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:267 Grid:267 | Grid-Visited: 19] Box:20/0,05 Step:MainBehavior PP:30 Dir: N 
	Line 195580: 05:22:44.941 INFO  Logger [Trinity][ProfileTag] Dequeueing current node <1073.75, 1323.75, 0> - Node <1073.75, 1323.75, 0> is within PathPrecision (30/30)
	Line 195581: 05:22:44.942 INFO  Logger [Trinity][ProfileTag] Nodes [Unvisited: Route:266 Grid:266 | Grid-Visited: 20] Box:20/0,05 Step:SetNodeVisited PP:30 Dir: NE

As you can see, the bot has come up to 109 explored grids before he dies, then it resets back to 0 again. This is when he starts to backtrack to all previous visited grids.

rrrix · Apr 27, 2014

Oksehode said:
As you can see, the bot has come up to 109 explored grids before he dies, then it resets back to 0 again. This is when he starts to backtrack to all previous visited grids.

Can you update your QuestTools from SVN? It looks like that was the thing that is reloading the profile on death, even if the option was not enabled in the UI. Reloading the profile will cause this.

Oksehode · Apr 27, 2014

rrrix said:
Can you update your QuestTools from SVN? It looks like that was the thing that is reloading the profile on death, even if the option was not enabled in the UI. Reloading the profile will cause this.

Yeah It's disabled in the UI. I've downloaded rev 19 of Quest Tools and I will try again, thanks man.

xxfearxx · Apr 27, 2014

rrix would it be possible to have an option to avoid stuff like molten core explosions and frozen even when using wotb archon akkrat's champion etc? having it stay in molten esp has resulted in lot of needless deaths on t3+ for me at least. or is there maybe something i can edit that would result in this? couldnt find anything when i looked but also dont really know what im looking for

Oksehode · Apr 27, 2014

I could be totally wrong but I think avoidance from AOE effects is turned off out of combat so if there is molten explosions left on the ground if all the elites/champ is dead, the bot will ignore the explosions. rrrix can correct me if I'm wrong.

Edit:
@rrrix

Did you do something to avoidance from previous versions? The bot feels "dumbed" down when a lot of things happen on screen with elite/champ packs. Taking more dmg than usual.

raxmo89 · Apr 27, 2014

solved!
the problem was that demon buddy had problems getting the correct questid from diablo, setting it to 1 solved my problems

xxfearxx · Apr 27, 2014

Oksehode said:
I could be totally wrong but I think avoidance from AOE effects is turned off out of combat so if there is molten explosions left on the ground if all the elites/champ is dead, the bot will ignore the explosions. rrrix can correct me if I'm wrong.

could be, however even in combat if its using wotb (havent tested with wiz/crusader recently but id guess same for archon akkrat) it won't avoid molten explosions. without wotb up it attempts to avoid based on however you set it up in the combat options for each class.

Gorm · Apr 27, 2014

rrrix said:

I went to Silver Spire Level 1, used this:

Code:

    <TrinityExploreDungeon questId="1" until="FullyExplored" boxSize="30" boxTolerance="0.01" pathPrecision="30" />

and this is the result - it works.

Code:

[Trinity][ProfileTag] Nodes [Unvisited: Route:37 Grid:37 | Grid-Visited: 4] Box:30/0.01 Step:MainBehavior PP:30 Dir: E 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 65 Direction: E) duration=2 distance=65 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 64 Direction: E) duration=1 distance=64 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 62 Direction: E) duration=1 distance=62 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 60 Direction: E) duration=1 distance=60 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 58 Direction: E) duration=1 distance=58 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 57 Direction: E) duration=1 distance=57 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 55 Direction: E) duration=1 distance=55 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 54 Direction: E) duration=1 distance=54 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 52 Direction: E) duration=2 distance=52 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 51 Direction: E) duration=1 distance=51 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 49 Direction: E) duration=1 distance=49 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 48 Direction: E) duration=3 distance=48 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 46 Direction: E) duration=1 distance=46 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 45 Direction: E) duration=2 distance=45 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 43 Direction: E) duration=1 distance=43 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 42 Direction: E) duration=2 distance=42 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 40 Direction: E) duration=3 distance=40 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 40 Direction: E) duration=2 distance=40 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 37 Direction: E) duration=1 distance=37 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 36 Direction: E) duration=1 distance=36 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 34 Direction: E) duration=2 distance=34 
[Trinity][Navigator] Navigator Moved dest=x="1249" y="479" z="0" (DungeonNode x="1249" y="479" z="0" Distance: 32 Direction: E) duration=2 distance=32 
[Trinity][ProfileTag] Dequeueing current node <1248.75, 478.75, 0> - Node <1248.75, 478.75, 0> is within PathPrecision (29/30)
[Trinity][ProfileTag] Nodes [Unvisited: Route:36 Grid:36 | Grid-Visited: 5] Box:30/0.01 Step:SetNodeVisited PP:30 Dir: E

Then I tried this:

Code:

<TrinityExploreDungeon questId="1" until="FullyExplored" boxSize="30" boxTolerance="0.01" pathPrecision="90" />

And it works:

Code:

[Trinity][ProfileTag] Nodes [Unvisited: Route:30 Grid:30 | Grid-Visited: 6] Box:30/0.01 Step:BrainBehavior.DungeonExplorer.Update PP:90 Dir: S 
[Trinity][ProfileTag] Current node was already marked as visited!
[Trinity][ProfileTag] Nodes [Unvisited: Route:30 Grid:30 | Grid-Visited: 6] Box:30/0.01 Step:BrainBehavior.DungeonExplorer.Update PP:90 Dir: N 
[Trinity][ProfileTag] Nodes [Unvisited: Route:30 Grid:30 | Grid-Visited: 6] Box:30/0.01 Step:MainBehavior PP:90 Dir: N 
[Trinity][Navigator] Navigator Moved dest=x="1011" y="711" z="0" (DungeonNode x="1011" y="711" z="0" Distance: 112 Direction: N) duration=13 distance=112 
[Trinity][Navigator] Navigator Moved dest=x="1011" y="711" z="0" (DungeonNode x="1011" y="711" z="0" Distance: 109 Direction: N) duration=1 distance=109 
[Trinity][Navigator] Navigator Moved dest=x="1011" y="711" z="0" (DungeonNode x="1011" y="711" z="0" Distance: 96 Direction: N) duration=1 distance=96 
[Trinity][Navigator] Navigator Moved dest=x="1011" y="711" z="0" (DungeonNode x="1011" y="711" z="0" Distance: 92 Direction: N) duration=1 distance=92 
[Trinity][Navigator] Navigator Moved dest=x="1011" y="711" z="0" (DungeonNode x="1011" y="711" z="0" Distance: 91 Direction: N) duration=1 distance=91 
[Trinity][ProfileTag] Dequeueing current node <1011.25, 711.25, 0> - Node <1011.25, 711.25, 0> is within PathPrecision (87/90)
[Trinity][ProfileTag] Nodes [Unvisited: Route:29 Grid:29 | Grid-Visited: 7] Box:30/0.01 Step:SetNodeVisited PP:90 Dir: NW 
[Trinity][ProfileTag] Nodes [Unvisited: Route:29 Grid:29 | Grid-Visited: 7] Box:30/0.01 Step:BrainBehavior.DungeonExplorer.Update PP:90 Dir: NW 
[Trinity][ProfileTag] Nodes [Unvisited: Route:29 Grid:29 | Grid-Visited: 7] Box:30/0.01 Step:MainBehavior PP:90 Dir: NW 
[Trinity][Navigator] Navigator Moved dest=x="1021" y="656" z="0" (DungeonNode x="1021" y="656" z="0" Distance: 93 Direction: NW) duration=17 distance=93 
[Trinity][Navigator] Navigator Moved dest=x="1021" y="656" z="0" (DungeonNode x="1021" y="656" z="0" Distance: 91 Direction: NW) duration=1 distance=91 
[Trinity][ProfileTag] Dequeueing current node <1021.25, 656.25, 0> - Node <1021.25, 656.25, 0> is within PathPrecision (88/90)
[Trinity][ProfileTag] Nodes [Unvisited: Route:28 Grid:28 | Grid-Visited: 8] Box:30/0.01 Step:SetNodeVisited PP:90 Dir: SW

rrix, you need to stop relying on the logs. This only proves that the log is working. Look at what the bot is actually doing.

With a path precision this large it should never touch the edge of the map.

This will be my last attempt to show you it is broken. Here is a video of another run. Watch the bot visit backtrack to the northwest touching every navigable point within 5 units.

https://mediacru.sh/mhhZRmtDhgk6

And of course, the logs say it is "working" but it obviously isn't.

http://pastebin.com/raw.php?i=RD7frszZ

gotteshand · Apr 27, 2014

sup rrrix,

found 2 typo's in the combat/abilities/wizard.cs

Code:

bool hasCalamity = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.Wizard_Teleport && s.RuneIndex == 0);

should be

Code:

bool hasCalamity = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.Wizard_Teleport && s.RuneIndex == 5);

and

Code:

bool hasSupermassive = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.X1_Wizard_Wormhole && s.RuneIndex == 0);

should be

Code:

bool hasSupermassive = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.X1_Wizard_Wormhole && s.RuneIndex == 1);

also would something like this work for damage migration during combat?

Code:

                bool hasSafePassage = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.Wizard_Teleport && s.RuneIndex == 1);
								// Defensive Teleport: SafePassage
                if (CombatBase.CanCast(SNOPower.Wizard_Teleport) && hasSafePassage && TimeSinceUse(SNOPower.Wizard_Teleport) >= 5000 && Player.CurrentHealthPct <= 0.75 && (CurrentTarget.IsBossOrEliteRareUnique || TargetUtil.IsEliteTargetInRange(30f)))
                {
								Vector3 vNewSafePassage = MathEx.CalculatePointFrom(CurrentTarget.Position, Player.Position, 0f);
								return new TrinityPower(SNOPower.Wizard_Teleport, 55f, vNewSafePassage);
                }

Basically when ever he takes loads of damage and life goes to 75% or below teleport to were he stands to get the 27% damage reduction for 5 seconds.. not sure of this will do what I want it to do

Not sure if !GetHasBuff(SNOPower.Wizard_Teleport) would work instead of the 5000 ms timer..

morfious · Apr 27, 2014

raxmo89 said:
oki will se but the ting its have worked fore me before the uppdate. but i will lock closer

wut?!

Babco · Apr 27, 2014

Lilly said:
rrrix, you are a legend!

For Witch Doctor class, here are my findings:

Trinity .26
Spirit Walk: This was cast outside combat only, which was good for movement.
Zombie Dogs: This was cast whenever off cooldown, regardless of conditions.
Gargantuan: This was cast outside cooldown too.

Trinity .27
Spirit Walk: This is now cast both in and out of combat, which sometimes saves lives. However sometimes it does not cast in combat until death.
Zombie Dogs: This is now cast off cooldown only if there are less than 3 dogs, awesome!
Gargantuan: This does not cast at all, regardless of runes now.

How to get DB to cast Spiriti Walk below say 60% health?
How to get Gargantuan to cast on cooldown?

I am happy to edit them myself, thanks a lot for all this.

Hi,

I would like to add the following when working with Ghom

Mass confusion : does not cast at all
Fire bats: Does not cast at all
Big Bad voodoo: Does not cast at all
Gargantuan: Cast when near boss
Zombie Dogs: Cast when near boss

Hitsuomy · Apr 27, 2014

Awesome work, I'm using with rift profile and plugin, it's 100% afk. Ty rrix.

rrrix · Apr 27, 2014

Gorm said:
rrix, you need to stop relying on the logs. This only proves that the log is working. Look at what the bot is actually doing.

With a path precision this large it should never touch the edge of the map.

This will be my last attempt to show you it is broken. Here is a video of another run. Watch the bot visit backtrack to the northwest touching every navigable point within 5 units.

And of course, the logs say it is "working" but it obviously isn't.

http://pastebin.com/raw.php?i=RD7frszZ

Hi Gorm,

I suggest trying a larger path precision.

I trust the logs because they show EXACTLY, in numbers, according to the game, the distances, the thresholds, and the actions being performed every single tick - up to 15 times a second.

It shows very clear in the video that the bot actually got to 30 units (yards/feet) away and then turned around. It did not run to the exact point, maybe you think "5 units" is a LOT bigger than it actually is. You should do some investigation about distances.

Try something other than a pathPrecision of 30. Try 90, 150, it's much more obvious it works. There is no special treatment of the number, it's all just Vector2 distance calculations.

In the video traveling to this node, from the east:

This is the point where your character turned around. It did not walk all the way and touch the wall where the node is:

AND, for reference, I got 3 players together, went to that exact scene, we formed a triangle, it took a few clicks but I got them about 30 units apart each.

Code:

[268B11B0] Type: Player Name: Demonhunter_Female-232 ActorSNO: 74706, Distance: 0
[268C42C4] Type: Player Name: WitchDoctor_Male-3807 ActorSNO: 6485, Distance: 30.33427
[268C069C] Type: Player Name: Wizard_Male-3793 ActorSNO: 6544, Distance: 31.21203

Full screenshot:
http://i.imgur.com/G50NSoT.jpg

Minimap:

The circle represents ~ 30, as denoted to where my party members are standing. This is the equivalent to the distance the bot will go when using that pathPrecision before queueing the next node.

With all that said - if you're expecting your bot to never run along a wall, and always stick to the middle, then, you need to learn a bit about how path finding works. The Demonbuddy path finding algorithm doesn't put more weight to a path the further away it is from a wall - all it really cares about is the shortest path, which you can observe in your video.

Good luck sticking with pathPrecision="30"

Gorm · Apr 27, 2014

rrrix said:
Hi Gorm,

I suggest trying a larger path precision.

I trust the logs because they show EXACTLY, in numbers, according to the game, the distances, the thresholds, and the actions being performed every single tick - up to 15 times a second.

It shows very clear in the video that the bot actually got to 30 units (yards/feet) away and then turned around. It did not run to the exact point, maybe you think "5 units" is a LOT bigger than it actually is. You should do some investigation about distances.

Try something other than a pathPrecision of 30. Try 90, 150, it's much more obvious it works. There is no special treatment of the number, it's all just Vector2 distance calculations.

In the video traveling to this node, from the east:

This is the point where your character turned around. It did not walk all the way and touch the wall where the node is:

Hello sorry but as I said, look at the North West corner. I did not debate that it worked for the node you pointed out.

I know how much 30 units is because that's the length of half the box size I chose. There's no reason for you to think I don't know how close the bot is supposed to get.

So I guess it at least stopped about 10 yards? So it was not the best example even if it still didn't back off farther away.

But this first example is a very obvious case where it failed.

http://www.thebuddyforum.com/demonb...ty/160447-trinity-1-8-27-a-3.html#post1493876

Endus · Apr 27, 2014

rrrix has amazing amounts of patience. It never ceases to amaze me how people who have no clue how the functions of this bot/routine/plugin work try to give rrrix orders and demand he make changes based upon their limited knowledge.

Keep up the good work rrrix. You probably already know it, but for every person that makes a post complaining, there are 10 more who aren't posting that are thankful.

rrrix · Apr 27, 2014

gotteshand said:

sup rrrix,

found 2 typo's in the combat/abilities/wizard.cs

Code:

bool hasCalamity = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.Wizard_Teleport && s.RuneIndex == 0);

should be

Code:

bool hasCalamity = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.Wizard_Teleport && s.RuneIndex == 5);

and

Code:

bool hasSupermassive = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.X1_Wizard_Wormhole && s.RuneIndex == 0);

should be

Code:

bool hasSupermassive = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.X1_Wizard_Wormhole && s.RuneIndex == 1);

also would something like this work for damage migration during combat?

Code:

                bool hasSafePassage = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.Wizard_Teleport && s.RuneIndex == 1);
                                // Defensive Teleport: SafePassage
                if (CombatBase.CanCast(SNOPower.Wizard_Teleport) && hasSafePassage && TimeSinceUse(SNOPower.Wizard_Teleport) >= 5000 && Player.CurrentHealthPct <= 0.75 && (CurrentTarget.IsBossOrEliteRareUnique || TargetUtil.IsEliteTargetInRange(30f)))
                {
                                Vector3 vNewSafePassage = MathEx.CalculatePointFrom(CurrentTarget.Position, Player.Position, 0f);
                                return new TrinityPower(SNOPower.Wizard_Teleport, 55f, vNewSafePassage);
                }

Basically when ever he takes loads of damage and life goes to 75% or below teleport to were he stands to get the 27% damage reduction for 5 seconds.. not sure of this will do what I want it to do

Not sure if !GetHasBuff(SNOPower.Wizard_Teleport) would work instead of the 5000 ms timer..

Hello,

I'm not sure where you're getting your RuneIndexes from - they are not in the same order that they appear in the game or battle.net website. Trinity has a "Debug" tab where you can dump skills and see the rune index.

This code works:

Code:

                bool hasSafePassage = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.Wizard_Teleport && s.RuneIndex == 1);
                // Defensive Teleport: SafePassage
                if (CombatBase.CanCast(SNOPower.Wizard_Teleport) && hasSafePassage && 
                    TimeSinceUse(SNOPower.Wizard_Teleport) >= 5000 && Player.CurrentHealthPct <= 0.75 && 
                    (CurrentTarget.IsBossOrEliteRareUnique || TargetUtil.IsEliteTargetInRange(30f)))
                {
                    return new TrinityPower(SNOPower.Wizard_Teleport, 1f, Player.Position);
                }

joka666 · Apr 27, 2014

rrrix awesome work mate, if I was in your position by now I would have the majority of posters on /autoignore xD

yes combat can be buggy at times, path precision will make you run into the odd wall here and there but all this is overshadowed by the simple fact that you can put on a profile for 10 hours and pretty much ignore your game whilst you do other stuff.

any little issue here and there is more than outweighed by the usefulness of this guys work!!!

gotteshand · Apr 27, 2014

rrrix said:

Hello,

I'm not sure where you're getting your RuneIndexes from - they are not in the same order that they appear in the game or battle.net website. Trinity has a "Debug" tab where you can dump skills and see the rune index.

This code works:

Code:

                bool hasSafePassage = HotbarSkills.AssignedSkills.Any(s => s.Power == SNOPower.Wizard_Teleport && s.RuneIndex == 1);
                // Defensive Teleport: SafePassage
                if (CombatBase.CanCast(SNOPower.Wizard_Teleport) && hasSafePassage && 
                    TimeSinceUse(SNOPower.Wizard_Teleport) >= 5000 && Player.CurrentHealthPct <= 0.75 && 
                    (CurrentTarget.IsBossOrEliteRareUnique || TargetUtil.IsEliteTargetInRange(30f)))
                {
                    return new TrinityPower(SNOPower.Wizard_Teleport, 1f, Player.Position);
                }

Yeah realized that my rune oder is wrong I just assumed it would be zero to five for all of em from no rune to the highest rune. But ofc blizzard doesn't keep it that simple. Should have done a dump my bad I'm sorry. Thanks for ironing out the code it'll help allot when botting on hardcore.

BOKN · Apr 27, 2014

how to fix.... bot dont attack
Siege_wallMonster_A_02-3893 ActorSNO: 230725

Trinity 1.8.28

New Member

Active Member

New Member

Active Member

New Member

Active Member

New Member

New Member

Member

New Member

New Member

New Member

Member

New Member

Member

Community Developer

New Member

Member

New Member

New Member