| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
This allows the chimera to take the legs of one of their parts.
This can give them the base speed of the legs monster,
also enables clinging, and for jumping spiders, will flavour a
self-blink as a jump instead of a blink.
|
| |
|
|
|
|
| |
This allows e.g.:
place:Zot:5 chimera
|
| |
|
|
|
|
|
|
|
|
| |
This enables a MONS spec to just be "chimera" and three depth-
appropriate monsters will be used. This can produce bizarre
results but might be useful. It should also allows things
like "place:Zot:5 chimera vs place:Pan chimera" in Arena.
The filters could be refined further to allow random chimera
to not be completely ridiculous.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In monster data it changes to S_RANDOM; this is fine for most purposes
for which this is used, e.g. determining whether or not a monster is
silent.
In handle_monster_shouts itself, the shout type is substituted for the
shout of one of the constituent parts.
There is a question mark over do_mon_str_replacements -- in most of the
places it's called from, chimera are irrelevant, and when it's called
from handle_monster_shouts the shout type we already determined is
passed in. So there shouldn't be any strange cases, unless perhaps
someone made something new that used sentient monsters as chimera
components. Would need to refactor mons_shouts to accept a monster
instead of a monster_type to make this any better.
|
| | |
|
| |
|
|
|
| |
If they have a batty component they'll now
have bat wings.
|
|
|
After creating the monster, the make_chimera function
in mon-chimera.cc can be used to set its component
creatures.
|
