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

Not stacking Taeguk?

henke420

Member
Joined
Feb 20, 2016
Messages
37
Reaction score
1
Demonhunter Issues

Hello, i've played LoN firebats WD with Taeguk and it's stacking it perfectly fine, but when i try with cold cluster marauder build it's not stacking Taeguk at all, is there any easy way to fix that? Thanks

Edit: Also another problem i found with Demon hunter is on the GR Maps with "shield doors" i don't know what to call Them but like the ones where you kill zoltan kulle it's trying to kill thru the "doors" and getting stuck there because he can't deal any damage through the "doors" even tho it's not a door you can open, the bots needs to run through the invisible wall to prevent this
 
Last edited:
Support for Taeguk stacking has to be done on a build by build basis. Can you provide a diablofans link or maybe a d3planner link of this build so that I can take a look?
 
Here, try this. I'm not completely satisfied with it as it still lets Taeguk drop sometimes. I'm guessing it's because this build has such a busy playstyle and the priority for CA ends up being pushed back, but it's still noticeably better than before.
 

Attachments

Here, try this. I'm not completely satisfied with it as it still lets Taeguk drop sometimes. I'm guessing it's because this build has such a busy playstyle and the priority for CA ends up being pushed back, but it's still noticeably better than before.

Thanks i'll try that :D

Edit: By far better in combat, but as you said not keeping Taeguk up out of combat like Vault or movement is higher priority
i changed CombatBase.TimeSincePowerUse(SNOPower.DemonHunter_ClusterArrow) > 2000)
to 1500 and it's doing better, but everytime i kill an elite pack for example he prioritize using vault to collect the progression orbs and thereby losing the stacks

but in my opinion it's probably good enough as they're going to make Taeguk really bad for DH in the 2.4.1 patch so might aswell not do something to advanced to fix it even more
 
Last edited:
Back
Top