# Legend text in AOTG lobby page don't have correct LocString

**URL:** <https://forums.ageofempires.com/t/legend-text-in-aotg-lobby-page-dont-have-correct-locstring/290375>\
**Category:** AoM - Report a Bug\
**Created:** [October 9, 2026, 12:02pm UTC](https://forums.ageofempires.com/t/legend-text-in-aotg-lobby-page-dont-have-correct-locstring/290375 "2026-10-09T12:02:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![C8024](https://forums.ageofempires.com/user_avatar/forums.ageofempires.com/c8024/32/46154_2.png) [@C8024](https://forums.ageofempires.com/u/C8024)\
**Post date:** [October 9, 2026, 12:02pm UTC](https://forums.ageofempires.com/t/legend-text-in-aotg-lobby-page-dont-have-correct-locstring/290375/1 "2026-10-09T12:02:12Z")

</div>

- 
## Game Version: Standard / Premium / DLC
- 
## Build Number: v.100.19.17020.0 (606844R)
- 
## Platform: Steam
- 
## Operating System: Windows 11

> ## Issue: LocString STR\_AOTG\_LEGEND is not properly used in AOTG lobby page.
> 
> It uses the LocString STR\_LEGEND and causes in some languages having different translations between Chart “Legend” and “Legend” Hero (e.g. in Chinese they are “圖例” and “傳奇”) can’t have correct translations. Also I didn’t find any LocString STR\_AOTG\_LEGEND used in UI.
> 
> And i18n for STR\_LEGEND and STR\_AOTG\_LEGEND are swapped in Traditional Chinese. Might need to swap their value too.

(please provide a detailed description of the issue)  
(use the upload button ![image](https://forums.ageofempires.com/uploads/default/original/3X/a/5/a5a00942db51cf22c52e31f05ed5c3c1fd224e72.png) to include a picture or video of the issue in action if possible)

> ### Trigger Event: Open the game. Change language to Traditional Chinese. The “Legend” button in tech tree is translated as “傳奇”.

(what was happening at the time of the performance/stability issue)  
(this could be an action you or another player took right before the issue started)

> ### Repro Steps:

1. (List the steps needed to reproduce the issue)
2. (Indicate if you were able to reproduce this, to help us identify frequency of the issue)
3. (etc)
