Extreme AI skirm micro is bugged

: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 #: Version 101.103.48086.0 (#179158) 23798925
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 11

:play_button: ISSUE EXPERIENCED

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

The Extreme AI skirmisher micro is bugged; they seem to be issued attack orders at a faster rate than they can reload, resulting in that they simply get no volley off at all and are just stuck in an animation spam. See attached video and rec.

: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 descriptiv e!

Here’s the steps to reproduce the issue:

  1. Launch a game vs. the Extreme AI on 1v1 random map

  2. Go archer rush

  3. Observe opponent’s skirmisher micro

:play_button: EXPECTED RESULT

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

The correct behaviour is issuing new attack orders no faster than the time required to finish a volley (meaning a javelin is actually thrown and there is actually a chance to deal the enemy damage - if no javelin is thrown then there is no chance to get value out of the units or to deal any damage to the opponent’s units).

:play_button: IMAGE

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

:play_button: GAME FILES (SAVE / RECORDING)

:backhand_index_pointing_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 ser vice.

Hello @Hjoerleif, the team is aware of the issue, thank you :slight_smile: