Outdated civ name in history

:play_button: GAME INFORMATION

:backhand_index_pointing_down: These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.

  • GAME BUILD #: Version 101.103.10863.0 (#141935) 17957298
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 11

:play_button: ISSUE EXPERIENCED

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

The year of the Wei Dynasty (Jowi) is November 25, 220 to February 14, 265, and the year of the Chok Dynasty (Chokhan) is 221 to 263, and the year of the O Dynasty (Sonoh) is May 17, 229 to May 1, 280, but the year is incorrect.

Wei Clock

200 AD- Battle of Guando

213 AD - Cáo Cáo, appointed as a great contributor

216 AD - Cáo Cáo, crowned king of the above.

220 AD - Cáo Cáo, died in 220, and his son ascended to the position of Emperor of the Wei Dynasty, founding the Wei

227-234 AD - Zhuge Liang’s North Beal, Han’s Chancellor

249~260 AD - Couteta Occurred Inside Wei ( Gopyeongryeong Rebellion/coup detection - failed)

263 AD - Wei, Han. Conquest

265 AD - Joe Whan to Sima Yan, the fall of Wei
ㄴ 265~ 317 AD - The name of the country has been changed to Jin Dynasty (To be precise, “Western Jin Dynasty”)


221 AD Han Clock

208 AD - Battle of Red Cliffs

212 ~ 214 AD - LIU BEI, the Sichuan Basin peace.

217 ~ 219 5 May AD / Battle of Han-Joong

219 AD - LIU BEI, enthroned, but sieges in the struggle for Jingzhou

221 AD - LIU BEI the establishment of the throne/Shu Han Foundation

222 AD - yí líng zhī zhàn outbreak, break out.

223 AD - LIU BEI, Died, his son, ascended the throne.

225 AD - Zhuge Liang, left for the conquest of the southern region.

227 ~ 234 AD - Zhuge Liang, left for the conquest of the northern region.

244 AD - Battle of Xingshi

247~262 AD - Jiang Wei, left in the conquest of the northern part of the country.

263 AD - collapsed by the expedition of Wei.


Wu Clock

198 AD - Sun Ce, the enthronement of the afternoon

208 AD - Battle of Red Cliffs

219 AD - The battle of j̄ng zh̄u took place.

221 AD - SUN QUAN, Ascending to the King of Wu.

222 AD - Yí líng dà zhàn broke out./ SUN QUAN, declaring himself Emperor.

229 AD - SUN QUAN, enthroned as emperor, founding Wu.

231 AD - A diplomatic dispute with gōngsūn yūn.

242-252 AD - A battle for supremacy has broken out over Wu’s next throne.

265-267 AD - an attempt to move the capital

279-280 AD - Wu, destroyed by the invasion of Jin Dynasty ,

280 AD - Jin Dynasty, Unification of the Chinese Continent.

bove all, Wei’s capital was Upsung/Heodo/Luoyang, Han’s capital was Chengdu alone, and Wu’s capital was Wuhan/Nanjing.

:play_button: FREQUENCY OF ISSUE

:backhand_index_pointing_down: How often does the issue occur? CHOSE ONE; DELETE THE REST!

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

:play_button: REPRODUCTION STEPS

:backhand_index_pointing_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. Launch Age of Empires II: Definitive Edition
  2. Click the cogwheel (located in the top-right corner of the screen, above the parchment icon and to the left of the xbox icon)
    3 . Click History (located in the middle of the screen, the third option)
  3. Scroll down the list of civilisations located on the left side of the screen until you see The Look for the Three Kingdoms civilizations
  4. Click on Wi/Chok/Oh Civilization
  5. Please check the year of the end of civilization.

:play_button: EXPECTED RESULT

:backhand_index_pointing_down: What was SUPPOSED to happen if the bug you encountered were not present?

Wei’s decay period is 265 AD, Han’s decay period is 263 AD, and Wu’s decay period is 280 AD, so it does not exceed 420 AD.

:play_button: IMAGE

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



:play_button: GAME FILES (SAVE / RECORDING)

:backhand_index_pointing_down: 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.

    • not applicable
1 Like