TC rally point randomly being set

: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 #: 162286
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 11

:play_button: ISSUE EXPERIENCED

The TC randomly sets the rally point to some point on the map.

:play_button: FREQUENCY OF ISSUE

:backhand_index_pointing_down: How often does the issue occur? CHOSE ONE; DELETE THE REST !

  • Less than 25% of the time / matches I play (RARELY)

:play_button: REPRODUCTION STEPS

:backhand_index_pointing_down: List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!

I am not certain how to reproduce the issue, but it seems to occur when switching be a unit and going to the TC.

In the recording you can see that just before 03:04 I select the vil and queue it to the berries, then I select the scout and patrol it forward. Then at 03:04 I select the TC (I have a go to TC hotkey and the screen centres on the TC so I know I selected the TC), at this time stamp the TC rally point it set to the woodline. I then reselect the vil that was sent to berries. At 03:05 the TC rally point is set in the eastern corner of the map. Following with view lock, I never go in that part of the map. It appears that the rally point get sets as I switch from the TC to the vil.

I am very confident that I did not miss-click on the minimap as it is at the start of dark age and I was surprised when I heard the TC set rally point noise but I had my cursor in the middle of the screen.

:play_button: EXPECTED RESULT

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

The TC only sets the rally point when the command is issued.

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

The bug occurs at 03:04-03:05.

In case this is helpful, Grubby had a similar experience on stream and went back to analyse it. You really need to have a screen recording to be able to catch the bug. You can find it here at 03:51:20 on this stream: Twitch

Thanks for the report!
We are luckily already tracking the issue!

1 Like