From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Transports that affect protection?
Date: Tue, 28 Sep 2004 21:13:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0409281503001.15951-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <1096345756.4050.437.camel@localhost>
On Mon, 27 Sep 2004, Lincoln Peters wrote:
> city. The wall usually provides 1000% protection against normal attacks
> (they can only attack the wall), so the army is going to have one heck
> of a time taking the city. On the other hand, if a siege tower moves
> adjacent to the city, any knights within the tower should be able to
> attack the city and ignore the wall. The same is true for knights who
> attack from flying vehicles or from the backs of flying monsters.
It is tempting to classify this as a sort of elevation-dependent
problem.
As I recall, there is already a property out there which affects
an occupant's height (for the purpose of vision). Perhaps this
could be commandeered for some sort of attack modification as
well. Just a thought....
> recently, but has anyone ever considered how one's transport might
> affect how one's attacks are affected by a defender's various
> protections?
I would probably restate the problem as how a transport modifies
its occupant's hit chance versus various targets. I believe that
there is already a sort of generalized occupant hit chance
modifier table, a TableUU between transport and occupant. I think
what you are proposing would perhaps require something like
'transport-adds-hit-chance-against' (one would not be able to
specify an occupant type in this case, since we don't have 3D
tables, __just the type of the occ's transport and the type of
the defender).
> When the wind is great, bow before it;
> when the wind is heavy, yield to it.
If Sun Tzu wrote that, the Mongols should have had one of their
vassals read it to them before they attempted their invasions of
Japan.
Eric
next prev parent reply other threads:[~2004-09-28 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 5:34 Lincoln Peters
2004-09-28 21:13 ` Eric McDonald [this message]
2004-09-29 1:38 ` mskala
2004-09-29 5:26 ` Eric McDonald
2004-09-30 2:05 ` mskala
2004-09-30 16:55 ` Eric McDonald
2004-09-29 14:52 ` Lincoln Peters
2004-09-29 18:34 ` 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=Pine.LNX.4.44.0409281503001.15951-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=sampln@sbcglobal.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).