I still can't deal with quotes as elegant as you guys do, but I'll do my best:
I wrote:
I'd like to discuss about battles:
8. City defence: Lets assume a city has just been built on a hill square. A standart, untrained 3 strength archer gets 50% hills bonus, 50% city bonus. Assuming it is also fortified, so that it gets a %25 bonus. So its defending strength is 6,75. And it has a first strike. So this cheap, primitive, untrained unit is already a solid defender. A swordsman, which is a formidable unit will lose against such a unit most of the time. The iron age bowman is even more stronger when defending, it is an incredible 9.
First of all, I think the archer shouldn't get a 50% bonus automatically. A newly found settlement with some huts and tents shouldn't be giving such defensive advantages. I think the archer should get its bonus, first when the city builds fortifications, i.e. palisades or walls. I hope this is not very complicated to implement, because we have already attacking malus for mounted units, when walls are present.
Ok, you can argue that archer is a ranged unit and the heavy melee units are struggling running up to the hill and they die out before they can reach the enemy, hiding behind huts and tents, shooting from windows whatever. But then, the best units to attack archers should be the archers. But this is also not the case. They don't come into consideration in Civ 4 if you are planning to attack a city.
Hawkwood answered:
Unfortunately, it is quite complicated to implement, and moreover would surely confuse many players. Also, from my first-hand experience of siege mode in Mount & Blade multiplayer, which I feel manages to approximate a real assault on a fortification quite well: defending archers are deadly; attacking archers are just moving targets - while they sometimes manage a good shot or two, you have a much better chance of survival if you are instead well-armored and carrying a shield. Then there are much more chances that, as an attacker, you actually live long enough to cause some serious harm to enemy.
It is sad to hear that it is hard to implement. :/ I don't think it would confuse many players though. I propose that wall gives further advantage for defending ranged units, which is pretty self explanatory.
I wrote:
9. Ok, in reality it was very very difficult to attack and invade a fortified city. Instead we see long lasting sieges, hoping that the city surrenders because of starvation, diseases etc. Of course, we don't have such mechanism in civilization, we should rely on direct attack to capture cities. And the odds of surviving when attacking a city is currently quite poor. Therefore I'd propose to tilt the balance slightly in attackers' favour. I'd really prefer a more dynamic capturing and recapturing and re-recapturing of cities. Why? I have two reasons:
a) Every time a city is captured, many improvements has to be rebuilt. So it will not be so easy to end up with many perfect cities so early in the game.
b) The AI really likes to assemble large armies. He invests a lot in them, but at the end, he can't see the benefit of them, he can't invade any cities, and eventually gets overplayed by a smart human player, who possesses a modest military for defense and invests in libraries etc. instead.
Hawkwood answered:
Tipping the balance in attackers' favor is very dangerous from balance point of view. It creates a positive feedback loop - the stronger you are, the stronger you will inevitably become in future. Also, you are forgetting one thing - while defenders indeed lose less units, they suffer from the very fact that the war is conducted on their territory - pillaged countryside can hurt your civ quite a bit, and AI is actually good at it.
I agree that AI does a good job by pillaging countryside. As a result the targeted civilization will collapse at some point. So playing purely defensively is not a good strategy at all, which is good. But my actual the point is, you have already tipped the balance well in the favor of defenders by implementing iron age archers, and made it already very difficult for the attacker.
I wrote:
10. You have been working hard on the AI of siege engines recently, with all these bombardment etc. It is a complicated task. Why not getting rid of this ranged attack altogether and doing the following: For example, a bombard gets a rather high strength of 8 or even 10 and attacks normally, but can cause a rather low maximum damage (for example 20%). This way it will survive most of the battles, doing the same effect as the ranged attack. In some cases it will get wounded, but this represents such effects like the machinery gets older and needed to be repaired and the ammunition gets lower. The more modern artillery gets a slightly higher maximum damage, and also some collateral damage. That way, it will be quite robust and AI will understand and manage the siege weapons more easily.
Hawkwood answered:
So basically you advocate us going back to vanilla BtS system?
Yes, I advocate going back to vanilla BtS system, but with one huge different: I set the damage cap way lower. Assume that: Let's take a unit, and give it 99 strength, 99 first strikes and, a maximum damage of 20%. When attacking, they will do the exactly same thing as today's bombard with ranged attack, and the AI will be able to understand and manage them much better.
Of course, we shouldn't give those units 99 str, because AI will probably start building nothing else but bombards. But for bombards, something like 8-10 str should do the trick, you can give it defensive malus too, if you wish. Few years ago, I used to play Rise of Mankind: A New Dawn, and I used to edit XML extensively, and I also changed the siege units as I've explained. And it just worked fine.
To support my view further that AI can't manage siege weapons properly, an example from my most recent game: I was invading Washington's territory in the late classical/early middle ages. He had a lot of catapults (I guess about 50% of his all troops), and he was trying to attack my invading army with them in the beginning of his turn, followed by an attack by other few units. Obviously, he is hoping to wear down my army with catapults, and destroying it with other units later; a behaviour we see in vanilla Civ. The problem is, that the AI doesn't realize that the catapult has no wearing down effect anymore, and their catapults are no match to my Chasquis Scouts on the hills, they also come with many first strikes, so most of the time they defeat those catapults without getting any damage.