This is the mail archive of the
xconq7@sources.redhat.com
mailing list for the Xconq project.
Re: Table Request: Accident-Occupant-Effect
- From: Elijah Meeks <elijahmeeks at yahoo dot com>
- To: Eric McDonald <mcdonald at phy dot cmich dot edu>
- Cc: xconq7 at sources dot redhat dot com
- Date: Thu, 23 Sep 2004 08:09:00 -0700 (PDT)
- Subject: Re: Table Request: Accident-Occupant-Effect
> 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.
I do like that, but is it possible to give a unit
multiple (auto-upgrade-to) properties? You know,
like:
(unit college-student (auto-upgrade-to dropout)
(auto-upgrade-to wageslave) (auto-upgrade-to
engineer))
(table auto-upgrade-chance
(college-student dropout 5000)
(college-student wageslave 3000)
(college-student engineer 2000)
)
Though the example's meant to be funny (dropout is
probably a wreck-type), the point is that you could
give units multiple paths based on the new table.
> 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. :-)
Sure, sounds great, but before you leave...
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com