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

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.11 by root, Thu Mar 23 20:15:08 2006 UTC vs.
Revision 1.20 by elmex, Thu Aug 31 21:09:33 2006 UTC

        &lt;slow movement&gt; 5  - default for deep swamp
        ...
        &lt;slow movement&gt; 7  - spider web (sticky as hell)
      </attribute>
   ">
+  <!ENTITY speed_left "
+     <attribute arch='speed_left' editor='speed left' type='float'>
+        The speed left to the object. On every tick, if this value is higher
+        than 0, the object acts/triggers/moves etc. and the value gets
+        decremented by 1. Otherwise, it is incremented by &lt;speed&gt; on
+        every tick.
+     </attribute>
+  ">
+  <!ENTITY activate_on "
+     <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'>
+       Whether the teleporter should only be activated on release.
+     </attribute>
+  ">
 ]>
 <types>
 <!--###################### bitmask definitions ######################-->
   <entry value="9" name="throw" />
   <entry value="10" name="trigger" />
   <entry value="11" name="close" />
   <entry value="12" name="timer" />
   <entry value="28" name="move" />
+  <entry value="41" name="drop_on" />
 </list>
 <list name="attack_movement_bits_0_3">
    <entry value="0" name="default" />
    <entry value="1" name="attack from distance" />
     zero weight are not pickable for players. Still, set the "non-pickable"-flag
     for explicitly non-pickable objects (hey, this is opensource.. you
     never know ;) ).
   </attribute>
   <attribute arch="value" editor="value" type="int">
-    Adds a certain value to the object: It will be worth that many times the
+    Determines the value of the object, in units of silver coins (one
-    default value from it's archetype (E.g. "value = 3" means three times
+    platinum coin == 50 silver coins). Value for buying/selling will be
-    worth the default value). Value for buying/selling will be
     further modified by various factors. Hence, testing values in-game is
     usually inevitable.
   </attribute>
   <attribute arch="glow_radius" editor="glow radius" type="int">
     If &lt;glow radius&gt; is set to a value greater zero, the object
     get teleported after they died on this battleground.
   </attribute>
 </type>
 <!--####################################################################-->
+<type number="165" name="Safe ground (CF+)">
+  <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>
+  <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. ]]>
   </description>
   <attribute arch="level" editor="literacy level" type="int">
   </attribute>
   <attribute arch="connected" editor="connection" type="int">
     Whenever the connection value is activated,
     the creator gets triggered.
   </attribute>
+  &activate_on;
   <attribute arch="lifesave" editor="infinit uses" type="bool">
     If &lt;infinit uses&gt; is set, the creator will work
     infinitely, regardless of the value in &lt;number of uses&gt;.
   </attribute>
   <attribute arch="hp" editor="number of uses" type="int">
   </attribute>
   <attribute arch="speed" editor="detection speed" type="float">
     This value defines the time between two detector-checks.
     If you want the detector to behave almost like pedestals/buttons,
     set speed rather high, like &lt;detection speed&gt; 1.0.
+  </attribute>
+  &speed_left;
+  <attribute arch="speed_left" editor="speed left" type="float">
+    The speed left. This value is incremented by &lt;speed&gt; on every tick.
+    If it is larger than 0, the detector checks, and the speed is decremented
+    by 1.
   </attribute>
 </type>
 <!--####################################################################-->
 <type number="112" name="Director">
   </attribute>
   <attribute arch="speed" editor="moving speed" type="float">
     The &lt;speed&gt; of the disease determines how fast the disease will
     "move", thus how fast the symptoms strike the host.
   </attribute>
+  &speed_left;
 </section>
 <section name="symptoms">
   <attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
     The disease will attack the host with the given &lt;attacktype&gt;.
     Godpower attacktype is commonly used for "unresistable" diseases.
     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%. ]]>
   </use>
   <attribute arch="other_arch" editor="target arch" type="string">
-    Only objects of matching archtype, lying ontop of the dublicator will be
+    Only objects of matching archtype, lying ontop of the duplicator will be
-    dublicated, multiplied or removed. All other objects will be ignored.
+    duplicated, multiplied or removed. All other objects will be ignored.
   </attribute>
   <attribute arch="level" editor="multiply factor" type="int">
     The number of items in the target pile will be multiplied by the
     &lt;multiply factor&gt;. If it is set to zero, all target objects
     will be destroyed.
   <attribute arch="connected" editor="connection" type="int">
     An activator (lever, altar, button, etc) with matching connection value
     is able to trigger this duplicator. Be very careful that players cannot
     abuse it to create endless amounts of money or other valuable stuff!
   </attribute>
+  &activate_on;
 </type>
 <!--####################################################################-->
 <type number="66" name="Exit">
   <ignore>
   <description><![CDATA[
     Just like with food, the player can fill his stomache and gain a
     little health by eating flesh-objects. <br>
     For dragon players, flesh plays a very special role though: If the
     flesh has resistances set, a dragon player has a chance to gain resistance in
-    those cathegories. The only constraint to this process is the &lt;flesh level&gt;.
+    those categories. The only constraint to this process is the &lt;flesh level&gt;.
     Don't forget that flesh items with resistances have to be balanced
     according to map/monster difficulty. ]]>
   </description>
   <use><![CDATA[
     For dragon players, flesh items can be highly valuable. Note that many
     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". ]]>
   </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>
   <attribute arch="connected" editor="connection" type="int">
     Whenever the inventory checker is triggered, all objects with identical
     &lt;connection&gt; value get activated. This only makes sense together with
     &lt;blocking passage&gt; disabled.
   </attribute>
   <attribute arch="level" editor="reconsecrate level" type="int">
     To re-consecrate an altar, the player's wisdom level must be as
     high or higher than this value. In that way, some altars can not
     be re-consecrated, while other altars, like those in dungeons, could be.
-    Altars located in temples should have at least &lt;reconsecrate level&gt; 100.
+    Altars located in temples should have at least &lt;reconsecrate level&gt; 120.
     Some characters might need those altars, they would be very unhappy to
     see them re-consecrated to another cult.
   </attribute>
 </type>
   <attribute arch="connected" editor="connection" type="int">
     Every time the &lt;connection&gt; value is triggered, the wall will cast
     it's spell. You should set &lt;casting speed&gt; to zero, or this won't
     have much visible effect.
   </attribute>
+  &activate_on;
   <attribute arch="speed" editor="casting speed" type="float">
     The &lt;casting speed&gt; defines the spellcasting speed of the wall.
     You can fine-tune how long the duration between two casts shall
     be. If you want to create a wall that can be activated (cast per
     trigger) via connected lever/button/etc, you must set "speed 0".
   </attribute>
+  &speed_left;
   <attribute arch="sp" editor="direction" type="list_direction">
     The magic wall will cast it's spells always in the specified
     &lt;direction&gt;. A magic wall with direction set to &lt;none&gt; will
     always fire in a random direction.
   </attribute>
     The &lt;marking speed&gt; defines how quickly it will mark something
     standing on the marker. Set this value rather high to make
     sure the player really gets his mark. I think &lt;marking speed&gt; 1.0
     should do fine.
   </attribute>
+  &speed_left;
   <attribute arch="food" editor="mark duration" type="int">
     This value defines the duration of the force it inserts.
     If nonzero, the duration of the player's mark is finite:
     about 1 food per 10 seconds. &lt;mark duration&gt; zero/unset
     means the mark will stay on the player forever.
   <attribute arch="level" editor="level" type="int">
     A monster's &lt;level&gt; is the most important attribute.
     &lt;level&gt; affects the power of a monster in various ways.
   </attribute>
   <attribute arch="race" editor="race" type="string">
-    Every monster should have a race set to cathegorize it.
+    Every monster should have a race set to categorize it.
     The monster's &lt;race&gt; can have different effects:
     Slaying weapons inflict tripple damage against enemy races
     and holy word kills only enemy races of the god.
   </attribute>
   <attribute arch="exp" editor="experience" type="int">
     When a player kills this monster, he will get exactly this
     amount of &lt;experience&gt;. The experience will flow into
-    the skill-cathegory the player used for the kill.
+    the skill-category the player used for the kill.
     If you create special monsters of tweaked strenght/abilities,
     always make sure that the &lt;experience&gt; is set to a
     reasonable value. Compare with existing arches to get a feeling
     what reasonable means. Keep in mind that spellcasting monsters
   </attribute>
   <attribute arch="speed" editor="speed" type="float">
     The &lt;speed&gt; determines how fast a monster will both move
     and fight. High &lt;speed&gt; makes a monster considerably stronger.
   </attribute>
+  &speed_left;
   <attribute arch="other_arch" editor="breed monster" type="string">
     This only takes effect if &lt;multiply&gt; is enabled. The monster will
     create a &lt;breed monster&gt; every once in a while. &lt;breed monster&gt;
     can be set to any valid arch-name of a monster. Multipart monster
     should not be used.
   </attribute>
   <attribute arch="speed" editor="movement speed" type="float">
     The movement speed value determines how fast a chain of
     these movers will push a player along (default is -0.2).
   </attribute>
+  &speed_left;
   <attribute arch="sp" editor="direction" type="list_direction">
     The mover will push creatures in the specified &lt;direction&gt;.
     A mover with direction set to &lt;none&gt; will spin clockwise,
     thus pushing creatures in unpredictable directions.
   </attribute>
   <attribute arch="no_pick" value="1" type="fixed" />
   <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;
   <attribute arch="hp" editor="destination X" type="int">
     The pit will transport creatures (and items) randomly into a two-square
     radius of the destination coordinates.
     If the destination square becomes blocked, the pit will act like
     being filled up and not work anymore!
 </type>
 <!--####################################################################-->
 <type number="14" name="Shooting Weapon">
   <description><![CDATA[
-    Schooting weapons like bows/crossbows are used to shoot projectiles
+    Shooting weapons like bows/crossbows are used to shoot projectiles
     (arrows/bolts). Shooting weapons and normal (melee) weapons can be
     wielded both at the same time. Like with any other equipment,
     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.
     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.
-    Schooting weapons should especially not add bonuses to the player
+    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. ]]>
   </use>
   <attribute arch="race" editor="ammunition class" type="string">
     the connection is triggered. This should be used in combination with
     &lt;invisible&gt; enabled and &lt;activate by walking/flying&gt; disabled.
     If activating your magic_mouth this way, the message will not only be
     printed to one player, but all players on the current map.
   </attribute>
+  &activate_on;
   &move_on;
   <attribute arch="food" editor="counter" type="int">
     If a counter-value is set (greater zero), the sign/magic_mouth can be applied
     (printing the message) only that many times. For signs this really shouldn't
     be used, while for magic_mouths it is extremely helpful.
   <attribute arch="speed" editor="drowning speed" type="float">
     The higher the &lt;drowning speed&gt;, the faster will players and items
     sink into the swamp. Swamp with very high &lt;drowning speed&gt; can be a nasty
     and unexpected death-trap. Players should get a warning before such areas.
   </attribute>
+  &speed_left;
   &move_on;
   &movement_types_terrain;
   <attribute arch="no_magic" editor="no spells" type="bool">
     If enabled, it is impossible for players to use (wizard-)
     spells on that spot.
   <attribute arch="connected" editor="connection" type="int">
     If a connection value is set, the teleporter will be activated
     whenever the connection is triggered. To use this properly,
     &lt;activation speed&gt; must be zero.
   </attribute>
+  &activate_on;
   <attribute arch="speed" editor="activation speed" type="float">
     If the &lt;activation speed&gt; is nonzero, the teleporter will
     automatically be activated in regular time-intervals. Hence, the
     player can just step on it and gets teleported sooner or later.
     The duration between two activates depends on the given value.
     Default in the teleporter arch is &lt;activation speed&gt; 0.1.
     VERY IMPORTANT: If you want to have your teleporter activated via
     button/handle/magic_ear/etc, you must set &lt;activation speed&gt; to zero!
   </attribute>
+  &speed_left;
 </type>
 <!--####################################################################-->
 <type number="26" name="Timed Gate">
   <ignore>
     Whenever the inventory checker is triggered, all objects with identical
     &lt;connection&gt; value get activated. This only makes sense together with
     &lt;blocking passage&gt; disabled. If unset, the gate opens automatically
     after some time.
   </attribute>
+  &activate_on;
   <attribute arch="wc" editor="position state" type="int">
     The &lt;position state&gt; defines the position of the gate:
     Zero means completely open/down, the "number of animation-steps" (usually
     about 6 or 7) means completely closed/up state. I suggest you don't
     mess with this value - Leave the default in place.
 <!--####################################################################-->
 <type number="0" name="Wall">
   <required>
     <attribute arch="is_floor" value="0" />
     <attribute arch="alive" value="0" />
-    <attribute arch="move_block" value="255" />
+    <attribute arch="no_pass" value="1" />
   </required>
   <ignore>
     <attribute arch="nrof" />
     <attribute arch="title" />
     <attribute arch="name_pl" />

Diff Legend

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

Comparing deliantra/Deliantra/res/types.xml (file contents): Revision 1.11 by root, Thu Mar 23 20:15:08 2006 UTC vs. Revision 1.20 by elmex, Thu Aug 31 21:09:33 2006 UTC

Diff Legend

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.11 by root, Thu Mar 23 20:15:08 2006 UTC vs.
Revision 1.20 by elmex, Thu Aug 31 21:09:33 2006 UTC