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

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.1 by root, Tue Feb 21 21:37:01 2006 UTC vs.
Revision 1.3 by root, Mon Mar 13 04:38:47 2006 UTC

…		…
1	<?xml version="1.0" standalone="no" ?>	1	<?xml version="1.0" standalone="no" ?>
2	<!--	2	<!--
3	######################################################################	3	######################################################################
4	# types.xml - This is the defintitions-file for all the different #	4	# types.xml - This is the definitions-file for all the different #
5	# Crossfire object types and their attributes. #	5	# Crossfire object types and their attributes. #
6	# #	6	# #
7	# The server code of the Crossfire game is always changing and #	7	# The server code of the Crossfire game is always changing and #
8	# evolving. From time to time, object-attributes change in purpose, #	8	# evolving. From time to time, object-attributes change in purpose, #
9	# or new ones are created. #	9	# or new ones are created. #
10	# Therefore, it is important that an Editor is flexible and #	10	# Therefore, it is important that an Editor is flexible and #
11	# easy to "upgrade" to handle such new features. That's why the #	11	# easy to "upgrade" to handle such new features. That's why the #
12	# CFJavaEditor reads the type-definitions from this xml file. #	12	# CFJavaEditor reads the type-definitions from this xml file. #
13	# #	13	# #
14	# If you encounter bugs, typos or missing entrys in the LATEST #	14	# If you encounter bugs, typos or missing entries in the LATEST #
15	# VERSION of this file - Don't hesitate to improve it, contact me #	15	# VERSION of this file - Don't hesitate to improve it, contact me #
16	# and eventually send the improved file to me: <red.blaze@gmx.net>. #	16	# and eventually send the improved file to me: <red.blaze@gmx.net>. #
17	# I will put it into the "official version" of the CFJavaEditor #	17	# I will put it into the "official version" of the CFJavaEditor #
18	# and all fellow Crossfire-Map-Makers can benefit from your work! #	18	# and all fellow Crossfire-Map-Makers can benefit from your work! #
19	# #	19	# #
65	# Created by Andreas Vogl. #	65	# Created by Andreas Vogl. #
66	######################################################################	66	######################################################################
67	-->	67	-->
68	<!DOCTYPE types [	68	<!DOCTYPE types [
69	<!ELEMENT types ((bitmask \| list \| ignore_list), default_type, ignore_list, type+)>	69	<!ELEMENT types ((bitmask \| list \| ignore_list), default_type, ignore_list, type+)>
70		70
71	<!ELEMENT bitmask (entry*)>	71	<!ELEMENT bitmask (entry*)>
72	<!ATTLIST bitmask name CDATA #REQUIRED>	72	<!ATTLIST bitmask name CDATA #REQUIRED>
73		73
74	<!ELEMENT list (entry*)>	74	<!ELEMENT list (entry*)>
75	<!ATTLIST list name CDATA #REQUIRED>	75	<!ATTLIST list name CDATA #REQUIRED>
76		76
77	<!ELEMENT entry EMPTY>	77	<!ELEMENT entry EMPTY>
78	<!ATTLIST entry bit CDATA #IMPLIED	78	<!ATTLIST entry bit CDATA #IMPLIED
79	value CDATA #IMPLIED	79	value CDATA #IMPLIED
80	name CDATA #REQUIRED>	80	name CDATA #REQUIRED>
81		81
82	<!ELEMENT ignore_list (attribute* \| EMPTY)>	82	<!ELEMENT ignore_list (attribute* \| EMPTY)>
83	<!ATTLIST ignore_list name CDATA #REQUIRED>	83	<!ATTLIST ignore_list name CDATA #REQUIRED>
84		84
85	<!ELEMENT default_type (attribute*)>	85	<!ELEMENT default_type (attribute*)>
86		86
87	<!ELEMENT type (import_type?,required?,ignore?,description?,use?,(section \| attribute)*)>	87	<!ELEMENT type (import_type?,required?,ignore?,description?,use?,(section \| attribute)*)>
88	<!ATTLIST type name CDATA #REQUIRED	88	<!ATTLIST type name CDATA #REQUIRED
89	number CDATA #REQUIRED>	89	number CDATA #REQUIRED>
90		90
91	<!ELEMENT description (#PCDATA)>	91	<!ELEMENT description (#PCDATA)>
92	<!ELEMENT use (#PCDATA)>	92	<!ELEMENT use (#PCDATA)>
93		93
94	<!ELEMENT import_type EMPTY>	94	<!ELEMENT import_type EMPTY>
95	<!ATTLIST import_type name CDATA #REQUIRED>	95	<!ATTLIST import_type name CDATA #REQUIRED>
96		96
97	<!ELEMENT required (attribute+)>	97	<!ELEMENT required (attribute+)>
98	<!ELEMENT ignore (attribute,ignore_list)>	98	<!ELEMENT ignore (attribute,ignore_list)>
99		99
100	<!ELEMENT section (attribute+)>	100	<!ELEMENT section (attribute+)>
101	<!ATTLIST section name CDATA #REQUIRED>	101	<!ATTLIST section name CDATA #REQUIRED>
102		102
103	<!ELEMENT attribute (#PCDATA)>	103	<!ELEMENT attribute (#PCDATA)>
104	<!ATTLIST attribute type CDATA #IMPLIED	104	<!ATTLIST attribute type CDATA #IMPLIED
105	arch CDATA #IMPLIED	105	arch CDATA #IMPLIED
106	arch_begin CDATA #IMPLIED	106	arch_begin CDATA #IMPLIED
107	arch_end CDATA #IMPLIED	107	arch_end CDATA #IMPLIED
…		…
339	This is the plural name of the object. A plural name must be set for	339	This is the plural name of the object. A plural name must be set for
340	all items that can be picked up and collected by the player.	340	all items that can be picked up and collected by the player.
341	</attribute>	341	</attribute>
342	<attribute arch="title" editor="title" type="string">	342	<attribute arch="title" editor="title" type="string">
343	This is the object's title. Once an object is identified the title is	343	This is the object's title. Once an object is identified the title is
344	attached to the name. Typical titels are "of mostrai", "of xray vision" etc.	344	attached to the name. Typical titles are "of Mostrai", "of xray vision" etc.
345	</attribute>	345	</attribute>
346	<attribute arch="face" editor="image" type="string">	346	<attribute arch="face" editor="image" type="string">
347	The image-name defines what image is displayed for this object in-game.	347	The image-name defines what image is displayed for this object in-game.
348	</attribute>	348	</attribute>
349	<attribute arch="nrof" editor="number" type="int">	349	<attribute arch="nrof" editor="number" type="int">
350	This value determines the number of objects in one stack (for example:	350	This value determines the number of objects in one stack (for example:
351	100 goldcoins => "number = 100"). You should set this at least to one, for	351	100 goldcoins => "number = 100"). You should set this at least to one, for
352	any pickable object - otherwise it won't be mergeable into a stack.	352	any pickable object - otherwise it won't be mergeable into a stack.
353	</attribute>	353	</attribute>
354	<attribute arch="weight" editor="weight" type="int">	354	<attribute arch="weight" editor="weight" type="int">
355	This value defines the object's weight in gramm (1000g is 1kg). Objects with	355	This value defines the object's weight in grams (1000g is 1kg). Objects with
356	zero weight are not pickable for players. Still, set the "non-pickable"-flag	356	zero weight are not pickable for players. Still, set the "non-pickable"-flag
357	for explicitly non-pickable objects (hey, this is opensource.. you	357	for explicitly non-pickable objects (hey, this is opensource.. you
358	never know ;) ).	358	never know ;) ).
359	</attribute>	359	</attribute>
360	<attribute arch="value" editor="value" type="int">	360	<attribute arch="value" editor="value" type="int">
…		…
365	usually inevitable.	365	usually inevitable.
366	</attribute>	366	</attribute>
367	<attribute arch="glow_radius" editor="glow radius" type="int">	367	<attribute arch="glow_radius" editor="glow radius" type="int">
368	If <glow radius> is set to a value greater zero, the object	368	If <glow radius> is set to a value greater zero, the object
369	appears lit up on dark maps. <glow radius> can be a value	369	appears lit up on dark maps. <glow radius> can be a value
370	between 0 and 4, the higher, the more light does the object emmit.	370	between 0 and 4, the higher, the more light does the object emit.
371	</attribute>	371	</attribute>
372	<attribute arch="material" editor="material" type="bitmask_material">	372	<attribute arch="material" editor="material" type="bitmask_material">
373	This bitmask-value informs the player of which material(s) the	373	This bitmask-value informs the player of which material(s) the
374	object consists. Material does also affect how likely the object	374	object consists. Material does also affect how likely the object
375	can be destroyed by hazardous spell-effects.	375	can be destroyed by hazardous spell-effects.
…		…
499	</attribute>	499	</attribute>
500	<attribute arch="hp" editor="long range spell" type="nz_spell">	500	<attribute arch="hp" editor="long range spell" type="nz_spell">
501	The monster will use the specified <long range spell>	501	The monster will use the specified <long range spell>
502	when the player is at least 6 squares away (from the	502	when the player is at least 6 squares away (from the
503	monster's head).	503	monster's head).
504		504
505	Setting a <long range spell> is optional. If unset, the	505	Setting a <long range spell> is optional. If unset, the
506	<short range spell> gets used all the time.	506	<short range spell> gets used all the time.
507	</attribute>	507	</attribute>
508	<attribute arch="maxsp" editor="importance" type="int">	508	<attribute arch="maxsp" editor="importance" type="int">
509	Sometimes you'll want a monster to use one ability more than others.	509	Sometimes you'll want a monster to use one ability more than others.
510	To achieve this, set the <importance> to a value greater than	510	To achieve this, set the <importance> to a value greater than
511	one. Abilities with this value zero/unset are counted to be of	511	one. Abilities with this value zero/unset are counted to be of
512	<importance> one.	512	<importance> one.
513		513
514	Example: A monster with "small fireball" of <importance> 3 and	514	Example: A monster with "small fireball" of <importance> 3 and
515	"paralyze" of <importance> 1 will averagely cast three out of four	515	"paralyze" of <importance> 1 will averagely cast three out of four
516	times the "small fireball".	516	times the "small fireball".
517	</attribute>	517	</attribute>
518	<attribute arch="attacktype" editor="is magical" true="2" false="0" type="bool_special">	518	<attribute arch="attacktype" editor="is magical" true="2" false="0" type="bool_special">
519	This flag specifies wether the ability <is magical> in nature.	519	This flag specifies whether the ability <is magical> in nature.
520	If enabled, all spells produced by this ability will have magic	520	If enabled, all spells produced by this ability will have magic
521	attacktype added to the usual attacktypes.	521	attacktype added to the usual attacktypes.
522		522
523	This should always be set for spell-like abilities. "Natural"	523	This should always be set for spell-like abilities. "Natural"
524	abilities like a dragon's firebreath are an exception.	524	abilities like a dragon's firebreath are an exception.
525	Note that non-magical abilities are more dangerous because	525	Note that non-magical abilities are more dangerous because
526	magic resistance does not protect from those.</attribute>	526	magic resistance does not protect from those.</attribute>
527	</type>	527	</type>
…		…
533	</ignore>	533	</ignore>
534	<description><![CDATA[	534	<description><![CDATA[
535	When a player puts a defined number of certain items on the altar,	535	When a player puts a defined number of certain items on the altar,
536	then either a spell is casted (on the player) or a connector is	536	then either a spell is casted (on the player) or a connector is
537	triggered. If the latter is the case, the altar works only once.	537	triggered. If the latter is the case, the altar works only once.
538	Either way, the sacrificed item dissapears. ]]>	538	Either way, the sacrificed item disappears. ]]>
539	</description>	539	</description>
540	<attribute arch="no_pick" value="1" type="fixed" />	540	<attribute arch="no_pick" value="1" type="fixed" />
541	<attribute arch="walk_on" value="1" type="fixed" />	541	<attribute arch="walk_on" value="1" type="fixed" />
542	<attribute arch="slaying" editor="match item name" type="string">	542	<attribute arch="slaying" editor="match item name" type="string">
543	This string specifies the item that must be put on the altar to	543	This string specifies the item that must be put on the altar to
…		…
547	expected to drop on the altar. (Often this is put in the altar's	547	expected to drop on the altar. (Often this is put in the altar's
548	name: E.g. "drop 100 platinums")	548	name: E.g. "drop 100 platinums")
549	</attribute>	549	</attribute>
550	<attribute arch="food" editor="drop amount" type="int">	550	<attribute arch="food" editor="drop amount" type="int">
551	The drop amount specifies the amount of items (specified	551	The drop amount specifies the amount of items (specified
552	in <match item name>) that must be dropped to activate the altar.	552	in <match item name>) that must be dropped to activate the altar.
553		553
554	If <match item name> is set to "money", then the value of the	554	If <match item name> is set to "money", then the value of the
555	sacrificed money must be equal to <drop amount> (ie, if food=200, then	555	sacrificed money must be equal to <drop amount> (ie, if food=200, then
556	200 silver, 20 gold, or 4 platinum will all work.)	556	200 silver, 20 gold, or 4 platinum will all work.)
557		557
558	Note that the maximum possible for <drop amount> is 32767.	558	Note that the maximum possible for <drop amount> is 32767.
559	</attribute>	559	</attribute>
560	<attribute arch="connected" editor="connection" type="int">	560	<attribute arch="connected" editor="connection" type="int">
561	If a connection value is set, the altar will trigger all objects	561	If a connection value is set, the altar will trigger all objects
562	with the same value, when activated. This will only work once.	562	with the same value, when activated. This will only work once.
563	</attribute>	563	</attribute>
564	<attribute arch="sp" editor="spell" type="spell">	564	<attribute arch="sp" editor="spell" type="spell">
565	When activated, the selected <spell> will be casted (once, on the	565	When activated, the selected <spell> will be casted (once, on the
566	player). This should work for any given spell. The altar will work	566	player). This should work for any given spell. The altar will work
567	infinitly in this way. Don't set both <spell> and <connection> for	567	infinitely in this way. Don't set both <spell> and <connection> for
568	one altar.	568	one altar.
569	</attribute>	569	</attribute>
570	<attribute arch_begin="msg" arch_end="endmsg" editor="message" type="text">	570	<attribute arch_begin="msg" arch_end="endmsg" editor="message" type="text">
571	This text will be displayed to the player	571	This text will be displayed to the player
572	in the exact moment when the altar is activated.	572	in the exact moment when the altar is activated.
…		…
579	<ignore_list name="non_pickable" />	579	<ignore_list name="non_pickable" />
580	</ignore>	580	</ignore>
581	<description><![CDATA[	581	<description><![CDATA[
582	Altar_triggers work pretty much like normal altars	582	Altar_triggers work pretty much like normal altars
583	(drop sacrifice -> connection activated), except for the fact that	583	(drop sacrifice -> connection activated), except for the fact that
584	they reset after usage. Hence, altar_triggers can be used infinitly. ]]>	584	they reset after usage. Hence, altar_triggers can be used infinitely. ]]>
585	</description>	585	</description>
586	<use><![CDATA[	586	<use><![CDATA[
587	Altar_triggers are very useful if you want to charge a price for...	587	Altar_triggers are very useful if you want to charge a price for...
588	<UL>	588	<UL>
589	<LI> ...an item. -> Connect the altar_trigger (set "last_sp 1") to a creator.	589	<LI> ...an item. -> Connect the altar_trigger (set "last_sp 1") to a creator.
590	<LI> ...opening a gate. -> Connect the altar_trigger (set "last_sp 0") to the gate.	590	<LI> ...opening a gate. -> Connect the altar_trigger (set "last_sp 0") to the gate.
591	<LI> ...information. -> Connect the altar_trigger (set "last_sp 1") to a magic_mouth.	591	<LI> ...information. -> Connect the altar_trigger (set "last_sp 1") to a magic_mouth.
592	</UL>	592	</UL>
593	The big advantage over normal altars is the infinite usability	593	The big advantage over normal altars is the infinite usability
594	of altar_triggers! If there are ten players on one server, they're	594	of altar_triggers! If there are ten players on one server, they're
595	quite grateful if things work more than once. =) ]]>	595	quite grateful if things work more than once. =) ]]>
…		…
603	expected to drop on the altar. (Often this is put in the altar's	603	expected to drop on the altar. (Often this is put in the altar's
604	name: E.g. "drop 100 platinums")	604	name: E.g. "drop 100 platinums")
605	</attribute>	605	</attribute>
606	<attribute arch="food" editor="drop amount" type="int">	606	<attribute arch="food" editor="drop amount" type="int">
607	The drop amount specifies the amount of items (specified	607	The drop amount specifies the amount of items (specified
608	in <match item name>) that must be dropped to activate the altar.	608	in <match item name>) that must be dropped to activate the altar.
609		609
610	If <match item name> is set to "money", then the value of the	610	If <match item name> is set to "money", then the value of the
611	sacrificed money must be equal to <drop amount> (ie, if food=200, then	611	sacrificed money must be equal to <drop amount> (ie, if food=200, then
612	200 silver, 20 gold, or 4 platinum will all work.)	612	200 silver, 20 gold, or 4 platinum will all work.)
613		613
614	Note that the maximum possible for <drop amount> is 32767.	614	Note that the maximum possible for <drop amount> is 32767.
615	</attribute>	615	</attribute>
616	<attribute arch="connected" editor="connection" type="int">	616	<attribute arch="connected" editor="connection" type="int">
617	If a connection value is set, the altar will trigger all objects	617	If a connection value is set, the altar will trigger all objects
618	with the same value, when activated. This will only work once.	618	with the same value, when activated. This will only work once.
619	</attribute>	619	</attribute>
620	<attribute arch="sp" editor="spell" type="spell">	620	<attribute arch="sp" editor="spell" type="spell">
621	When activated, this <spell> will be casted (once, on the player).	621	When activated, this <spell> will be casted (once, on the player).
622	This should work for any given spell. The altar will work infinitly	622	This should work for any given spell. The altar will work infinitely
623	in this way. Don't set both <spell> and <connection> for one altar.	623	in this way. Don't set both <spell> and <connection> for one altar.
624	</attribute>	624	</attribute>
625	<attribute arch="exp" editor="reset time" type="int">	625	<attribute arch="exp" editor="reset time" type="int">
626	Being activated, the altar will reset after <reset time> ticks.	626	Being activated, the altar will reset after <reset time> ticks.
627	After reset, the altar is ready to be activated once again.	627	After reset, the altar is ready to be activated once again.
…		…
629	</attribute>	629	</attribute>
630	<attribute arch="last_sp" editor="ignore reset" type="bool">	630	<attribute arch="last_sp" editor="ignore reset" type="bool">
631	If this attribute is enabled, the altar_trigger won't push the	631	If this attribute is enabled, the altar_trigger won't push the
632	connected value by altar reset. Only ONCE by dropping the sacrifice.	632	connected value by altar reset. Only ONCE by dropping the sacrifice.
633	This is typically used when the altar is connected to a creator,	633	This is typically used when the altar is connected to a creator,
634	e.g. for selling tickets.	634	e.g. for selling tickets.
635		635
636	If this attribute is disabled (default), the altar_trigger	636	If this attribute is disabled (default), the altar_trigger
637	will push the connected value TWICE per sacrifice: First by	637	will push the connected value TWICE per sacrifice: First by
638	dropping sacrifice, second by reset. This mode is typically	638	dropping sacrifice, second by reset. This mode is typically
639	used for altars being connected to gates, resulting in the	639	used for altars being connected to gates, resulting in the
…		…
672	The <item power> value measures how "powerful" an artifact is.	672	The <item power> value measures how "powerful" an artifact is.
673	Players will only be able to wear equipment with a certain total	673	Players will only be able to wear equipment with a certain total
674	amount of <item power>, depending on their own level. This is the	674	amount of <item power>, depending on their own level. This is the
675	only way to prevent low level players to wear "undeserved" equipment	675	only way to prevent low level players to wear "undeserved" equipment
676	(like gifts from other players or cheated items).	676	(like gifts from other players or cheated items).
677		677
678	It is very important to adjust the <item power> value carefully	678	It is very important to adjust the <item power> value carefully
679	for every artifact you create! If zero/unset, the CF server will	679	for every artifact you create! If zero/unset, the CF server will
680	calculate a provisional value at runtime, but this is never	680	calculate a provisional value at runtime, but this is never
681	going to be an accurate measurement of <item power>.	681	going to be an accurate measurement of <item power>.
682	</attribute>	682	</attribute>
…		…
689	unless the curse is removed.	689	unless the curse is removed.
690	</attribute>	690	</attribute>
691	<attribute arch="lifesave" editor="save life" type="bool">	691	<attribute arch="lifesave" editor="save life" type="bool">
692	An item with this flag enabled will save the players life	692	An item with this flag enabled will save the players life
693	for one time: When the player is wearing this item and his	693	for one time: When the player is wearing this item and his
694	healthpoints reach zero, the item dissapears, replenishing	694	health points reach zero, the item disappears, replenishing
695	half of the player's health.	695	half of the player's health.
696		696
697	An item with <save life> should not have	697	An item with <save life> should not have
698	any decent additional bonuses!	698	any decent additional bonuses!
699	</attribute>	699	</attribute>
700	<attribute arch="unique" editor="unique item" type="bool">	700	<attribute arch="unique" editor="unique item" type="bool">
701	Unique items exist only one time on a server. If the item	701	Unique items exist only one time on a server. If the item
…		…
868	additional <grace regen.> bonus should be VERY RARE!!	868	additional <grace regen.> bonus should be VERY RARE!!
869	</attribute>	869	</attribute>
870	<attribute arch="food" editor="food bonus" type="int">	870	<attribute arch="food" editor="food bonus" type="int">
871	Positive <food bonus> slows down the player's digestion,	871	Positive <food bonus> slows down the player's digestion,
872	thus he consumes less food. Negative values speed it up.	872	thus he consumes less food. Negative values speed it up.
873		873
874	Note that food is consumed not only for "being alive", but	874	Note that food is consumed not only for "being alive", but
875	also for healing and mana-regeneration.	875	also for healing and mana-regeneration.
876	<food bonus> only affects the amount of food consumed	876	<food bonus> only affects the amount of food consumed
877	for "being alive". Hence, even with high <food bonus>,	877	for "being alive". Hence, even with high <food bonus>,
878	during a fight a player can run out of food quickly.	878	during a fight a player can run out of food quickly.
879	</attribute>	879	</attribute>
880	<attribute arch="xrays" editor="xray vision" type="bool">	880	<attribute arch="xrays" editor="xray vision" type="bool">
881	Xray vision allows the player to see through obstacles	881	Xray vision allows the player to see through obstacles
882	in a two-square-wide radius. This is extremely helpful and	882	in a two-square-wide radius. This is extremely helpful and
883	desireable, so don't give it away for cheap on equipment.	883	desirable, so don't give it away for cheap on equipment.
884	</attribute>	884	</attribute>
885	<attribute arch="stealth" editor="stealth" type="bool">	885	<attribute arch="stealth" editor="stealth" type="bool">
886	Stealth allows the player to move silently.	886	Stealth allows the player to move silently.
887	This comes to effect if a player turns himself	887	This comes to effect if a player turns himself
888	invisible and tries to sneak around monsters.	888	invisible and tries to sneak around monsters.
…		…
893	the ability to <reflect spells>, all kinds of	893	the ability to <reflect spells>, all kinds of
894	spell-bullets and -beams will bounce off him.	894	spell-bullets and -beams will bounce off him.
895	This works only about 90% of all times, to	895	This works only about 90% of all times, to
896	avoid players being completely immune to certain	896	avoid players being completely immune to certain
897	types of attacks.	897	types of attacks.
898		898
899	This is a very powerful ability and it	899	This is a very powerful ability and it
900	shouldn't be handed out cheap!	900	shouldn't be handed out cheap!
901	</attribute>	901	</attribute>
902	<attribute arch="reflect_missile" editor="reflect missiles" type="bool">	902	<attribute arch="reflect_missile" editor="reflect missiles" type="bool">
903	If a player is wearing any piece of equipment with	903	If a player is wearing any piece of equipment with
…		…
969	get teleported after they died on this battleground.	969	get teleported after they died on this battleground.
970	</attribute>	970	</attribute>
971	</type>	971	</type>
972		972
973	<!--####################################################################-->	973	<!--####################################################################-->
974	<type number="104" name="Bracers">
975	<import_type name="Amulet" />
976	<description><![CDATA[
977	Bracers are armour-plates worn around the wrists.
978	Wearing bracer, the object's stats will directly be inherited to
979	the player. Usually enhancing his defense. ]]>
980	</description>
981	<use><![CDATA[
982	Feel free to create your own special artifacts. However, it is very
983	important that you keep your artifact in balance with existing maps. ]]>
984	</use>
985	<attribute arch="magic" editor="magic bonus" type="int">
986	<magic bonus> works just like ac, except that it can be improved by
987	"scrolls of Enchant Armour" or reduced by acid. It is less useful
988	than direct armour-class bonus on the bracers.
989	</attribute>
990	</type>
991
992	<!--####################################################################-->
993	<type number="16" name="Brestplate Armour">
994	<import_type name="Amulet" />
995	<description><![CDATA[
996	Wearing an armour, the object's stats will directly be inherited to
997	the player. Usually enhancing his defense. ]]>
998	</description>
999	<use><![CDATA[
1000	Feel free to create your own special artifacts. However, it is very
1001	important that you keep your artifact in balance with existing maps. ]]>
1002	</use>
1003	<attribute arch="last_heal" editor="spellpoint penalty" type="int">
1004	This poses a penalty to spell regeneration speed, for wearing the armour.
1005	The bigger the spellpoint penalty, the worse.
1006	</attribute>
1007	<attribute arch="last_sp" editor="slowdown penalty" type="int">
1008	Slowdown penalty reduces the player's walking speed when wearing the
1009	armour. Bigger values are worse - zero is best.
1010	</attribute>
1011	<attribute arch="magic" editor="magic bonus" type="int">
1012	<magic bonus> works just like ac, except that it can be improved by
1013	"scrolls of Enchant Armour" or reduced by acid. It is less useful
1014	than direct armour-class bonus on the armour.
1015	</attribute>
1016	</type>
1017
1018	<!--####################################################################-->
1019	<type number="8" name="Book">	974	<type number="8" name="Book">
1020	<description><![CDATA[	975	<description><![CDATA[
1021	Applying a book, the containing message is displayed to the player. ]]>	976	Applying a book, the containing message is displayed to the player. ]]>
1022	</description>	977	</description>
1023	<attribute arch="level" editor="literacy level" type="int">	978	<attribute arch="level" editor="literacy level" type="int">
…		…
1064	</attribute>	1019	</attribute>
1065	<attribute arch="magic" editor="magic bonus" type="int">	1020	<attribute arch="magic" editor="magic bonus" type="int">
1066	<magic bonus> works just like ac, except that it can be improved by	1021	<magic bonus> works just like ac, except that it can be improved by
1067	"scrolls of Enchant Armour" or reduced by acid. It is less useful	1022	"scrolls of Enchant Armour" or reduced by acid. It is less useful
1068	than direct armour-class bonus on the boots.	1023	than direct armour-class bonus on the boots.
1069		1024
1070	Important: <magic bonus> on boots has no effect if there is no	1025	Important: <magic bonus> on boots has no effect if there is no
1071	<armour class> set. It only works in combination with <armour class>.	1026	<armour class> set. It only works in combination with <armour class>.
		1027	</attribute>
		1028	</type>
		1029
		1030	<!--####################################################################-->
		1031	<type number="104" name="Bracers">
		1032	<import_type name="Amulet" />
		1033	<description><![CDATA[
		1034	Bracers are armour-plates worn around the wrists.
		1035	Wearing bracer, the object's stats will directly be inherited to
		1036	the player. Usually enhancing his defense. ]]>
		1037	</description>
		1038	<use><![CDATA[
		1039	Feel free to create your own special artifacts. However, it is very
		1040	important that you keep your artifact in balance with existing maps. ]]>
		1041	</use>
		1042	<attribute arch="magic" editor="magic bonus" type="int">
		1043	<magic bonus> works just like ac, except that it can be improved by
		1044	"scrolls of Enchant Armour" or reduced by acid. It is less useful
		1045	than direct armour-class bonus on the bracers.
		1046	</attribute>
		1047	</type>
		1048
		1049	<!--####################################################################-->
		1050	<type number="16" name="Brestplate Armour">
		1051	<import_type name="Amulet" />
		1052	<description><![CDATA[
		1053	Wearing an armour, the object's stats will directly be inherited to
		1054	the player. Usually enhancing his defense. ]]>
		1055	</description>
		1056	<use><![CDATA[
		1057	Feel free to create your own special artifacts. However, it is very
		1058	important that you keep your artifact in balance with existing maps. ]]>
		1059	</use>
		1060	<attribute arch="last_heal" editor="spellpoint penalty" type="int">
		1061	This poses a penalty to spell regeneration speed, for wearing the armour.
		1062	The bigger the spellpoint penalty, the worse.
		1063	</attribute>
		1064	<attribute arch="last_sp" editor="slowdown penalty" type="int">
		1065	Slowdown penalty reduces the player's walking speed when wearing the
		1066	armour. Bigger values are worse - zero is best.
		1067	</attribute>
		1068	<attribute arch="magic" editor="magic bonus" type="int">
		1069	<magic bonus> works just like ac, except that it can be improved by
		1070	"scrolls of Enchant Armour" or reduced by acid. It is less useful
		1071	than direct armour-class bonus on the armour.
1072	</attribute>	1072	</attribute>
1073	</type>	1073	</type>
1074		1074
1075	<!--####################################################################-->	1075	<!--####################################################################-->
1076	<type number="92" name="Button">	1076	<type number="92" name="Button">
…		…
1084	<connection> value get's triggered a second time. ]]>	1084	<connection> value get's triggered a second time. ]]>
1085	</description>	1085	</description>
1086	<attribute arch="walk_on" value="1" type="fixed" />	1086	<attribute arch="walk_on" value="1" type="fixed" />
1087	<attribute arch="walk_off" value="1" type="fixed" />	1087	<attribute arch="walk_off" value="1" type="fixed" />
1088	<attribute arch="no_pick" value="1" type="fixed" />	1088	<attribute arch="no_pick" value="1" type="fixed" />
1089	<attribute arch="weight" editor="press weight" type="string">	1089	<attribute arch="weight" editor="press weight" type="int">
1090	The button is pressed (triggered), as soon as	1090	The button is pressed (triggered), as soon as
1091	<press weigh> gram are placed ontop of it.	1091	<press weigh> gram are placed ontop of it.
1092	</attribute>	1092	</attribute>
1093	<attribute arch="connected" editor="connection" type="int">	1093	<attribute arch="connected" editor="connection" type="int">
1094	Every time the button is pressed or released, all objects	1094	Every time the button is pressed or released, all objects
…		…
1096	</attribute>	1096	</attribute>
1097	<attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">	1097	<attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
1098	This text may describe the item. You can use this	1098	This text may describe the item. You can use this
1099	message to explain the button's purpose to the player.	1099	message to explain the button's purpose to the player.
1100	</attribute>	1100	</attribute>
		1101	</type>
		1102
		1103	<!--####################################################################-->
		1104	<type number="30" name="Button Trigger">
		1105	<import_type name="Button" />
		1106	<ignore>
		1107	<ignore_list name="non_pickable" />
		1108	</ignore>
		1109	<description><![CDATA[
		1110	Handle buttons are buttons which reset after a short period
		1111	of time. Every time it is either applied or reset, the
		1112	<connection> value is triggered. ]]>
		1113	</description>
		1114	</type>
		1115
		1116	<!--####################################################################-->
		1117	<type number="37" name="Class Changer">
		1118	<ignore>
		1119	<ignore_list name="non_pickable" />
		1120	</ignore>
		1121	<description><![CDATA[
		1122	Class changer are used while creating a character. ]]>
		1123	</description>
		1124	<attribute arch="randomitems" editor="class items" type="treasurelist">
		1125	This entry determines which initial items the character receives.
		1126	</attribute>
		1127	<section name="stats">
		1128	<attribute arch="Str" editor="strength" type="int">
		1129	The player's strength will rise by the given value if he chooses this
		1130	class. (Negative values make strength fall)
		1131	</attribute>
		1132	<attribute arch="Dex" editor="dexterity" type="int">
		1133	The player's dexterity will rise by the given value if he chooses this
		1134	class. (Negative values make dexterity fall)
		1135	</attribute>
		1136	<attribute arch="Con" editor="constitution" type="int">
		1137	The player's constitution will rise by the given value if he chooses this
		1138	class. (Negative values make constitution fall)
		1139	</attribute>
		1140	<attribute arch="Int" editor="intelligence" type="int">
		1141	The player's intelligence will rise by the given value if he chooses this
		1142	class. (Negative values make intelligence fall)
		1143	</attribute>
		1144	<attribute arch="Pow" editor="power" type="int">
		1145	The player's power will rise by the given value if he chooses this
		1146	class. (Negative values make power fall)
		1147	</attribute>
		1148	<attribute arch="Wis" editor="wisdom" type="int">
		1149	The player's wisdom will rise by the given value if he chooses this
		1150	class. (Negative values make wisdom fall)
		1151	</attribute>
		1152	<attribute arch="Cha" editor="charisma" type="int">
		1153	The player's charisma will rise by the given value if he chooses this
		1154	class. (Negative values make charisma fall)
		1155	</attribute>
		1156	</section>
1101	</type>	1157	</type>
1102		1158
1103	<!--####################################################################-->	1159	<!--####################################################################-->
1104	<type number="87" name="Cloak">	1160	<type number="87" name="Cloak">
1105	<import_type name="Amulet" />	1161	<import_type name="Amulet" />
…		…
1114	</use>	1170	</use>
1115	<attribute arch="magic" editor="magic bonus" type="int">	1171	<attribute arch="magic" editor="magic bonus" type="int">
1116	<magic bonus> works just like ac, except that it can be improved by	1172	<magic bonus> works just like ac, except that it can be improved by
1117	"scrolls of Enchant Armour" or reduced by acid. It is less useful	1173	"scrolls of Enchant Armour" or reduced by acid. It is less useful
1118	than direct armour-class bonus on the cloak.	1174	than direct armour-class bonus on the cloak.
1119		1175
1120	Important: <magic bonus> on cloaks has no effect if there is no	1176	Important: <magic bonus> on cloaks has no effect if there is no
1121	<armour class> set. It only works in combination with <armour class>.	1177	<armour class> set. It only works in combination with <armour class>.
1122	</attribute>	1178	</attribute>
1123	</type>	1179	</type>
1124		1180
…		…
1153	</UL> ]]>	1209	</UL> ]]>
1154	</use>	1210	</use>
1155	<attribute arch="race" editor="container class" type="string">	1211	<attribute arch="race" editor="container class" type="string">
1156	If set, the container will hold only certain types of objects.	1212	If set, the container will hold only certain types of objects.
1157	Possible choices for <container class> are: "gold and jewels",	1213	Possible choices for <container class> are: "gold and jewels",
1158	"arrows" and "keys".	1214	"arrows" and "keys".
1159		1215
1160	Unfortunately it is not easy to create new container	1216	Unfortunately it is not easy to create new container
1161	classes, because items need a matching counterpiece-attribute	1217	classes, because items need a matching counterpiece-attribute
1162	to the <container class> before they can be put inside a	1218	to the <container class> before they can be put inside a
1163	container. This attribute ("race") is set only for the existing	1219	container. This attribute ("race") is set only for the existing
1164	container classes.	1220	container classes.
…		…
1239	on the converter, in order to get <receive number> items	1295	on the converter, in order to get <receive number> items
1240	of <receive arch>.	1296	of <receive arch>.
1241	</attribute>	1297	</attribute>
1242	<attribute arch="other_arch" editor="receive arch" type="string">	1298	<attribute arch="other_arch" editor="receive arch" type="string">
1243	<receive arch> is the name of the archetype to convert into.	1299	<receive arch> is the name of the archetype to convert into.
		1300	This field is ignored if the converter has items in inventory. In this
		1301	case one of the inventory items is duplicated. The duplicated item is
		1302	randomly chosen from all items present.
1244	</attribute>	1303	</attribute>
1245	<attribute arch="sp" editor="receive number" type="int">	1304	<attribute arch="sp" editor="receive number" type="int">
1246	The player has to put <cost number> items of <cost arch>	1305	The player has to put <cost number> items of <cost arch>
1247	on the converter, in order to get <receive number> items	1306	on the converter, in order to get <receive number> items
1248	of <receive arch>.	1307	of <receive arch>.
…		…
1268	</use>	1327	</use>
1269	<attribute arch="no_pick" value="1" type="fixed" />	1328	<attribute arch="no_pick" value="1" type="fixed" />
1270	<attribute arch="other_arch" editor="create arch" type="string">	1329	<attribute arch="other_arch" editor="create arch" type="string">
1271	This string defines the object that will be created.	1330	This string defines the object that will be created.
1272	You can choose any of the existing arches.	1331	You can choose any of the existing arches.
		1332	This field is ignored if the creator has items in inventory. In this case
		1333	one of the inventory items is duplicated. The duplicated item is randomly
		1334	chosen from all items present.
1273	</attribute>	1335	</attribute>
1274	<attribute arch="connected" editor="connection" type="int">	1336	<attribute arch="connected" editor="connection" type="int">
1275	Whenever the connection value is activated,	1337	Whenever the connection value is activated,
1276	the creator gets triggered.	1338	the creator gets triggered.
1277	</attribute>	1339	</attribute>
1278	<attribute arch="lifesave" editor="infinit uses" type="bool">	1340	<attribute arch="lifesave" editor="infinit uses" type="bool">
1279	If <infinit uses> is set, the creator will work	1341	If <infinit uses> is set, the creator will work
1280	infinitly, regardless of the value in <number of uses>.	1342	infinitely, regardless of the value in <number of uses>.
1281	</attribute>	1343	</attribute>
1282	<attribute arch="hp" editor="number of uses" type="int">	1344	<attribute arch="hp" editor="number of uses" type="int">
1283	The creator can be triggered <number of uses> times, thus	1345	The creator can be triggered <number of uses> times, thus
1284	creating that many objects, before it dissappears.	1346	creating that many objects, before it dissappears.
1285	Default is <number of uses> 1 (-> one-time usage).	1347	Default is <number of uses> 1 (-> one-time usage).
1286	</attribute>	1348	</attribute>
1287	<attribute arch="slaying" editor="name of creation" type="string">	1349	<attribute arch="slaying" editor="name of creation" type="string">
1288	The created object will bear the name specified in <name creation>.	1350	The created object will bear the name and title specified in <name of
1289	If nothing is set, the standard name of the archetype is used.	1351	creation>. If nothing is set, the standard name and title of the
		1352	archetype is used.
1290	</attribute>	1353	</attribute>
1291	<attribute arch="level" editor="level of creation" type="int">	1354	<attribute arch="level" editor="level of creation" type="int">
1292	The created object will be of that level. If zero/unset,	1355	The created object will be of that level. If zero/unset,
1293	the standard level of the archetype is used.	1356	the standard level of the archetype is used.
1294	</attribute>	1357	</attribute>
…		…
1400	<section name="spreading">	1463	<section name="spreading">
1401	<attribute arch="wc" editor="infectiosness" type="int">	1464	<attribute arch="wc" editor="infectiosness" type="int">
1402	The <infectiosness> defines the chance of new creatures getting	1465	The <infectiosness> defines the chance of new creatures getting
1403	infected. If you set this too high, the disease is very likely to	1466	infected. If you set this too high, the disease is very likely to
1404	be too effective.	1467	be too effective.
1405		1468
1406	<infectiosness>/127 is the chance of someone in range catching it.	1469	<infectiosness>/127 is the chance of someone in range catching it.
1407	</attribute>	1470	</attribute>
1408	<attribute arch="last_grace" editor="attenuation" type="int">	1471	<attribute arch="last_grace" editor="attenuation" type="int">
1409	The <attenuation> value reduces the diseases' <infectiosness>	1472	The <attenuation> value reduces the diseases' <infectiosness>
1410	everytime it infects someone new. This limits how many generations	1473	everytime it infects someone new. This limits how many generations
…		…
1413	<attribute arch="magic" editor="infection range" type="int">	1476	<attribute arch="magic" editor="infection range" type="int">
1414	<infection range> sets the range at which infection may occur.	1477	<infection range> sets the range at which infection may occur.
1415	If positive, the <infection range> is level dependant - If negative,	1478	If positive, the <infection range> is level dependant - If negative,
1416	it is not:	1479	it is not:
1417	E.g. "<infection range> -6" means creatures can be infected in	1480	E.g. "<infection range> -6" means creatures can be infected in
1418	six square range, and <plaque level> doesn't modify that.	1481	six square range, and <plaque level> doesn't modify that.
1419	</attribute>	1482	</attribute>
1420	<attribute arch="maxhp" editor="persistence" type="int">	1483	<attribute arch="maxhp" editor="persistence" type="int">
1421	<persistence> defines how long the disease can persist OUTSIDE a host.	1484	<persistence> defines how long the disease can persist OUTSIDE a host.
1422	The disease can "move" <persistence> times outside a host before it	1485	The disease can "move" <persistence> times outside a host before it
1423	vanishes. A negative value means the disease lasts for permanent	1486	vanishes. A negative value means the disease lasts for permanent
…		…
1426	<attribute arch="maxgrace" editor="curing duration" type="int">	1489	<attribute arch="maxgrace" editor="curing duration" type="int">
1427	The disease will last in the host for <curing duration> "disease moves"	1490	The disease will last in the host for <curing duration> "disease moves"
1428	(Assuming the host survives and doesn't use a curing spell).	1491	(Assuming the host survives and doesn't use a curing spell).
1429	After this period the disease is naturally cured, which provides the	1492	After this period the disease is naturally cured, which provides the
1430	host with immunity from this particular disease of lower or equal level.	1493	host with immunity from this particular disease of lower or equal level.
1431		1494
1432	A negative value means the disease can never be cured naturally.	1495	A negative value means the disease can never be cured naturally.
1433		1496
1434	Note that this value can be further modulated by spell-parameters,	1497	Note that this value can be further modulated by spell-parameters,
1435	if the disease is registered as spell in the code. Due to that,	1498	if the disease is registered as spell in the code. Due to that,
1436	most default diseases take a lot longer to cure than it seems.	1499	most default diseases take a lot longer to cure than it seems.
1437	</attribute>	1500	</attribute>
1438	<attribute arch="speed" editor="moving speed" type="float">	1501	<attribute arch="speed" editor="moving speed" type="float">
…		…
1448	<attribute arch="dam" editor="damage" type="int">	1511	<attribute arch="dam" editor="damage" type="int">
1449	A disease with a positive <damage> value will strike the player for that	1512	A disease with a positive <damage> value will strike the player for that
1450	amount of damage every time the symptoms occur.	1513	amount of damage every time the symptoms occur.
1451	A negative <damage> value produces %-based damage: "<damage> -10" means	1514	A negative <damage> value produces %-based damage: "<damage> -10" means
1452	the player's health is reduced by 10% every time the symptoms strike.	1515	the player's health is reduced by 10% every time the symptoms strike.
1453		1516
1454	Diseases with %-based damage can be dangerous - but not deadly -	1517	Diseases with %-based damage can be dangerous - but not deadly -
1455	for players of all levels.	1518	for players of all levels.
1456	</attribute>	1519	</attribute>
1457	<attribute arch="other_arch" editor="create arch" type="string">	1520	<attribute arch="other_arch" editor="create arch" type="string">
1458	If set, the specified arch is created and dropped every time the	1521	If set, the specified arch is created and dropped every time the
1459	symptoms strike.	1522	symptoms strike.
1460		1523
1461	This can be various things: farts, body pieces, eggs ...	1524	This can be various things: farts, body pieces, eggs ...
1462	Even monsters can be created that way. You could also make a	1525	Even monsters can be created that way. You could also make a
1463	disease where some exotic stuff like money/gems is created.	1526	disease where some exotic stuff like money/gems is created.
1464	</attribute>	1527	</attribute>
1465	<attribute arch="last_sp" editor="slowdown penalty" type="int">	1528	<attribute arch="last_sp" editor="slowdown penalty" type="int">
…		…
1520	</attribute>	1583	</attribute>
1521	</section>	1584	</section>
1522	<attribute arch_begin="msg" arch_end="endmsg" editor="message" type="text">	1585	<attribute arch_begin="msg" arch_end="endmsg" editor="message" type="text">
1523	This text is displayed to the player every time the	1586	This text is displayed to the player every time the
1524	symptoms strike.	1587	symptoms strike.
		1588	</attribute>
		1589	</type>
		1590
		1591	<!--####################################################################-->
		1592	<type number="23" name="Door">
		1593	<ignore>
		1594	<ignore_list name="non_pickable" />
		1595	</ignore>
		1596	<description><![CDATA[
		1597	A door can be opened with a normal key. It also can be broken by attacking
		1598	it, and it can be defeated with the lockpicking skill. If a door is
		1599	defeated, horizontally and vertically adjacent doors are automatically
		1600	removed. ]]>
		1601	</description>
		1602	<attribute arch="no_pick" value="1" type="fixed" />
		1603	<attribute arch="alive" value="1" type="fixed" />
		1604	<attribute arch="no_pass" editor="blocking passage" type="bool">
		1605	If set, a player must defeat the door to enter.
		1606	</attribute>
		1607	<attribute arch="hp" editor="hitpoints" type="int">
		1608	The more <hitpoints> the door has, the longer it takes to be broken.
		1609	</attribute>
		1610	<attribute arch="ac" editor="armour class" type="int">
		1611	Doors of high <armour class> are less likely to get hit.
		1612	<armour class> can be considered the "counterpiece" to
		1613	<weapon class>.
		1614	</attribute>
		1615	<attribute arch="other_arch" editor="drop arch" type="string">
		1616	This string defines the object that will be created when the door was
		1617	defeated.
		1618	</attribute>
		1619	<attribute arch="randomitems" editor="treasurelist" type="treasurelist">
		1620	This entry determines what kind of traps will appear in the door.
1525	</attribute>	1621	</attribute>
1526	</type>	1622	</type>
1527		1623
1528	<!--####################################################################-->	1624	<!--####################################################################-->
1529	<type number="83" name="Duplicator">	1625	<type number="83" name="Duplicator">
…		…
1574	(Monsters cannot use exits.) Depending on how it is set, the player applies	1670	(Monsters cannot use exits.) Depending on how it is set, the player applies
1575	the exit just by walking into it, or by pressing <a>pply when standing on	1671	the exit just by walking into it, or by pressing <a>pply when standing on
1576	the exit. ]]>	1672	the exit. ]]>
1577	</description>	1673	</description>
1578	<use><![CDATA[	1674	<use><![CDATA[
1579	If you want to have an invisible exit, set <invisible> (, of course	1675	If you want to have an invisible exit, set <invisible> (, of course
1580	<apply by walking>), and put it under the floor. Otherwise it could be	1676	<apply by walking>), and put it under the floor. Otherwise it could be
1581	detected with the show_invisible spell.	1677	detected with the show_invisible spell.
1582	<br><br>	1678	<br><br>
1583	You can be quite creative with the outlook of secret exits (their "face").	1679	You can be quite creative with the outlook of secret exits (their "face").
1584	Don't forget to give the player relyable hints about them though. ]]>	1680	Don't forget to give the player relyable hints about them though. ]]>
…		…
1588	You can enter an absolute path, beginning with '/' (for example	1684	You can enter an absolute path, beginning with '/' (for example
1589	"/peterm/FireTemple/fire1"). It can also be a relative path, not beginning	1685	"/peterm/FireTemple/fire1"). It can also be a relative path, not beginning
1590	with '/' (On the map "/peterm/FireTemple/Fire2" for example I could use the	1686	with '/' (On the map "/peterm/FireTemple/Fire2" for example I could use the
1591	relative path "Fire1"). Use relative paths whenever possible! Note that	1687	relative path "Fire1"). Use relative paths whenever possible! Note that
1592	upper/lower case must always be set correctly. However, please use lower	1688	upper/lower case must always be set correctly. However, please use lower
1593	case only.	1689	case only.
1594	It is well possible to have an exit pointing to the same map that the exit	1690	It is well possible to have an exit pointing to the same map that the exit
1595	is on. If slaying is not set in an exit, the player will see a message like	1691	is on. If slaying is not set in an exit, the player will see a message like
1596	"the exit is closed".	1692	"the exit is closed".
1597	</attribute>	1693	</attribute>
1598	<attribute arch="hp" editor="destination X" type="int">	1694	<attribute arch="hp" editor="destination X" type="int">
…		…
1812	</attribute>	1908	</attribute>
1813	<section name="terrain">	1909	<section name="terrain">
1814	<attribute arch="slow_move" editor="slow movement" type="int">	1910	<attribute arch="slow_move" editor="slow movement" type="int">
1815	If <slow movement> is set to a value greater zero, all	1911	If <slow movement> is set to a value greater zero, all
1816	creatures moving over this spot will be slower than normal.	1912	creatures moving over this spot will be slower than normal.
1817		1913
1818	<slow movement> 1 - rough terrain	1914	<slow movement> 1 - rough terrain
1819	<slow movement> 2 - very rough terrain	1915	<slow movement> 2 - very rough terrain
1820	...	1916	...
1821	<slow movement> 7 - spider web (sticky as hell)	1917	<slow movement> 7 - spider web (sticky as hell)
1822	</attribute>	1918	</attribute>
…		…
1867	</attribute>	1963	</attribute>
1868	<section name="terrain">	1964	<section name="terrain">
1869	<attribute arch="slow_move" editor="slow movement" type="int">	1965	<attribute arch="slow_move" editor="slow movement" type="int">
1870	If <slow movement> is set to a value greater zero, all	1966	If <slow movement> is set to a value greater zero, all
1871	creatures moving over this spot will be slower than normal.	1967	creatures moving over this spot will be slower than normal.
1872		1968
1873	<slow movement> 1 - rough terrain	1969	<slow movement> 1 - rough terrain
1874	<slow movement> 2 - very rough terrain	1970	<slow movement> 2 - very rough terrain
1875	...	1971	...
1876	<slow movement> 7 - spider web (sticky as hell)	1972	<slow movement> 7 - spider web (sticky as hell)
1877	</attribute>	1973	</attribute>
…		…
1975	</use>	2071	</use>
1976	<attribute arch="magic" editor="magic bonus" type="int">	2072	<attribute arch="magic" editor="magic bonus" type="int">
1977	<magic bonus> works just like ac, except that it can be improved by	2073	<magic bonus> works just like ac, except that it can be improved by
1978	"scrolls of Enchant Armour" or reduced by acid. It is less useful	2074	"scrolls of Enchant Armour" or reduced by acid. It is less useful
1979	than direct armour-class bonus on the helmet.	2075	than direct armour-class bonus on the helmet.
1980		2076
1981	Important: <magic bonus> on girdles has no effect if there is no	2077	Important: <magic bonus> on girdles has no effect if there is no
1982	<armour class> set. Girdles shouldn't have <armour class>, thus	2078	<armour class> set. Girdles shouldn't have <armour class>, thus
1983	<magic bonus> is pointless here.	2079	<magic bonus> is pointless here.
1984	</attribute>	2080	</attribute>
1985	</type>	2081	</type>
…		…
2094	</attribute>	2190	</attribute>
2095	<section name="terrain">	2191	<section name="terrain">
2096	<attribute arch="slow_move" editor="slow movement" type="int">	2192	<attribute arch="slow_move" editor="slow movement" type="int">
2097	If <slow movement> is set to a value greater zero, all	2193	If <slow movement> is set to a value greater zero, all
2098	creatures moving over this spot will be slower than normal.	2194	creatures moving over this spot will be slower than normal.
2099		2195
2100	<slow movement> 1 - rough terrain	2196	<slow movement> 1 - rough terrain
2101	<slow movement> 2 - very rough terrain	2197	<slow movement> 2 - very rough terrain
2102	...	2198	...
2103	<slow movement> 7 - spider web (sticky as hell)	2199	<slow movement> 7 - spider web (sticky as hell)
2104	</attribute>	2200	</attribute>
…		…
2141	</use>	2237	</use>
2142	<attribute arch="magic" editor="magic bonus" type="int">	2238	<attribute arch="magic" editor="magic bonus" type="int">
2143	<magic bonus> works just like ac, except that it can be improved by	2239	<magic bonus> works just like ac, except that it can be improved by
2144	"scrolls of Enchant Armour" or reduced by acid. It is less useful	2240	"scrolls of Enchant Armour" or reduced by acid. It is less useful
2145	than direct armour-class bonus on the helmet.	2241	than direct armour-class bonus on the helmet.
2146		2242
2147	Important: <magic bonus> on helmets has no effect if there is no	2243	Important: <magic bonus> on helmets has no effect if there is no
2148	<armour class> set. It only works in combination with <armour class>.	2244	<armour class> set. It only works in combination with <armour class>.
2149	Crowns for instance typically provide no <amour class>.	2245	Crowns for instance typically provide no <amour class>.
2150	</attribute>	2246	</attribute>
2151	</type>	2247	</type>
…		…
2162	</description>	2258	</description>
2163	<attribute arch="no_pick" value="1" type="fixed" />	2259	<attribute arch="no_pick" value="1" type="fixed" />
2164	<attribute arch="other_arch" editor="god name" type="string">	2260	<attribute arch="other_arch" editor="god name" type="string">
2165	The altar belongs to the god of the given name. Possible options for	2261	The altar belongs to the god of the given name. Possible options for
2166	<god name> are: Devourers, Lythander, Mostrai, Gaea, Ruggilli, Gnarg,	2262	<god name> are: Devourers, Lythander, Mostrai, Gaea, Ruggilli, Gnarg,
2167	Gorokh, Valriel and Sorig.	2263	Gorokh, Valriel and Sorig.
2168		2264
2169	If you want to have an unconsecrated altar, set	2265	If you want to have an unconsecrated altar, set
2170	<god name> 0 and eventually <reconsecrate level> 0.	2266	<god name> 0 and eventually <reconsecrate level> 0.
2171	</attribute>	2267	</attribute>
2172	<attribute arch="level" editor="reconsecrate level" type="int">	2268	<attribute arch="level" editor="reconsecrate level" type="int">
2173	To re-consecrate an altar, the player's wisdom level must be as	2269	To re-consecrate an altar, the player's wisdom level must be as
2174	high or higher than this value. In that way, some altars can not	2270	high or higher than this value. In that way, some altars can not
2175	be re-consecrated, while other altars, like those in dungeons, could be.	2271	be re-consecrated, while other altars, like those in dungeons, could be.
2176		2272
2177	Altars located in temples should have at least <reconsecrate level> 100.	2273	Altars located in temples should have at least <reconsecrate level> 100.
2178	Some characters might need those altars, they would be very unhappy to	2274	Some characters might need those altars, they would be very unhappy to
2179	see them re-consecrated to another cult.	2275	see them re-consecrated to another cult.
2180	</attribute>	2276	</attribute>
2181	</type>	2277	</type>
…		…
2301	This string specifies the object we are looking for: We have a match	2397	This string specifies the object we are looking for: We have a match
2302	if the player does/don't carry an object of archtype <match arch name>.	2398	if the player does/don't carry an object of archtype <match arch name>.
2303	</attribute>	2399	</attribute>
2304	<attribute arch="hp" editor="match type" type="int">	2400	<attribute arch="hp" editor="match type" type="int">
2305	This value specifies the object we are looking for: We have a match	2401	This value specifies the object we are looking for: We have a match
2306	if the player does/don't carry an object that is of type <match type>.	2402	if the player does/don't carry an object that is of type <match type>.
2307		2403
2308	Example: Set <match type> 15 (type 15 => weapon) and <blocking passage>	2404	Example: Set <match type> 15 (type 15 => weapon) and <blocking passage>
2309	enabled. Now you have an inv. checker blocking all players that carry any	2405	enabled. Now you have an inv. checker blocking all players that carry any
2310	kind of melee weapon. To pass, a player is forced to leave behind all	2406	kind of melee weapon. To pass, a player is forced to leave behind all
2311	his weaponry... bad news for a warrior. ;)	2407	his weaponry... bad news for a warrior. ;)
2312	</attribute>	2408	</attribute>
…		…
2326	</attribute>	2422	</attribute>
2327	<attribute arch="last_heal" editor="remove match" type="bool">	2423	<attribute arch="last_heal" editor="remove match" type="bool">
2328	<remove match> means remove object if found. Setting this is usually not	2424	<remove match> means remove object if found. Setting this is usually not
2329	recommended because inv. checkers are in general invisible. So, unlike	2425	recommended because inv. checkers are in general invisible. So, unlike
2330	for altars/ locked doors, the player won't expect to lose an object when	2426	for altars/ locked doors, the player won't expect to lose an object when
2331	walking over that square. And he doesn't even get a message either.	2427	walking over that square. And he doesn't even get a message either.
2332		2428
2333	So, if you enable <remove match>, make sure	2429	So, if you enable <remove match>, make sure
2334	to inform the player what's going on!	2430	to inform the player what's going on!
		2431	</attribute>
		2432	</type>
		2433
		2434	<!--####################################################################-->
		2435	<type number="163" name="Item Transformer">
		2436	<description><![CDATA[
		2437	An item transformer is simply applied, after having marked a 'victim'
		2438	item. If the victim is suitable, it will be transformed into something
		2439	else.]]>
		2440	</description>
		2441	<use><![CDATA[
		2442	To make an item transformable, you just have to fill the 'slaying' field.
		2443	The syntax is:
		2444	<br>
		2445	<pre>slaying slayer:[yield ]new_item[;slayer:[yield ]new_item]*</pre>
		2446	<br>
		2447	with [] denoting optional part, and * any number of preceding [].
		2448	'new_item' must be the name of an existing archetype.
		2449	<br><br>
		2450	Example, for object apple: slaying knife:2 half_apple
		2451	<br><br>
		2452	This means that, when applying a knife (should be an Item Transformer),
		2453	one 'apple' will be transformed into 2 'half_apple'.]]>
		2454	</use>
		2455	<attribute arch="food" editor="number of uses" type="int">
		2456	<number of uses> controls how many times the item transformer can
		2457	be used. The value 0 means "unlimited"
		2458	</attribute>
		2459	<attribute arch="slaying" editor="verb" type="string">
		2460	Contains the verb that is used to construct a message to the player
		2461	applying the item transformer.
		2462	</attribute>
		2463	<attribute arch="startequip" editor="godgiven item" type="bool">
		2464	A godgiven item vanishes as soon as the player
		2465	drops it to the ground.
		2466	</attribute>
		2467	<attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
		2468	This text may contain a description of the item transformer.
2335	</attribute>	2469	</attribute>
2336	</type>	2470	</type>
2337		2471
2338	<!--####################################################################-->	2472	<!--####################################################################-->
2339	<type number="60" name="Jewel">	2473	<type number="60" name="Jewel">
…		…
2347	This text may describe the object.	2481	This text may describe the object.
2348	</attribute>	2482	</attribute>
2349	</type>	2483	</type>
2350		2484
2351	<!--####################################################################-->	2485	<!--####################################################################-->
		2486	<type number="24" name="Key">
		2487	<description><![CDATA[
		2488	When carrying a key, a normal door can be opened. The key will
		2489	disappear. ]]>
		2490	</description>
		2491	<attribute arch="startequip" editor="godgiven item" type="bool">
		2492	A godgiven item vanishes as soon as the player
		2493	drops it to the ground.
		2494	</attribute>
		2495	</type>
		2496
		2497	<!--####################################################################-->
2352	<type number="20" name="Locked Door">	2498	<type number="20" name="Locked Door">
2353	<ignore>	2499	<ignore>
2354	<ignore_list name="non_pickable" />	2500	<ignore_list name="non_pickable" />
2355	</ignore>	2501	</ignore>
2356	<description><![CDATA[	2502	<description><![CDATA[
…		…
2358	the appropriate special key. ]]>	2504	the appropriate special key. ]]>
2359	</description>	2505	</description>
2360	<use><![CDATA[	2506	<use><![CDATA[
2361	If you want to create a locked door that cannot be opened (no key),	2507	If you want to create a locked door that cannot be opened (no key),
2362	set a <key string> like "no_key_available". This will clearify things	2508	set a <key string> like "no_key_available". This will clearify things
2363	and only a fool would create a key matching that string.	2509	and only a fool would create a key matching that string.
2364		2510
2365	Door-objects can not only be used for "doors". In many maps these	2511	Door-objects can not only be used for "doors". In many maps these
2366	are used with all kinds of faces/names, especially often as	2512	are used with all kinds of faces/names, especially often as
2367	"magic force". A good example is the map "Lake_Country/ebony/masterlev".	2513	"magic force". A good example is the map "Lake_Country/ebony/masterlev".
2368	There you have magic forces (door objects) put under certain artifact	2514	There you have magic forces (door objects) put under certain artifact
2369	items. To get your hands on the artifacts, you need to bring up the	2515	items. To get your hands on the artifacts, you need to bring up the
…		…
2373	<attribute arch="no_pick" value="1" type="fixed" />	2519	<attribute arch="no_pick" value="1" type="fixed" />
2374	<attribute arch="slaying" editor="key string" type="string">	2520	<attribute arch="slaying" editor="key string" type="string">
2375	The <key string> in the door must be identical with the	2521	The <key string> in the door must be identical with the
2376	<key string> in the special key, then the door is unlocked.	2522	<key string> in the special key, then the door is unlocked.
2377	It is VERY important to set the <key string> to something that	2523	It is VERY important to set the <key string> to something that
2378	is unique among the CF mapset.	2524	is unique among the CF mapset.
2379		2525
2380	DONT EVER USE the default string "set_individual_value".	2526	DONT EVER USE the default string "set_individual_value".
2381	</attribute>	2527	</attribute>
2382	<attribute arch="no_magic" editor="restrict spells" type="bool">	2528	<attribute arch="no_magic" editor="restrict spells" type="bool">
2383	Restricting the use of spells to pass this door.	2529	Restricting the use of spells to pass this door.
2384	This should be set in most cases.	2530	This should be set in most cases.
…		…
2426	<attribute arch_begin="msg" arch_end="endmsg" editor="keyword-matching" type="text">	2572	<attribute arch_begin="msg" arch_end="endmsg" editor="keyword-matching" type="text">
2427	This textfield contains the keyword-matching-syntax. The text should	2573	This textfield contains the keyword-matching-syntax. The text should
2428	have the following format: "@match <keyword1>\|<keyword2>\|... ".	2574	have the following format: "@match <keyword1>\|<keyword2>\|... ".
2429	Any number of keywords from one to infinite is allowed. Make sure	2575	Any number of keywords from one to infinite is allowed. Make sure
2430	they are seperated by a '\|'.	2576	they are seperated by a '\|'.
2431		2577
2432	Examples: "@match yes", "@match gold\|treasure". The connected	2578	Examples: "@match yes", "@match gold\|treasure". The connected
2433	value will be triggerd when the player speaks any of the given	2579	value will be triggerd when the player speaks any of the given
2434	keywords within a two-square radius. IMPORTANT: Upper/lower case	2580	keywords within a two-square radius. IMPORTANT: Upper/lower case
2435	does not make a difference!	2581	does not make a difference!
2436	</attribute>	2582	</attribute>
…		…
2614	</attribute>	2760	</attribute>
2615	<attribute arch="name" editor="delete mark" type="string">	2761	<attribute arch="name" editor="delete mark" type="string">
2616	When the player steps onto the marker, all existing forces in	2762	When the player steps onto the marker, all existing forces in
2617	the players inventory with a <key string> matching <delete mark>	2763	the players inventory with a <key string> matching <delete mark>
2618	will be removed. If you don't want to remove any marks, leave	2764	will be removed. If you don't want to remove any marks, leave
2619	this textfield empty.	2765	this textfield empty.
2620		2766
2621	Note that the string <delete mark> is set as the name of	2767	Note that the string <delete mark> is set as the name of
2622	this marker. So don't be confused, and remember changing the	2768	this marker. So don't be confused, and remember changing the
2623	name will take effect on the marker's functionality.	2769	name will take effect on the marker's functionality.
2624	</attribute>	2770	</attribute>
2625	<attribute arch_begin="msg" arch_end="endmsg" editor="marking message" type="text">	2771	<attribute arch_begin="msg" arch_end="endmsg" editor="marking message" type="text">
2626	In the moment when the player gets marked, this text is displayed	2772	In the moment when the player gets marked, this text is displayed
2627	to him. You should really set a message in any marker you create,	2773	to him. You should really set a message in any marker you create,
2628	because it's the only way for the player to notice what's going on.	2774	because it's the only way for the player to notice what's going on.
2629	</attribute>	2775	</attribute>
2630	</type>	2776	</type>
2631	<!--####################################################################-->	2777
2632	<type number="52" name="Trigger Marker">
2633	<ignore>
2634	<ignore_list name="system_object" />
2635	</ignore>
2636	<description><![CDATA[
2637	A trigger marker is an object that inserts an invisible force (a mark) into a
2638	player stepping on it WHEN TRIGGERED. This force does nothing except containing a
2639	<key string> which can be discovered by detectors or inventory
2640	checkers. It is also possible to use markers for removing marks again.
2641	<br><br>
2642	Note that the player has no possibility to "see" his own marks,
2643	except by the effect that they cause on the maps. ]]>
2644	</description>
2645	<use><![CDATA[
2646	Markers hold real cool possibilities for map-making. I encourage
2647	you to use them frequently. However there is one negative point
2648	about markers: Players don't "see" what's going on with them. It is
2649	your task, as map-creator, to make sure the player is always well
2650	informed and never confused.
2651	<br><br>
2652	Please avoid infinite markers when they aren't needed. They're
2653	using a little space in the player file after all, so if there
2654	is no real purpose, set an expire time. ]]>
2655	</use>
2656	<attribute arch="no_pick" value="1" type="fixed" />
2657	<attribute arch="slaying" editor="key string" type="string">
2658	The <key string> can be detected by inv. checkers/detectors.
2659	If the player already has a force with that <key string>,
2660	there won't be inserted a second one.
2661	</attribute>
2662	<attribute arch="connected" editor="connection" type="int">
2663	Unlike a regular marker this is the connection that triggers this marker to activate.
2664	</attribute>
2665	<attribute arch="food" editor="mark duration" type="int">
2666	This value defines the duration of the force it inserts.
2667	If nonzero, the duration of the player's mark is finite:
2668	about 1 food per 10 seconds. <mark duration> zero/unset
2669	means the mark will stay on the player forever.
2670	</attribute>
2671	<attribute arch="name" editor="delete mark" type="string">
2672	When the player steps onto the marker, all existing forces in
2673	the players inventory with a <key string> matching <delete mark>
2674	will be removed. If you don't want to remove any marks, leave
2675	this textfield empty.
2676
2677	Note that the string <delete mark> is set as the name of
2678	this marker. So don't be confused, and remember changing the
2679	name will take effect on the marker's functionality.
2680	</attribute>
2681	<attribute arch_begin="msg" arch_end="endmsg" editor="marking message" type="text">
2682	In the moment when the player gets marked, this text is displayed
2683	to him. You should really set a message in any marker you create,
2684	because it's the only way for the player to notice what's going on.
2685	</attribute>
2686	</type>
2687	<!--####################################################################-->	2778	<!--####################################################################-->
2688	<type number="36" name="Money">	2779	<type number="36" name="Money">
2689	<ignore>	2780	<ignore>
2690	<attribute arch="unpaid" />	2781	<attribute arch="unpaid" />
2691	</ignore>	2782	</ignore>
…		…
2733	It's no fun to play for two hours just to find out the last	2824	It's no fun to play for two hours just to find out the last
2734	monster is unbeatable. Similar, it's not exciting to fight orcs	2825	monster is unbeatable. Similar, it's not exciting to fight orcs
2735	after passing a room of dragons.<br>	2826	after passing a room of dragons.<br>
2736	This rule applies only for linear maps (one room after the other),	2827	This rule applies only for linear maps (one room after the other),
2737	with treasure at the end. You can sprinkle the treasure around,	2828	with treasure at the end. You can sprinkle the treasure around,
2738	or make non-linear maps - That is often more entertaining.	2829	or make non-linear maps - That is often more entertaining.
2739	<LI> Places with high level monsters must not be easy to reach.	2830	<LI> Places with high level monsters must not be easy to reach.
2740	Balrogs, Dragonmen and the likes should be at the end of a quest,	2831	Balrogs, Dragonmen and the likes should be at the end of a quest,
2741	not at the beginning.	2832	not at the beginning.
2742	<LI> Don't stick monsters together that tend to kill each other.	2833	<LI> Don't stick monsters together that tend to kill each other.
2743	Fire- and cold dragons in one room for example is a bad idea.	2834	Fire- and cold dragons in one room for example is a bad idea.
2744	By weakening and killing each other they are easy prey for players,	2835	By weakening and killing each other they are easy prey for players,
2745	not worth the experience they hold.	2836	not worth the experience they hold.
2746	<LI> Create your own monsters, especially for "boss"-type monsters.	2837	<LI> Create your own monsters, especially for "boss"-type monsters.
…		…
2763	<attribute arch="alive" value="1" type="fixed" />	2854	<attribute arch="alive" value="1" type="fixed" />
2764	<attribute arch="randomitems" editor="treasurelist" type="treasurelist">	2855	<attribute arch="randomitems" editor="treasurelist" type="treasurelist">
2765	When the monster is killed, items from the treasurelist will	2856	When the monster is killed, items from the treasurelist will
2766	drop to the ground. This is a common way to reward players	2857	drop to the ground. This is a common way to reward players
2767	for killing (masses of) monsters.	2858	for killing (masses of) monsters.
2768		2859
2769	Note that you can always put items into the monster's	2860	Note that you can always put items into the monster's
2770	inventory. Those will drop-at-kill just like the stuff	2861	inventory. Those will drop-at-kill just like the stuff
2771	from the <treasurelist>.	2862	from the <treasurelist>.
2772	</attribute>	2863	</attribute>
2773	<attribute arch="level" editor="level" type="int">	2864	<attribute arch="level" editor="level" type="int">
…		…
2782	</attribute>	2873	</attribute>
2783	<attribute arch="exp" editor="experience" type="int">	2874	<attribute arch="exp" editor="experience" type="int">
2784	When a player kills this monster, he will get exactly this	2875	When a player kills this monster, he will get exactly this
2785	amount of <experience>. The experience will flow into	2876	amount of <experience>. The experience will flow into
2786	the skill-cathegory the player used for the kill.	2877	the skill-cathegory the player used for the kill.
2787		2878
2788	If you create special monsters of tweaked strenght/abilities,	2879	If you create special monsters of tweaked strenght/abilities,
2789	always make sure that the <experience> is set to a	2880	always make sure that the <experience> is set to a
2790	reasonable value. Compare with existing arches to get a feeling	2881	reasonable value. Compare with existing arches to get a feeling
2791	what reasonable means. Keep in mind that spellcasting monsters	2882	what reasonable means. Keep in mind that spellcasting monsters
2792	are a lot harder to kill than non-spellcasters!	2883	are a lot harder to kill than non-spellcasters!
…		…
2811	This only takes effect if <multiply> is enabled. The monster	2902	This only takes effect if <multiply> is enabled. The monster
2812	will create a new monster every once in a while by duplicating it's inventory.	2903	will create a new monster every once in a while by duplicating it's inventory.
2813	In this case, the <breed monster> value is never used and can be forgotten.	2904	In this case, the <breed monster> value is never used and can be forgotten.
2814	Each time the monster need to generate an object, it will be	2905	Each time the monster need to generate an object, it will be
2815	a randomly chosen item from the inventory. When generator is destroyed,	2906	a randomly chosen item from the inventory. When generator is destroyed,
2816	inventory is destroyed.	2907	inventory is destroyed.
2817	</attribute>	2908	</attribute>
2818	<attribute arch="flying" editor="flying" type="bool">	2909	<attribute arch="flying" editor="flying" type="bool">
2819	Flying monsters won't get slowed down in rough terrain	2910	Flying monsters won't get slowed down in rough terrain
2820	and they won't be affected by movers.	2911	and they won't be affected by movers.
2821	</attribute>	2912	</attribute>
…		…
2826	<attribute arch="carrying" editor="carries weight" type="int">	2917	<attribute arch="carrying" editor="carries weight" type="int">
2827	If a monster has something in the inventory, this	2918	If a monster has something in the inventory, this
2828	value can be set to reflect the slowdown due to	2919	value can be set to reflect the slowdown due to
2829	the carried weight.	2920	the carried weight.
2830	</attribute>	2921	</attribute>
2831		2922
2832	<section name="melee">	2923	<section name="melee">
2833	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">	2924	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
2834	This number is a bitmask, specifying the monster's attacktypes	2925	This number is a bitmask, specifying the monster's attacktypes
2835	for melee damage. Attacktypes are: physical, magical, fire, cold.. etc.	2926	for melee damage. Attacktypes are: physical, magical, fire, cold.. etc.
2836	Strong monsters often have more than just physical attacktype.	2927	Strong monsters often have more than just physical attacktype.
2837		2928
2838	When a monster with multiple attacktypes hits aan oponent, it will do	2929	When a monster with multiple attacktypes hits aan oponent, it will do
2839	as much damage as the "best" of it's attacktypes does. So, the more	2930	as much damage as the "best" of it's attacktypes does. So, the more
2840	attacktypes, the more dangerous. Attacktypes "magic" and "chaos" are	2931	attacktypes, the more dangerous. Attacktypes "magic" and "chaos" are
2841	somehow exceptions.	2932	somehow exceptions.
2842	</attribute>	2933	</attribute>
…		…
2865	their opponent. <armour class> can be considered the "counterpiece"	2956	their opponent. <armour class> can be considered the "counterpiece"
2866	to <weapon class>.	2957	to <weapon class>.
2867	Values typically range between +20 (very bad) to -20 (quite good).	2958	Values typically range between +20 (very bad) to -20 (quite good).
2868	</attribute>	2959	</attribute>
2869	<attribute arch="Con" editor="healing rate" type="int">	2960	<attribute arch="Con" editor="healing rate" type="int">
2870	Monsters regenerate this many hit points each move. Each time the	2961	Monsters regenerate this many health points each 4 ticks. Hence, the
2871	monster has a move, it gets <healing rate> health points back.	2962	healing rate is independent of <speed>.
2872	Hence, <movement speed> has great effect on the monster's healing
2873	rate as well.
2874	</attribute>	2963	</attribute>
2875	<attribute arch="reflect_missile" editor="reflect missiles" type="bool">	2964	<attribute arch="reflect_missile" editor="reflect missiles" type="bool">
2876	A monster with this flag has the ability to <reflect missiles>,	2965	A monster with this flag has the ability to <reflect missiles>,
2877	all kinds of projectiles (e.g. arrows, bolts, boulders) will	2966	all kinds of projectiles (e.g. arrows, bolts, boulders) will
2878	bounce off.	2967	bounce off.
…		…
2888	<attribute arch="one_hit" editor="one hit only" type="bool">	2977	<attribute arch="one_hit" editor="one hit only" type="bool">
2889	Monsters with <one hit only> dissapear after one successful hit	2978	Monsters with <one hit only> dissapear after one successful hit
2890	to a player.	2979	to a player.
2891	</attribute>	2980	</attribute>
2892	</section>	2981	</section>
2893		2982
2894	<section name="spellcraft">	2983	<section name="spellcraft">
2895	<attribute arch="can_cast_spell" editor="can cast spell" type="bool">	2984	<attribute arch="can_cast_spell" editor="can cast spell" type="bool">
2896	If <can cast spell> is disabled, the monster cannot cast any spell.	2985	If <can cast spell> is disabled, the monster cannot cast any spell.
2897	Only wands/rods/etc can be used, given the appropriate abilities.	2986	Only wands/rods/etc can be used, given the appropriate abilities.
2898	</attribute>	2987	</attribute>
2899	<attribute arch="reflect_spell" editor="reflect spells" type="bool">	2988	<attribute arch="reflect_spell" editor="reflect spells" type="bool">
2900	A monster with this flag has the ability to <reflect spells>,	2989	A monster with this flag has the ability to <reflect spells>,
2901	all kinds of spell-bullets and -beams will bounce off.	2990	all kinds of spell-bullets and -beams will bounce off.
2902		2991
2903	Generally this flag should not be set because it puts	2992	Generally this flag should not be set because it puts
2904	wizard-type players at an unfair disadvantage.	2993	wizard-type players at an unfair disadvantage.
2905	</attribute>	2994	</attribute>
2906	<attribute arch="sp" editor="spellpoints" type="int">	2995	<attribute arch="sp" editor="spellpoints" type="int">
2907	Like players, monsters need <spellpoints> to do magic. Monsters use	2996	Like players, monsters need <spellpoints> to do magic. Monsters use
…		…
2916	can hold. Setting this to high values has little effect unless	3005	can hold. Setting this to high values has little effect unless
2917	the monster has a decent <spellpoint regen.>, or the spell	3006	the monster has a decent <spellpoint regen.>, or the spell
2918	"regenerate mana" at it's disposal.	3007	"regenerate mana" at it's disposal.
2919	</attribute>	3008	</attribute>
2920	<attribute arch="Pow" editor="spellpoint regen." type="int">	3009	<attribute arch="Pow" editor="spellpoint regen." type="int">
2921	Monsters regenerate this many spellpoints each move. Each time the	3010	Monsters regenerate this many spellpoints each 16 ticks. Hence, the
2922	monster has a move, it gets <spellpoint regen.> spellpoints back.	3011	spellpoint regeneration rate is independent of <speed>.
2923	Hence, <movement speed> has great effect on the monster's	3012
2924	spellpoint regeneration as well.
2925
2926	To make a real tough spellcasting monster, the rate of spellpoint	3013	To make a real tough spellcasting monster, the rate of spellpoint
2927	regeneration is most important. If your monster is still not casting	3014	regeneration is most important. If your monster is still not casting
2928	fast enough, give it the spell-ability of "regenerate mana".	3015	fast enough, give it the spell-ability of "regenerate mana".
2929	That, paired with high <max spellpoints>, is the ultimate thing.	3016	That, paired with high <max spellpoints>, is the ultimate thing.
2930	</attribute>	3017	</attribute>
…		…
2939	<attribute arch="path_denied" editor="denied paths" type="bitmask_spellpath">	3026	<attribute arch="path_denied" editor="denied paths" type="bitmask_spellpath">
2940	Click on the <denied paths> button to select spellpaths.	3027	Click on the <denied paths> button to select spellpaths.
2941	The creature won't be able to cast spells of the specified paths.	3028	The creature won't be able to cast spells of the specified paths.
2942	</attribute>	3029	</attribute>
2943	</section>	3030	</section>
2944		3031
2945	<section name="ability">	3032	<section name="ability">
2946	<attribute arch="Int" editor="detect hidden" type="int">	3033	<attribute arch="Int" editor="detect hidden" type="int">
2947	The <detect hidden> value gives monsters the ablitity to find	3034	The <detect hidden> value gives monsters the ablitity to find
2948	hidden/invisible creatures. Higher values make for better	3035	hidden/invisible creatures. Higher values make for better
2949	detection-skills. Enabling <see invisible> makes this value	3036	detection-skills. Enabling <see invisible> makes this value
…		…
2984	Monster is able to read scrolls.	3071	Monster is able to read scrolls.
2985	</attribute>	3072	</attribute>
2986	<attribute arch="can_use_skill" editor="can use skills" type="bool">	3073	<attribute arch="can_use_skill" editor="can use skills" type="bool">
2987	Monster is able to use skills from it's inventory.	3074	Monster is able to use skills from it's inventory.
2988	For example, you can put a throwing skill object and some	3075	For example, you can put a throwing skill object and some
2989	boulders into the monster's object and set <can use skills>.	3076	boulders into the monster's object and set <can use skills>.
2990	</attribute>	3077	</attribute>
2991	</section>	3078	</section>
2992		3079
2993	<section name="behave">	3080	<section name="behave">
2994	<attribute arch="monster" editor="monster behaviour" type="bool">	3081	<attribute arch="monster" editor="monster behaviour" type="bool">
2995	When <monster behaviour> is enabled, this object will behave	3082	When <monster behaviour> is enabled, this object will behave
2996	like a monster: It can move and attack enemies (which are	3083	like a monster: It can move and attack enemies (which are
2997	typically players).	3084	typically players).
2998	This flag should be set for all monsters as-such.	3085	This flag should be set for all monsters as-such.
2999	Monsters which don't move, like guards, should also have	3086	Monsters which don't move, like guards, should also have
3000	<monster behaviour>, but in combination with <stand still>.	3087	<monster behaviour>, but in combination with <stand still>.
3001	It should not be set for things like immobile generators.	3088	It should not be set for things like immobile generators.
3002	</attribute>	3089	</attribute>
3003	<attribute arch="unaggressive" editor="unaggressive" type="bool">	3090	<attribute arch="unaggressive" editor="unaggressive" type="bool">
3004	<unaggressive> monsters do not attack players unless attacked first.	3091	<unaggressive> monsters do not attack players unless attacked first.
3005	</attribute>	3092	</attribute>
3006	<attribute arch="friendly" editor="friendly" type="bool">	3093	<attribute arch="friendly" editor="friendly" type="bool">
…		…
3009	</attribute>	3096	</attribute>
3010	<attribute arch="stand_still" editor="stand still" type="bool">	3097	<attribute arch="stand_still" editor="stand still" type="bool">
3011	Monsters which <stand still> won't move to leave their position.	3098	Monsters which <stand still> won't move to leave their position.
3012	When agressive, they will attack all enemies who get close to	3099	When agressive, they will attack all enemies who get close to
3013	them. This behaviour is commonly known from castle guards.	3100	them. This behaviour is commonly known from castle guards.
3014		3101
3015	In older versions of Crossfire it was possible to eventually	3102	In older versions of Crossfire it was possible to eventually
3016	push a <stand still>-monster out of position by force.	3103	push a <stand still>-monster out of position by force.
3017	I believe this is no longer possible. Neverthless, you should	3104	I believe this is no longer possible. Neverthless, you should
3018	still be cautious when lining up <stand still>-monster in order	3105	still be cautious when lining up <stand still>-monster in order
3019	to "defend" something: Such monsters are rather easy to kill.	3106	to "defend" something: Such monsters are rather easy to kill.
…		…
3030	creature is able to perform.	3117	creature is able to perform.
3031	</attribute>	3118	</attribute>
3032	<attribute arch="pick_up" editor="pick up" type="bitmask_pick_up">	3119	<attribute arch="pick_up" editor="pick up" type="bitmask_pick_up">
3033	Click on the <pick up> button and select which types of objects	3120	Click on the <pick up> button and select which types of objects
3034	the creature should try to pick up.	3121	the creature should try to pick up.
3035		3122
3036	Note also that if <can use armor>, <can use weapon>, <can use ring>...	3123	Note also that if <can use armor>, <can use weapon>, <can use ring>...
3037	etc are set, then the creature will pick up the matching items even	3124	etc are set, then the creature will pick up the matching items even
3038	if this is not set here.	3125	if this is not set here.
3039	</attribute>	3126	</attribute>
3040	<attribute arch="Wis" editor="sensing range" type="int">	3127	<attribute arch="Wis" editor="sensing range" type="int">
…		…
3051	When the monster's health points drop below this percentage	3138	When the monster's health points drop below this percentage
3052	(relative to max health), it attempts to run away from the	3139	(relative to max health), it attempts to run away from the
3053	attacker.	3140	attacker.
3054	</attribute>	3141	</attribute>
3055	</section>	3142	</section>
3056		3143
3057	<section name="resistance">	3144	<section name="resistance">
3058	<attribute arch="resist_physical" editor="resist physical %" length="15" type="int">	3145	<attribute arch="resist_physical" editor="resist physical %" length="15" type="int">
3059	</attribute>	3146	</attribute>
3060	<attribute arch="resist_magic" editor="resist magic %" length="15" type="int">	3147	<attribute arch="resist_magic" editor="resist magic %" length="15" type="int">
3061	</attribute>	3148	</attribute>
…		…
3098	<attribute arch="resist_godpower" editor="resist godpower %" length="15" type="int">	3185	<attribute arch="resist_godpower" editor="resist godpower %" length="15" type="int">
3099	</attribute>	3186	</attribute>
3100	</section>	3187	</section>
3101	<attribute arch_begin="msg" arch_end="endmsg" editor="npc message" type="text">	3188	<attribute arch_begin="msg" arch_end="endmsg" editor="npc message" type="text">
3102	</attribute>	3189	</attribute>
		3190	</type>
		3191
		3192	<!--####################################################################-->
		3193	<type number="28" name="Monster (Grimreaper)">
		3194	<import_type name="Monster & NPC" />
		3195	<ignore>
		3196	<attribute arch="material" />
		3197	<attribute arch="name_pl" />
		3198	<attribute arch="nrof" />
		3199	<attribute arch="value" />
		3200	<attribute arch="unpaid" />
		3201	</ignore>
		3202	<description><![CDATA[
		3203	A grimreaper is a monster that vanishes after it did some number of
		3204	draining attacks. ]]> <!-- XXX: is this ok? -->
		3205	</description>
		3206	<section name="grimreaper">
		3207	<attribute arch="value" editor="attacks" type="int">
		3208	The object vanishes after this number of draining attacks.
		3209	</attribute>
		3210	</section>
3103	</type>	3211	</type>
3104		3212
3105	<!--####################################################################-->	3213	<!--####################################################################-->
3106	<type number="65" name="Mood Floor">	3214	<type number="65" name="Mood Floor">
3107	<ignore>	3215	<ignore>
…		…
3129	</use>	3237	</use>
3130	<attribute arch="no_pick" value="1" type="fixed" />	3238	<attribute arch="no_pick" value="1" type="fixed" />
3131	<attribute arch="last_sp" editor="mood" type="list_mood">	3239	<attribute arch="last_sp" editor="mood" type="list_mood">
3132	<mood> is used to determine what will happen to the	3240	<mood> is used to determine what will happen to the
3133	monster when affected by the mood floor:	3241	monster when affected by the mood floor:
3134		3242
3135	<mood> 'furious': Makes all monsters aggressive	3243	<mood> 'furious': Makes all monsters aggressive
3136		3244
3137	<mood> 'angry': As above but pets are unaffected	3245	<mood> 'angry': As above but pets are unaffected
3138		3246
3139	<mood> 'calm': Makes all monsters unaggressive	3247	<mood> 'calm': Makes all monsters unaggressive
3140		3248
3141	<mood> 'sleep': Puts all monsters to sleep	3249	<mood> 'sleep': Puts all monsters to sleep
3142		3250
3143	<mood> 'charm': Turns monster into a pet of person	3251	<mood> 'charm': Turns monster into a pet of person
3144	who triggers the square. This setting is not	3252	who triggers the square. This setting is not
3145	enabled for continous operation, you need to	3253	enabled for continous operation, you need to
3146	insert a <connection> value!	3254	insert a <connection> value!
3147	</attribute>	3255	</attribute>
3148	<attribute arch="connected" editor="connection" type="int">	3256	<attribute arch="connected" editor="connection" type="int">
3149	This should only be set in combination with <mood number> 4.	3257	This should only be set in combination with <mood number> 4.
3150	Normally, monsters are affected by the mood floor as soon as they	3258	Normally, monsters are affected by the mood floor as soon as they
3151	step on it. But charming (monster -> pet) is too powerful,	3259	step on it. But charming (monster -> pet) is too powerful,
3152	so it needs to be activated.	3260	so it needs to be activated.
3153		3261
3154	Typically it is connected to an altar, for buying a "hireling".	3262	Typically it is connected to an altar, for buying a "hireling".
3155	But a powerful pet could as well be the reward for solving a	3263	But a powerful pet could as well be the reward for solving a
3156	quest. Or even better: It could be part of a quest!	3264	quest. Or even better: It could be part of a quest!
3157	</attribute>	3265	</attribute>
3158	<attribute arch="no_magic" editor="no spells" type="bool">	3266	<attribute arch="no_magic" editor="no spells" type="bool">
…		…
3219	A mover with direction set to <none> will spin clockwise,	3327	A mover with direction set to <none> will spin clockwise,
3220	thus pushing creatures in unpredictable directions.	3328	thus pushing creatures in unpredictable directions.
3221	</attribute>	3329	</attribute>
3222	<attribute arch="lifesave" editor="gets used up" type="bool">	3330	<attribute arch="lifesave" editor="gets used up" type="bool">
3223	If enabled, the mover gets "used up" after a certain number of moves	3331	If enabled, the mover gets "used up" after a certain number of moves
3224	(specified by <number of uses>). If disabled, the mover works infinitly.	3332	(specified by <number of uses>). If disabled, the mover works infinitely.
3225	</attribute>	3333	</attribute>
3226	<attribute arch="hp" editor="number of uses" type="int">	3334	<attribute arch="hp" editor="number of uses" type="int">
3227	This value has only a meaning if <gets used up> is set:	3335	This value has only a meaning if <gets used up> is set:
3228	<number of uses> is the number of times minus one, that it	3336	<number of uses> is the number of times minus one, that it
3229	will move a creature before disappearing. (It will move	3337	will move a creature before disappearing. (It will move
3230	someone <number of uses>+1 times, then vanish).	3338	someone <number of uses>+1 times, then vanish).
3231	</attribute>	3339	</attribute>
3232	<section name="targets">	3340	<section name="targets">
3233	<attribute arch="level" editor="move players" type="bool">	3341	<attribute arch="level" editor="move players" type="bool">
3234	If <move players> is enabled, both players and monsters will be	3342	If <move players> is enabled, both players and monsters will be
3235	moved. In the arches' default it is disabled - thus ONLY monsters	3343	moved. In the arches' default it is disabled - thus ONLY monsters
3236	get moved. Remember that "monsters" includes NPCs!	3344	get moved. Remember that "monsters" includes NPCs!
3237		3345
3238	This feature provides you with the possibility to make NPCs	3346	This feature provides you with the possibility to make NPCs
3239	literally "come to life". Example: The player is talking with an	3347	literally "come to life". Example: The player is talking with an
3240	NPC, speaking a certain keyword. This triggers a magic_ear and	3348	NPC, speaking a certain keyword. This triggers a magic_ear and
3241	activates creators, creating (per default: monster-only) movers	3349	activates creators, creating (per default: monster-only) movers
3242	under the NPC's feet. The NPC starts "walking" on a predefined	3350	under the NPC's feet. The NPC starts "walking" on a predefined
…		…
3275	<attribute arch="no_pick" value="1" type="fixed" />	3383	<attribute arch="no_pick" value="1" type="fixed" />
3276	<attribute arch="slaying" editor="match race" type="string">	3384	<attribute arch="slaying" editor="match race" type="string">
3277	the <match race> defines the object we're looking for. If <match race>	3385	the <match race> defines the object we're looking for. If <match race>
3278	matches the monster's or the player's race, we have a match.	3386	matches the monster's or the player's race, we have a match.
3279	Yes, pedestals can detect a player's race! E.g. you could create a	3387	Yes, pedestals can detect a player's race! E.g. you could create a
3280	place where only fireborns can enter, by setting "slaying unnatural".	3388	place where only fireborns can enter, by setting "slaying unnatural".
3281		3389
3282	If it is set to "player", any player stepping on the pedestal	3390	If it is set to "player", any player stepping on the pedestal
3283	is a match. Very useful if you want to open a gate for players	3391	is a match. Very useful if you want to open a gate for players
3284	but not for monsters.	3392	but not for monsters.
3285	</attribute>	3393	</attribute>
3286	<attribute arch="connected" editor="connection" type="int">	3394	<attribute arch="connected" editor="connection" type="int">
…		…
3376	</attribute>	3484	</attribute>
3377	<attribute arch="attacktype" editor="special effect" type="list_potion_effect">	3485	<attribute arch="attacktype" editor="special effect" type="list_potion_effect">
3378	There are two types of special effects for potions:	3486	There are two types of special effects for potions:
3379	'life restoration' - restore the player's stats lost by death or draining	3487	'life restoration' - restore the player's stats lost by death or draining
3380	(this has nothing in common with the restoration spell!)	3488	(this has nothing in common with the restoration spell!)
3381	'improvement' - increase the player's maximum health/mana/grace	3489	'improvement' - increase the player's maximum health/mana/grace
3382	by a very small amount.	3490	by a very small amount.
3383	</attribute>	3491	</attribute>
3384	<attribute arch="cursed" editor="cursed" type="bool">	3492	<attribute arch="cursed" editor="cursed" type="bool">
3385	If a potion is cursed, benefits generally turn into penalties.	3493	If a potion is cursed, benefits generally turn into penalties.
3386	Note that potions can be "uncursed" by praying over an altar,	3494	Note that potions can be "uncursed" by praying over an altar,
…		…
3542	weapon and projectile. ]]>	3650	weapon and projectile. ]]>
3543	</description>	3651	</description>
3544	<use><![CDATA[	3652	<use><![CDATA[
3545	If you want to create new kinds of projectiles, you could	3653	If you want to create new kinds of projectiles, you could
3546	add an alchemical receipe to create these.	3654	add an alchemical receipe to create these.
3547		3655
3548	Don't create new pairs of weapons & projectiles unless	3656	Don't create new pairs of weapons & projectiles unless
3549	they really fullfill a useful purpose. In fact, even bows	3657	they really fullfill a useful purpose. In fact, even bows
3550	and crossbows are rarely ever used. ]]>	3658	and crossbows are rarely ever used. ]]>
3551	</use>	3659	</use>
3552	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">	3660	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
…		…
3557	</attribute>	3665	</attribute>
3558	<attribute arch="race" editor="ammunition class" type="string">	3666	<attribute arch="race" editor="ammunition class" type="string">
3559	Only shooting weapons with matching <ammunition class> can fire	3667	Only shooting weapons with matching <ammunition class> can fire
3560	these projectiles. For arrows set "arrows", for crossbow bolts	3668	these projectiles. For arrows set "arrows", for crossbow bolts
3561	set "crossbow bolts" (big surprise).	3669	set "crossbow bolts" (big surprise).
3562		3670
3563	In certain cases, the ammunition class is displayed in the game.	3671	In certain cases, the ammunition class is displayed in the game.
3564	Hence, when you create a new ammunition class, choose an	3672	Hence, when you create a new ammunition class, choose an
3565	intuitive name like "missiles", "spirit bolts" - whatever.	3673	intuitive name like "missiles", "spirit bolts" - whatever.
3566		3674
3567	You can also make special containers holding these projectiles	3675	You can also make special containers holding these projectiles
3568	by setting the <container class> to match your <ammunition class>.	3676	by setting the <container class> to match your <ammunition class>.
3569	</attribute>	3677	</attribute>
3570	<attribute arch="slaying" editor="slaying race" type="string">	3678	<attribute arch="slaying" editor="slaying race" type="string">
3571	Slaying means the weapon does tripple (3x) damage to monsters	3679	Slaying means the weapon does tripple (3x) damage to monsters
…		…
3687	<attribute arch="value" />	3795	<attribute arch="value" />
3688	<attribute arch="material" />	3796	<attribute arch="material" />
3689	<attribute arch="unpaid" />	3797	<attribute arch="unpaid" />
3690	</ignore>	3798	</ignore>
3691	<description><![CDATA[	3799	<description><![CDATA[
3692	A rune is a magical enscription on the dungeon floor.	3800	A rune is a magical enscription on the dungeon floor.
3693	<br><br>	3801	<br><br>
3694	Runes hit any monster or person who steps on them for 'dam' damage in	3802	Runes hit any monster or person who steps on them for 'dam' damage in
3695	'attacktype' attacktype. Alternatively, the rune could contain any spell,	3803	'attacktype' attacktype. Alternatively, the rune could contain any spell,
3696	and will cast this spell when it detonates. Yet another kind is the	3804	and will cast this spell when it detonates. Yet another kind is the
3697	"summoning rune", summoning predefined monsters of any kind, at detonation.	3805	"summoning rune", summoning predefined monsters of any kind, at detonation.
…		…
3705	<attribute arch="no_pick" value="1" type="fixed" />	3813	<attribute arch="no_pick" value="1" type="fixed" />
3706	<attribute arch="walk_on" value="1" type="fixed" />	3814	<attribute arch="walk_on" value="1" type="fixed" />
3707	<attribute arch="level" editor="rune level" type="int">	3815	<attribute arch="level" editor="rune level" type="int">
3708	This value sets the level the rune will cast the spell it contains at,	3816	This value sets the level the rune will cast the spell it contains at,
3709	if applicable. A level 99 rune casts a very, very mean spell of whatever.	3817	if applicable. A level 99 rune casts a very, very mean spell of whatever.
3710	(<rune level> 0 runes won't detonate at all!)	3818	(<rune level> 0 runes won't detonate at all!)
3711		3819
3712	Level Also effects how easily a rune may be found and disarmed, and	3820	Level Also effects how easily a rune may be found and disarmed, and
3713	how much experience the player gets for doing so. Beware: High level	3821	how much experience the player gets for doing so. Beware: High level
3714	runes can be quite a cheap source of experience! So either make them	3822	runes can be quite a cheap source of experience! So either make them
3715	tough, or keep the level low.	3823	tough, or keep the level low.
3716	</attribute>	3824	</attribute>
…		…
3723	The rune will detonate <number of charges> times before disappearing.	3831	The rune will detonate <number of charges> times before disappearing.
3724	</attribute>	3832	</attribute>
3725	<attribute arch="dam" editor="direct damage" type="int">	3833	<attribute arch="dam" editor="direct damage" type="int">
3726	<direct damage> specifies how much damage is done by the rune,	3834	<direct damage> specifies how much damage is done by the rune,
3727	if it doesn't contain a spell. This should be set in reasonable	3835	if it doesn't contain a spell. This should be set in reasonable
3728	relation to the rune's level.	3836	relation to the rune's level.
3729	</attribute>	3837	</attribute>
3730	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">	3838	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
3731	If there isn't any spell (and <summon monster> is unset), this	3839	If there isn't any spell (and <summon monster> is unset), this
3732	attribute defines what attacktype to use for direct damage when	3840	attribute defines what attacktype to use for direct damage when
3733	the rune detonates.	3841	the rune detonates.
…		…
3798	<attribute arch="no_magic" value="1" type="fixed" />	3906	<attribute arch="no_magic" value="1" type="fixed" />
3799	<attribute arch="damned" value="1" type="fixed" />	3907	<attribute arch="damned" value="1" type="fixed" />
3800	</type>	3908	</type>
3801		3909
3802	<!--####################################################################-->	3910	<!--####################################################################-->
		3911	<type number="111" name="Scroll">
		3912	<ignore>
		3913	<attribute arch="title" />
		3914	</ignore>
		3915	<description><![CDATA[
		3916	Scrolls contain spells (similar to spell-potions). Unlike potions,
		3917	scrolls require a certain literacy skill to read successfully.
		3918	Accordingly, for a successful reading, a small amount of
		3919	experience is gained. Scrolls allow only one time usage, but
		3920	usually they are sold in bulks. ]]>
		3921	</description>
		3922	<use><![CDATA[
		3923	For low level quests, scrolls of healing/curing-spells
		3924	can be a nice reward. At higher levels, scrolls become less
		3925	and less useful. ]]>
		3926	</use>
		3927	<attribute arch="level" editor="casting level" type="int">
		3928	The spell of the scroll will be casted at this level.
		3929	This value should always be set, at least to 1.
		3930	</attribute>
		3931	<attribute arch="sp" editor="spell" type="spell">
		3932	When a player/monster applies this scroll, the selected <spell>
		3933	will be casted (once). This should work for any given spell.
		3934	</attribute>
		3935	<attribute arch="startequip" editor="godgiven item" type="bool">
		3936	A godgiven item vanishes as soon as the player
		3937	drops it to the ground.
		3938	</attribute>
		3939	</type>
		3940
		3941	<!--####################################################################-->
		3942	<type number="33" name="Shield">
		3943	<import_type name="Amulet" />
		3944	<description><![CDATA[
		3945	Wearing a shield, the object's stats will directly be inherited to
		3946	the player. Shields usually provide good defense, only surpassed
		3947	by brestplate armour. Resistances on shields aren't uncommon either. ]]>
		3948	</description>
		3949	<use><![CDATA[
		3950	Feel free to create your own special artifacts. However, it is very
		3951	important that you keep your artifact in balance with existing maps. ]]>
		3952	</use>
		3953	<attribute arch="magic" editor="magic bonus" type="int">
		3954	<magic bonus> works just like ac, except that it can be improved by
		3955	"scrolls of Enchant Armour" or reduced by acid. It is less useful
		3956	than direct armour-class bonus on the shield.
		3957	</attribute>
		3958	</type>
		3959
		3960	<!--####################################################################-->
3803	<type number="14" name="Shooting Weapon">	3961	<type number="14" name="Shooting Weapon">
3804	<description><![CDATA[	3962	<description><![CDATA[
3805	Schooting weapons like bows/crossbows are used to shoot projectiles	3963	Schooting weapons like bows/crossbows are used to shoot projectiles
3806	(arrows/bolts). Shooting weapons and normal (melee) weapons can be	3964	(arrows/bolts). Shooting weapons and normal (melee) weapons can be
3807	wielded both at the same time. Like with any other equipment,	3965	wielded both at the same time. Like with any other equipment,
…		…
3821	</use>	3979	</use>
3822	<attribute arch="race" editor="ammunition class" type="string">	3980	<attribute arch="race" editor="ammunition class" type="string">
3823	Only projectiles with matching <ammunition class> can be fired	3981	Only projectiles with matching <ammunition class> can be fired
3824	with this weapon. For normal bows set "arrows", for normal	3982	with this weapon. For normal bows set "arrows", for normal
3825	crossbows set "crossbow bolts".	3983	crossbows set "crossbow bolts".
3826		3984
3827	In certain cases, the ammunition class is displayed in the game.	3985	In certain cases, the ammunition class is displayed in the game.
3828	Hence, when you create a new ammunition class, choose an	3986	Hence, when you create a new ammunition class, choose an
3829	intuitive name like "missiles", "spirit bolts" - whatever.	3987	intuitive name like "missiles", "spirit bolts" - whatever.
3830	</attribute>	3988	</attribute>
3831	<attribute arch="sp" editor="shooting speed" type="int">	3989	<attribute arch="sp" editor="shooting speed" type="int">
3832	After shooting a projectile, the player is frozen for a short	3990	After shooting a projectile, the player is frozen for a short
3833	period of time (to prevent shooting arrows machine-gun-like).	3991	period of time (to prevent shooting arrows machine-gun-like).
3834	The greater <shooting speed>, the shorter this period of time.	3992	The greater <shooting speed>, the shorter this period of time.
3835	1 is minimum (=worst) and 100 is maximum (=best) value.	3993	1 is minimum (=worst) and 100 is maximum (=best) value.
3836		3994
3837	You shouldn't set <shooting speed> lower than 10. YOU MUST NOT	3995	You shouldn't set <shooting speed> lower than 10. YOU MUST NOT
3838	SET IT TO ZERO! (That would freeze the player for eternety).	3996	SET IT TO ZERO! (That would freeze the player for eternety).
3839	</attribute>	3997	</attribute>
3840	<attribute arch="dam" editor="base damage" type="int">	3998	<attribute arch="dam" editor="base damage" type="int">
3841	The <base damage> significantly affects the damage done	3999	The <base damage> significantly affects the damage done
…		…
3852	The <item power> value measures how "powerful" an artifact is.	4010	The <item power> value measures how "powerful" an artifact is.
3853	Players will only be able to wear equipment with a certain total	4011	Players will only be able to wear equipment with a certain total
3854	amount of <item power>, depending on their own level. This is the	4012	amount of <item power>, depending on their own level. This is the
3855	only way to prevent low level players to wear "undeserved" equipment	4013	only way to prevent low level players to wear "undeserved" equipment
3856	(like gifts from other players or cheated items).	4014	(like gifts from other players or cheated items).
3857		4015
3858	It is very important to adjust the <item power> value carefully	4016	It is very important to adjust the <item power> value carefully
3859	for every artifact you create! If zero/unset, the CF server will	4017	for every artifact you create! If zero/unset, the CF server will
3860	calculate a provisional value at runtime, but this is never	4018	calculate a provisional value at runtime, but this is never
3861	going to be an accurate measurement of <item power>.	4019	going to be an accurate measurement of <item power>.
3862	</attribute>	4020	</attribute>
…		…
3933	should have such a description.	4091	should have such a description.
3934	</attribute>	4092	</attribute>
3935	</type>	4093	</type>
3936		4094
3937	<!--####################################################################-->	4095	<!--####################################################################-->
3938	<type number="111" name="Scroll">
3939	<ignore>
3940	<attribute arch="title" />
3941	</ignore>
3942	<description><![CDATA[
3943	Scrolls contain spells (similar to spell-potions). Unlike potions,
3944	scrolls require a certain literacy skill to read successfully.
3945	Accordingly, for a successful reading, a small amount of
3946	experience is gained. Scrolls allow only one time usage, but
3947	usually they are sold in bulks. ]]>
3948	</description>
3949	<use><![CDATA[
3950	For low level quests, scrolls of healing/curing-spells
3951	can be a nice reward. At higher levels, scrolls become less
3952	and less useful. ]]>
3953	</use>
3954	<attribute arch="level" editor="casting level" type="int">
3955	The spell of the scroll will be casted at this level.
3956	This value should always be set, at least to 1.
3957	</attribute>
3958	<attribute arch="sp" editor="spell" type="spell">
3959	When a player/monster applies this scroll, the selected <spell>
3960	will be casted (once). This should work for any given spell.
3961	</attribute>
3962	<attribute arch="startequip" editor="godgiven item" type="bool">
3963	A godgiven item vanishes as soon as the player
3964	drops it to the ground.
3965	</attribute>
3966	</type>
3967
3968	<!--####################################################################-->
3969	<type number="33" name="Shield">
3970	<import_type name="Amulet" />
3971	<description><![CDATA[
3972	Wearing a shield, the object's stats will directly be inherited to
3973	the player. Shields usually provide good defense, only surpassed
3974	by brestplate armour. Resistances on shields aren't uncommon either. ]]>
3975	</description>
3976	<use><![CDATA[
3977	Feel free to create your own special artifacts. However, it is very
3978	important that you keep your artifact in balance with existing maps. ]]>
3979	</use>
3980	<attribute arch="magic" editor="magic bonus" type="int">
3981	<magic bonus> works just like ac, except that it can be improved by
3982	"scrolls of Enchant Armour" or reduced by acid. It is less useful
3983	than direct armour-class bonus on the shield.
3984	</attribute>
3985	</type>
3986
3987	<!--####################################################################-->
3988	<type number="68" name="Shop Floor">	4096	<type number="68" name="Shop Floor">
3989	<ignore>	4097	<ignore>
3990	<ignore_list name="non_pickable" />	4098	<ignore_list name="non_pickable" />
3991	</ignore>	4099	</ignore>
3992	<description><![CDATA[	4100	<description><![CDATA[
…		…
4103	<attribute arch="food" editor="counter" type="int">	4211	<attribute arch="food" editor="counter" type="int">
4104	If a counter-value is set (greater zero), the sign/magic_mouth can be applied	4212	If a counter-value is set (greater zero), the sign/magic_mouth can be applied
4105	(printing the message) only that many times. For signs this really shouldn't	4213	(printing the message) only that many times. For signs this really shouldn't
4106	be used, while for magic_mouths it is extremely helpful.	4214	be used, while for magic_mouths it is extremely helpful.
4107	Monsters walking over the magic_mouth do not decrease the counter.	4215	Monsters walking over the magic_mouth do not decrease the counter.
4108		4216
4109	Often, you might want to have a message displayed only one time. For example:	4217	Often, you might want to have a message displayed only one time. For example:
4110	The player enters your map and you put a magic_mouth to tell him about the	4218	The player enters your map and you put a magic_mouth to tell him about the
4111	monsters and how dangerous they look and all. Later, when all the monsters	4219	monsters and how dangerous they look and all. Later, when all the monsters
4112	are killed and the player leaves the map, displaying the same message a	4220	are killed and the player leaves the map, displaying the same message a
4113	second time would be silly. <counter> 1 does a perfect job in such cases.	4221	second time would be silly. <counter> 1 does a perfect job in such cases.
…		…
4230	burned or otherwise destroyed.	4338	burned or otherwise destroyed.
4231	</attribute>	4339	</attribute>
4232	<attribute arch="unique" editor="unique item" type="bool">	4340	<attribute arch="unique" editor="unique item" type="bool">
4233	Unique items exist only one time on a server. If the item	4341	Unique items exist only one time on a server. If the item
4234	is taken, lost or destroyed - it's gone for good.	4342	is taken, lost or destroyed - it's gone for good.
4235		4343
4236	This can be used if you want to sell apartments on your	4344	This can be used if you want to sell apartments on your
4237	map: Simply sell a unique passport/key, and place	4345	map: Simply sell a unique passport/key, and place
4238	an inventory checker at the entrance of your apartment.	4346	an inventory checker at the entrance of your apartment.
4239	</attribute>	4347	</attribute>
4240	<attribute arch="startequip" editor="godgiven item" type="bool">	4348	<attribute arch="startequip" editor="godgiven item" type="bool">
…		…
4357	<use><![CDATA[	4465	<use><![CDATA[
4358	Spinners are very rarely used. I believe they are quite	4466	Spinners are very rarely used. I believe they are quite
4359	confusing and pointless. The only use I can think of is building	4467	confusing and pointless. The only use I can think of is building
4360	some puzzle about where to shoot into spinners to shoot somewhere you	4468	some puzzle about where to shoot into spinners to shoot somewhere you
4361	otherwise couldn't.	4469	otherwise couldn't.
4362		4470
4363	When placing spinners on a map with magic walls, make sure the spell-	4471	When placing spinners on a map with magic walls, make sure the spell-
4364	projectiles from magic walls don't get to fly in loops. ]]>	4472	projectiles from magic walls don't get to fly in loops. ]]>
4365	</use>	4473	</use>
4366	<attribute arch="sp" editor="direction number" type="int">	4474	<attribute arch="sp" editor="direction number" type="int">
4367	The spinner will change the direction of flying objects by	4475	The spinner will change the direction of flying objects by
4368	45 degrees per <direction number>. Negative values spin clockwise,	4476	45 degrees per <direction number>. Negative values spin clockwise,
4369	positive values counter clockwise.	4477	positive values counter clockwise.
4370		4478
4371	Example: <direction number> -2 means spin 90 degrees clockwise.	4479	Example: <direction number> -2 means spin 90 degrees clockwise.
4372	</attribute>	4480	</attribute>
4373	<attribute arch="walk_on" value="1" type="fixed" />	4481	<attribute arch="walk_on" value="1" type="fixed" />
4374	<attribute arch="fly_on" value="1" type="fixed" />	4482	<attribute arch="fly_on" value="1" type="fixed" />
4375	</type>	4483	</type>
…		…
4396	and unexpected death-trap. Players should get a warning before such areas.	4504	and unexpected death-trap. Players should get a warning before such areas.
4397	</attribute>	4505	</attribute>
4398	<attribute arch="slow_move" editor="slow movement" type="int">	4506	<attribute arch="slow_move" editor="slow movement" type="int">
4399	If <slow movement> is set to a value greater zero, all	4507	If <slow movement> is set to a value greater zero, all
4400	creatures moving over this spot will be slower than normal.	4508	creatures moving over this spot will be slower than normal.
4401		4509
4402	<slow movement> 1 - rough terrain	4510	<slow movement> 1 - rough terrain
4403	<slow movement> 2 - very rough terrain	4511	<slow movement> 2 - very rough terrain
4404	...	4512	...
4405	<slow movement> 5 - default for deep swamp	4513	<slow movement> 5 - default for deep swamp
4406	</attribute>	4514	</attribute>
…		…
4445	(for example "/peterm/FireTemple/fire1"). It can also be a relative	4553	(for example "/peterm/FireTemple/fire1"). It can also be a relative
4446	path, not beginning with '/' (On the map "/peterm/FireTemple/Fire2"	4554	path, not beginning with '/' (On the map "/peterm/FireTemple/Fire2"
4447	for example I could use the relative path "Fire1"). Use relative	4555	for example I could use the relative path "Fire1"). Use relative
4448	paths whenever possible! Note that upper/lower case must always be	4556	paths whenever possible! Note that upper/lower case must always be
4449	set correctly. However, please use lower case only.	4557	set correctly. However, please use lower case only.
4450		4558
4451	If the <exit path> is set, ONLY players can get teleported. If the	4559	If the <exit path> is set, ONLY players can get teleported. If the
4452	<exit path> is unset (empty), anything can get teleported: Players,	4560	<exit path> is unset (empty), anything can get teleported: Players,
4453	monsters and items. In this case, the destined map is automatically	4561	monsters and items. In this case, the destined map is automatically
4454	the same map the teleporter is on.	4562	the same map the teleporter is on.
4455	</attribute>	4563	</attribute>
4456	<attribute arch="hp" editor="destination X" type="int">	4564	<attribute arch="hp" editor="destination X" type="int">
4457	The exit destinations define the (x, y)-coordinates where the exit	4565	The exit destinations define the (x, y)-coordinates where the exit
4458	leads to.	4566	leads to.
4459		4567
4460	If both are set to zero and <exit path> is empty, the player will	4568	If both are set to zero and <exit path> is empty, the player will
4461	get teleported to another, randomly chosen teleporter on the same	4569	get teleported to another, randomly chosen teleporter on the same
4462	map (Slightly confusing for the player though). Make sure there	4570	map (Slightly confusing for the player though). Make sure there
4463	actually is a second one in that case.	4571	actually is a second one in that case.
4464		4572
4465	If both are set to zero and <exit path> is set, the player will	4573	If both are set to zero and <exit path> is set, the player will
4466	be transferred to the "default enter location" of the destined map.	4574	be transferred to the "default enter location" of the destined map.
4467	The latter can be set in the map-properties as "Enter X/Y". Though,	4575	The latter can be set in the map-properties as "Enter X/Y". Though,
4468	please DO NOT use that. It turned out to be a source for numerous	4576	please DO NOT use that. It turned out to be a source for numerous
4469	map-bugs.	4577	map-bugs.
4470	</attribute>	4578	</attribute>
4471	<attribute arch="sp" editor="destination Y" type="int">	4579	<attribute arch="sp" editor="destination Y" type="int">
4472	The exit destinations define the (x, y)-coordinates where the exit	4580	The exit destinations define the (x, y)-coordinates where the exit
4473	leads to.	4581	leads to.
4474		4582
4475	If both are set to zero and <exit path> is empty, the player will	4583	If both are set to zero and <exit path> is empty, the player will
4476	get teleported to another, randomly chosen teleporter on the same	4584	get teleported to another, randomly chosen teleporter on the same
4477	map (Slightly confusing for the player though). Make sure there	4585	map (Slightly confusing for the player though). Make sure there
4478	actually is a second one in that case.	4586	actually is a second one in that case.
4479		4587
4480	If both are set to zero and <exit path> is set, the player will	4588	If both are set to zero and <exit path> is set, the player will
4481	be transferred to the "default enter location" of the destined map.	4589	be transferred to the "default enter location" of the destined map.
4482	The latter can be set in the map-properties as "Enter X/Y". Though,	4590	The latter can be set in the map-properties as "Enter X/Y". Though,
4483	please DO NOT use that. It turned out to be a source for numerous	4591	please DO NOT use that. It turned out to be a source for numerous
4484	map-bugs.	4592	map-bugs.
…		…
4491	<attribute arch="speed" editor="activation speed" type="float">	4599	<attribute arch="speed" editor="activation speed" type="float">
4492	If the <activation speed> is nonzero, the teleporter will	4600	If the <activation speed> is nonzero, the teleporter will
4493	automatically be activated in regular time-intervals. Hence, the	4601	automatically be activated in regular time-intervals. Hence, the
4494	player can just step on it and gets teleported sooner or later.	4602	player can just step on it and gets teleported sooner or later.
4495	The duration between two activates depends on the given value.	4603	The duration between two activates depends on the given value.
4496	Default in the teleporter arch is <activation speed> 0.1.	4604	Default in the teleporter arch is <activation speed> 0.1.
4497		4605
4498	VERY IMPORTANT: If you want to have your teleporter activated via	4606	VERY IMPORTANT: If you want to have your teleporter activated via
4499	button/handle/magic_ear/etc, you must set <activation speed> to zero!	4607	button/handle/magic_ear/etc, you must set <activation speed> to zero!
		4608	</attribute>
		4609	</type>
		4610
		4611	<!--####################################################################-->
		4612	<type number="26" name="Timed Gate">
		4613	<ignore>
		4614	<ignore_list name="non_pickable" />
		4615	</ignore>
		4616	<description><![CDATA[
		4617	Gates play an important role in Crossfire. Gates can be opened
		4618	by activating a button/trigger, by speaking passwords (-> magic_ear)
		4619	or carrying special key-objects (-> inventory checker).
		4620	Unlike locked doors, gates can get shut again after a player has
		4621	passed, which makes them more practical in many cases. Unlike normal
		4622	gates, timed gates open when triggered but automatically close again
		4623	after some time.]]>
		4624	</description>
		4625	<use><![CDATA[
		4626	Use gates to divide your maps into separated areas. After solving
		4627	area A, the player gains access to area B, and so on. Make your
		4628	maps more complex than "one-way". ]]>
		4629	</use>
		4630	<attribute arch="no_pick" value="1" type="fixed" />
		4631	<attribute arch="connected" editor="connection" type="int">
		4632	Whenever the inventory checker is triggered, all objects with identical
		4633	<connection> value get activated. This only makes sense together with
		4634	<blocking passage> disabled. If unset, the gate opens automatically
		4635	after some time.
		4636	</attribute>
		4637	<attribute arch="wc" editor="position state" type="int">
		4638	The <position state> defines the position of the gate:
		4639	Zero means completely open/down, the "number of animation-steps" (usually
		4640	about 6 or 7) means completely closed/up state. I suggest you don't
		4641	mess with this value - Leave the default in place.
		4642	</attribute>
		4643	<attribute arch="no_pass" editor="blocking passage" type="bool">
		4644	For open gates, <blocking passage> should be unset.
		4645	For closed gates it must be set.
		4646	</attribute>
		4647	<attribute arch="no_magic" editor="restrict spells" type="bool">
		4648	Restricting the use of spells to pass this gate. This has
		4649	an effect only if <block view> is disabled.
		4650	</attribute>
		4651	<attribute arch="damned" editor="restrict prayers" type="bool">
		4652	Restricting the use of prayers to pass this door. This has
		4653	an effect only if <block view> is disabled.
		4654	</attribute>
		4655	<attribute arch="hp" editor="open duration" type="int">
		4656	Defines the duration the gate remains closed. This only takes effect
		4657	if the gate is not connected.
4500	</attribute>	4658	</attribute>
4501	</type>	4659	</type>
4502		4660
4503	<!--####################################################################-->	4661	<!--####################################################################-->
4504	<type number="155" name="Trap">	4662	<type number="155" name="Trap">
…		…
4511	<attribute arch="material" />	4669	<attribute arch="material" />
4512	<attribute arch="unpaid" />	4670	<attribute arch="unpaid" />
4513	</ignore>	4671	</ignore>
4514	<description><![CDATA[	4672	<description><![CDATA[
4515	A trap is a object that can either do damage or trigger another connected object	4673	A trap is a object that can either do damage or trigger another connected object
4516	when detonated. Traps are like runes except they are not magical in nature,	4674	when detonated. Traps are like runes except they are not magical in nature,
4517	and generally have either a physical attack or trigger a reaction.	4675	and generally have either a physical attack or trigger a reaction.
4518	<br><br>	4676	<br><br>
4519	Traps hit any monster or person who steps on them for 'dam' damage in	4677	Traps hit any monster or person who steps on them for 'dam' damage in
4520	'attacktype' attacktype and/or trigger a reaction.	4678	'attacktype' attacktype and/or trigger a reaction.
4521	<br><br>	4679	<br><br>
…		…
4525	Avoid monsters stepping on your traps. For example, a party of orcs setting	4683	Avoid monsters stepping on your traps. For example, a party of orcs setting
4526	off your lightning wall and pit trap is usually a bad idea. ]]>	4684	off your lightning wall and pit trap is usually a bad idea. ]]>
4527	</use>	4685	</use>
4528	<attribute arch="no_pick" value="1" type="fixed" />	4686	<attribute arch="no_pick" value="1" type="fixed" />
4529	<attribute arch="walk_on" value="1" type="fixed" />	4687	<attribute arch="walk_on" value="1" type="fixed" />
4530	<attribute arch="level" editor="trap level" type="int">	4688	<attribute arch="level" editor="trap level" type="int">
4531	Level effects how easily a trap may be found and disarmed, and	4689	Level effects how easily a trap may be found and disarmed, and
4532	how much experience the player gets for doing so. Beware: High level	4690	how much experience the player gets for doing so. Beware: High level
4533	traps can be quite a cheap source of experience! So either make them	4691	traps can be quite a cheap source of experience! So either make them
4534	tough, or keep the level low.	4692	tough, or keep the level low.
4535	</attribute>	4693	</attribute>
…		…
4540	</attribute>	4698	</attribute>
4541	<attribute arch="hp" editor="number of charges" type="int">	4699	<attribute arch="hp" editor="number of charges" type="int">
4542	The trap will detonate <number of charges> times before disappearing.	4700	The trap will detonate <number of charges> times before disappearing.
4543	</attribute>	4701	</attribute>
4544	<attribute arch="dam" editor="direct damage" type="int">	4702	<attribute arch="dam" editor="direct damage" type="int">
4545	<direct damage> specifies how much damage is done by the trap.	4703	<direct damage> specifies how much damage is done by the trap.
4546	This should be set in reasonable relation to the trap's level.	4704	This should be set in reasonable relation to the trap's level.
4547	</attribute>	4705	</attribute>
4548	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">	4706	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
4549	This attribute defines what attacktype to use for direct damage when	4707	This attribute defines what attacktype to use for direct damage when
4550	the trap detonates.	4708	the trap detonates.
4551	</attribute>	4709	</attribute>
…		…
4650	<quality level> 5 per default).	4808	<quality level> 5 per default).
4651	</attribute>	4809	</attribute>
4652	</type>	4810	</type>
4653		4811
4654	<!--####################################################################-->	4812	<!--####################################################################-->
		4813	<type number="52" name="Trigger Marker">
		4814	<ignore>
		4815	<ignore_list name="system_object" />
		4816	</ignore>
		4817	<description><![CDATA[
		4818	A trigger marker is an object that inserts an invisible force (a mark) into a
		4819	player stepping on it WHEN TRIGGERED. This force does nothing except containing a
		4820	<key string> which can be discovered by detectors or inventory
		4821	checkers. It is also possible to use markers for removing marks again.
		4822	<br><br>
		4823	Note that the player has no possibility to "see" his own marks,
		4824	except by the effect that they cause on the maps. ]]>
		4825	</description>
		4826	<use><![CDATA[
		4827	Markers hold real cool possibilities for map-making. I encourage
		4828	you to use them frequently. However there is one negative point
		4829	about markers: Players don't "see" what's going on with them. It is
		4830	your task, as map-creator, to make sure the player is always well
		4831	informed and never confused.
		4832	<br><br>
		4833	Please avoid infinite markers when they aren't needed. They're
		4834	using a little space in the player file after all, so if there
		4835	is no real purpose, set an expire time. ]]>
		4836	</use>
		4837	<attribute arch="no_pick" value="1" type="fixed" />
		4838	<attribute arch="slaying" editor="key string" type="string">
		4839	The <key string> can be detected by inv. checkers/detectors.
		4840	If the player already has a force with that <key string>,
		4841	there won't be inserted a second one.
		4842	</attribute>
		4843	<attribute arch="connected" editor="connection" type="int">
		4844	Unlike a regular marker this is the connection that triggers this marker to activate.
		4845	</attribute>
		4846	<attribute arch="food" editor="mark duration" type="int">
		4847	This value defines the duration of the force it inserts.
		4848	If nonzero, the duration of the player's mark is finite:
		4849	about 1 food per 10 seconds. <mark duration> zero/unset
		4850	means the mark will stay on the player forever.
		4851	</attribute>
		4852	<attribute arch="name" editor="delete mark" type="string">
		4853	When the player steps onto the marker, all existing forces in
		4854	the players inventory with a <key string> matching <delete mark>
		4855	will be removed. If you don't want to remove any marks, leave
		4856	this textfield empty.
		4857
		4858	Note that the string <delete mark> is set as the name of
		4859	this marker. So don't be confused, and remember changing the
		4860	name will take effect on the marker's functionality.
		4861	</attribute>
		4862	<attribute arch_begin="msg" arch_end="endmsg" editor="marking message" type="text">
		4863	In the moment when the player gets marked, this text is displayed
		4864	to him. You should really set a message in any marker you create,
		4865	because it's the only way for the player to notice what's going on.
		4866	</attribute>
		4867	</type>
		4868
		4869	<!--####################################################################-->
4655	<type number="0" name="Wall">	4870	<type number="0" name="Wall">
4656	<required>	4871	<required>
4657	<attribute arch="is_floor" value="0" />	4872	<attribute arch="is_floor" value="0" />
4658	<attribute arch="alive" value="0" />	4873	<attribute arch="alive" value="0" />
4659	<attribute arch="no_pass" value="1" />	4874	<attribute arch="no_pass" value="1" />
…		…
4680	Restricting the use of spells to pass this wall.	4895	Restricting the use of spells to pass this wall.
4681	</attribute>	4896	</attribute>
4682	<attribute arch="damned" editor="restrict prayers" type="bool">	4897	<attribute arch="damned" editor="restrict prayers" type="bool">
4683	This takes effect only with <blocksview> disabled.	4898	This takes effect only with <blocksview> disabled.
4684	Restricting the use of spells to pass this wall.	4899	Restricting the use of spells to pass this wall.
		4900	</attribute>
		4901	</type>
		4902
		4903	<!--####################################################################-->
		4904	<type number="109" name="Wand & Staff">
		4905	<description><![CDATA[
		4906	Wands contain a certain spell. The player can apply (ready) and
		4907	fire the wand. After a defined number of casts, the wand is
		4908	"used up". It is possible to recharge a wand with scrolls of
		4909	charging, but usually that isn't worth the cost. ]]>
		4910	</description>
		4911	<use><![CDATA[
		4912	Wands are quite seldomly used. The reason prolly is that they're
		4913	generally not cost-efficient. Handing out high-level wands with
		4914	powerful special spells isn't a good idea either, because of
		4915	the recharge ability.
		4916	<br><br>
		4917	For low levels, staffs of healing/cure and word of recall are
		4918	quite desirable though. Ideal rewards for low level quests. ]]>
		4919	</use>
		4920	<attribute arch="sp" editor="spell" type="spell">
		4921	The <spell> specifies the contained spell.
		4922	</attribute>
		4923	<attribute arch="level" editor="casting level" type="int">
		4924	The <casting level> of the wand determines it's power.
		4925	An average level for wands in shops is about 10.
		4926	</attribute>
		4927	<attribute arch="food" editor="number of charges" type="int">
		4928	The wand can be used <number of charges> times before it is
		4929	used up. It can be recharged with scrolls of charging.
		4930	</attribute>
		4931	<attribute arch="startequip" editor="godgiven item" type="bool">
		4932	A godgiven item vanishes as soon as the player
		4933	drops it to the ground.
		4934	</attribute>
		4935	<attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
		4936	This text may contain a description of the wand.
4685	</attribute>	4937	</attribute>
4686	</type>	4938	</type>
4687		4939
4688	<!--####################################################################-->	4940	<!--####################################################################-->
4689	<type number="0" name="Weak Wall">	4941	<type number="0" name="Weak Wall">
…		…
4799	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">	5051	<attribute arch="attacktype" editor="attacktype" type="bitmask_attacktype">
4800	This number is a bitmask, specifying the weapon's attacktypes.	5052	This number is a bitmask, specifying the weapon's attacktypes.
4801	Attacktypes are: physical, magical, fire, cold.. etc. Most artifact weapons	5053	Attacktypes are: physical, magical, fire, cold.. etc. Most artifact weapons
4802	have no more than one or two attacktypes. Keep in mind that all weapons	5054	have no more than one or two attacktypes. Keep in mind that all weapons
4803	can be blessed by the player's diety, thus adding an additional attacktype.	5055	can be blessed by the player's diety, thus adding an additional attacktype.
4804		5056
4805	When a player hits a monster with a weapon that has more than one attacktype,	5057	When a player hits a monster with a weapon that has more than one attacktype,
4806	then he will do as much damage as the "best" of his attacktypes does. So,	5058	then he will do as much damage as the "best" of his attacktypes does. So,
4807	the more attacktypes you've got, the better your chance to take advantage	5059	the more attacktypes you've got, the better your chance to take advantage
4808	of a monster's vulnerabilities. (Btw: Same rule applies for monster vs.	5060	of a monster's vulnerabilities. (Btw: Same rule applies for monster vs.
4809	player.). Attacktypes "magic" and "chaos" are somehow exceptions.	5061	player.). Attacktypes "magic" and "chaos" are somehow exceptions.
…		…
4811	<attribute arch="weapontype" editor="weapontype" type="list_weapon_type">	5063	<attribute arch="weapontype" editor="weapontype" type="list_weapon_type">
4812	The <weapontype> characterizes the weapon's type of physical	5064	The <weapontype> characterizes the weapon's type of physical
4813	attack. It could best be considered a "subclassification"	5065	attack. It could best be considered a "subclassification"
4814	of the physical attacktype. For now, this is only used for	5066	of the physical attacktype. For now, this is only used for
4815	attack messages!	5067	attack messages!
4816		5068
4817	You should always set this correctly when creating new	5069	You should always set this correctly when creating new
4818	weapons for your maps.	5070	weapons for your maps.
4819	</attribute>	5071	</attribute>
4820	<attribute arch="skill" editor="skill name" type="string">	5072	<attribute arch="skill" editor="skill name" type="string">
4821	Matching <skill name> of the skill that is required	5073	Matching <skill name> of the skill that is required
…		…
4829	</attribute>	5081	</attribute>
4830	<attribute arch="slaying" editor="slaying race" type="string">	5082	<attribute arch="slaying" editor="slaying race" type="string">
4831	Slaying means the weapon does tripple (3x) damage to monsters of the	5083	Slaying means the weapon does tripple (3x) damage to monsters of the
4832	specified race. If <slaying race> matches an arch name (e.g. "big_dragon"),	5084	specified race. If <slaying race> matches an arch name (e.g. "big_dragon"),
4833	only monsters of that archtype are hit with tripple damage.	5085	only monsters of that archtype are hit with tripple damage.
4834		5086
4835	No god blessings are possible for weapons with a race set in this entry	5087	No god blessings are possible for weapons with a race set in this entry
4836	(That's because god blessings add tripple damage against their own	5088	(That's because god blessings add tripple damage against their own
4837	enemy races). Tripple damage is very effective.	5089	enemy races). Tripple damage is very effective.
4838	</attribute>	5090	</attribute>
4839	<attribute arch="last_sp" editor="weapon speed" type="int">	5091	<attribute arch="last_sp" editor="weapon speed" type="int">
…		…
4855	The <item power> value measures how "powerful" an artifact is.	5107	The <item power> value measures how "powerful" an artifact is.
4856	Players will only be able to wear equipment with a certain total	5108	Players will only be able to wear equipment with a certain total
4857	amount of <item power>, depending on their own level. This is the	5109	amount of <item power>, depending on their own level. This is the
4858	only way to prevent low level players to wear "undeserved" equipment	5110	only way to prevent low level players to wear "undeserved" equipment
4859	(like gifts from other players or cheated items).	5111	(like gifts from other players or cheated items).
4860		5112
4861	It is very important to adjust the <item power> value carefully	5113	It is very important to adjust the <item power> value carefully
4862	for every artifact you create! If zero/unset, the CF server will	5114	for every artifact you create! If zero/unset, the CF server will
4863	calculate a provisional value at runtime, but this is never	5115	calculate a provisional value at runtime, but this is never
4864	going to be an accurate measurement of <item power>.	5116	going to be an accurate measurement of <item power>.
4865	</attribute>	5117	</attribute>
…		…
4873	the curse is removed.	5125	the curse is removed.
4874	</attribute>	5126	</attribute>
4875	<attribute arch="lifesave" editor="save life" type="bool">	5127	<attribute arch="lifesave" editor="save life" type="bool">
4876	An item with this flag enabled will save the players life	5128	An item with this flag enabled will save the players life
4877	for one time: When the player is wearing this item and his	5129	for one time: When the player is wearing this item and his
4878	healthpoints reach zero, the item dissapears, replenishing	5130	health points reach zero, the item disappears, replenishing
4879	half of the player's health.	5131	half of the player's health.
4880		5132
4881	An item with <save life> should not have	5133	An item with <save life> should not have
4882	any decent additional bonuses!	5134	any decent additional bonuses!
4883	</attribute>	5135	</attribute>
4884	<attribute arch="unique" editor="unique item" type="bool">	5136	<attribute arch="unique" editor="unique item" type="bool">
4885	Unique items exist only one time on a server. If the item	5137	Unique items exist only one time on a server. If the item
…		…
5045	additional <grace regen.> bonus should be VERY RARE!!	5297	additional <grace regen.> bonus should be VERY RARE!!
5046	</attribute>	5298	</attribute>
5047	<attribute arch="food" editor="food bonus" type="int">	5299	<attribute arch="food" editor="food bonus" type="int">
5048	Positive <food bonus> slows down the player's digestion,	5300	Positive <food bonus> slows down the player's digestion,
5049	thus he consumes less food. Negative values speed it up.	5301	thus he consumes less food. Negative values speed it up.
5050		5302
5051	Note that food is consumed not only for "being alive", but	5303	Note that food is consumed not only for "being alive", but
5052	also for healing and mana-regeneration.	5304	also for healing and mana-regeneration.
5053	<food bonus> only affects the amount of food consumed	5305	<food bonus> only affects the amount of food consumed
5054	for "being alive". Hence, even with high <food bonus>,	5306	for "being alive". Hence, even with high <food bonus>,
5055	during a fight a player can run out of food quickly.	5307	during a fight a player can run out of food quickly.
5056	</attribute>	5308	</attribute>
5057	<attribute arch="xrays" editor="xray vision" type="bool">	5309	<attribute arch="xrays" editor="xray vision" type="bool">
5058	Xray vision allows the player to see through obstacles	5310	Xray vision allows the player to see through obstacles
5059	in a two-square-wide radius. This is extremely helpful and	5311	in a two-square-wide radius. This is extremely helpful and
5060	desireable, so don't give it away for cheap on equipment.	5312	desirable, so don't give it away for cheap on equipment.
5061	</attribute>	5313	</attribute>
5062	<attribute arch="stealth" editor="stealth" type="bool">	5314	<attribute arch="stealth" editor="stealth" type="bool">
5063	Stealth allows the player to move silently.	5315	Stealth allows the player to move silently.
5064	This comes to effect if a player turns himself	5316	This comes to effect if a player turns himself
5065	invisible and tries to sneak around monsters.	5317	invisible and tries to sneak around monsters.
…		…
5070	the ability to <reflect spells>, all kinds of	5322	the ability to <reflect spells>, all kinds of
5071	spell-bullets and -beams will bounce off him.	5323	spell-bullets and -beams will bounce off him.
5072	This works only about 90% of all times, to	5324	This works only about 90% of all times, to
5073	avoid players being completely immune to certain	5325	avoid players being completely immune to certain
5074	types of attacks.	5326	types of attacks.
5075		5327
5076	This is a very powerful ability and it	5328	This is a very powerful ability and it
5077	shouldn't be handed out cheap!	5329	shouldn't be handed out cheap!
5078	</attribute>	5330	</attribute>
5079	<attribute arch="reflect_missile" editor="reflect missiles" type="bool">	5331	<attribute arch="reflect_missile" editor="reflect missiles" type="bool">
5080	If a player is wearing any piece of equipment with	5332	If a player is wearing any piece of equipment with
…		…
5104	This text describes the weapons's "story". Every decent artifact weapon	5356	This text describes the weapons's "story". Every decent artifact weapon
5105	should have such a description.	5357	should have such a description.
5106	</attribute>	5358	</attribute>
5107	</type>	5359	</type>
5108		5360
5109	<!--####################################################################-->
5110	<type number="109" name="Wand & Staff">
5111	<description><![CDATA[
5112	Wands contain a certain spell. The player can apply (ready) and
5113	fire the wand. After a defined number of casts, the wand is
5114	"used up". It is possible to recharge a wand with scrolls of
5115	charging, but usually that isn't worth the cost. ]]>
5116	</description>
5117	<use><![CDATA[
5118	Wands are quite seldomly used. The reason prolly is that they're
5119	generally not cost-efficient. Handing out high-level wands with
5120	powerfull special spells isn't a good idea either, because of
5121	the recharge ability.
5122	<br><br>
5123	For low levels, staffs of healing/cure and word of recall are
5124	quite desireable though. Ideal rewards for low level quests. ]]>
5125	</use>
5126	<attribute arch="sp" editor="spell" type="spell">
5127	The <spell> specifies the contained spell.
5128	</attribute>
5129	<attribute arch="level" editor="casting level" type="int">
5130	The <casting level> of the wand determines it's power.
5131	An average level for wands in shops is about 10.
5132	</attribute>
5133	<attribute arch="food" editor="number of charges" type="int">
5134	The wand can be used <number of charges> times before it is
5135	used up. It can be recharged with scrolls of charging.
5136	</attribute>
5137	<attribute arch="startequip" editor="godgiven item" type="bool">
5138	A godgiven item vanishes as soon as the player
5139	drops it to the ground.
5140	</attribute>
5141	<attribute arch_begin="msg" arch_end="endmsg" editor="description" type="text">
5142	This text may contain a description of the wand.
5143	</attribute>
5144	</type>
5145
5146	</types>	5361	</types>

Diff Legend

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

Comparing deliantra/Deliantra/res/types.xml (file contents): Revision 1.1 by root, Tue Feb 21 21:37:01 2006 UTC vs. Revision 1.3 by root, Mon Mar 13 04:38:47 2006 UTC

Diff Legend

Comparing deliantra/Deliantra/res/types.xml (file contents):
Revision 1.1 by root, Tue Feb 21 21:37:01 2006 UTC vs.
Revision 1.3 by root, Mon Mar 13 04:38:47 2006 UTC