Warrior Ancient and Medieval Rules

[Doug]

>>>
Oh, if it was in the case of seeing a router before the converted
charge makes contact, then hell yes, there is a waver...

In that game the router broke after the converted charge occured in a combat
coming before the break in the combat direction.
Jon
>>>

Huh? I cannot parse that last sentence to figure out the sequence of events.

combat #1 involved a converted charge.
combat #1 resulted in a rout
combat #2 is to be resolved after combat #1 per rules on Combat direction.
combat #2 prior to resolving its combat, a waver test is required due
to seeing the rout of #1.

?????

[joncleaves]

Huh? I cannot parse that last sentence to figure out the sequence of events.

combat #1 involved a converted charge.
combat #1 resulted in a rout
combat #2 is to be resolved after combat #1 per rules on Combat direction.
combat #2 prior to resolving its combat, a waver test is required due
to seeing the rout of #1.

?????>>

No, that is not what happened. In combat 1, a unit broke. The pursuer made
contact with another enemy unit (an SHK): converted charge.
Now in combat 2, a unit, friendly to the SHK, is broken and routs near the SHK.
No waver for the SHK as it is involved in a converted charge, which prevents all
waver tests by any body involved until the converted charge combat is resolved
next bound.

Jon

[Mark Mallard]

In a message dated 10/14/2004 3:41:21 AM GMT Daylight Time,
rockd@... writes:

In that game the router broke after the converted charge occured in a combat
coming before the break in the combat direction.
Jon



Ok i can see the logic here i think, but still the waver test rules need
amending so we know when these units test if ever for said router/destroyed unit
etc.

mark mallard


[Non-text portions of this message have been removed]