From: Elijah Meeks <elijahmeeks@yahoo.com>
To: xconq7@sources.redhat.com
Subject: Overwatch and Counterbattery?
Date: Wed, 26 May 2004 21:00:00 -0000 [thread overview]
Message-ID: <20040526210028.61091.qmail@web13125.mail.yahoo.com> (raw)
In-Reply-To: <l03130300bcd98b98f2ce@[212.181.162.155]>
Does Xconq have any support for fire-protection?
Specifically, I'm thinking of two forms, the one being
firing upon a unit that comes within range, which as I
understand it is called Overwatch in the various
turn-based games I've played. The other would be
firing on a unit after that unit has fired, which is
basically Counterbattery fire. The latter has
something to do with being made aware of a unit, but I
think for Xconq purposes, setting a table such as
uu-protection-fire-chance which would define the
percent chance that u1 will fire on u2 if u2 fires and
is in range. This would produce the same effect, I
think, as to break down an admittedly more realistic,
but likely more complicated system of determining a
unit's threat level on-the-fly or simply having units
expend ACP/material firing on the first unit to get
close to them (An effect that could be achieved with
the proposed table by saying u1 u* 100).
Elijah
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
next prev parent reply other threads:[~2004-05-26 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 3:45 bug in infantry building a base which is already started Jim Kingdon
2004-05-24 20:00 ` Eric McDonald
2004-05-25 3:33 ` Eric McDonald
2004-05-25 21:53 ` Hans Ronne
2004-05-25 22:02 ` Hans Ronne
2004-05-25 22:27 ` Eric McDonald
2004-05-25 23:14 ` Hans Ronne
2004-05-25 23:28 ` Eric McDonald
2004-05-26 0:00 ` Hans Ronne
2004-05-26 21:00 ` Elijah Meeks [this message]
2004-05-26 21:35 ` Overwatch and Counterbattery? Hans Ronne
2004-05-27 2:17 ` Eric McDonald
2004-05-25 22:14 ` bug in infantry building a base which is already started Eric McDonald
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=20040526210028.61091.qmail@web13125.mail.yahoo.com \
--to=elijahmeeks@yahoo.com \
--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).