Difference between revisions of "Counter Attack"
m |
|||
| Line 6: | Line 6: | ||
- Counter attack does count for the [[fatigue]] parameter: If you manage to force a stack to counter attack a lot, before it can attack itself, by the time it strikes itself, its blow is far less powerfull than it would have been. This is a way to beat e.g. a single-stack-army of a low-init ground unit ('mono treants') by having am army high number of high-init ranged units. | - Counter attack does count for the [[fatigue]] parameter: If you manage to force a stack to counter attack a lot, before it can attack itself, by the time it strikes itself, its blow is far less powerfull than it would have been. This is a way to beat e.g. a single-stack-army of a low-init ground unit ('mono treants') by having am army high number of high-init ranged units. | ||
| + | [[Category:Battle Factors]] | ||
Revision as of 04:41, 17 April 2008
When a stack is hit in the battle, units that have Counter attack can strike back and deal damage to the attacker.
- Counter attack is only triggered by a Primary Attack of an enemy stack (i.e. the Extra Attack does not trigger Counter attack). - Counter attacks have no effect against Ranged Units. ('To distant - could not strike back' line in battle report) - The damage from a counter attack is usually smaller than that unit's primary and extra attack.
- Counter attack does count for the fatigue parameter: If you manage to force a stack to counter attack a lot, before it can attack itself, by the time it strikes itself, its blow is far less powerfull than it would have been. This is a way to beat e.g. a single-stack-army of a low-init ground unit ('mono treants') by having am army high number of high-init ranged units.
