Nostalrius Begins - Quality wow vanilla realm (1.12)

Can you please fix the: "/target [name]" command. It seems, like it only checks the 1 symbol of the name and ignores the other part.
Example:
There are: npc Rok'Alim and a player (Rippy)
If u use "/target Rok" it will still choose the closest one and might choose Rippy. Pls, fix that

I'm not sure if this is handled by the client or the server as targeting is handled by a Lua function by the client.
I can only assume some addon is targeting players around you to check for health, mana, energy, or rage for some reason.

Testing this out in a heavily concentrated place, I decided to do a test with all my addons enabled.

No Target -> Targeting Brakgul Deathbringer:
/target Br
/target Ba

/target Me: Melodyx (1), Mendo (2)
/target Ek: Ekyea (1), Ekyea (2) -- Ekima was standing next to me, longer distance than Ekyea. I moved closer to Ekima and it only targeted Ekima at that time.

Safe to say distance is a factor in targeting and I tried 6 conflicting names with other players/NPCs. Still haven't received it targeting a player that did not have any of the letters specified.

I mean, it's not mostly about the NPCs.
I'm using somithimes "/target" macro to find npc that are walking. And sometimes even if that npc is in vision, it may target random NPC with same first letter

not sure if /targetexact Rok'Alim , already exist

Athene wrote:not sure if /targetexact Rok'Alim , already exist

http://wowwiki.wikia.com/MACRO_targetex ... on=history
Closed out of WoW for the night since I got work soon, but the page was made in 2009. Way after 1.12.1 came out.

http://wowwiki.wikia.com/API_TargetUnit?action=history
TargetUnit (API) page was made in 2004 just to make sure there's no reference errors like WoWHead's patch 1.11.1 on everything (creation date of the service).

I always thought it tried to find things that are close to the spelling or something which is what caused this. Guess it isn't working as intended.