Crossfire Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Disease headaches
- To:
- Subject: Re: Disease headaches
- From: Mark Wedel <>
- Date: Thu, 08 Jun 2000 20:17:43 -0700
- References: <>
- Sender:
Peter Mardahl wrote:
>
> lib/races also effects the race field: another annoyance. Same thing,
> two places. I'll change the diseases to specifically list things I
> consider "humanoid", if you haven't done it already.
> It'd be really cool if you could do something with this.
lib/races should really go away.
It was added at one point as a convenience way to set races instead of changing
the archetypes. That doesn't mean there is a good reason to keep it - just as
easily, I could see adding a lib/hp file or the like to more easily tweak hp,
but I really don't want one.
The main point is the lib/races is not needed - it does not provide any more
information - all the information that is there can just as easily be put in the
archetypes themselves.
As far as races/subraces go, and easy way to do something would be have the
race field something like:
race/subrace (change specifier as appropriate, just don't make it a comma).
So for example, you might have thing like dragon/blue_dragon, humanoid/elf,
etc.
A better way would probably be to extend the archetypes to add a subrace
field. You have to be careful - the 'humanoid/human' is a little tricky - you
need to get exact matches and not submatches, otherwise something that is
specific to humans would match all the humanoid fields, which is not what is
wanted.