From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <xconq7-return-3698-listarch-xconq7=sources.redhat.com@sources.redhat.com>
Received: (qmail 27411 invoked by alias); 12 Jul 2004 01:25:03 -0000
Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:xconq7-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/xconq7/>
List-Post: <mailto:xconq7@sources.redhat.com>
List-Help: <mailto:xconq7-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: xconq7-owner@sources.redhat.com
Received: (qmail 27403 invoked from network); 12 Jul 2004 01:25:02 -0000
Received: from unknown (HELO av7-2-sn2.hy.skanova.net) (81.228.8.109)
  by sourceware.org with SMTP; 12 Jul 2004 01:25:02 -0000
Received: by av7-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id 78B5D37E43; Mon, 12 Jul 2004 03:25:02 +0200 (CEST)
Received: from smtp2-2-sn2.hy.skanova.net (smtp2-2-sn2.hy.skanova.net [81.228.8.178])
	by av7-2-sn2.hy.skanova.net (Postfix) with ESMTP
	id 67A3237E42; Mon, 12 Jul 2004 03:25:02 +0200 (CEST)
Received: from [212.181.162.155] (h155n1fls24o1048.bredband.comhem.se [212.181.162.155])
	by smtp2-2-sn2.hy.skanova.net (Postfix) with ESMTP id D9DF937E42;
	Mon, 12 Jul 2004 03:25:01 +0200 (CEST)
X-Sender: u22611592@m1.226.comhem.se
Message-Id: <l03130301bd1797648610@[212.181.162.155]>
In-Reply-To: <2241.68.122.234.217.1089581065.squirrel@webmail.io.com>
References: <1713.68.126.82.218.1089405036.squirrel@webmail.io.com>
 <40EEAD66.50109@phy.cmich.edu>        
 <200407040055.i640tDx17333@panix5.panix.com><1088896371.19592.ezmlm@source
 s.redhat.com>               
 <2465.68.126.82.218.1088896685.squirrel@webmail.io.com>               
 <200407040055.i640tDx17333@panix5.panix.com>             
 <l03130300bd0daacd36d4@[212.181.162.155]>             
 <200407041512.i64FCx018057@panix5.panix.com>          
 <32786.68.122.234.217.1089262126.squirrel@webmail.io.com>          
 <40EDFCDE.9000902@phy.cmich.edu>       
 <3302.68.126.82.218.1089339533.squirrel@webmail.io.com>       
 <40EEAD66.50109@phy.cmich.edu>     
 <l03130304bd146ceb76be@[212.181.162.155]>   
 <1713.68.126.82.218.1089405036.squirrel@webmail.io.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 12 Jul 2004 03:27:00 -0000
To: "Henry J. Cobb" <hcobb@io.com>
From: Hans Ronne <hronne@comhem.se>
Subject: Re: Carrier groups
Cc: xconq7@sources.redhat.com
X-SW-Source: 2004/txt/msg00713.txt.bz2

>So a carrier strike group would be defined as a group of units centered on
>a carrier.  (With a full load of fighters and a battleship.)
>
>The entire group moves with the carrier and withdraws with it when the
>carrier is low on fuel, ammo or aircraft.

What you are suggesting is in effect the possibility of having side
doctrines for setting formations. This would certainly be possible.
However, the AI doesn't know how to use formations, so one would first have
to write some new AI code.

Hans