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

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.31 by root, Mon Sep 17 17:23:16 2007 UTC vs.
Revision 1.37 by root, Tue Aug 26 01:58:06 2008 UTC

 <?xml version="1.0" standalone="no" ?>
 <!--
 ######################################################################
 # types.xml - This is the definitions-file for all the different     #
-# Crossfire object types and their attributes.                       #
+# Deliantra object types and their attributes.                       #
 #                                                                    #
-# The server code of the Crossfire game is always changing and       #
+# The server code of the Deliantra 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 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!    #
-#                                                                    #
-# IMPORTANT: Make a backup copy of this file before you start        #
-# to modify it!                                                      #
 #                                                                    #
 # New types must be inserted maintaining the alphabetical order.     #
 #                                                                    #
 # about the 'type' elements:                                         #
 #                                                                    #
 # </required>                                                        #
 # <ignore>                                                           #
 #    list of attributes not to import from default_type              #
 # </ignore>                                                          #
 # <description><![CDATA[                                             #
-#   Description of this type. ]]>                                    #
+#   Description of this type.]]>                                    #
 # </description>                                                     #
 # <use><![CDATA[                                                     #
-#   How to use this type. ]]>                                        #
+#   How to use this type.]]>                                        #
 # </use>                                                             #
 # ... attributes ...                                                 #
 # </type>                                                            #
 #                                                                    #
 # about the 'attribute' type: <attribute ... type="XXX" >            #
         decremented by 1. Otherwise, it is incremented by &lt;speed&gt; on
         every tick.
      </attribute>
   ">
   <!ENTITY activate_on "
-     <attribute arch='activate_on_push' editor='Activate on push' type='bool'>
+     <attribute arch='activate_on_push' editor='activate on push' type='bool'>
        Whether the teleporter should only be activated on push.
      </attribute>
-     <attribute arch='activate_on_release' editor='Activate on release' type='bool'>
+     <attribute arch='activate_on_release' editor='activate on release' type='bool'>
        Whether the teleporter should only be activated on release.
      </attribute>
   ">
   <!ENTITY resistances_flesh_desc "
   <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 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.
+    The image-name defines what image is displayed for this object in-game. Take care if the archetype of the
+    object has an animation! See also the 'animation' attribute.
+  </attribute>
+  <attribute arch="animation" editor="animation" type="string">
+    The animation-name of the object. If you assign custom faces and the archetype
+    defines an animation you can disable the animation of an archetype by setting this
+    field to NONE.
   </attribute>
   <attribute arch="tag" editor="tag" type="string">
     You can tag objects with an identifier. Tagged objects can be found quickly
     from their tag, which makes them useful to tag exits and refer to those by
     their name.
     <br><br>
     A particularly nice feature of abilities is that they can hold two
     spells: One for short range- and one for long range use.
     \n\n
     You should know that spellcasting monsters receive abilities via
-    &lt;treasurelist&gt;. ]]>
+    &lt;treasurelist&gt;.]]>
   </description>
   <use><![CDATA[
     If you want to create "customized" spellcasting monsters, you
     should use abilities (rather than spellbooks/wands or something).
     The long/short-range spell feature can make boss-monsters more
     <br><br>
     You should keep in mind that magic abilities allow players
     to get better resistance. You can turn off the magic part to
     make the spells more dangerous. However, this really shouldn't
     be neccessary unless you work on very high level maps.
-    And what fun is a magic resistance cloak when it has no effect? ]]>
+    And what fun is a magic resistance cloak when it has no effect?]]>
   </use>
   <attribute arch="invisible" value="1" type="fixed" />
   <attribute arch="no_drop" value="1" type="fixed" />
   <attribute arch="sp" editor="short range spell" type="spell">
     The monster will use the specified &lt;short range spell&gt;
   </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 disappears. ]]>
+    Either way, the sacrificed item disappears.]]>
   </description>
   <attribute arch="no_pick" 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
+    If you want the player to have to drop a specific amount of money use "money".
-    expected to drop on the altar. (Often this is put in the altar's
+    See also the "drop amount" attribute.
-    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.
     <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 infinitely. ]]>
+    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. =) ]]>
+    quite grateful if things work more than once. =)]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <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
+    If you want the player to have to drop a specific amount of money use "money".
-    expected to drop on the altar. (Often this is put in the altar's
+    See also the "drop amount" attribute.
-    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.
 <!--####################################################################-->
 <type number="74" name="Skill Tool">
   <description><![CDATA[
     Wearing a skill tool will give the player the ability to use a skill.
-  ]]>
+ ]]>
   </description>
   <use><![CDATA[
     Feel free to assign resistancies and stats to a skill tools or change
     the skill that is given.
-  ]]>
+ ]]>
   </use>
   <attribute arch="skill" editor="skill name" type="string">
   This field describes which skill the player will be able to use wearing this item.
   </attribute>
   &player_stat_resist_sections;
 </type>
 <!--####################################################################-->
 <type number="39" name="Amulet">
   <description><![CDATA[
     Wearing an amulet, the object's stats will directly be inherited to
-    the player. Amulets are usually meant for protection and defense. ]]>
+    the player. Amulets are usually meant for protection and 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. ]]>
+    important that you keep your artifact in balance with existing maps.]]>
   </use>
   <attribute arch="ac" editor="armour class" type="int">
     This value defines the amount of armour-class bonus for wearing
     this item. &lt;Armour class&gt; lessens the chance of being hit. Lower
     values are better. It should usually be set only for armour-like equipment.
     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
+    for every artifact you create! If zero/unset, the Deliantra server will
     calculate a provisional value at runtime, but this is never
     going to be an accurate measurement of &lt;item power&gt;.
   </attribute>
   <attribute arch="damned" editor="damnation" type="bool">
     A damned piece of equipment cannot be unwielded unless the curse
     Battleground is very special: In short, players can die on battleground
     without any death penalties. They don't loose or gain experience
     while on battleground. Acid, draining and depletion effects don't
     work either.
     When a player dies on battleground, he gets teleported to an exit
-    location which is defined in the battleground object. ]]>
+    location which is defined in the battleground object.]]>
   </description>
   <use><![CDATA[
     Battleground is only meant for player vs. player duels. You can
     design combat arenas similiar to the one in scorn.<br>
     What should NEVER be done is placing battleground tiles in
     It must not be possible to gain significant treasure for fighting
     on battleground, because it bears no risk.<br><br>
     (Battleground will cease to work when the image or name is changed,
     or when it is placed beneath another floor tile.
     This is not a bug, it is there to prevent any attempts of placing
-    "hidden" battleground tiles anywhere.) ]]>
+    "hidden" battleground tiles anywhere.)]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="is_floor" value="1" type="fixed" />
   <attribute arch="hp" editor="destination X" type="int">
     The exit destinations define the (x, y)-coordinates where players
     get teleported after they died on this battleground.
   </attribute>
 </type>
 <!--####################################################################-->
-<type number="165" name="Safe ground (CF+)">
+<type number="165" name="Safe ground">
   <ignore>
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     Safe ground is a special object that prevents any effects that might
     be harmful for the map, other players or items on the map.
     It blocks all magic and prayers, usage of alchemy, prevents potions
     from being used and blocks bombs from exploding. Note that altars that
     do cast spells still work.
-    (This is a Crossfire+ feature, and might not work elsewhere)
-  ]]>
+ ]]>
   </description>
   <use><![CDATA[
     Safe ground can be used to prevents any means of burning
     or destroying the items in a shop. Put this object below all floor tiles
     in your map and your shop will be safe. It's generally useful for making
     areas where really no kind of spell should be invoked by a player.
-  ]]>
+ ]]>
   </use>
   &movement_types_terrain;
   <attribute arch="no_pick" value="1" type="fixed" />
 </type>
 <!--####################################################################-->
 <type number="8" name="Book">
   <description><![CDATA[
-    Applying a book, the containing message is displayed to the player. ]]>
+    Applying a book, the containing message is displayed to the player.]]>
   </description>
   <attribute arch="level" editor="literacy level" type="int">
     If this value is set to be greater than zero, the player needs a
     certain literacy level to succeed reading the book. The book can be
     read if: mental_level greater &lt;literacy level&gt; - 5. Adding level to a
 <type number="99" name="Boots">
   <import_type name="Amulet" />
   <description><![CDATA[
     Wearing boots, the object's stats will directly be inherited to
     the player. Usually enhancing his speed, or granting some minor
-    protection bonus. ]]>
+    protection bonus.]]>
   </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. ]]>
+    important that you keep your artifact in balance with existing maps.]]>
   </use>
   <attribute arch="exp" editor="speed bonus" type="int">
     Boots with &lt;speed bonus&gt; will increase the player's walking speed
     while worn. This kind of bonus is quite desirable for players of low-
     and medium level. High level players usually have fastest possible
 <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. ]]>
+    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. ]]>
+    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.
 <!--####################################################################-->
 <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. ]]>
+    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. ]]>
+    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>
   </ignore>
   <description><![CDATA[
     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. ]]>
+    &lt;connection&gt; value get's triggered a second time.]]>
   </description>
   &move_on;
   &move_off;
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="weight" editor="press weight" type="int">
     <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. ]]>
+    &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. ]]>
+    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">
 <type number="87" name="Cloak">
   <import_type name="Amulet" />
   <description><![CDATA[
     Wearing a cloak, the object's stats will directly be inherited to
     the player. Cloaks usually add minor &lt;armour class&gt; and
-    sometimes a bit of resistance. ]]>
+    sometimes a bit of resistance.]]>
   </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. ]]>
+    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 cloak.
 </type>
 <!--####################################################################-->
 <type number="9" name="Clock">
   <description><![CDATA[
-    Applying a clock, the time is displayed to the player. ]]>
+    Applying a clock, the time is displayed to the player.]]>
   </description>
   <attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
     This text may describe the item
   </attribute>
 </type>
     A player can put (certain kinds of) items in the container.
     The overall weight of items is reduced when put inside a
     container, depending on the settings.
     <br><br>
     A special feature of containers is the "cauldron",
-    capable of mixing alchemical receipes. ]]>
+    capable of mixing alchemical receipes.]]>
   </description>
   <use><![CDATA[
     Note on chests - There are two types of chests:
     <UL>
     <LI> First the random treasure chests - Those are NOT containers
          (but object type Treasure), they create random treasures when
          applied. Archetype name is "chest".
     <LI> Second there are the permanent chests - Those are containers,
          they can be opened and closed again. Archetype name is "chest_2".
-    </UL> ]]>
+    </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".
     <attribute arch="title" />
   </ignore>
   <description><![CDATA[
     Converters are like "exchange tables". When the player drops a
     specific type of items, they get converted into other items, at a
-    predefined exchange-ratio. ]]>
+    predefined exchange-ratio.]]>
   </description>
   <use><![CDATA[
     Converters are better than shopping with doormats, because the
     converters never get sold out. For some items like food or jewels
     those "exchange tables" are really nice, while for the more important
     <br><br>
     VERY IMPORTANT: Be careful with the exchange-ratio! When you drop
     items on a converter, the stuff you get must be of equal or lesser
     value than before! (Except if you are using "rare" items like
     dragonscales for payment). The code will not check if your ratio is
-    sane, so the player could gain infinite wealth by using your converter. ]]>
+    sane, so the player could gain infinite wealth by using your converter.]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="slaying" editor="cost arch" type="string">
     &lt;cost arch&gt; is the name of the archetype the player has to
     put on the converter, as payment.
   </ignore>
   <description><![CDATA[
     A creator is an object which creates another object when it
     is triggered. The child object can be anything. Creators are
     VERY useful for all kinds of map-mechanisms. They can even
-    periodically create things. ]]>
+    periodically create things.]]>
   </description>
   <use><![CDATA[
     Don't hesitate to hide your creators under the floor.
-    The created items will still always appear ontop of the floor. ]]>
+    The created items will still always appear ontop of the floor.]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="other_arch" editor="create arch" type="string">
     This string defines the object that will be created.
     You can choose any of the existing arches.
     finds a specific object, it toggles its connected value.
     <br><br>
     What is "unique" about them, compared to inv. checkers/ pedestals?
     - First, detectors check their square for a match periodically, not
     instantly. Second, detectors check directly for object names. Third,
-    detectors do not check the inventory of players/monsters. ]]>
+    detectors do not check the inventory of players/monsters.]]>
   </description>
   <use><![CDATA[
     There is one major speciality about detectors: You can detect spells
     blown over a detector! To detect a lighting bolt for example, set
     "slaying ligthing" and "speed 1.0". In combination with spellcasting
-    walls, this can be very useful for map-mechanisms. ]]>
+    walls, this can be very useful for map-mechanisms.]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="slaying" editor="match name" type="string">
     &lt;match name&gt; specifies the name of the object we are looking for.
     Actually it does also check for the &lt;key string&gt; in key-objects,
   <description><![CDATA[
     Directors change the direction of spell objects and other projectiles
     that fly past. Unlike spinners, directors always move objects in the
     same direction. It does not make a difference from what angle you
     shoot into it.<br>
-    Directors are visible per default. ]]>
+    Directors are visible per default.]]>
   </description>
   <use><![CDATA[
     Directors are rarely used in maps. Sometimes they are placed to
     change the direction of spells coming out of magic walls,
     "channeling" spell-projectiles in some direction. When doing this,
     into them!</B> The spell-projectiles bouncing between the directors
     would accumulate to huge numbers and at some point slow down the
     server by eating memory- and CPU-time.
     <br><br>
     You'd better not place directors in monster vs. player combat
-    areas too much, because that freaks out wizard-type players. ]]>
+    areas too much, because that freaks out wizard-type players.]]>
   </use>
   <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).
 <type number="158" name="Disease">
   <ignore>
     <ignore_list name="system_object" />
   </ignore>
   <description><![CDATA[
-    Diseases are an intersting form of spellcraft in Crossfire.
+    Diseases are an intersting form of spellcraft in Deliantra.
     Once casted, they can spread out and infect creatures in a large
     area. Being infected can have various effects, from amusing farts
-    to horrible damage - almost everything is possible. ]]>
+    to horrible damage - almost everything is possible.]]>
   </description>
   <use><![CDATA[
     Diseases are extremely flexible and usable in a many ways.
     So far they are mostly used for causing bad, unwanted effects.
     You could just as well create a disease which helps the player
     (recharging mana for example).
-    Infection with a "positive disease" could even be a quest reward. ]]>
+    Infection with a "positive disease" could even be a quest reward.]]>
   </use>
   <attribute arch="invisible" value="1" type="fixed" />
   <attribute arch="level" editor="plaque level" type="int">
     The &lt;plaque level&gt; is proportional to the disease's deadliness.
     This mainly reflects in the &lt;damage&gt;. It has no effect on
   </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. ]]>
+    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">
     When activated, a duplicator can duplicate, multiply or destroy a pile of
     objects which lies somewhere on top of the duplicator.
     The duplicator has one arch name specified as &lt;target arch&gt;,
     and only objects of this archetype can be affected.<br>
     It will multiply the number of items in the pile, by the &lt;multiply factor&gt;.
-    If the latter is set to zero, it will destroy objects. ]]>
+    If the latter is set to zero, it will destroy objects.]]>
   </description>
   <use><![CDATA[
     I hope it is clear that one must be very cautious when inserting a duplicator
     anywhere with &lt;multiply factor&gt; greater than one.
     It is designed to be used for betting mechanisms only (bet -&gt; win/loose).
     It is <b>not acceptable</b> to allow duplication of anything other than
     coins, gold and jewels. Besides, it is very important that the chance to
     loose the input matches the chance to earn winnings.<br>
     A duplicator with &lt;multiply factor&gt; 3 for example should have a
-    loosing rate of 2/3 = 67%. ]]>
+    loosing rate of 2/3 = 67%.]]>
   </use>
   <attribute arch="other_arch" editor="target arch" type="string">
     Only objects of matching archtype, lying ontop of the duplicator will be
     duplicated, multiplied or removed. All other objects will be ignored.
   </attribute>
   </ignore>
   <description><![CDATA[
     When the player applies an exit, he is transferred to a different location.
     (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.  ]]>
+    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. ]]>
+    Don't forget to give the player relyable hints about them though.]]>
   </use>
   <attribute arch="slaying" editor="exit path" type="string">
     The exit path defines the map that the player is transferred to.
     You can enter an absolute path, beginning with '/' (for example
     "/peterm/FireTemple/fire1"). It can also be a relative path, not beginning
     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 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. ]]>
+    according to map/monster difficulty.]]>
   </description>
   <use><![CDATA[
     For dragon players, flesh items can be highly valuable. Note that many
     standard monsters carry flesh items from their &lt;treasurelist&gt;.
     These flesh items "inherit" resistances and level from the monster they belong to.
     not the case - so you have to set it manually.
     <br><br>
     Generally adding special flesh-treaties for dragon players is a great thing
     to do. Always consider that dragon players might really not be interested
     in that special piece of weapon or armour, so don't let the dragon-fellows miss
-    out on the reward completely. ]]>
+    out on the reward completely.]]>
   </use>
   <attribute arch="food" editor="foodpoints" type="int">
     The player's stomache will get filled with this amount of foodpoints.
     The player's health will increase by &lt;foodpoints&gt;/50 hp.
   </attribute>
   <ignore>
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     Floor is a very basic thing whithout too much
-    functionality. It's a floor - you stand on it. ]]>
+    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" />
 <section name="terrain">
   &movement_types_terrain;
     Encounter-Floor is pretty much the same as normal floor.
     Most outdoor floor/ground-arches are set to be "encounters".
     That is kind of a relict from former code: When walking over
     encounter-floor, players sometimes got beamed to little maps
     with monsters on them. Nowadays this feature is disabled -
-    Hence encounter floor is not different from normal floor. ]]>
+    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" />
 <section name="terrain">
   &movement_types_terrain;
 <!--####################################################################-->
 <type number="6" name="Food">
   <description><![CDATA[
     By eating/drinking food-objects, the player can fill his
-    stomache and gain a little health. ]]>
+    stomache and gain a little health.]]>
   </description>
   <attribute arch="food" editor="foodpoints" type="int">
     The player's stomache will get filled with this amount of foodpoints.
     The player's health will increase by &lt;foodpoints&gt;/50 hp.
   </attribute>
 <type number="91" name="Gate">
   <ignore>
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
-    Gates play an important role in Crossfire. Gates can be opened
+    Gates play an important role in Deliantra. 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. ]]>
+    passed, which makes them more practical in many cases.]]>
   </description>
   <use><![CDATA[
     Use gates to divide your maps into seperated areas. After solving
     area A, the player gains access to area B, and so on. Make your
-    maps more complex than "one-way". ]]>
+    maps more complex than "one-way".]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="speed" value="1" type="float">
     The speed of the gate affects how fast it is closing/opening.
   </attribute>
 <type number="113" name="Girdle">
   <import_type name="Amulet" />
   <description><![CDATA[
     Wearing a girdle, the object's stats will directly be inherited to
     the player. Girdles usually provide stats- or damage bonuses and no
-    defense. ]]>
+    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. ]]>
+    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 helmet.
 <!--####################################################################-->
 <type number="100" name="Gloves">
   <import_type name="Amulet" />
   <description><![CDATA[
     Wearing gloves, the object's stats will directly be inherited to
-    the player. Gloves can add defense or damage bonuses. ]]>
+    the player. Gloves can add defense or damage bonuses.]]>
   </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. ]]>
+    important that you keep your artifact in balance with existing maps.]]>
   </use>
   <attribute arch="magic" editor="magic bonus" type="int">
     If the gloves provide &lt;armour class&gt;, &lt;magic bonus&gt; will increase it.
     If the gloves have &lt;weapon class&gt; instead, then &lt;magic bonus&gt;
     will increase that.
   <ignore>
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     A handle can be applied by players and (certain) monsters.
-    Every time it is applied, the &lt;connection&gt; value is triggered. ]]>
+    Every time it is applied, the &lt;connection&gt; value is triggered.]]>
   </description>
   <use><![CDATA[
     Handles are commonly used to move gates. When placing your lever,
     don't forget that some monsters are able to apply it.
     The ability to apply levers is rare among monsters -
-    but vampires can do it for example. ]]>
+    but vampires can do it for example.]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="connected" editor="connection" type="int">
     Every time the handle is applied, all objects
     with the same &lt;connection&gt; value are activated.
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     Handle triggers are handles which reset after a short period
     of time. Every time it is either applied or reset, the
-    &lt;connection&gt; value is triggered. ]]>
+    &lt;connection&gt; value is triggered.]]>
   </description>
   <use><![CDATA[
     When you connect an ordinary handle to a gate, the gate normally remains
     opened after the first player passed. If you want to keep the gate shut,
-    connecting it to a handle trigger is an easy solution.  ]]>
+    connecting it to a handle trigger is an easy solution. ]]>
   </use>
 </type>
 <!--####################################################################-->
 <type number="88" name="Hazard Floor">
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     The best example for Hazard Floor is lava. It works like standard
     floor, but damages all creatures standing on it.
-    Damage is taken in regular time intervals. ]]>
+    Damage is taken in regular time intervals.]]>
   </description>
   <use><![CDATA[
     The default lava for example does minor damage. But you can turn
     it up so that your hazard floor poses a real threat.<br>
     Like magic walls, such floors add a permanent thrill to your map.
     You can use that to safely chase off too-weak players, or just
-    to have something different. ]]>
+    to have something different.]]>
   </use>
   <attribute arch="is_floor" value="1" type="fixed" />
   <attribute arch="lifesave" value="1" type="fixed" />
   &move_on;
   <attribute arch="no_pick" value="1" type="fixed" />
   <import_type name="Amulet" />
   <description><![CDATA[
     Wearing a helmet, the object's stats will directly be inherited to
     the player. Normal helmets usually increase defense, while crowns
     add more special bonuses like stats/resistances paired with
-    low defense. ]]>
+    low 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. ]]>
+    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 helmet.
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     Holy_altars are altars for the various religions. Praying
     at a Holy_altar will make you a follower of that god, and
-    if you already follow that god, you may get some extra bonus. ]]>
+    if you already follow that god, you may get some extra bonus.]]>
   </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,
     Horns are very similar to rods. The difference is that horns regenerate
     spellpoints faster and thus are more valuable than rods.
     <br><br>
     A horn contains a spell. The player can use this spell by applying and
     "fireing" (blowing) the horn. Unlike wands/scrolls, horns can be
-    used endlessly. ]]>
+    used endlessly.]]>
   </description>
   <use><![CDATA[
     Horns are powerful due to their fast recharge rate. They should
     never contain high level attacking spells. Even curing/healing spells
-    are almost too good on a horn. ]]>
+    are almost too good on a horn.]]>
   </use>
   <attribute arch="sp" editor="spell" type="spell">
     Sets the &lt;spell&gt; of the horn. Consider twice before handing out any
     horns to players, since they can be used endlessly without any mana cost!
     Horns with heal/ restoration/ protection spells, IF available, MUST be
 <!--####################################################################-->
 <type number="73" name="Inorganic">
   <description><![CDATA[
     Inorganic materials are generally used as ingredients for
     alchemical receipes. By themselves, they have no special
-    functionalities. ]]>
+    functionalities.]]>
   </description>
   <attribute arch="is_dust" editor="is dust" type="bool">
   </attribute>
   &resistances_basic;
 </type>
     <br><br>
     Alternatively, you can set your inv. checker to block all players
     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. ]]>
+    great variety of possibilities.]]>
   </description>
   <use><![CDATA[
     Putting a check_inventory space in front of a gate (one below) and
     one on the opposite side works reasonably well as a control mechanism.
     Unlike the key/door-combo, this one works infinite since it is
     independant from map reset. Use it to put a "structure" into your
     maps: Player must solve area A to gain access to area B. This concept
-    can be found in nearly every RPG - simple but effective. ]]>
+    can be found in nearly every RPG - simple but effective.]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="slaying" editor="match key string" type="string">
     This string specifies the object we are looking for: We have a match
     if the player does/don't carry a key object or a mark with identical
 <!--####################################################################-->
 <type number="60" name="Jewel">
   <description><![CDATA[
     Items of the type Gold &amp; Jewels are handled like a currency.
     Unlike for any other type of item, in shops, the buy- and selling
-    prices differ only marginally. ]]>
+    prices differ only marginally.]]>
   </description>
   <attribute arch="race" value="gold and jewels" type="fixed" />
   <attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
     This text may describe the object.
   </attribute>
 <!--####################################################################-->
 <type number="24" name="Key">
   <description><![CDATA[
     When carrying a key, a normal door can be opened. The key will
-    disappear. ]]>
+    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>
   <ignore>
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     A locked door can be opened only when carrying
-    the appropriate special key. ]]>
+    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). ]]>
+    appropriate quest items (key objects).]]>
   </use>
   <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.
+    is unique among the Deliantra 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.
   <ignore>
     <ignore_list name="system_object" />
   </ignore>
   <description><![CDATA[
     Magic_ears trigger a connected value
-    when the player speaks a specific keyword. ]]>
+    when the player speaks a specific keyword.]]>
   </description>
   <use><![CDATA[
     Whenever you put magic_ears on your maps, make sure there are
     CLEAR and RELYABLE hints about the keywords somewhere. Don't make
     something like a gate that is opened by speaking "open" or
     <br><br>
     Magic_ears are typically used for interaction with NPCs. You
     can create the impression that the NPC actually *does* something
     according to his conversation with a player. Mostly this means
     opening a gate or handing out some item, but you could be quite
-    creative here. ]]>
+    creative here.]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="connected" editor="connection" type="int">
     The Magic_ear will trigger all objects with the
     same connection value, every time it is activated.
     Magic walls can contain any spell. However, some spells do not
     operate very successfully in them. The only way to know is to test
     the spell you want to use with a wall.
     <br><br>
     Several types of magical walls are predefined for you in the
-    archetypes, and can be found on the "connected" Pickmap. ]]>
+    archetypes, and can be found on the "connected" Pickmap.]]>
   </description>
   <use><![CDATA[
     Spellcasting walls pose an interesting alternative to monsters.
     Usually they are set to be undestroyable. Thus, while monsters
     in a map can be cleared out, the magic walls remain. Low level
     walls' spell(s).
     <br><br>
     It is possible to make walls rotate when triggered. But that is so
     confusing (and useless IMHO) that I did not mention it above. You
     can find a working example on the map
-    "/pup_land/castle_eureca/castle_eureca8". ]]>
+    "/pup_land/castle_eureca/castle_eureca8".]]>
   </use>
   <attribute arch="dam" editor="spell" type="spell">
     The magic wall will cast this &lt;spell&gt;.
   </attribute>
   <attribute arch="level" editor="spell level" type="int">
     player stepping on it. 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. ]]>
+    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. ]]>
+    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;,
     When a player picks an item from a shop and attempts to
     walk over the shop mat, the item's selling-price is automatically
     subtracted from the player's money.
     <br><br>
     For money, always use the default arches.
-    Don't modify them. ]]>
+    Don't modify them.]]>
   </description>
   <attribute arch="race" value="gold and jewels" type="fixed" />
 </type>
 <!--####################################################################-->
     Monsters can behave in various kinds of ways.
     They can be aggressive, attacking the player. Or peaceful,
     helping the player - maybe joining him as pet.
     The unagressive creatures who communicate with players are
     usually called "NPCs" (Non Player Character), a well-known
-    term in role-play environments. ]]>
+    term in role-play environments.]]>
   </description>
   <use><![CDATA[
     Monsters play a central role in most maps. Choosing the right
     combination of monsters for your map is vital:
     <UL>
          can use.
     </UL>
     I know it's impossible to make the perfectly balanced map. There's always
     some part which is found too easy or too hard for a certain kind of player.
     Just give it your best shot. And listen to feedback from players if you
-    receive some. :-) ]]>
+    receive some. :-)]]>
   </use>
   <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
   <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
+    In older versions of Deliantra 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.
     It's good for low level maps, but not much more.
   </ignore>
   <description><![CDATA[
     As the name implies, mood floors can change the "mood" of
     a monsters/NPC. For example, an unagressive monster could be
     turned mad to start attacking. Similar, an agressive monster
-    could be calmed. ]]>
+    could be calmed.]]>
   </description>
   <use><![CDATA[
     Mood floors are absolutely cool for NPC interaction. To make an
     unaggressive monster/NPC attack, put a creator with "other_arch
     furious_floor" under it. Connect the creator to a magic_ear, so the
     it directly to a magic_ear. Then the player speaks a keyword like
     "help me" - and the NPC joins him as pet.
     <br><br>
     (Of course you must always give clear hints about keywords!
     And there is no reason why you couldn't use a button/lever/pedestal
-    etc. instead of a magic_ear.) ]]>
+    etc. instead of a magic_ear.)]]>
   </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:
     can monsters. Motion is involuntary. Additionally, players or
     monsters can be "frozen" while ontop of movers so that they MUST
     move along a chain of them.
     <br><br>
     Multisquare monsters can be moved as well, given
-    enough space. Movers are usually invisible. ]]>
+    enough space. Movers are usually invisible.]]>
   </description>
   <use><![CDATA[
     NEVER EVER consider a mover being unpassable in the backwards
     direction. Setting "forced movement" makes it seemingly impossible
     but there is still a trick: One player can push a second player
     cannot be discovered with the show_invisible spell.
     <br><br>
     Note that Movers and Directors are seperate objects, even though
     they look and act similar. Directors only do spells/missiles,
     while movers only do living creatures (depending on how it
-    is set: monsters and players). ]]>
+    is set: monsters and players).]]>
   </use>
   <attribute arch="attacktype" editor="forced movement" type="bool">
     If forced movement is enabled, the mover "freezes" anyone it
     moves (so they are forced to move along a chain).
     For players there is no way to escape this forced movement,
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     Pedestals are designed to detect certain types of living objects.
     When a predefined type of living creature steps on the pedestal, the
-    connected value is triggered. ]]>
+    connected value is triggered.]]>
   </description>
   <use><![CDATA[
     If you want to create a place where only players of a certain race
     can enter, put a teleporter over your pedestal. So the teleporter is
     only activated for players of the matching race. Do not use gates,
     because many other players could sneak in. If you put powerful
     artifacts into such places, generally set "startequip 1", so that
-    they are preserved for that one race and can't be traded to others. ]]>
+    they are preserved for that one race and can't be traded to others.]]>
   </use>
   <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.
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     Pits are holes, transporting the player when he walks (and falls) into them.
     A speciality about pits is that they don't transport the player to
-    the exact destination, but within a two-square radius of the destination
+    the exact destination, but within a configurable radius of the destination
     (never on blocked squares).<br>
     Optionally, pits can get closed and opened, similar to gates.<br><br>
     Monsters and items are affected by pits just as well as players.
-    Even multipart monsters can fall through them, given enough space. ]]>
+    Even multipart monsters can fall through them, given enough space.]]>
   </description>
   <use><![CDATA[
     Pits can add interesting effects to your map. When using them, make
     sure to use them in a "logical way": Pits should always drop the
     player to some kind of lower level. They should not be used to
-    randomly interconnect maps like teleporters do. ]]>
+    randomly interconnect maps like teleporters do.]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
+  <attribute arch="range" editor="random radius" type="int">
+    The radius of the square area that the pit will randomly put the player into.
+  </attribute>
   <attribute arch="connected" editor="connection" type="int">
     When a &lt;connection&gt; value is set, the pit can be opened/closed
     by activating the connection.
   </attribute>
   &activate_on;
 <!--####################################################################-->
 <type number="7" name="Poison Food">
   <description><![CDATA[
     When eating, the player's stomache is drained by 1/4 of food.
-    If his food drops to zero, the player might even die. ]]>
+    If his food drops to zero, the player might even die.]]>
   </description>
 </type>
 <!--####################################################################-->
 <type number="5" name="Potion">
   <description><![CDATA[
     The player can drink these and gain various kinds of benefits
-    (/penalties) by doing so. ]]>
+    (/penalties) by doing so.]]>
   </description>
   <use><![CDATA[
-    One potion should never give multiple benefits at once. ]]>
+    One potion should never give multiple benefits at once.]]>
   </use>
   <attribute arch="level" editor="potion level" type="int">
     If the potion contains a spell, the spell is cast at this level.
     For other potions it should be set at least to 1.
   </attribute>
 <type number="156" name="Power Crystal">
   <description><![CDATA[
     Power crystals can store a player's mana:
     When the player applies the crystal with full mana, half of
     it flows into the crystal. When the player applies it with
-    lacking mana, the crystal replenishes the player's mana. ]]>
+    lacking mana, the crystal replenishes the player's mana.]]>
   </description>
   <attribute arch="sp" editor="initial mana" type="int">
     &lt;initial mana&gt; is the amount of spellpoints that the
     crystal holds when the map is loaded.
   </attribute>
     Projectiles like arrows/crossbow bolts are used as ammunition
     for shooting weapons.
     <br><br>
     It's very easy to add new pairs of weapons &amp; projectiles.
     Just set matching &lt;ammunition class&gt; both for shooting
-    weapon and projectile. ]]>
+    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. ]]>
+    and crossbows are rarely ever used.]]>
   </use>
   <attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
     This number is a bitmask, specifying the projectile's attacktypes.
     Attacktypes are: physical, magical, fire, cold.. etc.
     This works identical to melee weapons. Note that shooting
 <type number="70" name="Ring">
   <import_type name="Amulet" />
   <description><![CDATA[
     Rings are worn on the hands - one ring each.
     Wearing rings, the object's stats will directly be inherited to
-    the player. Usually enhancing his spellcasting potential. ]]>
+    the player. Usually enhancing his spellcasting potential.]]>
   </description>
   <use><![CDATA[
     When you create an artifact ring, never forget that players can
     wear <B>two</B> rings! Due to that it is extremely important to
     keep rings in balance with the game.
     <br><br>
     Also keep in mind that rings are generally the wizard's tools.
     They should primarily grant bonuses to spellcasting abilities
-    and non-physical resistances. ]]>
+    and non-physical resistances.]]>
   </use>
 </type>
 <!--####################################################################-->
 <type number="3" name="Rod">
   </ignore>
   <description><![CDATA[
     A rod contains a spell. The player can use this spell by applying and
     fireing the rod. Rods need time to regenerate their "internal" spellpoints,
     lowering the effectiveness in combat. But unlike wands/scrolls, rods can be
-    used endlessly. ]]>
+    used endlessly.]]>
   </description>
   <use><![CDATA[
     Rods with healing/curing spells are extremely powerful. Usually, potions have
     to be used for that purpose. Though, potions are expensive and only good for
-    one-time-use.<br> ]]>
+    one-time-use.<br>]]>
   </use>
   <attribute arch="sp" editor="spell" type="spell">
     Sets the &lt;spell&gt; of the rod. Consider twice before handing out special
     rods to players, since they can be used endlessly without any mana cost!
     Rods with heal/ restoration/ protection spells, IF available, MUST be
     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.
     <br><br>
-    Many runes are already defined in the archetypes. ]]>
+    Many runes are already defined in the archetypes.]]>
   </description>
   <use><![CDATA[
     Avoid monsters stepping on your runes. For example, summoning runes
-    together with spellcasting- and  attack-runes is usually a bad idea. ]]>
+    together with spellcasting- and  attack-runes is usually a bad idea.]]>
   </use>
   <attribute arch="no_pick" 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,
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     When the player applies a savebed, he is not only saved. Both his
     respawn-after-death and his word-of-recall positions are pointing
-    to the last-applied savebed. ]]>
+    to the last-applied savebed.]]>
   </description>
   <use><![CDATA[
     Put savebed locations in towns, do not put them into dungeons.
     It is absolutely neccessary that a place with savebeds is 100% secure.
     That means:
     <LI> Insert a reliable exit! Make sure there is no possibility that
          players get trapped in a savebed location.
     <LI> If possible, mark the whole site as no-spell area (Insert this
          arch called "dungeon_magic" everywhere). This is not required,
          but it makes the place much more safe.
-    </UL> ]]>
+    </UL>]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="no_magic" value="1" type="fixed" />
   <attribute arch="damned" value="1" type="fixed" />
 </type>
   <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. ]]>
+    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. ]]>
+    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>
 <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. ]]>
+    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. ]]>
+    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.
     wielded both at the same time. Like with any other equipment,
     stats/bonuses from shooting weapons are directly inherited to the player.
     <br><br>
     It's very easy to add new pairs of weapons &amp; projectiles.
     Just set matching &lt;ammunition class&gt; both for shooting
-    weapon and projectile. ]]>
+    weapon and projectile.]]>
   </description>
   <use><![CDATA[
     Shooting weapons should not add bonuses in general. There's already
     enough "equipment-slots" doing that: swords, rings, amulets, girdles etc.
     Shooting weapons should especially not add bonuses to the player
     that have nothing to do with schooting. A Wisdom bonus on a bow
     is crap for example! A name like "Longbow of great Wisdom" doesn't help
-    - still crap. ]]>
+    - still crap.]]>
   </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".
     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
+    for every artifact you create! If zero/unset, the Deliantra server will
     calculate a provisional value at runtime, but this is never
     going to be an accurate measurement of &lt;item power&gt;.
   </attribute>
   <attribute arch="no_strength" editor="ignore strength" type="bool">
     Usually the player's strentgh takes effect on the damage
     These items are all flagged as unpaid.
     When a player drops an item onto shop floor, the item becomes
     unpaid and the player receives payment according to the item's
     selling-value.
     Shopfloor always prevents magic (To hinder players from burning
-    or freezing the goods). ]]>
+    or freezing the goods).]]>
   </description>
   <use><![CDATA[
     Tile your whole shop-interior space which shop floor.
     (That assures players receive payment for dropping items).
     Place shop mats to enter/leave the shop, and make sure
-    there is no other exit than the shop mat. ]]>
+    there is no other exit than the shop mat.]]>
   </use>
   <attribute arch="is_floor" value="1" type="fixed" />
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="no_magic" value="1" type="fixed" />
   <attribute arch="auto_apply" editor="generate goods" type="bool">
     "shopping-area" and one outside. Shop mats don't use exit paths/
     or -destinations. When stepping onto a shopmat the player gets beamed
     to the nearest other mat. If the player has unpaid items in his
     inventory, the price gets charged from his coins automatically.
     If the player has insufficient coins to buy his unpaid items, he
-    is unable to pass any shopmat (So he has to drop unpaid items). ]]>
+    is unable to pass any shopmat (So he has to drop unpaid items).]]>
   </description>
   <use><![CDATA[
     As stated above, always place TWO shop mats into your shop.
-    Not more and not less than that. ]]>
+    Not more and not less than that.]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   &move_on;
 </type>
   </ignore>
   <description><![CDATA[
     The purpose of a sign or magic_mouth is to display a certain message to
     the player. There are three ways to have the player get this message:
     The player walking onto it (-&gt; magic_mouth), the player pressing &lt;a&gt;pply
-    (-&gt; sign) or the player triggering a button/handle/etc (-&gt; magic_mouth). ]]>
+    (-&gt; sign) or the player triggering a button/handle/etc (-&gt; magic_mouth).]]>
   </description>
   <use><![CDATA[
     Use signs and magic_mouths, plenty of them! Place magic_mouths to add
     some true roleplay feeling to your maps, support your storyline or give
     hints about hidden secrets/dangers. Place signs to provide the player
-    with all kinds of useful information for getting along in your maps. ]]>
+    with all kinds of useful information for getting along in your maps.]]>
   </use>
   <attribute arch="connected" editor="connection" type="int">
     When a connection value is set, the message will be printed whenever
     the connection is triggered. This should be used in combination with
     &lt;invisible&gt; enabled and &lt;activate by walking/flying&gt; disabled.
     <ignore_list name="system_object" />
   </ignore>
   <description><![CDATA[
     Skills are objects which exist in the player/monster inventory.
     Both NPC/monsters and players use the same skill archetypes. Not all skills
-    are enabled for monster use however. ]]>
+    are enabled for monster use however.]]>
   </description>
   <use><![CDATA[
     For mapmaking, Skill objects serve two purposes:
     <p>First, the predefined skill archtypes (in the 'skills' directory)
     can be seen as the global skill definitions. A skill which doesn't
     </p><p>
     Secondly, in order to enable monsters to use skills, you will need to
     copy default skill archtypes into the monsters' inventories.
     You can even customize the skills by changing stats. It is not
     recommended however, to use skills in your maps which are totally
-    unrelated to any predefined skill archtype.</p> ]]>
+    unrelated to any predefined skill archtype.</p>]]>
   </use>
   <attribute arch="invisible" value="1" type="fixed" />
   <attribute arch="no_drop" value="1" type="fixed" />
   <attribute arch="skill" editor="skill name" type="string">
     The &lt;skill name&gt; is used for matchings. When a usable
     expmul is 1, the player will get 500 added to that skill as well as
     500 to their total.
   </attribute>
   <attribute arch="subtype" editor="skill type" type="list_skill_type">
     The &lt;skill type&gt; defines the base functionality of the skill.
-    Skill types are hardcoded in the Crossfire server. It isn't hard to
+    Skill types are hardcoded in the Deliantra server. It isn't hard to
     create new skill types, but it requires a bit of server-coding.
   </attribute>
   <attribute arch="level" editor="level" type="int">
   </attribute>
   <attribute arch="exp" editor="experience" type="int">
 <!--####################################################################-->
 <type number="130" name="Skill Scroll">
   <description><![CDATA[
     By reading a skill scroll, a player has a chance to learn the
-    contained skill. ]]>
+    contained skill.]]>
   </description>
   <use><![CDATA[
     Skill scrolls are very much sought for by players. Currently,
     all skill scrolls are sold in shops randomly, which is in fact not
     a good system. It would be nice to have some cool quests with
-    skill scrolls rewarded at the end. ]]>
+    skill scrolls rewarded at the end.]]>
   </use>
   <attribute arch="race" value="scrolls" type="fixed" />
   <attribute arch="skill" editor="skill name" type="string">
     The &lt;skill name&gt; matches the skill object that can
     be learned from this scroll.
     When carrying the appropriate special key, a locked door can
     be opened. The key will dissapear.
     <br><br>
     This object-type can also be used for "passport"-like items:
     When walking onto an invetory checker, a gate for example might
-    get opened. The "passport" will stay in the player's inventory. ]]>
+    get opened. The "passport" will stay in the player's inventory.]]>
   </description>
   <use><![CDATA[
     How to make a "passport": You take the special key arch
     (archetype name is "key2"), set the face to something like
     card.111 and the name to "passport" - that's all. The &lt;key string&gt;
     certainly must match with the appropiate inventory checker.
     <br><br>
     Of course you can be creative with names and faces of
     key-objects. A "mysterious crystal" or a "big dragon claw"
     (with appropriate faces) appear more interesting than just
-    a "strange key", or "passport". ]]>
+    a "strange key", or "passport".]]>
   </use>
   <attribute arch="slaying" editor="key string" type="string">
     This string must be identical with the &lt;key string&gt; in the
     locked door, then it can be unlocked. It can also be used
     to trigger inventory checkers.
     players can learn it by reading the book. Once learned, players
     can use the spell as often as they like. With increasing skill level
     of the player, spells may gain power but also increase cost.<br>
     Monsters can use spells which are put in their inventory (provided
     that certain "enabling" settings are correct). The monster's
-    &lt;treasurelist&gt; can also be used to provide it with spells. ]]>
+    &lt;treasurelist&gt; can also be used to provide it with spells.]]>
   </description>
   <use><![CDATA[
     A lot of the spells' settings can be tuned and customized.
     When creating new spells which are accessible to players, it is
     important to think about balance. A single spell which is too
     powerful and/or too easy to use can eventually toss the whole skill
     and magic school system out of whack. Testing new spells is
-    quite important therefore. ]]>
+    quite important therefore.]]>
   </use>
   <attribute arch="no_drop" value="1" type="fixed" />
   <attribute arch="invisible" value="1" type="fixed" />
   <attribute arch="skill" editor="skill name" type="string">
     The &lt;skill name&gt; matches the skill which is needed
     to read.<br><br>
     You can create widely customized spells only by adjusting the
     spell object in the spellbooks inventory. Refer to the description
     of spell objects for detailed information how to customize spells.<br>
     If you want to have a random spellbook instead, choose a &lt;treasurelist&gt;
-    with a compilation of spells that the book may contain. ]]>
+    with a compilation of spells that the book may contain.]]>
   </description>
   <use><![CDATA[
     Don't put any of the godgiven spells into a spellbook! These are
     reserved for the followers of the appropriate cults. Handing them
     out in a spellbook would violate the balance between different religions.
     <br><br>
     Note that there is no fundamental difference between the spellbooks
     of varying schools (pyromancy, sorcery, evocation, summoning, and
     even praying). The difference lies only in the spells they contain.
     It is up to you, the mapmaker, to pick the right type of book
-    for your spells. ]]>
+    for your spells.]]>
   </use>
   <attribute arch="skill" value="literacy" type="fixed" />
   <attribute arch="randomitems" editor="treasurelist" type="treasurelist">
     There are two ways to put spells into a spellbook:
     1. Put a spell object in the books inventory. In this case,
   </ignore>
   <description><![CDATA[
     Spinners change the direction of spell objects and other projectiles
     that fly past. Unlike directors, it does make a difference from what
     angle you shoot into the spinner. The direction of objects flying past
-    is always changed by a certain degree. ]]>
+    is always changed by a certain degree.]]>
   </description>
   <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. ]]>
+    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.
     Swamp areas show a special behaviour:
     When a player stands still on a swamp-square for too long,
     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. ]]>
+    to die in the swamp.]]>
   </description>
   <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
     different location. The main difference to the object-type exit
     is the possibility to have teleporters connected to levers/buttons/etc.
     Sometimes teleporters are activated even against the players will.
     <br><br>
     Unlike exits, teleporters can also transfer items and
-    monsters to different locations on the same map. ]]>
+    monsters to different locations on the same map.]]>
   </description>
   <use><![CDATA[
     When creating maps, I guess sooner or later you'll want to have
     an invisible teleporter. If using "invisible 1", the teleporter
     can still be discovered with the show_invisible spell. And in
     some cases you can't place it under the floor to prevent this.
     <br><br>
     Fortunately, there is a cool trick to make a perfectly invisible
     teleporter: You simply add teleporter functionality to the floor
     itself. That means: You take the floor arch (e.g. "flagstone"),
-    set "type 41", and add slaying/hp/sp/connected... everything you need. ]]>
+    set "type 41", and add slaying/hp/sp/connected... everything you need.]]>
   </use>
   <attribute arch="slaying" editor="exit path" type="string">
     The exit path specifies the map that the player is transferred to.
     &lt;exit path&gt; can be an absolute path, beginning with '/'
     (for example "/peterm/FireTemple/fire1"). It can also be a relative
 <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
+    Gates play an important role in Deliantra. 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". ]]>
+    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
     Trapdoors are very similar to pits. The difference is that they
     can not be closed. Instead, the weight of the object on the
     trapdoor determines weither it slams the trapdoor open and falls through
     or not.<br>
     Once a trapdoor has been opened (by a creature or items of sufficient
-    weight,) it remains open, acting like an opened pit. ]]>
+    weight,) it remains open, acting like an opened pit.]]>
   </description>
   <use><![CDATA[
     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. ]]>
+    are not supposed to be used to randomly interconnect maps like teleporters.]]>
   </use>
   <attribute arch="no_pick" value="1" type="fixed" />
   &move_on;
   <attribute arch="weight" editor="hold weight" type="int">
     This value defines how much weight the trapdoor can hold.
     <attribute arch="value" />
     <attribute arch="material" />
   </ignore>
   <description><![CDATA[
     A treasure-object turns into certain randomitems when the map is loaded
-    into the game. ]]>
+    into the game.]]>
   </description>
   <use><![CDATA[
     About usage of the "random-artifact" treasurelist:
     This will generate powerful stuff like girdles, xray helmets, special
     swords etc. If you put this as reward to your quest, players might be
     motivated to do it more than once. BUT, by doing so they will get a huge
     number of different artifacts! Besides, players will always seek the place
     with the most easy-to-get random artifact and ignore all others.
     My advice: Don't use it! Attract players with good fighting experience
-    (from monsters), potions, spellbooks, money, and non-random artifacts.  ]]>
+    (from monsters), potions, spellbooks, money, and non-random artifacts. ]]>
   </use>
   <attribute arch="randomitems" editor="treasurelist" type="treasurelist">
     This entry determines what kind of treasure will appear. Look into
     /crossfire/share/crossfire/treasures for details about existing
     treasurelists.
     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. ]]>
+    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. ]]>
+    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;,
     <attribute arch="name_pl" />
     <attribute arch="value" />
     <attribute arch="unpaid" />
   </ignore>
   <description><![CDATA[
-    Walls usually block passage and sight. ]]>
+    Walls usually block passage and sight.]]>
   </description>
   &movement_types_terrain;
   <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.
 <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. ]]>
+    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. ]]>
+    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">
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     A weak wall is a breakable spot amidsts a solid wall. Typically
     these weak walls look similar to their solid "relatives" except
-    for a small crack or little chunks of wall on the ground. ]]>
+    for a small crack or little chunks of wall on the ground.]]>
   </description>
   <use><![CDATA[
     If you want to create hidden rooms, using weak walls is alot
     better than completely indiscernible passages in a wall.<br>
     Anyways, there can be a lot more to weak walls than just finding
     them: Rising their defensive stats, weak walls can become a
     serious obstacle. An ice wall might only be torn down by a fire
     attack for example. A granite wall for instance might be very
-    hard to destroy. ]]>
+    hard to destroy.]]>
   </use>
   <attribute arch="alive" value="1" type="fixed" />
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="tear_down" value="1" type="fixed" />
   <attribute arch="race" editor="race" type="string">
 <!--####################################################################-->
 <type number="15" name="Weapon">
   <description><![CDATA[
     Wielding a weapon, the object's stats will directly be inherited to the
     player. Usually enhancing his fighting-abilities. Non-magical weapons can
-    be improved with scrolls. ]]>
+    be improved with scrolls.]]>
   </description>
   <use><![CDATA[
     If you create artifacts (equipment) with stats- or resistance-bonus:
     Keep playbalance in mind! Such items mustn't be reachable without hard
-    fighting AND questing. ]]>
+    fighting AND questing.]]>
   </use>
   <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
     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
+    for every artifact you create! If zero/unset, the Deliantra server will
     calculate a provisional value at runtime, but this is never
     going to be an accurate measurement of &lt;item power&gt;.
   </attribute>
   <attribute arch="damned" editor="damnation" type="bool">
     A damned weapon cannot be unwielded unless
 </type>
 <type number="116" name="Event Connector">
   <description><![CDATA[
     Event connectors link specific events that happen to objects to
-    a crossfire plug-in. ]]>
+    a crossfire plug-in. They are not used at all in Deliantra.]]>
   </description>
-  <attribute arch="subtype" editor="event type" type="list_event_type">
-    The type of event that triggers a notify to the plug-in.
-  </attribute>
-  <attribute arch="title" editor="plug-in" type="string">
-    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="name" editor="options" type="string">
-    A string that is passed unaltered to the extension above. Often used to pass
-    options to the extension that alter its behaviour.
-  </attribute>
 </type>
 </types>

Diff Legend

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

Comparing deliantra/Deliantra/res/types.xml (file contents): Revision 1.31 by root, Mon Sep 17 17:23:16 2007 UTC vs. Revision 1.37 by root, Tue Aug 26 01:58:06 2008 UTC

Diff Legend

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.31 by root, Mon Sep 17 17:23:16 2007 UTC vs.
Revision 1.37 by root, Tue Aug 26 01:58:06 2008 UTC