GAME INFORMATION
These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
- GAME BUILD #: #66692
- GAME PLATFORM: Steam
- OPERATING SYSTEM: Windows 10
ISSUE EXPERIENCED
DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
In the update 66692, I found some AI changes in compagn scenarios, the most obvious thing is that AI won’t correctly research several military techs.
(All games discribed below are played in “hard” difficulty.)
For example, with many times of test by myself, in the 5th scenario “Jihad!” of “Saladin”, AI player “Tiberias" (blue) won’t research “Paladin”, “Heavy Camel Rider” and “Seige Ram”, and AI player “Tire” (Yellow) won’t research “Galleon” as they will do in previous build of AOE2DE and the original AOE2(The Conquerors).
This abnormity is found in several other compaign scenarios, such as in “Bapheus” scenario, AI player “Candar” (cyan) won’t research “Champion”, even instead of sending “Man-at-Arms” to attack.
I’m sure in previous builds things won’t happen like that.
BY THE WAY: The population limitation of “5.Jihad!” and “6.The Lion and the Demon” of “Saladin” are incorrect. (Not sure if there are more like this.)
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:
- Start “5.Jihad!” scenario of “Saladin” with difficulty set to hard.
- Just defend, do not attack.
- Wait, and wait forever
EXPECTED RESULT
What was SUPPOSED to happen if the bug you encountered were not present?
AI player “Tiberias" (blue) won’t research “Paladin”, “Heavy Camel Rider” and “Seige Ram”.
AI player “Tire” (Yellow) won’t research “Galleon”.
IMAGE
ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
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.