[Wesnoth-wiki-changes] FilterWML

[wiki]

UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040809 
Firefox/0.9.3
IP: 168.209.98.35
URI: http://wesnoth.slack.it/?FilterWML
 - - - - -
Index: FilterWML
===================================================================
RCS file: /home/wesnoth/cvsroot/wikiroot/FilterWML,v
retrieving revision 1.12
diff -u -r1.12 FilterWML
--- FilterWML   17 Oct 2004 16:07:14 -0000      1.12
+++ FilterWML   23 Oct 2004 13:15:41 -0000
@@ -2,7 +2,7 @@
 
 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 
the thing.
+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.
 
@@ -17,7 +17,7 @@
 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]||
+and //secondary unit// must match the filter contained in ||[filter_second]||.
 
 When a unit filter is applied to a map, first it applies to all units on the 
field, based on their coordinates.
 Next it applies to units in the recall list.
@@ -29,7 +29,7 @@
 * //description// unit matches the given description.
 A description is different from a name; while names can be changed and created 
in-game,
 a unit's description must be given to it by the scenario designer.
-When a unit is recruited, it recieves a name, but not a description.
+When a unit is recruited, it receives a name, but not a description.
 Also, descriptions are not affected by internationalization, only names.
 * //speaker// alias for description
 * //type// matches the unit's type name (can be a list of types)
@@ -39,14 +39,15 @@
 * //side// the unit is on the given side (can be a list)
 * //has_weapon// the unit has a weapon with the given name
 * //role// the unit has been assigned the given role
-* ||[not]|| this subtag contains another filter. if the content of this filter 
is matched, the parent's filter won't be
+* ||[not]|| this subtag contains another filter.
+If the content of this filter is matched, the parent's filter won't be.
 * standard location filter- the tile that the unit is standing on matches the 
location filter.
 
 ||Filtering Locations||
 
 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 by the phrase "standard location filter"
+Location filters are represented by the phrase "standard location filter".
 
 The following keys are used:
 * //x// the first coordinate
@@ -70,9 +71,9 @@
 
 Sometimes weapons are filtered on in WML.
 Currently the only weapon filter is in the ||[effect]|| tag.
-See also EffectWML
+See also EffectWML.
 
-these keys are used as filter input for weapon filters.
+These keys are used as filter input for weapon filters.
 
 * //range// a range to filter
   * 'short' only melee weapons pass
@@ -80,9 +81,9 @@
 * //name// filter on the attack's name.
 See ||data/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 'holy'
+Values are 'blade', 'pierce', 'impact', 'fire', 'cold', and 'holy'.
 * //special// filter on the attack's special power.
-For values see AbilitiesWML
+For values see AbilitiesWML.
 
 ||See Also||