Warrior Ancient and Medieval Rules

[Greg Regets]

While playing a Warrior game last night, I had the opportunity to
witness the loss of the C-in-C, with his standard, and his unit.

While having seen this quite a number of times in the past (both mine
and others), this event struck me as particularly interesting.

What struck me is the last few meetings I had with my boss at work
and how I felt when I left those meeting ... then using these real
world examples to relate to Warrior.

This thinking pointed out a FATAL flaw in Warrior ... one that Jon
just MUST fix ASAP!!!!

I mean ... why take all those damn waver tests when the troops see
the boss go? What if the boss is a jerk?

**********

So, while playing last night, we came up with a few alternatives to
cover the "boss is a jerk" scenario, as outlined in rules section
5.52 of the Warrior rulebook.

5.521. Upon seeing the C-in-C rout, all friendly missile units within
range, immediately turn and fire into the routed unit ... JUST TO
MAKE SURE!

5.522. Upon seeing the C-in-C rout, all friendly units get to
immediately loot the friendly baggage. This simulates what happens
when the boss gets canned, and the feeding frenzy takes place to
steal his chair and flat screen monitor.

5.523. Upon seeing the C-in-C rout, all friendly units quickly move
to the general's original deployment position ... because who
wouldn't wan't their bosses old parking spot?

5.524. Upon seeing the C-in-C rout, each friendly unit gets to take
all fatigue they have accumulated, and transfer it to the C-in-C. Do
I really need to further explain this one?

5.525. Upon seeing the C-in-C rout, all friendly bodies should
immediately report to the 2-in-C, in order to communicate the
tactical message that in their opinion, he should have been the C-in-
C all along.

Please feel free to make any other additional suggestions you might
have.

Roll Down and Lose (the C-in-C)

Greg

[joncleaves]

Please feel free to make any other additional suggestions you might
have.>>

Have a beer and chill, dude...lol

Jon

Greg, that's the funniest thing I've read in a long time.

Thanks

Allan
----- Original Message -----
From: "Greg Regets" <greg.regets@...>
To: <WarriorRules@yahoogroups.com>
Sent: Tuesday, October 19, 2004 3:57 PM
Subject: [WarriorRules] C-in-C: The Rules Need Fixed!


>
>
> While playing a Warrior game last night, I had the opportunity to
> witness the loss of the C-in-C, with his standard, and his unit.
>
> While having seen this quite a number of times in the past (both mine
> and others), this event struck me as particularly interesting.
>
> What struck me is the last few meetings I had with my boss at work
> and how I felt when I left those meeting ... then using these real
> world examples to relate to Warrior.
>
> This thinking pointed out a FATAL flaw in Warrior ... one that Jon
> just MUST fix ASAP!!!!
>
> I mean ... why take all those damn waver tests when the troops see
> the boss go? What if the boss is a jerk?
>
> **********
>
> So, while playing last night, we came up with a few alternatives to
> cover the "boss is a jerk" scenario, as outlined in rules section
> 5.52 of the Warrior rulebook.
>
> 5.521. Upon seeing the C-in-C rout, all friendly missile units within
> range, immediately turn and fire into the routed unit ... JUST TO
> MAKE SURE!
>
> 5.522. Upon seeing the C-in-C rout, all friendly units get to
> immediately loot the friendly baggage. This simulates what happens
> when the boss gets canned, and the feeding frenzy takes place to
> steal his chair and flat screen monitor.
>
> 5.523. Upon seeing the C-in-C rout, all friendly units quickly move
> to the general's original deployment position ... because who
> wouldn't wan't their bosses old parking spot?
>
> 5.524. Upon seeing the C-in-C rout, each friendly unit gets to take
> all fatigue they have accumulated, and transfer it to the C-in-C. Do
> I really need to further explain this one?
>
> 5.525. Upon seeing the C-in-C rout, all friendly bodies should
> immediately report to the 2-in-C, in order to communicate the
> tactical message that in their opinion, he should have been the C-in-
> C all along.
>
> Please feel free to make any other additional suggestions you might
> have.
>
> Roll Down and Lose (the C-in-C)
>
> Greg
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>

In a message dated 19/10/2004 20:59:27 GMT Daylight Time,
greg.regets@... writes:

Please feel free to make any other additional suggestions you might
have.



A Cautious Sub-General adopts a Wait (and see) order just in case the new
Boss turns out to be an even bigger jerk :)


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