Gort
Emperor
- Joined
- Nov 7, 2010
- Messages
- 1,518
They don't repair themselves; you have to run a Repair Walls Project, which you can only do if the walls haven't been attacked in the last 3 turns.
Whoa. Completely missed that one.
They don't repair themselves; you have to run a Repair Walls Project, which you can only do if the walls haven't been attacked in the last 3 turns.
They don't repair themselves; you have to run a Repair Walls Project, which you can only do if the walls haven't been attacked in the last 3 turns.
I think it makes more sense to have some sort of reduction of city strength per turn (for X turns) opposed to health, basically making the city weaker without actually reducing the population. I don't think fortifying a few units around a city for 10 turns should be enough. It should require an actual attack at some point.An AI-friendly change I'd like to see is for besieged cities to lose 10% of their health every turn (so a city besieged for 10 turns will fall, even if it's never attacked). The AI can besiege cities, and this change would circumvent the AI reluctance to actually attack. Plus, I think it makes sense historically (the city is starving, after all) and would make navies more significant (since you'll need navies to besiege coastal cities). It would also tip the balance a little bit away from ranged units and toward melee units which can exert zone of control.
Didn't know that either. Wonder why it doesn't show up as a normal "repair" as with buildings when you capture a city?They don't repair themselves; you have to run a Repair Walls Project, which you can only do if the walls haven't been attacked in the last 3 turns.
I am an average player and at emperor level I have never lost a single city in dozens of games, even the very first ones.
Am I a super player or the AI has been programmed by an alien species which ignores the word " strategy " ??
@Gort: Epic, if completely disheartening, read about the AI's (in)capability in besieging cities. Somehow, it seems as if Civ6 AI is even less capable than Civ5 AI?
I disagree. Almost on the other hand, I think cities are too easy to conquer if you know what you're doing. The new siege mechanism and the fact that you can knock down walls and hence remove city attack effectively counters many of the problems inherent in Civ5 city combat. City attacks might be tuned down a bit in damage, but on the bottom line, I think the problem is not cities being too hard to take, but the AI being completely clueless about what it's doing.
How long it takes the AI to conquer a capital city that shoots at them
Turn 208: Start
Turn 211: Meet Aztecs, declare war
Turn 219: Enemy city state machinegun shows up, gets shot by city center, retreats
Turn 240: Barbarian machinegun shows up, gets shot by city center and encampment, dies
Turn 252: First Aztec military unit shows up, half-dead infantryman
Turn 279: Carthage (neighbouring enemy city state) invades with two machineguns, a helicopter, an infantryman and a rocket artillery
Turn 284: City and encampment shoot down one of Carthage's helicopters, their rocket artillery has retreated having not yet fired a shot
Turn 285: City kills a Carthaginian machinegun
Turn 291: City kills the Carthaginian rocket artillery
Turn 302: City kills a Carthaginian infantryman - there are now no enemies near the capital
Turn 311: Aztecs invade in force - a modern tank army and two mechanised infantry. The tank army is bombarded for 6 damage by the encampment
Turn 312: The modern tank army attacks the encampment and dents it a bit
Turn 314: The two mechanised infantry form a corps
Turn 315: The modern tank army leaves
Turn 319: An Aztec and a Carthaginian helicopter show up
Turn 320: A Carthaginian rocket artillery shows up
Turn 321: The Carthaginian rocket artillery attacks the city for decent damage
Turn 323: The city and encampment destroy the Carthaginian helicopter
Turn 329: The city and encampment destroy the Carthaginian rocket artillery
Turn 347: I make a builder to repair some damage to the tiles around the city, a half-dead Aztec helicopter rushes adjacent from out of the fog of war. It is shot by the capital and encampment, I move the builder back into the capital.
Turn 348: I move the builder out again and the same even-more-dead Aztec helicopter rushes adjacent from out of the fog of war. It is shot and destroyed by the capital and encampment.
Turn 359: I notice a bug whereby the capital and the encampment's walls are not healing, even though there are no enemies nearby, and haven't been for about ten turns now.
Turn 360: Amsterdam invades with two mechanised infantry and a machinegun
Turn 366: Lisbon invades from a different side with two mechanised infantry and a machinegun
Turn 371: Carthage invades from a different side with one mechanised infantry. Lisbon brings in two rocket artillery.
Turn 374: City destroys one of Lisbon's mechanised infantry
Turn 375: Both of Lisbon's rocket artillery hit the encampment. Amsterdam and Carthage withdraw their forces.
Turn 376: Both of Lisbon's rocket artillery hit the encampment. It's now almost wall-less.
Turn 377: Both of Lisbon's rocket artillery hit the encampment. It's now in the red and cannot fire for the rest of the game since its walls are not regenerating.
Turn 379: One of Lisbon's rocket artillery hits the city.
Turn 380: One of Lisbon's rocket artillery hits the city.
Turn 382: One of Lisbon's rocket artillery hits the city. It is now without walls and cannot fire for the rest of the game since its walls are not regenerating.
Turn 383: One of Lisbon's rocket artillery hits the city, and one of their mechanised infantry assaults. It's now without fortifications and on half health.
Turn 384: Both of Lisbon's rocket artillery hit the city. It's now on a sliver of health.
Turn 385: Both of Lisbon's rocket artillery hit the city. It's now on a sliver of health.
Turn 386: Both of Lisbon's rocket artillery hit the city. It's now on a sliver of health. The adjacent mechanised infantry could probably take it but is on red health and healing 5 HP a turn.
Turn 387: Both of Lisbon's rocket artillery hit the city, and the adjacent mechanised infantry attacks, but fails to take the city somehow.
Turn 388: One rocket artillery hits the city.
Turn 389: One rocket artillery hits the city.
Turn 390: Amsterdam invades with three mechanised infantry.
Turn 391: One rocket artillery and a mechanised infantry attacks, but again they fail to take the city. It's been unable to fire for about ten turns and been in red health, but somehow they can't take it.
Turn 392: Two rocket artillery and a machinegun hit the city.
Turn 393: The city is now under siege with a single hitpoint. Is there something weird where city states can't conquer capitals?
Turn 394: Two rocket artillery, a machinegun and a mechanised infantry hit the city.
Turn 395: Two rocket artillery, a machinegun and a mechanised infantry hit the city.
Turn 396: The city gets attacked six times and my fingers are getting tired of typing.
Turn 397: Four attacks.
Turn 398: Five attacks.
Turn 399: Six attacks.
Turn 400: Five attacks.
Turn 401: Seven attacks.
For the next 22 turns my city has been completely surrounded by city state units and attacked about seven times. Aztecs are basically nowhere to be seen, so I decide to take over the city states with my envoys to break this deadlock. We struggle over the city states for a bit, but in the end I get one and they get two.
Turn 429: Somehow my capital is still sieged even though there are no enemy units near it.
Turn 432: My capital un-sieges when some enemies approach it. Huh.
Turn 433: Carthage hits my capital with a mechanised infantry.
Turn 436: After a few turns of attacks, my capital has no health again.
Turn 443: Carthage is still attacking the capital, but now an Aztec modern tank army has shown up.
Turn 444: Carthage is still attacking, now there are two Aztec modern tank armies.
Turn 448: The Aztec tank armies withdraw.
Turn 467: An Aztec tank army comes back.
Turn 468: The tank army is now adjacent to my capital, which has 1 HP.
Turn 470: The tank army is sitting near the capital, which is now healing. The Carthaginians have withdrawn.
Turn 475: The Aztecs now have four tank armies and a mechanised army within five tiles of my capital.
Turn 478: The Aztecs are now hitting Lisbon, ignoring my capital entirely. It has healed to full health but still has no walls.
Turn 483: The Aztecs conquer Lisbon.
Turn 486: The Aztecs now have six tank armies and one mechanised army in my territory.
Turn 488: The Aztecs leave.
Turn 498: The Aztecs now have eight tank armies in my territory.
Turn 501: Aztecs one-shot kill my encampment.
Turn 508: The Aztecs leave again.
Turn 513: OK, it's been more than 300 turns and nothing's happening. I'm giving up.
It doesnt matter if they do or not... they CAN NOT seem to fix their own game. If the dev isnt able to debug and fix the AI in a timely manner ( and this patch should have had a HUGE section of AI fixes) then fire him. If he can do his job then find someone that can and will. It either seem the devs on the AI team dont have the heart or are completely incompetent. I will be speaking with whoever I can at some point and maybe even an open letter to Firaxis and 2K.This seems extremely bad. Do the devs actually read through these forums? An AI that doesn't know how to war properly makes the single player games basically broken on higher difficulties.
You can't not go to war, because the AI has an advantage in tech and cities, yet you can't go to war because the AI can't attack/defend themselves properly. So what are you expected to do?
I agree it is super easy to take cities now because the AI is not really defending. My point is that when properly defended they can be almost impossible to take when terrain limits the number of units that can attack per turn or limit approach attack and retreat options.
The AI doesn't use garrisoned ranged units currently. If a city has walls, an encampment and two ranged units that's 4 ranged shots per turn. If it is not possible to make a single turn approach where you can attack the city that turn or the next turn that unit will be decimated before they do any damage.
If the ranged units are level 2 upgrades then the 4 ranged attacks are going to kill 1-2 units per turn as they approach.
Do you think if a human was defending a city that it would still be easy to take without overwhelming forces?
I may try that, maybe using 10% of remaining health each turn until a minimum value is reached, I wouldn't want the city to fall without at least a fight and lowering the health may be enough to trigger an AI attack.An AI-friendly change I'd like to see is for besieged cities to lose 10% of their health every turn (so a city besieged for 10 turns will fall, even if it's never attacked). The AI can besiege cities, and this change would circumvent the AI reluctance to actually attack. Plus, I think it makes sense historically (the city is starving, after all) and would make navies more significant (since you'll need navies to besiege coastal cities). It would also tip the balance a little bit away from ranged units and toward melee units which can exert zone of control.
Does the AI bring siege towers? 2 Samurai and a Siege Tower can bring down a medieval city with walls in one turn if it's on flat land. Against 2 Crossbowman and an encampment I would think 4 Knights and a Siege Tower could take out the encampment and then the city in about 3 turns. Maybe the AI doesn't build any support units or can't coordinate them well enough?
I like the idea that you would need to siege the city in order to attack without damage or maybe like you said lose a portion of city health regardless of attack. But if the city just lost 10% per turn then the attack power of the units becomes irrelevant. The amount of city health lost should be dictated by the combined strength of the surrounding units vs the city defense. You shouldn't be able to take a city surrounded with warriors in the same time it takes to take the same city with modern infantry.An AI-friendly change I'd like to see is for besieged cities to lose 10% of their health every turn (so a city besieged for 10 turns will fall, even if it's never attacked). The AI can besiege cities, and this change would circumvent the AI reluctance to actually attack. Plus, I think it makes sense historically (the city is starving, after all) and would make navies more significant (since you'll need navies to besiege coastal cities). It would also tip the balance a little bit away from ranged units and toward melee units which can exert zone of control.
Samaurai is a bit of a special situation because of it's full attack strength even when injured. But even in that case I have to disagree. I'm talking about having to attack a city with human level AI defending with walls, encampment and 2 upgraded crossbows in a city. Add in an obstacle like a river that covers 3 sides of the city hex, then things become exponentially more difficult.
Completely agree. The AI has no idea how to use ranged units for assault or defense. I'm just concerned that once they fix the AI ability to garrison and defend cities with ranged units that the AI will never be able to take each other's cities even with improved aggressiveness.The AI doesn't even try to succeed, though. Like you see ranged units start their turn in shooting range of your city but they don't shoot it. Melee units just milling around next to a city, not attacking it.
"Enemy in range -> Attack it" seems like the least we could expect from the combat AI. I could understand if the AI units were over-confident, attacking when they shouldn't, or shooting the first thing in range when there's a better target a move away - that's why AI players get difficulty bonuses to help them replace losses and have stronger units in the first place. But the AI units not even using their attacks is kind of unforgivable.