Quote Originally Posted by Mykll View Post
Well, ok. That is a little different. But, eh, still seems duplicated especially if you are in range and are able to auto-attack (unlike the BRD and MCH stances which don't auto-attack). Next time I am out I am going to have to get on one of those jobs, turn on the stance, and see if it changes that little indicator.

But aside from that, if you are in range (be it melee or BRD/MCH) and are in a stance that allows auto-attack, I don't see the situational times you need to know that. Yeah there are times when you tab through targets and you do not want to auto-attack the wrong one (non-aggroed group behind what you are fighting, something that is rooted, or asleep) but by the time you tab to those targets, the auto-attack already did its thing. And yeah I wish they would properly fix tab targeting.

So while that is interesting testing, and nice clarification, and I may do more later on, I am still failing to see why they gave very strict resources to this seemingly useless UI piece.
Yeah exactly, why add something that we already have (which coincidentally already worked better anyways and didn't need a "fix") and clutter the target bar even more? And then they give excuses on how they cant implement what we ask for cause the ui memory is already full.