Difference between revisions of "InterfaceActionsWML"

Revision as of 08:53, 12 November 2009

Interface actions

Interface actions are actions that do not have an effect on gameplay; instead, they show something to the player. The main interface tags are [message] and [objectives], but several other tags affect the interface also.

[message]

The most commonly used interface action is [message], which displays a message to the user in a dialog box. It can also be used to take input from the user.

The following key/tags are accepted for [message]:

StandardUnitFilter: the unit whose profile and name are displayed. If no unit matching this filter is found, the message is not displayed (The unit has probably been killed).
[message] elements should be constructed so that it is either guaranteed that a certain unit is alive, or so that dialog flows smoothly even if the message isn't displayed.

speaker: an alternative to standard unit filter. You may specify as the value of the speaker attribute a unit id or any of the following special values:
- narrator: the dialog box is displayed without a caption for the unit speaking or a unit image
- unit: the primary unit for the event is speaking
- second_unit: the secondary unit for the event is speaking

message: (translatable) the text to display to the right of the image. message is sometimes multiple lines; if it is, be sure to use quotes( ' or " )
[show_if]: if present then this message will only be displayed if the conditional statement in this tag is passed (see InternalActionsWML)
side_for: (default: all sides) comma-separated list of sides for who message is shown.
image: (default: profile image of speaker) the image to display next to the message.
caption: (default: name of speaker) the caption to display beside the image. Name to be displayed.
duration: (default: 10) the minimum number of frames for this message to be displayed. (A frame lasts about 30 milliseconds.) During this time any dialog decisions will be disregarded.
sound: a sound effect (wav file) to play as the message is displayed. This can be a comma-separated list, from which one will be randomly chosen.
[option]: zero or more [option] elements may be present. If [option] elements are present, then each option will be displayed in a menu for the user to select one option.
- message: (translatable) the text displayed for the option (see DescriptionWML)
- [show_if]: if present then this option will only be displayed if the conditional statement in this tag is passed (see InternalActionsWML)
- [command]: an element containing actions which are executed if the option is selected.
[text_input]: there can be only one [text_input] tag. this adds a text input field to the message.
- variable: the variable that the user's input will be written to
- label: a text label to the left of the input field
- max_chars: the maximum number of characters that may be typed into the field
- text: text that is written into the field in the beginning
Check EventWML#Multiplayer_safety to find out in which events you can safely use [option] and [text_input] without causing OOS.

Text formatting options for [message]. These can also be used in unit names (user_description), objectives, and such.

A tilde (~) as the first character causes the line to be boldfaced.
An at symbol (@) as the first character causes the line to be green, as done with victory conditions.
A pound symbol (#) as the first character causes the line to be red, as done with defeat conditions.
An asterisk (*) as the first character causes the line to be bigger.
A backquote (`) as the first character causes the line to be smaller.
If used, the caption key text is boldfaced.
An RGB colour code in the beginning causes the line to be the given colour. This can still be preceded by the above characters. Example: message=_"<255,0,0>Red!"

Template:DevFeature In the 1.7 branch these formatting codes are being discarded in favor of Pango markup. Running wmllint on your campaign will up-convert it, warning you about unusual cases you must fix by hand.

[objectives]

The other tag used for plot development is [objectives]. The [objectives] tag overwrites any previously set objectives, and displays text which should describe the objectives of the scenario. Scenario objectives are displayed on the player's first turn after the tag is used, or as part of the event if it triggers during that player's turn. Objectives can also be accessed at any time in a scenario using the "Scenario Objectives" game menu option, making this tag useful for scenario-specific information that the player may need to refer to during play.

This tag renders the objectives attribute of [scenario] obsolete (see objectives, ScenarioWML). Instead of using objectives, use [objectives] to set scenario objectives inside a prestart event. It can also be used to overwrite the starting objectives mid-scenario.

Attributes of [objectives]:

side: Default '0'. The side to set the objectives for. A value of 0 sets objectives for all sides.
summary: Displayed first in the objectives text, this should describe the basic objective for the overall scenario. Can be omitted.
note: Displayed last in the objectives text, this is sometimes used for hints or additional information. Can be omitted.
victory_string: Default ' _ "Victory:"', this text precedes the victory objectives.
defeat_string: Default ' _ "Defeat:"', this text precedes the defeat objectives.
silent: Default: not present. If set to "yes", the objectives are silently changed. Else, they will be shown to the user when appropriate.

Tags of [objectives]:

[objective]: describes a win or loss condition. Most scenarios have multiple win or loss conditions, so use a separate [objective] subtag for each line; this helps with translations.
- description: text for the specific win or loss condition.
- condition: The color and placement of the text. Values are 'win'(colored green, placed after victory_string) and 'lose'(colored red, placed after defeat_string)
- [show_if]: A condition that disables the objective if it doesn't hold. Conditional objectives are refreshed at [show_objectives] time only. Template:DevFeature

Macros

There are a few predefined macros for Objectives that you can use to shorten the code: SET_OBJECTIVES, VICTORY_CONDITION, and DEFEAT_CONDITION. Follow the links for each one to see complete syntax and example usage.

[set_menu_item]

This tag is used to add a custom option in the right-click context menu which can then be used to trigger arbitrary WML commands.

id: the unique id for this menu item. If a menu item with this id already exists, it allows you to set specific changes to that item.
description: the in-game text that will appear for this item in the menu.
image: the image to display next to this item.
needs_select: if yes (default no), then the latest select event (see EventWML) that triggered before this menu item was chosen will be transmitted over the network before this menu item action will be. This only has any effect in networked multiplayer, and is intended to allow more elaborate menu item behaviour there without causing out of sync errors. If you don't know what this means, just leave it false.
[show_if]: If present, the menu item will only be available if the conditional statement (see InternalActionsWML) within evaluates to true. When this is evaluated, the WML variables $x1 and $y1 will point to the location on which the context menu was invoked, so it's possible to for example only enable the option on empty hexes or on a particular unit.
[filter_location]: contains a location filter similar to the one found inside Single Unit Filters (see FilterWML). The menu item will only be available on matching locations.
[command]: contains the WML actions to be executed when the menu item is selected. Again, the WML variables $x1 and $y1 will point to the location on which the context menu was invoked on.

Other interface tags

The following tags are also action tags:

[item]: makes a graphical item appear on a certain hex. Note this only places the graphics for an item. It does not make the item do anything. Use a moveto event to make moving onto the item do something. (Hint: There are a number of predefined items that are used in various campaigns that you can make use of. You can find a list of them if you look into the items.cfg file in the wesnoth install directory (under /data/core/macros))
- x, y: the location to place the item.
- image: the image (in images/ as .png) to place on the hex.
- halo: an image to place centered on the hex. Use this instead of image if the image is bigger than the hex.
- team_name: name of the team for which the item is to be displayed (hidden for others). For multiple teams just put all the names in one string, for example separated by commas.
- visible_in_fog: whether the item should be visible through fog or not. Default yes.
[removeitem]: removes any graphical items on a given hex
- x, y: the hex to remove items off
- image if specified, only removes the given image item
[print]: displays a message across the screen. The message will disappear after a certain time.
- text: (translatable) the text to display.
- size: (default=12) the pointsize of the font to use
- duration: (default=50) the length of time to display the text for. This is measured in the number of 'frames'. A frame in Wesnoth is usually displayed for around 30ms.
- red, green, blue: (default=0,0,0) the color to display the text in. Values vary from 0-255.
[move_unit_fake]: moves an image of a unit along a certain path on the map. The path does not need to be a continuous list of adjacent hexes, so for example only the start and end points can be given, in which case the straightest line between those points will be calculated and used.
- type: the type of the unit whose image to use
- x: a comma-separated list of x locations to move along
- y: a comma-separated list of y locations to move along (x and y values are matched pairs)
- side: the side of the fake unit, used for team-coloring the fake unit
[hide_unit]: makes the given unit become invisible. Useful in conjunction with [move_unit_fake]: to move a leader unit into position on-screen. Each [hide_unit] tag only hides one unit.
- x, y: location of the unit to be hidden. (NOT a standard unit filter! Just x and y.)
[unhide_unit]: stops the currently hidden unit from being hidden.
[scroll]: Scroll a certain number of pixels in a given direction. Useful for earthquake/shaking effects.
- x, y: the number of pixels to scroll along the x and y axis
[scroll_to]: Scroll to a given hex
- x, y: the hex to scroll to
- check_fogged: whether to scroll even to locations covered in fog or shroud. Possible values true (don't scroll to fog) and false (scroll even to fog), with false as the default.
[scroll_to_unit] Scroll to a given unit
- StandardUnitFilter
- check_fogged: whether to scroll even to locations covered in fog or shroud. Possible values true (don't scroll to fog) and false (scroll even to fog), with false as the default.
[sound]: Plays a sound
- name: the filename of the sound to play (in sounds/ as .wav or .ogg)
- repeat: repeats the sound for a specified additional number of times (default=0)
[sound_source]: Creates a sound source. "Sound sources" is a general name for a mechanism which makes possible for map elements to emit sounds according to some rules, where "map elements" can be specific locations or terrain types. For now, only sound sources tied to locations are supported.
- id: a unique identification key of the sound source
- sounds: a list of comma separated, randomly played sounds associated with the sound source
- delay: a numerical value (in milliseconds) of the minimal delay between two playbacks of the source's sound if the source remains visible on the screen; if one scrolls out and back in, the source will be considered as ready to play
- chance: a percentage (a value from 0 to 100) describing the chance of the source being activated every second after the delay has passed or when the source's location appears on the screen (note that it cannot play more than one file at the same time)
- check_fogged: possible values "true" and "false" - if true the source will not play if its locations are fogged
- check_shrouded: Template:DevFeature possible values "true" and "false" - if true the source will not play if its locations are shrouded
- x,y: a StandardLocationFilter for the locations associated with the sound source
- fade_range (default = 3): distance in hexes that determines a "circular" area around the one specified by full_range where sound volume fades out linearly
- full_range (default = 14): distance in hexes that determines a "circular" area where source plays with full volume, relative to screen center
- loop: number of times a sound sample should be looped if it stays visible. -1 means infinite (~65000)
[remove_sound_source]: Removes a previously defined sound source.
- id: the identification key of the sound source to remove
[music]: Switches to playing different music
- name: the filename of the music to play (in music/ as .ogg)
- see MusicListWML for the correct syntax
[colour_adjust]: tints the colour of the screen.
- red, green, blue: values from -255 to 255, the amount to tint by for each colour
[delay]: pauses the game
- time: the time to pause in milliseconds
[redraw]: redraws the screen (this normally isn't done during events, although some of the other interface actions cause the screen or parts of it to be redrawn).
- side: if used, recalculates fog and shroud for that side. Useful if you for example spawn friendly units in the middle of an event and want the shroud to update accordingly (otherwise units that spawn inside fog would remain invisible for the duration of the event, since the fog would not automatically get cleared around them).
[unit_overlay]: sets an image that will be drawn over a particular unit, and follow it around
- x, y: the location of the unit to overlay on
- image: the image to place on the unit
[remove_unit_overlay]: removes a particular overlayed image from a unit
- x, y: the location of the unit to remove an overlay from
- image: the image to remove from the unit
[animate_unit]: uses the custom animation of a unit to animate it on screen (if the unit has the corresponding animation)
- flag: the key to find the good custom animation in the unit description see the [extra_anim] description in AnimationWML Standar anims can be triggered with the following keywors leading recruited standing idling levelin levelout healing healed poisoned movement defend attack death victory pre_teleport post_teleport
- [filter]: a StandardUnitFilter see FilterWML by default, the unit at the event location will be animated. You can use this tag to choose any other unit to animate
- [primary_attack]: if this tag is not present, the filter for animation will be triggered with no attack. If it is here, all attacks from the unit will be filtered, and a matching one will be used to filter the animation
- [secondary_attack]: same for the second attack
- hits: the hit type to filter unit on
- text: a text to hover during the animation
- red: red value for the text color
- green: green value for the text color
- blue: blue value for the text color
- with_bars: whether to display the status bars or not.
- [animate]: a sub block with the same syntax as the [animate_unit] except that the [filter] block is mandatory to find the unit. This block will find and animate another unit simultaneously
- [facing]: a StandardLocationFilter specifying what direction the unit should be facing when animated
[label] places a label on the map.
- x, y: the location of the label
- text: what the label should say
- team_name: if specified, the label will only be visible to the given team.
- visible_in_fog: whether the label should be visible through fog or not. Default yes.
[deprecated_message] shows a deprecated message in the message area, this feature is only intended to be used to warn about deprecated macros in mainline. The message is not translatable.
- message: the message to show.
[wml_message] outputs a message to Wesnoth's console output. Intended for campaign designers to output silent text to the console, without annoying the player; then, that text might contain information useful for later bug-reporting. The log domain for it is wml, and the debug/dbg log level is available for use with the logger attribute. Depending on the current log level (error by default), which may be changed with the in-game :log command, or the --log-<level>=wml command line switch, the messages are echoed to the in-game chat.
- message: the message to show.
- logger: the Wesnoth engine output logger that should catch the text; this might be 'err' (the errors log level), 'warn'/'wrn' (the warnings log level) or anything else (the information log level). Not all information will be displayed depending on the log level chosen when starting Wesnoth.
[open_help] opens the in-game help.
- topic: the id of the topic to open
[show_objectives]: Template:DevFeature refreshes the objectives defined by [objectives] and its [show_if] tags, and displays them. (It is also called whenever the user explicitly asks for the objectives; this matters only if the tag was overridden by a Lua script.)
- side: the side to show the objectives. If not set, all sides are used.

Useful Macros

There are some predefined macros that you find useful for interface actions. You can find a complete list along with a detailed explanation of how they work here.

{FLOATING_TEXT} Float some text over a unit similar to the damage numbers.
{HIGHLIGHT_UNIT} Highlight a unit on the map. Use this to show important units
{HIGHLIGHT_IMAGE} Places and highlights an image on the map. Use this to show important items or locations
{SET_IMAGE} Places an image on the map which has no other function.
{QUAKE <soundfile>} Creates a tremor like screenshake and plays <soundfile>. ({TREMOR} is a deprecated version, equivalent to {QUAKE (rumble.ogg)})
{FLASH_WHITE} Flash the screen white momentarily. You can also replace WHITE with RED, BLUE or GREEN for a different colour.

@@ Line 45: / Line 45: @@
 * An RGB colour code in the beginning causes the line to be the given colour. This can still be preceded by the above characters. Example: ''message=_"<255,0,0>Red!"''
-{{DevFeature}} In the 1.7 branch these formatting codes are being discarded in favor of [http://pygtk.org/docs/pygtk/pango-markup-language.html Pango] markup.  Running wmllint on your campaign will up-convert it, warning you about unusual cases you must fix by hand.  At the mement, Pango markup only works in '''message=''' attributes within '''[message]''' tags.  More attributes within other tags will be enabled in the future.
+{{DevFeature}} In the 1.7 branch these formatting codes are being discarded in favor of [http://library.gnome.org/devel/pango/unstable/PangoMarkupFormat.html Pango markup]. Running wmllint on your campaign will up-convert it, warning you about unusual cases you must fix by hand.
 == [objectives] ==