Stop Command New Bug

:arrow_forward: GAME INFORMATION

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

  • GAME BUILD #: 101.101.62085.0 8752729
  • 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.
Units ignore my first Stop command
It was working fine before new patch so i noticed it instantly
Most noticable with archers

:arrow_forward: FREQUENCY OF ISSUE

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

:arrow_forward: REPRODUCTION STEPS

:point_down: List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!
Select archers, Make them attack a building in agressive mode
Press the stop command
Units will continue to attack the building, instead of shooting ennemy units at range

Also works with targeting units (With selected archers in standground for this one) :
Select Archers, make them target a unity
Press stop command
Make the Ennemi targeted unit flee
Selected Archers will chase the targeted unit, ignoring the stop command

Now I have to press Stop command twice to make it have normal behavior

:arrow_forward: EXPECTED RESULT

:point_down: What was SUPPOSED to happen if the bug you encountered were not present?
Expected result is that selected units should forget about the targeted unit the first time i press stop command, not the second

:arrow_forward: IMAGE

:point_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
Age of Empires II Definitive Edition 2022 06 12 15 56 51 04 - YouTube

: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.
I may have games showing this but i need to find them, anyway it should not be an hard bug to reproduce
*

hey xI2ealGuNII,

Thank you for your post! i have been able to reproduce this issue and we are now tracking it internally :slight_smile: