public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: xconq-developers@lists.sourceforge.net,
	 xconq7 <xconq7@sources.redhat.com>
Subject: Re: New Feature: Overwatch
Date: Sat, 01 Jan 2005 21:38:00 -0000	[thread overview]
Message-ID: <41D71826.4060506@phy.cmich.edu> (raw)
In-Reply-To: <1104613760.402.175.camel@localhost.localdomain>

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

  reply	other threads:[~2005-01-01 21:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-01  6:59 Eric McDonald
2005-01-01  7:19 ` Lincoln Peters
2005-01-01 16:31   ` Eric McDonald
2005-01-01 21:09     ` Lincoln Peters
2005-01-01 21:38       ` Eric McDonald [this message]
2005-01-02  2:43         ` Bug reports, feature requests, and dilemmas [was: Re: New Feature: Overwatch] Lincoln Peters
2005-01-04 17:24           ` GIS and navigable rivers mskala
2005-01-04 21:27             ` Lincoln Peters

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41D71826.4060506@phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=sampln@sbcglobal.net \
    --cc=xconq-developers@lists.sourceforge.net \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).