I saw another post about Town Centers sometimes stop attacking and I was wondering if anybody else has seen this?
I had a game today where my Keeps stopped using their Cannon Emplacement twice and its super frustrating. In one case a fight was occurring under my Keep, I researched Cannon Emplacement, the research finished, shot a single cannonball, and never fired the cannonball again despite the fight lasting under that keep for multiple minutes.
I would like to theorize why that would happen and I have 2 potential Troubleshooting leads but its hard to test against AI. Also worth noting is I play exclusively HRE so this bug could be Civ-specific. Another thing worth noting is I often retarget my TC / Keeps which may result in the bug occurring.
1st lead is it has to do with the building becoming obsessed with targeting a Single unit and waits until it can attack that unit until it will look for another target. Hunch for this lead mostly comes from the current Prelate bug, where moving a Prelate while it is trying to Inspire a villager will prevent him from Auto-Inspiring other Villagers, since his AI is trying to inspire the villager he was moved away from before looking for other Villagers to inspire.
I suspect a similar behavior may be happening as well with the Keeps, whether a target it was deciding it would target next moved out of range in the last second / tick, or perhaps a unit died right as it was about to shoot. (IE. the Keep decided, "I am about to shoot that Man-at-Arms with the Cannon Emplacement, he dies from arrow fire, and the cannon refuses to retarget.)
2nd lead is it has to do with Garrisoning and Un-Garrisoning messing with the Keep / Town Center / Outpost somehow. Either Garrisoning / Un-Garrisoning adding and removing the wrong type of attack for some reason. Speculation for this lead has to do with me noticing this bug when I frequently Garrison and Un-Garrison a building ie. my Primary TC.
The intention of this post is to get to the bottom of this issue, and I would like to know if anyone has any info on this? Ideally we would be able to create instructions to reproduce the bug and can then submit it as a bug report.