Empires BattleBoard - Revision history

Andrewg: Andrewg moved page BattleBoard to Empires BattleBoard

2019-07-08T20:09:57Z

Andrewg moved page BattleBoard to Empires BattleBoard

← Older revision	Revision as of 20:09, 8 July 2019
(No difference)

Andrewg at 22:23, 7 September 2017

2017-09-07T22:23:52Z

← Older revision		Revision as of 22:23, 7 September 2017
Line 33:		Line 33:

	See BATTLESCRIPT.TXT for descriptions of commands to set up a BattleBoard UI, add units, play animations, move units, and display text with the units. Relevant commands start with "Battle3D".		See BATTLESCRIPT.TXT for descriptions of commands to set up a BattleBoard UI, add units, play animations, move units, and display text with the units. Relevant commands start with "Battle3D".

			== Squads ==

			Battle3DAddUnit takes a squadType, which is the name of a row in SQUADS.CSV which indicates the asset name, squad size, scale, and other display parameters for the 3D model. This table is also used for displaying groups on the map, although they are always shown as a single unit on the map.

			Placement of squad members is controlled by FORMATIONS.TXT, there is a chunk for each squad size indicating the placement of the member (x and y coordinates, -1 to 1) in the battle grid.

Andrewg at 19:53, 1 September 2017

2017-09-01T19:53:25Z

@@ Line 15: / Line 15: @@
 CENTERGAP 12
 ASSETSCALE 7
-EVENTFRAMES 60
+GRIDEMPTY BattleGrid.tga
-EVENTATTACKFRAME 10
+GRIDUNIT BattleGrid.tga
-EVENTDAMAGEFRAME 18
+GRIDTARGET BattleGridTarget.tga
-HITSTEXTCOLOUR $COL_RED
+GRIDATTACKER BattleGridAttack.tga
-EFFECTEXTCOLOUR $COL_YELLOW
+FILE UI_BATTLE/Battlefield_Default.dds
-TEXTSTEP 2.5
+</nowiki>
 * MINLINES is the minimum number of battle lines per side to show on the battle board regardless of the number of units present (the view will zoom out to show additional lines if required)
@@ Line 28: / Line 27: @@
 * CENTERGAP is an additional space between the front lines of opposing armies
 * ASSETSCALE is a scale factor for the units (the scale used the AssetScale from UNITS.CSV in thousandths, divided by this value)
-* EVENTFRAMES is the number of logical frames (1/30 s) used to display each battle event
+* GRIDEMPTY, GRIDUNIT, GRIDTARGET, and GRIDATTACKER are textures displayed over the ground to highlight empty grids, inactive units, targetted units, and attacking units respectively
 * FILE is the default terrain texture to use (if not specified by script)
 == Scripting ==
-To display a battle in a battle board UI, you must create and populate an event record in script:
+See BATTLESCRIPT.TXT for descriptions of commands to set up a BattleBoard UI, add units, play animations, move units, and display text with the units.  Relevant commands start with "Battle3D".

Andrewg at 17:12, 13 June 2017

2017-06-13T17:12:00Z

← Older revision		Revision as of 17:12, 13 June 2017
Line 83:		Line 83:
	0: Paused		0: Paused

	1: Playing		1: Playing Single Step

			2: Playing

	1000: Complete		1000: Complete

Andrewg at 23:57, 4 April 2017

2017-04-04T23:57:04Z

← Older revision		Revision as of 23:57, 4 April 2017
Line 10:		Line 10:
	DX 0		DX 0
	DY 0		DY 0
	~~COLOUR 0f200f~~
	MINLINES 3		MINLINES 3
	MINLINELENGTH 4		MINLINELENGTH 4
Line 24:		Line 23:
	FONT LARGEFONT</nowiki>		FONT LARGEFONT</nowiki>

	* COLOUR controls the background colour, use 0 for transparent
	* MINLINES is the minimum number of battle lines per side to show on the battle board regardless of the number of units present (the view will zoom out to show additional lines if required)		* MINLINES is the minimum number of battle lines per side to show on the battle board regardless of the number of units present (the view will zoom out to show additional lines if required)
	* MINLINELENGTH is the minimum number of slots per wing to show on the battle board regardless of the number of units present (the view will zoom out to show additional lines if required)		* MINLINELENGTH is the minimum number of slots per wing to show on the battle board regardless of the number of units present (the view will zoom out to show additional lines if required)
Line 36:		Line 34:
	* EFFECTEXTCOLOUR is the colour used for effec damage text		* EFFECTEXTCOLOUR is the colour used for effec damage text
	* FONT is the font used for pop up text		* FONT is the font used for pop up text
			* FILE is the default terrain texture to use (if not specified by script)
			* LOGBOX is the name of an existing listbox to output combat log to

	== Scripting ==		== Scripting ==

	To display a battle in a battle board UI, you must create and populate an event record in script:		To display a battle in a battle board UI, you must create and populate an event record in script:
	# Call CreateBattleRecord() to uniquely store events for this battle. A record handle will be returned which you will use to populate and destroy this record. The record will persist until it is destroyed with DestroyBattleRecord(recordHandle) and is included in saved games.		# Call CreateBattleRecord(factionID0a, factionID0b, factionID1a, factionID1b) to uniquely store events for this battle. A record handle will be returned which you will use to populate and destroy this record. The record will persist until it is destroyed with DestroyBattleRecord(recordHandle) and is included in saved games. Up to two faction IDs can be given for each side in the battle used when displaying faction names on the battle board.
	# Create a status event for every unit that is involved in the battle using AddBattleStatus(recordHandle, unitID, side, wing, line, distance, unitTemplateName, unitNameID, unitNumeral, hitsBefore, effecBefore~~, [advancedInfo]~~). recordHandle is the handle of a record created with CreateBattleRecord. unitID is a unique identifier for the unit (although it does not need to be the id of a valid unit object). side [0,1], wing[0,1], line[0,2], and distance [0,16] indicate where the unit is placed on the battle board. unitAlias is the name of a unit template used for visual properties of the unit (including Asset and AssetScale). unitNameID is the string ID of the base unit name and unitNumeral is a numeric ID to prepend to the name (negative values will be interpreted as Roman numerals). hitsBefore and effecBefore are the initial status of the unit~~. advancedInfo is an array of 32 integers used in the BATTLE_STATUS callback~~.		# Create a status event for every unit that is involved in the battle using AddBattleStatus(recordHandle, unitID, side, wing, line, distance, unitTemplateName, unitNameID, unitNumeral, hitsBefore, effecBefore). recordHandle is the handle of a record created with CreateBattleRecord. unitID is a unique identifier for the unit (although it does not need to be the id of a valid unit object). side [0,1], wing[0,1], line[0,2], and distance [0,16] indicate where the unit is placed on the battle board. unitAlias is the name of a unit template used for visual properties of the unit (including Asset and AssetScale). unitNameID is the string ID of the base unit name and unitNumeral is a numeric ID to prepend to the name (negative values will be interpreted as Roman numerals). hitsBefore and effecBefore are the initial status of the unit.
	# For any unit that has been set up using AddBattleStatus, you can optionally call UpdateBattleStatus(recordHandle, unitID, hitsAfter, effecAfter) to indicate the final status of the unit.		# For any unit that has been set up using AddBattleStatus, you can optionally call UpdateBattleStatus(recordHandle, unitID, hitsAfter, effecAfter) to indicate the final status of the unit.
	# For every event in the battle, call ~~AddBattleStatus~~(recordHandle, type~~, roll~~) to create the event, it will return an eventNum referenced below. ~~Unless otherwise noted, battle~~ events ~~should~~ be ~~created~~ in the order they are ~~to be displayed~~. ~~type provides instructions for how~~ the ~~event is displayed (see below). roll indicates~~ the ~~roll (or roll difference) associated with the event~~. No events are required to, for example, just show a preview of a battlefield.		# For any unit that has been set up using AddBattleStatus, you can optionally call SetBattleTooltipInfo(recordHandle, unitID, advancedInfo) to provide info for the detailed tooltip and combat log. advancedInfo is an array of 32 integers used in the BATTLE_STATUS callback.
	# For each participant in an event (actor, defender, support, etc.), call AddBattleEventParticipant(recordHandle, eventNum, unitID, hitsDelta, effecDelta, actionType, [advancedInfo]). recordHandle and eventNum returned by CreateBattleRecord and AddBattleEvent respectively. unitID is the id of a unit set up with AddBattleStatus. hitsDelta and effecDelta are the status to show on this unit. actionType ~~provided~~ instructions for hew the event is displayed (see below). advancedInfo is an array of 32 integers used in the BATTLE_MESSAGE callback.		# For every event in the battle, call AddBattleEvent(recordHandle, type) to create the event, it will return an eventNum referenced below. Battle events of type 0 will be played back sequentially in the order they are created. Type 1 events are deferred until the end of the battle and then played simultaneously. No events are required to, for example, just show a preview of a battlefield.
			# For each participant in an event (actor, defender, support, etc.), call AddBattleEventParticipant(recordHandle, eventNum, unitID, hitsDelta, effecDelta, movementType, actionType, turnToFace, [initString], [actionString], [advancedInfo]). recordHandle and eventNum returned by CreateBattleRecord and AddBattleEvent respectively. unitID is the id of a unit set up with AddBattleStatus. hitsDelta and effecDelta are the status to show on this unit. movementType, actionType, and turnToFace provide instructions for hew the event is displayed (see below). initString is the string ID of a static message to display over the unit at the start of the event. actionString is a static message to display at the climax of the event. advancedInfo is an array of 32 integers used in the BATTLE_MESSAGE callback to display advanced combat details.
	# When the UI is about to be activated (for example, in the UI_OBJ_ACTIVATE callback of its parent), set the user data on the UI object to the handle of the record to display. For example:		# When the UI is about to be activated (for example, in the UI_OBJ_ACTIVATE callback of its parent), set the user data on the UI object to the handle of the record to display. For example:
	<nowiki>FUNCTION UI_OBJ_ACTIVATE(id)		<nowiki>FUNCTION UI_OBJ_ACTIVATE(id)
Line 87:		Line 88:

	=== Event Types ===		=== Event Types ===
	~~10. Duel~~

	20. ~~Flanking - attackers will turn to face defenders~~		0. Standard

	30. Retreat / Pursuit - events of this type are delayed until the end of the battle playback and played simultaneously		1. Retreat / Pursuit - events of this type are delayed until the end of the battle playback and played simultaneously

	~~More to come?~~		=== Event Participant Parameters ===
			==== Movement Types ====

	~~=== Action Types ===~~		Describes the type of movement an event participant takes at the beginning of the event. Setting the turn to face parameter to 1 will cause the unit to turn toward its target while moving.
	0. ~~Passive defense~~

	1. ~~Standard attack~~ - ~~charge~~ forward ~~and~~ play ~~melee attack~~ animation		0. Stationary - don't more forward, continue to play idle animation

	2. ~~Support attack~~ - ~~advance slightly and play ranged attack~~ animation		1. Charge - move a large distance forward playing the charge animation

	~~More~~ to ~~come?~~		2. Advance - move a small distance forward playing the move animation

			==== Action Types ====

			Describes the type of action an event participant shows after the movement phase

			0. Passive - continue to play idle animation

			1. Melee - play melee animation

			2. Ranged Attack - play fire animation

Andrewg: /* Scripting */

2017-03-27T23:48:13Z

Scripting

← Older revision		Revision as of 23:48, 27 March 2017
Line 40:		Line 40:

	To display a battle in a battle board UI, you must create and populate an event record in script:		To display a battle in a battle board UI, you must create and populate an event record in script:
	# Call ~~CreateEventRecord~~() to uniquely store events for this battle. A record handle will be returned which you will use to populate and destroy this record. The record will persist until it is destroyed with ~~DestroyEventRecord~~(recordHandle) and is included in saved games.		# Call CreateBattleRecord() to uniquely store events for this battle. A record handle will be returned which you will use to populate and destroy this record. The record will persist until it is destroyed with DestroyBattleRecord(recordHandle) and is included in saved games.
	# Create a status event for every unit that is involved in the battle using ~~AddStatusEvent~~(recordHandle, unitID, side, wing, line, distance, ~~unitAlias~~, ~~unitNameIndex~~, hitsBefore, effecBefore). recordHandle is the handle of a record created with ~~CreateEventRecord~~. unitID is a unique identifier for the unit (although it does not need to be the id of a valid unit object). side [0,1], wing[0,1], line[0,2], and distance [0,16] indicate where the unit is placed on the battle board. unitAlias is the name of a unit template used for visual properties of the unit (including Asset and AssetScale). ~~unitNameIndex~~ is the ~~index~~ of a ~~UI string containing~~ the ~~display~~ name ~~of this unit~~. hitsBefore and effecBefore are the initial status of the unit.		# Create a status event for every unit that is involved in the battle using AddBattleStatus(recordHandle, unitID, side, wing, line, distance, unitTemplateName, unitNameID, unitNumeral, hitsBefore, effecBefore, [advancedInfo]). recordHandle is the handle of a record created with CreateBattleRecord. unitID is a unique identifier for the unit (although it does not need to be the id of a valid unit object). side [0,1], wing[0,1], line[0,2], and distance [0,16] indicate where the unit is placed on the battle board. unitAlias is the name of a unit template used for visual properties of the unit (including Asset and AssetScale). unitNameID is the string ID of the base unit name and unitNumeral is a numeric ID to prepend to the name (negative values will be interpreted as Roman numerals). hitsBefore and effecBefore are the initial status of the unit. advancedInfo is an array of 32 integers used in the BATTLE_STATUS callback.
	# For any unit that has been set up using ~~AddStatusEvent~~, you can optionally call ~~UpdateStatusEvent~~(recordHandle, unitID, hitsAfter, effecAfter) to indicate the final status of the unit.		# For any unit that has been set up using AddBattleStatus, you can optionally call UpdateBattleStatus(recordHandle, unitID, hitsAfter, effecAfter) to indicate the final status of the unit.
	# For every event in the battle, call ~~AddBattleEvent~~(recordHandle, type, roll) to create the event, it will return an eventNum referenced below. Unless otherwise noted, battle events should be created in the order they are to be displayed. type provides instructions for how the event is displayed (see below). roll indicates the roll (or roll difference) associated with the event. No events are required to, for example, just show a preview of a battlefield.		# For every event in the battle, call AddBattleStatus(recordHandle, type, roll) to create the event, it will return an eventNum referenced below. Unless otherwise noted, battle events should be created in the order they are to be displayed. type provides instructions for how the event is displayed (see below). roll indicates the roll (or roll difference) associated with the event. No events are required to, for example, just show a preview of a battlefield.
	# For each participant in an event (actor, defender, support, etc.), call AddBattleEventParticipant(recordHandle, eventNum, unitID, hitsDelta, effecDelta, actionType). recordHandle and eventNum returned by ~~CreateEventRecord~~ and AddBattleEvent respectively. unitID is the id of a unit set up with ~~AddStatusEvent~~. hitsDelta and effecDelta are the status to show on this unit. actionType provided instructions for hew the event is displayed (see below).		# For each participant in an event (actor, defender, support, etc.), call AddBattleEventParticipant(recordHandle, eventNum, unitID, hitsDelta, effecDelta, actionType, [advancedInfo]). recordHandle and eventNum returned by CreateBattleRecord and AddBattleEvent respectively. unitID is the id of a unit set up with AddBattleStatus. hitsDelta and effecDelta are the status to show on this unit. actionType provided instructions for hew the event is displayed (see below). advancedInfo is an array of 32 integers used in the BATTLE_MESSAGE callback.
	# When the UI is about to be activated (for example, in the UI_OBJ_ACTIVATE callback of its parent), set the user data on the UI object to the handle of the record to display. For example:		# When the UI is about to be activated (for example, in the UI_OBJ_ACTIVATE callback of its parent), set the user data on the UI object to the handle of the record to display. For example:
	<nowiki>FUNCTION UI_OBJ_ACTIVATE(id)		<nowiki>FUNCTION UI_OBJ_ACTIVATE(id)
Line 50:		Line 50:
	SetUIObjectUserData("BattleSummary3D", gBattleDesc.recordHandle);		SetUIObjectUserData("BattleSummary3D", gBattleDesc.recordHandle);
	}</nowiki>		}</nowiki>

			Feedback callbacks (on the UI containing the battle board):

			BATTLE_MESSAGE(int event, int action, int side, int wing, int line, int slot)
			* Incoming info is stored in work array 0
			* String is set in ui string 0, return 1 if there is something to show

			FUNCTION BATTLE_STATUS(int event, int action, int side, int wing, int line, int slot)
			* Incoming info is stored in work array 0
			* String is set in ui string 0, return 1 if there is something to show

	Playback can be controlled by calling BattleBoardControl(objectName, command). The following commands are available:		Playback can be controlled by calling BattleBoardControl(objectName, command). The following commands are available:

Andrewg at 23:53, 22 March 2017

2017-03-22T23:53:53Z

@@ Line 51: / Line 51: @@
 }</nowiki>
-When the battle playback is complete, the battleboard UI object will set a value[0] of >= 1000 (ex. check GetUIObjectValue("BattleSummary3D", 0) >= 1000).
+Playback can be controlled by calling BattleBoardControl(objectName, command).  The following commands are available:
 === Event Types ===

Andrewg: /* Scripting */

2017-03-15T00:06:48Z

Scripting

← Older revision		Revision as of 00:06, 15 March 2017
Line 50:		Line 50:
	SetUIObjectUserData("BattleSummary3D", gBattleDesc.recordHandle);		SetUIObjectUserData("BattleSummary3D", gBattleDesc.recordHandle);
	}</nowiki>		}</nowiki>

			When the battle playback is complete, the battleboard UI object will set a value[0] of >= 1000 (ex. check GetUIObjectValue("BattleSummary3D", 0) >= 1000).

	=== Event Types ===		=== Event Types ===

Andrewg at 00:19, 21 August 2016

2016-08-21T00:19:43Z

← Older revision		Revision as of 00:19, 21 August 2016
Line 1:		Line 1:
	== UI ==		== UI ==

	There is a custom 3d UI object for displaying ~~an animated~~ battle board. It can be added to a UI by adding a "CUSTOM" type object to a UI with the additional tag "BATTLEBOARD" and a number of optional parameters to control formatting and behaviour. For example:		There is a custom 3d UI object for displaying a battle board which . It can be added to a UI by adding a "CUSTOM" type object to a UI with the additional tag "BATTLEBOARD" and a number of optional parameters to control formatting and behaviour. For example:

	<nowiki>[BattleSummary3D]		<nowiki>[BattleSummary3D]
Line 43:		Line 43:
	# Create a status event for every unit that is involved in the battle using AddStatusEvent(recordHandle, unitID, side, wing, line, distance, unitAlias, unitNameIndex, hitsBefore, effecBefore). recordHandle is the handle of a record created with CreateEventRecord. unitID is a unique identifier for the unit (although it does not need to be the id of a valid unit object). side [0,1], wing[0,1], line[0,2], and distance [0,16] indicate where the unit is placed on the battle board. unitAlias is the name of a unit template used for visual properties of the unit (including Asset and AssetScale). unitNameIndex is the index of a UI string containing the display name of this unit. hitsBefore and effecBefore are the initial status of the unit.		# Create a status event for every unit that is involved in the battle using AddStatusEvent(recordHandle, unitID, side, wing, line, distance, unitAlias, unitNameIndex, hitsBefore, effecBefore). recordHandle is the handle of a record created with CreateEventRecord. unitID is a unique identifier for the unit (although it does not need to be the id of a valid unit object). side [0,1], wing[0,1], line[0,2], and distance [0,16] indicate where the unit is placed on the battle board. unitAlias is the name of a unit template used for visual properties of the unit (including Asset and AssetScale). unitNameIndex is the index of a UI string containing the display name of this unit. hitsBefore and effecBefore are the initial status of the unit.
	# For any unit that has been set up using AddStatusEvent, you can optionally call UpdateStatusEvent(recordHandle, unitID, hitsAfter, effecAfter) to indicate the final status of the unit.		# For any unit that has been set up using AddStatusEvent, you can optionally call UpdateStatusEvent(recordHandle, unitID, hitsAfter, effecAfter) to indicate the final status of the unit.
	# For every event in the battle, call AddBattleEvent(recordHandle, type, roll) to create the event, it will return an eventNum referenced below. Unless otherwise noted, battle events should be created in the order they are to be displayed. type provides instructions for how the event is displayed (see below). roll indicates the roll (or roll difference) associated with the event.		# For every event in the battle, call AddBattleEvent(recordHandle, type, roll) to create the event, it will return an eventNum referenced below. Unless otherwise noted, battle events should be created in the order they are to be displayed. type provides instructions for how the event is displayed (see below). roll indicates the roll (or roll difference) associated with the event. No events are required to, for example, just show a preview of a battlefield.
	# For each participant in an event (actor, defender, support, etc.), call AddBattleEventParticipant(recordHandle, eventNum, unitID, hitsDelta, effecDelta, actionType). recordHandle and eventNum returned by CreateEventRecord and AddBattleEvent respectively. unitID is the id of a unit set up with AddStatusEvent. hitsDelta and effecDelta are the status to show on this unit. actionType provided instructions for hew the event is displayed (see below).		# For each participant in an event (actor, defender, support, etc.), call AddBattleEventParticipant(recordHandle, eventNum, unitID, hitsDelta, effecDelta, actionType). recordHandle and eventNum returned by CreateEventRecord and AddBattleEvent respectively. unitID is the id of a unit set up with AddStatusEvent. hitsDelta and effecDelta are the status to show on this unit. actionType provided instructions for hew the event is displayed (see below).
	# When the UI is about to be activated (for example, in the UI_OBJ_ACTIVATE callback of its parent), set the user data on the UI object to the handle of the record to display. For example:		# When the UI is about to be activated (for example, in the UI_OBJ_ACTIVATE callback of its parent), set the user data on the UI object to the handle of the record to display. For example:
Line 54:		Line 54:
	10. Duel		10. Duel

	20. Flanking		20. Flanking - attackers will turn to face defenders

	30. Retreat ~~Attack~~ - events of this ~~time~~ are delayed until the end of the battle playback and played simultaneously		30. Retreat / Pursuit - events of this type are delayed until the end of the battle playback and played simultaneously

			More to come?

	=== Action Types ===		=== Action Types ===
	0. ~~No action - useful for applying damage to a passive unit~~		0. Passive defense

	1. Standard attack - charge forward and play melee attack animation		1. Standard attack - charge forward and play melee attack animation

	2. Support attack - advance slightly and play ranged attack animation		2. Support attack - advance slightly and play ranged attack animation

			More to come?

Andrewg at 23:10, 20 August 2016

2016-08-20T23:10:03Z

← Older revision		Revision as of 23:10, 20 August 2016
Line 38:		Line 38:

	== Scripting ==		== Scripting ==

			To display a battle in a battle board UI, you must create and populate an event record in script:
			# Call CreateEventRecord() to uniquely store events for this battle. A record handle will be returned which you will use to populate and destroy this record. The record will persist until it is destroyed with DestroyEventRecord(recordHandle) and is included in saved games.
			# Create a status event for every unit that is involved in the battle using AddStatusEvent(recordHandle, unitID, side, wing, line, distance, unitAlias, unitNameIndex, hitsBefore, effecBefore). recordHandle is the handle of a record created with CreateEventRecord. unitID is a unique identifier for the unit (although it does not need to be the id of a valid unit object). side [0,1], wing[0,1], line[0,2], and distance [0,16] indicate where the unit is placed on the battle board. unitAlias is the name of a unit template used for visual properties of the unit (including Asset and AssetScale). unitNameIndex is the index of a UI string containing the display name of this unit. hitsBefore and effecBefore are the initial status of the unit.
			# For any unit that has been set up using AddStatusEvent, you can optionally call UpdateStatusEvent(recordHandle, unitID, hitsAfter, effecAfter) to indicate the final status of the unit.
			# For every event in the battle, call AddBattleEvent(recordHandle, type, roll) to create the event, it will return an eventNum referenced below. Unless otherwise noted, battle events should be created in the order they are to be displayed. type provides instructions for how the event is displayed (see below). roll indicates the roll (or roll difference) associated with the event.
			# For each participant in an event (actor, defender, support, etc.), call AddBattleEventParticipant(recordHandle, eventNum, unitID, hitsDelta, effecDelta, actionType). recordHandle and eventNum returned by CreateEventRecord and AddBattleEvent respectively. unitID is the id of a unit set up with AddStatusEvent. hitsDelta and effecDelta are the status to show on this unit. actionType provided instructions for hew the event is displayed (see below).
			# When the UI is about to be activated (for example, in the UI_OBJ_ACTIVATE callback of its parent), set the user data on the UI object to the handle of the record to display. For example:
			<nowiki>FUNCTION UI_OBJ_ACTIVATE(id)
			{
			SetUIObjectUserData("BattleSummary3D", gBattleDesc.recordHandle);
			}</nowiki>

			=== Event Types ===
			10. Duel

			20. Flanking

			30. Retreat Attack - events of this time are delayed until the end of the battle playback and played simultaneously

			=== Action Types ===
			0. No action - useful for applying damage to a passive unit

			1. Standard attack - charge forward and play melee attack animation

			2. Support attack - advance slightly and play ranged attack animation