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

Demonhunter problems

poweredbyoats

New Member
Joined
Oct 4, 2012
Messages
28
Reaction score
0
So I made my new char a demonhunter just to try something different. Kind of regret it. I've gotten it to the point where it kills well, but there are at least a couple of problems.

1. Dies too much, especially against Reflect elites and especially when I use Spike Traps. Anyone dealing with Reflect in a special way? I'm thinking of rewriting the Giles code to check that Shadow Power is on before putting out traps. (Yes, I have around 4000 armor, 400 res.)

2. Shoots at walls in certain places. For this reason, I stopped running Skycrown. Still shooting at walls in Rakkis though (while on stairs), but not as regularly as it did in Skycrown. I guess this is a problem inherent in ranged combat. There must be a way to set up combat logic to deal with this.
 
1. Dies too much, especially against Reflect elites and especially when I use Spike Traps. Anyone dealing with Reflect in a special way? I'm thinking of rewriting the Giles code to check that Shadow Power is on before putting out traps. (Yes, I have around 4000 armor, 400 res.)
Reflect is a nasty one against DH. I usually don't have much problems but I end dying to some packs with other nasty affixes. I haven't tested latest unified trinity, but with latest giles there was a problem as the DH will use shadow power almost as soon as posible, ending in wasting disc, so when you really needed, you couldn't cast it. Also another thing you could look after is modify the HP at which the bot will seek either pots, HP pools or HP orbs. I didn't find any issue with spikes thought...

2. Shoots at walls in certain places. For this reason, I stopped running Skycrown. Still shooting at walls in Rakkis though (while on stairs), but not as regularly as it did in Skycrown. I guess this is a problem inherent in ranged combat. There must be a way to set up combat logic to deal with this.
This is a Trinity problem. It has been fixed in DB/Belph routine, but Trinity overrides that, so it needs to be fixed in Trinity also (again I haven't tested latest unified version).
 
Back
Top