Filtering in WML
A filter is a special WML block. Filters are used to describe a set of units, hexes, or weapons. Filters are defined as matching something if all the keys in the filter match that thing. For example, if a unit filter contains two keys, a unit must match both of the keys in order to match the filter.
Filters are often used in action tags (see EventWML). In this case the phrase "standard unit filter" is used in place of the set of standard keys. Sometimes a filter is used to find the first unit that matches the filter; for example, the [recall] tag recalls that unit.
Standard unit filters are also used in the tags [filter] and [filter_second]. These are subtags of [event] which describe when the event should trigger. Most event names (see EventWML) have units related to them called "primary unit" and "secondary unit". In order for an event to be triggered, primary unit must match the filter contained in [filter], and secondary unit must match the filter contained in [filter_second].
See StandardUnitFilter for details.
As you have seen, standard unit filter can contain a location filter. Several actions, such as [terrain], also use location filters. Location filters are represented on this site by the phrase "standard location filter".
See StandardLocationFilter for details.
These keys are used as filter input for weapon filters.
- range: a range to filter
- melee: only melee weapons pass
- ranged: only ranged weapons pass
- name: filter on the attack's name.
See data/units/ or http://www.wesnoth.org/units/ to find the name of a particular unit's attack.
- type: filter on the attack's type.
Values are 'blade', 'pierce', 'impact', 'fire', 'cold', and 'arcane'.
- damage: Template:DevFeature filter on damage value. Can be a specific number or a list of ranges like 'damage=0-5,7-99'
- special: filter on the attack's special power.
For values see AbilitiesWML.
Use [filter_location] within [filter] , for example:
[event] [filter] [filter_location] terrain=Ch [/filter_location] [/filter] [/event]
At some places the terrains can be filtered with a match list. The list is a comma separated list and matching will stop at the first matched terrain string. There's one special character ! which inverts the meaning of a match. Terrain strings can use the wildcard * to match zero or more following letters, characters behind the * are not allowed and the result is undefined.
ww* matches ww, www, wwW but not WWW
!, ww returns false if ww found and true if not
!, ww, wa, !, aa returns false if ww or wa found and true if aa found and false if none found.
*^V* matches all village-terrain
Notice how the * can be used separately for both layers (base and overlay layers are separated by the ^-character).
For a list of terrain types and their string codes see TerrainCodesWML.
The [filter_vision] tag allows you to filter events from the perspective of another side.
- yes: (default) matches when the unit is at a location that is not obscured by shroud or fog for the viewing_side
- no: matches when the unit is at location that is concealed by shroud or fog for the viewing_side
- viewing_side: the side, or list of sides, which are observing the unit's location. When multiple sides are listed, all of the sides must pass the visibility check in order for the [filter_vision] filter to return a successful match. When no sides are listed, all enemy sides must pass the visibility check.
Example: This event will fire when the enemy (side 2) moves into the player's field of vision. (This is only useful when the player's vision has been restricted by fog or shroud.)
[event] name=moveto first_time_only=yes [filter] side=2 [filter_vision] viewing_side=1 [/filter_vision] [/filter] [/event]