Health Bars for Warships often don't work the same as for other units

:arrow_forward: GAME INFORMATION

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

  • GAME BUILD #: Current, but it has also happened in previous builds
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED


For some reason, with most of my water battles, the HP bars don’t appear on warships. I have it set to the default HP bars, so they appear when a unit is damaged, selected, or hovered over. None of this happens for warships. It seems to work fine for transports, not sure about other ships, and I know it works fine for land units.

:arrow_forward: FREQUENCY OF ISSUE

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

I don’t really play too many maps with water conflict, but I might say:

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

: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. I don’t know. Start by setting health bars to default.
  2. Maybe play Barabarossa 5, and take Constantinople’s fleet? That is what I was doing when it most recently occured.

:arrow_forward: EXPECTED RESULT

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

I expect the HP bars to work normally, and actually let me better control my ships without having to worry about losing fights badly because I can’t judge HP without selecting ships, especially for enemies.

:arrow_forward: IMAGE

:point_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
The boats are selected, yet no HP bars.
As opposed to transport ships:

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

1 Like

Hi @TheConqueror753 !

Thanks, we are already tracking this issue!