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

Trinity 2.1.21 and QuestTools 2.1.38

Status
Not open for further replies.
hey guys how do you stop combat on the rift trials at the specified wave as mine currently doesn't work

Set it to the actual number of waves you want it to do. Not the wave power level. So set it to like 6, not 30.
 
Due some issues I performed a fresh install (out of the BETA zip) and now I am running Trinity 2.1.21 and QT 2.1.40 (which is inside the zip package). After running the full R-Rift profile the bot is trying to upgrade my gems without success and this error message:

Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.ArgumentOutOfRangeException: Der Index lag außerhalb des Bereichs. Er darf nicht negativ und kleiner als die Auflistung sein.
Parametername: index
bei System.ThrowHelper.ThrowArgumentOutOfRangeException()
bei System.Collections.Generic.List`1.get_Item(Int32 index)
bei QuestTools.ProfileTags.CompleteGreaterRift.<UpgradeGemsTask>d__2d.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
bei QuestTools.ProfileTags.CompleteGreaterRift.<CompleteGreaterRiftRoutine>d__1.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei Zeta.Bot.ActionRunCoroutine....()
--- Ende der internen Ausnahmestapelüberwachung ---
bei Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
bei Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
bei Buddy.Coroutines.Coroutine.Resume()
bei Zeta.Bot.ActionRunCoroutine.Run(Object context)
bei Zeta.TreeSharp.Action.RunAction(Object context)
bei Zeta.TreeSharp.Action..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.TreeSharp.PrioritySelector..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.Common.HookExecutor.Run(Object context)
bei Zeta.TreeSharp.Action.RunAction(Object context)
bei Zeta.TreeSharp.Action..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.TreeSharp.PrioritySelector..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.TreeSharp.PrioritySelector..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.Common.HookExecutor.Run(Object context)
bei Zeta.TreeSharp.Action.RunAction(Object context)
bei Zeta.TreeSharp.Action..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.TreeSharp.PrioritySelector..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.Bot.BotMain.()

Due the fact I am running a fresh install without any modifcations I would appreciate help
 
im looking for a way to have the bot ignore all the key of trials, any one know the adjustment to make
 
im looking for a way to have the bot ignore all the key of trials, any one know the adjustment to make

You can set the order of which the bot will be attempting to do rifts, trials and GRs by QuestTools options. Other way is to put your trials keys in another characters' bag.
 
You can set the order of which the bot will be attempting to do rifts, trials and GRs by QuestTools options. Other way is to put your trials keys in another characters' bag.

i think he wants to know how to make trinity NOT PICKUP keystone of trials.

i just deleted a char that was filled with keystones just to get rid of them.
 
looking for the fix to stop DH from spamming marked for death, has there been a fix for that, if so can you post so i can stop the spam thanks

tried searching for it but to many pages any help would be great
 
hello
the latest version of DB and trinity not use the WD soul harvest
there is a solution?
 
On my DH he often nose-dives straight into elite packs instead of staying at the kite range I specified in Trinity. How do I prevent this? Especially in GRifts this is a big deal as he will die often.
 
On my DH he often nose-dives straight into elite packs instead of staying at the kite range I specified in Trinity. How do I prevent this? Especially in GRifts this is a big deal as he will die often.

I think all is having that problem, been like this since patch 2.1 was released. Gotta love when the DH vaults into the mobs but dont have discipline to vault out again... You can take a loog at Fujiyama files which he posted here...https://www.thebuddyforum.com/demon...171-demon-hunter-m6-cold-rocket-build-19.html. It helped alittle..
 
Was the "freezing while attempting to pick up legendary" issue fixed?

I had to get back to Trinity 2.1.12 and QuestTools 2.1.32 to avoid it and want to know is it still persist and can I get back to current 2.1.21 and 2.1.38 versions.
 
Last edited:
On my DH he often nose-dives straight into elite packs instead of staying at the kite range I specified in Trinity. How do I prevent this? Especially in GRifts this is a big deal as he will die often.
What is your tps averange? Since patch 2.1 i think the bot Need more tps bot is with 10 tps good
 
latest git version always trying to town portal in trial and greater rifts
 
What is your tps averange? Since patch 2.1 i think the bot Need more tps bot is with 10 tps good

How can you increase the TPS?

All my computers are high end computers (4790K, 780TI SLi & 4960X, 880M SLi & 3940XM, 780M SLi) and my TPS are very low..
 
How can you increase the TPS?

All my computers are high end computers (4790K, 780TI SLi & 4960X, 880M SLi & 3940XM, 780M SLi) and my TPS are very low..
You can use tps modifier in the advanced-tab in trinity also set the process prority to high/realtime.
 
You can use tps modifier in the advanced-tab in trinity also set the process prority to high/realtime.

Yes, and restart db after the change. But the tps drops still there from 20 to instant 2 most time the drops are in fights. All happend since 2.1
 
Yes, and restart db after the change. But the tps drops still there from 20 to instant 2 most time the drops are in fights. All happend since 2.1

TPS setting is realtime, no need to restart DB.
 
For some reason, my quest tools keeps upgrading the wrong gem? I have it set to equipped(which is trapped and enforcer) and just for good measure, because I want enforcer upgraded and it wasn't being done, I moved it to top of the priority list. Instead it's spam upgrading pain enhancer, which isn't equipped, isn't anywhere near the top of the priority list in quest tools config, and even in this circumstance I posted from logs, only a 8% chance and still getting spammed. Any ideas how to fix this?

17:57:59.953 INFO Logger Upgrading Gems..
17:57:59.962 DEBUG Logger Total number of possible gems to upgrade 14
17:57:59.963 INFO Logger Number of Gems capable of upgrading 14
17:57:59.964 DEBUG Logger Upgrade Capable Gem PainEnhancer with Chance 8%
17:57:59.964 DEBUG Logger Upgrade Capable Gem GemOfEfficaciousToxin with Chance 60%
17:57:59.964 DEBUG Logger Upgrade Capable Gem Enforcer with Chance 100%
17:57:59.965 DEBUG Logger Upgrade Capable Gem Taeguk with Chance 100%
17:57:59.965 DEBUG Logger Upgrade Capable Gem PainEnhancer with Chance 100%
17:57:59.965 DEBUG Logger Upgrade Capable Gem InvigoratingGemstone with Chance 100%
17:57:59.966 DEBUG Logger Upgrade Capable Gem GogokOfSwiftness with Chance 100%
17:57:59.966 DEBUG Logger Upgrade Capable Gem BaneOfTheTrapped with Chance 100%
17:57:59.966 DEBUG Logger Upgrade Capable Gem WreathOfLightning with Chance 100%
17:57:59.966 DEBUG Logger Upgrade Capable Gem SimplicitysStrength with Chance 100%
17:57:59.967 DEBUG Logger Upgrade Capable Gem Moratorium with Chance 100%
17:57:59.967 DEBUG Logger Upgrade Capable Gem MirinaeTeardropOfTheStarweaver with Chance 100%
17:57:59.968 DEBUG Logger Upgrade Capable Gem GogokOfSwiftness with Chance 100%
17:57:59.968 DEBUG Logger Upgrade Capable Gem ZeisStoneOfVengeance with Chance 100%
17:57:59.968 INFO Logger Upgrading Gem Pain Enhancer Rank 34 Chance 0.08
17:58:01.078 INFO Logger Upgrading Gems..
17:58:02.254 INFO Logger Upgrading Gems..
17:58:02.255 INFO Logger Upgrading Gem Pain Enhancer Rank 34 Chance 0.08
17:58:03.439 INFO Logger Upgrading Gems..
17:58:03.440 INFO Logger Upgrading Gem Pain Enhancer Rank 34 Chance 0.08
17:58:04.609 INFO Logger Upgrading Gems..
 
You can use tps modifier in the advanced-tab in trinity also set the process prority to high/realtime.

Thanks, that helped alittle. I set it at 15 but I still se drops but they never belov 9.
 
some stuff that might help with low tick/s: increase d3 fore/background fps, disable vsync, set diablo 3 process priority higher
 
Status
Not open for further replies.
Back
Top