Ambiguously named buildings and techs in Italian aoe2 confuse the game

:arrow_forward: GAME INFORMATION

:point_down: These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.

  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED

:point_down: DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.

In the Italian version of the game both the Keep tower and the scenario only building named Fortress are called “Fortezza”. This leads to confusion when in a scenario you want a “Fortezza” to do something or a Fortezza is required as it seems the game randomly choose what Fortezza means (either Keep or Fortress).

:arrow_forward: FREQUENCY OF ISSUE

:point_down: How often does the issue occur? CHOSE ONE; DELETE THE REST!

  • 50% of the time / matches I play (FREQUENTLY)

:arrow_forward: REPRODUCTION STEPS

:point_down: List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!

Here’s the steps to reproduce the issue:

  1. Place a Keep and a Fortress (both Fortezza).
  2. Make a trigger that allows you to create a certain unit from the Fortress (Fortezza)
  3. The game assumes it to be either Keep or Fortress so it can happen you could train that unit from a Keep… indeed whenever you go back to the trigger the selected “Fortezza” can switch on one of the two randomly.

:arrow_forward: EXPECTED RESULT

:point_down: What was SUPPOSED to happen if the bug you encountered were not present?

Just rename either the Keep or the Fortress to something else than Fortezza!
Same problem with the two technologies named “Fortezza”, one is obviously the Keep upgrade and the other the Celts unique tech called Stronghold. Some renaming and imagination is needed in Italian.

:arrow_forward: IMAGE

:point_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.

:arrow_forward: GAME FILES (SAVE / RECORDING)

:point_down: 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.