|
|
|
 |

March 14th, 2004, 07:33 PM
|
 |
Lieutenant Colonel
|
|
Join Date: Jan 2004
Posts: 1,276
Thanks: 0
Thanked 2 Times in 2 Posts
|
|
Re: Fire when guard commander
Righto. But OTOH: Two armies set to "fire" will have the exact same effect as well (same as set to guard commander and firing while doing so). I fail to see the net loss / problem with firing while guarding a commander.
|

March 14th, 2004, 07:39 PM
|
 |
General
|
|
Join Date: Nov 2000
Posts: 3,013
Thanks: 17
Thanked 25 Times in 22 Posts
|
|
Re: Fire when guard commander
Quote:
Originally posted by tinkthank:
Righto. But OTOH: Two armies set to "fire" will have the exact same effect as well (same as set to guard commander and firing while doing so). I fail to see the net loss / problem with firing while guarding a commander.
|
Two armies set to fire will have their missile troops close to melee range after their ammunition runs out.
|

March 14th, 2004, 08:31 PM
|
 |
Major General
|
|
Join Date: Jan 2004
Location: twilight zone
Posts: 2,247
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Re: Fire when guard commander
Quote:
Originally posted by Graeme Dice:
Two armies set to fire will have their missile troops close to melee range after their ammunition runs out.
|
Which is why we need a new "Fire and Hold" command for missile troops (rather than just the current Fire & Attack), along with Fire while Guarding.
|

March 14th, 2004, 09:52 PM
|
Sergeant
|
|
Join Date: Feb 2004
Posts: 365
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Re: Fire when guard commander
Quote:
Originally posted by Arryn:
quote: Originally posted by Graeme Dice:
Two armies set to fire will have their missile troops close to melee range after their ammunition runs out.
|
Which is why we need a new "Fire and Hold" command for missile troops (rather than just the current Fire & Attack), along with Fire while Guarding. But then you could end up with two armies holding indefinitely at opposite ends of the battle screen. Which I guess wouldn't be so bad since auto-rout eventually kicks in.
|

March 14th, 2004, 10:04 PM
|
Corporal
|
|
Join Date: Feb 2004
Posts: 96
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Re: Fire when guard commander
Quote:
Originally posted by Yossar:
But then you could end up with two armies holding indefinitely at opposite ends of the battle screen. Which I guess wouldn't be so bad since auto-rout eventually kicks in.
|
Exactly. There's already a method for handling combats which take too long/are stalemated. No need to take away perfectly viable gameplay mechanics such as having Daoine Sidhe guarding your commander and throwing their javelins when something comes in range.
|

March 15th, 2004, 10:02 AM
|
 |
Captain
|
|
Join Date: Feb 2004
Location: within 200km of Ulm
Posts: 919
Thanks: 27
Thanked 0 Times in 0 Posts
|
|
Re: Fire when guard commander
Yeah, I do not see the problem either: I think its the Defender's right to sit and wait for the enemy to attack! And if the enemy does not attack, because he only got his guarding missile troops, then the defender should win after some, say 22, turns...
So discouraging cowardly attackers does not sound bad to me!
|

March 15th, 2004, 11:07 AM
|
Sergeant
|
|
Join Date: Feb 2004
Posts: 365
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Re: Fire when guard commander
Quote:
Originally posted by Chazar:
Yeah, I do not see the problem either: I think its the Defender's right to sit and wait for the enemy to attack! And if the enemy does not attack, because he only got his guarding missile troops, then the defender should win after some, say 22, turns...
|
I believe attacker's troops rout at 50 turns, defenders at 60, and everyone left (immobiles, berzerkers, paralyzed troops) dies at 70. Could be a bit off.
|
Thread Tools |
|
Display Modes |
Hybrid Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is On
|
|
|
|
|