These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
- GAME BUILD #: Latest Update 61213
- GAME PLATFORM: Steam
- OPERATING SYSTEM: Windows 10
DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
Sorry to bother you with this. But I’ve been seeing this issue since the Update Preview and I thought it was probably a one-off incident but now it is happening all the time.
At least ONE AI player will go full Age 2 aggression in team games and never advance beyond Commerce Age. They focus on large armies of commerce age units, and continuously make commerce age armies at the cost of aging up. They will make villagers and have an economy (upto 45 vils) but never save any money to age.
They will never be able to compete with opponents in Fortress/Industrial in the long run. This can happen to allies or enemies and I’ve noticed it happen to Spain, India, Germany, Lakota in my games so far.
It becomes a vicious cycle where towards late game, they keep losing units and retraining, losing and retraining, and hence never have the resources to age up and make better troops.
How often does the issue occur? CHOSE ONE; DELETE THE REST!
Happens in almost all team games with AI that I’ve played in the PUP and in this latest build.
List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!
Here’s the steps to reproduce the issue:
- Play a skirmish game with AI as allies and enemies.
- Observe AI behavior.
- Some of them may keep training troops with their resources and never age up.
What was SUPPOSED to happen if the bug you encountered were not present?
AI players should age up to keep up with opponents.
ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
Queen Isabella here is in Commerce Age, everybody else Industrial, and she is losing all battles. And also capped herself at 43 villagers - so it isn’t like the AI got raided hard and fell behind.
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.
Here is a recording from the current build:
Record Game 2022-02-02 00-55-13.age3Yrec (11.9 MB)
I also have several recordings from the PUP:
Record Game 2022-01-25 12-12-05.age3Yrec (10.0 MB)
Record Game 2022-01-31 16-04-15.age3Yrec (14.1 MB)