Mission "Strange Alliances" creating incorrect nuggets for the Secondary Objective

:play_button: GAME INFORMATION

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

  • GAME BUILD #: Latest public build
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 10

:play_button: ISSUE EXPERIENCED

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

In the campaign mission of Blood, Ice, and Steel, the “Strange Alliances” mission has incorrect treasures core to the secondary objective. The objective is to release captive settlers from the British (which are nuggets, aka treasures), but the nuggets incorrectly spawn as the current build’s default, the 3 Mutineers. Additionally, as you can see in the screenshot, the nugget objects fail to render in-game.

:play_button: FREQUENCY OF ISSUE

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

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

:play_button: REPRODUCTION STEPS

:backhand_index_pointing_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 through “Strange Alliances” until the colony is controlled by the British.

  2. Observe the treasures outside the colony.

  3. Notice they are incorrect.

:play_button: EXPECTED RESULT

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

The nuggets should each be 4 Musketeers guarding 2 Settlers.

:play_button: IMAGE

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

:play_button: GAME FILES (SAVE / RECORDING)

:backhand_index_pointing_down: Attach a SAVE GAME (.aoe3Ysav) or GAME RECORDING (.aoe3Yrec) of the match where you encountered the issue. Link it below if using an external file service.

  • No need, this is on the live build on all platforms. It’s a mistake with the scenario file for this mission.