Printable View
I recently attained MRD level 36 and proceeded to click on the glowing NPC Linkpearl for the Astalicia. The name of the NPC simply displays as "[en]".
The following is the ingame text.
[en]: Ahoy, first mate! Gots me another job fer ye, I 'as! Meet us at th' Astalicia.
Hola Kikosho!
Thank you for taking the time to post within the forum. We appreciate you reporting the minor text issue and we'll be happy to forward the concern. Before we can do that, we'll need for you to please fill out the following information.
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.>
Thank you!
Completely forgot about filling the rest, will do so now.
Platform: PC
ISP: Comcast
Type of Internet Connection: Cable
Internet Connection Speed: 30 mbps Download/3 mbps Upload
Date & Time: October 9, 2011
Frequency: Once
Character Name: Shanoa Kikosho
Race: Female Elezen
World: Rabanastre
Class/Skill Rank: MRD 36
Area and Coordinates: Camp Bald Knoll
Party or Solo: Party
NPC Name: Waekbryt
In-Game Time: 19:00
Steps:
1. Reached level 36 with my MRD class.
2. Touched the aetheryte at Camp Bald Knoll.
3. NPC Linkpearl for the Astalicia lit up.
4. When I clicked on the linkpearl, Waekbryt's name did not show up properly. Instead it was replaced with [en]. Full chat line is in my original post.
Greetings, Kikosho!
Thank you for providing the information that Bublex requested. Since this matter involves the display of an NPC's name, I have made sure to move this matter from "In-Game Bugs" to "Localization." Thanks again for your report!
The NPC who should be speaking is Rostnsthal, not Waekbyrt. Notice that he calls the player "first mate," and Waekbyrt wouldn't do that.
This bug has been here for a long time. I wonder what's up with it. It must be some programming thing not easily handled by the loc team.
Thanks for the report!
It turns out that this was not a LOC issue, but a mistake in the code (the wrong data cell was being called up for the EN version only). The programmer has identified the problem and fixed it locally. The fix should be implemented by patch 1.20.
I'd also like to give a silent shout out to Lienn for reporting a similar issue long, LONG ago (here). We finally got it!