Phase Element (Data) - Revision history

Rob at 00:19, 24 November 2008

2008-11-24T00:19:38Z

← Older revision		Revision as of 00:19, 24 November 2008
Line 1:		Line 1:
	{{context\|Kit Reference\|Definition File Reference}}		{{context\|Kit Reference\|Definition File Reference}}

			==The "phase" Element==

	Each phase within the [[Evaluation Cycle Basics\|evaluation cycle]] must be individually specified and the sequence in which the phase elements are defined dictates the sequence in which phases are processed during evaluation. The XML element name is "phase" and the complete list of attributes is below.		Each phase within the [[Evaluation Cycle Basics\|evaluation cycle]] must be individually specified and the sequence in which the phase elements are defined dictates the sequence in which phases are processed during evaluation. The XML element name is "phase" and the complete list of attributes is below.

Rob at 00:17, 24 November 2008

2008-11-24T00:17:42Z

← Older revision		Revision as of 00:17, 24 November 2008
Line 1:		Line 1:
	{{context\|Kit Reference\|Definition File Reference}}		{{context\|Kit Reference\|Definition File Reference}}

	Each phase within the evaluation cycle must be individually specified and the sequence in which the phase elements are defined dictates the sequence in which phases are processed during evaluation. The XML element name is "phase" and the complete list of attributes is below.		Each phase within the [[Evaluation Cycle Basics\|evaluation cycle]] must be individually specified and the sequence in which the phase elements are defined dictates the sequence in which phases are processed during evaluation. The XML element name is "phase" and the complete list of attributes is below.

	:{\| class="infotable"		:{\| class="infotable"
Line 14:		Line 14:
	\|-		\|-
	\|interleave		\|interleave
	\|(Optional) Boolean – Indicates whether all tasks within this phase are either interleaved across masters and minions or processed hierarchically with masters always being evaluated before minions. This works the exact same way as the "interleave" attribute within the "behavior" element, except that it only applies to tasks within this specific phase. Default: "yes".		\|(Optional) Boolean – Indicates whether all tasks within this phase are either (a) interleaved across [[Minion and Master Relationships\|masters and minions]] or (b) processed hierarchically, with masters always being evaluated before minions. This works the exact same way as the "interleave" attribute within [[Behavior Element (Data)\|the "behavior" element]], except that it only applies to tasks within this specific phase. Default: "yes".
	{{important}}This attribute is only applicable when interleaving is '''enabled''' for the game system. It provides a means of forcing individual phases to be non-interleaved, which makes it possible to safely control dependencies of minions upon their masters for enablement conditions and the like. The default is "yes" so that all phases are interleaved by default if the game system behavior is designated as interleaved.		{{important}}This attribute is only applicable when interleaving is '''enabled''' for the game system. It provides a means of forcing individual phases to be non-interleaved, which makes it possible to safely control dependencies of minions upon their masters for enablement conditions and the like. The default is "yes" so that all phases are interleaved by default if the game system behavior is designated as interleaved.
	\|-		\|-

Rob: New page: {{context|Kit Reference|Definition File Reference}} Each phase within the evaluation cycle must be individually specified and the sequence in which the phase elements are defined dictates...

2008-11-23T10:04:50Z

New page: {{context|Kit Reference|Definition File Reference}} Each phase within the evaluation cycle must be individually specified and the sequence in which the phase elements are defined dictates...

New page

{{context|Kit Reference|Definition File Reference}}

Each phase within the evaluation cycle must be individually specified and the sequence in which the phase elements are defined dictates the sequence in which phases are processed during evaluation. The XML element name is "phase" and the complete list of attributes is below.

:{| class="infotable"
|class="leftnormal"|id
|Id – Specifies the unique id assigned to this phase. This id is used to reference the phase throughout the data files.
|-
|name
|Text – Common name for the phase is displayed in various situations. Maximum length is 25 characters.
|-
|description
|(Optional) Text – Textual description of the role the phase serves within the game system. Default: Empty.
|-
|interleave
|(Optional) Boolean – Indicates whether all tasks within this phase are either interleaved across masters and minions or processed hierarchically with masters always being evaluated before minions. This works the exact same way as the "interleave" attribute within the "behavior" element, except that it only applies to tasks within this specific phase. Default: "yes".
{{important}}This attribute is only applicable when interleaving is '''enabled''' for the game system. It provides a means of forcing individual phases to be non-interleaved, which makes it possible to safely control dependencies of minions upon their masters for enablement conditions and the like. The default is "yes" so that all phases are interleaved by default if the game system behavior is designated as interleaved.
|-
|}

==Example==

The following example demonstrates what a "phase" element might look like. All default values are assumed for omitted optional attributes.

<pre>
<phase
id="Initialize"
name="Initialization"
description="Anything that has to happen before everything else">
</phase>
</pre>