View Full Version : Question on multi-leader routing
sansanjuan
February 26th, 2008, 02:58 PM
Wasn’t sure of all the nuances of leaderless routing after reading the manual. I understand a battle with single leader who is killed will cause all his/her troops to rout.
Case 1: What if an “empty” commander is also included? Will the dead commander’s troops seamlessly attach to the new commander?
Case 2: If commander “A” is killed and has a mix of 20x undead, 20x magic and 20x regular troops but the secondary commander can only handle 10x magic how would the troops reattach?
If these have been answered please point me to the thread as my search has been fruitless..
-SSJ
thejeff
February 26th, 2008, 03:38 PM
As near as I can tell, routing does not depend at all on the particular commander the squad was initially assigned to.
As long as there is a commander on the field with the appropriate type of leadership (regular/undead/magic) those units will not autorout.
You'll have to reorganize after battle if you lose commanders, but that's to be expected.
TwoBits
February 26th, 2008, 04:08 PM
You can get a merc commander killed, yet still employ his/her troops in the same battle, too (they're gone afterwards though) - that's a good way to try to bogart any magic items they might have, if they've come to outlive their usefulness...
sansanjuan
February 26th, 2008, 04:14 PM
Thanks for the replies.
"Bogart" ... that phrase made me smile. I've heard it before but wonder on the origin. Was Humphrey known for "Bogarting"?
-SSJ
Saulot
February 27th, 2008, 01:57 AM
Yes, it refers to him keeping a cigarette in his mouth without actually smoking it. (So more of keeping something to yourself / Not sharing, as opposed to actually stealing something)
TwoBits
February 27th, 2008, 01:16 PM
I believe I first heard that term used on an episode of Beavis and Butthead (where I acquired most of my vocabulary http://forum.shrapnelgames.com/images/smilies/wink.gif).
Dang, that really dates me, doesn't it?
According to Saulot's definition, it also seems I may have used it inappropriately...
vBulletin® v3.8.1, Copyright ©2000-2025, Jelsoft Enterprises Ltd.