Warrior Ancient and Medieval Rules

[Greg Regets]

6.164 Impetuous Charges (fourth bullet)

* Any troops tired or uneasy at declaration.

Combat Direction and sequence of movement to contact cannot be used
to remove impetuousness, and as such does not seem to be a valid
strategy to cancel charges.

Thanks ... g

[joncleaves]

In a message dated 5/7/2004 9:22:09 AM Eastern Daylight Time,
greg.regets@... writes:

> 6.164 Impetuous Charges (fourth bullet)
>
> * Any troops tired or uneasy at declaration.
>
> Combat Direction and sequence of movement to contact cannot be used
> to remove impetuousness, and as such does not seem to be a
> valid
> strategy to cancel charges.
>
> Thanks ... g>>

I don't know what this is in reponse to, Greg, but since I posted yesterday on
using unease to cancel charges, I'll clarify what I siad in case I cuased
confusion.

If a willing LMI unit has an El within 240 at declaration, it is not charging
impetuously.

If an elephant moves to within 240p during charge moves, the declaration has
already occurred and what you said above is dead on.

J

[Ewan McNay]

JonCleaves@... wrote:

> In a message dated 5/7/2004 9:22:09 AM Eastern Daylight Time,
> greg.regets@... writes:
>
>
>> 6.164 Impetuous Charges (fourth bullet)
>>
>> * Any troops tired or uneasy at declaration.
>>
>> Combat Direction and sequence of movement to contact cannot
>> be used to remove impetuousness, and as such does not seem
>> to be a valid strategy to cancel charges.
>>
>> Thanks ... g>>
>
> I don't know what this is in reponse to, Greg, but since I
> posted yesterday on using unease to cancel charges, I'll
> clarify what I siad in case I cuased confusion.

Naah, 'twas I (I think). I commented that combat direction
might be able to cause unease during the charge movement phase
(which was in error; thanks, Greg).

[joncleaves]

In a message dated 5/7/2004 9:42:51 AM Eastern Daylight Time,
ewan.mcnay@... writes:

> Naah, 'twas I (I think). I commented that combat direction
> might be able to cause unease during the charge movement
> phase
> (which was in error; thanks, Greg).>>

It can impact actually. If you had a charger earlier in the combat direction
get behind your flank it might make you uneasy for a waver test in a later
combat....

But Greg is correct that all declarations are before all movement, etc.

J

[Greg Regets]

I watched a game not long ago take a massive swing, just on this
single rule.

A guy charged something at a loss thinking it would make him behind
the flank of two adjacent enemy units (which it did) ... thus making
them uneasy (which it did) ... thus killing their impetuous status
(which it doesn't) ... thus cancelling the charges (which
weren't) ... thus testing waver when he charged with his elephants
who were already cancelling one cause of eagerness, etc ...

The two impetuous chargers both got breaks on the elephants. The guy
with the elephants went from having the enemy at his feet, to being
knocked off his feet.

A very good, very simple, and very important rule.

Thanks ... g



--- In WarriorRules@yahoogroups.com, JonCleaves@a... wrote:
> In a message dated 5/7/2004 9:42:51 AM Eastern Daylight Time,
ewan.mcnay@y... writes:
>
> > Naah, 'twas I (I think). I commented that combat direction
> > might be able to cause unease during the charge movement
> > phase
> > (which was in error; thanks, Greg).>>
>
> It can impact actually. If you had a charger earlier in the combat
direction get behind your flank it might make you uneasy for a waver
test in a later combat....
>
> But Greg is correct that all declarations are before all movement,
etc.
>
> J