Difference between revisions of "Conditions and actions"

Revision as of 11:45, 28 October 2017

This page needs improvement, you are welcome to contribute.

A target can be shared between action and condition nodes.

Both condition nodes and action nodes are mainly defined by a target and share almost the same evaluation process:

Step	Condition node	Action node
1.	Get all the entities of the `target type`.
2.	Remove all entities not matching the `target filters`. If there is not a single entity left the node is considered invalid.
3.	Select the best entity according to the `target selector`.
3.	The `any` and `all` selectors are special cases where all remaining entities are selected instead.	The `any` and `all` selectors are not allowed for action targeting.
4.	Check the condition on the remaining entity.	Execute the action upon the remaining entity.
	`Any` selector: Check if the condition is valid for at least one of the entities.
	`All` selector: Check if the condition is valid for all of the entities.

Condition nodes: Checking the condition is the very last step after filtering and selecting took place.

Consider the following condition node:

The following situation is evaluated like this:

There are 4 entities of target type enemy. Allies, resources and bases are discarded.
There are 3 entities not carrying a resource. The enemy moving to his base is removed from the list.
The distance between the Shotgun and the entities is measured. Only the closest enemy is selected.
The condition is only checked for the remaining entity. As this enemy has full shield, the condition is evaluated invalid.

The condition node is evaluated invalid in this situation.

The rest of the page is a work in progress.

@@ Line 30: / Line 30: @@
 |}
-{{Information|Condition nodes: '''Checking the condition is the very last step''' after filtering and selecting took place.}}
+{{Information|Condition nodes: Checking the condition is the very last step after filtering and selecting took place.}}
+=== Example ===
+Consider the following condition node:
+# Target type: Enemy
+# Target filters: Not carrying resource
+# Target selector: Closest to me
+# Condition: Shield is 0 to 25%
+The following situation is evaluated like this:
+# There are 4 entities of target type enemy. Allies, resources and bases are discarded.
+# There are 3 entities not carrying a resource. The enemy moving to his base is removed from the list.
+# The distance between the Shotgun and the entities is measured. Only the closest enemy is selected.
+# The condition is only checked for the remaining entity. As this enemy has full shield, the condition is evaluated invalid.
+[[File:Condition.png|thumb|none|800px|The condition node is evaluated invalid in this situation.]]
 {{Warning|The rest of the page is a work in progress.}}
@@ Line 46: / Line 64: @@
 What a selector selects if there are several possibilities of equal value.
-Visual example of 5 bots, 2 get filtered, one is selected, the condition is false, although another bot fits this condition.
 OR and AND between filters
 Lists of Actions per Target Type