It's been funny but enough is enough

[SylvAlternate]

Ok cool, but what if the guy in front of me is a PLD I should ignore and I'm better off killing the melee hopping around and going all around me? Because sure, I can cycle... through the entire peanut gallery behind him just to get to him. And reliably hitting him with my mouse is a challenge on its own because the guy's just hopping around. Especially in team fights where it's a hectic as all hell mosh pit.

and how exactly can they change the tab targetting to fix this? you've already got the option for cone priority, so target nearest player+tab should pick the second closest

[Asari5]

the intened function is the ability to cycle through the enemies. and it does. it starts from the enemy closest to you. if you target enemy nr. 4 it cycles further to enemy nr.5.
click on the ground to lose your target before using tab

[dwodmots]

Just set it to cone and it works fine.

[Jojoya]

Just set it to cone and it works fine.

Cone still isn't reliable, unfortunately, because it ignores range. I can have the closest enemy already targeted and hit tab. Intuitive would be for tab to move to the second closest enemy in front of me but half the time I end up targeting something out of range entirely.

Fortunately, it's rarely a problem in dungeons. It's usually open world content or places like Bozja where it's a problem. Nothing like being part of a hunt train, switching from the hunt mark to kill random trash hitting a healer then tabbing to switch back to the hunt mark just to end up targeting other random trash 30y behind the hunt mark and out of range

[SamSmoot]

Just set it to cone and it works fine.

One bit problem with cone targeting is that the cone starts at the camera, not the character. so if you hit tab and there's a target behind your character, that's on screen, it will be selected as the closest one. Cone targeting should be character relative.

[Shurrikhan]

One bit problem with cone targeting is that the cone starts at the camera, not the character. so if you hit tab and there's a target behind your character, that's on screen, it will be selected as the closest one. Cone targeting should be character relative.

Or it should at least give that choice, via another attached setting, ideally with a command line toggle (e.g., "/cbt" for "camera-based targeting" / "character-based targeting").

Just as we should probably have "Cycle Targets: Nearest to Farthest" (which should do that, not left to right), "Cycle Targets: Left to Right", "Cycle Targets: Downward via Enmity List" and "Cycle Targets: Hybrid (Near to Far, Left to Right)".

[Imora]

Someone has obviously not played wow and barraged a pack behind them.

[Cabalabob]

Pfft trying playing with a controller, the cycle target buttons will target someone in mare lamentorum before it’ll target someone in your pvp instance.

[Deveryn]

I don't know how much better it's supposed to work in something like frontline where you have a dozen or more enemies to pick from. I usually go for nearest, which I keep on my middle mouse button.

[IDontPetLalas]

I don't know how much better it's supposed to work in something like frontline where you have a dozen or more enemies to pick from. I usually go for nearest, which I keep on my middle mouse button.

As Midareyukki mentioned you don't always want to go for the person who is closet to you. What if the person who is closest to you is already CCed, or is half-dead but there's someone who is further away who is going to prevent someone on your team from capturing an objective? You go for the person further away, and when that person who is further away is in a mosh pit of other people you don't want tab targeting. Keybinds allow you to quickly and accurately target them out of a crowd.