Full tech tree not clearing (in regard to settlements)

: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 #: ######
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 10

:play_button: ISSUE EXPERIENCED

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

If the last game played was a custom scenario with Full Tech Tree enabled, the next random map game (including ranked) will remember FTT and not enable Settlements for civilizations that should get them. This will cause an out of sync in multiplayer when a player goes to build a lumber camp, etc. (that should have been a settlement).
A similar effect is NOT observed with mule carts.

:play_button: FREQUENCY OF ISSUE

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

  • 100% of the time

: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. Play a scenario with the full tech tree option enabled (may need to be the option that saves in the file.)
  2. Set up another skirmish game and verify that full tech tree is disabled.
  3. Select a civilization that should get settlements
  4. Start the game:
  5. Observe that the civilization that should build settlements builds mills, lumber camps, and mining camps instead.

:play_button: EXPECTED RESULT

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

The Full Tech Tree option should properly and fully reset for civilizations that build settlements.

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

MP Replay v101.103.48987.0 @2026.08.01 170400 (2).aoe2record (788.9 KB)