From: Eric McDonald <mcdonald@phy.cmich.edu>
To: mskala@ansuz.sooke.bc.ca
Cc: Lincoln Peters <sampln@sbcglobal.net>,
Xconq list <xconq7@sources.redhat.com>
Subject: Re: Transports that affect protection?
Date: Wed, 29 Sep 2004 05:26:00 -0000 [thread overview]
Message-ID: <415A1B75.4090707@phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0409282035550.5703-100000@diamond.ansuz.sooke.bc.ca>
mskala@ansuz.sooke.bc.ca wrote:
> On Tue, 28 Sep 2004, Eric McDonald wrote:
>
>>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....
>
>
> What if you made the siege tower the attacker, modified by the knights in
> it, instead of the knights the attackers modified by the siege
> tower? Having the siege tower be the attacker may be less intuitive, but
> it might fit more easily into the existing capabilities of XConq.
If you can tell us which tables could be utilized to do that (with model
0 combat; it seems to be possible with model 1 combat), I am sure that
anyone who is interested in item units would be thrilled. From my
vantage point, I cannot see how it could be done with current tools.
That is why I proposed the 'occupant-adds-hit-chance',
'occupant-adds-damage', etc... tables a while back ago when we were on
the subject of item units. I would love to be proven wrong on this,
because it means less work further down the road.
The only way that I see to do something like this with existing tables
would be to make the siege tower ACP-less by default, and then have its
occupants add ACP to it. Even though I added this feature a while back
ago, it is not perfect in that, currently, you must wait until the next
turn for the new ACP value to take effect. More modifications to the
kernel scheduler and related code are required before the ACP mod will
be able to take effect in the same turn.
Or, see if the relevant tables work in combat model 1.
Eric
next prev parent reply other threads:[~2004-09-29 2:18 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 [this message]
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=415A1B75.4090707@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=mskala@ansuz.sooke.bc.ca \
--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).