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

Trinity 2.1.15 and QuestTools 2.1.36

Status
Not open for further replies.
This is the normal way trinity was configured, that is why we have to edit Crusader.CS file under trinity>Combat>Abilities.
You probably had an edited/have edited that file.
Here's the fix:
Replace Phalanx
Code:
// Phalanx
// if (CanCastPhalanx())
if (CanCast(SNOPower.x1_Crusader_Phalanx3) && Player.PrimaryResource >= 21 && TargetUtil.AnyMobsInRange(40f, 1))
{
return new TrinityPower(SNOPower.x1_Crusader_Phalanx3, 40f, CurrentTarget.ACDGuid);
}

Shotgun Crusader auto-attacking single mobs instead of using Heaven's Fury - Fires of Heaven. (not fixed)
 
Shotgun Crusader auto-attacking single mobs instead of using Heaven's Fury - Fires of Heaven. (not fixed)

My bad, Change Phalanx code to match Heavens fury.
I do not use HF since its not as efficient in higher GR compared to stampede build.
 
Compiler Error: d:\...\Plugins\Trinity\Cache\RefreshObject.cs(105,30) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: d:\...\Plugins\Trinity\Combat\HandleTarget.cs(787,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: d:\...\Plugins\Trinity\Combat\HandleTarget.cs(937,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: d:\...\Plugins\Trinity\Combat\TargetCheck.cs(144,25) : warning CS4014: Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Compiler Error: d:\...\Plugins\Trinity\Combat\Abilities\DemonHunter.cs(229,47) : error CS0103: The name 'LastChangedZigZag' does not exist in the current context
Compiler Error: d:\...\Plugins\Trinity\Combat\Abilities\DemonHunter.cs(239,21) : error CS0103: The name 'LastZigZagUnitAcdGuid' does not exist in the current context
Compiler Error: d:\...\Plugins\Trinity\Combat\Abilities\DemonHunter.cs(230,46) : error CS0103: The name 'LastZigZagUnitAcdGuid' does not exist in the current context
Compiler Error: d:\...\Plugins\Trinity\Combat\Abilities\DemonHunter.cs(240,21) : error CS0103: The name 'LastChangedZigZag' does not exist in the current context

this keeps occurring no clue what to do i am ashamed that i deleted my older versions now that were working before.
problem is i have downloaded latest beta and stable version downloaded latest versions of Trinity and questtools i keep getting these errors no matter what currently i simple deleted everything.
 
With the new DH logic he doesn't attack Corrupting Growths just places sentries! Please help!
 
guys its just me or questools is bugged ?!?!? everytime i restart my DB the chance of the gem that i haved set to 30% goes to 10% ?! the rift priority its straight doesnt change but the chance of the gems to be upped are changing everytime i restart DB !
 
textsave | The easy way to save text online!

edited dh.cs, very crude edit, should kill destructible's, also made it use Companion always when some energy is expended to speed killing corrupted growth's, doesn't run into mobs, always shoots something does basic ranged attack when saving hatred for sentries.

only use this with 6pc marauder's.
 
I think the bot attempts to run through the monsters sometimes, but when theres a big cluster of them bot gets stuck in t hem and stays there for a while ( and hence dying there)

what should i LOG for this problem ?


I also had a problem after doing trial/ G rift the bot would either not go back to town for trial or not talk to G rift reward for gem upgrade / key upgrade. This is happening every time since the quest tool 2.1.30 update.
 

Attachments

Ticks are dropping to 3-6 every time an elite or boss comes within attacking range or engaged with this version, was getting constant 14-16 Ticks with 2.1.19

Tryed ticks at 30, just unchecked it thou made No Diff. even when putting Bot on high priority or both bot/d3...



Is Ticks per second safe to use? I think i remember seeing this saying USE AT YOUR OWN risk type of warning?


[Trinity][Performance] Execution of RefreshDiaObjectCache took 1283.04ms.
[Trinity][Performance] Execution of HandleTarget took 1720.71ms.
[Trinity][Performance] Execution of MainFindSafeZoneLoop took 1395.68ms.

[Trinity][Performance] Execution of RefreshDiaObjectCache.AvoidanceCheck took 1072.01ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache took 1102.77ms.


Seems Avoidance and avoid AoE options bottleneck the ticks to death.

I'm having this exact issue, only happens when the character is fighting champions or elite mobs and there is significant amount of AoE on screen. Latest DB Beta and Trinity etc.
 
@rrrix

I tried the the new trinity and quest tools and its working properly with m6 demonhunter.

Although i have a question :

I notice that it isn't using the companion abilities properly.
It should use wolf howl on every elite, but it doesnt.

Sometimes it goes of, sometimes not, can you look in to it to make it more consistent?

I got so much cooldown reduction that it is not problem to use it on every elite.

Please help thank you
 
Question about TPS, what exactly is the point of this. It says it's going to increase CPU usage, so i went slowly and moved it to 25, yet i'm at 16% CPU lol so i guess i could go much much higher, but is there a point ?

What does that do exactly ?
 
Question about TPS, what exactly is the point of this. It says it's going to increase CPU usage, so i went slowly and moved it to 25, yet i'm at 16% CPU lol so i guess i could go much much higher, but is there a point ?

What does that do exactly ?

Some say it makes the bot smarter, It makes it smoother for me. I went up to 80tps, but it errors out like crazy. The more fps you have the more tps you have but D3 cant handle all the TPS you are sending to it so it disconnects you A LOT. 30-45 is the range I seek and seems to work well with no errors.
 
I'm using the latest trinity/questtools and as a WD, it no longer casts piranado and won't use gargantuan except for elites.

Also, is there a way to have the bot NOT grab all your keys from stash? On HC, I don't like having everything in inventory incase I die. I tried protecting the stash page they are in, but that must not be working.


Thanks,
 
Status
Not open for further replies.
Back
Top