Kitsune

All attacks made by spells and magic items are considered to be magical attacks, as are all attacks that are specifically noted as being magical attacks. Shots fired from magical items are also considered to be magical attacks, unless their description specifically states otherwise. Hits inflicted by rolls on the Miscast table are treated as magical attacks.

Note that spells are not physical attacks unless clearly specified.

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

The value of a ward save will always be shown in a model's entry. These work in the same way as armour saves, and may be combined with other Ward saves as normal. The key difference between ward saves and armour saves is that ward saves are never modified by the S of the attack. However, no model may have a Ward save better than 4+ by combining multiple Ward saves regardless of source; single Ward saves with a better value than 4+ are always specified as such.

Sometimes a model has both an armour save and a Ward save. Where this is the case, the model takes its armour save as normal. If the armour save is failed (or modified to the point at which the model cannot pass it) then the model takes its Ward save.

Models with Strider will normally have a subset of Strider that is mentioned in the brackets. The rule only applies in terrain of the specified type. Models with Strider treat that piece of terrain as open ground for the purposes of Movement, meaning they ignore any M penalties or Dangerous Terrain tests otherwise caused by it. Note that they still follow the rules for that terrain type in terms of combat.

Before starting deployment, a unit with Scouts can choose to not deploy at the start of the battle. Scouts are set up after all other non-Scout units from both armies have been deployed, and do not count toward determining who finished deploying their army first. They can be set up either in their controlling player's deployment zone as normal, or anywhere on the battlefield more than 12" away from the enemy. If deployed in this second way, Scouts cannot declare a charge in the first turn if their side goes first.

Note that a character may only join a unit deploying with Scouts if they also have the same rule.

If both players' armies contain Scouts, players should roll off. The players then alternate deploying their scouting units one at a time, starting with the player who won the roll-off.