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 list <xconq7@sources.redhat.com>
Subject: Re: Transports that affect protection?
Date: Wed, 29 Sep 2004 14:52:00 -0000	[thread overview]
Message-ID: <1096435736.4050.4494.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0409281503001.15951-100000@leon.phy.cmich.edu>

On Tue, 2004-09-28 at 12:12, Eric McDonald wrote:
> 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....

That is an interesting thought, and I can see how it might solve this
problem.

> 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).

Somehow, I had not realized that a 3D table might be required to do
exactly what I was describing.  A "transport-adds-hit-chance-against"
table should work in my case, though.


I'll add that to the "to-do" list for knightmare.g, then implement it
there when it is implemented in the kernel.

(In case your wondering, I think I'm close to having an Alpha release
ready, but my off-line schedule is such that I can't predict exactly
when.)

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

Parts that positively cannot be assembled in improper order will be.

  parent reply	other threads:[~2004-09-29  5:26 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
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 [this message]
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=1096435736.4050.4494.camel@localhost \
    --to=sampln@sbcglobal.net \
    --cc=mcdonald@phy.cmich.edu \
    --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).