From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16993 invoked by alias); 1 Jan 2005 21:38:08 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 16975 invoked from network); 1 Jan 2005 21:38:03 -0000 Received: from unknown (HELO rwcrmhc13.comcast.net) (204.127.198.39) by sourceware.org with SMTP; 1 Jan 2005 21:38:03 -0000 Received: from [192.168.181.128] (c-67-176-41-158.client.comcast.net[67.176.41.158]) by comcast.net (rwcrmhc13) with ESMTP id <2005010121380201500c41ose>; Sat, 1 Jan 2005 21:38:02 +0000 Message-ID: <41D71826.4060506@phy.cmich.edu> Date: Sat, 01 Jan 2005 21:38:00 -0000 From: Eric McDonald User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) MIME-Version: 1.0 To: Lincoln Peters CC: xconq-developers@lists.sourceforge.net, xconq7 Subject: Re: New Feature: Overwatch References: <41D64A45.4030403@phy.cmich.edu> <1104563991.402.156.camel@localhost.localdomain> <41D6D054.6030006@phy.cmich.edu> <1104613760.402.175.camel@localhost.localdomain> In-Reply-To: <1104613760.402.175.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005/txt/msg00004.txt.bz2 Lincoln Peters wrote: > I suppose I should also copy the various unfulfilled feature requests > I've made on this list to the Sourceforge page, so that they'll be > easier to keep track of. Yes. That would be of much help. > Now it makes sense. Although it sounds like in one of the BoloDD games, > a tank could move to within 4 cells of a tower, start firing on it, and > only be automatically attacked once. Correct, __until the tank moves again. I think you may be looking for another feature that Elijah requested about the same time as overwatch, namely "counterfire". I have not attempted to implement this, but I envision it being the firing analog to "counterattack". Of course, things need to be set up so that an attack can be responded to by counterfire, and vice versa. In the case where both counterattack and counterfire are available, then probably a 'preferred-hit-method' table will be needed to decide between them. Such a table would also be useful for disambiguating the two options in the case of an overrun action, when both are available. Eric