Definition File Reference - Revision history

Rob at 02:00, 9 December 2008

2008-12-09T02:00:06Z

@@ Line 49: / Line 49: @@
 |{{flalt|Phase Element (Data)|phase}}
 |Zero or more "phase" elements may appear as defined by the given link. This element dictates the set of evaluation phases that will exist for the game system.
 |-
 |}

2008-12-09T01:58:19Z

← Older revision		Revision as of 01:58, 9 December 2008
Line 41:		Line 41:
	\|A single "behavior" element must appear as defined by the given link. This element details behavioral aspects for the game system and data files.		\|A single "behavior" element must appear as defined by the given link. This element details behavioral aspects for the game system and data files.
	\|-		\|-
	\|{{flalt\|ScriptMacro Element (Data)\|scriptmacro]]		\|{{flalt\|ScriptMacro Element (Data)\|scriptmacro}}
	\|Zero or more "scriptmacro" elements may appear as defined by the given link. This element defines macros for use within scripts.		\|Zero or more "scriptmacro" elements may appear as defined by the given link. This element defines macros for use within scripts.
	\|-		\|-

2008-12-09T01:57:58Z

@@ Line 40: / Line 40: @@
 |{{flalt|Behavior Element (Data)|behavior}}
 |A single "behavior" element must appear as defined by the given link. This element details behavioral aspects for the game system and data files.
 |-
 |{{flalt|Advancement Element (Data)|advancement}}
@@ Line 46: / Line 49: @@
 |{{flalt|Phase Element (Data)|phase}}
 |Zero or more "phase" elements may appear as defined by the given link. This element dictates the set of evaluation phases that will exist for the game system.
 |-
 |}

2008-12-04T05:13:49Z

Overview

← Older revision		Revision as of 05:13, 4 December 2008
Line 9:		Line 9:
	This section outlines the structure and mechanics for writing a definition file.		This section outlines the structure and mechanics for writing a definition file.

	{{important}}This section utilizes [[~~Conventions Used in~~ Reference ~~Section~~\|critical notational conventions]] that should be reviewed.		{{important}}This section utilizes [[Kit Reference#conventions\|critical notational conventions]] that should be reviewed.

	==Structural Composition==		==Structural Composition==

2008-12-01T00:50:35Z

Overview

← Older revision		Revision as of 00:50, 1 December 2008
Line 9:		Line 9:
	This section outlines the structure and mechanics for writing a definition file.		This section outlines the structure and mechanics for writing a definition file.

	{{important}}This section utilizes ~~critical notational conventions that can be found in~~ [[Conventions Used in Reference Section\|~~over here~~]].		{{important}}This section utilizes [[Conventions Used in Reference Section\|critical notational conventions]] that should be reviewed.

	==Structural Composition==		==Structural Composition==

2008-11-22T23:36:33Z

← Older revision	Revision as of 23:36, 22 November 2008
(No difference)

2008-11-22T22:22:08Z

Overview

← Older revision		Revision as of 22:22, 22 November 2008
Line 10:		Line 10:

	{{important}}This section utilizes critical notational conventions that can be found in [[Conventions Used in Reference Section\|over here]].		{{important}}This section utilizes critical notational conventions that can be found in [[Conventions Used in Reference Section\|over here]].

	{{important}}Just because you '''can''' put numerous different elements in the same file does not mean you '''should''' do so. Keeping your data files small and focused will also keep them much more manageable, so break up all the information across files where appropriate. See the Skeleton data files for examples of this.

	==Structural Composition==		==Structural Composition==

2008-11-22T22:21:42Z

Structural Composition

@@ Line 45: / Line 45: @@
 |{{flalt|Advancement Element (Data)|advancement}}
 |An optional "advancement" element may appear as defined by the given link. This element contains details regarding the advancement works within the data files.
 |-
 |{{flalt|Phase Element (Data)|phase}}
 |Zero or more "phase" elements may appear as defined by the given link. This element dictates the set of evaluation phases that will exist for the game system.
 |-
 |}

2008-11-22T22:20:25Z

Overview

← Older revision		Revision as of 22:20, 22 November 2008
Line 4:		Line 4:

	Each game system has a single definition file that describes the fundamental, non-changing characteristics of the game. HL uses the definition file to configure itself for each game system, reading in the definition file before any other files. All of the contents of the other data files are given meaningful interpretation by the contents of the definition file.		Each game system has a single definition file that describes the fundamental, non-changing characteristics of the game. HL uses the definition file to configure itself for each game system, reading in the definition file before any other files. All of the contents of the other data files are given meaningful interpretation by the contents of the definition file.

			The definition file must have the file extension ".def". By convention, the file is always named "definition.def" so that it can always be readily identified.

	This section outlines the structure and mechanics for writing a definition file.		This section outlines the structure and mechanics for writing a definition file.

2008-11-22T22:16:26Z

← Older revision		Revision as of 22:16, 22 November 2008
Line 8:		Line 8:

	{{important}}This section utilizes critical notational conventions that can be found in [[Conventions Used in Reference Section\|over here]].		{{important}}This section utilizes critical notational conventions that can be found in [[Conventions Used in Reference Section\|over here]].

			{{important}}Just because you '''can''' put numerous different elements in the same file does not mean you '''should''' do so. Keeping your data files small and focused will also keep them much more manageable, so break up all the information across files where appropriate. See the Skeleton data files for examples of this.

	==Structural Composition==		==Structural Composition==
Line 22:		Line 24:

	Within the document element, every definition file possesses the following child elements, appearing in the sequence given and with the names specified.		Within the document element, every definition file possesses the following child elements, appearing in the sequence given and with the names specified.

	{{important}}Just because you '''can''' put all of these different elements in the same file does not mean you '''should''' do so. Keeping your data files small and focused will also keep them much more manageable, so break up all the information across files where appropriate. See the Skeleton data files for examples of this.

	:{\| class="infotable"		:{\| class="infotable"