[DOWNLOAD] Trinity

[broomop]

2.50.235 makes DH dumber

 

[broomop]

2.50.231 is a better version on dps

 

[Sneeds44]

trinity stil has issue with opening doors it keeps standing infront of it im using the latest version 37 it stil has issue with opening doors i need to right click my self i hate that issue i gues i rever back to an older version im done abit with botting on db once the door opening is fixed i wil bot again this is not right it keeps standing at the doors it doesend left click on the door to open it

 

[Matios]

helltooth garg build with sacritfice still have big problem
2.4.1-2.4.2 Helltooth Sacrifice with Gargs 90+ HC viable - Witch Doctor - Diablo III Builds - Diablo Fans

bot focus use sacritfice before cast other more important buffs
when bot found new enemy, he start sacritfice zombie dogs, and after sacritfice all dogs he start using buff from set, soul harvester, piranhe, and die soo fast by this with no survival buff
correct will be if he first cast wall of death to get buff from set ( most important damage and 50 % damage reduction ) then soul harvest ( 15 % damage and about 80 % damage reduction ) then let him cast sacritfice

second thing is force to use wall of death to keep 100 % buff while not if fight , i have set mob pack size to 10, my bots play in group 3 dps 1 supp , and while move they die soo easy w/o damage reduction from set
now they can easy farm gr75-80 , if you will make correct work with this set, i think i can handle gr 90+
tnx and osrry for my poor english

 

[xzjv]

trinity stil has issue with opening doors it keeps standing infront of it im using the latest version 37 it stil has issue with opening doors i need to right click my self i hate that issue i gues i rever back to an older version im done abit with botting on db once the door opening is fixed i wil bot again this is not right it keeps standing at the doors it doesend left click on the door to open it

for those having the same issue, sneeds and i seem to have located his problem here, make sure the setting in objects for destructible is NOT set to ignore destructible (ignore when stuck is fine). Doors that are destructible should be being attacked regardless but that appears to currently be a bug.

 

[xzjv]

What has XZ been up to i hear you asking! he's been quiet! That is always dangerous i assure you.

I do intend to focus on the poll results for what you've said is important, which currently is swaying towards bounties.

However,

What i have realized is that we currently have a lot of settings where adjusting them is likely to just cause the bot to perform worse. Those sort of settings need to disappear, along with the ones that have become irrelevant over the years or just plain don't work anymore.

So simplification is what i am focusing on. As part of that, routines are being looked at.

The theory was that if we exposed settings for spell range etc then users would be able to tweak it and make the bot play better. But the seasons meta builds have shown that is just not possible with the current complexity of the settings. Often movement needs to be changed, spells used in weird and unexpected ways and in increasingly complicated situations. To really make them work well the the code files need to be changed; or a much more advanced interface created.

My goal is to take what we learned from Phelon's routine experiment and build something that's easier for most users to just equip the build in-game and have it perform well out of the box.

Currently the way it works is that there is a default/fallback routine; which is generally able to cast all spells. That exists to support all the weird and wonderful builds that users might like to configure in-game. Then we have 'special logic' for the 2-6 builds for each class (about as many as there are Sets) and there are usually 1-2 meta builds per season. With that in mind, many of the sliders and check-boxes you've configured in combat settings have to be ignored because they don't apply to the way the build needs to be played. As a user, you have no visibility what special logic is being run or what settings are applicable to it.

Another factor to be considered is the ease of replication of issues. The more settings we have, the more everyone is seeing something different when the bot plays. If i can't replicate a problem then its stabbing around in the dark trying to fix it. Phelon's routine project was successful in this regard, you knew that when you ran his routine it would be run exactly how he intended it to. I know users enjoy fiddling with settings and so i don't want to completely take that away but i think there is a happy middle ground to be found.

Anyway, i'm not going to detail out my current plans to solve those issues right now but these are the problems i'm currently thinking through.

 

[kelson]

What i have realized is that we currently have a lot of settings where adjusting them is likely to just cause the bot to perform worse.
So simplification is what i am focusing on. As part of that, routines are being looked at.
My goal is to take what we learned from Phelon's routine experiment and build something that's easier for most users to just equip the build in-game and have it perform well out of the box.
I know users enjoy fiddling with settings and so i don't want to completely take that away but i think there is a happy middle ground to be found.

Sounds like a plan... and its really really nice!
Thanks for your work, you are great!

 

[Fdain]

Corrupt Growth - not being attacked

Hey Xz, great work on Trinity. I have a bug to report, regarding the "Corrupt Growth" mob type in act 4. They're the big blobs of bio-mass with a bunch of health that block the various pathways to complete A4 bounties and kill the A4 keywarden. My Uliana's monk tries to attack them with just basic attack instead of using Seven-Sided strike, even if there are a bunch of other mobs around which should trigger SSS. I've attached my log, let me know if you need anything else to follow up on this. Thanks!

View attachment 12048 2016-09-10 10-29.txt

 

[HitmanReborn]

Item Evaluation not working properly

I've noticed that in trinity .235, item rules incorrectly checks attack speed % bonus. It always seems to think that the item has 0%, but I noticed that trinity records AttacksPerSecondPercent properly in the junk and stash logs. The problem is only occurring during item evaluation.

Here's a small snippets from my logs from yesterday:

18:57:26.539 DEBUG Logger [Trinity 2.50.235]   >>  The Shadow's Grasp (24) is a selected Slot (Gloves) with 4 rules.
18:57:26.540 DEBUG Logger [Trinity 2.50.235]   >>  1 required rules:
18:57:26.540 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Shadow's Grasp -- Critical Hit Chance  (Item: 10 -v- Rule: 10) = True
18:57:26.540 DEBUG Logger [Trinity 2.50.235]   >>  item must have 2 of 3 optional rules:
18:57:26.541 DEBUG Logger [Trinity 2.50.235]   >>  [COLOR="#FF0000"]Evaluated The Shadow's Grasp -- Attack Speed  (Item: 0 -v- Rule: 7) = False[/COLOR]
18:57:26.541 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Shadow's Grasp -- Critical Hit Damage  (Item: 41 -v- Rule: 40) = True
18:57:26.541 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Shadow's Grasp -- Cooldown  (Item: 0 -v- Rule: 8) = False
18:57:26.541 DEBUG Logger [Trinity 2.50.235]   >>  The Shadow's Grasp (332362) is a selected Item with 5 rules.
18:57:26.542 DEBUG Logger [Trinity 2.50.235]   >>  2 required rules:
18:57:26.543 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Shadow's Grasp -- Ancient  (Item: 0 -v- Rule: 1) = False
18:57:26.543 DEBUG Logger [Trinity 2.50.235]   >>  Not stashing because of required rule failure: Ancient
18:57:26.543 INFO  Logger [Trinity 2.50.235] The Shadow's Grasp [Unique_Gloves_Set_14_x1] [Gloves] = ItemListCheck=TRASH

Same item from the junk log:

Armor - Gloves 'The Shadow's Grasp'. Score = 0 {legendary item}
Attributes: (27): 
  	CritDamagePercent  = 0.41 
  	CritPercentBonusCapped  = 0.1 
  	[COLOR="#FF0000"]AttacksPerSecondPercent  = 0.07[/COLOR] 
  	Requirement EquipItem = 70 
  	ThornsFixed Physical = 2444 
  	DexterityItem  = 735 
  	ItemQualityLevel  = 9 
  	DurabilityMax  = 319 
  	DurabilityCur  = 319 
  	ExperienceBonus  = 199 
  	ArmorItemTotal  = 556 
  	ArmorItemSubTotal  = 556 
  	SetItemCount -131645 = 1 
  	ArmorItem  = 556.3333 
  	Skill Weapon_Melee_Instant = 1

 

[xzjv]

I've noticed that in trinity .235, item rules incorrectly checks attack speed % bonus. It always seems to think that the item has 0%, but I noticed that trinity records AttacksPerSecondPercent properly in the junk and stash logs. The problem is only occurring during item evaluation.

Here's a small snippets from my logs from yesterday:

18:57:26.539 DEBUG Logger [Trinity 2.50.235]   >>  The Shadow's Grasp (24) is a selected Slot (Gloves) with 4 rules.
18:57:26.540 DEBUG Logger [Trinity 2.50.235]   >>  1 required rules:
18:57:26.540 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Shadow's Grasp -- Critical Hit Chance  (Item: 10 -v- Rule: 10) = True
18:57:26.540 DEBUG Logger [Trinity 2.50.235]   >>  item must have 2 of 3 optional rules:
18:57:26.541 DEBUG Logger [Trinity 2.50.235]   >>  [COLOR=#FF0000]Evaluated The Shadow's Grasp -- Attack Speed  (Item: 0 -v- Rule: 7) = False[/COLOR]
18:57:26.541 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Shadow's Grasp -- Critical Hit Damage  (Item: 41 -v- Rule: 40) = True
18:57:26.541 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Shadow's Grasp -- Cooldown  (Item: 0 -v- Rule: 8) = False
18:57:26.541 DEBUG Logger [Trinity 2.50.235]   >>  The Shadow's Grasp (332362) is a selected Item with 5 rules.
18:57:26.542 DEBUG Logger [Trinity 2.50.235]   >>  2 required rules:
18:57:26.543 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Shadow's Grasp -- Ancient  (Item: 0 -v- Rule: 1) = False
18:57:26.543 DEBUG Logger [Trinity 2.50.235]   >>  Not stashing because of required rule failure: Ancient
18:57:26.543 INFO  Logger [Trinity 2.50.235] The Shadow's Grasp [Unique_Gloves_Set_14_x1] [Gloves] = ItemListCheck=TRASH

Same item from the junk log:

Armor - Gloves 'The Shadow's Grasp'. Score = 0 {legendary item}
Attributes: (27): 
      CritDamagePercent  = 0.41 
      CritPercentBonusCapped  = 0.1 
      [COLOR=#FF0000]AttacksPerSecondPercent  = 0.07[/COLOR] 
      Requirement EquipItem = 70 
      ThornsFixed Physical = 2444 
      DexterityItem  = 735 
      ItemQualityLevel  = 9 
      DurabilityMax  = 319 
      DurabilityCur  = 319 
      ExperienceBonus  = 199 
      ArmorItemTotal  = 556 
      ArmorItemSubTotal  = 556 
      SetItemCount -131645 = 1 
      ArmorItem  = 556.3333 
      Skill Weapon_Melee_Instant = 1

This is exactly the info i need, thanks.

If you're ever suspecting issues with reading the values on an item, another way to check is to go to the Trinity tab and click 'Itemlist Check' while the item is in your backpack and it will print out a bunch of informatio (but you'll need DB logging set up to verbose to see it)

 

[Sneeds44]

ye the doors are opening fine it was my fault i changed destructebles to set to ignore that was wrong i changed it back to the default it it was opening doors again

 

[HitmanReborn]

This is exactly the info i need, thanks.

If you're ever suspecting issues with reading the values on an item, another way to check is to go to the Trinity tab and click 'Itemlist Check' while the item is in your backpack and it will print out a bunch of information (but you'll need DB logging set up to verbose to see it)

I tried out the 'Itemlist Check' option with a few items and noticed that Maximum Discipline isn't working at the moment either as seen in the following snippet, the item has +12 maximum discipline on it

19:42:03.627 DEBUG Logger [Trinity 2.50.235]   >>  Dead Man's Legacy (Quiver) is not a selected Slot
19:42:03.628 DEBUG Logger [Trinity 2.50.235] ------- Starting Test of 16 supported properties for Dead Man's Legacy
19:42:03.628 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Life Percent  (Item: 0 -v- Rule: 0) = True
19:42:03.628 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Critical Hit Chance  (Item: 8.5 -v- Rule: 0) = True
19:42:03.630 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Skill Damage  (Item: 0 -v- Rule: 0) = True
19:42:03.630 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Vitality  (Item: 0 -v- Rule: 1000) = False
19:42:03.645 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Area Damage  (Item: 20 -v- Rule: 0) = True
19:42:03.646 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Cooldown  (Item: 7 -v- Rule: 0) = True
19:42:03.646 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Resource Cost  (Item: 0 -v- Rule: 0) = True
19:42:03.646 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Thorns  (Item: 0 -v- Rule: 3500) = False
19:42:03.647 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Attack Speed  (Item: 0 -v- Rule: 0) = True
19:42:03.647 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Hatred Regen  (Item: 0 -v- Rule: 0) = True
19:42:03.647 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Sockets  (Item: 0 -v- Rule: 0) = True
19:42:03.648 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Damage Against Elites  (Item: 0 -v- Rule: 0) = True
19:42:03.648 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Regenerate Life Per Second  (Item: 0 -v- Rule: 7185) = False
19:42:03.648 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Maximum Discipline  (Item: 0 -v- Rule: 0) = True
19:42:03.648 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Ancient  (Item: 1 -v- Rule: 0) = False
19:42:03.649 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Primary Stat  (Item: 838 -v- Rule: 1000) = False
19:42:03.649 DEBUG Logger [Trinity 2.50.235] ------- Finished Test for Dead Man's Legacy against max value
19:42:03.649 DEBUG Logger [Trinity 2.50.235]   >>  Dead Man's Legacy (197630) is a selected Item with 7 rules.
19:42:03.650 DEBUG Logger [Trinity 2.50.235]   >>  3 required rules:
19:42:03.650 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Ancient  (Item: 1 -v- Rule: 1) = True
19:42:03.650 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Critical Hit Chance  (Item: 8.5 -v- Rule: 8) = True
19:42:03.651 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Primary Stat  (Item: 838 -v- Rule: 685) = True
19:42:03.651 DEBUG Logger [Trinity 2.50.235]   >>  item must have 2 of 4 optional rules:
[COLOR="#FF0000"]19:42:03.651 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Maximum Discipline  (Item: 0 -v- Rule: 9) = False[/COLOR]
19:42:03.652 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Vitality  (Item: 0 -v- Rule: 685) = False
19:42:03.652 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Cooldown  (Item: 7 -v- Rule: 8) = False
19:42:03.652 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Dead Man's Legacy -- Area Damage  (Item: 20 -v- Rule: 20) = True

 

[adjutantavocado]

Here are some problems I've noticed with the bot running this Helltooth Gargantuan build. The list is in order of importance, from my view.

1. Soul Harvest not being spammed off cooldown to maintain 5 (or 10) stacks
2. Gargantuan not being recast when encountering Elites/Champions
3. Endless Walk set bonus not being used properly (bot does not stand still when safe to do so)
4. Wall of Death not being spammed when off cooldown to maintain maximum dps

Also some minor feature suggestions:

1. Increase the priority value of health globe pick-up when Nephalem Glory stacks are about to run out (10 seconds left or something).
2. Have bot use Oculus Ring circle when safe to do so.

Anyway, keep up the great work. Been a user for a long time.

 

[HitmanReborn]

Item Rule property not working properly

Another property I've noticed that isn't being properly evaluated is Base Max Damage. For some items it will grab the first value to evaluate and for other items will take the second value to evaluate. Have no idea what it did in Windforce's case. Here's are some snippets:

[HIDE]Windforce: +1079-1330

07:10:13.968 DEBUG Logger [Trinity 2.50.235]   >>  Windforce (TwoHandBow) is not a selected Slot
07:10:13.968 DEBUG Logger [Trinity 2.50.235] ------- Starting Test of 17 supported properties for Windforce
07:10:13.969 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Vitality  (Item: 745 -v- Rule: 1000) = False
07:10:13.969 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Area Damage  (Item: 23 -v- Rule: 0) = True
07:10:13.969 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Cooldown  (Item: 0 -v- Rule: 0) = True
07:10:13.970 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Resource Cost  (Item: 0 -v- Rule: 0) = True
07:10:13.970 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Chance To Immobilize  (Item: 0 -v- Rule: 0) = True
07:10:13.970 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Chance To Blind  (Item: 0 -v- Rule: 0) = True
07:10:13.971 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Attack Speed  (Item: 0 -v- Rule: 0) = True
07:10:13.971 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Life Per Hit  (Item: 0 -v- Rule: 23950) = False
07:10:13.972 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Sockets  (Item: 0 -v- Rule: 0) = True
[COLOR="#FF0000"]07:10:13.972 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Base Max Damage  (Item: 394 -v- Rule: 1940) = False[/COLOR]
07:10:13.972 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Damage Against Elites  (Item: 0 -v- Rule: 0) = True
07:10:13.972 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Chance To Stun  (Item: 0 -v- Rule: 0) = True
07:10:13.973 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Chance To Freeze  (Item: 0 -v- Rule: 0) = True
07:10:13.973 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Maximum Discipline  (Item: 0 -v- Rule: 0) = True
07:10:13.973 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Percent Damage  (Item: 0 -v- Rule: 0) = True
07:10:13.974 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Ancient  (Item: 0 -v- Rule: 0) = False
07:10:13.974 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Windforce -- Primary Stat  (Item: 705 -v- Rule: 1000) = False
07:10:13.974 DEBUG Logger [Trinity 2.50.235] ------- Finished Test for Windforce against max value

The Demon's Demise: +1229-1490

07:10:13.903 DEBUG Logger [Trinity 2.50.235]   >>  The Demon's Demise (HandCrossbow) is not a selected Slot
07:10:13.904 DEBUG Logger [Trinity 2.50.235] ------- Starting Test of 19 supported properties for The Demon's Demise
07:10:13.904 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Skill Damage  (Item: 0 -v- Rule: 0) = True
07:10:13.905 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Vitality  (Item: 898 -v- Rule: 1000) = False
07:10:13.905 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Area Damage  (Item: 0 -v- Rule: 0) = True
07:10:13.906 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Cooldown  (Item: 0 -v- Rule: 0) = True
07:10:13.906 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Resource Cost  (Item: 10 -v- Rule: 0) = True
07:10:13.906 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Chance To Immobilize  (Item: 0 -v- Rule: 0) = True
07:10:13.907 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Chance To Blind  (Item: 0 -v- Rule: 0) = True
07:10:13.907 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Attack Speed  (Item: 0 -v- Rule: 0) = True
07:10:13.907 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Life Per Hit  (Item: 0 -v- Rule: 23950) = False
07:10:13.908 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Hatred Regen  (Item: 0 -v- Rule: 0) = True
07:10:13.908 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Sockets  (Item: 0 -v- Rule: 0) = True
[COLOR="#FF0000"]07:10:13.908 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Base Max Damage  (Item: 1490 -v- Rule: 1940) = False[/COLOR]
07:10:13.909 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Damage Against Elites  (Item: 0 -v- Rule: 0) = True
07:10:13.909 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Chance To Stun  (Item: 0 -v- Rule: 0) = True
07:10:13.909 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Chance To Freeze  (Item: 0 -v- Rule: 0) = True
07:10:13.910 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Maximum Discipline  (Item: 0 -v- Rule: 0) = True
07:10:13.910 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Percent Damage  (Item: 0 -v- Rule: 0) = True
07:10:13.910 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Ancient  (Item: 1 -v- Rule: 0) = False
07:10:13.911 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated The Demon's Demise -- Primary Stat  (Item: 932 -v- Rule: 1000) = False
07:10:13.911 DEBUG Logger [Trinity 2.50.235] ------- Finished Test for The Demon's Demise against max value

Natalya's Slayer: +1245-1544

07:10:13.952 DEBUG Logger [Trinity 2.50.235]   >>  Natalya's Slayer (HandCrossbow) is not a selected Slot
07:10:13.952 DEBUG Logger [Trinity 2.50.235] ------- Starting Test of 19 supported properties for Natalya's Slayer
07:10:13.953 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Skill Damage  (Item: 0 -v- Rule: 0) = True
07:10:13.953 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Vitality  (Item: 0 -v- Rule: 1000) = False
07:10:13.954 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Area Damage  (Item: 0 -v- Rule: 0) = True
07:10:13.954 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Cooldown  (Item: 0 -v- Rule: 0) = True
07:10:13.954 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Resource Cost  (Item: 0 -v- Rule: 0) = True
07:10:13.955 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Chance To Immobilize  (Item: 0 -v- Rule: 0) = True
07:10:13.955 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Chance To Blind  (Item: 0 -v- Rule: 0) = True
07:10:13.955 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Attack Speed  (Item: 0 -v- Rule: 0) = True
07:10:13.956 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Life Per Hit  (Item: 0 -v- Rule: 23950) = False
07:10:13.956 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Hatred Regen  (Item: 0 -v- Rule: 0) = True
07:10:13.956 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Sockets  (Item: 1 -v- Rule: 0) = True
[COLOR="#FF0000"]07:10:13.956 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Base Max Damage  (Item: 1245 -v- Rule: 1940) = False[/COLOR]
07:10:13.957 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Damage Against Elites  (Item: 0 -v- Rule: 0) = True
07:10:13.957 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Chance To Stun  (Item: 0 -v- Rule: 0) = True
07:10:13.957 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Chance To Freeze  (Item: 0 -v- Rule: 0) = True
07:10:13.958 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Maximum Discipline  (Item: 0 -v- Rule: 0) = True
07:10:13.958 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Percent Damage  (Item: 9 -v- Rule: 0) = True
07:10:13.958 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Ancient  (Item: 1 -v- Rule: 0) = False
07:10:13.959 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Natalya's Slayer -- Primary Stat  (Item: 923 -v- Rule: 1000) = False
07:10:13.959 DEBUG Logger [Trinity 2.50.235] ------- Finished Test for Natalya's Slayer against max value

Manitcore: +1387-1679

07:10:13.883 DEBUG Logger [Trinity 2.50.235]   >>  Manticore (TwoHandCrossbow) is not a selected Slot
07:10:13.883 DEBUG Logger [Trinity 2.50.235] ------- Starting Test of 18 supported properties for Manticore
07:10:13.884 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Vitality  (Item: 0 -v- Rule: 1000) = False
07:10:13.884 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Area Damage  (Item: 17 -v- Rule: 0) = True
07:10:13.885 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Cooldown  (Item: 0 -v- Rule: 0) = True
07:10:13.885 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Resource Cost  (Item: 0 -v- Rule: 0) = True
07:10:13.886 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Chance To Immobilize  (Item: 0 -v- Rule: 0) = True
07:10:13.886 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Chance To Blind  (Item: 0 -v- Rule: 0) = True
07:10:13.887 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Attack Speed  (Item: 0 -v- Rule: 0) = True
07:10:13.888 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Life Per Hit  (Item: 0 -v- Rule: 23950) = False
07:10:13.888 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Sockets  (Item: 1 -v- Rule: 0) = True
[COLOR="#FF0000"]07:10:13.890 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Base Max Damage  (Item: 1387 -v- Rule: 1940) = False[/COLOR]
07:10:13.891 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Damage Against Elites  (Item: 0 -v- Rule: 0) = True
07:10:13.891 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Chance To Stun  (Item: 0 -v- Rule: 0) = True
07:10:13.892 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Chance To Freeze  (Item: 0 -v- Rule: 0) = True
07:10:13.892 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Maximum Discipline  (Item: 0 -v- Rule: 0) = True
07:10:13.893 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Percent Damage  (Item: 9 -v- Rule: 0) = True
07:10:13.893 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Ancient  (Item: 1 -v- Rule: 0) = False
07:10:13.894 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Primary Stat  (Item: 833 -v- Rule: 1000) = False
07:10:13.896 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Manticore -- Passive Power  (Item: 42 -v- Rule: 0) = True
07:10:13.896 DEBUG Logger [Trinity 2.50.235] ------- Finished Test for Manticore against max value[COLOR="#FF0000"][/COLOR]

Sever: +1073-1277

07:10:13.934 DEBUG Logger [Trinity 2.50.235]   >>  Sever (Sword) is not a selected Slot
07:10:13.935 DEBUG Logger [Trinity 2.50.235] ------- Starting Test of 16 supported properties for Sever
07:10:13.935 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Vitality  (Item: 0 -v- Rule: 1000) = False
07:10:13.935 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Area Damage  (Item: 0 -v- Rule: 0) = True
07:10:13.936 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Cooldown  (Item: 0 -v- Rule: 0) = True
07:10:13.936 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Resource Cost  (Item: 0 -v- Rule: 0) = True
07:10:13.936 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Chance To Immobilize  (Item: 0 -v- Rule: 0) = True
07:10:13.937 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Chance To Blind  (Item: 0 -v- Rule: 0) = True
07:10:13.937 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Attack Speed  (Item: 0 -v- Rule: 0) = True
07:10:13.938 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Life Per Hit  (Item: 18000 -v- Rule: 23950) = False
07:10:13.938 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Sockets  (Item: 0 -v- Rule: 0) = True
[COLOR="#FF0000"]07:10:13.938 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Base Max Damage  (Item: 1277 -v- Rule: 1940) = False[/COLOR]
07:10:13.939 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Damage Against Elites  (Item: 0 -v- Rule: 0) = True
07:10:13.939 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Chance To Stun  (Item: 0 -v- Rule: 0) = True
07:10:13.940 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Chance To Freeze  (Item: 0 -v- Rule: 0) = True
07:10:13.940 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Percent Damage  (Item: 8 -v- Rule: 0) = True
07:10:13.941 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Ancient  (Item: 0 -v- Rule: 0) = False
07:10:13.941 DEBUG Logger [Trinity 2.50.235]   >>  Evaluated Sever -- Primary Stat  (Item: 680 -v- Rule: 1000) = False
07:10:13.941 DEBUG Logger [Trinity 2.50.235] ------- Finished Test for Sever against max value

[/HIDE]

 

[Ghastis]

I made some changes in one of the files inside trinity and when I restarted the BOT the Trinity plugin option was gone. I deleted the folder and reinstalled with the same result so can anyone help me out on how to get the trinity plug in function back working?

 

[xzjv]

I made some changes in one of the files inside trinity and when I restarted the BOT the Trinity plugin option was gone. I deleted the folder and reinstalled with the same result so can anyone help me out on how to get the trinity plug in function back working?

It could be related to settings your changes made; if you just removed the plugin; try removing the entire DB folder, or just creating a new one somewhere to test it and really start from scratch from the DemonBuddy zip/installer.

Here are some problems I've noticed with the bot running this Helltooth Gargantuan build. The list is in order of importance, from my view

Thanks for the feedback.

Another property I've noticed that isn't being properly evaluated is Base Max Damage. For some items it will grab the first value to evaluate and for other items will take the second value to evaluate. Have no idea what it did in Windforce's case. Here's are some snippets:

I'll look into these. Thanks.

 

[xzjv]

I became inspired this morning

The next release will have a new thing for advanced users, an item-list rule type called 'Attribute' which will check against any attributes you feel like using.

518: WeaponRanged (-3578) i:0 f:1 Value=1
516: Weapon2H (-3580) i:0 f:1 Value=1
1123: ItemManipulationTimeout (-2973) i:0 f:0 Value=0


[Trinity 2.55.238] >> Natalya's Slayer (HandCrossbow) is not a selected Slot
[Trinity 2.55.238] ------- Starting Test of 20 supported properties for Natalya's Slayer
...
[Trinity 2.55.238] ------- Finished Test for Natalya's Slayer against max value
[Trinity 2.55.238] >> Natalya's Slayer (210874) is a selected Item with 1 rules.
[Trinity 2.55.238] >> 1 required rules:
[Trinity 2.55.238] >> Evaluated Natalya's Slayer -- Attribute Weapon2H 1 (Item: 1 -v- Rule: 1) = True


-----------------------------------------------------------------------------------------------------------------------------------------

233: DamageWeaponAverageTotal (-3863) [ DamageType: Cold: 3 ] i:0 f:1564.38 Value=1564.38

[Trinity 2.55.238] >> Evaluated Natalya's Slayer -- Attribute DamageWeaponAverageTotal 3 1500 (Item: 1564.38 -v- Rule: 1500) = True

It's totally not something you would want to use all the time... but for those few specific cases where a user-friendly version of the property is not available yet, or when new powers/items are introduced, savvy people will still have a way to evaluate against it.

 

[Aleks 1234]

Trinity 2.50.235 version is much worse and slower than the version Trinity 2.50.231 to build
[2.4.2] Witchdoctor - GR90+ / T13 Helltooth Garg (season 7) - Witch Doctor - Diablo III Builds - Diablo Fans
Portal 79 takes place on 3-4 minutes slower

 

[xzjv]

2.50.237

• Fixed ExploreGoblinRealm.xml profile.less
• Monk: Should attack faster with ThousandStormsGenerator (use a high TPS setting)
• Adventurer: Removed FullyPathable check from MoveToActorCoroutine as it was giving false failures in some situations (ie goblin realm boss chest)
• Adventurer: Updated MoveToScenePositionCoroutine to work outside of bounties.
• Fixed a bug with that prevented removing specific quantities of items from stash if when not stackable.
• Adjusted item required ranges for stuck issue picking up items and barricades with melee-range attacks.
• Blocked detection (attacking with blocked) should now trigger faster
• Migrated QT's TownRun tag and Conditions to Trinity
• ProfileTags: Renamed ExploreLevelArea to Explore.
• ProfileTags: InteractTag now works without a specified position.
• ProfileTags: Added - TakeFromStash.
• ProfileTags: MoveToPosition now uses a scene relative position where possible for dynamic worlds
• Weighting: Fixed an issue with destructible weighting that could cause a flip/flop at medium range.
• Adjusted collision radius for better barricades
• WD: Removed CoilsOfTheFirstSpider from being a required item of the IsHellToothFirebats build.
• Monk: Thousand Storms Generator build: While shenlongs damage buff is active it will now focus on killing.less
• WD: Experimental changes to Helltooth Firebats build.
• Exploration: Fixed stuttering movement due to exploration nodes not being marked as visited properly
• Visualizer: Added checkbox for adventurer exploration nodes.
• Improvements to detecting debuffs on units.

 

[Anonuzer01]

Anything that can be done to improve combat against Mathiel, especially with a Bombardment Crusader? I can destroy everything on T13 and GR up to around 74 but I can't do anything with that dude.

Edit: Dropped it down to T10 and easy enough. Trying to gather some mats, will just run it there.