public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Elijah Meeks <elijahmeeks@yahoo.com>
To: mskala@ansuz.sooke.bc.ca
Cc: xconq7@sources.redhat.com
Subject: Re: Table Request: Accident-Occupant-Effect
Date: Thu, 23 Sep 2004 15:09:00 -0000	[thread overview]
Message-ID: <20040923145926.22913.qmail@web13124.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0409222125590.29175-100000@diamond.ansuz.sooke.bc.ca>

--- mskala@ansuz.sooke.bc.ca wrote:

> On Wed, 22 Sep 2004, 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.
> 
> I don't know if this is better, but you could
> probably do it by giving
> each "offline" unit a material which, once fully
> consumed, will cause the
> unit to wreck into its "online" form.  For
> randomness you could give it
> just one point of the material and use a
> sufficiently small fractional
> consumption rate (we do support fractional
> consumption rates, right?).

That would work, also, but units that starve don't
wreck, they vanish.  So it would still need a change
to the code.




		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail

  parent reply	other threads:[~2004-09-23 14:59 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 [this message]
2004-09-23 17:59     ` Eric McDonald
2004-09-24  1:51       ` Elijah Meeks
2004-09-23  3:10 ` Eric McDonald
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=20040923145926.22913.qmail@web13124.mail.yahoo.com \
    --to=elijahmeeks@yahoo.com \
    --cc=mskala@ansuz.sooke.bc.ca \
    --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).