[ViewVC] Diff of: cvs/deliantra/Deliantra/Deliantra/Data.pm

Comparing deliantra/Deliantra/Deliantra/Data.pm (file contents):
Revision 1.4 by root, Wed Feb 22 22:36:45 2006 UTC vs.
Revision 1.5 by root, Wed Feb 22 22:41:22 2006 UTC

     },
     desc => 'Abilities are to be put in a monster\'s inventory. They grant monsters the knowledge to cast spells. Spells from abilities are usually magical in nature, thus adding magic attacktype to the spell-damage they produce. <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;.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Ability',
     use => '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 interesting and challenging. <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?'
   },
   Altar => {
     attr => {
       connected => {
       }
     },
     desc => 'When a player puts a defined number of certain items on the altar, then either a spell is casted (on the player) or a connector is triggered. If the latter is the case, the altar works only once. Either way, the sacrificed item dissapears.',
     ignore => [
       $IGNORE_LIST{non_pickable}
-    ]
+    ],
+    name => 'Altar'
   },
   'Altar Trigger' => {
     attr => {
       connected => {
 	desc => 'If a connection value is set, the altar will trigger all objects with the same value, when activated. This will only work once.',
     },
     desc => 'Altar_triggers work pretty much like normal altars (drop sacrifice -> connection activated), except for the fact that they reset after usage. Hence, altar_triggers can be used infinitly.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Altar Trigger',
     use => '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. =)'
   },
   Amulet => {
     attr => {
       ac => {
 	name => 'weapon class',
 	type => 'int'
       }
     },
     desc => 'Wearing an amulet, the object\'s stats will directly be inherited to the player. Amulets are usually meant for protection and defense.',
+    name => 'Amulet',
     section => [
       [
 	'resistance',
 	{
 	  resist_acid => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Battleground',
     use => '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 open dungeons or other free kinds of land. 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.)'
   },
   Book => {
     attr => {
       level => {
 	desc => 'Unique items exist only one time on a server. If the item is taken, lost or destroyed - it\'s gone for good.',
 	name => 'unique item',
 	type => 'bool'
       }
     },
-    desc => 'Applying a book, the containing message is displayed to the player.'
+    desc => 'Applying a book, the containing message is displayed to the player.',
+    name => 'Book'
   },
   Boots => {
     attr => {
       exp => {
 	desc => 'Boots with <speed bonus> 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 walking speed and thus don\'t need <speed bonus> anymore. Still, this bonus is good for nice artifacts - not everything has to be for highest level.',
     },
     desc => 'Wearing boots, the object\'s stats will directly be inherited to the player. Usually enhancing his speed, or granting some minor protection bonus.',
     import => [
       $TYPE{Amulet}
     ],
+    name => 'Boots',
     use => 'Feel free to create your own special artifacts. However, it is very important that you keep your artifact in balance with existing maps.'
   },
   Bracers => {
     attr => {
       magic => {
     },
     desc => '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.',
     import => [
       $TYPE{Amulet}
     ],
+    name => 'Bracers',
     use => 'Feel free to create your own special artifacts. However, it is very important that you keep your artifact in balance with existing maps.'
   },
   'Brestplate Armour' => {
     attr => {
       last_heal => {
     },
     desc => 'Wearing an armour, the object\'s stats will directly be inherited to the player. Usually enhancing his defense.',
     import => [
       $TYPE{Amulet}
     ],
+    name => 'Brestplate Armour',
     use => 'Feel free to create your own special artifacts. However, it is very important that you keep your artifact in balance with existing maps.'
   },
   Button => {
     attr => {
       connected => {
       }
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
-    ]
+    ],
+    name => 'Button'
   },
   Cloak => {
     attr => {
       magic => {
 	desc => '<magic bonus> works just like ac, except that it can be improved by "scrolls of Enchant Armour" or reduced by acid. It is less useful than direct armour-class bonus on the cloak. Important: <magic bonus> on cloaks has no effect if there is no <armour class> set. It only works in combination with <armour class>.',
     },
     desc => '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.',
     import => [
       $TYPE{Amulet}
     ],
+    name => 'Cloak',
     use => 'Feel free to create your own special artifacts. However, it is very important that you keep your artifact in balance with existing maps.'
   },
   Clock => {
     attr => {
       msg => {
 	end => 'endmsg',
 	name => 'description',
 	type => 'text'
       }
     },
-    desc => 'Applying a clock, the time is displayed to the player.'
+    desc => 'Applying a clock, the time is displayed to the player.',
+    name => 'Clock'
   },
   Container => {
     attr => {
       Str => {
 	desc => 'This value determines how much the weight of items is reduced in percent, when put inside the container. <reduce weight %> 0 means no reduction, <reduce weight %> 100 means items are weightless inside. Most default values are in the range of ten.',
 	name => 'unique item',
 	type => 'bool'
       }
     },
     desc => '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.',
+    name => 'Container',
     use => '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>'
   },
   Converter => {
     attr => {
       food => {
       'name_pl',
       'no_pick',
       'unpaid',
       'title'
     ],
+    name => 'Converter',
     use => '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 stuff like potions converters should not exist. <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.'
   },
   Creator => {
     attr => {
       connected => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Creator',
     use => 'Don\'t hesitate to hide your creators under the floor. The created items will still always appear ontop of the floor.'
   },
   Detector => {
     attr => {
       connected => {
     },
     desc => '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. Second, detectors check directly for object names. Third, detectors do not check the inventory of players/monsters.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Detector',
     use => '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.'
   },
   Director => {
     attr => {
       fly_on => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Director',
     use => '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, <B>never place directors facing each other with magic walls fireing 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.'
   },
   Disease => {
     attr => {
       ac => {
     },
     desc => 'Diseases are an intersting form of spellcraft in Crossfire. 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.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Disease',
     section => [
       [
 	'spreading',
 	{
 	  last_grace => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Duplicator',
     use => '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%.'
   },
   Exit => {
     attr => {
       fly_on => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Exit',
     use => '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.'
   },
   Flesh => {
     attr => {
       food => {
 	name => 'godgiven item',
 	type => 'bool'
       }
     },
     desc => '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;. Don\'t forget that flesh items with resistances have to be balanced according to map/monster difficulty.',
+    name => 'Flesh',
     section => [
       [
 	'resistance',
 	{
 	  resist_acid => {
     },
     desc => 'Floor is a very basic thing whithout too much functionality. It\'s a floor - you stand on it.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Floor',
     required => {
       alive => 0,
       is_floor => 1
     },
     section => [
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Floor (Encounter)',
     section => [
       [
 	'terrain',
 	{
 	  is_hilly => {
 	desc => 'A godgiven item vanishes as soon as the player drops it to the ground.',
 	name => 'godgiven item',
 	type => 'bool'
       }
     },
-    desc => 'By eating/drinking food-objects, the player can fill his stomache and gain a little health.'
+    desc => 'By eating/drinking food-objects, the player can fill his stomache and gain a little health.',
+    name => 'Food'
   },
   Gate => {
     attr => {
       connected => {
 	desc => 'Whenever the inventory checker is triggered, all objects with identical <connection> value get activated. This only makes sense together with <blocking passage> disabled.',
     },
     desc => 'Gates play an important role in Crossfire. Gates can be opened by activating a button/trigger, by speaking passwords (-> magic_ear) or carrying special key-objects (-> inventory checker). Unlike locked doors, gates can get shut again after a player has passed, which makes them more practical in many cases.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Gate',
     use => '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".'
   },
   Girdle => {
     attr => {
       magic => {
     },
     desc => 'Wearing a girdle, the object\'s stats will directly be inherited to the player. Girdles usually provide stats- or damage bonuses and no defense.',
     import => [
       $TYPE{Amulet}
     ],
+    name => 'Girdle',
     use => 'Feel free to create your own special artifacts. However, it is very important that you keep your artifact in balance with existing maps.'
   },
   Gloves => {
     attr => {
       magic => {
     },
     desc => 'Wearing gloves, the object\'s stats will directly be inherited to the player. Gloves can add defense or damage bonuses.',
     import => [
       $TYPE{Amulet}
     ],
+    name => 'Gloves',
     use => 'Feel free to create your own special artifacts. However, it is very important that you keep your artifact in balance with existing maps.'
   },
   Handle => {
     attr => {
       connected => {
     },
     desc => 'A handle can be applied by players and (certain) monsters. Every time it is applied, the &lt;connection&gt; value is triggered.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Handle',
     use => '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.'
   },
   'Handle Trigger' => {
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
     import => [
       $TYPE{Handle}
     ],
+    name => 'Handle Trigger',
     use => '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.'
   },
   'Hazard Floor' => {
     attr => {
       attacktype => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Hazard Floor',
     required => {
       is_floor => 1
     },
     section => [
       [
     },
     desc => '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.',
     import => [
       $TYPE{Amulet}
     ],
+    name => 'Helmet',
     use => 'Feel free to create your own special artifacts. However, it is very important that you keep your artifact in balance with existing maps.'
   },
   'Holy Altar' => {
     attr => {
       level => {
       }
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
-    ]
+    ],
+    name => 'Holy Altar'
   },
   Horn => {
     attr => {
       hp => {
 	desc => 'This value represents the initial amount of spellpoints in the horn. Naturally, this is quite unimportant.',
     },
     desc => '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.',
     ignore => [
       'title'
     ],
+    name => 'Horn',
     use => '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.'
   },
   Inorganic => {
     attr => {
       is_dust => {
 	name => 'is dust',
 	type => 'bool'
       }
     },
     desc => 'Inorganic materials are generally used as ingredients for alchemical receipes. By themselves, they have no special functionalities.',
+    name => 'Inorganic',
     section => [
       [
 	'resistance',
 	{
 	  resist_acid => {
     },
     desc => 'Inventory checkers passively check the players inventory for a specific object. You can set a connected value that is triggered either if that object is present or missing (-&gt; "last_sp") when a player walks over the inv. checker. A valid option is to remove the matching object (usually not recommended, see "last_heal"). <br><br> Alternatively, you can set your inv. checker to block all players that do/don\'t carry the matching object (-&gt; "no_pass"). <br><br> As you can see, inv. checkers are quite powerful, holding a great variety of possibilities.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Inventory Checker',
     use => '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.'
   },
   Jewel => {
     attr => {
       msg => {
       },
       race => {
 	type => 'fixed'
       }
     },
-    desc => '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.'
+    desc => '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.',
+    name => 'Jewel'
   },
   'Locked Door' => {
     attr => {
       damned => {
 	desc => 'Restricting the use of prayers to pass this door. This should be set in most cases.',
     },
     desc => 'A locked door can be opened only when carrying the appropriate special key.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Locked Door',
     use => '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).'
   },
   'Magic Ear' => {
     attr => {
       connected => {
     },
     desc => 'Magic_ears trigger a connected value when the player speaks a specific keyword.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Magic Ear',
     use => '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 "sesame", expecting the player to figure this out all by himself. <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.'
   },
   'Magic Wall' => {
     attr => {
       connected => {
     },
     desc => 'Magic walls fire spells in a given direction, in regular intervals. 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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Magic Wall',
     section => [
       [
 	'destroyable',
 	{
 	  ac => {
     },
     desc => 'A marker is an object that inserts an invisible force (a mark) into a 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.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Marker',
     use => '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.'
   },
   Misc => {
     attr => {
       cursed => {
       unique => {
 	desc => 'Unique items exist only one time on a server. If the item is taken, lost or destroyed - it\'s gone for good.',
 	name => 'unique item',
 	type => 'bool'
       }
-    }
+    },
+    name => 'Misc'
   },
   Money => {
     attr => {
       race => {
 	type => 'fixed'
       }
     },
     desc => 'Items of the type Money are handled as currency. Money cannot be sold/bought in shops. When money is dropped in a shop, it stays the same.<br> 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.',
     ignore => [
       'unpaid'
-    ]
+    ],
+    name => 'Money'
   },
   'Monster & NPC' => {
     attr => {
       alive => {
 	type => 'fixed'
       'name_pl',
       'nrof',
       'value',
       'unpaid'
     ],
+    name => 'Monster & NPC',
     required => {
       alive => 1,
       is_floor => 0,
       tear_down => 0
     },
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Mood Floor',
     use => '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 player speaks a keyword like "stupid sucker" - and the monster attacks. <br><br> To turn an NPC into a pet, put a charm_floor under it and connect 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.)'
   },
   Mover => {
     attr => {
       attacktype => {
     },
     desc => 'Movers move the objects above them. However, only living objects are affected (monsters/NPCs always, players optional). Movers have a direction, so players can be made to move in a pattern, and so 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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Mover',
     section => [
       [
 	'targets',
 	{
 	  fly_on => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Pedestal',
     use => '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.'
   },
   Pit => {
     attr => {
       connected => {
     },
     desc => '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 (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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Pit',
     use => '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.'
   },
   'Poison Food' => {
-    desc => 'When eating, the player\'s stomache is drained by 1/4 of food. If his food drops to zero, the player might even die.'
+    desc => 'When eating, the player\'s stomache is drained by 1/4 of food. If his food drops to zero, the player might even die.',
+    name => 'Poison Food'
   },
   Potion => {
     attr => {
       attacktype => {
 	desc => 'There are two types of special effects for potions: \'life restoration\' - restore the player\'s stats lost by death or draining (this has nothing in common with the restoration spell!) \'improvement\' - increase the player\'s maximum health/mana/grace by a very small amount.',
 	name => 'godgiven item',
 	type => 'bool'
       }
     },
     desc => 'The player can drink these and gain various kinds of benefits (/penalties) by doing so.',
+    name => 'Potion',
     section => [
       [
 	'stats',
 	{
 	  Cha => {
 	desc => '<initial mana> is the amount of spellpoints that the crystal holds when the map is loaded.',
 	name => 'initial mana',
 	type => 'int'
       }
     },
-    desc => '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.'
+    desc => '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.',
+    name => 'Power Crystal'
   },
   Projectile => {
     attr => {
       attacktype => {
 	desc => '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 weapons cannot have attacktypes.',
 	name => 'weaponclass',
 	type => 'int'
       }
     },
     desc => '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.',
+    name => 'Projectile',
     use => '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.'
   },
   Ring => {
     desc => '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.',
     import => [
       $TYPE{Amulet}
     ],
+    name => 'Ring',
     use => '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.'
   },
   Rod => {
     attr => {
       hp => {
     },
     desc => '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.',
     ignore => [
       'title'
     ],
+    name => 'Rod',
     use => '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>'
   },
   Rune => {
     attr => {
       Cha => {
       'weight',
       'value',
       'material',
       'unpaid'
     ],
+    name => 'Rune',
     section => [
       [
 	'spellcraft',
 	{
 	  maxhp => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Savebed',
     use => '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: <UL> <LI> Monsters must not be able to reach the savebeds under any circumstances! <LI> If there are NPCs around, make sure they have the friendly-flag set. <LI> Insert a relyable 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>'
   },
   Scroll => {
     attr => {
       level => {
     },
     desc => '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.',
     ignore => [
       'title'
     ],
+    name => 'Scroll',
     use => 'For low level quests, scrolls of healing/curing-spells can be a nice reward. At higher levels, scrolls become less and less useful.'
   },
   Shield => {
     attr => {
       magic => {
     },
     desc => '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.',
     import => [
       $TYPE{Amulet}
     ],
+    name => 'Shield',
     use => 'Feel free to create your own special artifacts. However, it is very important that you keep your artifact in balance with existing maps.'
   },
   'Shooting Weapon' => {
     attr => {
       cursed => {
 	name => 'weaponclass',
 	type => 'int'
       }
     },
     desc => 'Schooting weapons like bows/crossbows are used to shoot projectiles (arrows/bolts). Shooting weapons and normal (melee) weapons can be wielded both at the same time. Like with any other equipment, 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.',
+    name => 'Shooting Weapon',
     section => [
       [
 	'stats',
 	{
 	  Cha => {
     },
     desc => 'Shop floor is used for shops. It acts like a combination of the common floor- and the treasure type: When the map is loaded, randomitems (depending on the setings) are generated on it. 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).',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Shop Floor',
     use => '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.'
   },
   'Shop Mat' => {
     attr => {
       fly_on => {
     },
     desc => 'Shop mats are used for entering/leaving shops. You should always have exactly TWO shop mats on your shop-map: One inside the "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).',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Shop Mat',
     use => 'As stated above, always place TWO shop mats into your shop. Not more and not less than that.'
   },
   'Sign & MagicMouth' => {
     attr => {
       connected => {
     },
     desc => '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).',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Sign & MagicMouth',
     use => '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.'
   },
   Skill => {
     attr => {
       can_use_skill => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Skill',
     use => '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 exists as an archtype cannot be learned or used by players. When you want to use skills in your maps, you may need to look up the &lt;skill name&gt;s of defined skill archtypes, because those strings are used as a reference in many skill-related objects. </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>'
   },
   'Skill Scroll' => {
     attr => {
       race => {
 	name => 'skill name',
 	type => 'string'
       }
     },
     desc => 'By reading a skill scroll, a player has a chance to learn the contained skill.',
+    name => 'Skill Scroll',
     use => '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.'
   },
   'Special Key' => {
     attr => {
       material => {
     },
     desc => '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.',
     ignore => [
       'material'
     ],
+    name => 'Special Key',
     use => '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".'
   },
   Spell => {
     attr => {
       casting_time => {
     },
     desc => 'Spell objects define a spell. When a spell is put in a spellbook, 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.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Spell',
     use => '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.'
   },
   Spellbook => {
     attr => {
       msg => {
 	name => 'godgiven item',
 	type => 'bool'
       }
     },
     desc => 'By reading a spellbook, the player has a chance of learning the contained spell. Once learned from a book, the spell is available forever. Spellbooks with high level spells require some skill-level 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.',
+    name => 'Spellbook',
     use => '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.'
   },
   Spinner => {
     attr => {
       fly_on => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Spinner',
     use => '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.'
   },
   Swamp => {
     attr => {
       damned => {
       }
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
-    ]
+    ],
+    name => 'Swamp'
   },
   Teleporter => {
     attr => {
       connected => {
 	desc => 'If a connection value is set, the teleporter will be activated whenever the connection is triggered. To use this properly, <activation speed> must be zero.',
     },
     desc => 'When the player walks into a teleporter, he is transferred to a 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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Teleporter',
     use => '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.'
   },
   Trap => {
     attr => {
       Cha => {
       'weight',
       'value',
       'material',
       'unpaid'
     ],
+    name => 'Trap',
     use => 'Avoid monsters stepping on your traps. For example, a party of orcs setting off your lightning wall and pit trap is usually a bad idea.'
   },
   Trapdoor => {
     attr => {
       hp => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Trapdoor',
     use => '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.'
   },
   Treasure => {
     attr => {
       auto_apply => {
       'name_pl',
       'weight',
       'value',
       'material'
     ],
+    name => 'Treasure',
     use => '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.'
   },
   'Trigger Marker' => {
     attr => {
       connected => {
     },
     desc => 'A trigger marker is an object that inserts an invisible force (a mark) into a player stepping on it WHEN TRIGGERED. This force does nothing except containing a &lt;key string&gt; which can be discovered by detectors or inventory checkers. It is also possible to use markers for removing marks again. <br><br> Note that the player has no possibility to "see" his own marks, except by the effect that they cause on the maps.',
     ignore => [
       $IGNORE_LIST{system_object}
     ],
+    name => 'Trigger Marker',
     use => '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.'
   },
   Wall => {
     attr => {
       can_roll => {
       'title',
       'name_pl',
       'value',
       'unpaid'
     ],
+    name => 'Wall',
     required => {
       alive => 0,
       is_floor => 0,
       no_pass => 1
     }
 	name => 'godgiven item',
 	type => 'bool'
       }
     },
     desc => '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.',
+    name => 'Wand & Staff',
     use => 'Wands are quite seldomly used. The reason prolly is that they\'re generally not cost-efficient. Handing out high-level wands with powerfull 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 desireable though. Ideal rewards for low level quests.'
   },
   'Weak Wall' => {
     attr => {
       ac => {
     },
     desc => '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.',
     ignore => [
       $IGNORE_LIST{non_pickable}
     ],
+    name => 'Weak Wall',
     required => {
       alive => 1,
       is_floor => 0,
       tear_down => 1
     },
 	type => 'list',
 	value => $LIST{weapon_type}
       }
     },
     desc => '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.',
+    name => 'Weapon',
     section => [
       [
 	'resistance',
 	{
 	  resist_acid => {

Diff Legend

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

Comparing deliantra/Deliantra/Deliantra/Data.pm (file contents): Revision 1.4 by root, Wed Feb 22 22:36:45 2006 UTC vs. Revision 1.5 by root, Wed Feb 22 22:41:22 2006 UTC

Diff Legend

Comparing deliantra/Deliantra/Deliantra/Data.pm (file contents):
Revision 1.4 by root, Wed Feb 22 22:36:45 2006 UTC vs.
Revision 1.5 by root, Wed Feb 22 22:41:22 2006 UTC