Changes between Initial Version and Version 1 of XML.Entity.Actions.Formation

Timestamp:

Feb 23, 2008, 4:18:59 AM (16 years ago)

Author:

trac

Comment:

--

XML.Entity.Actions.Formation

@@ +1 @@
+Formations have an importance in the game for performing realistic and strategic tactics.  Can you stick a female worker in a testudo formation or do the priests take the front position in the formation?  I think not!  That is why we need to specify what is allowed and in what position for each entity.
+
+'''Example:'''
+
+{{{
+        <Actions>
+                <Formation>
+                        <Category>Melee</Category>
+                        <Type>Box, Column_C, Line_C, Column_O, Line_O, Flank</Type>
+                </Formation>
+       </Actions>
+}}}
+
+----
+
+= Category =
+''BRIEF DESCRIPTION ::'' The entity will occupy this position when in formation.
+
+Each entity that can enter a formation is assigned a category. The entity's category defines what position it takes in the formation.  These are the categories available:
+
+ * ''protected'' - takes the safest position in the formation (usually in the back or middle).
+ * ''melee'' - takes the position to shield the protected/ranged entities from attack.  Usually melee type units.
+ * ''ranged'' - takes the position that is most optimal for using a ranged weapon.
+ * ''lead'' - takes the position of leadership.  There is only one (if any) of these positions in each formation type.
+
+= Type =
+''BRIEF DESCRIPTION ::'' List of formations that the entity is allowed to perform.
+
+This defines what formations the entity may use.  If this is not defined, then the unit may not enter a formation.
+
+The formation types are:
+
+ * box
+ * column_c
+ * line_c
+ * column_o
+ * line_o
+ * flank
+ * skirmish
+ * wedge
+ * testudo
+ * phalanx
+
+For more information abou these formations, see the '''Formations''' document.