From: Eric McDonald <mcdonald@phy.cmich.edu>
To: xconq-developers@lists.sourceforge.net,
xconq7 <xconq7@sources.redhat.com>
Subject: New Feature: Overwatch
Date: Sat, 01 Jan 2005 06:59:00 -0000 [thread overview]
Message-ID: <41D64A45.4030403@phy.cmich.edu> (raw)
Hello Xconq Game Designers,
I have implemented a new feature to ring in the new year. (I managed
to complete and test it just before local midnight.)
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.
Three new GDL tables are associated with this feature: 'zoo-range',
'zoo-range-min', and 'acp-for-overwatch'. 'zoo-range' and
'zoo-range-min' are TableUU, and specify range in cells. If 'zoo-range'
exceeds the overwatcher's fire 'range' property, it will be clipped to
that property. Likewise, if 'zoo-range-min' is less than the
overwatcher's fire 'range-min' property it will be clipped to that
property. 'acp-for-overwatch' (TableUU) is a mechanism for providing
additional ACP so that an unit can respond to violations of its ZOO,
even it would normally be out of ACP; the table tells how much extra ACP
an overwatcher will get for the purpose of firing on another unit of a
certain type.
There is still room for improvement. A probability table would be a
nice addition, as would doctrines controlling minimum materials needed
to overwatch fire and maximum number of overwatch firing against an unit
of a particular type per move of that unit. I also must ensure that it
can work with acp-indep units.
Enjoy, and happy [Gregorian] new year,
Eric
next reply other threads:[~2005-01-01 6:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 6:59 Eric McDonald [this message]
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
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=41D64A45.4030403@phy.cmich.edu \
--to=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).