Closest enemy targeting "fix"

Closest enemy targeting "fix"

in Guild Wars 2 Discussion

Posted by: rfdarko.4639

rfdarko.4639

It seems that in today’s patch, closest enemy targeting was changed to prioritize champion mobs even if they are farther away then vets. I found this out today while doing the harpy fractal, where I would try to target the golem closest to me, only to find myself constant targeting the invulnerable raving asura. And again at malcore’s leap, I was targeting the invulnerable malcore and not the enemy closest to me.

Besides the obvious issue of prioritizing enemies which can’t be damaged, I don’t believe this is the way closest enemy targeting should work. Tab targeting, which cycles through enemies, could benefit from prioritizing champ mobs, but there are times when I simply want to target the thing close to me – and that’s what closest enemy targeting should be. I hope this change is reconsidered- for the moment I’ve resorted to click targeting because as the targeting works now, too often I end up targeting something I did not intend.

guildless hobo who likes to solo – [x]

Closest enemy targeting "fix"

in Guild Wars 2 Discussion

Posted by: papryk.6273

papryk.6273

the new targeting system is really frustrating…
closest enemy targeting should not prioritize champs

There IS a “closest enemy target” option. I believe it’s “C” by default.

no kitten sherlock…that’s what OP is talking about

(edited by papryk.6273)

Closest enemy targeting "fix"

in Guild Wars 2 Discussion

Posted by: chemiclord.3978

chemiclord.3978

the new targeting system is really frustrating…
closest enemy targeting should not prioritize champs

There IS a “closest enemy target” option. I believe it’s “C” by default.

no kitten sherlock…that’s what OP is talking about

Yes, I noticed that shortly after replying, which was why I deleted the message, Watson.