The Battle for Wesnoth Wiki - User contributions [en]

UsefulWMLFragments

2007-04-09T14:54:51Z

Henkutsu: /* Useful WML Fragments */

== Useful WML Fragments ==

NOTES ABOUT ADDING PAGES: try not to add new pages here. Find a category in which your code fits and add it to that page.

Most of the things found here are macros (see [[PreprocessorRef]]) that must 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.

For a step by step instruction, look here: [[HowTo: IncludeMacros]] and then here: [[HowTo: UseMacros]]

High level macros often require the lower level macros found in ProgrammingMacros, Utilities, and Scenario Tools.

=== Logic Structure Macros ===
*[[ProgrammingMacros]]: Definitions for some low-level macros to make it easier to write program-like WML.
*[[WML Utilities]]: Macros to assist other macros. Test Value of Variable. If Have Unit. Store Unit Attribute. Filter by Terrain. Iterate. Overlay with Filter. Determine Opposite Coordinates.

=== Campaign Tools ===
*[[WML Scenario Tools]]: Macros directly useful in a scenario. Modify unit. Give villages to a side. Return Unit to Recall List. Trap Unit. Change Keep Terrain. Hero die message. Item effect.
*[[WML Dialog Tools]]: Macros useful for unit dialog/storyboarding. Character Speaker, Blank story section, Delays and Fades.
*[[Victory Conditions]]: Number of Villages, Amount of Gold. Suitable for multiplayer scenarios.

==== Map Tools ====
*[[A Shop Like Thing]]: How to add even more RPG elements to your scenarios.
*[[Rain effect]]: Creating an overlay of rain in a scenario. (old)
*[[Map Modification WML]] Tools for editing the terrain in creative ways

==== Unit Tools ====
*[[MoveExistingUnit]]: Move a unit from one place to another, displaying its movement. Move Unit 1. Move Unit 2. Move Unit 3.
*[[WML Abilities]]: Knockback. Charm. Bloodlust. Abilities cannot currently be incorporated in the unit type definitions themselves, but must be included in the scenario file.
*[[WML Buildings]]: Generic Buildings, Light House/Dark Tower, Wishing Well #1, Wishing Well #2.
*[[RandomTraitUnit]]: Create a unit with two random traits. (very simple.) (updated)

==== Item Tools ====
*[[DroppableItem]]: Macros to drop items. Currently only macros for dropping items on unit death including a permenant item that can be picked up, and dropped, multiple times by different units.
*[[General Item WML]]

=== Multiplayer Tools ===
*[[PseudoRandom]]: A replacement for {RANDOM} in multiplayer, where {RANDOM} is buggy.
*[[General Multiplayer WML]]

=== Advanced WML ===
*[[Advanced WML]]: Branch on Village Type. Recruit from a Ship. Point Rotation Scheme.

=== Templates ===
*[[WML Templates]]: Generic campaign, scenario and unit templates. (updated)

== See Also ==

* [[ReferenceWML]]

[[Category: UsefulWMLFragments]]

User:Henkutsu

2007-04-09T14:50:20Z

Henkutsu:

Ok, still need to do more work on [[UsefulWMLFragments]].

Have updated most of the pages but still need to do:
* Category: UsefulWMLFragments
* Category: ObseleteWMLFragments
* [[HowTo: IncludeMacros]]
* [[HowTo: UseMacros]]
* Category: HowTo

Already fixed a few of the wrong links in the side bar... hmm. Back to my campaign!

User:Henkutsu

2007-04-09T14:49:41Z

Henkutsu:

Ok, still need to do more work on [[UsefulWMLFragments]].

Have updated most of the pages but still need to do:
*[[Category: UsefulWMLFragments]]
*[[Category: ObseleteWMLFragments]]
*[[HowTo: IncludeMacros]]
*[[HowTo: UseMacros]]
*[[Category: HowTo]]

Already fixed a few of the wrong links in the side bar... hmm. Back to my campaign!

A Shop Like Thing

2007-04-09T14:27:43Z

Henkutsu: Changed structure of page. Added comments and updated code where I could. Added see also. Kept links but it should all make sense now.

Please note that this code is a bit out of date. All references to "range" should be "melee" or "ranged" now instead of "short" and "long" (Have been fixed now). There may be other parts that are out of date, particularily in regards to adding specials. Check [[ReferenceWML]] on the tags just to check :) Happy coding.

== A Shop Like Thing ==

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?"

=== Melee damage increase ===
[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=melee
increase_damage=2
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

=== Ranged damage increase ===
[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=ranged
increase_damage=2
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

=== Extra damage and magical enhancement ===
(May be partially out of date)
[option]
message=_ "Crystal 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]

=== Increase maximum HP ===
[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]

=== Set Movement to 10 ===
[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]

=== Add Extra Movement ===
[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]

=== Heal damage ===
(May be partially out of date)
[option]
message=_ "Healing Fountain g:All 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]

=== Extra Melee attack ===
[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=melee
increase_attacks=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

=== Extra ranged attack ===
[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=ranged
increase_attacks=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

=== Add a weapon ===
(May be partially out of date)
[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=ranged
damage=8
number=1
[/effect]
[/object]
[/then]
[/if]
[/command]
[/option]

=== Add a weapon ===
(May be partially out of date)
[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]

== See Also ==
* [[UsefulWMLFragments]]
* [[ReferenceWML]]

[[Category: UsefulWMLFragments]]

UsefulWMLFragments

2007-04-09T14:14:12Z

Henkutsu:

== Useful WML Fragments ==

NOTES ABOUT ADDING PAGES: Don't add new pages here. Find a category in which your code fits and add it to that page.

Most of the things found here are macros (see [[PreprocessorRef]]) that must 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.

For a step by step instruction, look here: [[HowTo: IncludeMacros]] and then here: [[HowTo: UseMacros]]

High level macros often require the lower level macros found in ProgrammingMacros, Utilities, and Scenario Tools.

=== Logic Structure Macros ===
*[[ProgrammingMacros]]: Definitions for some low-level macros to make it easier to write program-like WML.
*[[WML Utilities]]: Macros to assist other macros. Test Value of Variable. If Have Unit. Store Unit Attribute. Filter by Terrain. Iterate. Overlay with Filter. Determine Opposite Coordinates.

=== Campaign Tools ===
*[[WML Scenario Tools]]: Macros directly useful in a scenario. Modify unit. Give villages to a side. Return Unit to Recall List. Trap Unit. Change Keep Terrain. Hero die message. Item effect.
*[[WML Dialog Tools]]: Macros useful for unit dialog/storyboarding. Character Speaker, Blank story section, Delays and Fades.
*[[Victory Conditions]]: Number of Villages, Amount of Gold. Suitable for multiplayer scenarios.

==== Map Tools ====
*[[A Shop Like Thing]]: How to add even more RPG elements to your scenarios.
*[[Rain effect]]: Creating an overlay of rain in a scenario.

==== Unit Tools ====
*[[MoveExistingUnit]]: Move a unit from one place to another, displaying its movement. Move Unit 1. Move Unit 2. Move Unit 3.
*[[WML Abilities]]: Knockback. Charm. Bloodlust. Abilities cannot currently be incorporated in the unit type definitions themselves, but must be included in the scenario file.
*[[WML Buildings]]: Generic Buildings, Light House/Dark Tower, Wishing Well #1, Wishing Well #2.
*[[RandomTraitUnit]]: Create a unit with two random traits. (very simple.) (updated)

==== Item Tools ====
*[[DroppableItem]]: Macros to drop items. Currently only macros for dropping items on unit death including a permenant item that can be picked up, and dropped, multiple times by different units.

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

=== Advanced WML ===
*[[Advanced WML]]: Branch on Village Type. Recruit from a Ship. Point Rotation Scheme.

=== Templates ===
*[[WML Templates]]: Generic campaign, scenario and unit templates. (updated)

== See Also ==

* [[ReferenceWML]]

[[Category: UsefulWMLFragments]]

DroppableItem

2007-04-09T14:12:23Z

Henkutsu: MAJOR CHANGE! Changed structure of page completely. Added comments and instructions to help newbies. Added sections. Kept links but it should all make sense now.

This page is for code fragments for dropping items.

== Droppable on Death ==

This section is for macros that drop an item due to the death of unit.

=== Dropping a picked up item ===

This macro comes in two parts with space for [effect] code between them. Using this macro creates an item at a point on the map specified by X and Y, keeps track of it (when the unit carrying it dies) via two variable (which the user names!!) and provides an image for the map.

Note that if you want any unit to be able to pick up the item you can ignore the ADDITIONAL_FILTERS part.
==== Part One ====
#define DROPPABLE_ITEM X Y XVAR YVAR NAME IMAGE ADDITIONAL_FILTERS
[label]
x={X}
y={Y}
text="{NAME}"
[/label]
[event]
name=prestart
{VARIABLE {XVAR} {X}}
{VARIABLE {YVAR} {Y}}

[item]
x=${XVAR}
y=${YVAR}
image={IMAGE}
[/item]

[event]
name=die
first_time_only=no
[store_unit]
[filter]
x=$x1
y=$y1
[/filter]
variable=itemstore
[/store_unit]
[if]
[variable]
name=itemstore.variables.{XVAR}
equals=on
[/variable]
[then]
{VARIABLE_OP {XVAR} to_variable x1}
{VARIABLE_OP {YVAR} to_variable y1}
[item]
x=$x1
y=$y1
image={IMAGE}
[/item]
[/then]
[/if]
[/event]

[event]
name=moveto
first_time_only=no
[filter]
x=${XVAR}
y=${YVAR}
{ADDITIONAL_FILTERS}
[/filter]

[removeitem]
x=${XVAR}
y=${YVAR}
[/removeitem]
[store_unit]
variable=itemstore
[filter]
x=${XVAR}
y=${YVAR}
[/filter]
[/store_unit]
{VARIABLE itemstore.variables.{XVAR} on}
[unstore_unit]
variable=itemstore
[/unstore_unit]

[unit_overlay]
x=${XVAR}
y=${YVAR}
image={IMAGE}
[/unit_overlay]

[object]
name={NAME}
image={IMAGE}
duration=forever
cannot_use_message="-cannot use message-"
[filter]
x=${XVAR}
y=${YVAR}
[/filter]
#enddef

==== Effect goes here ====

Of course the code for the macro above will do nothing without an [effect] attatched to the item (via the [object] tag in the above macro) other than cart an image around. To add an effect, make an [effect] tag as below (or look at [[EffectWML]]:

#All this should be between the usage of the DROPPABLE_ITEM macro and its /DROPPABLE_ITEM
#
# This is not the only thing you can do but for an item that increases movementspeed by 10(!) do:
[effect]
apply_to=movement
increase=10
[/effect]

==== Part 2 ====
Once you have done all of the above, call the closing macro to close all the tags and clear the variables.

#define /DROPPABLE_ITEM XVAR YVAR
[/object]

{VARIABLE {XVAR} 0}
{VARIABLE {YVAR} 0}
[/event]
[/event]
#enddef

=== Dropping Loot ===
This macro makes it so that when a unit matching a filter dies, it will drop an item (eg gold!)

#Re writing... come back later.

== See Also ==

* [[UsefulWMLFragments]]
* [[ReferenceWML]]

[[Category: UsefulWMLFragments]]

Template:WML Tags

2007-04-09T14:06:42Z

Henkutsu: changed effect to link to EffectWML instead of UnitWML

{| class="gallery" style="width:175px;float: right;border: 1px solid #B48648; color:#B48648; font-size: 7pt;margin-left;10px;"
|-
|
[{{SERVER}}{{localurl:Template:WML Tags|action=edit}} edit ]
'''WML Tags'''

|-
|''A:''
[[AbilitiesWMLTechnical1.1.3|abilities]],
[[CampaignWML#The_.5Babout.5D_tag|about]],
[[UnitWML|advancefrom]],
[[UnitWML|advancement]],
[[StatisticalScenarioWML|advances]],
[[AiWML|ai]],
[[DirectActionsWML|allow_recruit]],
[[VariablesWML|array]],
[[AttackWML|attack]],
[[StatisticalScenarioWML|attacks]],
[[AiWML|avoid]];
|-
|''B:''
[[CampaignWML#The_.5Bbinary_path.5D_tag|binary_path]],[[HelpWML|bold]];
|-
|''C:''
[[CampaignWML#The_.5Bcampaign.5D_tag|campaign]], [[DirectActionsWML|capture_village]], [[ReplayWML|choose]],
[[InternalActionsWML|clear_variable]],
[[InterfaceActionsWML|colour_adjust]],
[[ReplayWML|command]];
|-
|''D:''
[[StatisticalScenarioWML|deaths]],[[UnitWML|defend]],[[StatisticalScenarioWML|defends]],
[[UnitWML|defense]],
[[InterfaceActionsWML|delay]],
[[ReplayWML|destination]],
[[DirectActionsWML|disallow_recruit]],
[[InternalActionsWML|do]];
|-
|''E:''
[[EffectWML|effect]],[[InternalActionsWML|else]],[[ReplayWML|end_turn]],
[[DirectActionsWML|endlevel]],
[[EraWML|era]],
[[EventWML|event]],
[[ThemeWML|expenses]];
|-
|''F:''
[[FilterWML|filter]], [[FilterWML|filter_second]], [[HelpWML|format]], [[AttackWML|frame]];
|-
|''G:''
[[GameConfigWML|game_config]], [[ScenarioWML|generator]], [[DirectActionsWML|gold]], [[ThemeWML|gold]];
|-
|''H:''
[[InternalActionsWML|have_unit]], [[HelpWML|header]], [[InterfaceActionsWML|hide_unit]];
|-
|''I:''
[[InternalActionsWML|if]], [[TimeWML|illuminated_time]], [[TerrainGraphicsWML|image]],
[[HelpWML|img]], [[ThemeWML|income]], [[HelpWML|italic]], [[InterfaceActionsWML|item]];
|-
|''J:''
[[HelpWML|jump]];
|-
|''K:''
[[DirectActionsWML|kill]], [[StatisticalScenarioWML|killed]];
|-
|''L:''
[[LabelWML|label]] ([[InterfaceActionsWML|map]], [[ThemeWML|theme]]), [[LanguageWML|language]], [[AiWML|leader_goal]];
|-
|''M:''
[[ThemeWML|main_map]],[[ThemeWML|menu]], [[InterfaceActionsWML|message]], [[ThemeWML|mini_map]],
[[AttackWML|missile_frame]], [[SingleUnitWML|modifications]], [[DirectActionsWML|modify_side]],
[[DirectActionsWML|modify_turns]], [[ReplayWML|move]], [[InterfaceActionsWML|move_unit_fake]], [[UnitWML|movement costs]],
[[UnitsWML|movetype]], [[ScenarioWML|multiplayer]], [[EraWML|multiplayer_side]], [[InterfaceActionsWML|music]];
|-
|''N:''
[[FilterWML|not]], [[ThemeWML|num_units]];
|-
|''O:''
[[DirectActionsWML|object]], [[InterfaceActionsWML|objectives]], [[InterfaceActionsWML|objective]],
[[ThemeWML|observers]], [[InterfaceActionsWML|option]], [[InternalActionsWML|or]];
|-
|''P:''
[[ThemeWML|panel]], [[IntroWML|part]], [[DirectActionsWML|place_shroud]], [[ThemeWML|position]],
[[InterfaceActionsWML|print]], [[AiWML|protect_location]], [[AiWML|protect_unit]];
|-
|''R:''
[[UnitsWML|race]], [[ReplayWML|random]], [[ReplayWML|recall]], [[StatisticalScenarioWML|recalls]],
[[ReplayWML|recruit]], [[StatisticalScenarioWML|recruits]], [[InterfaceActionsWML|redraw]],
[[HelpWML|ref]], [[DirectActionsWML|remove_shroud]], [[InterfaceActionsWML|remove_unit_overlay]],
[[InterfaceActionsWML|removeitem]], [[SavefileWML|replay]], [[SavefileWML|replay_start]],
[[UnitWML|resistance]], [[ThemeWML|resolution]], [[ReplayWML|results]], [[InternalActionsWML|role]];
|-
|''S:''
[[SavefileWML|save]], [[ScenarioWML|scenario]],
[[InterfaceActionsWML|scroll]], [[InterfaceActionsWML|scroll_to]],
[[InterfaceActionsWML|scroll_to_unit]], [[HelpWML|section]],
[[InterfaceActionsWML#.5Bset_menu_item.5D_.28SVN_trunk_only.29|set_menu_item]], [[DirectActionsWML|set_recruit]],
[[InternalActionsWML|set_variable]], [[SideWML|side]], [[ThemeWML|side_playing]], [[SavefileWML|snapshot]],
[[InterfaceActionsWML|sound]], [[ReplayWML|source]], [[AbilitiesWMLTechnical1.1.3|specials]]
[[StatisticalScenarioWML#The_.5Bstatistics.5D_tag|statistics]],
[[ThemeWML|status]], [[DirectActionsWML|stone]], [[InternalActionsWML|store_gold]], [[InternalActionsWML|store_locations]],
[[InternalActionsWML|store_starting_location]], [[InternalActionsWML|store_unit]], [[IntroWML|story]];
|-
|''T:''
[[AiWML|target]],
[[StatisticalScenarioWML#The_.5Bteam.5D_tag|team]],
[[DirectActionsWML|teleport]], [[UnitWML|teleport_anim]],
[[TerrainWML|terrain]], [[DirectActionsWML|terrain]], [[TerrainGraphicsWML|terrain_graphics]], [[ScenarioWML#Test_scenario|test]],
[[CampaignWML#The_.5Btextdomain.5D_tag|textdomain]], [[ThemeWML|theme]], [[InternalActionsWML|then]],
[[TerrainGraphicsWML|tile]], [[TimeWML|time]], [[ScenarioWML|time_area]], [[ThemeWML|time_of_day]],
[[HelpWML|topic]], [[HelpWML|toplevel]], [[SingleUnitWML|trait]], [[ThemeWML|turn]], [[ScenarioWML|tutorial]];
|-
|''U:''
[[InterfaceActionsWML|unhide_unit]], unit ([[UnitWML|define]], [[SingleUnitWML|create]]),
[[ThemeWML|unit_abilities]], [[ThemeWML|unit_alignment]], [[ThemeWML|unit_description]],
[[ThemeWML|unit_hp]], [[ThemeWML|unit_image]], [[ThemeWML|unit_level]], [[ThemeWML|unit_moves]],
[[InterfaceActionsWML|unit_overlay]], [[ThemeWML|unit_profile]], [[ThemeWML|unit_status]],
[[ThemeWML|unit_traits]], [[ThemeWML|unit_type]], [[ThemeWML|unit_weapons]], [[ThemeWML|unit_xp]],
[[UnitsWML|units]], [[DirectActionsWML|unstone]], [[DirectActionsWML|unstore_unit]], [[ThemeWML|upkeep]];
|-
| ''V:''
[[InternalActionsWML|variable]], [[VariablesWML|variables]], [[SideWML|village]], [[ThemeWML|villages]];
|-
| ''W:''
[[InternalActionsWML|while]]
|}

UsefulWMLFragments

2007-04-09T13:40:18Z

Henkutsu: MAJOR CHANGE! Changed structure of page completely. Kept links but it should all make sense now.

== Useful WML Fragments ==

NOTES ABOUT ADDING PAGES: Don't add new pages here. Find a category in which your code fits and add it to that page.

Most of the things found here are macros (see [[PreprocessorRef]]) that must 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.

For a step by step instruction, look here: [[HowTo: IncludeMacros]] and then here: [[HowTo: UseMacros]]

High level macros often require the lower level macros found in ProgrammingMacros, Utilities, and Scenario Tools.

=== Logic Structure Macros ===
*[[ProgrammingMacros]]: Definitions for some low-level macros to make it easier to write program-like WML.
*[[WML Utilities]]: Macros to assist other macros. Test Value of Variable. If Have Unit. Store Unit Attribute. Filter by Terrain. Iterate. Overlay with Filter. Determine Opposite Coordinates.

=== Campaign Tools ===
*[[WML Scenario Tools]]: Macros directly useful in a scenario. Modify unit. Give villages to a side. Return Unit to Recall List. Trap Unit. Change Keep Terrain. Hero die message. Item effect.
*[[WML Dialog Tools]]: Macros useful for unit dialog/storyboarding. Character Speaker, Blank story section, Delays and Fades.
*[[Victory Conditions]]: Number of Villages, Amount of Gold. Suitable for multiplayer scenarios.

==== Map Tools ====
*[[A Shop Like Thing]]: How to add even more RPG elements to your scenarios.
*[[Rain effect]]: Creating an overlay of rain in a scenario.

==== Unit Tools ====
*[[MoveExistingUnit]]: Move a unit from one place to another, displaying its movement. Move Unit 1. Move Unit 2. Move Unit 3.
*[[WML Abilities]]: Knockback. Charm. Bloodlust. Abilities cannot currently be incorporated in the unit type definitions themselves, but must be included in the scenario file.
*[[WML Buildings]]: Generic Buildings, Light House/Dark Tower, Wishing Well #1, Wishing Well #2.
*[[RandomTraitUnit]]: Create a unit with two random traits. (very simple.) (updated)

==== Item Tools ====
*[[DroppableItem]]: Generic item that a unit can carry, and is left on the ground when the unit dies.

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

=== Advanced WML ===
*[[Advanced WML]]: Branch on Village Type. Recruit from a Ship. Point Rotation Scheme.

=== Templates ===
*[[WML Templates]]: Generic campaign, scenario and unit templates. (updated)

== See Also ==

* [[ReferenceWML]]

[[Category: UsefulWMLFragments]]

UsefulWMLFragments

2007-04-09T13:21:40Z

Henkutsu:

== Useful WML Fragments ==

Most of the things found here are macros (see [[PreprocessorRef]]) that must 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.

High level macros often require the lower level macros found in ProgrammingMacros, Utilities, and Scenario Tools.

[[WML Templates]]: Generic campaign, scenario and unit templates.

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

[[WML Utilities]]: Macros to assist other macros. Test Value of Variable. If Have Unit. Store Unit Attribute. Filter by Terrain. Iterate. Overlay with Filter. Determine Opposite Coordinates.

[[WML Scenario Tools]]: Macros directly useful in a scenario. Modify unit. Give villages to a side. Return Unit to Recall List. Trap Unit. Change Keep Terrain. Hero die message. Item effect.

[[WML Dialog Tools]]: Macros useful for unit dialog/storyboarding. Character Speaker, Blank story section, Delays and Fades.

[[MoveExistingUnit]]: Move a unit from one place to another, displaying its movement. Move Unit 1. Move Unit 2. Move Unit 3.

[[Victory Conditions]]: Number of Villages, Amount of Gold. Suitable for multiplayer scenarios.

[[WML Abilities]]: Knockback. Charm. Bloodlust. Abilities cannot currently be incorporated in the unit type definitions themselves, but must be included in the scenario file.

[[WML Buildings]]: Generic Buildings, Light House/Dark Tower, Wishing Well #1, Wishing Well #2.

[[RandomTraitUnit]]: Create a unit with two random traits. (very simple.)

[[DroppableItem]]: Generic item that a unit can carry, and is left on the ground when the unit dies.

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

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

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

[[Advanced WML]]: Branch on Village Type. Recruit from a Ship. Point Rotation Scheme.

== See Also ==

* [[ReferenceWML]]

[[Category: UsefulWMLFragments]]

Talk:UsefulWMLFragments

2007-04-09T13:20:08Z

Henkutsu:

I'm thinking that it would be good to have all pages linked also link back. It would also be good to add this page to the Category: WML, opinions? /tsr

Henkutsu: That is my thoughts too. Also several of the pages are badly outdated. After getting so many errors in my scenarios from old code, I'm now going through the whole thing cleaning it up. I'm adding the links and may move bits to different pages.
An example of the old code is the Random Traits stuff.

Talk:RandomTraitUnit

2007-04-09T13:17:21Z

Henkutsu:

Um. Just changed the whole thing...

Hope no one minded.

WML Abilities

2007-04-09T12:58:21Z

Henkutsu: Added a See Also section to the bottom to make navigation easier

Remember that you must include the WML ability code in every scenario where you intend them to work. Or include them in the unit file inside the [unit] tag.

Abilities require macros found elsewhere in UsefulFragments, typically ProgammingMacros, [[WML_Utilities|Utilities]], or Scenario Tools.

=== Knockback ===

When a unit is hit with a ''knockback'' attack, it is immediately pushed one hex away from the attacker, at which point the combat ends. Exception: units in villages can't be knocked out of them.

Examples that give ''knockback'' for every Drake Glider on their slam attack, and for the Shock Trooper named Jane:
{KNOCKBACK (type=Drake Glider) slam}
{KNOCKBACK description=Jane mace}

Requires the macros ''OPPOSITE_SIDE'', ''IF'', ''IF_HAVE_UNIT'' and ''STORE_UNIT_VAR''.

#define KNOCKBACK FILTER WEAPON
[event]
name=attacker_hits
first_time_only=no

[filter]
{FILTER}
[/filter]

[special_filter]
weapon={WEAPON}
[/special_filter]

[sound]
name=ghoul-hit.wav
[/sound]

{OPPOSITE_SIDE $x2 $y2 $x1 $y1 target_hex}

[store_locations]
x,y=$x2,$y2
terrain=AaBbDeLptUVvYZ
variable=defender_in_village
[/store_locations]

{IF_HAVE_UNIT x,y=$target_hex.x,$target_hex.y (
[else]
{IF defender_in_village.length not_equals 1 (
[then]
{STORE_UNIT_VAR x,y=$x2,$y2 side side_of_defender}

[teleport]
[filter]
x,y=$x2,$y2
[/filter]

x,y=$target_hex.x,$target_hex.y
[/teleport]

[capture_village]
side=$side_of_defender
x,y=$target_hex.x,$target_hex.y
[/capture_village]

{CLEAR_VARIABLE side_of_defender}
[/then]
)}
[/else]
)}

{CLEAR_VARIABLE target_hex}
{CLEAR_VARIABLE defender_in_village}
[/event]
#enddef

=== Charm ===

When a unit is hit with a ''charm'' attack, it instantly jumps to the attacker's side, and returns to it's original side at the beginning of that side's turn. A charmed unit has 1 movement point and can attack.

Example that makes all Troll Whelps have charm on their attack:

{CHARM (type=Troll Whelp) fist}

Requires the macros ''IF'', ''STORE_UNIT_VAR'' and ''MODIFY_UNIT''.

#define CHARM FILTER WEAPON
[event]
name=attacker_hits
first_time_only=no

[filter]
{FILTER}
[/filter]

[special_filter]
weapon={WEAPON}
[/special_filter]

{STORE_UNIT_VAR x,y=$x1,$y1 side charmer_side}
{STORE_UNIT_VAR x,y=$x2,$y2 side charmed_side}

{IF charmer_side not_equals $charmed_side (
[then]
{MODIFY_UNIT x,y=$x2,$y2 variables.real_side $charmed_side}
{MODIFY_UNIT x,y=$x2,$y2 side $charmer_side}
{MODIFY_UNIT x,y=$x2,$y2 moves 1}
{MODIFY_UNIT x,y=$x2,$y2 attacks_left 1}

{VARIABLE_OP varname format "side_$charmed_side|_units_charmed"}
{VARIABLE $varname yes}

{CLEAR_VARIABLE varname}
[/then]
)}

{CLEAR_VARIABLE charmer_side}
{CLEAR_VARIABLE charmed_side}
[/event]

[event]
name=side turn
first_time_only=no

{VARIABLE_OP this_side_charmed to_variable "side_$side_number|_units_charmed"}

{IF this_side_charmed equals yes (
[then]
[store_unit]
[filter]
[not]
side=$side_number
[/not]
[/filter]

variable=possibly_charmed
kill=no
[/store_unit]

{FOREACH possibly_charmed i}
{VARIABLE_OP real_side format "0$possibly_charmed[$i].variables.real_side"}

{IF real_side not_equals "0" (
[then]
{IF side_number equals $possibly_charmed[$i].variables.real_side (
[then]
{CLEAR_VARIABLE possibly_charmed[$i].variables.real_side}
{VARIABLE possibly_charmed[$i].side $side_number}

[unstore_unit]
variable=possibly_charmed[$i]
find_vacant=no
[/unstore_unit]
[/then]
)}
[/then]
)}
{NEXT i}

{CLEAR_VARIABLE possibly_charmed}
[/then]
)}
[/event]
#enddef

=== Bloodlust ===

Bloodlust is a very simple ability. If a unit that has bloodlust kills an enemy unit when attacking, it may attack again, provided that there are more enemy units adjacent to it.

Requires the macro MODIFY_UNIT.

This would give the bloodlust ability to all Dwarvish Ulfserkers (making them insanely powerful):

{BLOODLUST (type=Dwarvish Ulfserker)}

#define BLOODLUST FILTER
[event]
name=die
first_time_only=no

[filter_second]
{FILTER}
[/filter_second]

{MODIFY_UNIT x,y=$x2,$y2 moves 0}
{MODIFY_UNIT x,y=$x2,$y2 attacks_left 1}
[/event]
#enddef

=== Pickpocket ===

This special could also be called loot. When a unit with this attack special sucessfully hits an enemy unit, it gains a certain amount of gold - say 10.

To do this, use this code:

#define WEAPON_SPECIAL_PICKPOCKET
[damage]
id=pickpocket
name="Pickpocket"
description="Pickpocket:
When used offensively, this attack gives 10 gold to the attacker on every successful hit."
multiply=1
[/damage]
#enddef

Then put this event in your scenario:

[event]
name=attacker_hits
first_time_only=no
[filter]
side=$side_number
canrecruit=1
[/filter]
[special_filter]
weapon=pickpocket gloves
[/special_filter]
[gold]
side=$side_number
amount=10
[/gold]
[/event]

Then give the unit you want to have the "pickpocket" special something like this:

[object]
silent=yes
[effect]
apply_to=new_attack
name=pickpocket gloves
type=impact
range=melee
damage=3
number=3
[specials]
{WEAPON_SPECIAL_PICKPOCKET}
[/specials]
[/effect]
[/object]

== See Also ==

* [[UsefulWMLFragments]]
* [[WML Dialog Tools]]
* [[ReferenceWML]]

[[Category: UsefulWMLFragments]]

WML Utilities

2007-04-09T12:51:23Z

Henkutsu: Added to UsefullWMLFragments catagory

== Test Value of Variables ==

# Shortcut for IF statements testing the value of a variable. You still need to
# write [then] and [else] tags manually, though.
#
# You can use it like this:
#
# {IF some_variable equals yes (
# [then]
# # something
# [/then]
#
# [else]
# # something else
# [/else]
# )} 
#define IF VAR OP VAL CONTENTS
[if]
[variable]
name={VAR}
{OP}={VAL}
[/variable] 
{CONTENTS}
[/if]
#enddef

# Just a variation of the above, testing [have_unit] instead of [variable]. 
#define IF_HAVE_UNIT FILTER CONTENTS
[if]
[have_unit]
{FILTER}
[/have_unit] 
{CONTENTS}
[/if]
#enddef

== Store Attribute to Variable ==

# Example that flips all orcs to whatever side James is on:
#
# {STORE_UNIT_VAR description=James side side_of_James}
# {MODIFY_UNIT race=orc side $side_of_James} 
#define STORE_UNIT_VAR FILTER VAR TO_VAR
[store_unit]
[filter]
{FILTER}
[/filter] 
kill=no
variable=STORE_UNIT_VAR_store
[/store_unit] 
{VARIABLE_OP {TO_VAR} format $STORE_UNIT_VAR_store.{VAR}} 
{CLEAR_VARIABLE STORE_UNIT_VAR_store}
#enddef

== Filter by Terrain ==
# Check whethers or not the terrain in the given coordinates is of the given
# type or types. Filtering by terrain isn't possible directly.
#
# You can use it for example like this:
#
# [event]
# name=moveto
# first_time_only=no
#
# {IF_TERRAIN $x1 $y1 gfm (
# [then]
# {DEBUG_MSG "Stepped on grassland, forest or mountains!"}
# [/then]
# )}
# [/event] 
#define IF_TERRAIN X Y TYPES CONTENTS
[store_locations]
x={X}
y={Y}
terrain={TYPES}
variable=IF_TERRAIN_temp
[/store_locations] 
[if]
[variable]
name=IF_TERRAIN_temp.length
not_equals=0
[/variable] 
{CONTENTS}
[/if] 
{CLEAR_VARIABLE IF_TERRAIN_temp}
#enddef

==Iterate==
# You can iterate through a range of numbers with this macro. The CONTENTS
# are repeated with every iteration, and you can use the VAR variable to
# insert the number of the current step into each iteration. Note that
# when using this, you must iterate from a smaller number to the bigger
# number, because the increment is always 1.
#
# Example that spawns a row of skeletons into the coordinates (4,5),
# (5,5), (6,5), (7,5), (8,5) and (9,5):
#
# {ITERATE 4 9 i (
# [unit]
# type=Skeleton
# x=$i
# y=5
# [/unit]
# )} 
#define ITERATE FROM TO VAR CONTENTS
{VARIABLE {VAR} {FROM}} 
[while]
[variable]
name={VAR}
less_than_equal_to={TO}
[/variable] 
[do]
{CONTENTS} 
{VARIABLE_OP {VAR} add 1}
[/do]
[/while]
#enddef

== Adding unit overlays with a filter instead of (x,y) ==

# UNIT_OVERLAY adds an overlay to a unit, taking in a standard filter
#
# Example that gives all spearmen a book:
# {UNIT_OVERLAY type=Spearman items/book1.png}

#define UNIT_OVERLAY FILTER IMG
[store_unit]
[filter]
{FILTER}
[/filter]
variable=UNIT_OVERLAY_store
kill=no
[/store_unit]
{FOREACH UNIT_OVERLAY_store UNIT_OVERLAY_i}
{VARIABLE_OP UNIT_OVERLAY_tempx format $UNIT_OVERLAY_store[$UNIT_OVERLAY_i].x}
{VARIABLE_OP UNIT_OVERLAY_tempy format $UNIT_OVERLAY_store[$UNIT_OVERLAY_i].y}
[unit_overlay]
x=$UNIT_OVERLAY_tempx
y=$UNIT_OVERLAY_tempy
image={IMG}
[/unit_overlay]
{NEXT UNIT_OVERLAY_i}
{CLEAR_VARIABLE UNIT_OVERLAY_store}
#enddef

== Determining opposite coordinates ==

# Using this, you can determine the coordinates on the "opposite side" of a
# central hex, relative to another hex adjacent to it. What this really means
# is illustrated below:
# __ __ __
# __/ \__ __/2 \__ __/ \__
# / \__/1 \ / \__/ \ /2 \__/ \ C: central point
# \__/C \__/ \__/C \__/ \__/C \__/ 1: the hex to "mirror"
# /2 \__/ \ / \__/ \ / \__/1 \ 2: the result
# \__/ \__/ \__/1 \__/ \__/ \__/
# \__/ \__/ \__/
#
# The coordinates of the central point are given in {CENTER_X} and {CENTER_Y},
# and the coordinates of hex 1 in {X} and {Y}. The coordinates of hex 2 are
# then stored in {VAR}, which will have member variables x and y.
#
# Note that this uses the IF macro given earlier on this page. 
#define OPPOSITE_SIDE CENTER_X CENTER_Y X Y VAR
{VARIABLE x_odd {X}} 
{VARIABLE_OP x_odd multiply 0.5}
{VARIABLE_OP x_odd multiply 2} 
{VARIABLE c_x {CENTER_X}}
{VARIABLE c_y {CENTER_Y}}
{VARIABLE s_x {X}}
{VARIABLE s_y {Y}} 
{VARIABLE result_x {CENTER_X}}
{VARIABLE result_y {CENTER_Y}} 
{IF s_x greater_than $c_x (
[then]
{VARIABLE_OP result_x add -1}
[/then]
)} 
{IF s_x less_than $c_x (
[then]
{VARIABLE_OP result_x add 1}
[/then]
)} 
{IF s_x equals $c_x (
[then]
{IF s_y less_than $c_y (
[then]
{VARIABLE_OP result_y add 1}
[/then]
)} 
{IF s_y greater_than $c_y (
[then]
{VARIABLE_OP result_y add -1}
[/then]
)}
[/then]
)} 
{IF x_odd not_equals $s_x (
[then]
{IF s_y equals $c_y (
[then]
{VARIABLE_OP result_y add 1}
[/then]
)}
[/then] 
[else]
{IF s_y equals $c_y (
[then]
{VARIABLE_OP result_y add -1}
[/then]
)}
[/else]
)} 
{VARIABLE {VAR}.x $result_x}
{VARIABLE {VAR}.y $result_y} 
{CLEAR_VARIABLE c_x}
{CLEAR_VARIABLE c_y}
{CLEAR_VARIABLE s_x}
{CLEAR_VARIABLE s_y}
{CLEAR_VARIABLE result_x}
{CLEAR_VARIABLE result_y}
{CLEAR_VARIABLE x_odd}
#enddef

== General macros ==

#define FORMAT ARRAY VARIABLE
{VARIABLE_OP {VARIABLE} to_variable {ARRAY}.{VARIABLE}}
#enddef

##this is a "partial" macro; not all of the tags match up
#put {NEXT INDEX} after it
#define FOREACH_FORMAT ARRAY INDEX
{FOREACH {ARRAY} {INDEX}}
{FORMAT {ARRAY}[${INDEX}] x}
{FORMAT {ARRAY}[${INDEX}] y}
#enddef

#define STORE_UNIT NAME
[store_unit]
[filter]
description={NAME}
[/filter]
variable={NAME}_store
[/store_unit]
#enddef

#define UNSTORE_UNIT NAME X Y
{VARIABLE {NAME}_store.x {X}}
{VARIABLE {NAME}_store.y {Y}}
[unstore_unit]
variable={NAME}_store
[/unstore_unit]
{CLEAR_VARIABLE {NAME}_store}
#enddef

#define UNSTORE_ARRAY ARRAY
{FOREACH {ARRAY} i}
[unstore_unit]
variable={ARRAY}[$i]
[/unstore_unit]
[clear_variable]
variable={ARRAY}[$i]
[/clear_variable]
{NEXT i}
#enddef

== See Also ==

* [[UsefulWMLFragments]]
* [[ReferenceWML]]

[[Category: UsefulWMLFragments]]

UsefulWMLFragments

2007-04-09T12:24:31Z

Henkutsu: Added to UsefullWMLFragments catagory

== Useful WML Fragments ==

Most of the things found here are macros (see [[PreprocessorRef]]) that must 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.

High level macros often require the lower level macros found in ProgrammingMacros, Utilities, and Scenario Tools.

[[WML Templates]]: Generic campaign, scenario and unit templates.

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

[[WML Utilities]]: Macros to assist other macros. Test Value of Variable. If Have Unit. Store Unit Attribute. Filter by Terrain. Iterate. Overlay with Filter. Determine Opposite Coordinates.

[[WML Scenario Tools]]: Macros directly useful in a scenario. Modify unit. Give villages to a side. Return Unit to Recall List. Trap Unit. Change Keep Terrain. Hero die message. Item effect.

[[WML Dialog Tools]]: Macros useful for unit dialog/storyboarding. Character Speaker, Blank story section, Delays and Fades.

[[MoveExistingUnit]]: Move a unit from one place to another, displaying its movement. Move Unit 1. Move Unit 2. Move Unit 3.

[[Victory Conditions]]: Number of Villages, Amount of Gold. Suitable for multiplayer scenarios.

[[WML Abilities]]: Knockback. Charm. Bloodlust. Abilities cannot currently be incorporated in the unit type definitions themselves, but must be included in the scenario file.

[[WML Buildings]]: Generic Buildings, Light House/Dark Tower, Wishing Well #1, Wishing Well #2.

[[RandomTraitUnit]]: Create a unit with two random traits.

[[DroppableItem]]: Generic item that a unit can carry, and is left on the ground when the unit dies.

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

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

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

[[Advanced WML]]: Branch on Village Type. Recruit from a Ship. Point Rotation Scheme.

== See Also ==

* [[ReferenceWML]]

[[Category: UsefulWMLFragments]]

UsefulWMLFragments

2007-04-09T11:32:30Z

Henkutsu: Added tag about the village macro under wml scenario

== Useful WML Fragments ==

Most of the things found here are macros (see [[PreprocessorRef]]) that must 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.

High level macros often require the lower level macros found in ProgrammingMacros, Utilities, and Scenario Tools.

[[WML Templates]]: Generic campaign, scenario and unit templates.

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

[[WML Utilities]]: Macros to assist other macros. Test Value of Variable. If Have Unit. Store Unit Attribute. Filter by Terrain. Iterate. Overlay with Filter. Determine Opposite Coordinates.

[[WML Scenario Tools]]: Macros directly useful in a scenario. Modify unit. Give villages to a side. Return Unit to Recall List. Trap Unit. Change Keep Terrain. Hero die message. Item effect.

[[WML Dialog Tools]]: Macros useful for unit dialog/storyboarding. Character Speaker, Blank story section, Delays and Fades.

[[MoveExistingUnit]]: Move a unit from one place to another, displaying its movement. Move Unit 1. Move Unit 2. Move Unit 3.

[[Victory Conditions]]: Number of Villages, Amount of Gold. Suitable for multiplayer scenarios.

[[WML Abilities]]: Knockback. Charm. Bloodlust. Abilities cannot currently be incorporated in the unit type definitions themselves, but must be included in the scenario file.

[[WML Buildings]]: Generic Buildings, Light House/Dark Tower, Wishing Well #1, Wishing Well #2.

[[RandomTraitUnit]]: Create a unit with two random traits.

[[DroppableItem]]: Generic item that a unit can carry, and is left on the ground when the unit dies.

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

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

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

[[Advanced WML]]: Branch on Village Type. Recruit from a Ship. Point Rotation Scheme.

== See Also ==

* [[ReferenceWML]]

UsefulWMLFragments

2007-04-09T11:29:29Z

Henkutsu: Added a new page for character dialog macros.

== Useful WML Fragments ==

Most of the things found here are macros (see [[PreprocessorRef]]) that must 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.

High level macros often require the lower level macros found in ProgrammingMacros, Utilities, and Scenario Tools.

[[WML Templates]]: Generic campaign, scenario and unit templates.

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

[[WML Utilities]]: Macros to assist other macros. Test Value of Variable. If Have Unit. Store Unit Attribute. Filter by Terrain. Iterate. Overlay with Filter. Determine Opposite Coordinates.

[[WML Scenario Tools]]: Macros directly useful in a scenario. Modify unit. Return Unit to Recall List. Trap Unit. Change Keep Terrain. Hero die message. Item effect.

[[WML Dialog Tools]]: Macros useful for unit dialog/storyboarding. Character Speaker, Blank story section, Delays and Fades.

[[MoveExistingUnit]]: Move a unit from one place to another, displaying its movement. Move Unit 1. Move Unit 2. Move Unit 3.

[[Victory Conditions]]: Number of Villages, Amount of Gold. Suitable for multiplayer scenarios.

[[WML Abilities]]: Knockback. Charm. Bloodlust. Abilities cannot currently be incorporated in the unit type definitions themselves, but must be included in the scenario file.

[[WML Buildings]]: Generic Buildings, Light House/Dark Tower, Wishing Well #1, Wishing Well #2.

[[RandomTraitUnit]]: Create a unit with two random traits.

[[DroppableItem]]: Generic item that a unit can carry, and is left on the ground when the unit dies.

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

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

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

[[Advanced WML]]: Branch on Village Type. Recruit from a Ship. Point Rotation Scheme.

== See Also ==

* [[ReferenceWML]]