GAME INFORMATION
These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
- GAME BUILD #: 158041
- GAME PLATFORM: Steam
- OPERATING SYSTEM: Windows 11
ISSUE EXPERIENCED
DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
On the random map Citadel (comparable to base game’s Arena), all players start with Medium Walls (or Fortified, depending on starting age). But when playing as Shang, all of them are damaged from the start. It seems that something goes awry with the civ’s wall HP bonus.
Custom scenarios where Medium or Fortified Walls were directly placed for Shang are also affected. Small Walls are unaffected by the bug, and they also remain unaffected when automatically upgraded after changing the starting age to Iron or Post-Iron for a scenario.
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:
- Set up a Skirmish game, choose Shang civ for Player 1 and the map Citadel. Full Tech Tree must not be activated.
- When the game begins, inspect your damaged Medium/Fortified Walls.
- Alternatively, open the Scenario Editor, set Player 1 civ to Shang, and place Medium/Fortified Walls for that player (and a unit to prevent instant losing). Test the scenario and take a look at the damaged walls.
EXPECTED RESULT
What was SUPPOSED to happen if the bug you encountered were not present?
Naturally, walls should not be damaged when starting a game, unless this is intentionally done with triggers or script.
IMAGE
ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
A Shang player’s damaged walls on the Citadel map, after starting the game:
Damaged Medium and Fortified Walls of a Shang player in a custom scenario:
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.

