Behavior element behavior adding parameter table support for actors.

Adds ParameterTable instance. This allows to store parameter with primitive or persistable type for game elements or global game state. Parameter tables are sometimes called “Black boards”. Various game scripts can set values in a table while other game scripts can read the values from the table without the individual systems knowing each other. For performance reasons the entries in the table are queried and can be stored locally to avoid looking them up all the time. In addition to primitive values parameters support objects implementing the Persistable interface. This allows parameter tables to be stored in save states easily. Parameter values are cleared by setting them to \em null. This avoids the need to remove parameters from the table.

The parameter table is a pure storage facility. No notifications about changes to parameter values is done in any way. If you need tracking state changes use TSTriggerTable or the EventTracker.

This behavior can be used only once on an element.

Element class properties have the prefix parameterTable. .

This behavior has no events.

This behavior adds these behavior tree actions if behavior tree is present. If behavior has non-empty identifier replace parameterTree with parameterTree(id).

Set one or more parameter tree parameters.

This is an example of using this action:

<action name='parameterTree.set'>
  <parameter name='name'>counter</parameter>
  <parameter name='value.increment'>1</parameter>
</action>

Check one or more parameter tree parameters. Action succeeds if all parameter value matches their respective parameter tree parameter otherwise action fails. This action is typically used as first action in a sequence to run the sequence only if a parameter tree parameter matches (or not).

This is an example of using this action:

<sequence>
  <action name='parameterTree.check'>
    <parameter name='name'>counter</parameter>
    <parameter name='value.less'>3</parameter>
  </action>
  <!-- actions here run only if parameter tree parameter value is less than 3 -->
</sequence>

This behavior adds these behavior tree conditions if behavior tree is present. If behavior has non-empty identifier replace parameterTree with parameterTree(id).

Check one or more parameter tree parameters. Conditions returns true if all parameter value match their respective parameter tree parameter. This condition is typically used to run an action or sequence of actions as long as parameter tree conditions are true.

This is an example of using this condition:

<action name='myAction' id='doing something'>
  <parameter name='parameterTree.name'>counter</parameter>
  <parameter name='parameterTree.value.less'>3</parameter>
</action>

This behavior requires no other behaviors.

• ECBehaviorBehaviorTree: Add actions and conditions for behavior trees to use.

This behavior does support element class to be persistable (setPersistable).

ECBehaviorParameterTable.

Since DragonScript Module Version 1.0

• Store parameters of persistable data types for elements.

This example defines an element which support parameter table.

class MyElement extends BehaviorElementClass
  public var ECBehaviorParameterTable parameterTrable
  func new()
    parameterTable = ECBehaviorParameterTable.new(this)
  end
end

Using element class supporting adding behaviors the behavior can be added like this:

<?xml version='1.0' encoding='UTF-8'?>
<elementClass name='MyClass' class='GenericBehaviorElement'>
  <behavior type='ECBehaviorParameterTable'>
    <!-- set element properties. omit property prefix if used inside behavior tag -->
    <string name='.name'>value</string>
  </behavior>
 
  <!-- for adding multiple behaviors use unique identifiers -->
  <behavior type='ECBehaviorParameterTable' id='second'/>
</elementClass>

• DEExamples Repository