Old waypoint behaviour still broken (7694700)

:arrow_forward: GAME INFORMATION

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

  • GAME BUILD #: 7694700
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED


When using the old waypoint behavior, shift queuing foundations is still broken since first DE release.
With patch 7694700 it’s even more visual with the numbered actions.

After releasing shift and then placing the final foundations, all numbered actions are cancelled, the foundations are still placed and the villager walks straight to the final (lastly) placed foundation.

The only ways to shift queue buildings on the old waypoint behavior is to press escape instead releasing shift and placing the final foundation. Then the actions are numbered correctly.

What I do often is to shift queue through all the placed foundations again.

:arrow_forward: FREQUENCY OF ISSUE

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

  • 100% of the time / matches I play (ALWAYS)

:arrow_forward: REPRODUCTION STEPS

:point_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. In options/game disable new waypoint behavior
  2. Go into any game
  3. Shift queue palisade foundations and release shift before placing the last numbered action.

:arrow_forward: EXPECTED RESULT

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

The last action after releasing shift will still be numbered with the highest number, and the villager will work through all numbers.

:arrow_forward: IMAGE

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

Before releasing shift is shown below:

After releasing shift and placing the final foundations, which is supposed to be also numbered, is shown below:

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

…Since someone is working on the waypoint behavior, I thought this can come in handy…

Here would be my advice personally: Just learn the new waypoints. They are better. Old hotkeys on the other hand…

Apart from that this is still a bug report for an obvious bug in the game.

Also I don’t see how the new waypoint behavior is better, expect that sometimes a click is saved and it’s easier to switch to StarCraft.
Can you elaborate @TheConqueror753 ?

Hey everyone, this is considered a behavior by design.
Thx for understanding, have a nice day :slight_smile:

Well the design is bugged, that is what I am trying to say. @ChristheCo
Even if it doesn’t cause program errors, it’s still a bug, because it’s unexpected behavior.

Similar to castles/tower locking on an enemy building and ignoring approaching units (This if fixed afaik).
Or Portuguese bbt losing the ability to hit moving target after researching both ballistics and the unique tech.
Or range indicators showing the wrong range.

It won’t crash the game, but it’s clearly a bug.