Difference between revisions of "Conditions and actions"

Revision as of 00:39, 2 November 2017

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 remaining entity according to the target selector.
	The any and all selectors are special cases where all remaining entities are selected instead.	For action targeting the any and all selectors can only be used for moving, fleeing, tagging and untagging.
4.	Check the condition on the selected entity. The invert checkbox only inverts this condition and not the result of the entire node.	Execute the action on the selected entity.
	Any selector: Check if the condition is valid for at least one of the remaining entities.	When moving or fleeing the any and all selectors result in moving to or fleeing from the weighted average position of all remaining entities. There is no difference between the any and all selector.
	All selector: Check if the condition is valid for all of the remaining entities.	When tagging or untagging the any and all selectors result in tagging or untagging all remaining entities. There is no difference between the any and all selector.

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

Example

Consider the following condition node:

1. Target type: Enemy
2. Target filters: Not carrying resource
3. Target selector: Closest to me
4. Condition: Shield is 0 to 25%

The following situation is evaluated like this:

1. There are 4 entities of target type enemy. Allies, resources and bases are discarded.
2. There are 3 entities not carrying a resource. The enemy moving to his base is removed from the list.
3. The distance between the Shotgun and the remaining 3 entities is measured. Only the closest enemy of them is selected.
4. 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.

Thoughts to include into this page

• Example: Invert only inverts the condition not the full node
• Target filters
  • OR and AND between filters
  • Connecting different filters bot class and target action
  • inverting a filter
  • Lists of Filters per Target Type
• Target selector
  • What a selector selects if there are several possibilities of equal value.
  • Lists of Selectors per Target Type
• Actions
  • Lists of Actions per Target Type
• Conditions
  • List of Conditions per Target Type (same as filters?)

• 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