Fountain of Youth? - Fixed Gun AI recapture trigger is broken

:arrow_forward: GAME INFORMATION

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

:arrow_forward: ISSUE EXPERIENCED

In the “The Fountain of Youth?” scenario from the Blood campaign, once the player captures the Fixed Gun from The Circle, the Circle will attempt to recapture it at different points of the scenario. However, if any of the enemies succeed, the trigger that’s supposed to take effect either won’t work or will work erratically.

:arrow_forward: FREQUENCY OF ISSUE

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

:arrow_forward: REPRODUCTION STEPS

Here’s the steps to reproduce the issue:

  1. Capture the Fixed Gun as normal
  2. Remove your units from the Fixed Gun’s proximity. Don’t block any potential approaches.
  3. When an enemy unit from either the Red or Orange AI approaches the Fixed Gun, allow it to be captured.

4.a.1. When Orange captures the Fixed Gun, dialog from Morgan is triggered infinitely at high frequency until the Player recaptures it.

4.a.2. When the Player recaptures the gun, corresponding dialog from Morgan plays appropriately.
4.a.3. Only after the Fixed Gun is captured, a batch of Rodeleros and Hussars is spawned near the Player’s Dock.

4.b. When Red captures the Fixed Gun, there is no additional effect at all, even after the Player recaptures it.

:arrow_forward: EXPECTED RESULT

  1. Upon a successful capture by the AI, a message would trigger from Morgan, mentioning the Fixed Gun’s capture and the need to take it back.
  2. A batch of Rodeleros and Hussars spawns near the Player’s Dock, to help the Player recapture the Fixed Gun.
  3. Once the Fixed Gun is captured, appropriate dialog from Morgan is triggered.

:arrow_forward: IMAGE

:arrow_forward: GAME FILES (SAVE / RECORDING)

QuickSavegame.age3Ysav (5.3 MB)
The above attachment is for the Orange AI’s capture of the Fixed Gun, as it is harder to set up and appears to have no scripted attacks towards the Gun.

1 Like

Hi there! Thanks for your report on this issue. We’re now tracking the issue :+1: