GAME INFORMATION
These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
- GAME BUILD #: December PUP
- GAME PLATFORM: Steam
- OPERATING SYSTEM: Windows 10
ISSUE EXPERIENCED
DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
Running the PUP, the game cannot read the name of units that are renamed via custom strings IDs, using the Modify Attribute > Object Name ID.
It results in displaying the code name of each unit (the 5 cap letters code, like “UCATA”…), and fails to read the custom string linked to the custom ID.
I must add that the bug occurrs not only on loaded saved games (as of in the current build) but also on starting a new fresh game.
This is a PUP related issue, and should be corrected before the next official update.
FREQUENCY OF ISSUE
How often does the issue occur? CHOSE ONE; DELETE THE REST!
- 100% of the time / matches I play (ALWAYS)
REPRODUCTION STEPS
List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!
Here’s the steps to reproduce the issue:
- Modify an Object’s name via the Modify Attribute > Object Name ID effect using a custom ID linked to a custom Name.
- Test the scenario.
- Observe that the game doesn’t read the custom string’s ID, and thus display the default “code” name of the unit in question (5 capital letters).
EXPECTED RESULT
What was SUPPOSED to happen if the bug you encountered were not present?
The game should read the custom string’s ID and display the correct name on screen, like it does in the current version of the game, and all previous versions.
IMAGE
ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
GAME FILES (SAVE / RECORDING)
Attach a SAVE GAME (.aoe2spgame) or GAME RECORDING (.aoe2record) of the match where you encountered the issue. Link it below if using an external file service.
