A player only with unbuilt and not-started Wonder foundation cannot be defeated in campaigns

:arrow_forward: GAME INFORMATION

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

  • GAME BUILD #: 99404
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED


If a player should be defeated (no units, no production buildings, zero population etc.) but still has a Wonder foundation that was not being built yet, the player stays in the game “alive”. It happened during a custom campaign I wasn’t able to win because I found out one AI player placed a Wonder foundation and that was all it had. It’s a similar issue to Donjon building foundation bug a few years ago that was abused in multiplayer games.

:arrow_forward: FREQUENCY OF ISSUE

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

I was able to consistently reproduce the bug in campaigns and scenario editor. I wasn’t able to replicate the bug elsewhere.

: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. Start a campaign mission where you can build Wonder (eg. Saladin 6)
  2. Place a Wonder foundation (do not start building it!)
  3. Delete everything
  4. You’ll be left only with the Wonder foundation and stay not defeated

:arrow_forward: EXPECTED RESULT

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

A player should be forced to get defeated by the game if the player has no units, 0 population and no production buildings.

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

Hi @OneAirplane7414
I talked with the team about this issue, thanks for the report.