harvest655
Member
- Joined
- Apr 26, 2014
- Messages
- 98
- Reaction score
- 0
How to limit the minimum number of dashing-strike reserved
Trinity 2.8.1 and QuestTools 3.4.2
- Thread starter rrrix
- Start date
- Status
Fujiyama
Member
- Joined
- Mar 27, 2014
- Messages
- 485
- Reaction score
- 4
rrrix gonna give it to ya
botheric
Member
- Joined
- Mar 5, 2014
- Messages
- 259
- Reaction score
- 4
I guess you missed my post along everything
Any chance you could post you MonkCombat.cs and maybe few tips how is your bot set up for GR? I keep tweaking my gear, but my bot dies 20+ times in GR rift due to just dumb behavor, like dashing through whole map and not actually finishing off any mob.With new trinity I run into problem that if Rift Guardian don't spawn on my head, bot seems to seach whole map and next levels (due to dashing too far away). Only happened twice so far.
Fujiyama
Member
- Joined
- Mar 27, 2014
- Messages
- 485
- Reaction score
- 4
I guess you missed my post along everything
With new trinity I run into problem that if Rift Guardian don't spawn on my head, bot seems to seach whole map and next levels (due to dashing too far away). Only happened twice so far.
Can you post your trinity combat settings? I can have a look
I think rrrix fixed that last problem in QuestTools or the newest R-Rift. I'll see if I can find the time to upload my changes as I'm at work atm. Have not yet merged with 2.8.3 but it's working good with 2.8.1.
harvest655
Member
- Joined
- Apr 26, 2014
- Messages
- 98
- Reaction score
- 0
Trinity 2.8.1
1.Dashing strike not leave a number of times for the lowest
2.Dashing strike need to keep moving to create harm, not standing still create harm, constantly moving to avoid death
3. When in groups of elite monsters, one should point to point movement is not fixed in front of an elite monster, should be constantly alternating between two elite monsters use Dashing strike, or a monster to do with ordinary point to point mobile
4.OOC exhausted dashing strike, so completely unable to attack monsters
5.dashing strike too close, should be to pick the farthest distance, dashing strike will cause the entire path will have hurt
6.If dashing strike with dodge, will be perfect
7.On the rift final boss, miss probability is very large, can not hurt
Trinity Fork done well in this regard, hoping to improve on top of these shortcomings
1.Dashing strike not leave a number of times for the lowest
2.Dashing strike need to keep moving to create harm, not standing still create harm, constantly moving to avoid death
3. When in groups of elite monsters, one should point to point movement is not fixed in front of an elite monster, should be constantly alternating between two elite monsters use Dashing strike, or a monster to do with ordinary point to point mobile
4.OOC exhausted dashing strike, so completely unable to attack monsters
5.dashing strike too close, should be to pick the farthest distance, dashing strike will cause the entire path will have hurt
6.If dashing strike with dodge, will be perfect
7.On the rift final boss, miss probability is very large, can not hurt
Trinity Fork done well in this regard, hoping to improve on top of these shortcomings
Last edited:
Everytime Preparation is casted (DemonHunter), Bot stands still do nothing for almost 10 secs.
Code:
16:29:14.003 INFO Logger [Trinity][Targetting] Calculating TargetPosition for Preparation as Self. CurrentTarget=Corpulent_A
16:29:14.003 DEBUG TrinityDebug [Trinity][Behavior] Selected new power=DemonHunter_Preparation pos=x="0" y="0" z="0" acdGuid=-1 preWait=1 postWait=150 timeSinceAssigned=0 timeSinceUse=63565284554003.1 range=0
16:29:14.003 DEBUG TrinityDebug [Trinity][Behavior] Object in Range: noRangeRequired=True Target In Range=True stuckOnTarget=False npcInRange=False
16:29:14.003 DEBUG TrinityDebug [Trinity][Targetting] Attack Target=Corpulent_A Power=DemonHunter_Preparation Speed=0.45 SNO=3847 Elite=True Weight=50000 Type=Unit C-Dist=3.6 R-Dist=0.0 RangeReq'd=0.0 DistfromTrgt=0 tHP=90 MyHP=83 MyMana=166 InLoS=True Duration=0
16:29:14.004 INFO Logger [Trinity][Behavior] Used Power Preparation (129212) Range=0 (Other Buff) Delay=100/15000 TargetDist=3521.9 CurrentTarget=Corpulent_A
16:29:14.004 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree IsWaitingAfterPower ForceTargetUpdate CPowerShouldWaitBefore=65.0017 CPowerShouldWaitAfter=9900 power=DemonHunter_Preparation pos=x="0" y="0" z="0" acdGuid=-1 preWait=1 postWait=150 timeSinceAssigned=0.9983 timeSinceUse=0 range=0
16:29:14.199 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree IsWaitingAfterPower ForceTargetUpdate CPowerShouldWaitAfter=9704.9487 power=DemonHunter_Preparation pos=x="0" y="0" z="0" acdGuid=-1 preWait=1 postWait=150 timeSinceAssigned=196.0496 timeSinceUse=195.0513 range=0
16:29:14.248 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree IsWaitingAfterPower ForceTargetUpdate CPowerShouldWaitAfter=9655.9237 power=DemonHunter_Preparation pos=x="0" y="0" z="0" acdGuid=-1 preWait=1 postWait=150 timeSinceAssigned=245.0746 timeSinceUse=244.0763 range=0
16:29:14.349 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree IsWaitingAfterPower ForceTargetUpdate CPowerShouldWaitAfter=9554.9108 power=DemonHunter_Preparation pos=x="0" y="0" z="0" acdGuid=-1 preWait=1 postWait=150 timeSinceAssigned=346.0875 timeSinceUse=345.0892 range=0
~~~~~~~~~~~~~~ Same logs for 10 secs ~~~~~~~~~~~~~~~~~~
16:29:23.644 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree IsWaitingAfterPower ForceTargetUpdate CPowerShouldWaitAfter=259.4979 power=DemonHunter_Preparation pos=x="0" y="0" z="0" acdGuid=-1 preWait=1 postWait=150 timeSinceAssigned=9641.5004 timeSinceUse=9640.5021 range=0
16:29:23.745 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree IsWaitingAfterPower ForceTargetUpdate CPowerShouldWaitAfter=158.4717 power=DemonHunter_Preparation pos=x="0" y="0" z="0" acdGuid=-1 preWait=1 postWait=150 timeSinceAssigned=9742.5266 timeSinceUse=9741.5283 range=0
16:29:23.813 DEBUG TrinityDebug [Trinity][Behavior] HandleTarget returning Running to tree IsWaitingAfterPower ForceTargetUpdate CPowerShouldWaitAfter=91.4537 power=DemonHunter_Preparation pos=x="0" y="0" z="0" acdGuid=-1 preWait=1 postWait=150 timeSinceAssigned=9809.5446 timeSinceUse=9808.5463 range=0
16:29:23.948 DEBUG TrinityDebug [Trinity][Weight] Starting weights: packSize=2 packRadius=35 MovementSpeed=0.0 Elites=3 AoEs=0 disableIgnoreTag=False (MoveToObjectiveTag) closeRangePriority=False townRun=False questingArea=False level=70 isQuestingMode=False healthGlobeEmerg=False hiPriHG=False hiPriShrine=False
16:29:23.948 DEBUG TrinityDebug [Trinity][Weight] Weight=20993 name=QuillDemon_FastAttack_A sno=364563 type=Unit R-Dist=5 IsElite=False RAGuid=-470613947 Adding ShouldIgnore=False nearbyCount=1 radiusDistance=5 hotspot=False elitesInRange=False hitPointsPc=0.7 summoner=False quest=False minimap=False bounty=False IsTrash CloseRange10f
16:29:23.948 DEBUG TrinityDebug [Trinity][Weight] Weight=50000 name=Corpulent_A sno=3847 type=Unit R-Dist=4 IsElite=True RAGuid=-481230791 Adding shouldIgnore=False hitPointsPct=82 IsBossOrEliteRareUnique XtraPriority CloseRange10f MaxWeight
Last edited:
botheric
Member
- Joined
- Mar 5, 2014
- Messages
- 259
- Reaction score
- 4
If you're like me, you can stalk rrrix's work right here -- > https://www.assembla.com/profile/rrrix1
Link for Questtools -- https://www.assembla.com/code/questtools/git/nodes
Barbarian Whirlwind will now always be used if Bul-Kathos's Sword Set is equipped - NEEDS TESTING - My barb doesn't have the 2 BK set
Tested on - Beta DB 517, Trinity 2.8.1, Quest Tools 3.3.12 and of course 2BK Weapons
- Whirlwinds much more consistently, specially for movement, out of range targets, and doesn't abuse it in town which is perfect. At times, it'll drop Taeguk, but not as much as it did before, I guess this was more focused on, whirlwinding for speed rather than gem up time.
However, with that said, I have noticed two bugs, once you've killed the Rift guardian, it'll constantly WW until it is out of Fury before looting, I guess this is due to either the animation of the RG dying, or infact due to the constant WW being "just that good"
The other bug is when you're doing bounties, it'll have trouble teleporting, due to constant WWing, it'll constantly go to new areas in Act 1 as many of them link together.
Beggers can't be choosers, right?
Thanks for a good update for the Barbs RRRIX
Tested on - Beta DB 517, Trinity 2.8.1, Quest Tools 3.3.12 and of course 2BK Weapons
- Whirlwinds much more consistently, specially for movement, out of range targets, and doesn't abuse it in town which is perfect. At times, it'll drop Taeguk, but not as much as it did before, I guess this was more focused on, whirlwinding for speed rather than gem up time.
However, with that said, I have noticed two bugs, once you've killed the Rift guardian, it'll constantly WW until it is out of Fury before looting, I guess this is due to either the animation of the RG dying, or infact due to the constant WW being "just that good"
The other bug is when you're doing bounties, it'll have trouble teleporting, due to constant WWing, it'll constantly go to new areas in Act 1 as many of them link together.
Beggers can't be choosers, right?
Thanks for a good update for the Barbs RRRIX
Last edited:
Xenetron
Member
- Joined
- Mar 5, 2013
- Messages
- 627
- Reaction score
- 4
2.2 Tal Rasha Solo (GR50) - Wizard - Diablo III Builds - Diablo Fans
Support for this build would be awesome Rrrix
Support for this build would be awesome Rrrix
lovelygasaiyuno
New Member
- Joined
- Mar 28, 2015
- Messages
- 5
- Reaction score
- 0
it can't such normal rift bosses. so i use 2.5 now
Fujiyama
Member
- Joined
- Mar 27, 2014
- Messages
- 485
- Reaction score
- 4
Can you post your trinity combat settings? I can have a look
I think rrrix fixed that last problem in QuestTools or the newest R-Rift. I'll see if I can find the time to upload my changes as I'm at work atm. Have not yet merged with 2.8.3 but it's working good with 2.8.1.
Here are my latest, still 2.8.1 though.
ariyako
Member
- Joined
- Nov 20, 2013
- Messages
- 30
- Reaction score
- 2
thanks
xzjv
Community Developer
- Joined
- Mar 17, 2014
- Messages
- 1,243
- Reaction score
- 46
Yes thanks for pointing this out, those delays look wrong Delay=100/15000. shouldn't be 15,000 / preWait=1 postWait=150
Acps
New Member
- Joined
- Dec 24, 2011
- Messages
- 347
- Reaction score
- 0
Never had the QuestTools one, thanks. Bookmarked!
Acps
New Member
- Joined
- Dec 24, 2011
- Messages
- 347
- Reaction score
- 0
Super interested in what changes you make to fix this. I would rather it revive at checkpoint as well and TP to repair and rerun the rift. I miss out on a lot of gem upgrades, happens if i get a decent 46-48 grift and destroy the timer then proceed to get a terrible 49-51 with terrible affixes!
I think the death logic could be a bit better. Sometimes he just refuses to get far enough from the Elites to TP to repair and will just end up leaving the game.
Last edited:
Fujiyama
Member
- Joined
- Mar 27, 2014
- Messages
- 485
- Reaction score
- 4
I second this. Especially for gem upgrades, when you are pushing higher grifts than you can handle just to get some more levels on your gems this is bound to happen.
Acps
New Member
- Joined
- Dec 24, 2011
- Messages
- 347
- Reaction score
- 0
Actually, just watching my T6 run, I'd bet my left nut, it would be identicle to the code for when you run out of Ressurection Here charges. Just watched the bot pop the Revive at last checkpoint.
- Status