Guild Wars 2

Hello. I saw this on the patchnote :

• Tab targeting now prioritizes players over NPCs (including minions; mesmer clones are an exception) and champions over everything else.
• Deselecting a target will reset the tab-targeting history.

First I though it was great, no more searching for legendarie in keep, or struggling with spirit ranger in sPvP, but then…
I use a key to get “Nearest Enemy”, “C” like in GW1, but now, if a champio is at 1200 range and mobs are between champ and me, I get champ EVERY time, so I assume the tab targetting is working great, but now, we can’t target the nearest enemy, with the custom key.
Is it intended ? Is it hard to keep nearest enemy and tab with separate script ? Or it’s a bug and it will be fixed ?

I have the very same problem. Have “target nearest enemy” bound to a mouse button (used to have it on “C” like in GW1 before :-)).

Targeting is completely broken now, because it favors champions that I’m not in combat with and that are out of range over enemies I’m currently fighting.

Sometimes it favors or rather sticks to an immobile target like a “prison cell” although an enemy is right in front of me. Maybe the new target priority is plain and stupid “prefer highest hit point target within 2000 range” regardless of being in combat with being in reach and not obstructed, almost dead or beating the kitten out of me, …

Well meant the famous opposite of well done.

• https://forum-en.gw2archive.eu/forum/support/bugs/Nearest-enemy-targeting-broken
• https://forum-en.gw2archive.eu/forum/support/bugs/Target-nearest-enemy-priorities

Thanks Evan. After years of gw1 and now a year of gw2, pressing C is as reflexive as breathing.

I’ve ran into the same problem as well, I’ve bound “Closest Target” to C as well (former GW1 player here as well), and when I really do want to target the closest mob to me that isn’t a champion, pressing C does exactly what pressing tab does – targets the closest champion. Which can be behind a horde of regular mobs.

So yep – Target Closest is currently not working as the description says, I’m really hoping for a fix for this.

Yeah, I’m glad this is getting looked into. This has screwed me up so much since it was implemented, and I desperately want my “Nearest Enemy” targeting back! Thanks in advance to Evan and Dylan for their speedy work on a fix!

Given how massively this bug impacts game play of those using “target closest enemy” I’m beginning to wonder, if “looking into it” also includes fixing what has been broken.