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

rrrix

rrrix

New Member
Joined
Jul 11, 2010
Messages
3,449
Reaction score
61
For New Demonbuddy builds - not compatible with previous versions of Demonbuddy.

Demonbuddy BETA .519 and Release v405 already include the new Trinity and QuestTools ​


Trinity changelog

2.9.0
HandleTarget special movement will no longer be used in Town
LazyCache: Replaced MonsterInfo/ActorInfo and a few other properties with new ActorMeta Dictionary.
* Misc refactoring for fixes and performance.
* Changes should not effect DB's current operation at all.
Added TrinityMonsterAffix Mapping of Affixes by GBid
Fix for Legendary Item Markers while Picking up Legendaries is turned off.
Fix for Max BloodShards
Updated for Build 1.1.2296.24 + LazyCache work as follows.
* Expanded weighting and started reworking Unit weights
* Custom Implementation of ActorInfo, MonsterInfo
* Fix for detecting and avoiding bad DiaUnits
* Performance Improvements
* Added methods for CacheBase .ToTrinityUnit() .ToTrinityObject() etc.
LazyCache changes that should not effect DB running
* These files are disconnected from DB unless CacheUI is running or LazyCache is explicitly started.
* Minor changes to DataDictionary and PerformanceLogger.
Reverted files effected by the variable name change in commit "Prototype Weighting and LazyCache Updates"
* then manually merged newer changes to these files so they're up date.
Fixed WizardCombat not prioritizing destructibles when needed
HandleTarget now logs which section it returned RunStatus from
Fixed TownRun trying to start on Campaign 1st quest
Added hax for Demonbuddy Memory reading stupidity in BotManager -> Emergency Repair logic
Split prototype weighting into files for each type.
* Moved CombatContext to \Combat
* Moved all Weighting related to \Combat\Weighting
* Added tick param to Worker()
* Added support for CacheUI/LazyCache without bot running.
* Misc fixes on LazyCache props and weighting.
* Filtered Unit ActorTypes that aren't actually units by MonsterType.
Fix for Legendary detection
Ghost doc'd Extensions
Made a DIY wrapper for ItemStackQuantity
Removed CombatBase.CanCast check for ReUseDelay
Added try/catch for GetItemStackCount so it doesn't break townrun
Removed Ad-Hoc CanCast stuff from CombatBase, as it was getting weird with DH Avoidance logic
Several performance improvements in legacy cache - 8-10% improvement
InventoryCache now only reads Backpack ItemSetName
Reverted BarbarianCombat to legacy style - new format just doesn't work well in this case
Fixed up DemonHunter combat to work better with AoD'''s Nat Solo GR 54+ (/w video) Rain of vengeance Guide - Demon Hunter - Diablo III Builds - Diablo Fans
DemonHunter strafe is now used in movement
Cleaned up Monk Combat code a bit
Prototype Weighting and LazyCache Updates.
Fixed Spelling Mistake and updates to LazyCache
* Heavily Refactored LazyCache for better performance
* Added a panel in CacheViewer for LazyCache
Fixed incorrect class mapping for HealthGlobeLevelResource
Fixed DH combat settings never being applied (reverted to old methods)
BarbarianCombat - started converting to new Combat class style
LazyCache: Added more stuff, juicy juicy stuff.
Expanded on LazyCache, populated more objects. Added TabUI buttons to test.
Added prototype caching system called LazyCache.
Renamed Enums: GItemType to TrinityItemType, GItemBaseType to TrinityItemBaseType, GObjectType to TrinityObjectType
Modified how legendary minimap markers are added to cache and blacklisted. Legendary markers > 300 yards will not be added.
DH fires Rain of Vengeance even more, and walks into groups of mobs less.
DH Combat - Natalyas
* Reduced the time bot spends per-emptively trying to refresh bastian.
* Moved Rain of Vengeance to a higher priority.
* Bot will now ensure bastian spender is up before casting combat spells.
Fixes for Preparation & Vault. Added ReUseDelay to Meta.
* meta.ReUseDelay can prevent a skill from being used again for a time after use.
* Removed bad ItemId for Hwoj Wrap.
* Added some utility Extensions
* Fixed exception on GetValueOrDefaultAttribute when no default attribute found.
* Lowered default skill delay Before/After to 50ms (was 100ms)
Fixed WW OOC movement also letting regular movement be used


QuestTools changelog

Updated for new DB
Added check for Rift Trial Enabled in RiftTrial.cs
 

Attachments

Last edited:
I feel like my monk doesnt care that I need to have more than 75 spirit. Im in situation with dashing strike cool down all the time. this might be my end problem, I just dont understand why this happens
 
For you guys having problems with barb and WOTB, this should fix your problems :).
 
jubisman said:
Uh, I forgot about that part, sorry. Should be easy enough to fix, gimme a minute.

edit: there you go, now it'll use WOTB as soon as you're out of town if you have "When not on Cooldown" checked
Click to expand...
Now its working!
Thanks!
 
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
 
Last edited:
trinity ignores min hatered to use strafe. it uses it no matter what you set the min too. any fix for this?
 
@ rrrix, xzjv,

Only item i found missing so far.


[Trinity] ------ New/Unknown Items 1 ------
[Trinity] Item: Belt: Omnislash (423250)
 
having some issues with my barb... he is not using ww anytime. anyone else have this problem? taeguk always falling down -.-
 
jubisman said:
Uh, I forgot about that part, sorry. Should be easy enough to fix, gimme a minute.

edit: there you go, now it'll use WOTB as soon as you're out of town if you have "When not on Cooldown" checked
Click to expand...

Where i must copy this file please ?

THx
 
I'm making good progress on addressing some core issues with Trinity that make it difficult for us to work and to debug issues.

The heart of it will be a new Caching system and a new Weighting system (neither of which are actually hooked up yet). We aim to get some more separation of concerns going so that caching is responsible for just that, targeting responsible for targeting, weighting for... you guessed it - weighting. etc and we don't have every piece of code interwoven with each other and doing small parts of every job.

The new caching is designed to request stuff from Diablo3/DB as few times as possible. We will be able to set each field to refresh at different speeds. So that things like the position of monsters can update quickly, while things that never change or change slowly can be requested less frequently.

The weighting system is designed for greater visibility into how the weight is being calculated and so we can request a weight be calculated on an individual object rather than having to weight everything at once.

Anyway, thought some of you might be interested in whats up with the large and weird check-ins on assembla.

The bottom line is that we hope to improve TPS and make things easier for ourselves moving forward.

dVEZoTJ.png


PS: CacheUI is by rrrix, i just hijacked it.
 
Last edited:
xzjv said:
I'm making good progress on addressing some core issues with Trinity that make it difficult for us to work and to debug issues.

The heart of it will be a new Caching system and a new Weighting system (neither of which are actually hooked up yet). We aim to get some more separation of concerns going so that caching is responsible for just that, targeting responsible for targeting, weighting for... you guessed it - weighting. etc and we don't have every piece of code interwoven with each other and doing small parts of every job.

The new caching is designed to request stuff from Diablo3/DB as few times as possible. We will be able to set each field to refresh at different speeds. So that things like the position of monsters can update quickly, while things that never change or change slowly can be requested less frequently.

The weighting system is designed for greater visibility into how the weight is being calculated and so we can request a weight be calculated on an individual object rather than having to weight everything at once.

Anyway, thought some of you might be interested in whats up with the large and weird check-ins on assembla.

The bottom line is that we hope to improve TPS and make things easier for ourselves moving forward.

dVEZoTJ.png


PS: CacheUI is by rrrix, i just hijacked it.
Click to expand...
I understand shiat, but in you I trust ;)
 
Issues i've found so far:

When using 2 x Bul kathos weapon, its not spamming WW
Its not using WOTB of cooldown - even when its marked like this.
 
WoTB Not working on coodown

trolderik said:
Issues i've found so far:

When using 2 x Bul kathos weapon, its not spamming WW
Its not using WOTB of cooldown - even when its marked like this.
Click to expand...

WoTB on Cooldown checked but it's only firing on elites. Have done a full EzUpdater pull and still happening. Log attached.
 

Attachments

You must log in or register to reply here.
Back
Top