Onager queue cutting bug

Age of Empires II: DE II - Report a Bug
1

: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 #: 101.103.21943.0 (153015) 19511862
  • 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.
Unable to queue cut trees with onagers anymore (shift + right click multiple trees with onager), as they don’t properly move on to the next cut in their queue (may cut 2nd/3rd one if cut is very close to the first)

: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) - occurs with everyone else I have spoken with

: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. Use onager to cut multiple trees with a single queue command (shift + right click trees 1…2..3…etc.)

:play_button: EXPECTED RESULT

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

  1. Supposed to cut all trees in the queue, after it finishes cutting tree 1, then tree 2, then tree 3, etc.

:play_button: IMAGE

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

See video:
0s-15s: Current bug situation, onagers stop cutting what is in their queue
15s to 30s: How it previously cut, as you can see the onagers continue to cut what is in their queue

: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 service.

*Occurs 100% of the time

5 Likes
2

I’ve experienced the same problem and this is a major barrier to play the maps thatg I enjoy.

1 Like
3

Thank you both, we’re tracking this issue.

2 Likes
4

As a primarily Bamboo Nothing and Forest Nothing player I do a lot of onager cutting and I have experienced as described above as well.

5

Yeah, this does break onager cutting which affect multiple aoe communities such as Black forest, Michi, Forest Nothing etc and even standard maps which need onager cutting.

6

Yep, I reported a similar issue almost a year ago, it was fixed like 4 months ago and now this :frowning:
Now the queue flags remain visible after the first command is finished, and onagers are stuck staring at the work ahead of them :smiley:

7

atually i find that the current onager queue cutting but is actually way worse than before

prior is that if the queued spot is too close to onager itself, it will not move back to cut and get stuck. however now even the further away targets also doesnt cut after like once or twice.

8

I have the same issue. Very annoying to play forest nothing as I need to spend a LOT more time focussed on the onagers and cannot track my economy/military production. Would be nice if it were fixed

1 Like
9

nothing more tiring than cutting 2001 trees on bf manually without being able to queue actions, takes me back to 2001

1 Like
10

Yeah, it’s frustrating. I don’t understand how these obvious bugs keep getting past testing.
Recently, I’ve noticed that onagers sometimes ignore units or buildings queued for attack – they will start attacking something else. However, the queue flags remain visible until a non-queued command is issued.