Bugs in Last City of the Incas (Act 3 Steel)

:arrow_forward: GAME INFORMATION

  • **BUILD #:100.12.1529.0
  • PLATFORM: Steam
  • OS: Windows 10

:arrow_forward: ISSUE EXPERIENCED

:question: DESCRIBE THE ISSUE IN DETAIL (below). Limit to ONE issue per thread.

There are some bugs in the Last City of the Incas scenario:
There is a gap in the wall south of the base, enemies can get in.
Every city from the incas are set to Mother Nature rather than to the ally player, and you can attack each building except the warhuts and the fortresses.
The Fortresses are still being referred as temples in the scenario, not sure if it’s a bug but the fortresses aren’t named “temple” so there could be confussion, the characters and the interface should say fortress rather than temple or change their name.
Some units get stuck on inca buildings (see bellow)

:arrow_forward: FREQUENCY OF ISSUE

:question: How often does the issue occur? CHOSE ONE; DELETE THE REST.

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

:arrow_forward: REPRODUCTION STEPS

:question: List the DETAILED STEPS we can take to reproduce the issue… Be descriptive!

Here’s the steps to reproduce the issue:

  1. Load Last City of the Incas
  2. See the south wall to see the gap there
  3. Use a unit to attack an inca building and they will even thought they are your ally buildings (but set to mother nature)
  4. See the interface talking about temples when there are now fortresses.
  5. Move some settlers near the inca buildings picture bellow and they should get stuck.

:arrow_forward: EXPECTED RESULT

:question: What was supposed to happen if the bug you encountered were not present?
The wall should be complete.
You shouldn’t be able to burn enemy city.
Fortresses should be correctly identified.
Settlers shouldn’t get stuck.

:arrow_forward: ACTUAL RESULT

:question: What actually happened (what went wrong) because of the issue you’re reporting?
Wall is incomplete.
You can attack allied city.
Fortresses are called temples
Settlers get stuck.

:arrow_forward: IMAGE & ATTACHMENTS

:question: Attach a relevant PICTURE (.jpg, .png, .gif), VIDEO (.mp4, YouTube), DXDIAG FILE (.txt), or CRASH/GAME LOGS (.aoe2record, .txt) below.

Also, the AI should really be more aggressive in this scenario: in the original one, the temples didn’t had an attack, now they are powerful buildings and the Circle don’t really attack them, I never felt pressured and won the scenario with 4 out of 8 pieces or artillery.

Same issues found by me too. The gap in the wall is there and the Kancha Houses buildings are owned by Mother Nature ande can be attacked by the player. The Circle still destroyed a “Temple” when I was playing an another day but this is easy to protect even though I was playing on Hard mode (The AI isn’t much better at some stuff on here though anyway.) I anticipate they won’t be able to correct the temple issue besides pulling the assets from the original game as you can’t easily dub or cut the words that Amelia says. They got away with cutting the last bit off of Kanyenke to make it Ka:nien but this is more difficult. I say put the original assets for the Temples back in this game and touch them up a bit or flare the map so the player can identify the so called “Temples.”

Theres also a random “Native Building” outside of your base owned by Mother Nature that lets you upgrade a “Traveling Merchant”? which also doesn’t do anything and is purely a resource loss. Ij fact this is the case with a lot o Native buildings which seem to have upgrades for a stagecoach for a trade route for some reason

I say put the original assets for the Temples back in this game and touch them up a bit or flare the map so the player can identify the so called “Temples.”

Curiously enough, the updated models for the Inca Temple and Inca Outpost are present in the game. You can see them in the Inca Overview video they released last week, and in the Scenario Editor.

I agree with the notion of putting the Temples back in, and maybe even some of the old Inca Outposts. It would be a shame to let these assets go unused.

1 Like

This issue is currently being tracked, thank you for the report.