Stendhal/Creature Organization/Examples

These changes should be able to be made without affecting the game. But the logic tilesets for Tiled should eventually be reworked. Creature classes only appear to affect class definition on the website.

Option 1: Very generalized categories

animal.xml

Merge the following:
- farm_animal.xml
- small_animal.xml
- crocodile
- giant spider
- giantrat
- king cobra

human.xml

Merge the following:
- amazoness.xml
- chaos.xml
- madaram.xml
- giant, elder giant, master giant, amazoness giant, ice giant, black giant (optionally to mythical.xml or hybrid.xml)

hybrid.xml

Merge the following into this file:
- beholder.xml
- demon.xml (optionally to undead.xml)
- elemental.xml (optionally to mythical_being.xml)
- ent.xml (optionally to mythical_being.xml)
- frogman.xml
- gargoyle.xml
- giant.xml
- goblin.xml
- golem.xml
- kobold.xml
- minotaur.xml
- oni.xml
- orc.xml
- ratfolk.xml
- sheepman.xml
- troll.xml
- cat woman
- dark mutant
- devil queen (optional)
- dwarf golem
- giant kobold
- glow monster
- green slime, brown slime, black slime, twilight slime
- imperial experiment
- imperial mutant
- lamia
- naga, high naga & armed naga
- thing
- werewolf

dragon.xml

- green dragon, blue dragon, red dragon, twin headed dragon, flying golden dragon, black dragon
- bone dragon (optionally to undead.xml)
- chaos green dragonrider (optionally to human.xml)
- chaos red dragonrider (optionally to human.xml)

undead.xml

Merge the following:
- mummy.xml
- vampire.xml
- black death
- gashadokuro
- golden death
- tiny skelly
- zombie rat (optional)

Option 2: More distinction between classes

This organization has been implemented in CVS. The reorganization does not break client/server compatibility, but does cause some inconsistencies with logic tilesets and sprite locations. Below are some suggestions for reorganizing logic tilesets. However, changing those will break compatibility. Reorganizing logic tilesets and spritesheet locations will need to be done a little at a time to not create a huge incompatibility between the server and client.

(***) Unsure about these options

angel.xml

animal.xml

arachnid
- giant spider
- spider & poisonous spider

crustacean
- crab

fowl
- chick
- chicken
- mother hen
- penguin
- pigeon

insect
- killer bee

mammal
- deer
- babybear & panda
- bat & killer bat
- bear & black bear
- beaver
- boar
- cow & bull
- elephant
- fox
- goat
- horse & white horse
- lion & tiger
- monkey
- mouse
- piglet
- ram
- rat, caverat, venomrat, razorrat & giantrat
- wolf & <creature "big bad wolf" not found>
- zombie rat (optionally animal_undead.xml, undead.xml or animal.xml)

mythical
- centaur
- pegasus
- unicorn

reptile
- caiman & crocodile
- cobra & king cobra
- snake & grass snake

beast.xml ***

beholder (possibly in its own class)

gargoyle

misc
- mimic
- snarfkin
- xenocium

mutant

slime (possibly in its own class)

stone (or merged with earth)
- dwarf golem ***
- stone golem ***

water
- water elemental

wind
- djinn

wood
- ent, old ent & entwife ***
- wooden golem ***

elf.xml

albino_elf

dark_elf

elf

giant.xml

amazon
- amazoness giant

human
- giant, elder giant, master giant
- black giant (alternative subclass "dark")

imperial
- imperial general giant

kobold
- giant kobold

madaram
- kasarkutominubat

gnome.xml

gnome
- gnome
- mage gnome
militant
- infantry gnome
- cavalryman gnome

goblin.xml

goblin

human.xml

amazon

assassin

barbarian

blordrough

cannibal

chaos
- chaos soldier
- chaos warrior
- chaos commander
- chaos sorcerer
- chaos dragonrider
- chaos lord
- chaos overlord
- chess pieces

imperial
- imperial archer, imperial archer leader & imperial elite archer
- imperial chief
- imperial commander
- imperial defender
- imperial demon servant & imperial demon lord (optionally demon.xml)
- imperial elite guardian
- imperial general
- imperial general giant (optionally giant.xml)
- imperial knight
- imperial leader
- imperial priest & imperial high priest
- imperial scientist
- imperial veteran

kalavan.xml

madaram
- madaram archer
- madaram peasant
- madaram trooper
- madaram soldier
- madaram healer
- madaram axeman
- madaram queen
- madaram hero
- madaram windwalker (alternate subclass "wind")
- madaram cavalry
- madaram stalker
- madaram buster blader
- chess pieces

misc
- emperor dalmung (not sure where this belongs)

mithrilbourgh.xml

monk
- devil monk
- monk & darkmonk

pirate (not activated)
- pirate
- pirate wench
- buccaneer
- smuggler
- evil pirate
- pirate leader

risecia

wizard ***
- littlewitch
- littlewizard

humanoid.xml ***

aruthon
- robot aruthon
- dark aruthon

fairy
- leprechaun & clurichaun
- littlefairy

misc
- brain ahouga

mohiko
- blue mohiko

roohako
- red roohako

hybrid.xml

arachnid
- arachne

cat woman
- cat woman

frogman

kobold

minotaur
- minotaur
- minotaur king

naga
- naga, high naga, armed naga
- lamia

rat folk
- ratman
- ratwoman
- archrat

sheepman

werewolf
- werewolf

oni.xml

oni

orc.xml

orc
- orc, orc spearman, orc hunter, orc warrior & orc chief
mountain orc
- mountain orc, mountain orc hunter, mountain orc warrior & mountain orc chief

troll.xml ***

Perhaps each of these should have its own category or placed in hybrid or humanoid?

cyclops
- cyclops

ogre
- ogre, elder ogre, ogre soldier & superogre

troll

undead.xml

animal
- zombie rat
- ghost hound

fallen

lich
- lich
- high lich
- dead lich

misc
- death knight
- necrosophia

mummy
- mummy
- royal mummy

skeleton

specter

vampire

zombie
- bloody zombie
- zombie
- rotten zombie
- headless monster
- myling (not activated)

Examples

A possible method of organization would be to put the creatures in a file with a corresponding class name, and use a subclass tag to segregate different creatures within their class.

Example: undead.xml This method will not be used. There is currently no use for using a subclass tag.

<creatures>

  <subclass value="skeleton">
    
    <creature name="skeleton">
    </creature>
    
    <creature name="warrior skeleton">
    </creature>
  
  </subclass>
  
  <subclass value="zombie">
  
    <creature name="zombie">
    </creature>
    
    <creature name="rotten zombie">
    </creature>
    
  </subclass>
  
</creatures>

In the above example creatures skeleton & warrior skeleton would be of class undead and subclass skeleton while zombie & rotten zombie would be class undead and subclass zombie.

If subclass tags not possible comments can be used in place of them in the traditional method: This is how the reorganizations is laid out. It is the same as before with comments to separate subclasses within the creature.xml.

<creatures>

  <!-- START: skeleton -->
    
  <creature name="skeleton">
  </creature>
  
  <creature name="warrior skeleton">
  </creature>

  <!-- END: skeleton -->
  
  <!-- START: zombie -->
  
  <creature name="zombie">
  </creature>
  
  <creature name="rotten zombie">
  </creature>
  
  <!-- END: zombie -->
  
</creatures>

Organization of logic tilesets

The logic tilesets can either be kept in the currently used directory and just refactored to match the creature.xml files. Or the tilesets can be placed in a subdirectory of "tileset/logic/creature". For example: amazon, which is a subclass of human, would be located in "tileset/logic/creature/human/amazon.png". NOTE: classes with many subclasses can be divided up.