Personally I dislike sieges, as I've said many times before. It's why I particularly hated RTW - though the sieges in that were definitely an improvement the issue of stupid AI was still there (arguably worse in fact).
Sieges show the MTW AI at it's worst IMHO.
1) The units that march back and forth in front of the gates getting cut down, routing, coming back for more, etc... before eventually manually attacking the wall on one side and then dying.
2) The cannon/ballista towers (which I never build), which shoot your own men, shoot your walls, gates, towers...
3) The AI approach: I've won many siege defence battles when outnumbered about 10 to 1, simply because the AI was too stupid to attack in a coordinated fashion... but instead sends it's units against you piecemeal (the kind of battles that could be won by simply positioning the troops, starting off and then going down to the pub...)
4) The AI often doesn't bring siege engines, positions them too close to the walls (the crews get shot to pieces) or in a position where they can't all hit the gates/all hit the same piece of wall.
When it comes to attacking it's certainly more in the AI's favour as it's sitting in the same place and the stucture itself adds to the challenge. But I've always found moving your best units out and using autoresolve gives a lower casualty rates than risking your general and decent units attacking a castle that sends a constant spray of "auto arrows" at you. Also if you don't bring siege equipment along with every single army stack, you stand a fair chance of being involved in a few sieges without equipment. In such cases I will almost always starve them out as manually battering down the wall or gates is far too costly.
Bookmarks