[ViewVC] Diff of: cvs/deliantra/Deliantra/res/types.xml

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.2 by root, Mon Mar 13 03:47:36 2006 UTC vs.
Revision 1.13 by root, Sun Mar 26 08:21:37 2006 UTC

 <?xml version="1.0" standalone="no" ?>
 <!--
 ######################################################################
-# types.xml - This is the defintitions-file for all the different    #
+# types.xml - This is the definitions-file for all the different     #
 # Crossfire object types and their attributes.                       #
 #                                                                    #
 # The server code of the Crossfire game is always changing and       #
 # evolving. From time to time, object-attributes change in purpose,  #
 # or new ones are created.                                           #
 # Therefore, it is important that an Editor is flexible and          #
 # easy to "upgrade" to handle such new features. That's why the      #
 # CFJavaEditor reads the type-definitions from this xml file.        #
 #                                                                    #
-# If you encounter bugs, typos or missing entrys in the LATEST       #
+# If you encounter bugs, typos or missing entries in the LATEST      #
 # VERSION of this file - Don't hesitate to improve it, contact me    #
 # and eventually send the improved file to me: <red.blaze@gmx.net>.  #
 # I will put it into the "official version" of the CFJavaEditor      #
 # and all fellow Crossfire-Map-Makers can benefit from your work!    #
 #                                                                    #
 # Created by Andreas Vogl.                                           #
 ######################################################################
 -->
 <!DOCTYPE types [
   <!ELEMENT types ((bitmask | list | ignore_list)*, default_type, ignore_list*, type+)>
   <!ELEMENT bitmask (entry*)>
   <!ATTLIST bitmask name CDATA #REQUIRED>
   <!ELEMENT list (entry*)>
   <!ATTLIST list name CDATA #REQUIRED>
   <!ELEMENT entry EMPTY>
   <!ATTLIST entry bit   CDATA #IMPLIED
                   value CDATA #IMPLIED
                   name  CDATA #REQUIRED>
   <!ELEMENT ignore_list (attribute* | EMPTY)>
   <!ATTLIST ignore_list name CDATA #REQUIRED>
   <!ELEMENT default_type (attribute*)>
   <!ELEMENT type (import_type?,required?,ignore?,description?,use?,(section | attribute)*)>
   <!ATTLIST type name   CDATA #REQUIRED
                  number CDATA #REQUIRED>
   <!ELEMENT description (#PCDATA)>
   <!ELEMENT use (#PCDATA)>
   <!ELEMENT import_type EMPTY>
   <!ATTLIST import_type name CDATA #REQUIRED>
   <!ELEMENT required (attribute+)>
   <!ELEMENT ignore (attribute*,ignore_list*)>
   <!ELEMENT section (attribute+)>
   <!ATTLIST section name CDATA #REQUIRED>
   <!ELEMENT attribute (#PCDATA)>
   <!ATTLIST attribute type       CDATA #IMPLIED
                       arch       CDATA #IMPLIED
                       arch_begin CDATA #IMPLIED
                       arch_end   CDATA #IMPLIED
                       editor     CDATA #IMPLIED
                       value      CDATA #IMPLIED
                       length     CDATA #IMPLIED
                       true       CDATA #IMPLIED
                       false      CDATA #IMPLIED>
+  <!ENTITY move_on "
+     <attribute arch='move_on' editor='movement type' type='bitmask_movement_type'>
+        Which movement types automatically (as opposed to manually) activate this object.
+     </attribute>
+  ">
+  <!ENTITY move_off "
+     <attribute arch='move_off' editor='movement type' type='bitmask_movement_type'>
+        Which movement types deactivate this object (e.g. button).
+     </attribute>
+  ">
+  <!ENTITY move_type "
+     <attribute arch='move_type' editor='movement type' type='bitmask_movement_type'>
+        Determines which kinds of movement this object can use (e.g. for monsters)
+        or grants (e.g. for amulets).
+     </attribute>
+  ">
+  <!ENTITY movement_types_terrain "
+     <attribute arch='move_block' editor='blocked movement' type='bitmask_movement_type'>
+       Objects using these movement types cannot move over this space.
+     </attribute>
+     <attribute arch='move_allow' editor='allowed movement' type='bitmask_movement_type'>
+       Objects using these movement types are allowed to move over this space. Takes
+       precedence over 'blocked movements'.
+     </attribute>
+     <attribute arch='move_slow' editor='slowed movement' type='bitmask_movement_type'>
+       The types of movement that should by slowed down by the 'slow movement penalty'.
+     </attribute>
+     <attribute arch='move_slow_penalty' editor='slow movement penalty' type='int'>
+       If &lt;slow movement&gt; is set to a value greater zero, all
+       creatures matching 'slow move' will be slower than normal on this spot.
+       &lt;slow movement&gt; 1  - rough terrain
+       &lt;slow movement&gt; 2  - very rough terrain
+       ...
+       &lt;slow movement&gt; 5  - default for deep swamp
+       ...
+       &lt;slow movement&gt; 7  - spider web (sticky as hell)
+     </attribute>
+  ">
+  <!ENTITY speed_left "
+     <attribute arch='speed_left' editor='speed left' type='float'>
+        The speed left to the object. On every tick, if this value is higher
+        than 0, the object acts/triggers/moves etc. and the value gets
+        decremented by 1. Otherwise, it is incremented by &lt;speed&gt; on
+        every tick.
+     </attribute>
+  ">
 ]>
 <types>
 <!--###################### bitmask definitions ######################-->
   <entry bit="4" name="Wood" />
   <entry bit="5" name="Organics" />
   <entry bit="6" name="Stone" />
   <entry bit="7" name="Cloth" />
   <entry bit="8" name="Adamantite" />
+  <entry bit="9" name="Liquid" />
+  <entry bit="10" name="Soft Metal" />
+  <entry bit="11" name="Bone" />
+  <entry bit="12" name="Ice" />
+  <entry bit="13" name="(supress name on display)" />
 </bitmask>
 <bitmask name="spellpath">
   <entry bit="0" name="Protection" />
   <entry bit="1" name="Fire" />
   <entry bit="2" name="Food" />
   <entry bit="3" name="Weapons" />
   <entry bit="4" name="Armour" />
   <entry bit="5" name="Inverse" />
   <entry bit="6" name="All" />
+</bitmask>
+<bitmask name="movement_type">
+  <entry bit="0" name="Walk" />
+  <entry bit="1" name="Fly Low" />
+  <entry bit="2" name="Fly High" />
+  <entry bit="3" name="Swim" />
+  <entry bit="4" name="Boat" />
+  <entry bit="16" name="Other" />
 </bitmask>
 <!--###################### list definitions ######################-->
 <list name="direction">
   <entry value="45" name="disease" />
   <entry value="46" name="aura" />
   <entry value="47" name="town portal" />
 </list>
+<list name="event_type">
+  <entry value="0" name="none" />
+  <entry value="1" name="apply" />
+  <entry value="2" name="attack" />
+  <entry value="3" name="death" />
+  <entry value="4" name="drop" />
+  <entry value="5" name="pickup" />
+  <entry value="6" name="say" />
+  <entry value="7" name="stop" />
+  <entry value="8" name="time" />
+  <entry value="9" name="throw" />
+  <entry value="10" name="trigger" />
+  <entry value="11" name="close" />
+  <entry value="12" name="timer" />
+  <entry value="28" name="move" />
+</list>
+<list name="attack_movement_bits_0_3">
+   <entry value="0" name="default" />
+   <entry value="1" name="attack from distance" />
+   <entry value="2" name="run away" />
+   <entry value="3" name="hit and run" />
+   <entry value="4" name="wait, then hit, then move" />
+   <entry value="5" name="rush blindly" />
+   <entry value="6" name="always run" />
+   <entry value="7" name="attack from distance if hit" />
+   <entry value="8" name="do not approach" />
+</list>
+<list name="attack_movement_bits_4_7">
+   <entry value="0" name="none" />
+   <entry value="16" name="pet" />
+   <entry value="32" name="small circle" />
+   <entry value="48" name="large circle" />
+   <entry value="64" name="small horizontal" />
+   <entry value="80" name="large horizontal" />
+   <entry value="96" name="random direction" />
+   <entry value="112" name="random movement" />
+   <entry value="128" name="small vertical" />
+   <entry value="144" name="large vertical" />
+</list>
 <!--###################### default attributes ######################-->
 <!--
   The attributes of the default_type get added to all other types by default.
   Every type can have an 'ignore' element however, which is used to specify
     This is the plural name of the object. A plural name must be set for
     all items that can be picked up and collected by the player.
   </attribute>
   <attribute arch="title" editor="title" type="string">
     This is the object's title. Once an object is identified the title is
-    attached to the name. Typical titels are "of mostrai", "of xray vision" etc.
+    attached to the name. Typical titles are "of Mostrai", "of xray vision" etc.
   </attribute>
   <attribute arch="face" editor="image" type="string">
     The image-name defines what image is displayed for this object in-game.
   </attribute>
   <attribute arch="nrof" editor="number" type="int">
     This value determines the number of objects in one stack (for example:
     100 goldcoins =&gt; "number = 100"). You should set this at least to one, for
     any pickable object - otherwise it won't be mergeable into a stack.
   </attribute>
   <attribute arch="weight" editor="weight" type="int">
-    This value defines the object's weight in gramm (1000g is 1kg). Objects with
+    This value defines the object's weight in grams (1000g is 1kg). Objects with
     zero weight are not pickable for players. Still, set the "non-pickable"-flag
     for explicitly non-pickable objects (hey, this is opensource.. you
     never know ;) ).
   </attribute>
   <attribute arch="value" editor="value" type="int">
-    Adds a certain value to the object: It will be worth that many times the
+    Determines the value of the object, in units of silver coins (one
-    default value from it's archetype (E.g. "value = 3" means three times
+    platinum coin == 50 silver coins). Value for buying/selling will be
-    worth the default value). Value for buying/selling will be
     further modified by various factors. Hence, testing values in-game is
     usually inevitable.
   </attribute>
   <attribute arch="glow_radius" editor="glow radius" type="int">
     If &lt;glow radius&gt; is set to a value greater zero, the object
     appears lit up on dark maps. &lt;glow radius&gt; can be a value
-    between 0 and 4, the higher, the more light does the object emmit.
+    between 0 and 4, the higher, the more light does the object emit.
   </attribute>
   <attribute arch="material" editor="material" type="bitmask_material">
     This bitmask-value informs the player of which material(s) the
     object consists. Material does also affect how likely the object
     can be destroyed by hazardous spell-effects.
          the fallback for all types which don't match any other defined types.
          The required attribute "misc x" prevents that it gets confused with
          other types like "monster & npc" which also have type number 0. -->
     <attribute arch="misc" value="x" />
   </required>
-  <attribute arch="no_pass" editor="blocking passage" type="bool">
+  &movement_types_terrain;
-    If set, the object cannot be passed by players nor monsters.
-  </attribute>
   <attribute arch="cursed" editor="cursed" type="bool">
     Curses can have various effects: On equipment and food,
     they generally harm the player in some way.
   </attribute>
   <attribute arch="damned" editor="damned" type="bool">
   </attribute>
   <attribute arch="hp" editor="long range spell" type="nz_spell">
     The monster will use the specified &lt;long range spell&gt;
     when the player is at least 6 squares away (from the
     monster's head).
     Setting a &lt;long range spell&gt; is optional. If unset, the
     &lt;short range spell&gt; gets used all the time.
   </attribute>
   <attribute arch="maxsp" editor="importance" type="int">
     Sometimes you'll want a monster to use one ability more than others.
     To achieve this, set the &lt;importance&gt; to a value greater than
     one. Abilities with this value zero/unset are counted to be of
     &lt;importance&gt; one.
     Example: A monster with "small fireball" of &lt;importance&gt; 3 and
     "paralyze" of &lt;importance&gt; 1 will averagely cast three out of four
     times the "small fireball".
   </attribute>
   <attribute arch="attacktype" editor="is magical" true="2" false="0" type="bool_special">
-    This flag specifies wether the ability &lt;is magical&gt; in nature.
+    This flag specifies whether the ability &lt;is magical&gt; in nature.
     If enabled, all spells produced by this ability will have magic
     attacktype added to the usual attacktypes.
     This should always be set for spell-like abilities. "Natural"
     abilities like a dragon's firebreath are an exception.
     Note that non-magical abilities are more dangerous because
     magic resistance does not protect from those.</attribute>
 </type>
   </ignore>
   <description><![CDATA[
     When a player puts a defined number of certain items on the altar,
     then either a spell is casted (on the player) or a connector is
     triggered. If the latter is the case, the altar works only once.
-    Either way, the sacrificed item dissapears. ]]>
+    Either way, the sacrificed item disappears. ]]>
   </description>
   <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="walk_on" value="1" type="fixed" />
+  &move_on;
   <attribute arch="slaying" editor="match item name" type="string">
     This string specifies the item that must be put on the altar to
     activate it. It can either be the name of an archetype, or directly
     the name of an object. Yet, titles are not recognized by altars.
     Remember to put a note somewhere, telling the player what he is
     expected to drop on the altar. (Often this is put in the altar's
     name: E.g. "drop 100 platinums")
   </attribute>
   <attribute arch="food" editor="drop amount" type="int">
     The drop amount specifies the amount of items (specified
     in &lt;match item name&gt;) that must be dropped to activate the altar.
     If &lt;match item name&gt; is set to "money", then the value of the
     sacrificed money must be equal to &lt;drop amount&gt; (ie, if food=200, then
     200 silver, 20 gold, or 4 platinum will all work.)
     Note that the maximum possible for &lt;drop amount&gt; is 32767.
   </attribute>
   <attribute arch="connected" editor="connection" type="int">
     If a connection value is set, the altar will trigger all objects
     with the same value, when activated. This will only work once.
   </attribute>
   <attribute arch="sp" editor="spell" type="spell">
     When activated, the selected &lt;spell&gt; will be casted (once, on the
     player). This should work for any given spell. The altar will work
-    infinitly in this way. Don't set both &lt;spell&gt; and &lt;connection&gt; for
+    infinitely in this way. Don't set both &lt;spell&gt; and &lt;connection&gt; for
     one altar.
   </attribute>
   <attribute arch_begin="msg" arch_end="endmsg" editor="message" type="text">
     This text will be displayed to the player
     in the exact moment when the altar is activated.
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     Altar_triggers work pretty much like normal altars
     (drop sacrifice -> connection activated), except for the fact that
-    they reset after usage. Hence, altar_triggers can be used infinitly. ]]>
+    they reset after usage. Hence, altar_triggers can be used infinitely. ]]>
   </description>
   <use><![CDATA[
     Altar_triggers are very useful if you want to charge a price for...
     <UL>
     <LI> ...an item. -> Connect the altar_trigger (set "last_sp 1") to a creator.
     <LI> ...opening a gate. -> Connect the altar_trigger (set "last_sp 0") to the gate.
     <LI> ...information. -> Connect the altar_trigger (set "last_sp 1") to a magic_mouth.
     </UL>
     The big advantage over normal altars is the infinite usability
     of altar_triggers! If there are ten players on one server, they're
     quite grateful if things work more than once. =) ]]>
     expected to drop on the altar. (Often this is put in the altar's
     name: E.g. "drop 100 platinums")
   </attribute>
   <attribute arch="food" editor="drop amount" type="int">
     The drop amount specifies the amount of items (specified
     in &lt;match item name&gt;) that must be dropped to activate the altar.
     If &lt;match item name&gt; is set to "money", then the value of the
     sacrificed money must be equal to &lt;drop amount&gt; (ie, if food=200, then
     200 silver, 20 gold, or 4 platinum will all work.)
     Note that the maximum possible for &lt;drop amount&gt; is 32767.
   </attribute>
   <attribute arch="connected" editor="connection" type="int">
     If a connection value is set, the altar will trigger all objects
     with the same value, when activated. This will only work once.
   </attribute>
   <attribute arch="sp" editor="spell" type="spell">
     When activated, this &lt;spell&gt; will be casted (once, on the player).
-    This should work for any given spell. The altar will work infinitly
+    This should work for any given spell. The altar will work infinitely
     in this way. Don't set both &lt;spell&gt; and &lt;connection&gt; for one altar.
   </attribute>
   <attribute arch="exp" editor="reset time" type="int">
     Being activated, the altar will reset after &lt;reset time&gt; ticks.
     After reset, the altar is ready to be activated once again.
   </attribute>
   <attribute arch="last_sp" editor="ignore reset" type="bool">
     If this attribute is enabled, the altar_trigger won't push the
     connected value by altar reset. Only ONCE by dropping the sacrifice.
     This is typically used when the altar is connected to a creator,
     e.g. for selling tickets.
     If this attribute is disabled (default), the altar_trigger
     will push the connected value TWICE per sacrifice: First by
     dropping sacrifice, second by reset. This mode is typically
     used for altars being connected to gates, resulting in the
     gate being opened and closed again.
   </attribute>
-  <attribute arch="walk_on" value="1" type="fixed">
+  &move_on;
-  </attribute>
   <attribute arch_begin="msg" arch_end="endmsg" editor="message" type="text">
     This text will be displayed to the player
     in the exact moment when the altar is activated.
   </attribute>
 </type>
     The &lt;item power&gt; value measures how "powerful" an artifact is.
     Players will only be able to wear equipment with a certain total
     amount of &lt;item power&gt;, depending on their own level. This is the
     only way to prevent low level players to wear "undeserved" equipment
     (like gifts from other players or cheated items).
     It is very important to adjust the &lt;item power&gt; value carefully
     for every artifact you create! If zero/unset, the CF server will
     calculate a provisional value at runtime, but this is never
     going to be an accurate measurement of &lt;item power&gt;.
   </attribute>
     unless the curse is removed.
   </attribute>
   <attribute arch="lifesave" editor="save life" type="bool">
     An item with this flag enabled will save the players life
     for one time: When the player is wearing this item and his
-    healthpoints reach zero, the item dissapears, replenishing
+    health points reach zero, the item disappears, replenishing
     half of the player's health.
     An item with &lt;save life&gt; should not have
     any decent additional bonuses!
   </attribute>
   <attribute arch="unique" editor="unique item" type="bool">
     Unique items exist only one time on a server. If the item
     additional &lt;grace regen.&gt; bonus should be VERY RARE!!
   </attribute>
   <attribute arch="food" editor="food bonus" type="int">
     Positive &lt;food bonus&gt; slows down the player's digestion,
     thus he consumes less food. Negative values speed it up.
     Note that food is consumed not only for "being alive", but
     also for healing and mana-regeneration.
     &lt;food bonus&gt; only affects the amount of food consumed
     for "being alive". Hence, even with high &lt;food bonus&gt;,
     during a fight a player can run out of food quickly.
   </attribute>
   <attribute arch="xrays" editor="xray vision" type="bool">
     Xray vision allows the player to see through obstacles
     in a two-square-wide radius. This is extremely helpful and
-    desireable, so don't give it away for cheap on equipment.
+    desirable, so don't give it away for cheap on equipment.
   </attribute>
   <attribute arch="stealth" editor="stealth" type="bool">
     Stealth allows the player to move silently.
     This comes to effect if a player turns himself
     invisible and tries to sneak around monsters.
     the ability to &lt;reflect spells&gt;, all kinds of
     spell-bullets and -beams will bounce off him.
     This works only about 90% of all times, to
     avoid players being completely immune to certain
     types of attacks.
     This is a very powerful ability and it
     shouldn't be handed out cheap!
   </attribute>
   <attribute arch="reflect_missile" editor="reflect missiles" type="bool">
     If a player is wearing any piece of equipment with
     projectiles (e.g. arrows, bolts, boulders) will
     bounce off him. This works only about 90% of all
     times, to avoid players being completely immune to
     certain types of attacks.
   </attribute>
-  <attribute arch="flying" editor="levitate" type="bool">
+  &move_type;
-    As soon as the player applies a piece of equipment with
-    &lt;levitate&gt; set, the player will start to float in the air.
-  </attribute>
   <attribute arch="path_attuned" editor="attuned paths" type="bitmask_spellpath">
     Click on the &lt;attuned paths&gt; button to select spellpaths.
     The player will get attuned to the specified spellpaths
     while wearing this item.
   </attribute>
     get teleported after they died on this battleground.
   </attribute>
 </type>
 <!--####################################################################-->
-<type number="104" name="Bracers">
-  <import_type name="Amulet" />
-  <description><![CDATA[
-    Bracers are armour-plates worn around the wrists.
-    Wearing bracer, the object's stats will directly be inherited to
-    the player. Usually enhancing his defense. ]]>
-  </description>
-  <use><![CDATA[
-    Feel free to create your own special artifacts. However, it is very
-    important that you keep your artifact in balance with existing maps. ]]>
-  </use>
-  <attribute arch="magic" editor="magic bonus" type="int">
-    &lt;magic bonus&gt; works just like ac, except that it can be improved by
-    "scrolls of Enchant Armour" or reduced by acid. It is less useful
-    than direct armour-class bonus on the bracers.
-  </attribute>
-</type>
-<!--####################################################################-->
-<type number="16" name="Brestplate Armour">
-  <import_type name="Amulet" />
-  <description><![CDATA[
-    Wearing an armour, the object's stats will directly be inherited to
-    the player. Usually enhancing his defense. ]]>
-  </description>
-  <use><![CDATA[
-    Feel free to create your own special artifacts. However, it is very
-    important that you keep your artifact in balance with existing maps. ]]>
-  </use>
-  <attribute arch="last_heal" editor="spellpoint penalty" type="int">
-    This poses a penalty to spell regeneration speed, for wearing the armour.
-    The bigger the spellpoint penalty, the worse.
-  </attribute>
-  <attribute arch="last_sp" editor="slowdown penalty" type="int">
-    Slowdown penalty reduces the player's walking speed when wearing the
-    armour. Bigger values are worse - zero is best.
-  </attribute>
-  <attribute arch="magic" editor="magic bonus" type="int">
-    &lt;magic bonus&gt; works just like ac, except that it can be improved by
-    "scrolls of Enchant Armour" or reduced by acid. It is less useful
-    than direct armour-class bonus on the armour.
-  </attribute>
-</type>
-<!--####################################################################-->
 <type number="8" name="Book">
   <description><![CDATA[
     Applying a book, the containing message is displayed to the player. ]]>
   </description>
   <attribute arch="level" editor="literacy level" type="int">
     is taken, lost or destroyed - it's gone for good.
   </attribute>
   <attribute arch_begin="msg" arch_end="endmsg" editor="book content" type="text">
     This is the text that appears "written" in the book.
   </attribute>
+  <attribute arch="slaying" editor="key string" type="string">
+    This is the key string of the book. The key string is checked by an inventory checker.
+    (This is used eg. for the gate/port passes in scorn)
+  </attribute>
 </type>
 <!--####################################################################-->
 <type number="99" name="Boots">
   <import_type name="Amulet" />
   </attribute>
   <attribute arch="magic" editor="magic bonus" type="int">
     &lt;magic bonus&gt; works just like ac, except that it can be improved by
     "scrolls of Enchant Armour" or reduced by acid. It is less useful
     than direct armour-class bonus on the boots.
     Important: &lt;magic bonus&gt; on boots has no effect if there is no
     &lt;armour class&gt; set. It only works in combination with &lt;armour class&gt;.
+  </attribute>
+</type>
+<!--####################################################################-->
+<type number="104" name="Bracers">
+  <import_type name="Amulet" />
+  <description><![CDATA[
+    Bracers are armour-plates worn around the wrists.
+    Wearing bracer, the object's stats will directly be inherited to
+    the player. Usually enhancing his defense. ]]>
+  </description>
+  <use><![CDATA[
+    Feel free to create your own special artifacts. However, it is very
+    important that you keep your artifact in balance with existing maps. ]]>
+  </use>
+  <attribute arch="magic" editor="magic bonus" type="int">
+    &lt;magic bonus&gt; works just like ac, except that it can be improved by
+    "scrolls of Enchant Armour" or reduced by acid. It is less useful
+    than direct armour-class bonus on the bracers.
+  </attribute>
+</type>
+<!--####################################################################-->
+<type number="16" name="Brestplate Armour">
+  <import_type name="Amulet" />
+  <description><![CDATA[
+    Wearing an armour, the object's stats will directly be inherited to
+    the player. Usually enhancing his defense. ]]>
+  </description>
+  <use><![CDATA[
+    Feel free to create your own special artifacts. However, it is very
+    important that you keep your artifact in balance with existing maps. ]]>
+  </use>
+  <attribute arch="last_heal" editor="spellpoint penalty" type="int">
+    This poses a penalty to spell regeneration speed, for wearing the armour.
+    The bigger the spellpoint penalty, the worse.
+  </attribute>
+  <attribute arch="last_sp" editor="slowdown penalty" type="int">
+    Slowdown penalty reduces the player's walking speed when wearing the
+    armour. Bigger values are worse - zero is best.
+  </attribute>
+  <attribute arch="magic" editor="magic bonus" type="int">
+    &lt;magic bonus&gt; works just like ac, except that it can be improved by
+    "scrolls of Enchant Armour" or reduced by acid. It is less useful
+    than direct armour-class bonus on the armour.
   </attribute>
 </type>
 <!--####################################################################-->
 <type number="92" name="Button">
     When a predefined amount of weigh is placed on a button, the
     &lt;connection&gt; value is triggered. In most cases this happens when a
     player or monster steps on it. When the button is "released", the
     &lt;connection&gt; value get's triggered a second time. ]]>
   </description>
-  <attribute arch="walk_on" value="1" type="fixed" />
+  &move_on;
-  <attribute arch="walk_off" value="1" type="fixed" />
+  &move_off;
   <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="weight" editor="press weight" type="string">
+  <attribute arch="weight" editor="press weight" type="int">
     The button is pressed (triggered), as soon as
     &lt;press weigh&gt; gram are placed ontop of it.
   </attribute>
   <attribute arch="connected" editor="connection" type="int">
     Every time the button is pressed or released, all objects
   </attribute>
   <attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
     This text may describe the item. You can use this
     message to explain the button's purpose to the player.
   </attribute>
+</type>
+<!--####################################################################-->
+<type number="30" name="Button Trigger">
+  <import_type name="Button" />
+  <ignore>
+    <ignore_list name="non_pickable" />
+  </ignore>
+  <description><![CDATA[
+    Handle buttons are buttons which reset after a short period
+    of time. Every time it is either applied or reset, the
+    &lt;connection&gt; value is triggered. ]]>
+  </description>
+</type>
+<!--####################################################################-->
+<type number="37" name="Class Changer">
+  <ignore>
+    <ignore_list name="non_pickable" />
+  </ignore>
+  <description><![CDATA[
+    Class changer are used while creating a character. ]]>
+  </description>
+  <attribute arch="randomitems" editor="class items" type="treasurelist">
+    This entry determines which initial items the character receives.
+  </attribute>
+<section name="stats">
+  <attribute arch="Str" editor="strength" type="int">
+    The player's strength will rise by the given value if he chooses this
+    class. (Negative values make strength fall)
+  </attribute>
+  <attribute arch="Dex" editor="dexterity" type="int">
+    The player's dexterity will rise by the given value if he chooses this
+    class. (Negative values make dexterity fall)
+  </attribute>
+  <attribute arch="Con" editor="constitution" type="int">
+    The player's constitution will rise by the given value if he chooses this
+    class. (Negative values make constitution fall)
+  </attribute>
+  <attribute arch="Int" editor="intelligence" type="int">
+    The player's intelligence will rise by the given value if he chooses this
+    class. (Negative values make intelligence fall)
+  </attribute>
+  <attribute arch="Pow" editor="power" type="int">
+    The player's power will rise by the given value if he chooses this
+    class. (Negative values make power fall)
+  </attribute>
+  <attribute arch="Wis" editor="wisdom" type="int">
+    The player's wisdom will rise by the given value if he chooses this
+    class. (Negative values make wisdom fall)
+  </attribute>
+  <attribute arch="Cha" editor="charisma" type="int">
+    The player's charisma will rise by the given value if he chooses this
+    class. (Negative values make charisma fall)
+  </attribute>
+</section>
 </type>
 <!--####################################################################-->
 <type number="87" name="Cloak">
   <import_type name="Amulet" />
   </use>
   <attribute arch="magic" editor="magic bonus" type="int">
     &lt;magic bonus&gt; works just like ac, except that it can be improved by
     "scrolls of Enchant Armour" or reduced by acid. It is less useful
     than direct armour-class bonus on the cloak.
     Important: &lt;magic bonus&gt; on cloaks has no effect if there is no
     &lt;armour class&gt; set. It only works in combination with &lt;armour class&gt;.
   </attribute>
 </type>
     </UL> ]]>
   </use>
   <attribute arch="race" editor="container class" type="string">
     If set, the container will hold only certain types of objects.
     Possible choices for &lt;container class&gt; are: "gold and jewels",
     "arrows" and "keys".
     Unfortunately it is not easy to create new container
     classes, because items need a matching counterpiece-attribute
     to the &lt;container class&gt; before they can be put inside a
     container. This attribute ("race") is set only for the existing
     container classes.
     one of the inventory items is duplicated. The duplicated item is randomly
     chosen from all items present.
   </attribute>
   <attribute arch="connected" editor="connection" type="int">
     Whenever the connection value is activated,
     the creator gets triggered.
   </attribute>
   <attribute arch="lifesave" editor="infinit uses" type="bool">
     If &lt;infinit uses&gt; is set, the creator will work
-    infinitly, regardless of the value in &lt;number of uses&gt;.
+    infinitely, regardless of the value in &lt;number of uses&gt;.
   </attribute>
   <attribute arch="hp" editor="number of uses" type="int">
     The creator can be triggered &lt;number of uses&gt; times, thus
     creating that many objects, before it dissappears.
     Default is &lt;number of uses&gt; 1 (-&gt; one-time usage).
   </attribute>
   <attribute arch="speed" editor="detection speed" type="float">
     This value defines the time between two detector-checks.
     If you want the detector to behave almost like pedestals/buttons,
     set speed rather high, like &lt;detection speed&gt; 1.0.
+  </attribute>
+  &speed_left;
+  <attribute arch="speed_left" editor="speed left" type="float">
+    The speed left. This value is incremented by &lt;speed&gt; on every tick.
+    If it is larger than 0, the detector checks, and the speed is decremented
+    by 1.
   </attribute>
 </type>
 <!--####################################################################-->
 <type number="112" name="Director">
   <attribute arch="sp" editor="direction" type="list_direction">
     Projectiles will leave the director flying in the selected &lt;direction&gt;.
     A director with direction &lt;none&gt; simply stops projectiles.
     (The latter works out a bit strange for some spells).
   </attribute>
-  <attribute arch="walk_on" value="1" type="fixed" />
+  &move_on;
-  <attribute arch="fly_on" value="1" type="fixed" />
 </type>
 <!--####################################################################-->
 <type number="158" name="Disease">
   <ignore>
 <section name="spreading">
   <attribute arch="wc" editor="infectiosness" type="int">
     The &lt;infectiosness&gt; defines the chance of new creatures getting
     infected. If you set this too high, the disease is very likely to
     be too effective.
     &lt;infectiosness&gt;/127 is the chance of someone in range catching it.
   </attribute>
   <attribute arch="last_grace" editor="attenuation" type="int">
     The &lt;attenuation&gt; value reduces the diseases' &lt;infectiosness&gt;
     everytime it infects someone new. This limits how many generations
   <attribute arch="magic" editor="infection range" type="int">
     &lt;infection range&gt; sets the range at which infection may occur.
     If positive, the &lt;infection range&gt; is level dependant - If negative,
     it is not:
     E.g. "&lt;infection range&gt; -6" means creatures can be infected in
     six square range, and &lt;plaque level&gt; doesn't modify that.
   </attribute>
   <attribute arch="maxhp" editor="persistence" type="int">
     &lt;persistence&gt; defines how long the disease can persist OUTSIDE a host.
     The disease can "move" &lt;persistence&gt; times outside a host before it
     vanishes. A negative value means the disease lasts for permanent
   <attribute arch="maxgrace" editor="curing duration" type="int">
     The disease will last in the host for &lt;curing duration&gt; "disease moves"
     (Assuming the host survives and doesn't use a curing spell).
     After this period the disease is naturally cured, which provides the
     host with immunity from this particular disease of lower or equal level.
     A negative value means the disease can never be cured naturally.
     Note that this value can be further modulated by spell-parameters,
     if the disease is registered as spell in the code. Due to that,
     most default diseases take a lot longer to cure than it seems.
   </attribute>
   <attribute arch="speed" editor="moving speed" type="float">
     The &lt;speed&gt; of the disease determines how fast the disease will
     "move", thus how fast the symptoms strike the host.
   </attribute>
+  &speed_left;
 </section>
 <section name="symptoms">
   <attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
     The disease will attack the host with the given &lt;attacktype&gt;.
     Godpower attacktype is commonly used for "unresistable" diseases.
   <attribute arch="dam" editor="damage" type="int">
     A disease with a positive &lt;damage&gt; value will strike the player for that
     amount of damage every time the symptoms occur.
     A negative &lt;damage&gt; value produces %-based damage: "&lt;damage&gt; -10" means
     the player's health is reduced by 10% every time the symptoms strike.
     Diseases with %-based damage can be dangerous - but not deadly -
     for players of all levels.
   </attribute>
   <attribute arch="other_arch" editor="create arch" type="string">
     If set, the specified arch is created and dropped every time the
     symptoms strike.
     This can be various things: farts, body pieces, eggs ...
     Even monsters can be created that way. You could also make a
     disease where some exotic stuff like money/gems is created.
   </attribute>
   <attribute arch="last_sp" editor="slowdown penalty" type="int">
   </attribute>
 </section>
   <attribute arch_begin="msg" arch_end="endmsg" editor="message" type="text">
     This text is displayed to the player every time the
     symptoms strike.
+  </attribute>
+</type>
+<!--####################################################################-->
+<type number="23" name="Door">
+  <ignore>
+    <ignore_list name="non_pickable" />
+  </ignore>
+  <description><![CDATA[
+    A door can be opened with a normal key. It also can be broken by attacking
+    it, and it can be defeated with the lockpicking skill. If a door is
+    defeated, horizontally and vertically adjacent doors are automatically
+    removed. ]]>
+  </description>
+  <attribute arch="no_pick" value="1" type="fixed" />
+  <attribute arch="alive" value="1" type="fixed" />
+  &movement_types_terrain;
+  <attribute arch="hp" editor="hitpoints" type="int">
+    The more &lt;hitpoints&gt; the door has, the longer it takes to be broken.
+  </attribute>
+  <attribute arch="ac" editor="armour class" type="int">
+    Doors of high &lt;armour class&gt; are less likely to get hit.
+    &lt;armour class&gt; can be considered the "counterpiece" to
+    &lt;weapon class&gt;.
+  </attribute>
+  <attribute arch="other_arch" editor="drop arch" type="string">
+    This string defines the object that will be created when the door was
+    defeated.
+  </attribute>
+  <attribute arch="randomitems" editor="treasurelist" type="treasurelist">
+    This entry determines what kind of traps will appear in the door.
   </attribute>
 </type>
 <!--####################################################################-->
 <type number="83" name="Duplicator">
     (Monsters cannot use exits.) Depending on how it is set, the player applies
     the exit just by walking into it, or by pressing &lt;a&gt;pply when standing on
     the exit.  ]]>
   </description>
   <use><![CDATA[
     If you want to have an invisible exit, set &lt;invisible&gt; (, of course
     &lt;apply by walking&gt;), and put it *under* the floor. Otherwise it could be
     detected with the show_invisible spell.
     <br><br>
     You can be quite creative with the outlook of secret exits (their "face").
     Don't forget to give the player relyable hints about them though. ]]>
     You can enter an absolute path, beginning with '/' (for example
     "/peterm/FireTemple/fire1"). It can also be a relative path, not beginning
     with '/' (On the map "/peterm/FireTemple/Fire2" for example I could use the
     relative path "Fire1"). Use relative paths whenever possible! Note that
     upper/lower case must always be set correctly. However, please use lower
     case only.
     It is well possible to have an exit pointing to the same map that the exit
     is on. If slaying is not set in an exit, the player will see a message like
     "the exit is closed".
   </attribute>
   <attribute arch="hp" editor="destination X" type="int">
     If both are set to zero, the player will be transferred to the "default
     enter location" of the destined map. The latter can be set in the map-
     properties as "Enter X/Y". Though, please DO NOT use that.
     It turned out to be a source for numerous map-bugs.
   </attribute>
-  <attribute arch="walk_on" editor="apply by walking" type="bool">
+  &move_on;
-    If set, the player will apply the exit by just walking into it. This must
-    be set for the invisible exits for example. If unset, the player has
-    to step onto the exit and press 'a' to get transferred.
-  </attribute>
-  <attribute arch="fly_on" editor="apply by flying" type="bool">
-    If set, the player will apply the exit by "flying into it". Flying means
-    the player is levitating. E.g. wearing levitation boots.
-  </attribute>
   <attribute arch_begin="msg" arch_end="endmsg" editor="exit message" type="text">
     If set, this message will be displayed to the player when he applies the exit.
     This is quite useful to throw in some "role-play feeling": "As you enter the
     dark cave you hear the sound of rustling dragonscales...". Well, my english
     is poor, but you get the point. =)
   <description><![CDATA[
     Just like with food, the player can fill his stomache and gain a
     little health by eating flesh-objects. <br>
     For dragon players, flesh plays a very special role though: If the
     flesh has resistances set, a dragon player has a chance to gain resistance in
-    those cathegories. The only constraint to this process is the &lt;flesh level&gt;.
+    those categories. The only constraint to this process is the &lt;flesh level&gt;.
     Don't forget that flesh items with resistances have to be balanced
     according to map/monster difficulty. ]]>
   </description>
   <use><![CDATA[
     For dragon players, flesh items can be highly valuable. Note that many
     Floor is a very basic thing whithout too much
     functionality. It's a floor - you stand on it. ]]>
   </description>
   <attribute arch="is_floor" value="1" type="fixed" />
   <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="no_pass" editor="blocking passage" type="bool">
-    If set, the object cannot be passed by players nor monsters.
-  </attribute>
 <section name="terrain">
-  <attribute arch="slow_move" editor="slow movement" type="int">
+  &movement_types_terrain;
-    If &lt;slow movement&gt; is set to a value greater zero, all
-    creatures moving over this spot will be slower than normal.
-    &lt;slow movement&gt; 1  - rough terrain
-    &lt;slow movement&gt; 2  - very rough terrain
-    ...
-    &lt;slow movement&gt; 7  - spider web (sticky as hell)
-  </attribute>
   <attribute arch="is_wooded" editor="wooded terrain" type="bool">
     This flag indicates this spot contains wood or high grass.
     Players with activated woodsman skill can move faster here.
   </attribute>
   <attribute arch="is_hilly" editor="hilly terrain" type="bool">
     with monsters on them. Nowadays this feature is disabled -
     Hence encounter floor is not different from normal floor. ]]>
   </description>
   <attribute arch="is_floor" value="1" type="fixed" />
   <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="no_pass" editor="blocking passage" type="bool">
-    If set, the object cannot be passed by players nor monsters.
-  </attribute>
 <section name="terrain">
-  <attribute arch="slow_move" editor="slow movement" type="int">
+  &movement_types_terrain;
-    If &lt;slow movement&gt; is set to a value greater zero, all
-    creatures moving over this spot will be slower than normal.
-    &lt;slow movement&gt; 1  - rough terrain
-    &lt;slow movement&gt; 2  - very rough terrain
-    ...
-    &lt;slow movement&gt; 7  - spider web (sticky as hell)
-  </attribute>
   <attribute arch="is_wooded" editor="wooded terrain" type="bool">
     This flag indicates this spot contains wood or high grass.
     Players with activated woodsman skill can move faster here.
   </attribute>
   <attribute arch="is_hilly" editor="hilly terrain" type="bool">
     The &lt;position state&gt; defines the position of the gate:
     Zero means completely open/down, the "number of animation-steps" (usually
     about 6 or 7) means completely closed/up state. I suggest you don't
     mess with this value - Leave the default in place.
   </attribute>
-  <attribute arch="no_pass" editor="blocking passage" type="bool">
+  &movement_types_terrain;
-    For open gates, &lt;blocking passage&gt; should be unset.
-    For closed gates it must be set.
-  </attribute>
   <attribute arch="no_magic" editor="restrict spells" type="bool">
     Restricting the use of spells to pass this gate. This has
     an effect only if &lt;block view&gt; is disabled.
   </attribute>
   <attribute arch="damned" editor="restrict prayers" type="bool">
   </use>
   <attribute arch="magic" editor="magic bonus" type="int">
     &lt;magic bonus&gt; works just like ac, except that it can be improved by
     "scrolls of Enchant Armour" or reduced by acid. It is less useful
     than direct armour-class bonus on the helmet.
     Important: &lt;magic bonus&gt; on girdles has no effect if there is no
     &lt;armour class&gt; set. Girdles shouldn't have &lt;armour class&gt;, thus
     &lt;magic bonus&gt; is pointless here.
   </attribute>
 </type>
     You can use that to safely chase off too-weak players, or just
     to have something different. ]]>
   </use>
   <attribute arch="is_floor" value="1" type="fixed" />
   <attribute arch="lifesave" value="1" type="fixed" />
-  <attribute arch="walk_on" value="1" type="fixed" />
+  &move_on;
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
     This attribute specifys the attacktypes that this floor uses to
     damage it's victims. Attacktypes are: physical, fire, cold.. etc.
     If you want a real tough hazard floor, add more than just one attacktype.
     I guess this value is supposed to work similar to monster levels.
     But in fact, it does not seem to have an effect. Set any non-zero
     value to be on the safe side.
   </attribute>
 <section name="terrain">
-  <attribute arch="slow_move" editor="slow movement" type="int">
+  &movement_types_terrain;
-    If &lt;slow movement&gt; is set to a value greater zero, all
-    creatures moving over this spot will be slower than normal.
-    &lt;slow movement&gt; 1  - rough terrain
-    &lt;slow movement&gt; 2  - very rough terrain
-    ...
-    &lt;slow movement&gt; 7  - spider web (sticky as hell)
-  </attribute>
   <attribute arch="is_wooded" editor="wooded terrain" type="bool">
     This flag indicates this spot contains wood or high grass.
     Players with activated woodsman skill can move faster here.
   </attribute>
   <attribute arch="is_hilly" editor="hilly terrain" type="bool">
   </use>
   <attribute arch="magic" editor="magic bonus" type="int">
     &lt;magic bonus&gt; works just like ac, except that it can be improved by
     "scrolls of Enchant Armour" or reduced by acid. It is less useful
     than direct armour-class bonus on the helmet.
     Important: &lt;magic bonus&gt; on helmets has no effect if there is no
     &lt;armour class&gt; set. It only works in combination with &lt;armour class&gt;.
     Crowns for instance typically provide no &lt;amour class&gt;.
   </attribute>
 </type>
   </description>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="other_arch" editor="god name" type="string">
     The altar belongs to the god of the given name. Possible options for
     &lt;god name&gt; are: Devourers, Lythander, Mostrai, Gaea, Ruggilli, Gnarg,
     Gorokh, Valriel and Sorig.
     If you want to have an unconsecrated altar, set
     &lt;god name&gt; 0 and eventually &lt;reconsecrate level&gt; 0.
   </attribute>
   <attribute arch="level" editor="reconsecrate level" type="int">
     To re-consecrate an altar, the player's wisdom level must be as
     high or higher than this value. In that way, some altars can not
     be re-consecrated, while other altars, like those in dungeons, could be.
     Altars located in temples should have at least &lt;reconsecrate level&gt; 100.
     Some characters might need those altars, they would be very unhappy to
     see them re-consecrated to another cult.
   </attribute>
 </type>
     either if that object is present or missing (-&gt; "last_sp") when a
     player walks over the inv. checker. A valid option is to remove the
     matching object (usually not recommended, see "last_heal").
     <br><br>
     Alternatively, you can set your inv. checker to block all players
-    that do/don't carry the matching object (-&gt; "no_pass").
+    that do/don't carry the matching object.
     <br><br>
     As you can see, inv. checkers are quite powerful, holding a
     great variety of possibilities. ]]>
   </description>
   <use><![CDATA[
     This string specifies the object we are looking for: We have a match
     if the player does/don't carry an object of archtype &lt;match arch name&gt;.
   </attribute>
   <attribute arch="hp" editor="match type" type="int">
     This value specifies the object we are looking for: We have a match
     if the player does/don't carry an object that is of type &lt;match type&gt;.
     Example: Set &lt;match type&gt; 15 (type 15 =&gt; weapon) and &lt;blocking passage&gt;
     enabled. Now you have an inv. checker blocking all players that carry any
     kind of melee weapon. To pass, a player is forced to leave behind all
     his weaponry... bad news for a warrior. ;)
   </attribute>
   <attribute arch="connected" editor="connection" type="int">
     Whenever the inventory checker is triggered, all objects with identical
     &lt;connection&gt; value get activated. This only makes sense together with
     &lt;blocking passage&gt; disabled.
   </attribute>
-  <attribute arch="no_pass" editor="blocking passage" type="bool">
+  &movement_types_terrain;
-    If set, only players meeting the match criteria can pass
-    through that space. If unset (default), the inventory
-    checker acts like a trigger/button.
-  </attribute>
   <attribute arch="last_heal" editor="remove match" type="bool">
     &lt;remove match&gt; means remove object if found. Setting this is usually not
     recommended because inv. checkers are in general invisible. So, unlike
     for altars/ locked doors, the player won't expect to lose an object when
     walking over that square. And he doesn't even get a message either.
     So, *if* you enable &lt;remove match&gt;, make sure
     to inform the player what's going on!
   </attribute>
 </type>
     This text may describe the object.
   </attribute>
 </type>
 <!--####################################################################-->
+<type number="24" name="Key">
+  <description><![CDATA[
+    When carrying a key, a normal door can be opened. The key will
+    disappear. ]]>
+  </description>
+  <attribute arch="startequip" editor="godgiven item" type="bool">
+    A godgiven item vanishes as soon as the player
+    drops it to the ground.
+  </attribute>
+</type>
+<!--####################################################################-->
 <type number="20" name="Locked Door">
   <ignore>
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     the appropriate special key. ]]>
   </description>
   <use><![CDATA[
     If you want to create a locked door that cannot be opened (no key),
     set a &lt;key string&gt; like "no_key_available". This will clearify things
     and only a fool would create a key matching that string.
     Door-objects can not only be used for "doors". In many maps these
     are used with all kinds of faces/names, especially often as
     "magic force". A good example is the map "Lake_Country/ebony/masterlev".
     There you have magic forces (door objects) put under certain artifact
     items. To get your hands on the artifacts, you need to bring up the
     appropriate quest items (key objects). ]]>
   </use>
-  <attribute arch="no_pass" value="1" type="fixed" />
+  <attribute arch="move_type" value="0" type="fixed" />
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="slaying" editor="key string" type="string">
     The &lt;key string&gt; in the door must be identical with the
     &lt;key string&gt; in the special key, then the door is unlocked.
     It is VERY important to set the &lt;key string&gt; to something that
     is unique among the CF mapset.
     DONT EVER USE the default string "set_individual_value".
   </attribute>
   <attribute arch="no_magic" editor="restrict spells" type="bool">
     Restricting the use of spells to pass this door.
     This should be set in most cases.
   <attribute arch_begin="msg" arch_end="endmsg" editor="keyword-matching" type="text">
     This textfield contains the keyword-matching-syntax. The text should
     have the following format: "@match &lt;keyword1&gt;|&lt;keyword2&gt;|... ".
     Any number of keywords from one to infinite is allowed. Make sure
     they are seperated by a '|'.
     Examples: "@match yes", "@match gold|treasure". The connected
     value will be triggerd when the player speaks any of the given
     keywords within a two-square radius. IMPORTANT: Upper/lower case
     does not make a difference!
   </attribute>
     The &lt;casting speed&gt; defines the spellcasting speed of the wall.
     You can fine-tune how long the duration between two casts shall
     be. If you want to create a wall that can be activated (cast per
     trigger) via connected lever/button/etc, you must set "speed 0".
   </attribute>
+  &speed_left;
   <attribute arch="sp" editor="direction" type="list_direction">
     The magic wall will cast it's spells always in the specified
     &lt;direction&gt;. A magic wall with direction set to &lt;none&gt; will
     always fire in a random direction.
   </attribute>
-  <attribute arch="no_pass" editor="blocking passage" type="bool">
+  &movement_types_terrain;
-    If set, the object cannot be passed by players nor monsters.
-  </attribute>
 <section name="destroyable">
   <attribute arch="alive" editor="is destroyable" type="bool">
     Walls with &lt;is destroyable&gt; enabled can be attacked and (eventually)
     destroyed by the player. If disabled, all other attributes on
     this tab, as well as resistances, are meaningless.
     The &lt;marking speed&gt; defines how quickly it will mark something
     standing on the marker. Set this value rather high to make
     sure the player really gets his mark. I think &lt;marking speed&gt; 1.0
     should do fine.
   </attribute>
+  &speed_left;
   <attribute arch="food" editor="mark duration" type="int">
     This value defines the duration of the force it inserts.
     If nonzero, the duration of the player's mark is finite:
     about 1 food per 10 seconds. &lt;mark duration&gt; zero/unset
     means the mark will stay on the player forever.
   </attribute>
   <attribute arch="name" editor="delete mark" type="string">
     When the player steps onto the marker, all existing forces in
     the players inventory with a &lt;key string&gt; matching &lt;delete mark&gt;
     will be removed. If you don't want to remove any marks, leave
     this textfield empty.
     Note that the string &lt;delete mark&gt; is set as the name of
     this marker. So don't be confused, and remember changing the
     name will take effect on the marker's functionality.
   </attribute>
   <attribute arch_begin="msg" arch_end="endmsg" editor="marking message" type="text">
     In the moment when the player gets marked, this text is displayed
     to him. You should really set a message in any marker you create,
     because it's the only way for the player to notice what's going on.
   </attribute>
 </type>
-<!--####################################################################-->
-<type number="26" name="Timed Gate">
-  <ignore>
-    <ignore_list name="non_pickable" />
-  </ignore>
-  <description><![CDATA[
-    Gates play an important role in Crossfire. Gates can be opened
-    by activating a button/trigger, by speaking passwords (-> magic_ear)
-    or carrying special key-objects (-> inventory checker).
-    Unlike locked doors, gates can get shut again after a player has
-    passed, which makes them more practical in many cases. Unlike normal
-    gates, timed gates open when triggered but automatically close again
-    after some time.]]>
-  </description>
-  <use><![CDATA[
-    Use gates to divide your maps into separated areas. After solving
-    area A, the player gains access to area B, and so on. Make your
-    maps more complex than "one-way". ]]>
-  </use>
-  <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="connected" editor="connection" type="int">
-    Whenever the inventory checker is triggered, all objects with identical
-    &lt;connection&gt; value get activated. This only makes sense together with
-    &lt;blocking passage&gt; disabled. If unset, the gate opens automatically
-    after some time.
-  </attribute>
-  <attribute arch="wc" editor="position state" type="int">
-    The &lt;position state&gt; defines the position of the gate:
-    Zero means completely open/down, the "number of animation-steps" (usually
-    about 6 or 7) means completely closed/up state. I suggest you don't
-    mess with this value - Leave the default in place.
-  </attribute>
-  <attribute arch="no_pass" editor="blocking passage" type="bool">
-    For open gates, &lt;blocking passage&gt; should be unset.
-    For closed gates it must be set.
-  </attribute>
-  <attribute arch="no_magic" editor="restrict spells" type="bool">
-    Restricting the use of spells to pass this gate. This has
-    an effect only if &lt;block view&gt; is disabled.
-  </attribute>
-  <attribute arch="damned" editor="restrict prayers" type="bool">
-    Restricting the use of prayers to pass this door. This has
-    an effect only if &lt;block view&gt; is disabled.
-  </attribute>
-  <attribute arch="hp" editor="open duration" type="int">
-    Defines the duration the gate remains closed. This only takes effect
-    if the gate is not connected.
-  </attribute>
-</type>
-<!--####################################################################-->
-<type number="52" name="Trigger Marker">
-  <ignore>
-    <ignore_list name="system_object" />
-  </ignore>
-  <description><![CDATA[
-    A trigger marker is an object that inserts an invisible force (a mark) into a
-    player stepping on it WHEN TRIGGERED. This force does nothing except containing a
-    &lt;key string&gt; which can be discovered by detectors or inventory
-    checkers. It is also possible to use markers for removing marks again.
-    <br><br>
-    Note that the player has no possibility to "see" his own marks,
-    except by the effect that they cause on the maps. ]]>
-  </description>
-  <use><![CDATA[
-    Markers hold real cool possibilities for map-making. I encourage
-    you to use them frequently. However there is one negative point
-    about markers: Players don't "see" what's going on with them. It is
-    your task, as map-creator, to make sure the player is always well
-    informed and never confused.
-    <br><br>
-    Please avoid infinite markers when they aren't needed. They're
-    using a little space in the player file after all, so if there
-    is no real purpose, set an expire time. ]]>
-  </use>
-  <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="slaying" editor="key string" type="string">
-    The &lt;key string&gt; can be detected by inv. checkers/detectors.
-    If the player already has a force with that &lt;key string&gt;,
-    there won't be inserted a second one.
-  </attribute>
-  <attribute arch="connected" editor="connection" type="int">
-   Unlike a regular marker this is the connection that triggers this marker to activate.
-  </attribute>
-  <attribute arch="food" editor="mark duration" type="int">
-    This value defines the duration of the force it inserts.
-    If nonzero, the duration of the player's mark is finite:
-    about 1 food per 10 seconds. &lt;mark duration&gt; zero/unset
-    means the mark will stay on the player forever.
-  </attribute>
-  <attribute arch="name" editor="delete mark" type="string">
-    When the player steps onto the marker, all existing forces in
-    the players inventory with a &lt;key string&gt; matching &lt;delete mark&gt;
-    will be removed. If you don't want to remove any marks, leave
-    this textfield empty.
-    Note that the string &lt;delete mark&gt; is set as the name of
-    this marker. So don't be confused, and remember changing the
-    name will take effect on the marker's functionality.
-  </attribute>
-  <attribute arch_begin="msg" arch_end="endmsg" editor="marking message" type="text">
-    In the moment when the player gets marked, this text is displayed
-    to him. You should really set a message in any marker you create,
-    because it's the only way for the player to notice what's going on.
-  </attribute>
-</type>
 <!--####################################################################-->
 <type number="36" name="Money">
   <ignore>
     <attribute arch="unpaid" />
   </ignore>
          It's no fun to play for two hours just to find out the last
          monster is unbeatable. Similar, it's not exciting to fight orcs
          after passing a room of dragons.<br>
          This rule applies only for linear maps (one room after the other),
          with treasure at the end. You can sprinkle the treasure around,
          or make non-linear maps - That is often more entertaining.
     <LI> Places with high level monsters must not be easy to reach.
          Balrogs, Dragonmen and the likes should be at the end of a quest,
          not at the beginning.
     <LI> Don't stick monsters together that tend to kill each other.
          Fire- and cold dragons in one room for example is a bad idea.
          By weakening and killing each other they are easy prey for players,
          not worth the experience they hold.
     <LI> Create your own monsters, especially for "boss"-type monsters.
   <attribute arch="alive" value="1" type="fixed" />
   <attribute arch="randomitems" editor="treasurelist" type="treasurelist">
     When the monster is killed, items from the treasurelist will
     drop to the ground. This is a common way to reward players
     for killing (masses of) monsters.
     Note that you can always put items into the monster's
     inventory. Those will drop-at-kill just like the stuff
     from the &lt;treasurelist&gt;.
   </attribute>
   <attribute arch="level" editor="level" type="int">
     A monster's &lt;level&gt; is the most important attribute.
     &lt;level&gt; affects the power of a monster in various ways.
   </attribute>
   <attribute arch="race" editor="race" type="string">
-    Every monster should have a race set to cathegorize it.
+    Every monster should have a race set to categorize it.
     The monster's &lt;race&gt; can have different effects:
     Slaying weapons inflict tripple damage against enemy races
     and holy word kills only enemy races of the god.
   </attribute>
   <attribute arch="exp" editor="experience" type="int">
     When a player kills this monster, he will get exactly this
     amount of &lt;experience&gt;. The experience will flow into
-    the skill-cathegory the player used for the kill.
+    the skill-category the player used for the kill.
     If you create special monsters of tweaked strenght/abilities,
     always make sure that the &lt;experience&gt; is set to a
     reasonable value. Compare with existing arches to get a feeling
     what reasonable means. Keep in mind that spellcasting monsters
     are a lot harder to kill than non-spellcasters!
   </attribute>
   <attribute arch="speed" editor="speed" type="float">
     The &lt;speed&gt; determines how fast a monster will both move
     and fight. High &lt;speed&gt; makes a monster considerably stronger.
   </attribute>
+  &speed_left;
   <attribute arch="other_arch" editor="breed monster" type="string">
     This only takes effect if &lt;multiply&gt; is enabled. The monster will
     create a &lt;breed monster&gt; every once in a while. &lt;breed monster&gt;
     can be set to any valid arch-name of a monster. Multipart monster
     should not be used.
     This only takes effect if &lt;multiply&gt; is enabled. The monster
     will create a new monster every once in a while by duplicating it's inventory.
     In this case, the &lt;breed monster&gt; value is never used and can be forgotten.
     Each time the monster need to generate an object, it will be
     a randomly chosen item from the inventory. When generator is destroyed,
     inventory is destroyed.
   </attribute>
-  <attribute arch="flying" editor="flying" type="bool">
+  &move_type;
-    Flying monsters won't get slowed down in rough terrain
-    and they won't be affected by movers.
-  </attribute>
   <attribute arch="undead" editor="undead" type="bool">
     Several spells only affect undead monsters:
     turn undead, banish undead, holy word, etc.
   </attribute>
   <attribute arch="carrying" editor="carries weight" type="int">
     If a monster has something in the inventory, this
     value can be set to reflect the slowdown due to
     the carried weight.
   </attribute>
 <section name="melee">
   <attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
     This number is a bitmask, specifying the monster's attacktypes
     for melee damage. Attacktypes are: physical, magical, fire, cold.. etc.
     Strong monsters often have more than just physical attacktype.
     When a monster with multiple attacktypes hits aan oponent, it will do
     as much damage as the "best" of it's attacktypes does. So, the more
     attacktypes, the more dangerous. Attacktypes "magic" and "chaos" are
     somehow exceptions.
   </attribute>
   <attribute arch="one_hit" editor="one hit only" type="bool">
     Monsters with &lt;one hit only&gt; dissapear after one successful hit
     to a player.
   </attribute>
 </section>
 <section name="spellcraft">
   <attribute arch="can_cast_spell" editor="can cast spell" type="bool">
     If &lt;can cast spell&gt; is disabled, the monster cannot cast any spell.
     Only wands/rods/etc can be used, given the appropriate abilities.
   </attribute>
   <attribute arch="reflect_spell" editor="reflect spells" type="bool">
     A monster with this flag has the ability to &lt;reflect spells&gt;,
     all kinds of spell-bullets and -beams will bounce off.
     Generally this flag should not be set because it puts
     wizard-type players at an unfair disadvantage.
   </attribute>
   <attribute arch="sp" editor="spellpoints" type="int">
     Like players, monsters need &lt;spellpoints&gt; to do magic. Monsters use
     "regenerate mana" at it's disposal.
   </attribute>
   <attribute arch="Pow" editor="spellpoint regen." type="int">
     Monsters regenerate this many spellpoints each 16 ticks. Hence, the
     spellpoint regeneration rate is independent of &lt;speed&gt;.
     To make a real tough spellcasting monster, the rate of spellpoint
     regeneration is most important. If your monster is still not casting
     fast enough, give it the spell-ability of "regenerate mana".
     That, paired with high &lt;max spellpoints&gt;, is the ultimate thing.
   </attribute>
   <attribute arch="path_denied" editor="denied paths" type="bitmask_spellpath">
     Click on the &lt;denied paths&gt; button to select spellpaths.
     The creature won't be able to cast spells of the specified paths.
   </attribute>
 </section>
 <section name="ability">
   <attribute arch="Int" editor="detect hidden" type="int">
     The &lt;detect hidden&gt; value gives monsters the ablitity to find
     hidden/invisible creatures. Higher values make for better
     detection-skills. Enabling &lt;see invisible&gt; makes this value
     Monster is able to read scrolls.
   </attribute>
   <attribute arch="can_use_skill" editor="can use skills" type="bool">
     Monster is able to use skills from it's inventory.
     For example, you can put a throwing skill object and some
     boulders into the monster's object and set &lt;can use skills&gt;.
   </attribute>
 </section>
 <section name="behave">
   <attribute arch="monster" editor="monster behaviour" type="bool">
     When &lt;monster behaviour&gt; is enabled, this object will behave
     like a monster: It can move and attack enemies (which are
     typically players).
     This flag should be set for all monsters as-such.
     Monsters which don't move, like guards, should also have
     &lt;monster behaviour&gt;, but in combination with &lt;stand still&gt;.
     It should *not* be set for things like immobile generators.
   </attribute>
   <attribute arch="unaggressive" editor="unaggressive" type="bool">
     &lt;unaggressive&gt; monsters do not attack players unless attacked first.
   </attribute>
   <attribute arch="friendly" editor="friendly" type="bool">
   </attribute>
   <attribute arch="stand_still" editor="stand still" type="bool">
     Monsters which &lt;stand still&gt; won't move to leave their position.
     When agressive, they will attack all enemies who get close to
     them. This behaviour is commonly known from castle guards.
     In older versions of Crossfire it was possible to eventually
     push a &lt;stand still&gt;-monster out of position by force.
     I believe this is no longer possible. Neverthless, you should
     still be cautious when lining up &lt;stand still&gt;-monster in order
     to "defend" something: Such monsters are rather easy to kill.
     creature is able to perform.
   </attribute>
   <attribute arch="pick_up" editor="pick up" type="bitmask_pick_up">
     Click on the &lt;pick up&gt; button and select which types of objects
     the creature should try to pick up.
     Note also that if &lt;can use armor&gt;, &lt;can use weapon&gt;, &lt;can use ring&gt;...
     etc are set, then the creature will pick up the matching items even
     if this is not set here.
   </attribute>
   <attribute arch="Wis" editor="sensing range" type="int">
     the creature wakes up. This is done as a square, for reasons of speed.
     Thus, if the &lt;sensing range&gt; is 11, any player that moves within the
     11x11 square of the monster will wake the monster up. If the player
     has stealth, the size of this square is reduced in half plus 1.
   </attribute>
-  <attribute arch="attack_movement" editor="attack movement" type="int">
+  <attribute arch="attack_movement_bits_0_3" editor="attack movement" type="list_attack_movement_bits_0_3">
+    If this is set to default, the standard mode of movement will be used.
+  </attribute>
+  <attribute arch="attack_movement_bits_4_7" editor="normal movement" type="list_attack_movement_bits_4_7">
+    This movement is not in effect when the monster has an enemy and should
+    only be used for non agressive monsters.
   </attribute>
   <attribute arch="run_away" editor="run at % health" type="int">
     This is a percentage value in the range 0-100.
     When the monster's health points drop below this percentage
     (relative to max health), it attempts to run away from the
     attacker.
   </attribute>
 </section>
 <section name="resistance">
   <attribute arch="resist_physical" editor="resist physical %" length="15" type="int">
   </attribute>
   <attribute arch="resist_magic" editor="resist magic %" length="15" type="int">
   </attribute>
   <attribute arch="resist_godpower" editor="resist godpower %" length="15" type="int">
   </attribute>
 </section>
   <attribute arch_begin="msg" arch_end="endmsg" editor="npc message" type="text">
   </attribute>
+</type>
+<!--####################################################################-->
+<type number="28" name="Monster (Grimreaper)">
+  <import_type name="Monster &amp; NPC" />
+  <ignore>
+    <attribute arch="material" />
+    <attribute arch="name_pl" />
+    <attribute arch="nrof" />
+    <attribute arch="value" />
+    <attribute arch="unpaid" />
+  </ignore>
+  <description><![CDATA[
+    A grimreaper is a monster that vanishes after it did some number of
+    draining attacks. ]]> <!-- XXX: is this ok? -->
+  </description>
+<section name="grimreaper">
+  <attribute arch="value" editor="attacks" type="int">
+    The object vanishes after this number of draining attacks.
+  </attribute>
+</section>
 </type>
 <!--####################################################################-->
 <type number="65" name="Mood Floor">
   <ignore>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="last_sp" editor="mood" type="list_mood">
     &lt;mood&gt; is used to determine what will happen to the
     monster when affected by the mood floor:
     &lt;mood&gt; 'furious': Makes all monsters aggressive
     &lt;mood&gt; 'angry': As above but pets are unaffected
     &lt;mood&gt; 'calm': Makes all monsters unaggressive
     &lt;mood&gt; 'sleep': Puts all monsters to sleep
     &lt;mood&gt; 'charm': Turns monster into a pet of person
                     who triggers the square. This setting is not
                     enabled for continous operation, you need to
                     insert a &lt;connection&gt; value!
   </attribute>
   <attribute arch="connected" editor="connection" type="int">
     This should only be set in combination with &lt;mood number&gt; 4.
     Normally, monsters are affected by the mood floor as soon as they
     step on it. But charming (monster -&gt; pet) is too powerful,
     so it needs to be activated.
     Typically it is connected to an altar, for buying a "hireling".
     But a powerful pet could as well be the reward for solving a
     quest. Or even better: It could be *part* of a quest!
   </attribute>
   <attribute arch="no_magic" editor="no spells" type="bool">
   </attribute>
   <attribute arch="speed" editor="movement speed" type="float">
     The movement speed value determines how fast a chain of
     these movers will push a player along (default is -0.2).
   </attribute>
+  &speed_left;
   <attribute arch="sp" editor="direction" type="list_direction">
     The mover will push creatures in the specified &lt;direction&gt;.
     A mover with direction set to &lt;none&gt; will spin clockwise,
     thus pushing creatures in unpredictable directions.
   </attribute>
   <attribute arch="lifesave" editor="gets used up" type="bool">
     If enabled, the mover gets "used up" after a certain number of moves
-    (specified by &lt;number of uses&gt;). If disabled, the mover works infinitly.
+    (specified by &lt;number of uses&gt;). If disabled, the mover works infinitely.
   </attribute>
   <attribute arch="hp" editor="number of uses" type="int">
     This value has only a meaning if &lt;gets used up&gt; is set:
     &lt;number of uses&gt; is the number of times minus one, that it
     will move a creature before disappearing. (It will move
     someone &lt;number of uses&gt;+1 times, then vanish).
   </attribute>
 <section name="targets">
   <attribute arch="level" editor="move players" type="bool">
     If &lt;move players&gt; is enabled, both players and monsters will be
     moved. In the arches' default it is disabled - thus ONLY monsters
     get moved. Remember that "monsters" includes NPCs!
     This feature provides you with the possibility to make NPCs
     literally "come to life". Example: The player is talking with an
     NPC, speaking a certain keyword. This triggers a magic_ear and
     activates creators, creating (per default: monster-only) movers
     under the NPC's feet. The NPC starts "walking" on a predefined
     route! Note that it's useful to set this NPC immune to everything,
     preventing the player to push the NPC off his trace.
   </attribute>
-  <attribute arch="walk_on" editor="move walking creatures" type="bool">
+  <attribute arch="move_on" editor="movement type" type="movement_type">
-    This should always be set.
+     Which movement types activate the mover.
-  </attribute>
-  <attribute arch="fly_on" editor="move flying creatures" type="bool">
-    Move flying creatures enabled means all flying (living)
-    objects will get moved too. If disabled, only walking
-    (non-flying) creatures will get moved.
   </attribute>
 </section>
 </type>
 <!--####################################################################-->
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="slaying" editor="match race" type="string">
     the &lt;match race&gt; defines the object we're looking for. If &lt;match race&gt;
     matches the monster's or the player's race, we have a match.
     Yes, pedestals can detect a player's race! E.g. you could create a
     place where only fireborns can enter, by setting "slaying unnatural".
     If it is set to "player", any player stepping on the pedestal
     is a match. Very useful if you want to open a gate for players
     but not for monsters.
   </attribute>
   <attribute arch="connected" editor="connection" type="int">
     When the pedestal is triggered, all objects with the same
     connection value get activated.
   </attribute>
-  <attribute arch="walk_on" value="1" type="fixed" />
+  &move_on;
-  <attribute arch="walk_off" value="1" type="fixed" />
 </type>
 <!--####################################################################-->
 <type number="94" name="Pit">
   <ignore>
     The &lt;position state&gt; defines the position of the gate:
     Zero means completely open/down, the "number of animation-steps" (usually
     about 6 or 7) means completely closed/up state. I suggest you don't
     mess with this value - Leave the default in place.
   </attribute>
-  <attribute arch="walk_on" editor="swallow walking" type="bool">
+  &move_on;
-    If set, all walking creatures will fall into the pit.
-    This does NOT need to be set for closed pits!
-  </attribute>
-  <attribute arch="fly_on" editor="swallow flying" type="bool">
-    If set, all flying creatures will fall into the pit as well.
-    This is not the behaviour expected from a pit, and it should
-    only be used for map-mechanisms (e.g. for transporting flying
-    monsters).
-    An interesting side-effect: If this flag is enabled, spell
-    effects like fire/snow also make their way through the pit.
-  </attribute>
 </type>
 <!--####################################################################-->
 <type number="7" name="Poison Food">
   <description><![CDATA[
   </attribute>
   <attribute arch="attacktype" editor="special effect" type="list_potion_effect">
     There are two types of special effects for potions:
     'life restoration' - restore the player's stats lost by death or draining
                     (this has nothing in common with the restoration spell!)
     'improvement' - increase the player's maximum health/mana/grace
                     by a very small amount.
   </attribute>
   <attribute arch="cursed" editor="cursed" type="bool">
     If a potion is cursed, benefits generally turn into penalties.
     Note that potions can be "uncursed" by praying over an altar,
     weapon and projectile. ]]>
   </description>
   <use><![CDATA[
     If you want to create new kinds of projectiles, you could
     add an alchemical receipe to create these.
     Don't create new pairs of weapons &amp; projectiles unless
     they really fullfill a useful purpose. In fact, even bows
     and crossbows are rarely ever used. ]]>
   </use>
   <attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
   </attribute>
   <attribute arch="race" editor="ammunition class" type="string">
     Only shooting weapons with matching &lt;ammunition class&gt; can fire
     these projectiles. For arrows set "arrows", for crossbow bolts
     set "crossbow bolts" (big surprise).
     In certain cases, the ammunition class is displayed in the game.
     Hence, when you create a new ammunition class, choose an
     intuitive name like "missiles", "spirit bolts" - whatever.
     You can also make special containers holding these projectiles
     by setting the &lt;container class&gt; to match your &lt;ammunition class&gt;.
   </attribute>
   <attribute arch="slaying" editor="slaying race" type="string">
     Slaying means the weapon does tripple (3x) damage to monsters
     <attribute arch="value" />
     <attribute arch="material" />
     <attribute arch="unpaid" />
   </ignore>
   <description><![CDATA[
     A rune is a magical enscription on the dungeon floor.
     <br><br>
     Runes hit any monster or person who steps on them for 'dam' damage in
     'attacktype' attacktype. Alternatively, the rune could contain any spell,
     and will cast this spell when it detonates. Yet another kind is the
     "summoning rune", summoning predefined monsters of any kind, at detonation.
   <use><![CDATA[
     Avoid monsters stepping on your runes. For example, summoning runes
     together with spellcasting- and  attack-runes is usually a bad idea. ]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="walk_on" value="1" type="fixed" />
+  &move_on;
   <attribute arch="level" editor="rune level" type="int">
     This value sets the level the rune will cast the spell it contains at,
     if applicable. A level 99 rune casts a very, very mean spell of whatever.
     (&lt;rune level&gt; 0 runes won't detonate at all!)
     Level Also effects how easily a rune may be found and disarmed, and
     how much experience the player gets for doing so. Beware: High level
     runes can be quite a cheap source of experience! So either make them
     tough, or keep the level low.
   </attribute>
     The rune will detonate &lt;number of charges&gt; times before disappearing.
   </attribute>
   <attribute arch="dam" editor="direct damage" type="int">
     &lt;direct damage&gt; specifies how much damage is done by the rune,
     if it doesn't contain a spell. This should be set in reasonable
     relation to the rune's level.
   </attribute>
   <attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
     If there isn't any spell (and &lt;summon monster&gt; is unset), this
     attribute defines what attacktype to use for direct damage when
     the rune detonates.
   <attribute arch="no_magic" value="1" type="fixed" />
   <attribute arch="damned" value="1" type="fixed" />
 </type>
 <!--####################################################################-->
+<type number="111" name="Scroll">
+  <ignore>
+    <attribute arch="title" />
+  </ignore>
+  <description><![CDATA[
+    Scrolls contain spells (similar to spell-potions). Unlike potions,
+    scrolls require a certain literacy skill to read successfully.
+    Accordingly, for a successful reading, a small amount of
+    experience is gained. Scrolls allow only one time usage, but
+    usually they are sold in bulks. ]]>
+  </description>
+  <use><![CDATA[
+    For low level quests, scrolls of healing/curing-spells
+    can be a nice reward. At higher levels, scrolls become less
+    and less useful. ]]>
+  </use>
+  <attribute arch="level" editor="casting level" type="int">
+    The spell of the scroll will be casted at this level.
+    This value should always be set, at least to 1.
+  </attribute>
+  <attribute arch="sp" editor="spell" type="spell">
+    When a player/monster applies this scroll, the selected &lt;spell&gt;
+    will be casted (once). This should work for any given spell.
+  </attribute>
+  <attribute arch="startequip" editor="godgiven item" type="bool">
+    A godgiven item vanishes as soon as the player
+    drops it to the ground.
+  </attribute>
+</type>
+<!--####################################################################-->
+<type number="33" name="Shield">
+  <import_type name="Amulet" />
+  <description><![CDATA[
+    Wearing a shield, the object's stats will directly be inherited to
+    the player. Shields usually provide good defense, only surpassed
+    by brestplate armour. Resistances on shields aren't uncommon either. ]]>
+  </description>
+  <use><![CDATA[
+    Feel free to create your own special artifacts. However, it is very
+    important that you keep your artifact in balance with existing maps. ]]>
+  </use>
+  <attribute arch="magic" editor="magic bonus" type="int">
+    &lt;magic bonus&gt; works just like ac, except that it can be improved by
+    "scrolls of Enchant Armour" or reduced by acid. It is less useful
+    than direct armour-class bonus on the shield.
+  </attribute>
+</type>
+<!--####################################################################-->
 <type number="14" name="Shooting Weapon">
   <description><![CDATA[
     Schooting weapons like bows/crossbows are used to shoot projectiles
     (arrows/bolts). Shooting weapons and normal (melee) weapons can be
     wielded both at the same time. Like with any other equipment,
   </use>
   <attribute arch="race" editor="ammunition class" type="string">
     Only projectiles with matching &lt;ammunition class&gt; can be fired
     with this weapon. For normal bows set "arrows", for normal
     crossbows set "crossbow bolts".
     In certain cases, the ammunition class is displayed in the game.
     Hence, when you create a new ammunition class, choose an
     intuitive name like "missiles", "spirit bolts" - whatever.
   </attribute>
   <attribute arch="sp" editor="shooting speed" type="int">
     After shooting a projectile, the player is frozen for a short
     period of time (to prevent shooting arrows machine-gun-like).
     The greater &lt;shooting speed&gt;, the shorter this period of time.
     1 is minimum (=worst) and 100 is maximum (=best) value.
     You shouldn't set &lt;shooting speed&gt; lower than 10. YOU MUST NOT
     SET IT TO ZERO! (That would freeze the player for eternety).
   </attribute>
   <attribute arch="dam" editor="base damage" type="int">
     The &lt;base damage&gt; significantly affects the damage done
     The &lt;item power&gt; value measures how "powerful" an artifact is.
     Players will only be able to wear equipment with a certain total
     amount of &lt;item power&gt;, depending on their own level. This is the
     only way to prevent low level players to wear "undeserved" equipment
     (like gifts from other players or cheated items).
     It is very important to adjust the &lt;item power&gt; value carefully
     for every artifact you create! If zero/unset, the CF server will
     calculate a provisional value at runtime, but this is never
     going to be an accurate measurement of &lt;item power&gt;.
   </attribute>
     should have such a description.
   </attribute>
 </type>
 <!--####################################################################-->
-<type number="111" name="Scroll">
-  <ignore>
-    <attribute arch="title" />
-  </ignore>
-  <description><![CDATA[
-    Scrolls contain spells (similar to spell-potions). Unlike potions,
-    scrolls require a certain literacy skill to read successfully.
-    Accordingly, for a successful reading, a small amount of
-    experience is gained. Scrolls allow only one time usage, but
-    usually they are sold in bulks. ]]>
-  </description>
-  <use><![CDATA[
-    For low level quests, scrolls of healing/curing-spells
-    can be a nice reward. At higher levels, scrolls become less
-    and less useful. ]]>
-  </use>
-  <attribute arch="level" editor="casting level" type="int">
-    The spell of the scroll will be casted at this level.
-    This value should always be set, at least to 1.
-  </attribute>
-  <attribute arch="sp" editor="spell" type="spell">
-    When a player/monster applies this scroll, the selected &lt;spell&gt;
-    will be casted (once). This should work for any given spell.
-  </attribute>
-  <attribute arch="startequip" editor="godgiven item" type="bool">
-    A godgiven item vanishes as soon as the player
-    drops it to the ground.
-  </attribute>
-</type>
-<!--####################################################################-->
-<type number="33" name="Shield">
-  <import_type name="Amulet" />
-  <description><![CDATA[
-    Wearing a shield, the object's stats will directly be inherited to
-    the player. Shields usually provide good defense, only surpassed
-    by brestplate armour. Resistances on shields aren't uncommon either. ]]>
-  </description>
-  <use><![CDATA[
-    Feel free to create your own special artifacts. However, it is very
-    important that you keep your artifact in balance with existing maps. ]]>
-  </use>
-  <attribute arch="magic" editor="magic bonus" type="int">
-    &lt;magic bonus&gt; works just like ac, except that it can be improved by
-    "scrolls of Enchant Armour" or reduced by acid. It is less useful
-    than direct armour-class bonus on the shield.
-  </attribute>
-</type>
-<!--####################################################################-->
 <type number="68" name="Shop Floor">
   <ignore>
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
   <use><![CDATA[
     As stated above, always place TWO shop mats into your shop.
     Not more and not less than that. ]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="walk_on" editor="apply by walking" type="bool">
+  &move_on;
-    If set, the player can enter/leave the
-    shop by just walking into the shop mat.
-  </attribute>
-  <attribute arch="fly_on" editor="apply by flying" type="bool">
-    If set, the player can enter/leave the
-    shop by "flying" into the shop mat.
-  </attribute>
 </type>
 <!--####################################################################-->
 <type number="98" name="Sign &amp; MagicMouth">
   <ignore>
     the connection is triggered. This should be used in combination with
     &lt;invisible&gt; enabled and &lt;activate by walking/flying&gt; disabled.
     If activating your magic_mouth this way, the message will not only be
     printed to one player, but all players on the current map.
   </attribute>
-  <attribute arch="walk_on" editor="activate by walking" type="bool">
+  &move_on;
-    If set, the player gets the message when walking ontop of the object.
-    "invisible 1" should be set in this case. This is the typical configuration
-    for a "magic_mouth": The player walks through a dungeon and suddenly he
-    gets a message. Use this to create some roleplay atmosphere, and to inform
-    the player about possible dangers or secrets.
-  </attribute>
-  <attribute arch="fly_on" editor="activate by flying" type="bool">
-    If set, the player gets the message when flying (=levitating) ontop
-    of the object. Usually this should be set together with walk_on.
-  </attribute>
   <attribute arch="food" editor="counter" type="int">
     If a counter-value is set (greater zero), the sign/magic_mouth can be applied
     (printing the message) only that many times. For signs this really shouldn't
     be used, while for magic_mouths it is extremely helpful.
     Monsters walking over the magic_mouth do not decrease the counter.
     Often, you might want to have a message displayed only one time. For example:
     The player enters your map and you put a magic_mouth to tell him about the
     monsters and how dangerous they look and all. Later, when all the monsters
     are killed and the player leaves the map, displaying the same message a
     second time would be silly. &lt;counter&gt; 1 does a perfect job in such cases.
     burned or otherwise destroyed.
   </attribute>
   <attribute arch="unique" editor="unique item" type="bool">
     Unique items exist only one time on a server. If the item
     is taken, lost or destroyed - it's gone for good.
     This can be used if you want to sell apartments on your
     map: Simply sell a unique passport/key, and place
     an inventory checker at the entrance of your apartment.
   </attribute>
   <attribute arch="startequip" editor="godgiven item" type="bool">
   <use><![CDATA[
     Spinners are very rarely used. I believe they are quite
     confusing and pointless. The only use I can think of is building
     some puzzle about where to shoot into spinners to shoot somewhere you
     otherwise couldn't.
     When placing spinners on a map with magic walls, make sure the spell-
     projectiles from magic walls don't get to fly in loops. ]]>
   </use>
   <attribute arch="sp" editor="direction number" type="int">
     The spinner will change the direction of flying objects by
     45 degrees per &lt;direction number&gt;. Negative values spin clockwise,
     positive values counter clockwise.
     Example: &lt;direction number&gt; -2 means spin 90 degrees clockwise.
   </attribute>
-  <attribute arch="walk_on" value="1" type="fixed" />
+  &move_on;
-  <attribute arch="fly_on" value="1" type="fixed" />
 </type>
 <!--####################################################################-->
 <type number="138" name="Swamp">
   <ignore>
     he will start to sink in and eventually drown and die.
     Items dropped on the swamp sink in and dissapear.
     Players with knowledge of the woodsman skill are a lot less likely
     to die in the swamp. ]]>
   </description>
-  <attribute arch="walk_on" value="1" type="fixed" />
   <attribute arch="is_floor" value="1" type="fixed" />
   <attribute arch="is_wooded" value="1" type="fixed" />
   <attribute arch="speed" editor="drowning speed" type="float">
     The higher the &lt;drowning speed&gt;, the faster will players and items
     sink into the swamp. Swamp with very high &lt;drowning speed&gt; can be a nasty
     and unexpected death-trap. Players should get a warning before such areas.
   </attribute>
-  <attribute arch="slow_move" editor="slow movement" type="int">
+  &speed_left;
-    If &lt;slow movement&gt; is set to a value greater zero, all
+  &move_on;
-    creatures moving over this spot will be slower than normal.
+  &movement_types_terrain;
-    &lt;slow movement&gt; 1  - rough terrain
-    &lt;slow movement&gt; 2  - very rough terrain
-    ...
-    &lt;slow movement&gt; 5  - default for deep swamp
-  </attribute>
   <attribute arch="no_magic" editor="no spells" type="bool">
     If enabled, it is impossible for players to use (wizard-)
     spells on that spot.
   </attribute>
   <attribute arch="damned" editor="no prayers" type="bool">
     (for example "/peterm/FireTemple/fire1"). It can also be a relative
     path, not beginning with '/' (On the map "/peterm/FireTemple/Fire2"
     for example I could use the relative path "Fire1"). Use relative
     paths whenever possible! Note that upper/lower case must always be
     set correctly. However, please use lower case only.
     If the &lt;exit path&gt; is set, ONLY players can get teleported. If the
     &lt;exit path&gt; is unset (empty), anything can get teleported: Players,
     monsters and items. In this case, the destined map is automatically
     the same map the teleporter is on.
   </attribute>
   <attribute arch="hp" editor="destination X" type="int">
     The exit destinations define the (x, y)-coordinates where the exit
     leads to.
     If both are set to zero and &lt;exit path&gt; is empty, the player will
     get teleported to another, randomly chosen teleporter on the same
     map (Slightly confusing for the player though). Make sure there
     actually *is* a second one in that case.
     If both are set to zero and &lt;exit path&gt; is set, the player will
     be transferred to the "default enter location" of the destined map.
     The latter can be set in the map-properties as "Enter X/Y". Though,
     please DO NOT use that. It turned out to be a source for numerous
     map-bugs.
   </attribute>
   <attribute arch="sp" editor="destination Y" type="int">
     The exit destinations define the (x, y)-coordinates where the exit
     leads to.
     If both are set to zero and &lt;exit path&gt; is empty, the player will
     get teleported to another, randomly chosen teleporter on the same
     map (Slightly confusing for the player though). Make sure there
     actually *is* a second one in that case.
     If both are set to zero and &lt;exit path&gt; is set, the player will
     be transferred to the "default enter location" of the destined map.
     The latter can be set in the map-properties as "Enter X/Y". Though,
     please DO NOT use that. It turned out to be a source for numerous
     map-bugs.
   <attribute arch="speed" editor="activation speed" type="float">
     If the &lt;activation speed&gt; is nonzero, the teleporter will
     automatically be activated in regular time-intervals. Hence, the
     player can just step on it and gets teleported sooner or later.
     The duration between two activates depends on the given value.
     Default in the teleporter arch is &lt;activation speed&gt; 0.1.
     VERY IMPORTANT: If you want to have your teleporter activated via
     button/handle/magic_ear/etc, you must set &lt;activation speed&gt; to zero!
+  </attribute>
+  &speed_left;
+</type>
+<!--####################################################################-->
+<type number="26" name="Timed Gate">
+  <ignore>
+    <ignore_list name="non_pickable" />
+  </ignore>
+  <description><![CDATA[
+    Gates play an important role in Crossfire. Gates can be opened
+    by activating a button/trigger, by speaking passwords (-> magic_ear)
+    or carrying special key-objects (-> inventory checker).
+    Unlike locked doors, gates can get shut again after a player has
+    passed, which makes them more practical in many cases. Unlike normal
+    gates, timed gates open when triggered but automatically close again
+    after some time.]]>
+  </description>
+  <use><![CDATA[
+    Use gates to divide your maps into separated areas. After solving
+    area A, the player gains access to area B, and so on. Make your
+    maps more complex than "one-way". ]]>
+  </use>
+  <attribute arch="no_pick" value="1" type="fixed" />
+  <attribute arch="connected" editor="connection" type="int">
+    Whenever the inventory checker is triggered, all objects with identical
+    &lt;connection&gt; value get activated. This only makes sense together with
+    &lt;blocking passage&gt; disabled. If unset, the gate opens automatically
+    after some time.
+  </attribute>
+  <attribute arch="wc" editor="position state" type="int">
+    The &lt;position state&gt; defines the position of the gate:
+    Zero means completely open/down, the "number of animation-steps" (usually
+    about 6 or 7) means completely closed/up state. I suggest you don't
+    mess with this value - Leave the default in place.
+  </attribute>
+  &movement_types_terrain;
+  <attribute arch="no_magic" editor="restrict spells" type="bool">
+    Restricting the use of spells to pass this gate. This has
+    an effect only if &lt;block view&gt; is disabled.
+  </attribute>
+  <attribute arch="damned" editor="restrict prayers" type="bool">
+    Restricting the use of prayers to pass this door. This has
+    an effect only if &lt;block view&gt; is disabled.
+  </attribute>
+  <attribute arch="hp" editor="open duration" type="int">
+    Defines the duration the gate remains closed. This only takes effect
+    if the gate is not connected.
   </attribute>
 </type>
 <!--####################################################################-->
 <type number="155" name="Trap">
     <attribute arch="material" />
     <attribute arch="unpaid" />
   </ignore>
   <description><![CDATA[
     A trap is a object that can either do damage or trigger another connected object
 	when detonated. Traps are like runes except they are not magical in nature,
 	and generally have either a physical attack or trigger a reaction.
     <br><br>
     Traps hit any monster or person who steps on them for 'dam' damage in
     'attacktype' attacktype and/or trigger a reaction.
     <br><br>
   <use><![CDATA[
     Avoid monsters stepping on your traps. For example, a party of orcs setting
 off your lightning wall and pit trap is usually a bad idea. ]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="walk_on" value="1" type="fixed" />
+  &move_on;
   <attribute arch="level" editor="trap level" type="int">
     Level  effects how easily a trap may be found and disarmed, and
     how much experience the player gets for doing so. Beware: High level
     traps can be quite a cheap source of experience! So either make them
     tough, or keep the level low.
   </attribute>
   </attribute>
   <attribute arch="hp" editor="number of charges" type="int">
     The trap will detonate &lt;number of charges&gt; times before disappearing.
   </attribute>
   <attribute arch="dam" editor="direct damage" type="int">
     &lt;direct damage&gt; specifies how much damage is done by the trap.
 	This should be set in reasonable relation to the trap's level.
   </attribute>
   <attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
     This attribute defines what attacktype to use for direct damage when
     the trap detonates.
   </attribute>
     Trapdoors should be used in the same fashion as pits:
     They should always drop the victims to some kind of lower level. They
     are not supposed to be used to randomly interconnect maps like teleporters. ]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
-  <attribute arch="walk_on" value="1" type="fixed" />
+  &move_on;
   <attribute arch="weight" editor="hold weight" type="int">
     This value defines how much weight the trapdoor can hold.
     Once items or creatures are gathered on the trapdoor, with
     a total weight surpassing this value, then the trapdoor will
     open and things start falling through.
     &lt;quality level&gt; 5 per default).
   </attribute>
 </type>
 <!--####################################################################-->
+<type number="52" name="Trigger Marker">
+  <ignore>
+    <ignore_list name="system_object" />
+  </ignore>
+  <description><![CDATA[
+    A trigger marker is an object that inserts an invisible force (a mark) into a
+    player stepping on it WHEN TRIGGERED. This force does nothing except containing a
+    &lt;key string&gt; which can be discovered by detectors or inventory
+    checkers. It is also possible to use markers for removing marks again.
+    <br><br>
+    Note that the player has no possibility to "see" his own marks,
+    except by the effect that they cause on the maps. ]]>
+  </description>
+  <use><![CDATA[
+    Markers hold real cool possibilities for map-making. I encourage
+    you to use them frequently. However there is one negative point
+    about markers: Players don't "see" what's going on with them. It is
+    your task, as map-creator, to make sure the player is always well
+    informed and never confused.
+    <br><br>
+    Please avoid infinite markers when they aren't needed. They're
+    using a little space in the player file after all, so if there
+    is no real purpose, set an expire time. ]]>
+  </use>
+  <attribute arch="no_pick" value="1" type="fixed" />
+  <attribute arch="slaying" editor="key string" type="string">
+    The &lt;key string&gt; can be detected by inv. checkers/detectors.
+    If the player already has a force with that &lt;key string&gt;,
+    there won't be inserted a second one.
+  </attribute>
+  <attribute arch="connected" editor="connection" type="int">
+   Unlike a regular marker this is the connection that triggers this marker to activate.
+  </attribute>
+  <attribute arch="food" editor="mark duration" type="int">
+    This value defines the duration of the force it inserts.
+    If nonzero, the duration of the player's mark is finite:
+    about 1 food per 10 seconds. &lt;mark duration&gt; zero/unset
+    means the mark will stay on the player forever.
+  </attribute>
+  <attribute arch="name" editor="delete mark" type="string">
+    When the player steps onto the marker, all existing forces in
+    the players inventory with a &lt;key string&gt; matching &lt;delete mark&gt;
+    will be removed. If you don't want to remove any marks, leave
+    this textfield empty.
+    Note that the string &lt;delete mark&gt; is set as the name of
+    this marker. So don't be confused, and remember changing the
+    name will take effect on the marker's functionality.
+  </attribute>
+  <attribute arch_begin="msg" arch_end="endmsg" editor="marking message" type="text">
+    In the moment when the player gets marked, this text is displayed
+    to him. You should really set a message in any marker you create,
+    because it's the only way for the player to notice what's going on.
+  </attribute>
+</type>
+<!--####################################################################-->
 <type number="0" name="Wall">
   <required>
     <attribute arch="is_floor" value="0" />
     <attribute arch="alive" value="0" />
-    <attribute arch="no_pass" value="1" />
+    <attribute arch="move_block" value="255" />
   </required>
   <ignore>
     <attribute arch="nrof" />
     <attribute arch="title" />
     <attribute arch="name_pl" />
     <attribute arch="unpaid" />
   </ignore>
   <description><![CDATA[
     Walls usually block passage and sight. ]]>
   </description>
-  <attribute arch="no_pass" editor="blocking passage" type="bool">
+  &movement_types_terrain;
-    If set, the object cannot be passed by players nor monsters.
-  </attribute>
   <attribute arch="can_roll" editor="moveable" type="bool">
     If set, the object is able to "roll", so it can be pushed around.
     This setting is used for boulders and barrels.
   </attribute>
   <attribute arch="no_magic" editor="restrict spells" type="bool">
     Restricting the use of spells to pass this wall.
   </attribute>
   <attribute arch="damned" editor="restrict prayers" type="bool">
     This takes effect only with &lt;blocksview&gt; disabled.
     Restricting the use of spells to pass this wall.
+  </attribute>
+</type>
+<!--####################################################################-->
+<type number="109" name="Wand &amp; Staff">
+  <description><![CDATA[
+    Wands contain a certain spell. The player can apply (ready) and
+    fire the wand. After a defined number of casts, the wand is
+    "used up". It is possible to recharge a wand with scrolls of
+    charging, but usually that isn't worth the cost. ]]>
+  </description>
+  <use><![CDATA[
+    Wands are quite seldomly used. The reason prolly is that they're
+    generally not cost-efficient. Handing out high-level wands with
+    powerful special spells isn't a good idea either, because of
+    the recharge ability.
+    <br><br>
+    For low levels, staffs of healing/cure and word of recall are
+    quite desirable though. Ideal rewards for low level quests. ]]>
+  </use>
+  <attribute arch="sp" editor="spell" type="spell">
+    The &lt;spell&gt; specifies the contained spell.
+  </attribute>
+  <attribute arch="level" editor="casting level" type="int">
+    The &lt;casting level&gt; of the wand determines it's power.
+    An average level for wands in shops is about 10.
+  </attribute>
+  <attribute arch="food" editor="number of charges" type="int">
+    The wand can be used &lt;number of charges&gt; times before it is
+    used up. It can be recharged with scrolls of charging.
+  </attribute>
+  <attribute arch="startequip" editor="godgiven item" type="bool">
+    A godgiven item vanishes as soon as the player
+    drops it to the ground.
+  </attribute>
+  <attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
+    This text may contain a description of the wand.
   </attribute>
 </type>
 <!--####################################################################-->
 <type number="0" name="Weak Wall">
   <attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
     This number is a bitmask, specifying the weapon's attacktypes.
     Attacktypes are: physical, magical, fire, cold.. etc. Most artifact weapons
     have no more than one or two attacktypes. Keep in mind that all weapons
     can be blessed by the player's diety, thus adding an additional attacktype.
     When a player hits a monster with a weapon that has more than one attacktype,
     then he will do as much damage as the "best" of his attacktypes does. So,
     the more attacktypes you've got, the better your chance to take advantage
     of a monster's vulnerabilities. (Btw: Same rule applies for monster vs.
     player.). Attacktypes "magic" and "chaos" are somehow exceptions.
   <attribute arch="weapontype" editor="weapontype" type="list_weapon_type">
     The &lt;weapontype&gt; characterizes the weapon's type of physical
     attack. It could best be considered a "subclassification"
     of the physical attacktype. For now, this is only used for
     attack messages!
     You should always set this correctly when creating new
     weapons for your maps.
   </attribute>
   <attribute arch="skill" editor="skill name" type="string">
     Matching &lt;skill name&gt; of the skill that is required
   </attribute>
   <attribute arch="slaying" editor="slaying race" type="string">
     Slaying means the weapon does tripple (3x) damage to monsters of the
     specified race. If &lt;slaying race&gt; matches an arch name (e.g. "big_dragon"),
     only monsters of that archtype are hit with tripple damage.
     No god blessings are possible for weapons with a race set in this entry
     (That's because god blessings add tripple damage against their own
     enemy races). Tripple damage is very effective.
   </attribute>
   <attribute arch="last_sp" editor="weapon speed" type="int">
     The &lt;item power&gt; value measures how "powerful" an artifact is.
     Players will only be able to wear equipment with a certain total
     amount of &lt;item power&gt;, depending on their own level. This is the
     only way to prevent low level players to wear "undeserved" equipment
     (like gifts from other players or cheated items).
     It is very important to adjust the &lt;item power&gt; value carefully
     for every artifact you create! If zero/unset, the CF server will
     calculate a provisional value at runtime, but this is never
     going to be an accurate measurement of &lt;item power&gt;.
   </attribute>
     the curse is removed.
   </attribute>
   <attribute arch="lifesave" editor="save life" type="bool">
     An item with this flag enabled will save the players life
     for one time: When the player is wearing this item and his
-    healthpoints reach zero, the item dissapears, replenishing
+    health points reach zero, the item disappears, replenishing
     half of the player's health.
     An item with &lt;save life&gt; should not have
     any decent additional bonuses!
   </attribute>
   <attribute arch="unique" editor="unique item" type="bool">
     Unique items exist only one time on a server. If the item
     additional &lt;grace regen.&gt; bonus should be VERY RARE!!
   </attribute>
   <attribute arch="food" editor="food bonus" type="int">
     Positive &lt;food bonus&gt; slows down the player's digestion,
     thus he consumes less food. Negative values speed it up.
     Note that food is consumed not only for "being alive", but
     also for healing and mana-regeneration.
     &lt;food bonus&gt; only affects the amount of food consumed
     for "being alive". Hence, even with high &lt;food bonus&gt;,
     during a fight a player can run out of food quickly.
   </attribute>
   <attribute arch="xrays" editor="xray vision" type="bool">
     Xray vision allows the player to see through obstacles
     in a two-square-wide radius. This is extremely helpful and
-    desireable, so don't give it away for cheap on equipment.
+    desirable, so don't give it away for cheap on equipment.
   </attribute>
   <attribute arch="stealth" editor="stealth" type="bool">
     Stealth allows the player to move silently.
     This comes to effect if a player turns himself
     invisible and tries to sneak around monsters.
     the ability to &lt;reflect spells&gt;, all kinds of
     spell-bullets and -beams will bounce off him.
     This works only about 90% of all times, to
     avoid players being completely immune to certain
     types of attacks.
     This is a very powerful ability and it
     shouldn't be handed out cheap!
   </attribute>
   <attribute arch="reflect_missile" editor="reflect missiles" type="bool">
     If a player is wearing any piece of equipment with
     This text describes the weapons's "story". Every decent artifact weapon
     should have such a description.
   </attribute>
 </type>
-<!--####################################################################-->
+<type number="116" name="Event Connector">
-<type number="109" name="Wand &amp; Staff">
-  <description><![CDATA[
-    Wands contain a certain spell. The player can apply (ready) and
-    fire the wand. After a defined number of casts, the wand is
-    "used up". It is possible to recharge a wand with scrolls of
-    charging, but usually that isn't worth the cost. ]]>
-  </description>
+  <description><![CDATA[
-  <use><![CDATA[
+    Event connectors link specific events that happen to objects to
-    Wands are quite seldomly used. The reason prolly is that they're
+    a crossfire plug-in. ]]>
-    generally not cost-efficient. Handing out high-level wands with
+  </description>
-    powerfull special spells isn't a good idea either, because of
+  <attribute arch="subtype" editor="event type" type="list_event_type">
-    the recharge ability.
+    The type of event that triggers a notify to the plug-in.
-    <br><br>
+  </attribute>
-    For low levels, staffs of healing/cure and word of recall are
-    quite desireable though. Ideal rewards for low level quests. ]]>
-  </use>
-  <attribute arch="sp" editor="spell" type="spell">
+  <attribute arch="title" editor="plug-in" type="string">
-    The &lt;spell&gt; specifies the contained spell.
+    The name of the plug-in that should be notified of the event, e.g. "cfpython"
+    for python and "perl" for the Crossfire-Perl plug-in.
   </attribute>
+  <attribute arch="slaying" editor="extension" type="string">
+    The name of the extension to invoke (for python, this is the path to a script,
+    for perl this is the name of a extension package without the ".ext" extension.
+  </attribute>
-  <attribute arch="level" editor="casting level" type="int">
+  <attribute arch="name" editor="options" type="string">
-    The &lt;casting level&gt; of the wand determines it's power.
+    A string that is passed unaltered to the extension above. Often used to pass
-    An average level for wands in shops is about 10.
+    options to the extension that alter its behaviour.
-  </attribute>
-  <attribute arch="food" editor="number of charges" type="int">
-    The wand can be used &lt;number of charges&gt; times before it is
-    used up. It can be recharged with scrolls of charging.
-  </attribute>
-  <attribute arch="startequip" editor="godgiven item" type="bool">
-    A godgiven item vanishes as soon as the player
-    drops it to the ground.
-  </attribute>
-  <attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
-    This text may contain a description of the wand.
   </attribute>
 </type>
 </types>

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing deliantra/Deliantra/res/types.xml (file contents): Revision 1.2 by root, Mon Mar 13 03:47:36 2006 UTC vs. Revision 1.13 by root, Sun Mar 26 08:21:37 2006 UTC

Diff Legend

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.2 by root, Mon Mar 13 03:47:36 2006 UTC vs.
Revision 1.13 by root, Sun Mar 26 08:21:37 2006 UTC