has the mountain problem been addressed before?

[neoiq5719]

Is it a problem of programming, is it a bug or what? has this been also addressed or not? it happened to me once before and i tried to ignore it but lately it happens a lot when u try to get a battle up on a mountain. Either your troops are not able to get down ( if u r at the top) OR your troops are not able to move up ( if you are at the bottom) so the final solution is to exit the battle with the consecuent loss of it . Is this marvellous upcoming patch gonna fix this?

[HRE_HeinrichV]

that happened to me once. the enemy were so high up, i couldnt get to them.

[HoreTore]

It's simply bad maps.

A very, very good reason why you should have the timer ON...

[TevashSzat]

Always always have it on, there are simply too many situations where u need it for it to be turned off. Besides, you rarely run out of time except for sieges where u should be using auto calc already

[neoiq5719]

i know but i hate having the timer on. Using the timer sounds like " hey i gotta take over that country by 5 pm or else". I battle takes whatever it takes and period. NO WATCHES FOR THAT.

[HoreTore]

I see it rather differently... I really like the timer. In those rare cases where it reaches the bottom, it forces me to make rash decisions to win the battle, which I really like. Like being forced to make a head-on rush at the last gate of a citadel instead of marching my infantry over the linked walls too shoot at the town center.

[Afro Thunder]

Did you know that you can turn on/turn off the timer while you're on the campaign map?

[Mr Frost]

Did you know that you can turn on/turn off the timer while you're on the campaign map?
Exactly .
A quicksave {or what in the Neverwinter Nights games I call a Save Verses Bull S#!t} before a battle and you can simply reload when a bug rears its' ugly head .

[Afro Thunder]

Except you should only do that when your game gets bugged, not when you lose a battle or something.