More timer gripes
Ok, all the arguments for/against timers in RTW aside, there is one thing that really annoys me. On a siege, if it is no longer possible to win (because time remaining time is less than three minutes and you haven't started the 3 minute capture timer yet), the battle should *end*. I just "lost" my assault on thebes because there were a dozen enemy troops on a wall (that had been fighting for 25 real-world minutes on a wall with my troops. The rest of the city was clear. I lost with *14* seconds left on the 3 minute clock. That is ridiculous! There was no rational reason why I should have "lost" that battle, and then had to wait three minutes to find out. I can see it now:
General: Ok, that's it. Time to retreat. Head to the hills!
Aide: But sir, the enemy is crushed! There are twelve remaining enemy soldiers holed up on the wall in the corner of the city, but they are trapped.
General: It doesn't matter! We did not stay in the central square long enough before the defenders transformation completed (timer finished), and they are now rising up as horrible super-destructo beasts that will destroy us all!
Aide: But surely 12 horrible monsters trapped up on the walls cannot possibly survive against four full 240-men levy pikemen Phalanxes guarding the only exit!
General: NO! We must leave now! Who knows what horrible powers they have! Order the retreat!
Aide: But sir ...
(sound of metal flying through air, then blood spraying out)
General: You! You are my new aide! Send message for a full retreat! And do not question my orders or you too will be "replaced"!
Oh, did I mention that Thebes somehow generated two full chariot units, and three other units after the retreat? I'm going to use the no-timer cheat before I play again. This was a completely unreasonable use of the timer, IMO. About the only good that came from this was the fact that I killed the last family member of the faction (Egypt) and thus Thebes is now in rebel hands.
Reply With Quote
Originally Posted by hoof
Bookmarks