Fire rate of archers and cavalry archers are faster than shown fire rate when setting to a small value

[hugehugecat]

GAME INFORMATION

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

• GAME BUILD #: 169123
• GAME PLATFORM: Steam
• OPERATING SYSTEM: Windows 11

ISSUE EXPERIENCED

^{DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.}

When I set attribute for archers and cavalry archers with attack reload time below 1 second, the actual fire rate of these units is faster than the desired fire rate, and the lower reload time the more severity it has. This issue has occurred since last build.

FREQUENCY OF ISSUE

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

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

REPRODUCTION STEPS

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

Here’s the steps to reproduce the issue:

1. Modify attack reload time via trigger or XS scripting, for example, 0.7

2. Shoot something in test scenario and time the shooting interval with your phone

3. Compare the average interval with the reload time set before

EXPECTED RESULT

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

Fire rate should be the same as shown fire rate

[hugehugecat]

@Felizon89 @thieftdp8498 Anyone can sync the fire rate of the shown fire rate and actual fire rate?

[ForgotGamerTag8]

Are you testing the scenario at 1.0x speed, or at the default 1.7x speed?

How many game seconds does it take to shoot 100 times? (Like firing against a fortified wall, doing 1 damage per hit, so time to do 100 damage)

I believe that for units, the shown fire rate should be exactly the same as the actual fire rate for units that fire one projectile. With multiple projectiles that take time to fire (like Chu Ko Nu), actual fire rate is slower; the wiki says, https://ageofempires.fandom.com/wiki/Chu_Ko_Nu_(Age_of_Empires_II)

Reload time
3 in theory
3.44, 3.89 (Elite) in practice

[thieftdp8498]

this maybe due to attack frame delay? havent had much time recently but worth checking there, set it to 0 and try testing it again