The Battle for Wesnoth Wiki - User contributions [en]

EasyCoding

2007-09-21T03:15:53Z

Appleide: /* WML related features */

== Foreword ==
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

--[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)

== Animation related features ==
=== Victory animation ===
'''an animation to be played by the surviving unit during the death animation of the other unit'''

this should be fairly easy to do, just duplicate all death animation code, and modify the unit_die function to change the state of both units.

ask Boucman for extra help

* unit_display.cpp
* unit_type.cpp
* unit.cpp
* unit_animation.cpp;

Done! Submitting patch as soon as it can be tested. [[User:TheAT|TheAT]] 01:53, 17 October 2006 (CEST)

=== En Guard animation ===
'''An animation to replace the standing animation when the unit is next to an enemy'''

Slightly more tricky than the previous one, you should copy most of the standing code,
but beware that this should be invisible to external callers.
The call to get_stats should be looked at

Ask Boucman for extra help

* unit.cpp
* unit_type.cpp
* unit_animation.cpp

=== Special tags for Extra_anim ===
'''Special tags in the animate_unit event to call standard unit animations'''

One of the big limitation of the extra_animation tags is
that you need to modify the unit itself to have the extra anim.
Most anims can't be easily called that way.
It would be interesting to have special tags that would be recognised
to call the standard animations (attack, defense, etc...)

The tricky part is to handle correctly the "offset" parameter,
and add all the WML handling to "fill in" the information
we won't have available (non-existant filtering criterias)

This is more tricky than the two above,
and I would advise doing one of the other two first to understand how it works

Ask Boucman for extra help

* unit.cpp
* actions.cpp

=== Animate flags during a [delay] event ===
currently, the [event] tag calls SDL_delay() and blocks the game completely. It would be trivial to change it to a loop that would call event::pump() every 10ms to have all animations updated

the tricky part is to make sure the screen is somehow "locked" and that player can't play during that time (should be the case, simple checking is needed)

grep should give you the file to change

Note: this possibly shouldn't be implemented anymore, due to the blurred dialogs which would need to be reblurred on every redraw. Unless, of course, you can implement this so that the contents of dialogs aren't reblurred and redrawn but only the rest of the screen. -zookeeper

I am on this.Boucman please email me with more details when you have time [[User:Spx2|Spx2]] 12:31, 23 December 2006 (CEST)

Boucman please email me with an event that i can test this on

== WML related features ==

=== Side-specific messages ===
Side-specific [message]s ([http://gna.org/bugs/index.php?7427 FR #7427])
=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960])
=== Recall Event ===
WML event trigger for recalling (the current one triggers on both recalls and recruits) ([http://gna.org/bugs/index.php?3622 FR #3622]) (please read the comments of the report for a proper description of how this should work)
=== Enabling checking of damage dealt in WML ===
A WML variable should be set when triggering some combat-related events, allowing WML to know the amount of damage being dealt. ([http://gna.org/bugs/index.php?7673 FR #7673])
=== Support for leaderless multiplayergames ===
Add support for the WML tag victory_when_enemies_defeated in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])
=== Textboxes in options menu ===
Allow wml tag allowing players to enter text into textboxes in [messages] tag.

== GUI related features ==
=== Theme Changes ===
* show number of owned villages/total villages (FR: #3135) (--[[User:Alink|alink]] done but must update help, doc, tooltip...)
* allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])
* hide the hourglass item from the statusbar when there is no timer

=== Widget Changes ===
* show side number, name and team association information in the status table
* make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
* input history (chat, commands, ..), seek Sapient for more info and tips

== Miscellaneous ==
=== More powerful village naming ===
'''Adding mountain names and other features to village names, having a second random name in village names'''

Currently the village naming engine has a very good structure that could allow
more powerfull names to be generated.
Understanding how it works should be quite easy, and a few usefull improvements could be added.

* Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
* It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
* Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice

=== Debug Mode ===
* New debug command functionality (setting status.variables, possibly terrain, WML value display)
* Make it possible to toggle shroud and fog (but take care that this is only possible in campaigns)

FilterWML

2007-09-15T14:16:02Z

Appleide: /* Filtering Units */

{{WML Tags}}
== 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.

== Filtering Units ==

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]'''.

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.
This is important to remember as it means, for example,
that the tag '''[kill]''' can be used to kill units in the recall list.

{{DevFeature}} : you can access the filtered unit within the filter as the ''$this_unit'' variable, see [[SingleUnitWML]] for the possible content of these variables

Any number of the following key/tags can be used in a standard unit filter:

* ''description'' unit matches the given description. This is the same as ''description'' in the [unit] tag. Note that it is independent of ''user_description'', which can be internationalized independent of this. See [[SingleUnitWML]].
* ''speaker'' alias for description
* ''type'' matches the unit's type name (can be a list of types)
* ''race'' the race of the unit type.<br>Races are listed in the unit files ('''data/units/''')
* ''ability'' unit has a given ability; see [[AbilitiesWML]]
* ''side'' the unit is on the given side (can be a list)
* ''has_weapon'' the unit has a weapon with the given name
* ''canrecruit'' 1 if the unit can recruit (i.e. is a leader)
* ''gender'' female if the unit is female rather than the default of male
* ''role'' the unit has been assigned the given role; see '''[role]''', [[InternalActionsWML]]
* ''level'' the level of the unit
* ''x,y'' the position of the unit
* ''find_in'' name of an array or container variable; if present, the unit will not match unless it is also found stored in the variable {{DevFeature}}
* '''[wml_filter]''' {{DevFeature}} this is WML level filter for the unit. In it, you can filter on anything that is in the WML description of a unit. This description can be found in any savegame also in [[SingleUnitWML]].
* '''[and]''' an extra unit filter. Unless the unit also matches the [and] filter, then it will not count as a match. {{DevFeature}} ''Note: [and],[or], and [not] filters are considered after the containing filter; they are then processed in the order encountered.''
* '''[or]''' an extra unit filter. If a unit matches the [or] filter, then it will count as a match regardless of conditions in previous filters or the containing filter. {{DevFeature}}
* '''[not]''' an extra unit filter. If a unit matches the [not] filter, then that unit will not be considered a match by the containing filter.
* '''[filter_adjacent]''' {{DevFeature}} standard unit filter; if present the correct number of adjacent units must match this filter
** ''count'' - a number, range, or comma separated range; default "1-6"
** ''adjacent'' - a comma separated list of directions; default "n,ne,se,s,sw,nw"
** ''is_enemy'' - a boolean specifying whether the adjacent unit must be an enemy or an ally (optional)
* '''[filter_location]''' (in 1.2 a special filter / {{DevFeature}} standard location filter) - the tile that the unit is standing on matches the location filter.
** ''time_of_day'' filter matches only on a given time of day (one of lawful, chaotic or neutral).
** ''terrain'' comma separated list of terrains. If you are using terrain letters ([[TerrainLettersWML]]), then yes you must use commas to separate the terrains; this is different from the the '''[store_locations]''' tag or IF_TERRAIN macro (of utils.cfg)! So instead of "gfm", write "g,f,m" here.
** ''x,y'' the same as in the unit filter; supports any range {{DevFeature}}
** '''[filter]''' a standard unit filter; if present a unit must also be there {{DevFeature}}
** ''owner_side'' the side of the owner, if this location is an owned village. {{DevFeature}}
** ''find_in'' name of an array or container variable; if present, the location will not match unless it is also found stored in the variable {{DevFeature}}
** ''radius'' matches if any location within the radius matches this filter {{DevFeature}}
:This might not work, try enclosing "terrain=Gg" or whatever, with "[and] [/and]" if you use radius; Example for 1.3.7
[have_location]
x=$x1
y=$y1
[and]
terrain=Gg^Vh
[/and]
radius=1
[/have_location]

** '''[filter_radius]''' a standard location filter; normally the radius extends outwards from matching locations one step at a time without checking any additional information-- however, if this tag is present, the radius will be restricted so that it can only expand outwards in the directions where it passes the given location filter {{DevFeature}}
** '''[and]''' an extra location filter. Unless a location matches the [and] filter, then it will be excluded. {{DevFeature}} ''Note: [and],[or],and [not] extra location filters are considered after everything else in the containing filter (except radius, which is considered last in 1.3.8 and greater); they are then processed in the order encountered.''
** '''[or]''' an extra location filter. If a location matches the [or] filter, then it will count as a match regardless of conditions in previous filters or the containing filter. {{DevFeature}}
** '''[not]''' an extra location filter. If a location matches the [not] filter, then that location will be excluded. {{DevFeature}}
** '''[filter_adjacent_location]''' a standard location filter; if present the correct number of adjacent locations must match this filter {{DevFeature}}
*** ''count'' - a number, range, or comma separated range; default "1-6"
*** ''adjacent'' - a comma separated list of directions; default "n,ne,se,s,sw,nw"

* You are limited to having one ''description'', however this can be worked around. If you have several specific units you want excepted from matching, use a separate [not] subfilter for each one. If you want to match any of several specific units, you can apply DeMorgan's law and do the test by having a [not] subfilter and then below that another [not] subfilter for each unit you want included. For example to kill ([kill] uses the standard unit filter) all units except Gwiti Ha'atel and Tanar you can do the following:
[kill]
[not]
description=Gwiti Ha'atel
[/not]
[not]
description=Tanar
[/not]
[/kill]
:And similarly if you wanted to kill both Gwiti Ha'atel and Tanar, but no one else you could do the following:
[kill]
[not]
[not]
description=Gwiti Ha'atel
[/not]
[not]
description=Tanar
[/not]
[/not]
[/kill]
:although this is probably easier achieved using two tags:
[kill]
description=Gwiti Ha'atel
[/kill]
[kill]
description=Tanar
[/kill]
:although in {{DevFeature}} you would just do it like this:
[kill]
description=Gwiti Ha'atel
[or]
description=Tanar
[/or]
[/kill]

== 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 on this site by the phrase "standard location filter".

The following keys are used:
* ''x'' the first coordinate
* ''y'' the second coordinate
(in the development version, all the keys and tags found in [filter_location] above are part of the standard location filter {{DevFeature}})

While some locations should only be one hex (like the starting position of a unit),
others filter over multiple hexes.
The following syntax is used to filter over multiple hexes:

Dashes('''-''') are used to have the location be a range of hexes.
There must be values before and after the dash;
everything in between these numbers (inclusively) is part of the range.

Commas(''',''') are used to separate coordinates into a list.
The '''x''' and '''y''' lists are then paired up, with each pair representing one hex or range.

Note: although the ordering of locations in a list generally does not matter,
the action '''[move_unit_fake]''' takes in a list of hexes,
and moves an image onto each of those hexes in order.

== Filtering Weapons ==

Sometimes weapons are filtered on in WML.
Currently the only weapon filter is in the '''[effect]''' tag.
See also [[EffectWML]].

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://wesnoth.slack.it/unitlist.cgi
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'.
* ''special'' filter on the attack's special power.
For values see [[AbilitiesWML]].

=== Filtering Terrains ===

'''''[[User:SkeletonCrew#Branch_terrain|(SVN terrain only)]]'''''
At some places the terrains can be filtered with a
match list. This list is only usable with the new terrain
strings. 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.

Eg: <br>
ww* matches ww, www, wwW but not WWW <br>
!, ww returns false if ww found and true if not <br>
!, ww, wa, !, aa returns false if ww or wa found and true if aa found and false if none found.

== See Also ==

* [[UnitWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

EffectWML

2007-09-15T14:13:47Z

Appleide: /* the [effect] tag */

{{WML Tags}}
== the [effect] tag ==

The tag [effect] is used to describe one modification to a unit.
Any number of [effect] tags can be used to describe a complete
modification.
Modifications are permanent changes to a unit;
currently there is no way of removing a modification.

The following keys are always recognized for [effect]:
* ''unit_type'' only apply this effect if the affected unit's type name matches ''unit_type'' (can be a list of types).
* ''times'' {{DevFeature}} describes how much time the effect is applied. The default is to apply the effect once. Other possible value : "per level" which means that the effect is applied level times, where level is the unit level.
* ''apply_to'' describes what the effect actually affects.
[effect] uses different keys depending on the value of ''apply_to''. ''apply_to'' can take the following values:
* "new_attack" will use all other keys and tags as the description of an attack that will be added to the unit. See [[AttackWML]].
* ''remove_attacks'' {{DevFeature}} remove the matching attacks. All tags from the attack filter construct will be used to match the attack; see [[FilterWML]]. Notes: do not use a [filter] tag. Also, the last remaining attack will never be removed (since Wesnoth don't support it).
* "attack" find an attack and modify it. All tags from the attack filter construct will be used to match the attack; see [[FilterWML]]. After that, the following keys and tags can be used to modify the attack. Note: do not use a [filter] tag. Just put the keys you want to filter on inside the [effect] tag.
** ''set_name'' change the attack's name (ie identifier). ({{DevFeature}} this doesn't change the weapon's description like in 1.2)
** ''set_description'' {{DevFeature}} change the attack's description (ie displayed name).
** ''set_type'' change the attack type. Values are 'blade', 'pierce', 'impact', 'fire', 'cold', and 'holy'.
** ''set_special'' change the attack's specials. See [[AbilitiesWML]] for a list of possible values. Note that you can only set the normal specials defined in ''data/abilities.cfg'', not custom ones.
** ''[set_specials]'' {{DevFeature}} change the attack's specials. The specials to add are given exactly as in the [specials] tag.
*** ''mode'' if ''append'', adds the given specials to the attack. If ''replace'', replaces the existing specials with the given ones. Default ''replace''.
** ''remove_specials'' {{DevFeature}} remove the listed specials. The value of this key is the coma-separated list of the id of the specials to remove. This key is always evaluated before a [set_specials] tags in the same [effect]
** ''increase_damage'' increases the attack's damage. This can be positive or negative, so you can use it to decrease damage as well. If it ends in a percent(''''%''''), the change in damage will be a percentage ratio of the attack's original damage.
** ''increase_attacks'' increases the number of attack strikes. Like ''increase_damage'', it can be positive or negative, or a percentage.
** ''attack_weight'' change the attack's attack_weight. See [[AttackWML]] for explainations about attack_weight.
** ''defense_weight'' change the attack's defense_weight. See [[AttackWML]] for explainations about defense_weight.
* "hitpoints" modifies the unit's HP and/or max HP.
** ''increase'' the amount to increase the unit's HP.
** ''heal_full'' if present and not set to "no" the unit will be put back to full HP.
** ''increase_total'' will increase the total HP of the unit. Can be specified either as a negative or a positive value. It can also be specified as a percentage of the current total; i.e. "-50%" will cut max HP in half.
** ''violate_maximum'' it the unit ends up with more than its max HP after these modifications, and this key is present (set to any non-null value, ex. 'yes'), the unit's HP won't be lowered to its max HP.
* "movement" modifies the unit's movement points.
** ''increase'' maximum movement is increased by this amount. It can be positive, negative, or specified as a percentage.
** ''set'' maximum movement is set to a specific value.
* "max_experience" affects the amount of XP the unit needs for the next level.
** ''increase'' how to change the xp; again it can be negative, positive or a percentage.
* "loyal" no keys associated. The affected unit will be loyal i.e have an upkeep of 0.
* "movement_costs" speed through specific terrain is modified
** ''replace'' If set to "true", any new values replace the old ones. Otherwise, new values are added to old values (negative values allowed).
** [set_specials]
** [movement_costs] a subtag that describes the new movement costs just like in [[UnitWML]] for describing a unit type
* "defense" Sets unit chance to be hit in specific terrain (100 - defense value)
** ''replace'' If set to "true", any new values replace the old ones. Otherwise, new values are added to old values (negative values allowed).
** [defense] a subtag that describes the new defense just like in [[UnitWML]] for describing a unit type
* "resistance" Sets percent damage taken from combat
** ''replace'' If set to "true", any new values replace the old ones. Otherwise, new values are added to old values (negative values allowed).
** [resistance] a subtag that describes the new resistance just like in [[UnitWML]] for describing a unit type
* "variation" switches the unit into one of its variations.
** ''name'' the name of the variation to invoke.
* "status" modifies the status affecting the unit.
** ''add'' a list of status modifications to add. Beware, these may be reapplied later, such as when the unit is recalled or levels up; if in an event, you can use [[InternalActionsWML|[store_unit]]] and [[DirectActionsWML|[unstore_unit]]], modifying unit.status.name directly, to avoid this, or if you are creating the unit, you can just add it to the unit's [status] tag in the [unit] tag. These are listed in [status], [[SingleUnitWML]].
** ''remove'' a list of status modifications to remove.
* ''zoc'' {{DevFeature}} toggle the zone of control.
** ''value'' new value for zoc (0=disable, other=enable).
* ''profile'' {{DevFeature}} customize the profile for this unit type
** ''portrait'' new image to display when the unit speaks
** ''description'' sets the text to display when hovering over the unit's type in the righthand pane
* "new_ability" {{DevFeature}} Adds one or more abilities to a unit.
** [abilities] A subtag that contains the ability definitions.
* "remove_ability" {{DevFeature}} Removes one or more abilities from a unit. Abilities are not reference counted: added, added, removed = gone.
** [abilities] A subtag that contains the ability definitions. Strictly speaking, all that is needed is the id= inside some tag.
* ''new_animation'' {{DevFeature}} contain animations that will be added to the unit

== See Also ==

* [[UnitWML]]
* [[AttackWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

FilterWML

2007-09-15T14:08:41Z

Appleide:

{{WML Tags}}
== 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.

== Filtering Units ==

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]'''.

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.
This is important to remember as it means, for example,
that the tag '''[kill]''' can be used to kill units in the recall list.

{{DevFeature}} : you can access the filtered unit within the filter as the ''$this_unit'' variable, see [[SingleUnitWML]] for the possible content of these variables

Any number of the following key/tags can be used in a standard unit filter:

* ''description'' unit matches the given description. This is the same as ''description'' in the [unit] tag. Note that it is independent of ''user_description'', which can be internationalized independent of this. See [[SingleUnitWML]].
* ''speaker'' alias for description
* ''type'' matches the unit's type name (can be a list of types)
* ''race'' the race of the unit type.<br>Races are listed in the unit files ('''data/units/''')
* ''ability'' unit has a given ability; see [[AbilitiesWML]]
* ''side'' the unit is on the given side (can be a list)
* ''has_weapon'' the unit has a weapon with the given name
* ''canrecruit'' 1 if the unit can recruit (i.e. is a leader)
* ''gender'' female if the unit is female rather than the default of male
* ''role'' the unit has been assigned the given role; see '''[role]''', [[InternalActionsWML]]
* ''level'' the level of the unit
* ''x,y'' the position of the unit
* ''find_in'' name of an array or container variable; if present, the unit will not match unless it is also found stored in the variable {{DevFeature}}
* '''[wml_filter]''' {{DevFeature}} this is WML level filter for the unit. In it, you can filter on anything that is in the WML description of a unit. This description can be found in any savegame also in [[SingleUnitWML]].
* '''[and]''' an extra unit filter. Unless the unit also matches the [and] filter, then it will not count as a match. {{DevFeature}} ''Note: [and],[or], and [not] filters are considered after the containing filter; they are then processed in the order encountered.''
* '''[or]''' an extra unit filter. If a unit matches the [or] filter, then it will count as a match regardless of conditions in previous filters or the containing filter. {{DevFeature}}
* '''[not]''' an extra unit filter. If a unit matches the [not] filter, then that unit will not be considered a match by the containing filter.
* '''[filter_adjacent]''' {{DevFeature}} standard unit filter; if present the correct number of adjacent units must match this filter
** ''count'' - a number, range, or comma separated range; default "1-6"
** ''adjacent'' - a comma separated list of directions; default "n,ne,se,s,sw,nw"
** ''is_enemy'' - a boolean specifying whether the adjacent unit must be an enemy or an ally (optional)
* '''[filter_location]''' (in 1.2 a special filter / {{DevFeature}} standard location filter) - the tile that the unit is standing on matches the location filter.
** ''time_of_day'' filter matches only on a given time of day (one of lawful, chaotic or neutral).
** ''terrain'' comma separated list of terrains. If you are using terrain letters ([[TerrainLettersWML]]), then yes you must use commas to separate the terrains; this is different from the the '''[store_locations]''' tag or IF_TERRAIN macro (of utils.cfg)! So instead of "gfm", write "g,f,m" here.
** ''x,y'' the same as in the unit filter; supports any range {{DevFeature}}
** '''[filter]''' a standard unit filter; if present a unit must also be there {{DevFeature}}
** ''owner_side'' the side of the owner, if this location is an owned village. {{DevFeature}}
** ''find_in'' name of an array or container variable; if present, the location will not match unless it is also found stored in the variable {{DevFeature}}
** ''radius'' matches if any location within the radius matches this filter {{DevFeature}}
EDIT: This might not work, try enclosing "terrain=Gg" or whatever, with "[and] [/and]" if you use radius
** '''[filter_radius]''' a standard location filter; normally the radius extends outwards from matching locations one step at a time without checking any additional information-- however, if this tag is present, the radius will be restricted so that it can only expand outwards in the directions where it passes the given location filter {{DevFeature}}
** '''[and]''' an extra location filter. Unless a location matches the [and] filter, then it will be excluded. {{DevFeature}} ''Note: [and],[or],and [not] extra location filters are considered after everything else in the containing filter (except radius, which is considered last in 1.3.8 and greater); they are then processed in the order encountered.''
** '''[or]''' an extra location filter. If a location matches the [or] filter, then it will count as a match regardless of conditions in previous filters or the containing filter. {{DevFeature}}
** '''[not]''' an extra location filter. If a location matches the [not] filter, then that location will be excluded. {{DevFeature}}
** '''[filter_adjacent_location]''' a standard location filter; if present the correct number of adjacent locations must match this filter {{DevFeature}}
*** ''count'' - a number, range, or comma separated range; default "1-6"
*** ''adjacent'' - a comma separated list of directions; default "n,ne,se,s,sw,nw"

* You are limited to having one ''description'', however this can be worked around. If you have several specific units you want excepted from matching, use a separate [not] subfilter for each one. If you want to match any of several specific units, you can apply DeMorgan's law and do the test by having a [not] subfilter and then below that another [not] subfilter for each unit you want included. For example to kill ([kill] uses the standard unit filter) all units except Gwiti Ha'atel and Tanar you can do the following:
[kill]
[not]
description=Gwiti Ha'atel
[/not]
[not]
description=Tanar
[/not]
[/kill]
:And similarly if you wanted to kill both Gwiti Ha'atel and Tanar, but no one else you could do the following:
[kill]
[not]
[not]
description=Gwiti Ha'atel
[/not]
[not]
description=Tanar
[/not]
[/not]
[/kill]
:although this is probably easier achieved using two tags:
[kill]
description=Gwiti Ha'atel
[/kill]
[kill]
description=Tanar
[/kill]
:although in {{DevFeature}} you would just do it like this:
[kill]
description=Gwiti Ha'atel
[or]
description=Tanar
[/or]
[/kill]

== 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 on this site by the phrase "standard location filter".

The following keys are used:
* ''x'' the first coordinate
* ''y'' the second coordinate
(in the development version, all the keys and tags found in [filter_location] above are part of the standard location filter {{DevFeature}})

While some locations should only be one hex (like the starting position of a unit),
others filter over multiple hexes.
The following syntax is used to filter over multiple hexes:

Dashes('''-''') are used to have the location be a range of hexes.
There must be values before and after the dash;
everything in between these numbers (inclusively) is part of the range.

Commas(''',''') are used to separate coordinates into a list.
The '''x''' and '''y''' lists are then paired up, with each pair representing one hex or range.

Note: although the ordering of locations in a list generally does not matter,
the action '''[move_unit_fake]''' takes in a list of hexes,
and moves an image onto each of those hexes in order.

== Filtering Weapons ==

Sometimes weapons are filtered on in WML.
Currently the only weapon filter is in the '''[effect]''' tag.
See also [[EffectWML]].

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://wesnoth.slack.it/unitlist.cgi
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'.
* ''special'' filter on the attack's special power.
For values see [[AbilitiesWML]].

=== Filtering Terrains ===

'''''[[User:SkeletonCrew#Branch_terrain|(SVN terrain only)]]'''''
At some places the terrains can be filtered with a
match list. This list is only usable with the new terrain
strings. 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.

Eg: <br>
ww* matches ww, www, wwW but not WWW <br>
!, ww returns false if ww found and true if not <br>
!, ww, wa, !, aa returns false if ww or wa found and true if aa found and false if none found.

== See Also ==

* [[UnitWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

TerrainCodesWML

2007-07-07T08:09:28Z

Appleide: /* See Also */

{{WML Tags}}
== Values of terrain letters ==

What each letter represents in Wesnoth maps,
and the possible values of the ''letter'' key.

See [[TerrainWML]] for information on how to define a terrain.

* '''A''' human (snow) hill village
* '''a''' human hill village
* '''B''' desert village (adobe)
* '''b''' human mountain village
* '''C''' castle
* '''c''' shallow water, "coast"
* '''D''' underground village (cave, village), "dungeon village"
* '''d''' sand, (old desert)
* '''E''' desert road
* '''e''' elven (snow) village
* '''F''' forest (snow)
* '''f''' forest
* '''G''' savanna (grass)
* '''g''' grass
* '''H''' hills (snow)
* '''h''' hills
* '''I''' desert
* '''i''' ice (tundra)
* '''J''' desert hills
* '''j''' -nothing- (will be snowy mountains)
* '''K''' keep (castle)
* '''k''' river ford (grass, shallow water)
* '''L''' tropical forest village (savanna, village)
* '''l''' lava (canyon)
* '''M''' desert mountains
* '''m''' mountain
* '''N''' ruined castle
* '''n''' encampment (castle)
* '''O''' -nothing- (will probably be an Orc Castle one day)
* '''o''' dwarven castle (castle)
* '''P''' desert oasis
* '''p''' dwarven village
* '''Q''' sunken ruin
* '''q''' ruin (swamp)
* '''R''' road (grass)
* '''r''' dirt (grass)
* '''S''' tundra
* '''s''' deep water
* '''T''' forest (tropical)
* '''t''' village
* '''U''' desert village (tent)
* '''u''' cave
* '''V''' snow village (tundra, village)
* '''v''' human village (village)
* '''W''' cavewall
* '''w''' swamp
* '''X''' canyon (replaced by chasm in trunk)
* '''x''' reserved for UMCs
* '''Y''' swamp village (swamp, village)
* '''y''' reserved for UMCs
* '''Z''' mermen village (shallow water)
* '''z''' reserved for UMCs
* '''/''','''|''','''\''' bridge (grass, shallow water)
* '''~''' fog
* ' ' void/shroud (it uses the "space" character)
* '''*''' reserved for UMCs
* '''^''' reserved for UMCs
* '''%''' reserved for UMCs
* '''@''' reserved for UMCs
* '''[''' rockbound cave
* ''']''' mushroom grove
* ''' ' ''' illuminated cave
* ''' ? ''' great Elven tree
* ''' & ''' impassable mountains
* ''' " ''' ???
* ''' $ ''' ???
* ''' . ''' ???
* ''' ; ''' ???
* ''' : ''' ???
* ''' < ''' ???
* ''' > ''' ???
* ''' _ ''' ???
* ''' ` ''' ???

==Reserved letters and non-letter Characters==
Reserved letters are for custom terrains in user-made campaigns. In addition to these it is currently also possible to use other characters not on the above list to represent custom terrain, such as ½ § @ % etc., but new "official" terrain may be assigned for these characters in the future. So when creating custom terrain, the letters marked as reserved on the above list should be used first.
Use campaign definitions (see [[CampaignWML]]) to prevent your custom terrains from interfering with other campaigns.

== Terrain strings '''''[[User:SkeletonCrew#Branch_terrain|(SVN terrain only)]]''''' ==
The terrains will be changed from a single letter to a multi letter system. There will be a compability layer for a short while. This layer doesn't work for campaigns with custom terrains, these campaigns have to be changed to use the new system.

The following rules are stated for the new terrain letters, note most of these rules are not validated since it would slow down Wesnoth; not following these rules might break Wesnoth.
* terrain strings are between 2 and 4 characters
* terrain strings start with a capital letter and the following letters are lower case
* terrain strings can only contain letters and the symbols /|\ which are meant for directional items like bridges.
* the underscore is used for internal terrains
* the star '*' can be used for wildcards in some parts

Starting positions are defined by a number followed by 1 space and then the terrain string; this means that a starting position is no longer automatically a keep.

The letters Y,y,Z,z are reserved for UMC so any string containing any of these letters is a custom terrain. Other undefined terrain strings are reserved for future expansion within Wesnoth.

=== Conversion form old to new ===
Map conversion logic is included in the [[Maintenance_tools|upconvert]] tool. This script will, among other things, convert a map with the old letters to the new strings. Here is a lookup table with the letters.

char= a b c d e f g h i j k l m
str= Vhh Vhm Ww Ds Vea Ff Gg Hh Ai Wwf Ql Mm

char= n o p q r s t u v w x y z
str= Ce Cud Vud Chs Re Wo Veg Uu Vhg Ss

char= A B C D E F G H I J K L M
str= Vhha Vda Ch Vu Rd Fa Gs Ha Dd Hd _K Vht Md

char= N O P Q R S T U V W X Y Z
str= Chr Do Chw Rr Aa Ft Vdt Vha Xu Qxu Vs Vwm

char= / | \ & _ ~ ? ] [ '
str= Bww/ Bww| Bww\ Xm _s _f Fet Uf Uh Uui

=== terrains sorted per group ===
This list shows the string for the terrains, the italic strings are reservations for terrains.
The old letter is extra shown for as an extra reference.

==== Snow terrains ====
<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>Ai</td>
<td>i</td>
<td>ice</td>
<td>snow</td>
</tr>

<tr>
<td>Aa</td>
<td>S</td>
<td>tundra "Arctic"</td>
<td>snow</td>
</tr>

</table>

==== Bridges ====
Since bridges are directional all strings here
will be appended with either /|\ to show their
direction. In this list these signs are replaced
with a *.

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td><i>Brx*</i></td>
<td></td>
<td>Bridge of stones over chasm for aboveground</td>
<td>bridge</td>
</tr>

<tr>
<td><i>Bxu*</i></td>
<td></td>
<td>Bridge over chasm underground</td>
<td>bridge</td>
</tr>

<tr>
<td><i>Bsw*</i></td>
<td></td>
<td>wooden bridge over swamp</td>
<td>bridge</td>
</tr>

<tr>
<td><i>Bwr*</i></td>
<td></td>
<td>Stone Bridge over shallow water</td>
<td>bridge</td>
</tr>

<tr>
<td>Bww*</td>
<td>/|\</td>
<td>wooden bridge bridge, over wadeable, wooden</td>
<td>bridge, common</td>
</tr>

</table>

==== Castles ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>Ce</td>
<td>n</td>
<td>encampment (castle)</td>
<td>castle, common</td>
</tr>

<tr>
<td>Ch</td>
<td>C</td>
<td>human castle</td>
<td>castle, common</td>
</tr>

<tr>
<td>Cv</td>
<td></td>
<td>Elven castle</td>
<td>castle</td>
</tr>

<tr>
<td>Chr</td>
<td>N</td>
<td>ruined castle</td>
<td>castle</td>
</tr>

<tr>
<td>Chs</td>
<td>q</td>
<td>human ruin (swamp)</td>
<td>castle</td>
</tr>

<tr>
<td>Chw</td>
<td>Q</td>
<td>human sunken ruin</td>
<td>castle</td>
</tr>

<tr>
<td><i>Co</i></td>
<td>O</td>
<td>will be an Orc Castle one day</td>
<td>castle</td>
</tr>

<tr>
<td>Cud</td>
<td>o</td>
<td>dwarven castle "castle underground, dwarf"</td>
<td>castle, underground</td>
</tr>

</table>

==== desert ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>Dd</td>
<td>I</td>
<td>desert</td>
<td>desert</td>
</tr>

<tr>
<td>Do</td>
<td>P</td>
<td>desert oasis</td>
<td>desert</td>
</tr>

<tr>
<td>Ds</td>
<td>d</td>
<td>sand, (old desert)</td>
<td>desert</td>
</tr>

</table>

==== Forest ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>Fa</td>
<td>F</td>
<td>forest (snow) "forest arctic"</td>
<td>forrest, snow</td>
</tr>

<tr>
<td><i>Fb</i></td>
<td></td>
<td>Sinister Forest "Forest, Bad"</td>
<td>forrest</td>
</tr>

<tr>
<td>Fet</td>
<td>?</td>
<td>great Elven tree</td>
<td>forrest</td>
</tr>

<tr>
<td>Ff</td>
<td>f</td>
<td>forrest</td>
<td>forrest, common</td>
</tr>

<tr>
<td>Ft</td>
<td>T</td>
<td>forrest tropical</td>
<td>forrest</td>
</tr>

</table>

==== Grass ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td><i>Gb</i></td>
<td></td>
<td>dying "Grass brown/bad"</td>
<td>grass</td>
</tr>

<tr>
<td><i>Gf</i></td>
<td></td>
<td>Farmer's Fields</td>
<td>grass</td>
</tr>

<tr>
<td>Gg</td>
<td>g</td>
<td>grass</td>
<td>grass, common</td>
</tr>

<tr>
<td>Gs</td>
<td>G</td>
<td>savanna (grass)</td>
<td>grass</td>
</tr>

</table>

==== hill ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>Ha</td>
<td>H</td>
<td>hills (snow) "hills arctic"</td>
<td>hill, snow</td>
</tr>

<tr>
<td>Hd</td>
<td>J</td>
<td>desert hills (dunes)</td>
<td>hill, desert</td>
</tr>

<tr>
<td>Hh</td>
<td>h</td>
<td>hills</td>
<td>hill, common</td>
</tr>

</table>

==== Keep ====
The keep definition is now done with terrain transition WML,
since we're no longer out of letters, this will be done
manually. the _K is for backwards compability but this
will be removed in the near future. The _K uses the special
castle transition WML the new ones don't. This would
also allow to mix items, eg a Kh keep in a Ce castle.

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>_K</td>
<td>K</td>
<td>keep (castle)</td>
<td>keep, common</td>
</tr>

<tr>
<td>Ke</td>
<td></td>
<td>encampment (keep)</td>
<td>keep, common</td>
</tr>

<tr>
<td>Kh</td>
<td></td>
<td>keep castle</td>
<td>keep, common</td>
</tr>

<tr>
<td>Khr</td>
<td></td>
<td>ruined keep</td>
<td>keep</td>
</tr>

<tr>
<td>Khs</td>
<td></td>
<td>human ruin keep(swamp)</td>
<td>keep</td>
</tr>

<tr>
<td>Khw</td>
<td></td>
<td>human sunken ruin keep</td>
<td>keep</td>
</tr>

<tr>
<td><i>Ko</i></td>
<td></td>
<td>will be an Orc keep one day</td>
<td>keep</td>
</tr>

<tr>
<td>Kud</td>
<td></td>
<td>dwarven keep "keep underground, dwarf"</td>
<td>keep, underground</td>
</tr>

<tr>
<td>Kv</td>
<td></td>
<td>Elven Keep"</td>
<td>keep, unknown?</td>
</tr>

</table>

==== Mountain ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td><i>Ma</i></td>
<td></td>
<td>snowy mountains</td>
<td>mountain, snow</td>
</tr>

<tr>
<td>Md</td>
<td>M</td>
<td>desert mountains</td>
<td>mountain, desert</td>
</tr>

<tr>
<td>Mm</td>
<td>m</td>
<td>mountain</td>
<td>mountain, common</td>
</tr>

</table>

==== (mostly) Impassable ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td><i>Qx</i></td>
<td></td>
<td>chasm for above ground</td>
<td>misc</td>
</tr>

<tr>
<td>Qxu</td>
<td>X</td>
<td>chasm for underground</td>
<td>misc, underground</td>
</tr>

<tr>
<td><i>Qxw</i></td>
<td></td>
<td>aboveground chasm with water pouring over the edge</td>
<td>misc</td>
</tr>

<tr>
<td>Ql</td>
<td>l</td>
<td>lava</td>
<td>misc</td>
</tr>

<tr>
<td><i>Qr</i></td>
<td></td>
<td>stone wall</td>
<td>misc</td>
</tr>

</table>

==== road ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td><i>Rc</i></td>
<td></td>
<td>Carpeted Floor</td>
<td>road</td>
</tr>

<tr>
<td>Rd</td>
<td>E</td>
<td>desert road</td>
<td>road, desert</td>
</tr>

<tr>
<td>Re</td>
<td>r</td>
<td>dirt road "earth"</td>
<td>road, common</td>
</tr>

<tr>
<td>Rr</td>
<td></td>
<td>stone road "rock"</td>
<td>road</td>
</tr>

<tr>
<td><i>Rw</i></td>
<td></td>
<td>Wood floor (interior)</td>
<td>road</td>
</tr>

</table>

==== swamp ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td><i>Sb</i></td>
<td></td>
<td>fetid swamp "Swamp Bad"</td>
<td>swamp</td>
</tr>

<tr>
<td><i>Ss</i></td>
<td>w</td>
<td>swamp</td>
<td>swamp</td>
</tr>

</table>

==== underground ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>Uu</td>
<td>u</td>
<td>normal cave</td>
<td>underground</td>
</tr>

<tr>
<td>Uui</td>
<td>'</td>
<td>illuminated cave</td>
<td>underground</td>
</tr>

<tr>
<td>Uf</td>
<td>]</td>
<td>mushroom grove "underground forest"</td>
<td>underground</td>
</tr>

<tr>
<td>Uh</td>
<td>[</td>
<td>rockbound cave (functionally "underground hill")</td>
<td>underground</td>
</tr>

<tr>
<td>Uhi</td>
<td></td>
<td>illuminated rockbound cave (functionally "underground hill")</td>
<td>underground</td>
</tr>

<tr>
<td><i>Uuc</i></td>
<td></td>
<td>normal cave, carved</td>
<td>underground</td>
</tr>

</table>

==== village ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>Vda</td>
<td>B</td>
<td>desert village (adobe)</td>
<td>village, desert</td>
</tr>

<tr>
<td>Vdt</td>
<td>U</td>
<td>desert village (tent)</td>
<td>village, desert</td>
</tr>

<tr>
<td>Veg</td>
<td>t</td>
<td>elven village "village elven grassland"</td>
<td>village</td>
</tr>

<tr>
<td>Vea</td>
<td>e</td>
<td>elven (snow) village</td>
<td>village, snow</td>
</tr>

<tr>
<td>Vha</td>
<td>V</td>
<td>village, snow snow village (tundra, village)</td>
<td>village, snow</td>
</tr>

<tr>
<td>Vhg</td>
<td>v</td>
<td>human village (village)</td>
<td>village, common</td>
</tr>

<tr>
<td>Vhh</td>
<td>a</td>
<td>human hill village</td>
<td>village, hill, common</td>
</tr>

<tr>
<td>Vhha</td>
<td>A</td>
<td>human (snow) hill village</td>
<td>village, snow, hill</td>
</tr>

<tr>
<td>Vhm</td>
<td>b</td>
<td>human mountain village</td>
<td>village, mountain</td>
</tr>

<tr>
<td>Vht</td>
<td>L</td>
<td>tropical village (savanna, village) --nothing foresty about this village</td>
<td>village</td>
</tr>

<tr>
<td>Vu</td>
<td>D</td>
<td>underground village (cave, village)</td>
<td>village, underground</td>
</tr>

<tr>
<td>Vud</td>
<td>p</td>
<td>dwarven village</td>
<td>village, underground</td>
</tr>

<tr>
<td>Vwm</td>
<td>Z</td>
<td>mermen village (shallow water)</td>
<td>village, water</td>
</tr>

<tr>
<td>Vs</td>
<td>Y</td>
<td>swamp village (swamp, village)</td>
<td>village, swamp</td>
</tr>

<tr>
<td>Vsm</td>
<td></td>
<td>swamp merfolk village (swamp)</td>
<td>village, swamp</td>
</tr>

</table>

==== water ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>Wo</td>
<td>s</td>
<td>deep water "water, ocean"</td>
<td>water, common</td>
</tr>

<tr>
<td>Ww</td>
<td>c</td>
<td>shallow water, "water, wade-able"</td>
<td>water, common</td>
</tr>

<tr>
<td>Wwf</td>
<td>k</td>
<td>river ford "water wadeable, ford"</td>
<td>water</td>
</tr>

<tr>
<td><i>Wwu</i></td>
<td></td>
<td>shallow underground water</td>
<td>water, underground</td>
</tr>

</table>

==== Impassable ====

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>Xm</td>
<td>&</td>
<td>impassable moutains</td>
<td>impassable, mountain</td>
</tr>

<tr>
<td><i>Xrw</i></td>
<td></td>
<td>Impassable stone "rock" wall (interior)</td>
<td>impassable</td>
</tr>

<tr>
<td>Xu</td>
<td>W</td>
<td>cavewall</td>
<td>impassable, underground</td>
</tr>

<tr>
<td><i>Xuc</i></td>
<td></td>
<td>cavewall, carved</td>
<td>impassable, underground</td>
</tr>

<tr>
<td><i>Xww</i></td>
<td></td>
<td>Impassable wooden wall (interior)</td>
<td>impassable</td>
</tr>

</table>

==== Specials ====
These terrains are hardcoded in the game and translated
automatically. The old UMC terrains are here for backwards
compability this compability will only be guaranteed till
the next major release after 1.2.(That would be 1.4 or 2.0.)
As stated before the * will no longer be supported.

<table border="1"><tr>
<th>String</th>
<th>Old letter</th>
<th>Description</th>
<th>Theme</th>
</tr>

<tr>
<td>_f</td>
<td>~</td>
<td>fog</td>
<td>misc</td>
</tr>

<tr>
<td>_s</td>
<td> (space character)</td>
<td>void/shroud</td>
<td>misc</td>
</tr>

</table>

== Adding terrains ==
When adding terrains make sure the following files are also checked:

data/faction/* contains favorite positions for the different factions, this is only used for the random map generator at the moment so it is not very important.

data/abilities.cfg contains the definition of ''submerge'' and ''ambush'' so depending on the change these need to be updated.

data/utils/utils.cfg contains the macro STARTING_VILLAGES which contains a list of village strings. This list doesn't support wildcards (yet).

== See Also ==
* [[TerrainWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

TerrainCodesWML

2007-07-07T08:01:18Z

Appleide: /* Keep */

User:Appleide

2007-05-26T08:54:16Z

Appleide:

Appleide' User Page.

Played Wesnoth since v0.5. (Pro-noob status)

In Progress
-Nothing, but I thought of another faction.

Achievements

-Tried to make some factions, but wasn't motivated/artistically skilled enough for it.
-Made the first DotX map. =)

AbilitiesWML

2006-07-05T02:07:37Z

Appleide: /* Attack specials */

{{WML Tags}}
== Abilities and their effects ==

There are two types of abilities: ones that apply to units (called ''abilities'') and weapon-based (called
''specials''). A unit may have multiple abilities,
but each attack can only have at most one special.

== Normal abilities (for BFW 1.0) ==
{| class="gallery" style="text-align:left"
|-
! ambush
| the unit becomes invisible on forest. Invisible units cannot be seen by enemies and do not possess zone of control, although if an enemy moves next to one, it becomes visible again.
|-
! cures
| unit will heal ''curer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''cure_amount''. If a neighbour is poisoned, it will cure the poison instead of healing.
|-
! heals
| unit will heal ''healer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''heal_amount''. If a neighbour is poisoned, it will prevent the poison's effect instead of healing.
|-
! illuminates
| all neighbouring hex will be "illuminated", in other words have a different time of day (See [[TimeWML]]). Typically, this will be one step brighter.
|-
! leadership
| the unit will increase the damage of all neighbouring units by +25% per level difference. (If the neighbouring unit is of a higher level, this effect is negated.)
|-
! nightstalk
| the unit becomes invisible during night.
|-
! regenerates
| the unit will heal itself 8 hp per turn. If it is poisoned, it will remove the poison instead of healing.
|-
! skirmisher
| the unit ignores zone of control when moving, but still cannot move directly through an enemy unit
|-
! steadfast
| the unit takes half normal damage when it did not initiate the attack.
|-
! teleport
| the unit can move between any two allied villages for one move point
|}

== Normal abilities {{DevFeature}} ==
{| class="gallery" style="text-align:left"
|-
! submerge
| the unit becomes invisible in deep water.
|}

== Attack specials ==
{| class="gallery" style="text-align:left"
|-
! backstab
| doubles damage whenever there is a unit on the opposite side (location) of the defending unit that distracts it. In 1.0.x the distracting unit must be on the same side (player) as the attacker. {{DevFeature}}: the distracting unit must be an enemy of the defending unit and not incapacitated (e.g. turned to stone).
|-
! berserk
| forces the combat to continue until either the attacker or the defender is killed, or until 30 rounds have passed (whichever comes first.)
|-
! charge
| when attacking, both this weapon and defender get double damage.
|-
! drain
| The controller of this weapon gains health equal to half the damage done (rounded down) whenever this attack hits.
|-
! firststrike
| when this weapon is used to defend, the battle proceeds as if it were the attacker (i.e. it attacks first).
|-
! magical
| this weapon always has a 70% chance of hitting.
|-
! marksman
| when attacking, this weapon has a minimum of 60% chance of hitting.
|-
! plague
| The controller of this weapon is copied onto the tile that any unit this attack killed was on.
|-
! poison
| when this weapon hits, the defender becomes poisoned (see [status], [[SingleUnitWML]]).
|-
! slow
| when this weapon hits, the defender becomes slowed (see [status], [[SingleUnitWML]]).
|-
! stone
| when this weapon hits, the defender turns to stone (see [status], [[SingleUnitWML]]).
|}

== See Also ==

* [[AbilitiesWMLTechnical1.1.3]]
* [[UnitWML]]
* [[SingleUnitWML]]
* [[ReferenceWML]]

AbilitiesWML

2006-07-05T01:44:42Z

Appleide: /* Attack specials */

{{WML Tags}}
== Abilities and their effects ==

There are two types of abilities: ones that apply to units (called ''abilities'') and weapon-based (called
''specials''). A unit may have multiple abilities,
but each attack can only have at most one special.

== Normal abilities (for BFW 1.0) ==
{| class="gallery" style="text-align:left"
|-
! ambush
| the unit becomes invisible on forest. Invisible units cannot be seen by enemies and do not possess zone of control, although if an enemy moves next to one, it becomes visible again.
|-
! cures
| unit will heal ''curer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''cure_amount''. If a neighbour is poisoned, it will cure the poison instead of healing.
|-
! heals
| unit will heal ''healer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''heal_amount''. If a neighbour is poisoned, it will prevent the poison's effect instead of healing.
|-
! illuminates
| all neighbouring hex will be "illuminated", in other words have a different time of day (See [[TimeWML]]). Typically, this will be one step brighter.
|-
! leadership
| the unit will increase the damage of all neighbouring units by +25% per level difference. (If the neighbouring unit is of a higher level, this effect is negated.)
|-
! nightstalk
| the unit becomes invisible during night.
|-
! regenerates
| the unit will heal itself 8 hp per turn. If it is poisoned, it will remove the poison instead of healing.
|-
! skirmisher
| the unit ignores zone of control when moving, but still cannot move directly through an enemy unit
|-
! steadfast
| the unit takes half normal damage when it did not initiate the attack.
|-
! teleport
| the unit can move between any two allied villages for one move point
|}

== Normal abilities {{DevFeature}} ==
{| class="gallery" style="text-align:left"
|-
! submerge
| the unit becomes invisible in deep water.
|}

== Attack specials ==
{| class="gallery" style="text-align:left"
|-
! backstab
| doubles damage whenever there is a unit on the opposite side (location) of the defending unit that distracts it. In 1.0.x the distracting unit must be on the same side (player) as the attacker. {{DevFeature}}: the distracting unit must be an enemy of the defending unit and not incapacitated (e.g. turned to stone).
|-
! berserk
| forces the combat to continue until either the attacker or the defender is killed, or until 30 rounds have passed (whichever comes first.)
|-
! charge
| when attacking, both this weapon and defender get double damage.
|-
! drain
| The controller of this weapon gains health equal to half the damage done (rounded down) whenever this attack hits.
|-
! firststrike
| when this weapon is used to defend, the battle proceeds as if it were the attacker (i.e. it attacks first).
|-
! magical
| this weapon always has a 70% chance of hitting.
|-
! marksman
| when attacking, this weapon has a minimum of 60% chance of hitting.
|-
! plague
| The controller of this weapon is copied onto the tile that any unit this attack killed was on.
|-
! poison
| when this weapon hits, the defender becomes poisoned (see [status], [[SingleUnitWML]]).
|-
! rage (x)
| forces the combat to repeat for x times. 1.17 or over only.
|-
! slow
| when this weapon hits, the defender becomes slowed (see [status], [[SingleUnitWML]]).
|-
! stone
| when this weapon hits, the defender turns to stone (see [status], [[SingleUnitWML]]).
|}

== See Also ==

* [[AbilitiesWMLTechnical1.1.3]]
* [[UnitWML]]
* [[SingleUnitWML]]
* [[ReferenceWML]]

AbilitiesWML

2006-07-05T01:43:28Z

Appleide: /* Attack specials */

{{WML Tags}}
== Abilities and their effects ==

There are two types of abilities: ones that apply to units (called ''abilities'') and weapon-based (called
''specials''). A unit may have multiple abilities,
but each attack can only have at most one special.

== Normal abilities (for BFW 1.0) ==
{| class="gallery" style="text-align:left"
|-
! ambush
| the unit becomes invisible on forest. Invisible units cannot be seen by enemies and do not possess zone of control, although if an enemy moves next to one, it becomes visible again.
|-
! cures
| unit will heal ''curer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''cure_amount''. If a neighbour is poisoned, it will cure the poison instead of healing.
|-
! heals
| unit will heal ''healer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''heal_amount''. If a neighbour is poisoned, it will prevent the poison's effect instead of healing.
|-
! illuminates
| all neighbouring hex will be "illuminated", in other words have a different time of day (See [[TimeWML]]). Typically, this will be one step brighter.
|-
! leadership
| the unit will increase the damage of all neighbouring units by +25% per level difference. (If the neighbouring unit is of a higher level, this effect is negated.)
|-
! nightstalk
| the unit becomes invisible during night.
|-
! regenerates
| the unit will heal itself 8 hp per turn. If it is poisoned, it will remove the poison instead of healing.
|-
! skirmisher
| the unit ignores zone of control when moving, but still cannot move directly through an enemy unit
|-
! steadfast
| the unit takes half normal damage when it did not initiate the attack.
|-
! teleport
| the unit can move between any two allied villages for one move point
|}

== Normal abilities {{DevFeature}} ==
{| class="gallery" style="text-align:left"
|-
! submerge
| the unit becomes invisible in deep water.
|}

== Attack specials ==
{| class="gallery" style="text-align:left"
|-
! backstab
| doubles damage whenever there is a unit on the opposite side (location) of the defending unit that distracts it. In 1.0.x the distracting unit must be on the same side (player) as the attacker. {{DevFeature}}: the distracting unit must be an enemy of the defending unit and not incapacitated (e.g. turned to stone).
|-
! berserk
| forces the combat to continue until either the attacker or the defender is killed, or until 30 rounds have passed (whichever comes first.)
|-
! charge
| when attacking, both this weapon and defender get double damage.
|-
! drain
| The controller of this weapon gains health equal to half the damage done (rounded down) whenever this attack hits.
|-
! firststrike
| when this weapon is used to defend, the battle proceeds as if it were the attacker (i.e. it attacks first).
|-
! magical
| this weapon always has a 70% chance of hitting.
|-
! marksman
| when attacking, this weapon has a minimum of 60% chance of hitting.
|-
! plague
| The controller of this weapon is copied onto the tile that any unit this attack killed was on.
|-
! poison
| when this weapon hits, the defender becomes poisoned (see [status], [[SingleUnitWML]]).
|-
! rage (x)
| forces the combat to repeat for x times
|-
! slow
| when this weapon hits, the defender becomes slowed (see [status], [[SingleUnitWML]]).
|-
! stone
| when this weapon hits, the defender turns to stone (see [status], [[SingleUnitWML]]).
|}

== See Also ==

* [[AbilitiesWMLTechnical1.1.3]]
* [[UnitWML]]
* [[SingleUnitWML]]
* [[ReferenceWML]]

AbilitiesWML

2006-07-05T01:43:09Z

Appleide: /* Attack specials */

{{WML Tags}}
== Abilities and their effects ==

There are two types of abilities: ones that apply to units (called ''abilities'') and weapon-based (called
''specials''). A unit may have multiple abilities,
but each attack can only have at most one special.

== Normal abilities (for BFW 1.0) ==
{| class="gallery" style="text-align:left"
|-
! ambush
| the unit becomes invisible on forest. Invisible units cannot be seen by enemies and do not possess zone of control, although if an enemy moves next to one, it becomes visible again.
|-
! cures
| unit will heal ''curer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''cure_amount''. If a neighbour is poisoned, it will cure the poison instead of healing.
|-
! heals
| unit will heal ''healer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''heal_amount''. If a neighbour is poisoned, it will prevent the poison's effect instead of healing.
|-
! illuminates
| all neighbouring hex will be "illuminated", in other words have a different time of day (See [[TimeWML]]). Typically, this will be one step brighter.
|-
! leadership
| the unit will increase the damage of all neighbouring units by +25% per level difference. (If the neighbouring unit is of a higher level, this effect is negated.)
|-
! nightstalk
| the unit becomes invisible during night.
|-
! regenerates
| the unit will heal itself 8 hp per turn. If it is poisoned, it will remove the poison instead of healing.
|-
! skirmisher
| the unit ignores zone of control when moving, but still cannot move directly through an enemy unit
|-
! steadfast
| the unit takes half normal damage when it did not initiate the attack.
|-
! teleport
| the unit can move between any two allied villages for one move point
|}

== Normal abilities {{DevFeature}} ==
{| class="gallery" style="text-align:left"
|-
! submerge
| the unit becomes invisible in deep water.
|}

== Attack specials ==
{| class="gallery" style="text-align:left"
|-
! backstab
| doubles damage whenever there is a unit on the opposite side (location) of the defending unit that distracts it. In 1.0.x the distracting unit must be on the same side (player) as the attacker. {{DevFeature}}: the distracting unit must be an enemy of the defending unit and not incapacitated (e.g. turned to stone).
|-
! berserk
| forces the combat to continue until either the attacker or the defender is killed, or until 30 rounds have passed (whichever comes first.)
|-
! charge
| when attacking, both this weapon and defender get double damage.
|-
! drain
| The controller of this weapon gains health equal to half the damage done (rounded down) whenever this attack hits.
|-
! firststrike
| when this weapon is used to defend, the battle proceeds as if it were the attacker (i.e. it attacks first).
|-
! magical
| this weapon always has a 70% chance of hitting.
|-
! marksman
| when attacking, this weapon has a minimum of 60% chance of hitting.
|-
! plague
| The controller of this weapon is copied onto the tile that any unit this attack killed was on.
|-
! poison
| when this weapon hits, the defender becomes poisoned (see [status], [[SingleUnitWML]]).
|-
! rage (x)
| forces the combat to repeat for x times. Version 1.17 or over only.
|-
! slow
| when this weapon hits, the defender becomes slowed (see [status], [[SingleUnitWML]]).
|-
! stone
| when this weapon hits, the defender turns to stone (see [status], [[SingleUnitWML]]).
|}

== See Also ==

* [[AbilitiesWMLTechnical1.1.3]]
* [[UnitWML]]
* [[SingleUnitWML]]
* [[ReferenceWML]]

A Shop Like Thing

2006-01-16T02:40:43Z

Appleide:

Just paste this code into your scenario:
The code inside each [option] tag are different items, their attributes can easily be changed.
In the first section of code, it defines on what coordinates on the map are the shops located. it also shows which sides can use them. You can take out any item in [options] tags and this code still works., as long as you have the beginning and the end bits.

"side=1,2,3,4
x=37,34,40,37
y=1,2,2,4"

[event]
name=moveto
first_time_only=no
[filter]
side=1,2,3,4
x=37,34,40,37
y=1,2,2,4
[/filter]
[store_gold]
side=$side_number
variable=gold
[/store_gold]
[message]
speaker=narrator
message=_ "What items would you like to purchase?"

[option]
message=_ "Sharpen Melee Weapon g:140 dmg:2"
[command]
[if]
[variable]
name=gold
greater_than=140
[/variable]
[then]
[gold]
amount=-140
side=$side_number
[/gold]
[object]
[effect]
apply_to=attack
range=short
increase_damage=2
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Enchance Ranged Weapon g:150 dmg:2"
[command]
[if]
[variable]
name=gold
greater_than=150
[/variable]
[then]
[gold]
side=$side_number
amount=-150
[/gold]
[object]
[effect]
apply_to=attack
range=long
increase_damage=2
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Magical Orb g:150 dmg:+2 Magical"
[command]
[if]
[variable]
name=gold
greater_than=150
[/variable]
[then]
[gold]
amount=-150
side=$side_number
[/gold]
[object]
[effect]
apply_to=attack
special=magical
increase_damage=2
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Toughness Increase Scroll g:250 hp:10"
[command]
[if]
[variable]
name=gold
greater_than=250
[/variable]
[then]
[gold]
amount=-250
side=$side_number
[/gold]
[object]
[effect]
apply_to=hitpoints
increase_total=10
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Flying Boots g:400 m:to 10"
[command]
[if]
[variable]
name=gold
greater_than=400
[/variable]
[then]
[gold]
amount=-400
side=$side_number
[/gold]
[object]
[effect]
apply_to=movement
set=10
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Boot Upgrade g:400 m:+1"
[command]
[if]
[variable]
name=gold
greater_than=400
[/variable]
[then]
[gold]
amount=-400
side=1
[/gold]
[object]
[effect]
apply_to=movement
increase=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Healing Fountain g:0 hp:+50"
[command]
[if]
[variable]
name=gold
greater_than=0
[/variable]
[then]
[gold]
amount=0
side=$side_number
[/gold]
[object]
[effect]
apply_to=hitpoints
increase=50
violate_max=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Rage Stone g:300 atks:+1 Melee"
[command]
[if]
[variable]
name=gold
greater_than=300
[/variable]
[then]
[gold]
amount=-300
side=$side_number
[/gold]
[object]
[effect]
apply_to=attack
range=short
increase_attacks=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Sight Stone g:350 atks:+1 ranged"
[command]
[if]
[variable]
name=gold
greater_than=350
[/variable]
[then]
[gold]
amount=-350
side=$side_number
[/gold]
[object]
[effect]
apply_to=attack
range=long
increase_attacks=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Fire Scepter g:350 atks:8-1 ranged magical fire"
[command]
[if]
[variable]
name=gold
greater_than=350
[/variable]
[then]
[gold]
amount=-350
side=$side_number
[/gold]
[object]
[effect]
apply_to=new_attack
name=Fire Scepter
type=fire
special=magical
range=long
damage=8
number=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Ice Scepter g:350 atks:8-1 ranged magical Ice"
[command]
[if]
[variable]
name=gold
greater_than=350
[/variable]
[then]
[gold]
amount=-350
side=$side_number
[/gold]
[object]
[effect]
apply_to=new_attack
name=Ice Scepter
type=cold
special=magical
range=long
damage=8
number=1
[/effect]
[/object] [/then]
[/if]
[/command]
[/option]
##########################closing tags
[/message]
[/event]

A Shop Like Thing

2006-01-16T02:38:22Z

Appleide:

Just paste this code into your scenario:
The code inside each [option] tag are different items, their attributes can easily be changed.
In the first section of code, it defines on what coordinates on the map are the shops located. it also shows which sides can use them.

"side=1,2,3,4
x=37,34,40,37
y=1,2,2,4"

[event]
name=moveto
first_time_only=no
[filter]
side=1,2,3,4
x=37,34,40,37
y=1,2,2,4
[/filter]
[store_gold]
side=$side_number
variable=gold
[/store_gold]
[message]
speaker=narrator
message=_ "What items would you like to purchase?"

[option]
message=_ "Sharpen Melee Weapon g:140 dmg:2"
[command]
[if]
[variable]
name=gold
greater_than=140
[/variable]
[then]
[gold]
amount=-140
side=$side_number
[/gold]
[object]
[effect]
apply_to=attack
range=short
increase_damage=2
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Enchance Ranged Weapon g:150 dmg:2"
[command]
[if]
[variable]
name=gold
greater_than=150
[/variable]
[then]
[gold]
side=$side_number
amount=-150
[/gold]
[object]
[effect]
apply_to=attack
range=long
increase_damage=2
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Magical Orb g:150 dmg:+2 Magical"
[command]
[if]
[variable]
name=gold
greater_than=150
[/variable]
[then]
[gold]
amount=-150
side=$side_number
[/gold]
[object]
[effect]
apply_to=attack
special=magical
increase_damage=2
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Toughness Increase Scroll g:250 hp:10"
[command]
[if]
[variable]
name=gold
greater_than=250
[/variable]
[then]
[gold]
amount=-250
side=$side_number
[/gold]
[object]
[effect]
apply_to=hitpoints
increase_total=10
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Flying Boots g:400 m:to 10"
[command]
[if]
[variable]
name=gold
greater_than=400
[/variable]
[then]
[gold]
amount=-400
side=$side_number
[/gold]
[object]
[effect]
apply_to=movement
set=10
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Boot Upgrade g:400 m:+1"
[command]
[if]
[variable]
name=gold
greater_than=400
[/variable]
[then]
[gold]
amount=-400
side=1
[/gold]
[object]
[effect]
apply_to=movement
increase=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Healing Fountain g:0 hp:+50"
[command]
[if]
[variable]
name=gold
greater_than=0
[/variable]
[then]
[gold]
amount=0
side=$side_number
[/gold]
[object]
[effect]
apply_to=hitpoints
increase=50
violate_max=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Rage Stone g:300 atks:+1 Melee"
[command]
[if]
[variable]
name=gold
greater_than=300
[/variable]
[then]
[gold]
amount=-300
side=$side_number
[/gold]
[object]
[effect]
apply_to=attack
range=short
increase_attacks=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Sight Stone g:350 atks:+1 ranged"
[command]
[if]
[variable]
name=gold
greater_than=350
[/variable]
[then]
[gold]
amount=-350
side=$side_number
[/gold]
[object]
[effect]
apply_to=attack
range=long
increase_attacks=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Fire Scepter g:350 atks:8-1 ranged magical fire"
[command]
[if]
[variable]
name=gold
greater_than=350
[/variable]
[then]
[gold]
amount=-350
side=$side_number
[/gold]
[object]
[effect]
apply_to=new_attack
name=Fire Scepter
type=fire
special=magical
range=long
damage=8
number=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

[option]
message=_ "Ice Scepter g:350 atks:8-1 ranged magical Ice"
[command]
[if]
[variable]
name=gold
greater_than=350
[/variable]
[then]
[gold]
amount=-350
side=$side_number
[/gold]
[object]
[effect]
apply_to=new_attack
name=Ice Scepter
type=cold
special=magical
range=long
damage=8
number=1
[/effect]
[/object] [/then]
[/if]
[/command]
[/option]
[/message]
[/event]

UsefulWMLFragments

2006-01-16T02:11:01Z

Appleide: /* Useful WML Fragments */

== Useful WML Fragments ==

[[WmlTemplates]]: Campaign, scenario and unit templates, for the lazy ;)

Currently, these are all macros (see [[PreprocessorRef]])
that may be copied into a scenario file or another file included first by the campaign,
and then used in the scenario (or multiplayer map).
Remember that a macro cannot be used at a point before it is defined.

[[ProgrammingMacros]]: Definitions for some low-level macros to make it easier to write program-like WML.

[[WmlMacros]]: Simple functions such as store/unstore, variable formatting, item triggers.

[[Hardcore WML]]: Ways of accomplishing some unusual things with WML.

[[WishingWell]]: Hero(es) can get boosts for traits at a wishing well.

[[DroppableItem]]: A macro to create items that units can carry, that are left on the ground when those units die.

[[RandomTraitUnit]]: A series of macros to create a unit with two random traits.

[[PseudoRandom]]: A replacement for {RANDOM} in multiplayer, where {RANDOM} is buggy.

[[MoveExistingUnit]]: A general way to move a unit from one place to another, displaying its movement.

[[BranchOnVillageType]]: Crude hack for branching on village type.

[[Rain effect]]: Creating an overlay of rain in a scenario.

[[Victory Conditions]]: Macros for different kinds of victory conditions, for example victory by controlling x% of villages on the map. Also suitable for multiplayer scenarios.

[[A Shop Like Thing]]: How to add even more RPG elements to your scenarios.

== See Also ==

* [[ReferenceWML]]