GAME INFORMATION
These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
- GAME BUILD #: 169652
- GAME PLATFORM: Steam
- OPERATING SYSTEM: Windows 11
ISSUE EXPERIENCED
DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
Mercenary Peltasts and Rhodian Slingers are units available in the Scenario Editor. According to their descriptions, they “cannot attack at close range”. Contrary to this, they have no minimum range and thus can attack at close range.
The same goes for the similar units Alexander’s Peltast and Alexander’s Slinger, which appear in the Alexander campaign.
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 descriptive!
Here’s the steps to reproduce the issue:
- Open the Scenario Editor and place a Mercenary Peltast and a Rhodian Slinger for Player 1 in the Scenario Editor. Place something they can attack (e.g. the Gaia-only unit Dummy Target) next to them, no empty tiles between attacker and attacked unit.
- Test the scenario and let both units attack. It can be seen that the Peltast and Slinger are unaffected by minimum range. Select one and read the description by hovering over its icon (extended tooltips have to be enabled). It is claimed that it cannot attack at close range.
EXPECTED RESULT
What was SUPPOSED to happen if the bug you encountered were not present?
If the the units are intended to have minimum range, they should have it. Otherwise, the descriptions have to be corrected.
IMAGE
ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
Description of the Mercenary Peltast implies minimum range, which it doesn’t have:
The same goes for the Rhodian Slinger:
The claim “cannot attack at close range” is also part of Alexander’s Peltast and Alexander’s Slinger’s descriptions.
However, all four units are able to attack at close range:
GAME FILES (SAVE / RECORDING)
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.


