Swiftstride When charging, units entirely made of models with Swiftstride and M 7 or higher roll 3D6, discard the lowest result, and add the result to their M value. When fleeing or pursuing, they roll 3D6, rather than 2D6.
When charging, units entirely made of models with Swiftstride and M 6 or lower roll 2D6, and add the result to their M value. Whenfleeing or pursuing, they roll 3D6, and discard the lowest result.
Swiftstride has no effect on models using a M value lower than 4.
Swiftstride M6 or lower
Charging: M + 2D6
Failed Charge: 2D6
Fleeing/Pursuing: 3D6 (discard the lowest)
Swiftstride M7 or more
Charging: M + 3D6 (discard the lowest)
Failed Charge: 3D6 (discard the lowest)
Fleeing/Pursuing: 3D6
Mixed Unit A Mixed Unit most often consist of two different Troop Types, with one or more handlers that drive the rest of the unit forward. The handler(s) may be deployed in the rear rank of the unit. Mixed Units cannot be joined by characters, unless specified.
If a Mixed unit is required to take a characteristic test, this is done using the characteristics of the unit itself, not the handlers. The only exception is LD tests, which are taken using the unit’s highest LD value. When the models in a unit with Mixed Unit have different M allowances, the handlers M value is ignored, unless they are the only models remaining. Any rules that the unit might have do not apply to the Handlers unless specified – ignore the handlers completely in those cases.
As long as the unit (but not the handlers) have a unit strength of 5 or more, any missile hits are resolved against the unit itself. At less than unit strength 5, the controlling player decides who is hit, but must allocate one hit on each model before they can add a second hit on a model; they must allocate two hits on each model before they can allocate a third, and so on. Hits from templates are resolved against the handlers as normal. In close combat, the handlers can only be attacked by models who are in base contact with them.
