Targeting Issue with Latest Patch

[Macha]

Greetings everyone!

I apologize for the trouble many of you have been experiencing with the targeting. I could see that being very inconvenient in certain situations. In order to forward the concern, we'll need a bit more information. zzapp, since you started the thread, could you please fill out the following?
________________________________

Platform:
ISP:
Type of Internet Connection:
Internet Connection Speed:
Date & Time:
Frequency:
Character Name:
Race:
World:
Class/Skill Rank:
Physical Level:
Area and Coordinates:
Party or Solo:
NPC Name:
Monster Name:
In-Game Time:
Steps:
1.
2.
3.
<*Add more steps if necessary.>
________________________________

Actually, I would like to fill this out too if you don't mind.

Platform: PC
ISP: University (Sorry, but I do not want to give out personal details)
Type of Internet Connection:
Internet Connection Speed: 5 MBPS
Date & Time: ANY
Frequency: All
Character Name: Macha Maudegonne
Race: Keeper of The Moon
World: Trabia
Class/Skill Rank: ANY
Physical Level: ANY
Area and Coordinates: ANY
Party or Solo: ANY
NPC Name: ANY
Monster Name: ANY
In-Game Time: ANY
Steps:
1. Hit "Confirm" button in any targeting mode to select any NPC, Mob, or player. (e.g., in enemy mode, hit "Confirm" to select the nearest target. Target is not dependent on any mode)
2. Scroll through targets using left or right after hitting confirm. Any target is still selectable.


This is different as compared to how targeting was before the patch. Previously, hitting "Confirm" would select the nearest target applicable to the mode that the user has set, or the user if there are no applicable targets in range. If the user's party was in battle, then it would select the monster that is currently engaged-- provided that the user is in "Enemy" target mode.

While users are still able to select applicable targets by using left or right, this is slightly inconvenient for people who have a gamepad setup like I do; my left and right are above my left analog stick, which means that I have to stop running to select a target (I personally do not like auto-run unless I am following somebody), and that the target could be ANY target on the field (as compared to the "Confirm" selects actively engaged mob, now it will select a random mob on screen). Thusly, it is not very time efficient.

tl;dr Confirm button does not target applicable targets; it effectively changes the target mode to ALL while the user is actively selecting a target. This is not dependent on what mode the user is currently in.

[origamikitsune]

Have to fill one out in a separate thread, new thread for each person. At least, that's what they have said in the past. I assume its so they can gauge how "important" we think it is by how many of us report it.

[Lorelai]

This obviously isn't a client side bug haha

I love the idea of using auto-run + the face buttons to select targeting modes, and the fact that up/down can once again be used to target myself and fellow party members.

They just need to iron out this little bug and it'll be perfect. (:

[zzapp]

I'm sorry, Xophious, for being a little late responding to your request, and thank you Macha for your input.

Platform: PC
ISP: Fairpoint Communications
Type of Internet Connection: DSL
Internet Connection Speed: 1.5 MBPS
Date & Time: Any
Frequency: Constant
Character Name: Eli Storm
Race: Midland Hyur
World: Istory
Class/Skill Rank: All
Physical Level: 50
Area and Coordinates: All
Party or Solo: Both
NPC Name: All
Monster Name: All
In-Game Time: Any
Steps:
1. Regadless of A or B targeting mode, hitting the controller A (enter) button will target whatever is directly in front of you, regardless of what filter you have activated. This was not the case prior to 1.17a. I think the new targeting mechanism is fine, except for this issue. I.E. - You should not be able to target mobs when in friendly mode, and vice versa.

2. When target modes A and B were initially established, we were told we would be able to toggle back and forth with /tm. This is not, however, the case, unfortunately, which necessitates two macros instead of the one if it toggled, as advertised.

Best regards.