public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Elijah Meeks <elijahmeeks@yahoo.com>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: Wrecked-Type Doesn't Apply to Detonating Units
Date: Mon, 16 Aug 2004 00:27:00 -0000	[thread overview]
Message-ID: <20040814174249.45766.qmail@web13125.mail.yahoo.com> (raw)
In-Reply-To: <411D8BE5.5040508@phy.cmich.edu>

> I don't recall intentionally setting it up that way.
> I suppose it could 
> be made to do so, but I am not sure whether that
> would be a good idea or 
> not. What if a detonating unit can also destroy
> another unit through 
> conventional means? I guess we could pretend that
> this is never a real 
> game design possiblility, and let the
> 'wrecked-type-if-destroyed' table 
> handle detonation deaths as well. If we don't, then
> probably YANT (yet 
> another new table) is called for:
> 'wrecked-type-if-blown-up', perhaps?

I think it's forseeable that you could want different
wreck-types depending on whether a unit destroys
another unit conventionally (In this case I'm thinking
of ships or battlemechs with nuclear engines, which
when destroyed or self-destructed perhaps cause
different effects than their regular attacks) but, for
now, I think it would be fine to just default the
wrecked-type-if-killed table to apply to detonating
units.  As far as I'm aware, there are no current
games that would be adversely affected by this and
there are a couple cute things I want to do with this
feature in Opal.




		
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

  parent reply	other threads:[~2004-08-14 17:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 17:51 time.g weirdness Robert Goulding
2004-08-10 18:11 ` Hans Ronne
2004-08-11  1:23 ` Hans Ronne
2004-08-11 16:34   ` Jim Kingdon
2004-08-11 16:34     ` Hans Ronne
2004-08-11 16:47       ` Eric McDonald
2004-08-11 17:09         ` Hans Ronne
2004-08-12  4:03           ` Eric McDonald
2004-08-12 11:16             ` Hans Ronne
2004-08-11 16:41     ` Eric McDonald
2004-08-12  8:42       ` Jim Kingdon
2004-08-12  8:56         ` Hans Ronne
2004-08-12 15:42           ` Jim Kingdon
2004-08-12 16:58             ` Eric McDonald
2004-08-12 17:35               ` Hans Ronne
2004-08-12 16:55         ` Eric McDonald
2004-08-12 15:39 ` Hans Ronne
2004-08-12 16:53   ` Jim Kingdon
2004-08-12 16:59     ` Hans Ronne
2004-08-12 17:08     ` Eric McDonald
2004-08-12 17:19       ` Hans Ronne
2004-08-12 17:24         ` Eric McDonald
2004-08-12 18:15           ` Hans Ronne
2004-08-13 23:46             ` Eric McDonald
2004-08-14  3:50             ` Wrecked-Type Doesn't Apply to Detonating Units Elijah Meeks
2004-08-14  9:19               ` Eric McDonald
2004-08-14 15:36                 ` Hans Ronne
2004-08-14 16:00                   ` Eric McDonald
2004-08-14 17:42                     ` Eric McDonald
2004-08-16  0:27                 ` Elijah Meeks [this message]
2004-08-16 18:24                   ` Eric McDonald
2004-08-16 21:34                     ` Elijah Meeks
2004-08-17  0:50                       ` 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=20040814174249.45766.qmail@web13125.mail.yahoo.com \
    --to=elijahmeeks@yahoo.com \
    --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).