> > Yes, i usualy do that. But I'm implementing a lot of new classes (you ppl
> > will just love the coding I'm making for CLASS_VAMPIRE, including specials
> > and skills).
<snip>
> Class vampire? My unfinshed implementation is Race. Surely unless you are
> using classes as races, or have not got races , (just to cover myself)
> then a Race is a better idea.
I am constantly surprised to find out that people use class _OR_ race for
vampirism. I suppose it's the easy way to add something like this, but
being a purist of sorts, I have resisted taking this path until I have
time to do it correctly: as an affliction.
Historically (myths, stories, legends) vampirism is not race based, its
almost a disease, or curse. Almost every kind of creature has played its
part in vampire stories. AD&D (I bring up because of Diku's roots) even
contains vampiric animals. I myself am a fan of the Anne Rice style
vampires, but I digress.
I guess the point of this email was to make sure that I got the point
across that IMnsHO, far, far, FAR, too many MUDs, of all types, completely
ruin vampires by making them some class or race. If you are going to
bother to put vampires in your MUD, do it right, make sunlight hurt them,
make them need to feed, put in some kind of power hirearchy that may be
more important than leveling. Make it INTERESTING, not mundane!
Of course, that's what we all strive for, against the measuring stick of
popular opinion, it's sometimes hard to take an accurate measure.
-Ghost Shaidan
Implementor of Questionable Sanity
qs.mudservices.com 4000
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST