You can use these validators to make sure an effect only happens when there is a specified number of a specified unit in the area.
Count - The number off of which to base the search
Compare - The circumstance in which the validator should pass
You can also add another validator into the search itself, a "unit type" validator usually being particularly useful.
Example -
I only want my guy to fire a fireball if there are 3 or more enemy penguins within the impact radius. This requires an enumerate area validator.
1) Input radius of 1.5 (the impact radius of the fireball)
2) Areas - Validator - Is Penguin (unit type validator)
2) Set count - 3
3) Search filters - exclude player, neutral, ally
4) Compare - Greater Than Or Equal To
Attach it to my guy's fireball search effect in which he searches for a target, and he will only fire if there are 3 or more enemy penguins at the target location.
How do you actually use these validators? How does the 'Count' field play into things?
You can use these validators to make sure an effect only happens when there is a specified number of a specified unit in the area.
Count - The number off of which to base the search
Compare - The circumstance in which the validator should pass
You can also add another validator into the search itself, a "unit type" validator usually being particularly useful.
Example -
I only want my guy to fire a fireball if there are 3 or more enemy penguins within the impact radius. This requires an enumerate area validator.
1) Input radius of 1.5 (the impact radius of the fireball)
2) Areas - Validator - Is Penguin (unit type validator)
2) Set count - 3
3) Search filters - exclude player, neutral, ally
4) Compare - Greater Than Or Equal To
Attach it to my guy's fireball search effect in which he searches for a target, and he will only fire if there are 3 or more enemy penguins at the target location.