GAME INFORMATION
These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
- GAME BUILD #: 101.102.24724.0 (#90260) 11771158 - and all other versions for at least the last months. But possibly ever since “Object Name ID” became a modifiable attribute in the scenario editor (?)
- GAME PLATFORM: Steam
- OPERATING SYSTEM: Windows 10
ISSUE EXPERIENCED
DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
Note: This bug only affects objects that are renamed using the trigger effect Modify Attribute: Object Name ID. It does NOT affect objects renamed with “Change Object Name”.
After loading a saved game that contains units that are renamed this way, the units will no longer show the name chosen by the scenario designer, but their internal name.
E.g. a renamed Archer will be named ARCHR, a Teutonic Knight becomes TKNIT, Willam Wallace becomes HWIWA.
FREQUENCY OF ISSUE
How often does the issue occur? CHOSE ONE; DELETE THE REST!
- 100% of the time
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:
- In the Scenario Editor, place an Archer and use the trigger effect Modify Attribute: Object Name ID to rename him to “Anything” .
- Test the scenario, check that the Archer is now called “Anything”, and save the game.
- Load the game. The Archer formerly known as “Anything” will now be named “ARCHR”.
EXPECTED RESULT
What was SUPPOSED to happen if the bug you encountered were not present?
The Archer renamed to “Anything” should still be named “Anything” after loading the saved game
IMAGE
ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
This modified William Wallace look-alike is Morten the Black, ancestor of the famous Hospitaller Morgan Black. But after loading my saved game he has renamed himself to “HWIWA” without my permission…

This bug isn’t as serious as other scenario related bugs, since it can be worked around by adding a timed looping trigger that regularly re-renames the renamed objects. But it’s still mildly annoying…