"Nearest enemy" targeting broken
Came here to post this exact bug. I was just killed because I expected the “Target nearest enemy” to target the 1 hp drake next to me rather than the out of range player. I wish it worked exactly as in gw1, by proximity
I agree with everything stated to this point.
I was aware of the priority changes coming in today’s patch regarding “TAB Targeting”, but nowhere were these changes mentioned to also affect “Target Nearest”, which is totally separate from and should not be related to “TAB Targeting” and the changes made to that aspect of the targeting system.
“Target Nearest” should…well, “Target Nearest”, regardless of the type of enemy.
| [Free Ports For All “Not So Secret” JP Needs (and 1st Try Dive Tips)] |
| [Classic Thread: “all is vain”] |
I agree: it appears that the changes to tab targeting have also incorrectly been applied to “target nearest,” instead of just “target next” and “target previous” (“tab targeting” only applies if you use the default keybindings).
It took me longer than the folks posting above to figure out why I could only “target nearest” when I turned away from the nearest legendary/champ/event boss.
Indeed. Please fix “Nearest Enemy” so it targets the nearest enemy.
Thanks.
Always follow what is true.” — Sentry-skritt Bordekka
This is being officially tracked:
https://forum-en.gw2archive.eu/forum/support/bugs/Fixed-Tab-Targetting-and-custom-key/first#post3039240
Same thread: bug has been ID’d and in process of getting fixed.
Yep, very annoying bug since it’s a 8+ years habit to press ‘c’ to target the nearest foe. Now we have to click on the foe to target it if there is a champ nearby.
Before the patch, we were constantly losing target and now, we can’t even target anymore.
Yeah im adding my name to this list the nearby target key is busted. Was fighting in WvW mins ago and was gettign atked by 4 people. Instead of targeting the warrior thats attacking me (closest), i target a Doe in the distance and hit the wrong atk button… Im read this other official forum log in the meantime someone post above. But plz fix this