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

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.45 by root, Thu Jan 8 03:05:17 2009 UTC vs.
Revision 1.52 by root, Wed Oct 21 00:16:24 2009 UTC

      <attribute arch='move_type' editor='movement type' type='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 "
+  <!ENTITY move_block "
      <attribute arch='move_block' editor='blocked movement' type='movement_type'>
        Objects using these movement types cannot move over this space.
      </attribute>
+  ">
+  <!ENTITY movement_types_terrain "
+     &move_block;
      <attribute arch='move_allow' editor='allowed movement' type='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='movement_type'>
           &player_res_desc;
         </attribute>
       </section>
    ">
+  <!ENTITY match_compat "
+    If the string starts with 'match ', then it is interpreted
+    as a match expression (e.g. 'match type=POTION', or 'match type=SPELL
+    in applied type=CONTAINER in inv in originator'). For details, see
+    http://pod.tst.eu/http://cvs.schmorp.de/deliantra/server/lib/cf/match.pm
+  ">
 ]>
 <types>
 <!--###################### bitmask definitions ######################-->
     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 emit.
+    between 0 and 9, 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.
     Putting an invisible object under the floor always prevents it from being
     shown.
   </attribute>
   <attribute arch="blocksview" editor="block view" type="bool">
     If an item is set to block view, players (and monsters) cannot
-    see byond it unless they cross it or manage to stand ontop.
+    see beyond it unless they cross it or manage to stand ontop.
   </attribute>
   <attribute arch="identified" editor="identified" type="bool">
     If an item is identified, the player has full knowledge about it.
   </attribute>
   <attribute arch="unpaid" editor="unpaid" type="bool">
     Note that non-magical abilities are more dangerous because
     magic resistance does not protect from those.</attribute>
 </type>
 <!--####################################################################-->
+<type number="81" name="Torch">
+  <description><![CDATA[
+    Torches are a special kind of Lamp, they are worn out by repeatedly
+    lightening them up (when the is_lightable flag is set) and otherwise
+    they can only be used once.]]>
+  </description>
+  <attribute arch="food" editor="burning duration" type="int">
+     This field specifies the burning duration of the torch.
+  </attribute>
+  <attribute arch="range" editor="enabled glow radius" type="int">
+     This field sets the glow radius of the torch if it is enabled.
+     If you want to make a torch that is already burning set the
+     "glow radius" field.
+  </attribute>
+  <attribute arch="level" editor="level" type="int">
+    If this field specyfies the cursed effect's level. If it is
+    0 no cursed effect will be generate. See also the "cursed" flag.
+  </attribute>
+  <attribute arch="cursed" editor="cursed" type="bool">
+    Cursed torches, which have a level above 0, explode if the
+    player applies them.
+  </attribute>
+</type>
+<type number="82" name="Lamp">
+  <description><![CDATA[
+    Lamps are carryable light sources for players with a fuel tank.]]>
+  </description>
+  <attribute arch="speed" editor="burn speed" type="float">
+     This field is the speed of the lamp. (If the value 0.00208 is given
+     here the fuel field will specify the burning duration in minutes.)
+  </attribute>
+  <attribute arch="food" editor="fuel" type="int">
+     This field sets the burning duration of the lamp, which depends on the speed
+     field of this object.
+  </attribute>
+  <attribute arch="range" editor="enabled glow radius" type="int">
+     This field sets the glow radius of the lamp if it is enabled.
+     If you want to make a lamp that is already burning set the
+     "glow radius" field.
+  </attribute>
+  <attribute arch="level" editor="level" type="int">
+    If this field specyfies the cursed effect's level. If it is
+    0 no cursed effect will be generate. See also the "cursed" flag.
+  </attribute>
+  <attribute arch="cursed" editor="cursed" type="bool">
+    Cursed lamps, which have a level above 0, explode if the
+    player applies them.
+  </attribute>
+</type>
+<!--####################################################################-->
 <type number="18" name="Altar">
   <ignore>
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
     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.
     If you want the player to have to drop a specific amount of money use "money".
     See also the "drop amount" attribute.
+    &match_compat;
   </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.
     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.
     If you want the player to have to drop a specific amount of money use "money".
     See also the "drop amount" attribute.
+    &match_compat;
   </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.
     item with by using a skill.
   </attribute>
 </type>
 <!--####################################################################-->
+<type number="110" name="Inscribable">
+  <description><![CDATA[
+    Inscribable Item - when inscribed, it becomes another object.]]>
+  </description>
+  <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="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.
+  </attribute>
+  <attribute arch="other_arch" editor="book/scroll arch" type="string">
+     This is the item created after being inscribed - scrolls are treated
+     like spell scrolls, all else will have it's message replaced.
+  </attribute>
+</type>
+<!--####################################################################-->
 <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
     Detectors work quite much like inv. checkers/pedestals: If the detector
     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, so generate much higher server load
-    instantly. Second, detectors check directly for object names. Third,
+    Second, detectors check directly for object names. Third,
     detectors do not check the inventory of players/monsters.]]>
   </description>
-  <use><![CDATA[
+  <use>
-    There is one major speciality about detectors: You can detect spells
+    Best avoid this type at all costs, use a pedestal instead.
-    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.]]>
   </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,
   <ignore>
     <ignore_list name="system_object" />
   </ignore>
   <description><![CDATA[
     The map script object is a very special object that can react to connected
-    events and executes a perl script.
+    events and executes a perl script in the msg slot.
   ]]>
   </description>
   <use><![CDATA[
-    The perl script gets passed an $activator object and can use the set/get/find/timer functions
+    The perl script gets passed a $state value and $activator, $self, $originator objects and can use the set/get/find/timer functions
-    to react to/trigger other objects.
+    to react to/trigger other objects. See http://pod.tst.eu/http://cvs.schmorp.de/deliantra/server/lib/cf/mapscript.pm for details.
   ]]>
   </use>
   <attribute arch="connected" editor="connection" type="string">
      When the map script object is triggered, it will execute
      the perl script with the triggering object as $activator.
     If enabled, it is impossible for players to use prayers
     on that spot. It also prevents players from saving.
   </attribute>
   <attribute arch="unique" editor="unique map" type="bool">
     Unique floor means that any items dropped on that spot
-    will be saved byond map reset. For permanent apartments,
+    will be saved beyond map reset. For permanent apartments,
     all floor tiles must be set &lt;unique map&gt;.
   </attribute>
   <attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
     This text may describe the object.
   </attribute>
     If enabled, it is impossible for players to use prayers
     on that spot. It also prevents players from saving.
   </attribute>
   <attribute arch="unique" editor="unique map" type="bool">
     Unique floor means that any items dropped on that spot
-    will be saved byond map reset. For permanent apartments,
+    will be saved beyond map reset. For permanent apartments,
     all floor tiles must be set &lt;unique map&gt;.
   </attribute>
   <attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
     This text may describe the object.
   </attribute>
     If enabled, it is impossible for players to use prayers
     on that spot. It also prevents players from saving.
   </attribute>
   <attribute arch="unique" editor="unique map" type="bool">
     Unique floor means that any items dropped on that spot
-    will be saved byond map reset. For permanent apartments,
+    will be saved beyond map reset. For permanent apartments,
     all floor tiles must be set &lt;unique map&gt;.
   </attribute>
 </type>
 <!--####################################################################-->
 <type number="56" name="Holy Altar">
   <ignore>
     <ignore_list name="non_pickable" />
   </ignore>
   <description><![CDATA[
-    Holy_altars are altars for the various religions. Praying
+    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.]]>
   </description>
   <attribute arch="no_pick" value="1" type="fixed" />
   <attribute arch="other_arch" editor="god name" type="string">
     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.
+    &match_compat;
   </attribute>
   <attribute arch="connected" editor="connection" type="string">
     When the pedestal is triggered, all objects with the same
     connection value get activated.
   </attribute>
   &move_on;
+</type>
+<!--####################################################################-->
+<type number="19" name="Item Match">
+  <ignore>
+    <ignore_list name="non_pickable" />
+  </ignore>
+  <description><![CDATA[
+    Match objects use the deliantra matching language
+    (http://pod.tst.eu/http://cvs.schmorp.de/deliantra/server/lib/cf/match.pm)
+    to match items on the same mapspace (if move_on/off are unset) or
+    items trying to enter (if move_blocked is set).
+    If a connected value is given, then it is triggered if the first object
+    matching the expression is put on it, and the last is removed.]]>
+  </description>
+  <use><![CDATA[
+    If you want to trigger something else (e.g. a gate) when an item is above this object,
+    use the move_on/move_off settings.
+    If you want to keep something from entering if it has (or lacks) a specific item,
+    use the move_blocked setting.]]>
+  </use>
+  <attribute arch="no_pick" value="1" type="fixed" />
+  <attribute arch="slaying" editor="match expression" type="string">
+    &match_compat;
+    Optionally you can leave out the "match " prefix.
+  </attribute>
+  <attribute arch="connected" editor="connection" type="string">
+    When the match is triggered, all objects with the same
+    connection value get activated.
+  </attribute>
+  &move_on;
+  &move_off;
+  &move_block;
 </type>
 <!--####################################################################-->
 <type number="94" name="Pit">
   <ignore>

Diff Legend

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

Comparing deliantra/Deliantra/res/types.xml (file contents): Revision 1.45 by root, Thu Jan 8 03:05:17 2009 UTC vs. Revision 1.52 by root, Wed Oct 21 00:16:24 2009 UTC

Diff Legend

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.45 by root, Thu Jan 8 03:05:17 2009 UTC vs.
Revision 1.52 by root, Wed Oct 21 00:16:24 2009 UTC