[CF-Devel] new quetzal (dragon) race

[Andreas Vogl]

in reply to Peter M.:

>
     
      I don't see a compelling reason to modify the Quetzalcoatl instead
     
     >
     
      of creating another dragon player-race.
     
     
Sorry but I really would like to use the Quetzal-race for this.
My scheme ("dragon skin" and all that) is designed for dragons.
And I don't want two dragon races that work *completely* different.

May I suggest to move the old Quetzal-scheme to a different
race instead? What about the ever-unuseable fireborn for example?
Grant weapons to fireborns and that's it.
Or why not create a completely new race with fire immu and
no_armour (like the old Qetzal).

Though, I want to note that the old Quetzal-scheme has serious
problems because it cannot get a total level of resistances
that other players can get.
And the fire immu is often used for abusive purposes.
I thought replacing it would be an improvement - but I
have not problem with leaving it in the game in some way
(just not as Quetzal/dragon - please).

>
     
      This is reverse-compatible and extends the game rather than
     
     >
     
      mutating it, and possibly breaking someone's treasured characters.
     
     
I guarantee you that my work is 100% reverse-compatible.
Existing Q's of the old kind can continue to lead a happy
life with my code checked in.

>
     
      In terms of how to do it, I'd rather not see a lot of hard-wired
     
     >
     
      special purpose code having to do with dragons only implemented,
     
     >
     
      eg, when a DRAGON eats part of a FIRE ELEMENTAL'S RESIDUE, he
     
     >
     
      gains 5 points of fire immunity.
     
     
The way I have planned and coded it, it is a unique race
and therefore needs unique code. The dragon skin- and abilities
work together and it doesn't make sense to reuse this for other
races/classes.

If I want to make general reusable code, I would need to do it
completely different. I don't want to re-invent the skill system
or rewrite file parsers. Doing it as I planned is already
an immense load of work.

I've coded it as general and expandable as I could so far.
However, creating a feature like this without special code
is an impossible task for me.


Andreas