From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Table Request: Accident-Occupant-Effect
Date: Thu, 23 Sep 2004 03:10:00 -0000 [thread overview]
Message-ID: <41523CFA.6050902@phy.cmich.edu> (raw)
In-Reply-To: <20040923004610.31863.qmail@web13121.mail.yahoo.com>
Elijah Meeks wrote:
> Only accidents don't affect occupants. So, if anyone
> can think of a better solution to this problem, let me
> know, otherwise, if somebody in the know gets the
> chance, I think it's worthwhile to see accidents
> affect occupants.
Or how about a new unit property, 'auto-upgrade-chance'? By default this
would be 100%, so as to not interfere with the regular auto-upgrade
mechnaism. However, you could set it to 25%, and make sure that no
materials, advances, size, etc... are required for the auto-upgrade.
This feels less hackish than using accidents for such purpose, and may
prove useful in other situations as well.
Eric
P.S. Between you and Lincoln, it sounds like I am going to be doing
kernel hacking rather than SDL UI hacking this weekend. I guess I'll
have to cloister myself in a monastery somewhere with a laptop and no
access to the outside world, if I ever want to stay on track. :-)
next prev parent reply other threads:[~2004-09-23 3:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 1:40 Elijah Meeks
2004-09-23 2:26 ` mskala
2004-09-23 5:38 ` Eric McDonald
2004-09-23 15:09 ` Elijah Meeks
2004-09-23 17:59 ` Eric McDonald
2004-09-24 1:51 ` Elijah Meeks
2004-09-23 3:10 ` Eric McDonald [this message]
2004-09-23 17:47 ` Elijah Meeks
2004-09-23 18:23 ` 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=41523CFA.6050902@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=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).