Quote:
Arker said:
Like I said, learn to read. I didn't say the former, and the unexplained behaviour was explained long ago. It's still stupid but it's not unexplained.
|
Are you trying to pretend that you never wrote:
"I don't see how you could say that with a straight face, knowing that there are several final orders that can be given, yet as discussed in this thread the AI always uses 'stay behind troops' even when it's not the order given?"
Quote:
And your explanations, as I've said already, match my observations. Perhaps you should do some re-reading, or chug a pot of coffee, or something?
|
Perhaps you should make up your mind whether you agree with us, or whether you actually agree with your statement that I've quoted above.
Quote:
The heroic quickness glitch explains the one instance I observed where the commander, with final order 'cast spells,' moved behind the rearmost troops and *then* cast BoW. Without it, he would cast, then move.
|
Then he either had absolutely no spells to cast that would reach any enemy targets (as was already explained to you), or you are mistaken, and you left him on stay behind troops or with no final order.
Quote:
Why on earth you're on about me needing to provide a replay to show behaviour you already explained I don't know.
|
I want a replay because you are claiming behaviour that does not happen in the actual game.
Quote:
The AI suffers from a chronic need to 'do something' every turn, and if there's nothing useful for it to do it will cast useless or harmful spells, and when it can't even do that it will 'stay behind troops' - exactly as you've explained, exactly as I've observed many times, exactly as anyone that's played this game very much will have seen.
|
Why don't you make up your bloody mind whether you think that it's a bug or not when your mages move in various situations. The previous paragraph has you complaining that it's a bug when your mages change to stay behind troops for a turn. Now you're trying to tell me that it's not a bug.