Conditions and actions

This page needs improvement, you are welcome to contribute.

Basics

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.
	The any and all selectors are special cases where all remaining entities are selected in step 3.	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.

The rest of the page is a work in progress.

Thoughts to include into this page

Target - The type of Gladiabots Entity (Ally, Enemy, AllyBase, EnemyBase, Resource) to be checked Filters - Criteria that the target has to meet Condition - Action that the Target is executing Evaluation - Checking the [Invert] check box makes the Condition evaluate True if the filtered Target is not executing the action mentioned in the Condition.

• explanation of conditions and, similarly, actions
• action filters
• how robots are chosen when more than one robot respect the filters and the conditions in an action or a condition
• filter options within a category are in "or" between them, not "and"
• more info about filters introduced in alpha 7 and the OR /AND part
• more info about OR/AND between filter categories