From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Skeezics Boondoggle <skeezics@q7.com>
Cc: xconq7@sources.redhat.com
Subject: Re: fighters fighting without ammo
Date: Sat, 13 Dec 2003 04:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312122309410.6182-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0312070811360.19370-100000@q7.q7.com>
Hi Chris,
On Sun, 7 Dec 2003, Skeezics Boondoggle wrote:
> Perhaps the calculations for both bomber and fighter attacks could reflect
> a proportional damage assessment based on how many defenders are present?
If we do something with Bruno's idea of distinguishing between
point weapons (bullets, etc...) and spread weapons (bombs,
etc...), then this might be definitely be something to think
about.
Another idea I have had for a while is "critical hits". Have
separate 'critical-hit-chance' and 'critical-hit-damage' tables
which would represent the chance to do extraordinary damage and
how much damage that would be. This could reflect things like a
bomb hitting a ship's ammo magazine or an assassin severing
someone's spinal cord.
> Choose one target with the "a" command and you inflict full damage on that
> one target; click on a full hex otherwise and you potentially inflict
> minor damage on multiple units. (But the HP granularity probably wouldn't
> allow for that level of precision, and could reduce the effectiveness of
> air attacks too much. Hmmm.)
Of course, HP and damage could be rescaled to reflect a new
granularity.
> I'm looking forward to some of the AI improvements, but y'know, most times
> I like to just take a break and "go conquer the world" so it's kind of
> relaxing to just swarm over the map and blast everything to bits. :-)
Personally, I think that clubbing baby seals gets boring after a
while.... Maybe if the AI's were more like young walruses that
tried to gore you occasionally, things would be a bit more
gratifying....
> I guess if the AIs start to get smarter I'll have to work a little harder.
> :-)
You poor devil. :-)
Regards,
Eric
prev parent reply other threads:[~2003-12-13 4:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 16:07 Kenneth Gonsalves
2003-12-07 16:54 ` Lincoln Peters
2003-12-07 17:36 ` Jim Kingdon
2003-12-07 18:13 ` Skeezics Boondoggle
2003-12-07 23:54 ` Bruno Boettcher
2003-12-13 5:11 ` Eric McDonald
2003-12-13 10:57 ` Bruno Boettcher
2003-12-13 12:02 ` Hans Ronne
2003-12-13 19:55 ` Eric McDonald
2003-12-13 20:02 ` Jim Kingdon
2003-12-14 4:33 ` Hans Ronne
2003-12-08 8:19 ` Kenneth Gonsalves
2003-12-13 4:59 ` Eric McDonald [this message]
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.0312122309410.6182-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=skeezics@q7.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).