From: mskala@ansuz.sooke.bc.ca
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: Consumption-per-fire?
Date: Sun, 06 Jun 2004 04:34:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0406060024520.7351-100000@diamond.ansuz.sooke.bc.ca> (raw)
In-Reply-To: <1086455552.1485.129.camel@localhost.localdomain>
On Sat, 5 Jun 2004, Eric McDonald wrote:
> This actually raises one of the gripes I have had with capture. A
> captive unit should not always be able to be used by the capturing side.
If the "unit" basically represents inanimate equipment, then it often
seems natural for the capturing side to be able to use it. If it
represents people, then that seems much less natural - prisoners of war
don't turn into soldiers for the side that captured them, barring a really
good brainwashing technology. Maybe it would be cool to be able to
overload wrecking even further with the chance to specify a unit type that
the captured unit will turn into - but I think that's another enhancement
that doesn't really need to be made right now.
On teleportation: one cool way to teleport is to construct a new instance
of yourself at a distance, and then be consumed by the hp-to-garrison
requirement of creating the new unit. I haven't tried that, but I think
it'd work.
--
Matthew Skala
mskala@ansuz.sooke.bc.ca Embrace and defend.
http://ansuz.sooke.bc.ca/
next prev parent reply other threads:[~2004-06-06 4:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 2:52 build doctrine question/bug? Tom Schaub
2004-05-30 3:28 ` Eric McDonald
2004-06-02 20:30 ` Consumption-per-fire? Elijah Meeks
2004-06-04 21:44 ` Consumption-per-fire? Hans Ronne
2004-06-04 22:15 ` Consumption-per-fire? Elijah Meeks
2004-06-04 22:50 ` Consumption-per-fire? Hans Ronne
2004-06-04 23:04 ` Consumption-per-fire? Elijah Meeks
2004-06-04 23:19 ` Consumption-per-fire? Eric McDonald
2004-06-05 3:37 ` Consumption-per-fire? Elijah Meeks
2004-06-05 4:22 ` Consumption-per-fire? Eric McDonald
2004-06-05 8:11 ` Consumption-per-fire? Hans Ronne
2004-06-05 8:22 ` Consumption-per-fire? Hans Ronne
2004-06-05 13:10 ` Consumption-per-fire? Eric McDonald
2004-06-05 15:03 ` Consumption-per-fire? Hans Ronne
2004-06-05 15:57 ` Consumption-per-fire? Elijah Meeks
2004-06-05 17:05 ` Consumption-per-fire? Hans Ronne
2004-06-05 18:37 ` Overrun actions (was: Consumption-per-fire?) Hans Ronne
2004-06-05 22:30 ` Elijah Meeks
2004-06-05 22:54 ` Jim Kingdon
2004-06-06 0:31 ` Hans Ronne
2004-06-06 0:59 ` Elijah Meeks
2004-06-06 2:21 ` Hans Ronne
2004-06-06 6:17 ` Eric McDonald
2004-06-06 7:39 ` Hans Ronne
2004-06-06 13:33 ` Eric McDonald
2004-06-05 17:15 ` Consumption-per-fire? Eric McDonald
2004-06-05 19:30 ` Consumption-per-fire? Hans Ronne
2004-06-06 6:32 ` Consumption-per-fire? Eric McDonald
2004-06-06 4:34 ` mskala [this message]
2004-06-06 6:52 ` Consumption-per-fire? Eric McDonald
2004-06-06 7:13 ` Consumption-per-fire? Lincoln Peters
2004-06-05 7:05 ` Consumption-per-fire? Hans Ronne
2004-06-04 23:12 ` Consumption-per-fire? Eric McDonald
2004-06-04 22:22 ` build doctrine question/bug? Hans Ronne
2004-06-05 17:08 ` Hans Ronne
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.21.0406060024520.7351-100000@diamond.ansuz.sooke.bc.ca \
--to=mskala@ansuz.sooke.bc.ca \
--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).