No, really! Solved: Multishot DH "No valid power selected...."

[Anonuzer01]

I've seen several people on Discord that were getting "No valid power selected for target" errors in their log on an Unhallowed Multishot DH. Meanwhile, the DH just stands in one spot doing nothing.

The solution for this appears to be to make sure you have the minimum of 37% CDR. Don't ask me why but that is what seems to have solved it for those having the issue.

Just wanted to pass along the info.

EDIT 12-15-17. So the above seemed to fix the issue for a few of us for awhile but looks like that was just RNG. Pretty sure I've figured it out and it appears to have been a range issue between when to attack a target and the distance that either multishot or evasive fire could be used.

Replace the file in the routine folder with the one attached. Let me know if you still have the issue with the new file.

 

[Anonuzer01]

Maybe.

 

[prf]

37% is no downtime on vengeance and that doesnt solve it.

 

[Anonuzer01]

Yeah, it's unusual as hell. Me and a couple of the guys that have been having this issue raised our CDR and it's like it went away but then I started seeing it again off and on last night. I think it's a positional/distance issue and I've got some ideas I'm going to toy with today.

 

[qvazmir]

Isn't it just due to not having enough hatred to cast multishot? And that's solved by having perma vengeance? Or is this happening even with a generator?

 

[Anonuzer01]

Happening with perma vengeance and with a generator. Think I have it fixed though. At least I haven't seen it since I made a small modification to the routine. The DH Base had ranges of 75 for trash and 120 for elites. The Multishot routine had ranges of 80 for multishot and 60 for evasive fire.

So, If the target was Elite and 81-120 away it couldn't multishot.
If it was Elite and 61-120 away and DH was out of hatred it couldn't Evasive fire.
If the target was trash and 61-75 away and DH was out of hatred it couldn't evasive fire.

Set both ranges for multishot and evasive fire to 120 and haven't seen any issues since. Let me know if you guys see it on your end.

 

[Anonuzer01]

There may be better ways of solving this but for now it seems to be working. I looked through my log for my run overnight and while it still popped up occasionally it was only immediately after gating or taking a portal into a new zone, so most likely just caused by lag from the loading process.