Conditions and actions

This page needs improvement, you are welcome to contribute.

Basics

A target can be shared between action and condition nodes.

The rest of the page is a work in progress.

Conditions and actions share almost the same evaluation process:

Conditions follow these steps:

1. get all the entities of the <target type>
2. only keep the entities matching the <target filters>
   • if no entity is returned by previous step, condition is considered invalid
3. select the best entity according to the <target selector> ("any" is a special case where you keep all the entities from previous step)
4. check the condition on the remaining entity(ies) (for "any" selector, node is valid if the condition is valid on at least one of the entities)

Actions follow these steps:

1. get all the entities of the <target type>
2. only keep the entities matching the <target filters>
   • if no entity is returned by previous step, action is considered invalid
3. select the best entity according to the <target selector> ("any" is not allowed for action targeting)
4. if action is possible, execute it

Filters are actually applied before checking the condition.

Thoughts to include into this page

Conditions are in syntax Target(Filters)-Condition(Evaluation)

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.

• Filters and Conditions
• explanation of conditions and, similarly, actions
• action filters
• any and all
• 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