[1.2][bug] Monsters razed cities leave city tiles on the map

from Elemental Forums

An old bug that is still around.

 

I just had a city I had conquered razed by Ghasa Overheart's (troll shaman) army.  When I returned to deal with the Ghara Overheart the city's old tiles showed up on the mini map as city tiles. Look at the 4 tiles between the fire shard and the twilight bees next to Lord Markin's army.

Save file.

 

Also if you scroll right you will see Kraxis's last city Abbeagoobra which has been settled on top of an air altar.

 

Nakisisa

5,675 views 4 replies
Reply #1 from Elemental Forums Top

I'm not sure if this is a bug. It happened for me in FE various times i thought this was working as intended. Also sometimes when you build an outpost, a new city tile appears, i dont know if that's also a bug.

Reply #2 from Elemental Forums Top

AdmiralTorti I think we are talking about different things. 

 

You appear to be talking about tiles with yields for building cities on.

 

I am talking about the label for the tile type which appears above the mini-map which can be plains, hills, mountainside, mountain, ocean, forest, city, etc.

In this case when the monster razed the city its tiles remained city tiles instead of converting back to the original terrain tile.

This stops you from rebuilding on them or casting Birth of Summer spell as the game thinks they are still part of a city.   If you build an outpost on the tile and then raze the outpost the tile will revert back to a terrain tile and can be built on normally.

 

Nakisisa

TouchTasks - Access tasks with ease on Windows touchscreens.
Reply #4 from Elemental Forums Top

"This stops you from rebuilding on them or casting Birth of Summer spell as the game thinks they are still part of a city.   If you build an outpost on the tile and then raze the outpost the tile will revert back to a terrain tile and can be built on normally"

 

Jesus at least this is a work around that lets me play. I was seriously getting annoyed at losing a city and thinking it was permanently gone.

 

Yes, this is a bad bug that needs to be addressed IMO.