YEOMEN card doesnt add the 0.25 multiplier against heavy infantry as described to longbowmen PUP

:arrow_forward: GAME INFORMATION

:point_down: These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
sending the YEOMEN card does NOT add the +0.25 multipliers against heavy infantry as described.
while the range changes does change, the 0.25 multiplier is missing. upgrading the longbowmen to imperial doesnt change the heavy infantry multipliers

  • GAME BUILD #: V100.13.690.0 UP
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED

:point_down: DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.

sending the YEOMEN card does NOT add the +0.25 multipliers against heavy infantry as described.
while the range changes does change, the 0.25 multiplier is missing. upgrading the longbowmen to imperial doesnt change the heavy infantry multipliers

: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. make longbowmen
  2. send the card
    3.observe that it doesnt do what the card says it does
    it’s supposed to be 1.5x against heavy infantry, yet longbowmen have 1.25 while the range did increase

:arrow_forward: EXPECTED RESULT

:point_down: What was SUPPOSED to happen if the bug you encountered were not present?
expected to see 1.5x against heavy infantry

:arrow_forward: IMAGE

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

:arrow_forward: GAME FILES (SAVE / RECORDING)

:point_down: Attach a SAVE GAME (.aoe3Ysav) or GAME RECORDING (.aoe3Yrec) of the match where you encountered the issue. Link it below if using an external file service.

2 Likes

Hello @chrissss159533, Thanks for the report. We are already tracking this issue. :+1:

In the release patch its still bugged