When you use the staked archers command, do the archers still shoot arrows?
Do you guys use time limits on battles or not? any reasons?
thanks
When you use the staked archers command, do the archers still shoot arrows?
Do you guys use time limits on battles or not? any reasons?
thanks
Sure, the archers still shoot arrows. The command to use stakes is really handy because the archers can shoot arrows over the stakes and still be relatively safe from frontal attacks.
I personally use time limits because the AI will sometimes get stuck on sieges and you'll just have to wait it out. It also helps on defensive battles where you don't want to forsake your nice position and the AI doesn't want to attack you.
If I wanted to be [jerked] around and have my intelligence insulted, I'd go back to church.
-Bill Maher
My reasons for not using time limits are:
I don't use time limits as I like to play the battle out to the end.
In the field as I use mostly all cavalry armies, one good spot can quickly be substituted with another. Also playing defensive with an all cav army is not the same as playing defensive with a balanced or mostly infantry army. You move anyway, and almost never stop, except to shoot, then you move again. Usually you don't hold a single position but many and force the enemy to react. Sometimes you do get nice cliffs, so you go up there shoot as much as you can and then move. Point is you're not stationary long.
I also feel that I can win otherwise unwinnable battles with the time limit. I can just run around the map as defender until the time runs out. Though I actually don't do that, but I feel tempted to .. lol.
I rarely let an enemy siege a city, I always catch the enemy army outside and cut it downm before it gets to it's target.
If, on rare, occasion, an enemy sieges a city it's usually met by a relieving army from outside the city. If, on even rarer occasion, an enemy assualts the city, I have'nt seen the AI loop bug, or just standing there, I usually end up attacking anyway.
Lastly I like to take my time and I don't want to be looking at the time.
For me the time limit is a negative. I don't like it, never use it.
If you remember me from M:TW days add me on Steam, do mention your org name.
http://www.steamcommunity.com/id/__shak
I couldn't imagine not using time limits. I often fight very outnumbered and sometimes it is great fun, desperately trying to survive until the counter runs down. I feel like Wellington at Waterloo "Give me night or give me Blucher".
I always use time limits. It feels more realistic, to me, that there should be some time pressure on. It also offers the possibility of more "even" outcomes to battles.
That being said, I rarely find that field battles take a long time to resolve - the only occasions when the time limit actually expires are in siege battles.
I never used to use time limits in MTW and RTW because as far as I was concerned a lot of battles used to take all day, certainly not 45 minutes max.
But then sometimes on Rome I'd notice something which have become much more prevalant with M2TW- passive ai.
So now I do have them on just because when I'm on the defensive it forces the ai into action.
Although sometimes it winds me up because I've got at fantastic defensive position and the ai just doesn't bother to try and assault me at all.
I've always had the time limit on in all TW games. I can't remember that it ever was a problem, like not having enough time for an assault (Maybe the one or other castle attack in MTW, not sure). There's plenty of time for all battles and I always play them out to the end.
As it is now I need to have it on, because when the AI siege-attacks you and runs out of possibilities to break/scale your walls, it will just stand there and wait.
I'd prefer it when the AI would consider retreating rather than us waiting for sunset.
![]()
Singleplayer: Download beta_8
Multiplayer: Download beta_5.All.in.1
I'll build a mountain of corpses - Ogami Itto, Lone Wolf & Cub
Sometimes standing up for your friends means killing a whole lot of people - Sin City, by Frank Miller
I always use time limits. Only once or twice have I ever come close to the time limit, both times when I was assaulting a city in the RTR mod. Once I ran out of time, and once I killed the last greek pikeman in the city square with 10 seconds left. Both times I was assaulting a city with 16+ defensive units, mostly pike. Killing them took time.
Age and treachery will defeat youth and skill every time.
I'm not 100% sure, but I think this behavior is tied to the AI's siege weapon ammunition stock. I've had two sieges now where the AI busted down my walls and then just kept on flinging rocks for a while. None of their units were moving, so I decided to wait it out. Then, when the timer was about at the halfway mark, the catapults quit firing and the army started to move.Originally Posted by R'as al Ghul
Back OT, I have played every TW game with the timer on and never had a problem. Sometimes the AI will get stuck in a bunch of rocks or something, and it's the only way to end the battle without losing.
The timer in MTW used to scale to the battle; you'd get like ten minutes to fight off the suicidal attack of the Danish king and his six sons, but you'd have a 3-hour + slugfest when the Mongols appeared in one of your provinces.
Since the advent of RTW, I've found that I never need the full amount of the timer to kick the AI's tail in a field battle (or occasionally lose because my stupid general runs away or gets himself killed) and I've only even come close in a really huge siege.
You can't make an omelette without killing a few people.
- Mr. Croup, Neverwhere
I never used to have battle time limits. I use them in my current campaign because of several battles that annoyed me. I was attacked on a bridge more than once by a large force, when I only had 5 or so very experienced units of infantry. I would have been cut down by the opposing archers if I tried to cross the bridge, and the AI was attacking me...but they just stood there.
They should have attacked me. I attack in 95% of situations, but not that one.
I have yet to actually encounter a battle that expired, so its been a non-issue for me. The closest I got was about half of the time remaining, and I spent a good portion of the first half creating 6-8 holes in walls/heads.
Last edited by Aelwyn; 12-11-2006 at 15:51.
The AI tends to become passive in sieges so playing with time limits is a must for me, even waiting for the the time limit to end gets annoying when you have the AI do nothing and just wait.
I use time limits.
In M2TW I think they are a must because the AI will just stand there when it is the attacker sometimes, and I'm not going to come off my hill or from behind my walls.
The other thing I do which feels like a bit more of an exploit is win battles on the 3 minute city square rule. For example, if the AI has a small garrison but a lot of reinforcements coming I'll make a mad dash for the square and occupy it for 3 minutes before it can get the reinforcements brought up. I've also been known to blow the gate with cannon and run my army right past the guys on the walls to the city square.
As a side note, the city square clock seems a little buggy in M2TW. Sometimes I will get credit for occupying the square while there are still enemies in it.
That's not buggy; it's not the same mechanic as it was in RTW. Back in Rome, you only controlled the square when you had troops in it and there were no enemy in the square at all. Even one enemy trooper in the square and you didn't control it. In this game, it's based on the number of troops on both sides in the square. I'm not sure of the exact number, but generally if you outnumber them by 2-3:1 you'll have control of the square even if their entire remaining garrison is standing there.
Age and treachery will defeat youth and skill every time.
I only use it when enemy forces are besieging my settlement.
Intel Core 2 Duo E8500 @ 3.16GHz
XFX Geforce 9800GTX 512mb
XFX nForce 680i SLI Motherboard
4GB Crucial Ballistix DDR2 RAM
2x Seagate Barracuda 250GB 7200RPM
Windows Vista Ultimate SP1
i never use the timer, i had a few multiple stack fights in mtw where the ai defender won when the time ran out, even tho i was kicking its ass and it still had reinforcements on the way. never turned the timer on again, and even turned off the second rtw and m2tw was installed. Just as i turn off the green arrow markers and use the minimal ui. those are the first changes to the game i make when i (re)install.
I used time limits until the AI sieged a city of mine and didn't budge. I couldn't win if I sallied forth but would easily win if they assaulted. They didn't budge and I ended up exiting the battle which killed all of my troops and lost me the city, even though they wouldn't move.
since then I have used a time limit.
The stakes archers shoot and the stakes pulverize cavalry chrges.
I use the timer on when I'm being attacked, timer off when I am attacking.
My reason is that I sometimes find that the AI does not attack is the timer is not on, which can be somewhat frustrating when they are assaulting a settlement and decide not to move.
"You cannot simultaneously prevent and prepare for war."
-Albert Einstein
"Beer is proof that God loves us and wants us to be happy."
-Benjamin Franklin
Hmm well I guess because I play all cav, I'm always attacking, hence I have very rarely seen the passive AI. In a siege defintely not, I have'nt seen it.
On field I've seen it, when it's completely screwed it just stands there (lol). In a siege, horses are (mostly) useless in the confines of the city and the cruddy garrison militia is (more useful but) useless too, so I sally out and do my thing.
That's only IF I ever get into a (defensive) siege situation. That has happened a total of about 2-3 times out of a total of 165 battles fought in current campaign.
There have been some huge battles, 1500 vs 2500, 700 vs 4000. For these battles I really get nervous with the timer one. It happened to me in MTW that I lost battles pointlessly, because of that timer. I was winning big time but there were too many enemy to kill in allocated time span.
Taught me another lesson too, quicksave at end of each turn.
Last edited by Shahed; 12-11-2006 at 19:21.
If you remember me from M:TW days add me on Steam, do mention your org name.
http://www.steamcommunity.com/id/__shak
the green arrow markers that show you where you're going? also, the mad dash technique to the square has gotten me soooo many regions. what you do is get spies in there to give you an open gate (i usually do it so i have a 100% chance, but you dont need to...you can have whatever you like but sometimes it doesnt open) and then you run in your guys to the square and win it before reinforcements arrive. you dont even need that much more superior of a force.
How can you tell if armies are causing devestation on your land?
I don't think you'd likely have this problem anymore. MTW produced much longer, more epic multistack battles than RTW or M2TW. I can't recall ever coming close to time limiting out while on attack.Originally Posted by Brighdaasa
On the campaign map there is black/grey darkened tiles on the land which has been pillaged.Originally Posted by Test112345
On the settlement details scroll, under the income heading there is a "devastation" outflow.
Last edited by Shahed; 12-11-2006 at 22:36.
If you remember me from M:TW days add me on Steam, do mention your org name.
http://www.steamcommunity.com/id/__shak
I always played with the timer in RTW, but never really relied upon it---battles almost always ended pretty quickly and decisively. I think I ran out of time on a siege once when most of my siege equipment got torched and it took forever to get the troops up a single ladder. In M2TW with the passive AI you have to have the timer or else you end up with nothing happening (or being forced into a suicidal charge in order to get it over with).
I'm getting curious now... does this passive AI happen to people in every single siege battle ?
If you remember me from M:TW days add me on Steam, do mention your org name.
http://www.steamcommunity.com/id/__shak
I use the battle time limit's always have. They help in sieges were the AI just stands there. They also truly put a bit of a worry when attacking a settlement, trying to take it in time can take a bit. They also allow for more even outcomes in large field battles involving a few stacks.
In MTW the timer scaled with the number of troops. I've had one that had a timer near 6 hours. It really used to help with those 30,000+ battles. Quite honestly the battle speed is the single greatest improvement from MTW to M2TW, no longer do you have those 4 hour fights between you and the next biggest kid in europe. Which I might add became pointless after 30 minutesI never used to use time limits in MTW and RTW because as far as I was concerned a lot of battles used to take all day, certainly not 45 minutes max..
Wine is a bit different, as I am sure even kids will like it.
"Hilary Clinton is the devil"BigTex
~Texas proverb
Always use time limit. Tried without for a short time but had 2 or 3 battles where I was defending and greatly outnumbered yet the AI sat there. Only way to end the battle would be to attack the AI (suicide) or end the battle with a loss. At least if the AI attacked me I'd be able to inflict reasonable losses on it before I'd have lost.
Anyway, after those 2 or 3 experiences, I went back to always using the timer.
Magnum
If the AI realizes it doesn't have enought troops to take the city (or just successfully attack you on a normal battle) it will just sit there and do nothing, even if it was the attacker. So time limits are essential to end the battle. I don't mind that either, since the limits are generous enough that I have never been pressed to end a battle because of time.I'm getting curious now... does this passive AI happen to people in every single siege battle ?
I have always used time limit,, rtw, bi and now mtw2
can i play as a faction only if i have DESTROYED them or if i just face them in battle at some point during my campaign?
oh, and does sacking seem to not damage buildings for anyone else either? i sack cities but no buildings get damaged. wierd.
Bookmarks