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

On Fri, 2004-12-31 at 23:59 -0700, Eric McDonald wrote:
>    The new feature is overwatch. An unit can now have a 
> zone-of-overwatch (ZOO) that it maintains against other units of various 
> types. The principle is very similar to ZOC (zone-of-control), except 
> that ZOO's are inherently penetrable, whereas ZOC's are normally "hard". 
> An unit entering into a ZOO of enemy unit will be immediately and 
> automatically fired upon, provided the enemy unit has the necessary ACP 
> and/or materials.

This sounds like exactly what I was looking for with towers in bolodd2.g
and bolodd3.g (I wanted them to automatically fire at any enemy unit
that came within their firing range).  And I imagine that this feature
will prove valuable in many more games.

What would happen if multiple enemy units are within the zone of
overwatch?

---
Lincoln Peters
<sampln@sbcglobal.net>

Confucius say too much.
		-- Recent Chinese Proverb

  reply	other threads:[~2005-01-01  7:19 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 [this message]
2005-01-01 16:31   ` Eric McDonald
2005-01-01 21:09     ` Lincoln Peters
2005-01-01 21:38       ` Eric McDonald
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=1104563991.402.156.camel@localhost.localdomain \
    --to=sampln@sbcglobal.net \
    --cc=mcdonald@phy.cmich.edu \
    --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).