Pyrrhus Scenario 1 -- defeated when Demetrius still has his Town Centre

:arrow_forward: GAME INFORMATION

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

  • GAME BUILD #: 101.102.18071.0
  • 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 first scenario of the Pyrrhus campaign, after I have destroyed Antiochus’ Stables, the objective says that at least one allied Town Centre must stand until the timer runs out. However, when both of Antigonus’ Town Centres are destroyed, I am defeated, even though Demetrius’ Town Centre still stands.

:arrow_forward: FREQUENCY OF ISSUE

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

  • 100% of the time / matches I play (ALWAYS)

: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. Play the first scenario of the Pyrrhus campaign.
  2. Destroy Antiochus’ Stables.
  3. Wait until Lysimachus destroys Antigonus’ Town Centres.
  4. Be defeated even though Demetrius’ Town Centre still stands.

:arrow_forward: EXPECTED RESULT

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

I wasn’t supposed to be defeated until Demetrius’ Town Centre was also destroyed. (Which, to be fair, probably would have happened not long after.)

:arrow_forward: IMAGE

:point_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
Here’s a screenshot from after my defeat, clearly showing “0/3 allied Town Centres remaining” and Demetrius’ Town Centre intact.

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

SP Replay v101.102.18071.0 #(83607) @2023.05.28 183104.aoe2record (1.1 MB)

Hi @TommoChocolate
This issue could be related to a trigger issue the team is investigating, thanks for your report :slight_smile: