public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Elijah Meeks <elijahmeeks@yahoo.com>
To: xconq7@sources.redhat.com
Subject: mcdonald@phy.cmich.edu
Date: Thu, 20 Nov 2003 21:22:00 -0000	[thread overview]
Message-ID: <20031120195327.90997.qmail@web13106.mail.yahoo.com> (raw)

"I believe that more than an icon is at stake here.
Damaged units have lessened capabilities (which cannot
be wholly addressed through acp-damage-effect)."

I just tested my setup last night and, to my pleasant
surprise, found that the hp-to-garrison totally wiped
out the original unit.  What I forgot to check was
whether this was because my hp-to-garrison was so high
that it burned through the various levels of
wrecked-type units or if it's within the code that a
unit destroyed by hp-to-garrison is 'vanished' instead
of 'destroyed'.  I'll find out tonight, but it works
and it's cool.  The only problem now is that there
needs to be four Xconq units for each normal unit
(i.e. Reinforced Corps, Corps, Understrength Corps,
Severely Depleted Corps just for a Corps).  I don't
mind creating the units and Xconq doesn't mind
processing them, but that's a whole heckava lot of
units for the player to need to scroll through in the
build window, especially given that units declared as
wrecked-types need to be declared before the units
that reference them.

Which is a long way of saying please, please, please
make the build window only show what can be built. 
Please!

Also, does Xconq have a hotseat mode?



__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

             reply	other threads:[~2003-11-20 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 21:22 Elijah Meeks [this message]
2003-11-20 22:16 ` mcdonald@phy.cmich.edu Lincoln Peters
2003-11-20 22:18   ` hotseat Andreas Bringedal
2003-11-20 22:32   ` Build List Limits and Hotseat Elijah Meeks
2003-11-20 22:39     ` Lincoln Peters
2003-11-21  1:09       ` Eric McDonald
2003-11-21  1:13         ` Elijah Meeks

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=20031120195327.90997.qmail@web13106.mail.yahoo.com \
    --to=elijahmeeks@yahoo.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).