Difference between revisions of "Validators"

From HIVE
Jump to navigation Jump to search
m (Added categories)
m
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
Validators are [[catalog]] objects, representing boolean functions (they validate whether given conditions apply or not). They are used by other catalog objects, such as abilities (for auto-cast validation), behaviors (to decide whether the behavior works or not) or effects. Each validator entry is one condition, that can be tested by incuding this validator in appropriate field.
 
Validators are [[catalog]] objects, representing boolean functions (they validate whether given conditions apply or not). They are used by other catalog objects, such as abilities (for auto-cast validation), behaviors (to decide whether the behavior works or not) or effects. Each validator entry is one condition, that can be tested by incuding this validator in appropriate field.
  
Validators inherit the [[Effect target list|target references]] form whatever object used them.
+
Validators inherit the [[Effect target reference|target references]] form whatever object used them.
  
 
==Types==
 
==Types==
Line 30: Line 30:
 
===Player===
 
===Player===
  
[[Category:StarCraft II]][[Category:Reference]][[Category:Data Editor]]
+
[[Category:StarCraft II]][[Category:Reference]][[Category:Data Editor]][[Category:Catalogs]]

Latest revision as of 22:50, 9 May 2011

Validators are catalog objects, representing boolean functions (they validate whether given conditions apply or not). They are used by other catalog objects, such as abilities (for auto-cast validation), behaviors (to decide whether the behavior works or not) or effects. Each validator entry is one condition, that can be tested by incuding this validator in appropriate field.

Validators inherit the target references form whatever object used them.

Types

Wrapup

Wrapup validators work only with other validators, they are used to construct more complex conditions.

Combine

Simplest wrapup validator, it combines multiple other validators with AND/OR logic function. It can also be used to negate other validator.

Condition

Condition validator first test one helper validator, and then, regarding the helper's outcome, decide which of the two validators to use. (If-then-else equivalent)

Function

Simillar to condition, but allows for more complex conditions (switch equivalent).

Generic

Generic validators don't belong to any other category.

Enumerate area

Counts all units in area that fulfill given condition (=validator). Then compares the count to a give value.

Terrain

Compares the Terrain texture set of the map.

Time of Day

Compares the time of day, propably in-game time.

Unit

Most of unit validators are self-explanaory, I would like to point out:

Unit filter

This applies the standard filter (attributes, unit state, invulnerability....)

Location

Player