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

Trinity 2.8.1 and QuestTools 3.4.2

Status
Not open for further replies.
DH:

Just a few quick observations:

1. When the DH kites he shoots in the wrong direction (using UE, evasive fire/multishot is used 2 or 3 times before he even starts moving), in the direction he is kiting towards, or just a random direction without target.

2. DH spams SS so often even when the setting is turned off. You will frequently be out of disc. He spams SS when enemy moves near him, SS when he walks. When I'm using SS with healing vapors, I don't want to spam SS at all, only when the DH is low or for avoidance. (This behavior has been around since early v2.x).

I looked through the log, its just this (for a bounty):
Code:
[QuestTools][ExploreDungeonTag] ExploreDungeon Started
[QuestTools][MiniMapMarker] Adding MiniMapMarker -431250551 at <576.9863, 1244.036, 9.730615>, IsPOI: True, IsExit: False, Distance: 436 to KnownMarkers
[QuestTools][ExploreDungeonTag] Found exitNameHash -431250551!
[Trinity] Clicking UI element Conversation Button (519235888)
[QuestTools][MoveToMapMarkerTag] ReachedDestination, no object found - finished!
[QuestTools][GameUI] Clicking UI element Conversation Button (519235888)
Looking for 347060 or 204032

3. Final observation, DH walks INTO the mobs, sometimes very deep into a pack, most of the times right beside the first mob. It doesn't even take into account the range trigger setting. Just right beside the mobs, which disables the UE4p passive as well as Steady Aim passive, reducing potential DPS output by a lot.
 
Last edited:
Once again QuestTools' "Stop trial at wave XX" isn't working. Just woke up to my DH having blown 30+ greater rift trial keys into keys he can't use because they're too high, even tho I set the wave number super low.
 
The bot still takes all the fire bomb aoe... I mean ALL. In the settings I have also enabled the check to "Disable Looting on AoE or Near Elites" but it still goes in and take the fire bomb in tha face :D. Is there a fix to this?
 
Is anyone else having issues on Rift Guardians? Bot seems to be waiting for loot before he attempts to even engage and kill him?

Using Dashing Monk

***Fresh install definitely still standing next to Rift Guardians and waiting for loot, never attacking. Makes Greater Rifts unable to complete. Eventually they AFK timer kicks in and it restarts.... Attached a log

View attachment 11164 2015-04-20 09.45.txt
 
Last edited:
Thank you for your constant contribution to keeping things alive!

I am unsure if this is a suitable place for requests but...here it is.

I am curious if Triumvirate support is on the to do list. Keeping this buff up would help immensely! Also refreshing Focus+Restraint (hitting with a resource generating attack, while having sufficient resource to cast a resource spending ability) seems to be an issue as well.

Aside from that, things worked well over night! Thank you again.
 
Once again QuestTools' "Stop trial at wave XX" isn't working. Just woke up to my DH having blown 30+ greater rift trial keys into keys he can't use because they're too high, even tho I set the wave number super low.

Strange...Are you sure u choose the right number? Do you now that if you choose "Disable at wave 35" - he will disable not on Wave lv 35 , but only after defeating 35 waves. Choose number 7-8 and he wil get you 35-40 lv keys
 
There is a problem with a Dashing Strike on a Monk.

Sometimes bot will use Dashing Strike until all of it's charges are gone. This happens mostly when bot is stack in a group of mobs or avoiding molten explosion, lighting orb or grotesque explosion. Bot will stupidly charge in the center of those areas. However in my bot settings bot is set to ignore any avoidance (double Unity FTW). That problem also persisted in 2.5.2.

The interesting thing that while performing this action, bot doesn't use MonkCombat rotation script nor PlayerMovement OOC script (I debugged both usages). I don't get how bot manages to pull that cast, but for Dashing Strike build loosing those stacks are crucial. Is there another script that calls for this ability? Looking forward for a response!

P.S.: Thank you very much for .Charges property in 2.8.0! Being able to get extra dash every 8 seconds results in a 50+ dashes for a run. That's huge.

Also this:

Is anyone else having issues on Rift Guardians? Bot seems to be waiting for loot before he attempts to even engage and kill him?
 
Last edited:
Compatible with DB 404 / DB Beta Build 518.

Trinity changelog (not much changed in QuestTools, just a compatability update):

Major features of 2.8.0:
  • xzjv totally remodeled the DemonHunter combat design. This makes it easier to re-prioritize but will take some getting used-to for those who like to make modifications. It's for the better. Feedback appreciated!
  • Re-added a bunch of useful features that were developed with BuddyMe.
  • Added window to see into the Trinity cache in real time.


2.8.0 change notes:
ItemList: fix for Attack speed on weapons
Moved Weights.cs from Combat directory to Cache directory
DemonHunterCombat support for Natalyas Set, Added a couple new A4 Obstacles
Fixed ClusterArrow & EvasiveFire, More Optimizations, Improved Logging.
Added 'SkillSelection' log category in advanced tab to debug ability selection.
Re-factored and Polished SkillMeta system.
Moved all CastRange settings to Combat area.
Added clone ability to FieldCollection
Moved setting of all defaults to the Defaults delegate
Added calling class/method helper to Logger
Moved GetCombatPower's logging to CombatBase and set to Verbose
Now Routing all ToPower calls through CombatBase.GetTrinityPower()
Now uses 50% of MaxTargetDistance if CastRange has not been set.
Added 'SkillMeta' based combat/abilities system (currently just DemonHunter)
Added setting in Advanced to allow duplicate log messages
Re-factored DemonHunterCombat for readability (mostly the same logic)
Added mpre ItemIds, thanks Winkoo and Oggy2k5
ItemList: Fix for broken property in DB for Black/Physical weapon damage.
Fixed CacheUpdate event not always being invoked
Added game completion dialog button clicking
Refactored MonkCombat if statements to methods
Added 2 new items and some more Ids (thanks BuddyMe)
2.7.1
Added charges check to monk dashing strike
Collected new Skills/Runes/Passives for 2.2. Fixed Bastian Buffs, DH Combat Improvements.
Removed some logging from WizardCombat
Added TimeSinceGeneratorCast and TimeSinceSpenderCast to SpellHistory
DH should use Vengeance and Multishot more.
Parsed new properties IsDamaging, AreaEffectRadius and IconSlug for Skills,Runes,Passives
Merged over some more stuff in Skills.cs from before rollback
Removed TVar's from Barbarian Rend stuff. Rend parameters are now hard-coded (TVar's aren't working very well...)
Re-added Resources/JS Class Generator stuff
Rend SpellDelay TVar default => 3500 millisec
Re-added Legendary Gems CacheData.Inventory fix
Re-added regular potion fix (D3 2.2.0)
Re-added Skill Charges
Re-added Crusader DestroyObjectPower
Re-added goblin identification by internal name
Re-added CacheUI stuff
Cleaned up some noisy logging
More optimization on Monk dashing strike w/ Raiment of a Thousand Storms
Added Directional avoidance animations - avoidance should now be triggered for mallet lords only when they're facing the player


Trail rifts disable combat after wave not working Screenshot by Lightshot fix pls
 
well my dh cant do now gr 31 without diying :D....
i use uh set with kridershot. it fails to use elematal arrow as generator it shoots normal arrows.
dh moves into arcane and other affix it wont kite.
i go back to 2.7 atm more stable for demonhunter.

here is my log. hope u can fix it

View attachment 5112 2015-04-20 16.27.txt.zip
 
rrixx can you add the Zei's Hydra support from BuddyMe? It adds much damage for wizard and it's way better for wizard with Zei's

I can't use anything from the fork. Can you link a build that you would like implemented and we get get it going?

We have a bit of a backlog with a lot of other stuff in the works.
 
wave 35? i doubt your bot can reach such wave to disable.

rrrix hear me out. Please set the wave limit lower. Because there is no wave 40+.
Or put an information into quest tools "wave 6 = grift 20". This confuses soooo many people. :)
 
rrrix hear me out. Please set the wave limit lower. Because there is no wave 40+.
Or put an information into quest tools "wave 6 = grift 20". This confuses soooo many people. :)
Yep, if he wants gr35 keys, he should stop at wave 8.
 
rrrix hear me out. Please set the wave limit lower. Because there is no wave 40+.
Or put an information into quest tools "wave 6 = grift 20". This confuses soooo many people. :)

This is an option. You can set it whatever you want.
 
Status
Not open for further replies.
Back
Top