SG2 Campaign System Revision

I've changed/cleaned up my campaign system a bit.  We started a game
last night.  We only played up to the first conflict, platoon
vs. platoon.  My side got chewed up, and everybody seemed to like it.
Check it out:

http://www.cowell.org/~andy/min/sg2/sg2cam.pdf

Some things that aren't in there or need to be clarifed:
* Wpn Platoon: May move, support another battle this turn and move, or
  support two battles this turn.  May not support a battle after it is
  activated.
* Wounded evac and return to duty

I'd appreciate anybody looking it over and giving their comments.
From - Wed Jan 03 11:06:13 2001
Return-Path: <owner-gzg-l@scotch.csua.berkeley.edu>
Received: from scotch.csua.berkeley.edu (scotch.CSUA.Berkeley.EDU
[128.32.43.51])
	by lilac.propagation.net (8.8.5/8.8.5) with ESMTP id MAA28731;
	Sun, 31 Dec 2000 12:00:07 -0600
Received: from localhost (daemon@localhost)
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) with SMTP id
eBVHw5b12650;
	Sun, 31 Dec 2000 09:58:05 -0800 (PST)
Received: by scotch.csua.berkeley.edu (bulk_mailer v1.12); Sun, 31 Dec
2000 09:58:04 -0800
Received: (from majordom@localhost)
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) id eBVHw3M12629
	for gzg-l-outgoing; Sun, 31 Dec 2000 09:58:03 -0800 (PST)
Received: from soda.csua.berkeley.edu
(IDENT:V1t4WEOBpOAvLhQwO27s/TDUAS3odEwz@soda.CSUA.Berkeley.EDU
[128.32.43.52])
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) with ESMTP id
eBVHw2Z12624
	for <gzg-l@lists.CSUA.Berkeley.EDU>; Sun, 31 Dec 2000 09:58:02
-0800 (PST)
Received: from okura.cowell.org (IDENT:root@okura.toysmakeuspowerful.com
[12.13.79.17])
	by soda.csua.berkeley.edu (8.11.0/8.11.1) with ESMTP id
eBVHw1p89422
	for <gzg-l@csua.berkeley.edu>; Sun, 31 Dec 2000 09:58:01 -0800
(PST)
	(envelope-from andy@cowell.org)
Received: from cowell.org (IDENT:andy@localhost [127.0.0.1])
	by okura.cowell.org (8.9.3/8.9.3) with ESMTP id MAA02199
	for <gzg-l@csua.berkeley.edu>; Sun, 31 Dec 2000 12:58:07 -0500
Message-Id: <200012311758.MAA02199@okura.cowell.org>
To: gzg-l@csua.berkeley.edu
Subject: Re: SG2 Campaign System Revision 
In-Reply-To: Your message of "Sun, 31 Dec 2000 11:52:29 CST."
	     <200012311752.MAA02062@okura.cowell.org> 
Date: Sun, 31 Dec 2000 11:58:07 -0600
From: Andy Cowell <andy@cowell.org>
Sender: owner-gzg-l@lists.CSUA.Berkeley.EDU
Reply-To: gzg-l@csua.berkeley.edu
Delivered-To: gzg-l@csua.berkeley.edu
Status:   
X-Mozilla-Status: 0000
X-Mozilla-Status2: 00000000
X-UIDL: 39d245de00000aef

In message <200012311752.MAA02062@okura.cowell.org>, Andy Cowell writes:
> 
> http://www.cowell.org/~andy/min/sg2/sg2cam.pdf
:
> I'd appreciate anybody looking it over and giving their comments.

Oh, one other thing.  I'd especially appreciate comments on the
scenario creation system.  It seems fun, but it needs some work.
Right now, the defender would almost always pick "Hold Location" (it
seems to me).  Plus, I'd like to have other options as well.  Let me
know what you think.
From - Wed Jan 03 11:06:13 2001
Return-Path: <owner-gzg-l@scotch.csua.berkeley.edu>
Received: from scotch.csua.berkeley.edu (scotch.CSUA.Berkeley.EDU
[128.32.43.51])
	by lilac.propagation.net (8.8.5/8.8.5) with ESMTP id PAA15170;
	Sun, 31 Dec 2000 15:57:55 -0600
Received: from localhost (daemon@localhost)
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) with SMTP id
eBVLwEj15460;
	Sun, 31 Dec 2000 13:58:14 -0800 (PST)
Received: by scotch.csua.berkeley.edu (bulk_mailer v1.12); Sun, 31 Dec
2000 13:58:07 -0800
Received: (from majordom@localhost)
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) id eBVLw6b15439
	for gzg-l-outgoing; Sun, 31 Dec 2000 13:58:06 -0800 (PST)
Received: from soda.csua.berkeley.edu (soda.CSUA.Berkeley.EDU
[128.32.43.52])
	by scotch.csua.berkeley.edu (8.11.0/8.11.0) with ESMTP id
eBVLw5Z15434
	for <gzg-l@lists.CSUA.Berkeley.EDU>; Sun, 31 Dec 2000 13:58:05
-0800 (PST)
Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net
[209.226.175.25])
	by soda.csua.berkeley.edu (8.11.0/8.11.1) with ESMTP id
eBVLvxp07136
	for <gzg-l@csua.berkeley.edu>; Sun, 31 Dec 2000 13:57:59 -0800
(PST)
	(envelope-from awg@sympatico.ca)
Received: from Toronto-ppp220719.sympatico.ca ([64.228.103.44])
	  by tomts5-srv.bellnexxia.net
	  (InterMail vM.4.01.03.00 201-229-121) with SMTP
	  id
<20001231215752.HZGQ14993.tomts5-srv.bellnexxia.net@Toronto-ppp220719.sy
mpatico.ca>
	  for <gzg-l@csua.berkeley.edu>; Sun, 31 Dec 2000 16:57:52 -0500
From: Allan Goodall <awg@sympatico.ca>
To: gzg-l@csua.berkeley.edu
Subject: Re: SG2 Campaign System Revision 
Date: Sun, 31 Dec 2000 16:55:51 -0500
Organization: Haphazard at best.
Message-ID: <of3v4tk30cshdm95m10l1g08ng5n7gbd6j@4ax.com>
References: <200012311752.MAA02062@okura.cowell.org>
<200012311758.MAA02199@okura.cowell.org>
In-Reply-To: <200012311758.MAA02199@okura.cowell.org>
X-Mailer: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by
scotch.csua.berkeley.edu
 id eBVLw5Z15435
Sender: owner-gzg-l@lists.CSUA.Berkeley.EDU
Reply-To: gzg-l@csua.berkeley.edu
Delivered-To: gzg-l@csua.berkeley.edu
Status:   
X-Mozilla-Status: 0000
X-Mozilla-Status2: 00000000
X-UIDL: 39d245de00000af0

On Sun, 31 Dec 2000 11:58:07 -0600, Andy Cowell <andy@cowell.org> wrote:

>Oh, one other thing.  I'd especially appreciate comments on the
>scenario creation system.  It seems fun, but it needs some work.
>Right now, the defender would almost always pick "Hold Location" (it
>seems to me).	Plus, I'd like to have other options as well.  Let me
>know what you think.

Hi, Andy.

I've looked it over quickly. It doesn't look too bad!

I'm not sure you need a "fight" option. I think that you basically need
to
have only "stay" and "retreat". When there are units in a hex, they will
either stay or leave. Here's what would happen:

1) Both units enter the hex, both choose "stay": you have a meeting
engagement.
2) One unit is in the hex, one unit enters the hex, and both choose
"stay":
you have an assault on a defended position.
3) Both units enter the hex, one chooses "stay" and one chooses
"retreat": the
retreating unit gives up the hex, and the other unit takes the hex
unopposed.
4) One unit is in the hex, one unit enters the hex. The unit in the hex
picks
"stay", the unit entering the hex chooses "retreat": the unit already in
the
hex retains the hex unopposed.
5) One unit is in the hex, one unit enters the hex. The unit in the hex
picks
"retreat", the unit entering the hex chooses "stay": you have a
rearguard/retreat scenario.
6)  One unit is in the hex, one unit enters the hex. Both units choose
"retreat": the unit already in the hex withdraws, the unit moving into
the hex
falls back. The hex is empty.

You might want to play with which unit chooses their option first:
simultaneous, defender first, or attacker first.

With what I've outlined the actual players have to decide their
objectives.
The players will have to decide if the hex is worth fighting over,
whether or
not it's worth taking the location, or if the destruction of enemy
forces
should be a priority.

Anyway, just some thoughts...

Have you thought of some method of doing hidden movement and hidden
units at a
campaign level? If so, capturing prisoners becomes a viable objective
(in
actual combat, that IS a viable mission).

Wish I had a group of SG2 players that played regularly. This has me
thinking
about campaign possibilities!

Allan Goodall		       awg@sympatico.ca
Goodall's Grotto:  http://www.vex.net/~agoodall

"Surprisingly, when you throw two naked women with sex
toys into a living room full of drunken men, things 
always go bad." - Kyle Baker, "You Are Here"