Shift Queue Multiple Units to Attack then Move Does not Work

[ValkyrieLow5052]

GAME INFORMATION

^{These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.}

• GAME BUILD #: 101.101.43210.0 5867313
• GAME PLATFORM: Steam
• OPERATING SYSTEM: Windows 10

ISSUE EXPERIENCED

^{DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.}
When multiple units are selected, shift queuing Move command (right click on ground) after an attack command (right click on enemy unit) will cancel the attack command and immediately cause the units to execute the Move command. This does not occur 100% of the time but it happens very frequently.

This is unexpected because it only occurs with multiple units and this bug does not occur when the multiple attack commands are queued.

Bug Example:
If 2 scouts are selected and set to attack an enemy villager then the player shift queues Move command, then sometimes the bug happens and the scouts will forget the attack command and execute the move command.

This is inconsistent with the following cases which work as expected (No bug example):
If 1 scout is selected and set to attack an enemy villager then the player shift queues Move command, the scout will attack the villager until the villager is dead, then execute the Move command.

If 2 scout is selected and set to attack an enemy villager then the player shift queues another attack command on another enemy villager, then the scouts will attack the 1st villager until the villager is dead and then attack the 2nd enemy villager until it is dead. However if the player adds another shift queue move command both attack commands which should be executed before the move command are erased and the scouts just move.

FREQUENCY OF ISSUE

^{How often does the issue occur? CHOSE ONE; DELETE THE REST!}

• 50% of the time / matches I play (FREQUENTLY)

REPRODUCTION STEPS

^{List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!}

Here’s the steps to reproduce the issue:

0. This issue can be replicated by creating a scenario and testing or creating a skirmish game.
1. Create 2 or more military units such as scouts
2. Select 2 or more military units
3. Set the military units to Stand Ground stance
4. Right click an enemy unit such as a villager (the units should start trying to attack and kill the enemy unit)
5. Holding down shift, right click on ground to queue Move command

Steps 4-5 may need to be repeated to replicate the bug or to replicate the intended shift queue behaviour.

EXPECTED RESULT

^{What was SUPPOSED to happen if the bug you encountered were not present?}

The selected units will attack the enemy unit until it is dead then it will execute the queued Move command. This should be consistent and happen every time Move command is shift queued after an attack command.

IMAGE

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

What is expected/what happens when the shift queue works

What happens instead when the bug triggers

A rarer instance where one scout follows through with the attack but the other scout forgets the attack command and immediately executes the move command:

GAME FILES (SAVE / RECORDING)

^{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.}

[Walkop]

I’ve experienced this as well. Attack queuing should either be possible, or not possible. Inconsistency in the behavior is definitely an issue that needs to be addressed.

Personally, I don’t see it being enabled being an issue with melee units; ranged units could change some metas in a way that I don’t think is good for the health of the game.

[Harooooo1]

Shift-move after shift-attack is bugged

GAME INFORMATION Build: latest build, the July hotfix Platform: Steam / Microsoft Store Operating System: Windows 10 / Windows 7 / Mac / Linux Gamertag: harooooo1 ISSUE If you initiate a shift-attack command on a target, and then give a shift-move order somewhere away from the target (to move after the target is dead), the shift queue flags don’t appear, the shift queue doesn’t work, and the units immediately move away. However, if it’s in reverse, for ex…

I reported this ages ago, in July, around half a year ago lol, and it didn’t seem to get addressed.