https://wiki.wesnoth.org/api.php?action=feedcontributions&feedformat=atom&user=BaufoThe Battle for Wesnoth Wiki - User contributions [en]2026-04-25T06:29:56ZUser contributionsMediaWiki 1.31.16https://wiki.wesnoth.org/index.php?title=ServerAdministration&diff=28660ServerAdministration2009-03-14T22:08:41Z<p>Baufo: /* Available commands */</p>
<hr />
<div>== Overview ==<br />
<br />
The Wesnoth server, wesnothd provides a simple interface for administering the server from within the game itself.<br />
<br />
To issue an administrative command to the server, you must be connected to the server using Wesnoth, and in the lobby. Any text you type into the chat box that begins with '/query ' will be considered an administrative command instead of a normal chat message. It will not be relayed to other users, but instead treated as a command by the server.<br />
<br />
Most commands are not accessible to normal users. They are only accessible once you have authenticated yourself to the server as an administrator. The way to authenticate yourself as an administrator is to use the command,<br />
<br />
'''/query <password>'''<br />
<br />
where <password> is the administrative password to the server. The administrative password is specified as the passwd attribute in wesnothd.cfg. By convention, it will generally start with 'admin ' followed by the actual password, so the usual syntax to authenticate yourself is,<br />
<br />
'''/query admin <passwd>'''<br />
<br />
Naturally the password for a server should be kept a secret. One danger is that if you forget to type '/query ' at the start of a command you may accidentally type the password in a chat message, and let all users on the server know it. If you do this, then notify an administrator who has access to the box as soon as possible, so they can reset the password in wesnothd.cfg. We may provide features to prevent this kind of accident in future versions.<br />
<br />
A message from the server should tell you that you have successfully authenticated yourself as an administrator. The server will recognize you as an administrator until the next time you log out of the server.<br />
<br />
== Available commands ==<br />
<br />
'''/query games''': shows how many games have ended in various ways. (available to non-administrators)<br />
<br />
'''/query metrics''': shows a simple metrics report of how the server has been performing. (available to non-administrators)<br />
<br />
'''/query netstats''': shows some network stats. (available to non-administrators)<br />
<br />
'''/query stats''': shows the current number of users and games. (available to non-administrators)<br />
<br />
'''/query wml''': shows stats about WML documents and their current memory consumption. (available to non-administrators)<br />
<br />
'''/query status [<nickmask>]''': this command will show you a list of users (matching the nickmask) connected to the server, with IP addresses, and how long they have been connected. Note that IP addresses of users are not available to non-administrators, and should be treated as confidential. When used as a non-administrator it just returns the entry of the user.<br />
<br />
'''/query motd [<message>]''': this command sets the message of the day that appears as the first message users get when they log on to the server. You can prefix the message with color formatting as described in [[InterfaceActionsWML#.5Bmessage.5D]]. Without argument it returns the current motd. (available to non-administrators)<br />
<br />
'''/query msg <message>''': this command will relay the message 'message' to all users on the server, even if they are in a game. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix the message with color formatting as described in [[InterfaceActionsWML#.5Bmessage.5D]].<br />
<br />
'''/query lobbymsg <message>''': this command will relay the message 'message' to all users in the lobby of the server. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix the message with color formatting as described in [[InterfaceActionsWML#.5Bmessage.5D]].<br />
<br />
'''/green <message>''': this command executes the lobbysmg command with green font (alias for '/query lobbymsg @<message>').<br />
<br />
'''/red <message>''': this command executes the lobbysmg command with red font (alias for '/query lobbymsg #<message>').<br />
<br />
'''/yellow <message>''': this command executes the lobbysmg command with yellow font (alias for '/query lobbymsg <255,255,0><message>').<br />
<br />
'''/query kick <mask> [<reason>]''': this command will disconnect the user matching the given nick or ip mask from the server.<br />
<br />
'''/query ban <mask> [<time>] <reason>''': this command will make the server refuse connections from users matching the given ip mask or the ips of users matching the nick mask. Existing bans (and their reason!) will be overwritten so you can change the reason for a ban by adding it again.<br />
<br />
'''/query gban <mask> <group> [<time>] <reason>''': this command will make a ban that belongs to a group. They function just like ordinary bans but only the group name is mentioned in the ban listing.<br />
<br />
'''/query bans''': shows a list of currently banned ip masks and the reasons for the bans.<br />
<br />
'''/query kban <mask> [<time>] <reason>''': this command is equivalent to 'kick <mask>' 'ban <mask> [<time] <reason>' -- i.e. bans the users matching the ip mask or the ips of users matching the nick mask and disconnects them all in one go. The most common way to ban someone from the server.<br />
<br />
'''/query unban <ipmask>''': this command removes the specified ip mask from the ban list.<br />
<br />
'''/query ungban <group>''': this command removes all bans in the group.<br />
<br />
'''/query searchlog <mask>''': this returns the IP a nick matching the mask has used or the nicks that used a matching IP. Unlike status this searches the IP log.<br />
<br />
'''/query deny_unregistered_login [<yes/no>]''': If set to yes the server will refuse to let unregistered users log in. Without an argument the current setting is displayed. There is an alias 'dul' for convenience.<br />
<br />
<br />
Masks are arguments that can contain wildcards ('*' and '?'). '*' matches any number of characters (including none), and '?' any one character. Ip masks are masks that contain at least one '.'.<br />
<br />
The time parameter is used to set the time when a ban expires. A simple example is 2D12h which means after 2 days and 12 hours the ban gets removed. Modifiers are: s=seconds, m=minutes, h=hours, D=days, M=months and Y=years (short times with lowercase and long times with uppercase). We can also set shortcuts like LONG, MEDIUM and SHORT for common ban lengths but none is set yet.<br />
<br />
== Future extensions ==<br />
<br />
The current administrative interface is fairly primitive. We plan to provide some further extensions in the future, such as,<br />
<br />
'''/query mute <nick>''': makes it so that any messages sent by the user with the given nick will not be received by any other user on the server unless they share an IP address with 'nick'. Any games created by 'nick' will likewise not be seen by other users. 'nick' may observe games but will not appear in the observer list, and players of the game will not see any messages they type.<br />
<br />
[[Category:Troubleshooting and Bugs]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=ServerAdministration&diff=28659ServerAdministration2009-03-14T22:05:20Z<p>Baufo: /* Available commands */</p>
<hr />
<div>== Overview ==<br />
<br />
The Wesnoth server, wesnothd provides a simple interface for administering the server from within the game itself.<br />
<br />
To issue an administrative command to the server, you must be connected to the server using Wesnoth, and in the lobby. Any text you type into the chat box that begins with '/query ' will be considered an administrative command instead of a normal chat message. It will not be relayed to other users, but instead treated as a command by the server.<br />
<br />
Most commands are not accessible to normal users. They are only accessible once you have authenticated yourself to the server as an administrator. The way to authenticate yourself as an administrator is to use the command,<br />
<br />
'''/query <password>'''<br />
<br />
where <password> is the administrative password to the server. The administrative password is specified as the passwd attribute in wesnothd.cfg. By convention, it will generally start with 'admin ' followed by the actual password, so the usual syntax to authenticate yourself is,<br />
<br />
'''/query admin <passwd>'''<br />
<br />
Naturally the password for a server should be kept a secret. One danger is that if you forget to type '/query ' at the start of a command you may accidentally type the password in a chat message, and let all users on the server know it. If you do this, then notify an administrator who has access to the box as soon as possible, so they can reset the password in wesnothd.cfg. We may provide features to prevent this kind of accident in future versions.<br />
<br />
A message from the server should tell you that you have successfully authenticated yourself as an administrator. The server will recognize you as an administrator until the next time you log out of the server.<br />
<br />
== Available commands ==<br />
<br />
'''/query games''': shows how many games have ended in various ways. (available to non-administrators)<br />
<br />
'''/query metrics''': shows a simple metrics report of how the server has been performing. (available to non-administrators)<br />
<br />
'''/query netstats''': shows some network stats. (available to non-administrators)<br />
<br />
'''/query stats''': shows the current number of users and games. (available to non-administrators)<br />
<br />
'''/query wml''': shows stats about WML documents and their current memory consumption. (available to non-administrators)<br />
<br />
'''/query status [<nickmask>]''': this command will show you a list of users (matching the nickmask) connected to the server, with IP addresses, and how long they have been connected. Note that IP addresses of users are not available to non-administrators, and should be treated as confidential. When used as a non-administrator it just returns the entry of the user.<br />
<br />
'''/query motd [<message>]''': this command sets the message of the day that appears as the first message users get when they log on to the server. You can prefix the message with color formatting as described in [[InterfaceActionsWML#.5Bmessage.5D]]. Without argument it returns the current motd. (available to non-administrators)<br />
<br />
'''/query msg <message>''': this command will relay the message 'message' to all users on the server, even if they are in a game. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix the message with color formatting as described in [[InterfaceActionsWML#.5Bmessage.5D]].<br />
<br />
'''/query lobbymsg <message>''': this command will relay the message 'message' to all users in the lobby of the server. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix the message with color formatting as described in [[InterfaceActionsWML#.5Bmessage.5D]].<br />
<br />
'''/green <message>''': this command executes the lobbysmg command with green font (alias for '/query lobbymsg @<message>').<br />
<br />
'''/red <message>''': this command executes the lobbysmg command with red font (alias for '/query lobbymsg #<message>').<br />
<br />
'''/yellow <message>''': this command executes the lobbysmg command with yellow font (alias for '/query lobbymsg <255,255,0><message>').<br />
<br />
'''/query kick <mask> [<reason>]''': this command will disconnect the user matching the given nick or ip mask from the server.<br />
<br />
'''/query ban <mask> [<time>] <reason>''': this command will make the server refuse connections from users matching the given ip mask or the ips of users matching the nick mask. Existing bans (and their reason!) will be overwritten so you can change the reason for a ban by adding it again.<br />
<br />
'''/query gban <mask> <group> [<time>] <reason>''': this command will make a ban that belongs to a group. They function just like ordinary bans but only the group name is mentioned in the ban listing.<br />
<br />
'''/query bans''': shows a list of currently banned ip masks and the reasons for the bans.<br />
<br />
'''/query kban <mask> [<time>] <reason>''': this command is equivalent to 'kick <mask>' 'ban <mask> [<time] <reason>' -- i.e. bans the users matching the ip mask or the ips of users matching the nick mask and disconnects them all in one go. The most common way to ban someone from the server.<br />
<br />
'''/query unban <ipmask>''': this command removes the specified ip mask from the ban list.<br />
<br />
'''/query ungban <group>''': this command removes all bans in the group.<br />
<br />
'''/query searchlog <mask>''': this returns the IP a nick matching the mask has used or the nicks that used a matching IP. Unlike status this searches the IP log.<br />
<br />
<br />
Masks are arguments that can contain wildcards ('*' and '?'). '*' matches any number of characters (including none), and '?' any one character. Ip masks are masks that contain at least one '.'.<br />
<br />
The time parameter is used to set the time when a ban expires. A simple example is 2D12h which means after 2 days and 12 hours the ban gets removed. Modifiers are: s=seconds, m=minutes, h=hours, D=days, M=months and Y=years (short times with lowercase and long times with uppercase). We can also set shortcuts like LONG, MEDIUM and SHORT for common ban lengths but none is set yet.<br />
<br />
== Future extensions ==<br />
<br />
The current administrative interface is fairly primitive. We plan to provide some further extensions in the future, such as,<br />
<br />
'''/query mute <nick>''': makes it so that any messages sent by the user with the given nick will not be received by any other user on the server unless they share an IP address with 'nick'. Any games created by 'nick' will likewise not be seen by other users. 'nick' may observe games but will not appear in the observer list, and players of the game will not see any messages they type.<br />
<br />
[[Category:Troubleshooting and Bugs]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=MultiplayerServerWML&diff=28217MultiplayerServerWML2009-02-10T18:28:05Z<p>Baufo: /* The login procedure */</p>
<hr />
<div>= Multiplayer Server WML =<br />
This page describes the WML used to communicate with the multiplayer server (wesnothd).<br />
<br />
== The login procedure ==<br />
<br />
* server request (optional)<br />
** '''[version]'''<br />
<br />
* client response<br />
** '''[version]'''<br />
*** '''version''': The client's version string.<br />
<br />
* server request<br />
** '''[mustlogin]'''<br />
<br />
* client response<br />
** '''[login]'''<br />
*** '''username''': The username the client would like to have.<br />
*** '''password_reminder''': If "yes" the client requests the server to send a password reminder for the provided username.<br />
*** '''password''': The hashed password, created from the username, the password and salt received from the server.<br />
<br />
* server response<br />
** '''[join_lobby]''' or<br />
** '''[error]'''<br />
*** '''message''': The error message.<br />
*** '''password_request''': If not empty the server asks the client to provide a password for its desired username.<br />
*** '''phpbb_encryption''': If "yes" the client will encrypt the password using phpbb's algorithm.<br />
*** '''random_salt''': Random salt sent to the client for mixing with the password hash.<br />
*** '''hash_seed''': Salt generated from the original hash that is required to recreate it.<br />
*** '''salt''': Salt generated from the original hash that is required to recreate it.<br />
*** '''force_confirmation''': Display an ok/cancel dialog with the content of the 'message' key.<br />
<br />
* server response<br />
** '''[gamelist]'''<br />
*** '''[game]''' (repeated)<br />
**** '''id''': A unique id of the game.<br />
**** '''name''': The title of the game.<br />
**** '''mp_scenario''': The id of the scenario.<br />
**** '''mp_era''': The id of the used era.<br />
**** '''mp_use_map_settings''': Does the game use the map settings specified in the scenario.<br />
**** '''mp_fog''': Does the game use fog.<br />
**** '''mp_shroud''': Does the game use shroud.<br />
**** '''mp_village_gold''': The number of gold per village.<br />
**** '''experience_modifier''': The experience setting.<br />
**** '''mp_countdown''': Does the game use a timer.<br />
**** '''mp_countdown_reservoir_time''': Upper limit of the possibly available time.<br />
**** '''mp_countdown_init_time''': Initial time.<br />
**** '''mp_countdown_action_bonus''': Time bonus per action.<br />
**** '''mp_countdown_turn_bonus''': Time bonus per turn.<br />
**** '''map_data''': The map data.<br />
**** '''hash''': The hash value of the map_data.<br />
**** '''observer''': Are observers allowed or not.<br />
**** '''human_sides''': The number of sides played by humans.<br />
**** '''slots''': The number of vacant/max slots.<br />
**** '''turn''': The current turn/max turn.<br />
** '''[user]''' (repeated)<br />
*** '''name''': The username of the player.<br />
*** '''game_id''': The ID of the game the player is in (version 1.3.7+svn).<br />
*** '''location''': The name of the game the player is in.<br />
*** '''available''': "yes" if the player is in the lobby; "no" if in a game.<br />
Many of the keys under [game] are described more indepth on the [[ScenarioWML]] page.<br />
<br />
== Error messages ==<br />
<br />
* '''[error]'''<br />
** '''message''': The error message.<br />
<br />
== Chat (lobby and in-game) ==<br />
<br />
* '''[message]'''<br />
** '''sender''': (optional - filled by the server) The sender of the message.<br />
** '''message''': The message itself.<br />
* '''[whisper]'''<br />
** '''receiver''': The receiver of the whisper<br />
** '''sender''': (optional - filled by the server) The sender of the whisper.<br />
** '''message''': The message itself.<br />
<br />
== Nick registration related commands (lobby and in-game) ==<br />
<br />
* '''[nickserv]'''<br />
** '''[register]'''<br />
*** '''password''': The password for the nick.<br />
*** '''mail''': The email address for the nick.<br />
** '''[drop]''': Drop this username.<br />
** '''[set]''': Set a detail (e.g. email address) for this nick.<br />
*** '''detail''': The detail, e.g. "mail".<br />
*** '''value''': The new value for this detail, e.g. "user@edomain"<br />
** '''[info]''': Request info about another username.<br />
*** '''name''': The username.<br />
<br />
== Updating the lobby state ==<br />
<br />
* '''[gamelist_diff]''': server message - basically a diff from two [gamelist]s; the keys listed are the ones that actually occure in practice<br />
** '''index''': The index of a user.<br />
** '''[insert_child]''' A new user logged on.<br />
*** '''[user]'''<br />
**** '''name''': The name of the user.<br />
**** '''available''' "yes"<br />
*** '''[delete_child]''' A user logged off.<br />
** '''[change_child]'''<br />
*** '''[user]'''<br />
**** '''[insert]''': A user joined/left a game.<br />
***** '''available''': "yes" when the user left a game. "no" when the user joined a game<br />
***** '''location''': The name of the game the user joined.<br />
**** '''[delete]'''<br />
***** '''location''': "x" when a game was left.<br />
*** '''[gamelist]'''<br />
**** '''index''': Index of the game in question.<br />
**** '''[insert_child]''': A game started.<br />
***** '''[game]''' All the usual keys of [game] possible, see above.<br />
**** '''[delete_child]''': A game ended.<br />
***** '''[game]'''<br />
**** '''[change_child]''': Something changed in a game.<br />
***** '''[game]'''<br />
****** '''[insert]'''<br />
******* '''slots''': The number of free slots in the form: free/max slots<br />
******* '''turn''': The turn number in the form: current turn/max turns<br />
****** '''[delete]'''<br />
******* '''map''': "x" comes with every ''turn'' or ''slots'' change for games with shroud<br />
******* '''mp_scenario''': "x" comes with ''turn'' and ''slots'' changes for games with no scenario id<br />
<br />
* '''[observer]''' or '''[observer_quit]''': server message - players joining([observer_quit] - quitting the lobby "game")/quitting([observer] - joining the lobby "game") a game<br />
** '''name''': Username of the player/observer.<br />
<br />
== Game setup (the phase from creation to start) ==<br />
To create a game the client sends:<br />
* '''[create_game]'''<br />
** '''name''': The title of the game.<br />
<br />
followed by a message with the scenario options as under [game] (see above) plus the scenario data ([time], [era], [side], etc. see [[ScenarioWML]])<br />
<br />
* '''[join]'''<br />
** '''id''': The id of the game.<br />
** '''observe''': Join the game as an observer.<br />
<br />
* '''[scenario_diff]''': [[ScenarioWML]] diff (side changes, etc.)<br />
<br />
* '''[start_game]''': sent by the host to start a game<br />
* '''[leave_game]''': sent by the client when it leaves a game; sent by the server to make a client leave a game<br />
<br />
== In-game communication ==<br />
<br />
* '''[store_next_scenario]''': sent by the host - the scenario data (see [[ScenarioWML]]) to advance to the next scenario<br />
* '''[notify_next_scenario]''': sent by the server to tell players that the data for the next scenario is available<br />
* '''[load_next_scenario]''': sent by the client to request the data for the next scenario<br />
* '''[next_scenario]''': data for the next scenario (see [[ScenarioWML]]), sent by the server on request<br />
<br />
* '''[info]''': sent by the host on game end - info about the game state<br />
** '''type''': "termination" <br />
** '''condition''': the termination reason<br />
<br />
* '''[change_controller]''': a player (un)droids one of his sides or assigns control to someone else (The host can assign control for any side.)<br />
** '''side''': the side to change controller<br />
** '''player''': the nick of the player to take control<br />
** '''controller''': the new controller: "human" or "human_ai"<br />
** '''own_side''': "yes"<br />
<br />
If a player leaves this is sent to the host for all sides he owned.<br />
* '''side_drop''': The number of a side that dropped because a player left.<br />
* '''controller''': The controller of that side. ("ai", "network")<br />
<br />
* '''[muteall]''': the host mutes/unmutes all observers - toggles<br />
* '''[mute]''': the host mutes an observer - toggles<br />
** '''username''': the username of the observer - if not specified the servers returns a list of muted usernames<br />
* '''[kick]''' or '''[ban]''': the host kicks/bans a player/observer<br />
** '''username''': the username of the player/observer<br />
<br />
* '''[turn]'''<br />
** '''[command]''': (repeated) can contain all the tags you can find in a replay: [recruit], [move], [end_turn], etc.<br />
*** '''[speak]'''<br />
**** '''message''': text of the message<br />
**** '''description''': the sender (in 1.4 and earlier; later replaced by '''id''')<br />
**** '''id''': the sender {{DevFeature}}<br />
**** '''team_name''': the name of the team the message is for - empty if it's a public message<br />
<br />
== Administrative commands ==<br />
* '''[query]'''<br />
** '''type''': The type of query. See [[ServerAdministration]] for details.<br />
<br />
[[Category:WML Reference]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=MultiplayerServerWML&diff=28114MultiplayerServerWML2009-01-29T17:31:56Z<p>Baufo: /* The login procedure */</p>
<hr />
<div>= Multiplayer Server WML =<br />
This page describes the WML used to communicate with the multiplayer server (wesnothd).<br />
<br />
== The login procedure ==<br />
<br />
* server request (optional)<br />
** '''[version]'''<br />
<br />
* client response<br />
** '''[version]'''<br />
*** '''version''': The client's version string.<br />
<br />
* server request<br />
** '''[mustlogin]'''<br />
<br />
* client response<br />
** '''[login]'''<br />
*** '''username''': The username the client would like to have.<br />
*** '''password_reminder''': If "yes" the client requests the server to send a password reminder for the provided username.<br />
*** '''password''': The hashed password, created from the username, the password and salt received from the server.<br />
<br />
* server response<br />
** '''[join_lobby]''' or<br />
** '''[error]'''<br />
*** '''message''': The error message.<br />
*** '''password_request''': If not empty the server asks the client to provide a password for its desired username.<br />
*** '''phpbb_encryption''': If "yes" the client will encrypt the password using phpbb's algorithm.<br />
*** '''random_salt''': Random salt sent to the client for mixing with the password hash.<br />
*** '''hash_seed''': Salt generated from the original hash that is required to recreate it.<br />
*** '''salt''': Salt generated from the original hash that is required to recreate it.<br />
<br />
* server response<br />
** '''[gamelist]'''<br />
*** '''[game]''' (repeated)<br />
**** '''id''': A unique id of the game.<br />
**** '''name''': The title of the game.<br />
**** '''mp_scenario''': The id of the scenario.<br />
**** '''mp_era''': The id of the used era.<br />
**** '''mp_use_map_settings''': Does the game use the map settings specified in the scenario.<br />
**** '''mp_fog''': Does the game use fog.<br />
**** '''mp_shroud''': Does the game use shroud.<br />
**** '''mp_village_gold''': The number of gold per village.<br />
**** '''experience_modifier''': The experience setting.<br />
**** '''mp_countdown''': Does the game use a timer.<br />
**** '''mp_countdown_reservoir_time''': Upper limit of the possibly available time.<br />
**** '''mp_countdown_init_time''': Initial time.<br />
**** '''mp_countdown_action_bonus''': Time bonus per action.<br />
**** '''mp_countdown_turn_bonus''': Time bonus per turn.<br />
**** '''map_data''': The map data.<br />
**** '''hash''': The hash value of the map_data.<br />
**** '''observer''': Are observers allowed or not.<br />
**** '''human_sides''': The number of sides played by humans.<br />
**** '''slots''': The number of vacant/max slots.<br />
**** '''turn''': The current turn/max turn.<br />
** '''[user]''' (repeated)<br />
*** '''name''': The username of the player.<br />
*** '''game_id''': The ID of the game the player is in (version 1.3.7+svn).<br />
*** '''location''': The name of the game the player is in.<br />
*** '''available''': "yes" if the player is in the lobby; "no" if in a game.<br />
Many of the keys under [game] are described more indepth on the [[ScenarioWML]] page.<br />
<br />
== Error messages ==<br />
<br />
* '''[error]'''<br />
** '''message''': The error message.<br />
<br />
== Chat (lobby and in-game) ==<br />
<br />
* '''[message]'''<br />
** '''sender''': (optional - filled by the server) The sender of the message.<br />
** '''message''': The message itself.<br />
* '''[whisper]'''<br />
** '''receiver''': The receiver of the whisper<br />
** '''sender''': (optional - filled by the server) The sender of the whisper.<br />
** '''message''': The message itself.<br />
<br />
== Nick registration related commands (lobby and in-game) ==<br />
<br />
* '''[nickserv]'''<br />
** '''[register]'''<br />
*** '''password''': The password for the nick.<br />
*** '''mail''': The email address for the nick.<br />
** '''[drop]''': Drop this username.<br />
** '''[set]''': Set a detail (e.g. email address) for this nick.<br />
*** '''detail''': The detail, e.g. "mail".<br />
*** '''value''': The new value for this detail, e.g. "user@edomain"<br />
** '''[info]''': Request info about another username.<br />
*** '''name''': The username.<br />
<br />
== Updating the lobby state ==<br />
<br />
* '''[gamelist_diff]''': server message - basically a diff from two [gamelist]s; the keys listed are the ones that actually occure in practice<br />
** '''index''': The index of a user.<br />
** '''[insert_child]''' A new user logged on.<br />
*** '''[user]'''<br />
**** '''name''': The name of the user.<br />
**** '''available''' "yes"<br />
*** '''[delete_child]''' A user logged off.<br />
** '''[change_child]'''<br />
*** '''[user]'''<br />
**** '''[insert]''': A user joined/left a game.<br />
***** '''available''': "yes" when the user left a game. "no" when the user joined a game<br />
***** '''location''': The name of the game the user joined.<br />
**** '''[delete]'''<br />
***** '''location''': "x" when a game was left.<br />
*** '''[gamelist]'''<br />
**** '''index''': Index of the game in question.<br />
**** '''[insert_child]''': A game started.<br />
***** '''[game]''' All the usual keys of [game] possible, see above.<br />
**** '''[delete_child]''': A game ended.<br />
***** '''[game]'''<br />
**** '''[change_child]''': Something changed in a game.<br />
***** '''[game]'''<br />
****** '''[insert]'''<br />
******* '''slots''': The number of free slots in the form: free/max slots<br />
******* '''turn''': The turn number in the form: current turn/max turns<br />
****** '''[delete]'''<br />
******* '''map''': "x" comes with every ''turn'' or ''slots'' change for games with shroud<br />
******* '''mp_scenario''': "x" comes with ''turn'' and ''slots'' changes for games with no scenario id<br />
<br />
* '''[observer]''' or '''[observer_quit]''': server message - players joining([observer_quit] - quitting the lobby "game")/quitting([observer] - joining the lobby "game") a game<br />
** '''name''': Username of the player/observer.<br />
<br />
== Game setup (the phase from creation to start) ==<br />
To create a game the client sends:<br />
* '''[create_game]'''<br />
** '''name''': The title of the game.<br />
<br />
followed by a message with the scenario options as under [game] (see above) plus the scenario data ([time], [era], [side], etc. see [[ScenarioWML]])<br />
<br />
* '''[join]'''<br />
** '''id''': The id of the game.<br />
** '''observe''': Join the game as an observer.<br />
<br />
* '''[scenario_diff]''': [[ScenarioWML]] diff (side changes, etc.)<br />
<br />
* '''[start_game]''': sent by the host to start a game<br />
* '''[leave_game]''': sent by the client when it leaves a game; sent by the server to make a client leave a game<br />
<br />
== In-game communication ==<br />
<br />
* '''[store_next_scenario]''': sent by the host - the scenario data (see [[ScenarioWML]]) to advance to the next scenario<br />
* '''[load_next_scenario]''': sent by the client to request the data for the next scenario<br />
* '''[next_scenario]''': data for the next scenario (see [[ScenarioWML]]), sent by the server on request<br />
<br />
* '''[info]''': sent by the host on game end - info about the game state<br />
** '''type''': "termination" <br />
** '''condition''': the termination reason<br />
<br />
* '''[change_controller]''': a player gives away one of his sides<br />
** '''side''': the side to change controller<br />
** '''player''': the nick of the player to take control<br />
** '''own_side''': "yes"<br />
<br />
If a player leaves this is sent to the host for all sides he owned.<br />
* '''side_drop''': The number of a side that dropped because a player left.<br />
* '''controller''': The controller of that side. ("human", "ai", "network", "none")<br />
<br />
* '''[muteall]''': the host mutes/unmutes all observers - toggles<br />
* '''[mute]''': the host mutes an observer - toggles<br />
** '''username''': the username of the observer - if not specified the servers returns a list of muted usernames<br />
* '''[kick]''' or '''[ban]''': the host kicks/bans a player/observer<br />
** '''username''': the username of the player/observer<br />
<br />
* '''[turn]'''<br />
** '''[command]''': (repeated) can contain all the tags you can find in a replay: [recruit], [move], [end_turn], etc.<br />
*** '''[speak]'''<br />
**** '''message''': text of the message<br />
**** '''description''': the sender (in 1.4 and earlier; later replaced by '''id''')<br />
**** '''id''': the sender {{DevFeature}}<br />
**** '''team_name''': the name of the team the message is for - empty if it's a public message<br />
<br />
== Administrative commands ==<br />
* '''[query]'''<br />
** '''type''': The type of query. See [[ServerAdministration]] for details.<br />
<br />
[[Category:WML Reference]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=ServerAdministration&diff=27699ServerAdministration2008-12-23T20:22:26Z<p>Baufo: /* Available commands */</p>
<hr />
<div>== Overview ==<br />
<br />
The Wesnoth server, wesnothd provides a simple interface for administering the server from within the game itself.<br />
<br />
To issue an administrative command to the server, you must be connected to the server using Wesnoth, and in the lobby. Any text you type into the chat box that begins with '/query ' will be considered an administrative command instead of a normal chat message. It will not be relayed to other users, but instead treated as a command by the server.<br />
<br />
Most commands are not accessible to normal users. They are only accessible once you have authenticated yourself to the server as an administrator. The way to authenticate yourself as an administrator is to use the command,<br />
<br />
'''/query <password>'''<br />
<br />
where <password> is the administrative password to the server. The administrative password is specified as the passwd attribute in wesnothd.cfg. By convention, it will generally start with 'admin ' followed by the actual password, so the usual syntax to authenticate yourself is,<br />
<br />
'''/query admin <passwd>'''<br />
<br />
Naturally the password for a server should be kept a secret. One danger is that if you forget to type '/query ' at the start of a command you may accidentally type the password in a chat message, and let all users on the server know it. If you do this, then notify an administrator who has access to the box as soon as possible, so they can reset the password in wesnothd.cfg. We may provide features to prevent this kind of accident in future versions.<br />
<br />
A message from the server should tell you that you have successfully authenticated yourself as an administrator. The server will recognize you as an administrator until the next time you log out of the server.<br />
<br />
== Available commands ==<br />
<br />
'''/query metrics''': this command will show a simple metrics report of how the server has been performing. (available to non-administrators)<br />
<br />
'''/query netstats''': shows some network stats. (available to non-administrators)<br />
<br />
'''/query wml''': shows stats about WML documents and their current memory consumption. (available to non-administrators)<br />
<br />
'''/query status [<nickmask>]''': this command will show you a list of users (matching the nickmask) connected to the server, with IP addresses, and how long they have been connected. Note that IP addresses of users are not available to non-administrators, and should be treated as confidential. When used as a non-administrator it just returns the entry of the user.<br />
<br />
'''/query motd [<message>]''': this command sets the message of the day that appears as the first message users get when they log on to the server. Without argument it returns the current motd. (available to non-administrators)<br />
<br />
'''/query msg <message>''': this command will relay the message 'message' to all users on the server, even if they are in a game. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix your message with <red,green,blue> to color it, e.g. /query msg <255,255,0>message> for a yellow message.<br />
<br />
'''/query lobbymsg <message>''': this command will relay the message 'message' to all users in the lobby of the server. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix your message with <red,green,blue> to color it, e.g. /query msg <255,255,0>message> for a yellow message.<br />
<br />
'''/green <message>''': this command send the lobbysmg command with green font.<br />
<br />
'''/red <message>''': this command send the lobbysmg command with red font.<br />
<br />
'''/yellow <message>''': this command send the lobbysmg command with yellow font.<br />
<br />
'''/query kick <mask>''': this command will disconnect the user matching the given nick or ip mask from the server.<br />
<br />
'''/query ban <mask> [<time>] <reason>''': this command will make the server refuse connections from users matching the given ip mask or the ips of users matching the nick mask. When banning by nick mask already existing bans will not be overwritten. When banning by ip mask existing bans (and their reason!) will be overwritten so you can change the reason for a ban that way.<br />
<br />
'''/query gban <mask> <group> [<time>] <reason>''': this command will make ban that belongs to a group. It functions just like ordinary ban but ban listing just ignores them.<br />
<br />
'''/query bans''': shows a list of currently banned ip masks and the reasons for the bans.<br />
<br />
'''/query kban <mask> [<time>] <reason>''': this command is equivalent to 'kick <mask>' 'ban <mask> [<time] <reason>' -- i.e. bans the users matching the ip mask or the ips of users matching the nick mask and disconnects them all in one go. The most common way to ban someone from the server.<br />
<br />
'''/query unban <ipmask>''': this command removes the specified ip mask from the ban list.<br />
<br />
'''/query ungban <group>''': this command removes all bans in the group.<br />
<br />
'''/query searchlog <mask>''': this returns the IP a nick matching the mask has used or the nicks that an IP matching the used. Unlike status this searches the IP log.<br />
<br />
<br />
Masks are arguments that can contain wildcards ('*' and '?'). '*' matches any number of characters (including none), and '?' any one character. Ip masks are masks that contain at least one '.'.<br />
<br />
The time parameter is used to set the time when a ban expires. A simple example is 2D12h which means after 2 days and 12 hours the ban gets removed. Modifiers are: s=seconds, m=minutes, h=hours, D=days, M=months and Y=years (short times with lowercase and long times with uppercase). We can also set shortcuts like LONG, MEDIUM and SHORT for common ban lengths but none is set yet.<br />
<br />
== Future extensions ==<br />
<br />
The current administrative interface is fairly primitive. We plan to provide some further extensions in the future, such as,<br />
<br />
'''/query mute <nick>''': makes it so that any messages sent by the user with the given nick will not be received by any other user on the server unless they share an IP address with 'nick'. Any games created by 'nick' will likewise not be seen by other users. 'nick' may observe games but will not appear in the observer list, and players of the game will not see any messages they type.<br />
<br />
[[Category:Troubleshooting and Bugs]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=ServerAdministration&diff=27698ServerAdministration2008-12-23T19:18:02Z<p>Baufo: /* Available commands */</p>
<hr />
<div>== Overview ==<br />
<br />
The Wesnoth server, wesnothd provides a simple interface for administering the server from within the game itself.<br />
<br />
To issue an administrative command to the server, you must be connected to the server using Wesnoth, and in the lobby. Any text you type into the chat box that begins with '/query ' will be considered an administrative command instead of a normal chat message. It will not be relayed to other users, but instead treated as a command by the server.<br />
<br />
Most commands are not accessible to normal users. They are only accessible once you have authenticated yourself to the server as an administrator. The way to authenticate yourself as an administrator is to use the command,<br />
<br />
'''/query <password>'''<br />
<br />
where <password> is the administrative password to the server. The administrative password is specified as the passwd attribute in wesnothd.cfg. By convention, it will generally start with 'admin ' followed by the actual password, so the usual syntax to authenticate yourself is,<br />
<br />
'''/query admin <passwd>'''<br />
<br />
Naturally the password for a server should be kept a secret. One danger is that if you forget to type '/query ' at the start of a command you may accidentally type the password in a chat message, and let all users on the server know it. If you do this, then notify an administrator who has access to the box as soon as possible, so they can reset the password in wesnothd.cfg. We may provide features to prevent this kind of accident in future versions.<br />
<br />
A message from the server should tell you that you have successfully authenticated yourself as an administrator. The server will recognize you as an administrator until the next time you log out of the server.<br />
<br />
== Available commands ==<br />
<br />
'''/query metrics''': this command will show a simple metrics report of how the server has been performing. (available to non-administrators)<br />
<br />
'''/query netstats''': shows some network stats. (available to non-administrators)<br />
<br />
'''/query wml''': shows stats about WML documents and their current memory consumption. (available to non-administrators)<br />
<br />
'''/query status [<nickmask>]''': this command will show you a list of users (matching the nickmask) connected to the server, with IP addresses, and how long they have been connected. Note that IP addresses of users are not available to non-administrators, and should be treated as confidential. When used as a non-administrator it just returns the entry of the user.<br />
<br />
'''/query motd [<message>]''': this command sets the message of the day that appears as the first message users get when they log on to the server. Without argument it returns the current motd. (available to non-administrators)<br />
<br />
'''/query msg <message>''': this command will relay the message 'message' to all users on the server, even if they are in a game. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix your message with <red,green,blue> to color it, e.g. /query msg <255,255,0>message> for a yellow message.<br />
<br />
'''/query lobbymsg <message>''': this command will relay the message 'message' to all users in the lobby of the server. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix your message with <red,green,blue> to color it, e.g. /query msg <255,255,0>message> for a yellow message.<br />
<br />
'''/query green <message>''': this command send the lobbysmg command with green font.<br />
<br />
'''/query red <message>''': this command send the lobbysmg command with red font.<br />
<br />
'''/query yellow <message>''': this command send the lobbysmg command with yellow font.<br />
<br />
'''/query kick <mask>''': this command will disconnect the user matching the given nick or ip mask from the server.<br />
<br />
'''/query ban <mask> [<time>] <reason>''': this command will make the server refuse connections from users matching the given ip mask or the ips of users matching the nick mask. When banning by nick mask already existing bans will not be overwritten. When banning by ip mask existing bans (and their reason!) will be overwritten so you can change the reason for a ban that way.<br />
<br />
'''/query gban <mask> <group> [<time>] <reason>''': this command will make ban that belongs to a group. It functions just like ordinary ban but ban listing just ignores them.<br />
<br />
'''/query bans''': shows a list of currently banned ip masks and the reasons for the bans.<br />
<br />
'''/query kban <mask> [<time>] <reason>''': this command is equivalent to 'kick <mask>' 'ban <mask> [<time] <reason>' -- i.e. bans the users matching the ip mask or the ips of users matching the nick mask and disconnects them all in one go. The most common way to ban someone from the server.<br />
<br />
'''/query unban <ipmask>''': this command removes the specified ip mask from the ban list.<br />
<br />
'''/query ungban <group>''': this command removes all bans in the group.<br />
<br />
'''/query searchlog <mask>''': this returns the IP a nick matching the mask has used or the nicks that an IP matching the used. Unlike status this searches the IP log.<br />
<br />
<br />
Masks are arguments that can contain wildcards ('*' and '?'). '*' matches any number of characters (including none), and '?' any one character. Ip masks are masks that contain at least one '.'.<br />
<br />
The time parameter is used to set the time when a ban expires. A simple example is 2D12h which means after 2 days and 12 hours the ban gets removed. Modifiers are: s=seconds, m=minutes, h=hours, D=days, M=months and Y=years (short times with lowercase and long times with uppercase). We can also set shortcuts like LONG, MEDIUM and SHORT for common ban lengths but none is set yet.<br />
<br />
== Future extensions ==<br />
<br />
The current administrative interface is fairly primitive. We plan to provide some further extensions in the future, such as,<br />
<br />
'''/query mute <nick>''': makes it so that any messages sent by the user with the given nick will not be received by any other user on the server unless they share an IP address with 'nick'. Any games created by 'nick' will likewise not be seen by other users. 'nick' may observe games but will not appear in the observer list, and players of the game will not see any messages they type.<br />
<br />
[[Category:Troubleshooting and Bugs]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=ServerAdministration&diff=26781ServerAdministration2008-09-21T18:31:16Z<p>Baufo: /* Available commands */</p>
<hr />
<div>== Overview ==<br />
<br />
The Wesnoth server, wesnothd provides a simple interface for administering the server from within the game itself.<br />
<br />
To issue an administrative command to the server, you must be connected to the server using Wesnoth, and in the lobby. Any text you type into the chat box that begins with '/query ' will be considered an administrative command instead of a normal chat message. It will not be relayed to other users, but instead treated as a command by the server.<br />
<br />
Most commands are not accessible to normal users. They are only accessible once you have authenticated yourself to the server as an administrator. The way to authenticate yourself as an administrator is to use the command,<br />
<br />
'''/query <password>'''<br />
<br />
where <password> is the administrative password to the server. The administrative password is specified as the passwd attribute in wesnothd.cfg. By convention, it will generally start with 'admin ' followed by the actual password, so the usual syntax to authenticate yourself is,<br />
<br />
'''/query admin <passwd>'''<br />
<br />
Naturally the password for a server should be kept a secret. One danger is that if you forget to type '/query ' at the start of a command you may accidentally type the password in a chat message, and let all users on the server know it. If you do this, then notify an administrator who has access to the box as soon as possible, so they can reset the password in wesnothd.cfg. We may provide features to prevent this kind of accident in future versions.<br />
<br />
A message from the server should tell you that you have successfully authenticated yourself as an administrator. The server will recognize you as an administrator until the next time you log out of the server.<br />
<br />
== Available commands ==<br />
<br />
'''/query metrics''': this command will show a simple metrics report of how the server has been performing. (available to non-administrators)<br />
<br />
'''/query netstats''': shows some network stats. (available to non-administrators)<br />
<br />
'''/query wml''': shows stats about WML documents and their current memory consumption. (available to non-administrators)<br />
<br />
'''/query status [<nickmask>]''': this command will show you a list of users (matching the nickmask) connected to the server, with IP addresses, and how long they have been connected. Note that IP addresses of users are not available to non-administrators, and should be treated as confidential. When used as a non-administrator it just returns the entry of the user.<br />
<br />
'''/query motd [<message>]''': this command sets the message of the day that appears as the first message users get when they log on to the server. Without argument it returns the current motd. (available to non-administrators)<br />
<br />
'''/query msg <message>''': this command will relay the message 'message' to all users on the server, even if they are in a game. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from.<br />
<br />
'''/query lobbymsg <message>''': this command will relay the message 'message' to all users in the lobby of the server. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from.<br />
<br />
'''/query kick <mask>''': this command will disconnect the user matching the given nick or ip mask from the server.<br />
<br />
'''/query ban <mask> [<time>] <reason>''': this command will make the server refuse connections from users matching the given ip mask or the ips of users matching the nick mask. When banning by nick mask already existing bans will not be overwritten. When banning by ip mask existing bans (and their reason!) will be overwritten so you can change the reason for a ban that way.<br />
<br />
'''/query gban <mask> <group> [<time>] <reason>''': this command will make ban that belongs to a group. It functions just like ordinary ban but ban listing just ignores them.<br />
<br />
'''/query bans''': shows a list of currently banned ip masks and the reasons for the bans.<br />
<br />
'''/query kban <mask> [<time>] <reason>''': this command is equivalent to 'kick <mask>' 'ban <mask> [<time] <reason>' -- i.e. bans the users matching the ip mask or the ips of users matching the nick mask and disconnects them all in one go. The most common way to ban someone from the server.<br />
<br />
'''/query unban <ipmask>''': this command removes the specified ip mask from the ban list.<br />
<br />
'''/query ungban <group>''': this command removes all bans in the group.<br />
<br />
'''/query searchlog <mask>''': this returns the IP a nick matching the mask has used or the nicks that an IP matching the used. Unlike status this searches the IP log.<br />
<br />
<br />
Masks are arguments that can contain wildcards ('*' and '?'). '*' matches any number of characters (including none), and '?' any one character. Ip masks are masks that contain at least one '.'.<br />
<br />
The time parameter is used to set the time when a ban expires. A simple example is 2D12h which means after 2 days and 12 hours the ban gets removed. Modifiers are: s=seconds, m=minutes, h=hours, D=days, M=months and Y=years (short times with lowercase and long times with uppercase). We can also set shortcuts like LONG, MEDIUM and SHORT for common ban lengths but none is set yet.<br />
<br />
== Future extensions ==<br />
<br />
The current administrative interface is fairly primitive. We plan to provide some further extensions in the future, such as,<br />
<br />
'''/query mute <nick>''': makes it so that any messages sent by the user with the given nick will not be received by any other user on the server unless they share an IP address with 'nick'. Any games created by 'nick' will likewise not be seen by other users. 'nick' may observe games but will not appear in the observer list, and players of the game will not see any messages they type.<br />
<br />
[[Category:Troubleshooting and Bugs]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=ServerAdministration&diff=26780ServerAdministration2008-09-21T18:17:17Z<p>Baufo: /* Available commands */</p>
<hr />
<div>== Overview ==<br />
<br />
The Wesnoth server, wesnothd provides a simple interface for administering the server from within the game itself.<br />
<br />
To issue an administrative command to the server, you must be connected to the server using Wesnoth, and in the lobby. Any text you type into the chat box that begins with '/query ' will be considered an administrative command instead of a normal chat message. It will not be relayed to other users, but instead treated as a command by the server.<br />
<br />
Most commands are not accessible to normal users. They are only accessible once you have authenticated yourself to the server as an administrator. The way to authenticate yourself as an administrator is to use the command,<br />
<br />
'''/query <password>'''<br />
<br />
where <password> is the administrative password to the server. The administrative password is specified as the passwd attribute in wesnothd.cfg. By convention, it will generally start with 'admin ' followed by the actual password, so the usual syntax to authenticate yourself is,<br />
<br />
'''/query admin <passwd>'''<br />
<br />
Naturally the password for a server should be kept a secret. One danger is that if you forget to type '/query ' at the start of a command you may accidentally type the password in a chat message, and let all users on the server know it. If you do this, then notify an administrator who has access to the box as soon as possible, so they can reset the password in wesnothd.cfg. We may provide features to prevent this kind of accident in future versions.<br />
<br />
A message from the server should tell you that you have successfully authenticated yourself as an administrator. The server will recognize you as an administrator until the next time you log out of the server.<br />
<br />
== Available commands ==<br />
<br />
'''/query metrics''': this command will show a simple metrics report of how the server has been performing. (available to non-administrators)<br />
<br />
'''/query netstats''': shows some network stats. (available to non-administrators)<br />
<br />
'''/query wml''': shows stats about WML documents and their current memory consumption. (available to non-administrators)<br />
<br />
'''/query status [<nickmask>]''': this command will show you a list of users (matching the nickmask) connected to the server, with IP addresses, and how long they have been connected. Note that IP addresses of users are not available to non-administrators, and should be treated as confidential. When used as a non-administrator it just returns the entry of the user.<br />
<br />
'''/query motd [<message>]''': this command sets the message of the day that appears as the first message users get when they log on to the server. Without argument it returns the current motd. (available to non-administrators)<br />
<br />
'''/query msg <message>''': this command will relay the message 'message' to all users on the server, even if they are in a game. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from.<br />
<br />
'''/query lobbymsg <message>''': this command will relay the message 'message' to all users in the lobby of the server. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from.<br />
<br />
'''/query kick <mask>''': this command will disconnect the user matching the given nick or ip mask from the server.<br />
<br />
'''/query ban <mask> [<time>] <reason>''': this command will make the server refuse connections from users matching the given ip mask or the ips of users matching the nick mask. When banning by nick mask already existing bans will not be overwritten. When banning by ip mask existing bans (and their reason!) will be overwritten so you can change the reason for a ban that way.<br />
<br />
'''/query gban <mask> <group> [<time>] <reason>''': this command will make ban that belongs to a group. It functions just like ordinary ban but ban listing just ignores them.<br />
<br />
'''/query bans''': shows a list of currently banned ip masks and the reasons for the bans.<br />
<br />
'''/query kban <mask> [<time>] <reason>''': this command is equivalent to 'kick <mask>' 'ban <mask> [<time] <reason>' -- i.e. bans the users matching the ip mask or the ips of users matching the nick mask and disconnects them all in one go. The most common way to ban someone from the server.<br />
<br />
'''/query unban <ipmask>''': this command removes the specified ip mask from the ban list.<br />
<br />
'''/query ungban <group>''': this command removes all bans in the group.<br />
<br />
'''/query lookup <mask>''': this returns the IP a nick matching the mask has used or the nicks that an IP matching the used. Unlike status this searches the IP log.<br />
<br />
<br />
Masks are arguments that can contain wildcards ('*' and '?'). '*' matches any number of characters (including none), and '?' any one character. Ip masks are masks that contain at least one '.'.<br />
<br />
The time parameter is used to set the time when a ban expires. A simple example is 2D12h which means after 2 days and 12 hours the ban gets removed. Modifiers are: s=seconds, m=minutes, h=hours, D=days, M=months and Y=years (short times with lowercase and long times with uppercase). We can also set shortcuts like LONG, MEDIUM and SHORT for common ban lengths but none is set yet.<br />
<br />
== Future extensions ==<br />
<br />
The current administrative interface is fairly primitive. We plan to provide some further extensions in the future, such as,<br />
<br />
'''/query mute <nick>''': makes it so that any messages sent by the user with the given nick will not be received by any other user on the server unless they share an IP address with 'nick'. Any games created by 'nick' will likewise not be seen by other users. 'nick' may observe games but will not appear in the observer list, and players of the game will not see any messages they type.<br />
<br />
[[Category:Troubleshooting and Bugs]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=ServerAdministration&diff=26773ServerAdministration2008-09-21T16:36:20Z<p>Baufo: added lookup command</p>
<hr />
<div>== Overview ==<br />
<br />
The Wesnoth server, wesnothd provides a simple interface for administering the server from within the game itself.<br />
<br />
To issue an administrative command to the server, you must be connected to the server using Wesnoth, and in the lobby. Any text you type into the chat box that begins with '/query ' will be considered an administrative command instead of a normal chat message. It will not be relayed to other users, but instead treated as a command by the server.<br />
<br />
Most commands are not accessible to normal users. They are only accessible once you have authenticated yourself to the server as an administrator. The way to authenticate yourself as an administrator is to use the command,<br />
<br />
'''/query <password>'''<br />
<br />
where <password> is the administrative password to the server. The administrative password is specified as the passwd attribute in wesnothd.cfg. By convention, it will generally start with 'admin ' followed by the actual password, so the usual syntax to authenticate yourself is,<br />
<br />
'''/query admin <passwd>'''<br />
<br />
Naturally the password for a server should be kept a secret. One danger is that if you forget to type '/query ' at the start of a command you may accidentally type the password in a chat message, and let all users on the server know it. If you do this, then notify an administrator who has access to the box as soon as possible, so they can reset the password in wesnothd.cfg. We may provide features to prevent this kind of accident in future versions.<br />
<br />
A message from the server should tell you that you have successfully authenticated yourself as an administrator. The server will recognize you as an administrator until the next time you log out of the server.<br />
<br />
== Available commands ==<br />
<br />
'''/query metrics''': this command will show a simple metrics report of how the server has been performing. (available to non-administrators)<br />
<br />
'''/query netstats''': shows some network stats. (available to non-administrators)<br />
<br />
'''/query wml''': shows stats about WML documents and their current memory consumption. (available to non-administrators)<br />
<br />
'''/query status [<nickmask>]''': this command will show you a list of users (matching the nickmask) connected to the server, with IP addresses, and how long they have been connected. Note that IP addresses of users are not available to non-administrators, and should be treated as confidential. When used as a non-administrator it just returns the entry of the user.<br />
<br />
'''/query motd [<message>]''': this command sets the message of the day that appears as the first message users get when they log on to the server. Without argument it returns the current motd. (available to non-administrators)<br />
<br />
'''/query msg <message>''': this command will relay the message 'message' to all users on the server, even if they are in a game. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from.<br />
<br />
'''/query lobbymsg <message>''': this command will relay the message 'message' to all users in the lobby of the server. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from.<br />
<br />
'''/query kick <mask>''': this command will disconnect the user matching the given nick or ip mask from the server.<br />
<br />
'''/query ban <mask> [<time>] <reason>''': this command will make the server refuse connections from users matching the given ip mask or the ips of users matching the nick mask. When banning by nick mask already existing bans will not be overwritten. When banning by ip mask existing bans (and their reason!) will be overwritten so you can change the reason for a ban that way.<br />
<br />
'''/query gban <mask> <group> [<time>] <reason>''': this command will make ban that belongs to a group. It functions just like ordinary ban but ban listing just ignores them.<br />
<br />
'''/query bans''': shows a list of currently banned ip masks and the reasons for the bans.<br />
<br />
'''/query kban <mask> [<time>] <reason>''': this command is equivalent to 'kick <mask>' 'ban <mask> [<time] <reason>' -- i.e. bans the users matching the ip mask or the ips of users matching the nick mask and disconnects them all in one go. The most common way to ban someone from the server.<br />
<br />
'''/query unban <ipmask>''': this command removes the specified ip mask from the ban list.<br />
<br />
'''/query ungban <group>''': this command removes all bans in the group.<br />
<br />
'''/query lookup <mask>''': this returns the IP a nick matching the mask has used or the nicks that an IP matching the used.<br />
<br />
<br />
Masks are arguments that can contain wildcards ('*' and '?'). '*' matches any number of characters (including none), and '?' any one character. Ip masks are masks that contain at least one '.'.<br />
<br />
The time parameter is used to set the time when a ban expires. A simple example is 2D12h which means after 2 days and 12 hours the ban gets removed. Modifiers are: s=seconds, m=minutes, h=hours, D=days, M=months and Y=years (short times with lowercase and long times with uppercase). We can also set shortcuts like LONG, MEDIUM and SHORT for common ban lengths but none is set yet.<br />
<br />
== Future extensions ==<br />
<br />
The current administrative interface is fairly primitive. We plan to provide some further extensions in the future, such as,<br />
<br />
'''/query mute <nick>''': makes it so that any messages sent by the user with the given nick will not be received by any other user on the server unless they share an IP address with 'nick'. Any games created by 'nick' will likewise not be seen by other users. 'nick' may observe games but will not appear in the observer list, and players of the game will not see any messages they type.<br />
<br />
[[Category:Troubleshooting and Bugs]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=MultiplayerServerWML&diff=26708MultiplayerServerWML2008-09-13T17:05:51Z<p>Baufo: </p>
<hr />
<div>= Multiplayer Server WML =<br />
This page describes the WML used to communicate with the multiplayer server (wesnothd).<br />
<br />
== The login procedure ==<br />
<br />
* server request (optional)<br />
** '''[version]'''<br />
<br />
* client response<br />
** '''[version]'''<br />
*** '''version''': The client's version string.<br />
<br />
* server request<br />
** '''[mustlogin]'''<br />
<br />
* client response<br />
** '''[login]'''<br />
*** '''username''': The username the client would like to have.<br />
*** '''password_reminder''': If "yes" the client requests the server to send a password reminder for the provided username.<br />
*** '''password''': The hashed password, created from the username, the password and salt received from the server.<br />
<br />
* server response<br />
** '''[join_lobby]'''<br />
** or<br />
** '''[error]'''<br />
*** '''message''': The error message.<br />
*** '''password_request''': If not empty the server asks the client to provide a password for its desired username<br />
*** '''random_salt''': Random salt sent to the client for mixing with the password hash.<br />
*** '''hash_seed''': Salt generated from the original hash that is required to recreate it.<br />
*** '''salt''': Salt generated from the original hash that is required to recreate it.<br />
<br />
* server response<br />
** '''[gamelist]'''<br />
*** '''[game]''' (repeated)<br />
**** '''id''': A unique id of the game.<br />
**** '''name''': The title of the game.<br />
**** '''mp_scenario''': The id of the scenario.<br />
**** '''mp_era''': The id of the used era.<br />
**** ''mp_use_map_settings''': Does the game use the map settings specified in the scenario.<br />
**** '''mp_fog''': Does the game use fog.<br />
**** '''mp_shroud''': Does the game use shroud.<br />
**** '''mp_village_gold''': The number of gold per village.<br />
**** '''experience_modifier''': The experience setting.<br />
**** '''mp_countdown''': Does the game use a timer.<br />
**** '''mp_countdown_reservoir_time''': Upper limit of the possibly available time.<br />
**** '''mp_countdown_init_time''': Initial time.<br />
**** '''mp_countdown_action_bonus''': Time bonus per action.<br />
**** '''mp_countdown_turn_bonus''': Time bonus per turn.<br />
**** '''map_data''': The map data.<br />
**** '''hash''': The hash value of the map_data.<br />
**** '''observer''': Are observers allowed or not.<br />
**** '''human_sides''': The number of sides played by humans.<br />
**** '''slots''': The number of vacant/max slots.<br />
**** '''turn''': The current turn/max turn.<br />
** '''[user]''' (repeated)<br />
*** '''name''': The username of the player.<br />
*** '''game_id''': The ID of the game the player is in (version 1.3.7+svn).<br />
*** '''location''': The name of the game the player is in.<br />
*** '''available''': "yes" if the player is in the lobby; "no" if in a game.<br />
Many of the keys under [game] are described more indepth on the [[ScenarioWML]] page.<br />
<br />
== Error messages ==<br />
<br />
* '''[error]'''<br />
** '''message''': The error message.<br />
<br />
== Chat (lobby and in-game) ==<br />
<br />
* '''[message]'''<br />
** '''sender''': (optional - filled by the server) The sender of the message.<br />
** '''message''': The message itself.<br />
* '''[whisper]'''<br />
** '''receiver''': The receiver of the whisper<br />
** '''sender''': (optional - filled by the server) The sender of the whisper.<br />
** '''message''': The message itself.<br />
<br />
== Nick registration related commands (lobby and in-game) ==<br />
<br />
* '''[nickserv]'''<br />
** '''[register]'''<br />
*** '''password''': The password for the nick.<br />
*** '''mail''': The email address for the nick.<br />
** '''[drop]''': Drop this username.<br />
** '''[set]''': Set a detail (e.g. email address) for this nick.<br />
*** '''detail''': The detail, e.g. "mail".<br />
*** '''value''': The new value for this detail, e.g. "user@edomain"<br />
** '''[info]''': Request info about another username.<br />
*** '''name''': The username.<br />
<br />
== Updating the lobby state ==<br />
<br />
* '''[gamelist_diff]''': server message - basically a diff from two [gamelist]s; the keys listed are the ones that actually occure in practice<br />
** '''index''': The index of a user.<br />
** '''[insert_child]''' A new user logged on.<br />
*** '''[user]'''<br />
**** '''name''': The name of the user.<br />
**** ''available'' "yes"<br />
*** '''[delete_child]''' A user logged off.<br />
** '''[change_child]'''<br />
*** '''[user]'''<br />
**** '''[insert]''': A user joined/left a game.<br />
***** '''available''': "yes" when the user left a game. "no" when the user joined a game<br />
***** '''location''': The name of the game the user joined.<br />
**** '''[delete]'''<br />
***** '''location''': "x" when a game was left.<br />
*** '''[gamelist]'''<br />
**** '''index''': Index of the game in question.<br />
**** '''[insert_child]''': A game started.<br />
***** '''[game]''' All the usual keys of [game] possible, see above.<br />
**** '''[delete_child]''': A game ended.<br />
***** '''[game]'''<br />
**** '''[change_child]''': Something changed in a game.<br />
***** '''[game]'''<br />
****** '''[insert]'''<br />
******* '''slots''': The number of free slots in the form: free/max slots<br />
******* '''turn''': The turn number in the form: current turn/max turns<br />
****** '''[delete]'''<br />
******* '''map''': "x" comes with every ''turn'' or ''slots'' change for games with shroud<br />
******* '''mp_scenario''': "x" comes with ''turn'' and ''slots'' changes for games with no scenario id<br />
<br />
* '''[observer]''' or '''[observer_quit]''': server message - players joining([observer_quit] - quitting the lobby "game")/quitting([observer] - joining the lobby "game") a game<br />
** '''name''': Username of the player/observer.<br />
<br />
== Game setup (the phase from creation to start) ==<br />
To create a game the client sends:<br />
* '''[create_game]'''<br />
** '''name''': The title of the game.<br />
<br />
followed by a message with the scenario options as under [game] (see above) plus the scenario data ([time], [era], [side], etc. see [[ScenarioWML]])<br />
<br />
* '''[join]'''<br />
** '''id''': The id of the game.<br />
** '''observe''': Join the game as an observer.<br />
<br />
* '''[scenario_diff]''': [[ScenarioWML]] diff (side changes, etc.)<br />
<br />
* '''[start_game]''': sent by the host to start a game<br />
* '''[leave_game]''': sent by the client when it leaves a game; sent by the server to make a client leave a game<br />
<br />
== In-game communication ==<br />
<br />
* '''[store_next_scenario]''': sent by the host - the scenario data (see [[ScenarioWML]]) to advance to the next scenario<br />
* '''[load_next_scenario]''': sent by the client to request the data for the next scenario<br />
* '''[next_scenario]''': data for the next scenario (see [[ScenarioWML]]), sent by the server on request<br />
<br />
* '''[info]''': sent by the host on game end - info about the game state<br />
** '''type''': "termination" <br />
** '''condition''': the termination reason<br />
<br />
* '''[change_controller]''': a player gives away one of his sides<br />
** '''side''': the side to change controller<br />
** '''player''': the nick of the player to take control<br />
** '''own_side''': "yes"<br />
<br />
If a player leaves this is sent to the host for all sides he owned.<br />
* '''side_drop''': The number of a side that dropped because a player left.<br />
* '''controller''': The controller of that side. ("human", "ai", "network", "none")<br />
<br />
* '''[muteall]''': the host mutes/unmutes all observers - toggles<br />
* '''[mute]''': the host mutes an observer - toggles<br />
** '''username''': the username of the observer - if not specified the servers returns a list of muted usernames<br />
* '''[kick]''' or '''[ban]''': the host kicks/bans a player/observer<br />
** '''username''': the username of the player/observer<br />
<br />
* '''[turn]'''<br />
** '''[command]''': (repeated) can contain all the tags you can find in a replay: [recruit], [move], [end_turn], etc.<br />
*** '''[speak]'''<br />
**** '''message''': text of the message<br />
**** '''description''': the sender (in 1.4 and earlier; later replaced by '''id''')<br />
**** '''id''': the sender {{DevFeature}}<br />
**** '''team_name''': the name of the team the message is for - empty if it's a public message<br />
<br />
== Administrative commands ==<br />
* '''[query]'''<br />
** '''type''': The type of query. See [[ServerAdministration]] for details.<br />
<br />
[[Category:WML Reference]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=MultiplayerServerWML&diff=26707MultiplayerServerWML2008-09-13T16:58:23Z<p>Baufo: /* The login procedure */</p>
<hr />
<div>= Multiplayer Server WML =<br />
This page describes the WML used to communicate with the multiplayer server (wesnothd).<br />
<br />
== The login procedure ==<br />
<br />
* server request (optional)<br />
** '''[version]'''<br />
<br />
* client response<br />
** '''[version]'''<br />
*** '''version''': The client's version string.<br />
<br />
* server request<br />
** '''[mustlogin]'''<br />
<br />
* client response<br />
** '''[login]'''<br />
*** '''username''': The username the client would like to have.<br />
*** '''password_reminder''': If "yes" the client requests the server to send a password reminder for the provided username.<br />
*** '''password''': The hashed password, created from the username, the password and salt received from the server.<br />
<br />
* server response<br />
** '''[join_lobby]'''<br />
** or<br />
** '''[error]'''<br />
*** '''message''': The error message.<br />
*** '''password_request''': If not empty the server asks the client to provide a password for its desired username<br />
*** '''random_salt''': Random salt sent to the client for mixing with the password hash.<br />
*** '''hash_seed''': Salt generated from the original hash that is required to recreate it.<br />
*** '''salt''': Salt generated from the original hash that is required to recreate it.<br />
<br />
* server response<br />
** '''[gamelist]'''<br />
*** '''[game]''' (repeated)<br />
**** '''id''': A unique id of the game.<br />
**** '''name''': The title of the game.<br />
**** '''mp_scenario''': The id of the scenario.<br />
**** '''mp_era''': The id of the used era.<br />
**** ''mp_use_map_settings''': Does the game use the map settings specified in the scenario.<br />
**** '''mp_fog''': Does the game use fog.<br />
**** '''mp_shroud''': Does the game use shroud.<br />
**** '''mp_village_gold''': The number of gold per village.<br />
**** '''experience_modifier''': The experience setting.<br />
**** '''mp_countdown''': Does the game use a timer.<br />
**** '''mp_countdown_reservoir_time''': Upper limit of the possibly available time.<br />
**** '''mp_countdown_init_time''': Initial time.<br />
**** '''mp_countdown_action_bonus''': Time bonus per action.<br />
**** '''mp_countdown_turn_bonus''': Time bonus per turn.<br />
**** '''map_data''': The map data.<br />
**** '''hash''': The hash value of the map_data.<br />
**** '''observer''': Are observers allowed or not.<br />
**** '''human_sides''': The number of sides played by humans.<br />
**** '''slots''': The number of vacant/max slots.<br />
**** '''turn''': The current turn/max turn.<br />
** '''[user]''' (repeated)<br />
*** '''name''': The username of the player.<br />
*** '''game_id''': The ID of the game the player is in (version 1.3.7+svn).<br />
*** '''location''': The name of the game the player is in.<br />
*** '''available''': "yes" if the player is in the lobby; "no" if in a game.<br />
Many of the keys under [game] are described more indepth on the [[ScenarioWML]] page.<br />
<br />
== Error messages ==<br />
<br />
* '''[error]'''<br />
** '''message''': The error message.<br />
<br />
== Chat (lobby and in-game) ==<br />
<br />
* '''[message]'''<br />
** '''sender''': (optional - filled by the server) The sender of the message.<br />
** '''message''': The message itself.<br />
* '''[whisper]'''<br />
** '''receiver''': The receiver of the whisper<br />
** '''sender''': (optional - filled by the server) The sender of the whisper.<br />
** '''message''': The message itself.<br />
<br />
== Updating the lobby state ==<br />
<br />
* '''[gamelist_diff]''': server message - basically a diff from two [gamelist]s; the keys listed are the ones that actually occure in practice<br />
** '''index''': The index of a user.<br />
** '''[insert_child]''' A new user logged on.<br />
*** '''[user]'''<br />
**** '''name''': The name of the user.<br />
**** ''available'' "yes"<br />
*** '''[delete_child]''' A user logged off.<br />
** '''[change_child]'''<br />
*** '''[user]'''<br />
**** '''[insert]''': A user joined/left a game.<br />
***** '''available''': "yes" when the user left a game. "no" when the user joined a game<br />
***** '''location''': The name of the game the user joined.<br />
**** '''[delete]'''<br />
***** '''location''': "x" when a game was left.<br />
*** '''[gamelist]'''<br />
**** '''index''': Index of the game in question.<br />
**** '''[insert_child]''': A game started.<br />
***** '''[game]''' All the usual keys of [game] possible, see above.<br />
**** '''[delete_child]''': A game ended.<br />
***** '''[game]'''<br />
**** '''[change_child]''': Something changed in a game.<br />
***** '''[game]'''<br />
****** '''[insert]'''<br />
******* '''slots''': The number of free slots in the form: free/max slots<br />
******* '''turn''': The turn number in the form: current turn/max turns<br />
****** '''[delete]'''<br />
******* '''map''': "x" comes with every ''turn'' or ''slots'' change for games with shroud<br />
******* '''mp_scenario''': "x" comes with ''turn'' and ''slots'' changes for games with no scenario id<br />
<br />
* '''[observer]''' or '''[observer_quit]''': server message - players joining([observer_quit] - quitting the lobby "game")/quitting([observer] - joining the lobby "game") a game<br />
** '''name''': Username of the player/observer.<br />
<br />
== Game setup (the phase from creation to start) ==<br />
To create a game the client sends:<br />
* '''[create_game]'''<br />
** '''name''': The title of the game.<br />
<br />
followed by a message with the scenario options as under [game] (see above) plus the scenario data ([time], [era], [side], etc. see [[ScenarioWML]])<br />
<br />
* '''[join]'''<br />
** '''id''': The id of the game.<br />
** '''observe''': Join the game as an observer.<br />
<br />
* '''[scenario_diff]''': [[ScenarioWML]] diff (side changes, etc.)<br />
<br />
* '''[start_game]''': sent by the host to start a game<br />
* '''[leave_game]''': sent by the client when it leaves a game; sent by the server to make a client leave a game<br />
<br />
== In-game communication ==<br />
<br />
* '''[store_next_scenario]''': sent by the host - the scenario data (see [[ScenarioWML]]) to advance to the next scenario<br />
* '''[load_next_scenario]''': sent by the client to request the data for the next scenario<br />
* '''[next_scenario]''': data for the next scenario (see [[ScenarioWML]]), sent by the server on request<br />
<br />
* '''[info]''': sent by the host on game end - info about the game state<br />
** '''type''': "termination" <br />
** '''condition''': the termination reason<br />
<br />
* '''[change_controller]''': a player gives away one of his sides<br />
** '''side''': the side to change controller<br />
** '''player''': the nick of the player to take control<br />
** '''own_side''': "yes"<br />
<br />
If a player leaves this is sent to the host for all sides he owned.<br />
* '''side_drop''': The number of a side that dropped because a player left.<br />
* '''controller''': The controller of that side. ("human", "ai", "network", "none")<br />
<br />
* '''[muteall]''': the host mutes/unmutes all observers - toggles<br />
* '''[mute]''': the host mutes an observer - toggles<br />
** '''username''': the username of the observer - if not specified the servers returns a list of muted usernames<br />
* '''[kick]''' or '''[ban]''': the host kicks/bans a player/observer<br />
** '''username''': the username of the player/observer<br />
<br />
* '''[turn]'''<br />
** '''[command]''': (repeated) can contain all the tags you can find in a replay: [recruit], [move], [end_turn], etc.<br />
*** '''[speak]'''<br />
**** '''message''': text of the message<br />
**** '''description''': the sender (in 1.4 and earlier; later replaced by '''id''')<br />
**** '''id''': the sender {{DevFeature}}<br />
**** '''team_name''': the name of the team the message is for - empty if it's a public message<br />
<br />
== Administrative commands ==<br />
* '''[query]'''<br />
** '''type''': The type of query. See [[ServerAdministration]] for details.<br />
<br />
[[Category:WML Reference]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=MultiplayerServerWML&diff=26706MultiplayerServerWML2008-09-13T16:50:52Z<p>Baufo: /* The login procedure */</p>
<hr />
<div>= Multiplayer Server WML =<br />
This page describes the WML used to communicate with the multiplayer server (wesnothd).<br />
<br />
== The login procedure ==<br />
<br />
* server request (optional)<br />
** '''[version]'''<br />
<br />
* client response<br />
** '''[version]'''<br />
*** '''version''': The client's version string.<br />
<br />
* server request<br />
** '''[mustlogin]'''<br />
<br />
* client response<br />
** '''[login]'''<br />
*** '''username''': The username the client would like to have.<br />
*** '''password_reminder''': If "yes" the client requests the server to send a password reminder for the provided username.<br />
*** '''password''': The hashed password, created from the username, the password and salt received from the server.<br />
<br />
* server response<br />
** '''[join_lobby]'''<br />
<br />
* server response<br />
** '''[gamelist]'''<br />
*** '''[game]''' (repeated)<br />
**** '''id''': A unique id of the game.<br />
**** '''name''': The title of the game.<br />
**** '''mp_scenario''': The id of the scenario.<br />
**** '''mp_era''': The id of the used era.<br />
**** ''mp_use_map_settings''': Does the game use the map settings specified in the scenario.<br />
**** '''mp_fog''': Does the game use fog.<br />
**** '''mp_shroud''': Does the game use shroud.<br />
**** '''mp_village_gold''': The number of gold per village.<br />
**** '''experience_modifier''': The experience setting.<br />
**** '''mp_countdown''': Does the game use a timer.<br />
**** '''mp_countdown_reservoir_time''': Upper limit of the possibly available time.<br />
**** '''mp_countdown_init_time''': Initial time.<br />
**** '''mp_countdown_action_bonus''': Time bonus per action.<br />
**** '''mp_countdown_turn_bonus''': Time bonus per turn.<br />
**** '''map_data''': The map data.<br />
**** '''hash''': The hash value of the map_data.<br />
**** '''observer''': Are observers allowed or not.<br />
**** '''human_sides''': The number of sides played by humans.<br />
**** '''slots''': The number of vacant/max slots.<br />
**** '''turn''': The current turn/max turn.<br />
** '''[user]''' (repeated)<br />
*** '''name''': The username of the player.<br />
*** '''game_id''': The ID of the game the player is in (version 1.3.7+svn).<br />
*** '''location''': The name of the game the player is in.<br />
*** '''available''': "yes" if the player is in the lobby; "no" if in a game.<br />
Many of the keys under [game] are described more indepth on the [[ScenarioWML]] page.<br />
<br />
== Error messages ==<br />
<br />
* '''[error]'''<br />
** '''message''': The error message.<br />
<br />
== Chat (lobby and in-game) ==<br />
<br />
* '''[message]'''<br />
** '''sender''': (optional - filled by the server) The sender of the message.<br />
** '''message''': The message itself.<br />
* '''[whisper]'''<br />
** '''receiver''': The receiver of the whisper<br />
** '''sender''': (optional - filled by the server) The sender of the whisper.<br />
** '''message''': The message itself.<br />
<br />
== Updating the lobby state ==<br />
<br />
* '''[gamelist_diff]''': server message - basically a diff from two [gamelist]s; the keys listed are the ones that actually occure in practice<br />
** '''index''': The index of a user.<br />
** '''[insert_child]''' A new user logged on.<br />
*** '''[user]'''<br />
**** '''name''': The name of the user.<br />
**** ''available'' "yes"<br />
*** '''[delete_child]''' A user logged off.<br />
** '''[change_child]'''<br />
*** '''[user]'''<br />
**** '''[insert]''': A user joined/left a game.<br />
***** '''available''': "yes" when the user left a game. "no" when the user joined a game<br />
***** '''location''': The name of the game the user joined.<br />
**** '''[delete]'''<br />
***** '''location''': "x" when a game was left.<br />
*** '''[gamelist]'''<br />
**** '''index''': Index of the game in question.<br />
**** '''[insert_child]''': A game started.<br />
***** '''[game]''' All the usual keys of [game] possible, see above.<br />
**** '''[delete_child]''': A game ended.<br />
***** '''[game]'''<br />
**** '''[change_child]''': Something changed in a game.<br />
***** '''[game]'''<br />
****** '''[insert]'''<br />
******* '''slots''': The number of free slots in the form: free/max slots<br />
******* '''turn''': The turn number in the form: current turn/max turns<br />
****** '''[delete]'''<br />
******* '''map''': "x" comes with every ''turn'' or ''slots'' change for games with shroud<br />
******* '''mp_scenario''': "x" comes with ''turn'' and ''slots'' changes for games with no scenario id<br />
<br />
* '''[observer]''' or '''[observer_quit]''': server message - players joining([observer_quit] - quitting the lobby "game")/quitting([observer] - joining the lobby "game") a game<br />
** '''name''': Username of the player/observer.<br />
<br />
== Game setup (the phase from creation to start) ==<br />
To create a game the client sends:<br />
* '''[create_game]'''<br />
** '''name''': The title of the game.<br />
<br />
followed by a message with the scenario options as under [game] (see above) plus the scenario data ([time], [era], [side], etc. see [[ScenarioWML]])<br />
<br />
* '''[join]'''<br />
** '''id''': The id of the game.<br />
** '''observe''': Join the game as an observer.<br />
<br />
* '''[scenario_diff]''': [[ScenarioWML]] diff (side changes, etc.)<br />
<br />
* '''[start_game]''': sent by the host to start a game<br />
* '''[leave_game]''': sent by the client when it leaves a game; sent by the server to make a client leave a game<br />
<br />
== In-game communication ==<br />
<br />
* '''[store_next_scenario]''': sent by the host - the scenario data (see [[ScenarioWML]]) to advance to the next scenario<br />
* '''[load_next_scenario]''': sent by the client to request the data for the next scenario<br />
* '''[next_scenario]''': data for the next scenario (see [[ScenarioWML]]), sent by the server on request<br />
<br />
* '''[info]''': sent by the host on game end - info about the game state<br />
** '''type''': "termination" <br />
** '''condition''': the termination reason<br />
<br />
* '''[change_controller]''': a player gives away one of his sides<br />
** '''side''': the side to change controller<br />
** '''player''': the nick of the player to take control<br />
** '''own_side''': "yes"<br />
<br />
If a player leaves this is sent to the host for all sides he owned.<br />
* '''side_drop''': The number of a side that dropped because a player left.<br />
* '''controller''': The controller of that side. ("human", "ai", "network", "none")<br />
<br />
* '''[muteall]''': the host mutes/unmutes all observers - toggles<br />
* '''[mute]''': the host mutes an observer - toggles<br />
** '''username''': the username of the observer - if not specified the servers returns a list of muted usernames<br />
* '''[kick]''' or '''[ban]''': the host kicks/bans a player/observer<br />
** '''username''': the username of the player/observer<br />
<br />
* '''[turn]'''<br />
** '''[command]''': (repeated) can contain all the tags you can find in a replay: [recruit], [move], [end_turn], etc.<br />
*** '''[speak]'''<br />
**** '''message''': text of the message<br />
**** '''description''': the sender (in 1.4 and earlier; later replaced by '''id''')<br />
**** '''id''': the sender {{DevFeature}}<br />
**** '''team_name''': the name of the team the message is for - empty if it's a public message<br />
<br />
== Administrative commands ==<br />
* '''[query]'''<br />
** '''type''': The type of query. See [[ServerAdministration]] for details.<br />
<br />
[[Category:WML Reference]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=MultiplayerServerWML&diff=26705MultiplayerServerWML2008-09-13T16:50:15Z<p>Baufo: /* The login procedure */</p>
<hr />
<div>= Multiplayer Server WML =<br />
This page describes the WML used to communicate with the multiplayer server (wesnothd).<br />
<br />
== The login procedure ==<br />
<br />
* server request (optional)<br />
** '''[version]'''<br />
<br />
* client response<br />
** '''[version]'''<br />
*** '''version''': The client's version string.<br />
<br />
* server request<br />
** '''[mustlogin]'''<br />
<br />
* client response<br />
** '''[login]'''<br />
*** '''username''': The username the client would like to have.<br />
*** '''password_reminder''': If "yes" the client requests the server to send a password reminder for the provided.<br />
username.<br />
*** '''password''': The hashed password, created from the username, the password and salt received from the server.<br />
<br />
* server response<br />
** '''[join_lobby]'''<br />
<br />
* server response<br />
** '''[gamelist]'''<br />
*** '''[game]''' (repeated)<br />
**** '''id''': A unique id of the game.<br />
**** '''name''': The title of the game.<br />
**** '''mp_scenario''': The id of the scenario.<br />
**** '''mp_era''': The id of the used era.<br />
**** ''mp_use_map_settings''': Does the game use the map settings specified in the scenario.<br />
**** '''mp_fog''': Does the game use fog.<br />
**** '''mp_shroud''': Does the game use shroud.<br />
**** '''mp_village_gold''': The number of gold per village.<br />
**** '''experience_modifier''': The experience setting.<br />
**** '''mp_countdown''': Does the game use a timer.<br />
**** '''mp_countdown_reservoir_time''': Upper limit of the possibly available time.<br />
**** '''mp_countdown_init_time''': Initial time.<br />
**** '''mp_countdown_action_bonus''': Time bonus per action.<br />
**** '''mp_countdown_turn_bonus''': Time bonus per turn.<br />
**** '''map_data''': The map data.<br />
**** '''hash''': The hash value of the map_data.<br />
**** '''observer''': Are observers allowed or not.<br />
**** '''human_sides''': The number of sides played by humans.<br />
**** '''slots''': The number of vacant/max slots.<br />
**** '''turn''': The current turn/max turn.<br />
** '''[user]''' (repeated)<br />
*** '''name''': The username of the player.<br />
*** '''game_id''': The ID of the game the player is in (version 1.3.7+svn).<br />
*** '''location''': The name of the game the player is in.<br />
*** '''available''': "yes" if the player is in the lobby; "no" if in a game.<br />
Many of the keys under [game] are described more indepth on the [[ScenarioWML]] page.<br />
<br />
== Error messages ==<br />
<br />
* '''[error]'''<br />
** '''message''': The error message.<br />
<br />
== Chat (lobby and in-game) ==<br />
<br />
* '''[message]'''<br />
** '''sender''': (optional - filled by the server) The sender of the message.<br />
** '''message''': The message itself.<br />
* '''[whisper]'''<br />
** '''receiver''': The receiver of the whisper<br />
** '''sender''': (optional - filled by the server) The sender of the whisper.<br />
** '''message''': The message itself.<br />
<br />
== Updating the lobby state ==<br />
<br />
* '''[gamelist_diff]''': server message - basically a diff from two [gamelist]s; the keys listed are the ones that actually occure in practice<br />
** '''index''': The index of a user.<br />
** '''[insert_child]''' A new user logged on.<br />
*** '''[user]'''<br />
**** '''name''': The name of the user.<br />
**** ''available'' "yes"<br />
*** '''[delete_child]''' A user logged off.<br />
** '''[change_child]'''<br />
*** '''[user]'''<br />
**** '''[insert]''': A user joined/left a game.<br />
***** '''available''': "yes" when the user left a game. "no" when the user joined a game<br />
***** '''location''': The name of the game the user joined.<br />
**** '''[delete]'''<br />
***** '''location''': "x" when a game was left.<br />
*** '''[gamelist]'''<br />
**** '''index''': Index of the game in question.<br />
**** '''[insert_child]''': A game started.<br />
***** '''[game]''' All the usual keys of [game] possible, see above.<br />
**** '''[delete_child]''': A game ended.<br />
***** '''[game]'''<br />
**** '''[change_child]''': Something changed in a game.<br />
***** '''[game]'''<br />
****** '''[insert]'''<br />
******* '''slots''': The number of free slots in the form: free/max slots<br />
******* '''turn''': The turn number in the form: current turn/max turns<br />
****** '''[delete]'''<br />
******* '''map''': "x" comes with every ''turn'' or ''slots'' change for games with shroud<br />
******* '''mp_scenario''': "x" comes with ''turn'' and ''slots'' changes for games with no scenario id<br />
<br />
* '''[observer]''' or '''[observer_quit]''': server message - players joining([observer_quit] - quitting the lobby "game")/quitting([observer] - joining the lobby "game") a game<br />
** '''name''': Username of the player/observer.<br />
<br />
== Game setup (the phase from creation to start) ==<br />
To create a game the client sends:<br />
* '''[create_game]'''<br />
** '''name''': The title of the game.<br />
<br />
followed by a message with the scenario options as under [game] (see above) plus the scenario data ([time], [era], [side], etc. see [[ScenarioWML]])<br />
<br />
* '''[join]'''<br />
** '''id''': The id of the game.<br />
** '''observe''': Join the game as an observer.<br />
<br />
* '''[scenario_diff]''': [[ScenarioWML]] diff (side changes, etc.)<br />
<br />
* '''[start_game]''': sent by the host to start a game<br />
* '''[leave_game]''': sent by the client when it leaves a game; sent by the server to make a client leave a game<br />
<br />
== In-game communication ==<br />
<br />
* '''[store_next_scenario]''': sent by the host - the scenario data (see [[ScenarioWML]]) to advance to the next scenario<br />
* '''[load_next_scenario]''': sent by the client to request the data for the next scenario<br />
* '''[next_scenario]''': data for the next scenario (see [[ScenarioWML]]), sent by the server on request<br />
<br />
* '''[info]''': sent by the host on game end - info about the game state<br />
** '''type''': "termination" <br />
** '''condition''': the termination reason<br />
<br />
* '''[change_controller]''': a player gives away one of his sides<br />
** '''side''': the side to change controller<br />
** '''player''': the nick of the player to take control<br />
** '''own_side''': "yes"<br />
<br />
If a player leaves this is sent to the host for all sides he owned.<br />
* '''side_drop''': The number of a side that dropped because a player left.<br />
* '''controller''': The controller of that side. ("human", "ai", "network", "none")<br />
<br />
* '''[muteall]''': the host mutes/unmutes all observers - toggles<br />
* '''[mute]''': the host mutes an observer - toggles<br />
** '''username''': the username of the observer - if not specified the servers returns a list of muted usernames<br />
* '''[kick]''' or '''[ban]''': the host kicks/bans a player/observer<br />
** '''username''': the username of the player/observer<br />
<br />
* '''[turn]'''<br />
** '''[command]''': (repeated) can contain all the tags you can find in a replay: [recruit], [move], [end_turn], etc.<br />
*** '''[speak]'''<br />
**** '''message''': text of the message<br />
**** '''description''': the sender (in 1.4 and earlier; later replaced by '''id''')<br />
**** '''id''': the sender {{DevFeature}}<br />
**** '''team_name''': the name of the team the message is for - empty if it's a public message<br />
<br />
== Administrative commands ==<br />
* '''[query]'''<br />
** '''type''': The type of query. See [[ServerAdministration]] for details.<br />
<br />
[[Category:WML Reference]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=User:Baufo&diff=16433User:Baufo2007-07-14T09:15:19Z<p>Baufo: </p>
<hr />
<div>* Name: Thomas Baumhauer<br />
* Location: Vienna, Austria<br />
* [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=102738 Forum profile]<br />
* Email: [mailto:baufo_ATTHEHOST_gmx_DOT_at baufo ATTHEHOST gmx DOT at]<br />
* Weblog: [http://baufo.freehostia.com Baufo Speaks]<br />
<br />
== Contributions ==<br />
* Multiplayer content<br />
** Defense of the Goblin ([http://www.wesnoth.org/forum/viewtopic.php?t=12566 forum thread])<br />
** The Dwarvish Treasure ([http://www.wesnoth.org/forum/viewtopic.php?t=12681 forum thread])<br />
** (and some plain maps)<br />
* Singleplayer content<br />
** Currently maintaining Descent into Darkness ([http://www.wesnoth.org/forum/viewtopic.php?t=13776 forum thread])<br />
* Coding<br />
** Friendslist for multiplayer<br />
** (and some minor fixes)</div>Baufohttps://wiki.wesnoth.org/index.php?title=User:Baufo&diff=16241User:Baufo2007-07-01T14:05:05Z<p>Baufo: </p>
<hr />
<div>* Name: Thomas Baumhauer<br />
* Location: Vienna, Austria<br />
* Email: [mailto:baufo_ATTHEHOST_gmx_DOT_at baufo ATTHEHOST gmx DOT at]<br />
* Weblog: [http://baufo.freehostia.com Baufo Speaks]<br />
<br />
== Contributions ==<br />
* Multiplayer content<br />
** Defense of the Goblin ([http://www.wesnoth.org/forum/viewtopic.php?t=12566 forum thread])<br />
** The Dwarvish Treasure ([http://www.wesnoth.org/forum/viewtopic.php?t=12681 forum thread])<br />
** (and some plain maps)<br />
* Singleplayer content<br />
** Currently maintaining Descent into Darkness ([http://www.wesnoth.org/forum/viewtopic.php?t=13776 forum thread])<br />
* Coding<br />
** Friendslist for multiplayer<br />
** (and some minor fixes)</div>Baufohttps://wiki.wesnoth.org/index.php?title=Credits&diff=16238Credits2007-07-01T08:46:07Z<p>Baufo: /* Miscellaneous */</p>
<hr />
<div>{| style="float:right"<br />
|<br />
__TOC__<br />
|}<br />
In July 2003, '''David White''' released the first version of Wesnoth. Since then, many people have joined the project, contributing in very different ways.<br />
<br />
== Developers ==<br />
====Coders, (minor and major)====<br />
* Alfredo Beaumont (ziberpunk) - autotools<br />
* András Salamon ([[User:Ott|ott]]) - QA, bug fixing, subediting, game mechanics<br />
* Benoît Timbert (Noyga) - coder<br />
* Bram Ridder (Morloth) - editor improvements<br />
* [[User:bruno|Bruno Wolff III]] - Campaign web interface, [[MainlineScenarios#The_Dark_Hordes|The Dark Hordes]] maintainer, bug fixing, minor coder<br />
* Cédric Duval - coder, internationalization manager<br />
* David Philippi (Torangan) - internationalization manager, wescamp<br />
* [mailto:davidnwhite_AT_verizon.net David White] (Sirp) - founder, lead developer, scenario designer<br />
* Dominic Bolin (Xan) - programmer<br />
* Guillaume Melquiond (silene) - coding, bug fixes<br />
* Jérémy Rosen (Boucman) - coder<br />
* Jörg Hinrichs (Yogi Bear/YogiHH) - coder<br />
* Jon Daniel (forcemstr) - coder, bug fixes<br />
* J. W. C. McNabb (Darth Fool) - coder, graphics<br />
* [mailto:justin.zaun_AT_gmail.com Justin Zaun] (jzaun) - coder, scenario designer<br />
* [mailto:erl_AT_erl.se Kristoffer Erlandsson] (erl) - help system, editor<br />
* Nicolas Weeger (ryo) - Python API<br />
* [mailto:patrick_x99(AT).hotmail.com Patrick Parker] ([[User:Sapient|Sapient]]) - improvements to user interface, WML engine, various features<br />
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - several parts of the code, notably terrain graphics code<br />
* [mailto:ydirson_AT_altern.org Yann Dirson] - gettext support, tinygui<br />
* [mailto:esr&x40;thyrsus.com Eric S. Raymond] - macro and tools cleanup<br />
<br />
====Miscellaneous====<br />
* Benjamin Drieu (benj) - campaign writer (wrote "Son of the Black Eye")<br />
* [mailto:dragonking_AT_o2.pl Bartek Waresiak] (Dragonking) - multiplayer balancing<br />
* Crossbow/Miyo - administrator, release manager<br />
* esci - campaign writer (wrote "Descent into Darkness")<br />
* Francisco Muñoz (fmunoz) - artwork manager, many images, scenario designer (also listed below)<br />
* Hogne Håskjold (frame) - terrain designer (also listed below)<br />
* [mailto:isaac_AT_sindominio.net Isaac Clerencia] - administrator, release manager, debian packager<br />
* James Spencer (Shade) - campaign writer (wrote "The Rise of Wesnoth")<br />
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) - website, i18n<br />
* Joseph Simmons (Turin) - campaign writer, some graphics (wrote "The Eastern Invasion," and others)<br />
* Mark Michelsen (skovbaer) - internationalization manager<br />
* Mike Quiñones (Doc Paterson) - multiplayer balancing, multiplayer maps<br />
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - administrator, campaign maintainer (Two Brothers), internationalization manager, release manager<br />
* Richard Kettering (Jetryl) - artwork manager, many images (also listed below)<br />
* Richard S. (Noy) - multiplayer balancing<br />
* Soliton - multiplayer balancing<br />
* Susanna Björverud (sanna) - internationalization manager<br />
* [mailto:baufo_AT_gmx_DOT_at Thomas Baumhauer] ([[User:Baufo|Baufo]])<br />
* [mailto:kleinfel_AT_wpi.edu Zack Kleinfeld] - multiplayer maps, unit balancing<br />
<br />
====Unclassified====<br />
* Jan Zvánovec (jaz)<br />
* John B. Messerly (jbm)<br />
* J.R. Blain (Cowboy)<br />
* Maksim Orlovich (SadEagle)<br />
* Zas<br />
<br />
== Artists ==<br />
==== Major Contributors ====<br />
* Francisco Muñoz (fmunoz) - Founding Artist and former lead artist, worked consistently on all aspects till around v0.7-0.9.<br />
* Richard Kettering [http://www.wesnoth.org/wiki/User:Jetryl (Jetryl)] - Current art director/slave, major focus on sprites, portraits, buildings, and icons<br />
* Hogne Håskjold (frame/freim) - Former director of terrain art, made much of the current terrains (esp. mountains)<br />
* J. W. Bjerk [http://www.wesnoth.org/wiki/User:Eleazar (Eleazar)] - Terrain-art lead. Made chasm, cave, water, etc, sprite animations, various visual tweaks and clean-ups<br />
* Pekka Aikio (pekka) - tiles, esp. castles, and attack icons<br />
* Lari Nieminen (zookeeper) - Current sprite animation director and WML wizard<br />
* James Woo (Pickslide) - portraits (major focus on orcs and campaigns, especially UtBS, TEI, TSoF)<br />
* Jason Lutes - portraits (major focus on humans, some campaign portraits)<br />
* ?? (Neoriceisgood) - sprite creator and animator (major focus on drakes, dwarves, saurians)<br />
* Peter Geinitz (Shadow/Wayfarer) - sprite creator and animator<br />
<br />
==== Moderate Contributors ====<br />
* Alex Jarocha-Ernst (Jormungandr) - portraits<br />
* Moritz Göbelbecker (mog) - tiles, esp. swamp, encampment, ice, and work with lava/chasm<br />
* Erkki Lonkainen (Eternal) - created and animated many replacement sprites (esp. ogre, orc assassin & spear units, and cockatrice)<br />
* Maximiliano Buis (Redeth) - Made nearly all of the idle animations, and some death animations (as of 1.3.1)<br />
* Leonhard ? (Leonhard) - made several of the new attack icons<br />
* Michael Gil de Muro (grp21) - portraits (for the campaign "The Rise of Wesnoth")<br />
* Robert Bolin (Zebulon) - tiles, sprite editing and animations<br />
* Christophe Anjard (Christophe33) - made many of the old (c. v0.6) terrains, and some sprites for the dwarves<br />
* Johann de Venecia (Johann) - drew the new campaign story art for HttT<br />
* Mark Goodenough (Ranger M) - Sprite animator<br />
<br />
==== Minor Contributors ====<br />
<br />
* Eli Dupree (Elvish Pillager) - sprites and animations<br />
* Murray Cook (Zhukov) - Sprite animator<br />
* Gerald Clears (Smok'em Jags) - sprite animator<br />
* Jesse Holland (Kestenvarn) - map illustrator, designed the current map for HttT<br />
* Mikko Kraft (Deserter) - Sprite animator<br />
* Michael Mielewczik (Mille) - Sprite animator<br />
* Stephen Stone (Disto) - Sprite animator<br />
* Andrew James Patterson (Kamahawk) - sprites<br />
* Diego Brea (Cobretti) - sprite creator/animator<br />
* ?? (antwerpz) - sprite creator/animator for old saurian units<br />
* Gareth Miller (Gafgarion) - made some early sprites/tiles<br />
* James Barton (Sangel) - sprites<br />
* John Muccigrosso (Eponymous Archon) - made some early sprites, such as the human bowmen<br />
* ?? (Slainte) - made sprites for c. v0.6 mages, also made many of the old attack icons<br />
* ?? (Svetac) - made many of the old attack icons<br />
* Johanna Manninen (lohari) - edited tiles, ported freeciv tiles used in very early versions of wesnoth<br />
* Tristan Millner (tatmf) - made portrait of dwarven fighter<br />
* EEL (EELuminatus) - Made death animations for the wose line.<br />
* Mattias Westlund (West) - new colored cursors, TB portrait<br />
* Eric Holdos (Rev. V!) - Made a few extra frames for the elvish captain/hero.<br />
* Musketaquid - animated windmill<br />
<br />
==== Very Minor Contributors ====<br />
* Gideon Chia (Deonjo) - new "units" icon for general status bar<br />
* John-Robert Funck (XJaPaN) - sprite animator<br />
* Anton Ecker (Kaldred) - burnt villages<br />
* Joe (battlestar) - some scenery graphics including burnt tent.<br />
* Jonatan Alamà (tin) - made red logo used until before v1.0<br />
* Jimmy Olsson (Azlan) - made old icons for windows version<br />
* Randall Walls (slightcrazed) - sprite animator<br />
* Jason Frailey (Valdroni) - made scorpion portrait<br />
* Nicholas Kerpan (Thrawn) - made human theif portrait<br />
* ?? (Highhole) - revised storm trident<br />
* Irwin Ismail (Swordy) - original projectile/attack icon for chakram<br />
* Evan Crook (Flametrooper) - Sprite animator (TC conversion)<br />
* Daniel Borgmann (dborg) - semi-transparent map grid<br />
* Garrett Wessner (Stilgar) - gold coin-pile<br />
* Javier Hoyos (Vendanna) - naga hunter attack frames<br />
<br />
== Musicians ==<br />
* Aleksi Aubry-Carlson (Aleksi) - music coordinator/composer<br />
* Joseph Toscano (zhaymusic.com) - music<br />
* Pau Congost - music<br />
* Fredrik Lindroth - music<br />
* Timothy Pinkham (TimothyP) - music coordinator/composer<br />
<br />
== Translators ==<br />
* adson - hungarian translation<br />
* İhsan Akın - turkish translation<br />
* Agata Chmiel - polish translation<br />
* Aleksej Korgenkov (Grimpanto) - esperanto translation<br />
* Alessio D'Ascanio (otaku) - italian translation<br />
* Alexander Alexiou (Santi) - greek translation<br />
* Alexander Kjäll (capitol) - swedish translation<br />
* Alexandr Menovchicov - russian translation<br />
* Alexey Remizov - russian translation<br />
* Alexey Zakharchenko - russian translation<br />
* Alfredo Beaumont (ziberpunk) - basque translation<br />
* Ambra Viviani Loos - brazilian portuguese translation<br />
* Americo Iacovizzi (DarkAmex) - italian translation<br />
* Anders K. Madsen (madsen) - danish translation<br />
* András Salamon ([[User:Ott|ott]]) - afrikaans, english and hungarian translation<br />
* Andre Schmidt (schmidta) - german translation<br />
* Anežka Bubeníčková (Bubu) - czech translation<br />
* Ankka - finnish translation<br />
* Anton Tsigularov (Atilla) - bulgarian translation<br />
* Arkadiusz Danilecki (szopen) - polish translation<br />
* Arnaud Garoux (La vie en wose) - french translation<br />
* Arne Deprez - dutch translation<br />
* Artur R. Czechowski - polish translation<br />
* Åse Petersson (tintin) - swedish translation<br />
* Aurélien Brevers (Breversa) - french translation<br />
* Azamat Hackimov ([[User:Winterheart|winterheart]]) - russian translation<br />
* Bartek Waresiak (Dragonking) - polish translation<br />
* Beer (Eddi) - hungarian translation<br />
* Benoit Astruc - french translation<br />
* Benoît Timbert (Noyga) - french translation<br />
* Bjarke Sørensen (basher) - danish translation<br />
* BlueStar - japanese translation<br />
* Boris Stumm (quijote_) - german translation<br />
* BOrsuk - polish translation<br />
* Branko Kokanovic (kokan) - serbian translation<br />
* Bruno Fève (PP) - french translation<br />
* [mailto:caslav_DOT_ilic_AT_gmx_DOT_net Časlav Ilić] - serbian translation<br />
* Cédric Duval - french translation<br />
* Carles Company (brrr) - catalan translation<br />
* Celso Goya - brazilian portuguese translation<br />
* Christoph Berg (chrber) - german translation<br />
* [mailto:cbterra_AT_gmail.com Claudio Terra] - brazilian portuguese translation<br />
* Claus Aranha - brazilian portuguese translation<br />
* crys0000 - italian translation<br />
* Dan Rosàs Garcia (focks) - catalan translation<br />
* Damien Jacquot - french translation<br />
* Daniel López (Azazelo) - catalan translation<br />
* DaringTremayne - french translation<br />
* David Nečas (Yeti) - czech translation<br />
* dentro - hungarian translation<br />
* Denica Mincheva - bulgarian translation<br />
* Enes Akın (yekialem) - turkish translation<br />
* Erik J. Mesoy (Circon) - norwegian translation<br />
* Eugenio Favalli (ElvenProgrammer) - italian translation<br />
* Federico Tomassetti - italian translation<br />
* Flamma - spanish translation<br />
* Florence Guettaa (inflow) - french translation<br />
* Foppe Benedictus - dutch translation<br />
* Francesco Lorenzon (Likso) - esperanto translation<br />
* Franciso Muñoz (fmunoz) - spanish translation<br />
* François Mariage (Paquito) - french translation<br />
* François Orieux - french translation<br />
* Gabriel Rodríguez (Chewie) - spanish translation<br />
* Gaute Jao (Bombadil) - norwegian translation<br />
* Geoffroy Douillié ([[User:Gdou|Gdou]]) - french translation<br />
* Georgi Dimitrov (oblak)- bulgarian translation<br />
* Gérard Bodin - french translation<br />
* Gerfried Fuchs ([[User:Rhonda|Rhonda]]) - german translation<br />
* Gilluin - hungarian translation<br />
* Guillaume Duwelz-Rebert - french translation<br />
* [mailto:massart.guillaume_AT_wanadoo.fr Guillaume Massart (Piou2fois)] - french translation<br />
* Guillaume Melquiond (silene) - french translation<br />
* Hallvard Norheim Bø (Lysander) - norwegian translation<br />
* Harry Kaimenas - greek translation<br />
* Håvard Korsvoll - norwegian translation<br />
* Huang huan (unicon) - chinese translation<br />
* Hugo Gerlach (Entrimo) - swedish translation<br />
* Ilya Kaznacheev - russian translation<br />
* Ilya Kotov - russian translation<br />
* Ivan Kovacs - slovak translation<br />
* isazi - italian translation<br />
* Iván Herrero (navitux) - spanish translation<br />
* Jaka Kranjc (lynx) - slovenian translation<br />
* Jan Greve (Jan) - german translation<br />
* Jan-Heiner Laberenz (jan-heiner) - german translation<br />
* Jean Privat (Tout) - french translation<br />
* Jean-Luc Menut - french translation<br />
* Jean-Luc Richard (Le Gnome) - french translation<br />
* Jehan Hysseo (Jey) - french translation<br />
* Jérémy Rosen (Boucman) - french translation<br />
* Jesper Fuglsang Wolff (ulven) - danish translation<br />
* Joan Queralt - catalan translation<br />
* Joe Hansen - danish translation<br />
* Joeri Melis - dutch translation<br />
* Jonatan Alamà (tin) - catalan translation<br />
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) - catalan translation coordinator<br />
* Jose Gordillo (kilder) - spanish and catalan translation<br />
* Jose Manuel Gomez (joseg) - spanish translation<br />
* Joset Anthony Zamora (sophie^) - filipino translation<br />
* Julien Moncel - french translation<br />
* Julien Tailleur - french translation<br />
* Julen Landa (genars) - basque translation<br />
* Jussi Rautio (jgrr) - finnish translation<br />
* Kai Ensenbach (Pingu) - german translation<br />
* Kékkői László (BlackEvil) - hungarian translation<br />
* Karol Nowak (grzywacz) - polish translation<br />
* Katerina Sykioti - greek translation<br />
* Kertész Csaba - hungarian translation<br />
* Khiraly - hungarian translation<br />
* Kim Woong (Kazya) - korean translation<br />
* kko - finnish translation<br />
* Konstantinos Karasavvas - greek translation<br />
* Konstantinos Egarhos - greek translation<br />
* Kosif - turkish translation<br />
* Kovács Dániel - hungarian translation<br />
* krix - hungarian translation<br />
* Lala - dutch translation<br />
* Leo Danielson (Lugo Moll) - swedish translation<br />
* Luciano Montanaro (Luciano) - italian translation<br />
* Lukáš Faltýnek - czech translation<br />
* Ľubo Fajth - esperanto translation<br />
* Maarten Albrecht - dutch and esperanto translation<br />
* Mark Michelsen (skovbaer) - danish translation<br />
* Mark Polo (mpolo) - latin translation<br />
* Mark Recasens - catalan translation<br />
* Mart Tõnso - estonian translation<br />
* Martin Dzbor - slovak translation<br />
* Martin Šín - czech translation<br />
* Matej Repinc - slovenian translation<br />
* Mathias Bundgaard Svensson (freaken) - danish translation<br />
* Matias Parmala - finnish translation<br />
* methinks - polish translation<br />
* Michał Jedynak (Artanis) - polish translation<br />
* Michał Ligowski (misiorysio) - polish translation<br />
* Michel Loos - brazilian portuguese translation<br />
* Michel Poléni (Thanatloc) - french translation<br />
* Mik2303 - greek translation<br />
* Mikel Olasagasti (Hey_neken) - basque translation<br />
* Mikko Kraft (deserter) - finnish translation<br />
* Mintaka - czech translation<br />
* Naoki Iimura (amatubu) いいむらなおき - japanese translation<br />
* Nico Oliver - afrikaans translation<br />
* Nicolas Boudin (Blurgk) - french translation<br />
* Nikolay Vladimirov (Turki) - bulgarian translation<br />
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - german translation<br />
* [mailto:okyada_AT_gmail.com Nobuhito Okada] 岡田信人 - japanese translation<br />
* [mailto:tapik_AT_buchtovi.cz Oto Buchta] ([[User:Tapik|tapik]]) - czech translation<br />
* Pau Rul·lan Ferragut - catalan translation<br />
* Paweł Stradomski - polish translation<br />
* Paweł Tomak - polish translation<br />
* paxed - finnish translation<br />
* Petr Kopač (Ferda) - czech translation<br />
* Petr Kovár (Juans) - czech translation<br />
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - french translation<br />
* Pieter Vermeylen (Onne) - dutch translation<br />
* P&#305;nar Yanarda&#287; (moonquelle) - turkish translation<br />
* Q - japanese translation<br />
* Rastislav Šarišský (Asto) - esperanto translation<br />
* Renato Cunha - brazilian portuguese translation<br />
* Ricardo Sodré Andrade - brazilian portuguese translation<br />
* Roberto Garcia (Motxales) - catalan translation<br />
* Roberto Romero (sildur) - spanish translation<br />
* Roel Thijs (Roel) - dutch translation<br />
* Roger Koot - dutch translation<br />
* RokStar - italian translation<br />
* Roman Tuchin (Sankt) - russian translation<br />
* Rudolf Orság - czech translation<br />
* Ruben Philipp Wickenhäuser (The Very Uhu) - german translation<br />
* Sébastien Raynaud (Galactic turkey) - french translation<br />
* Sérgio de Miranda Costa - brazilian portuguese translation<br />
* Selim Farsakoğlu - turkish translation<br />
* Sofronius - czech translation<br />
* Spiros, Giorgis - greek translation<br />
* [mailto:sreckotoroman_AT_gmail_DOT_com Srećko Toroman] (FreeCraft) - serbian translation<br />
* Stefan Bergström (tephlon) - swedish translation<br />
* Stephan Grochtmann (Schattenstephan) - german translation<br />
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - swedish translation<br />
* Susanne Mesoy (Rarlgland) - norwegian translation<br />
* Széll Tamás (TomJoad) - hungarian translation<br />
* Takanobu Hirai - japanese translation<br />
* Tiago Souza (Salvador) - brazilian portuguese translation<br />
* Tobe Deprez - dutch translation<br />
* Uz-Valentin Friedrich - german translation<br />
* Vít Komárek - czech translation<br />
* Vít Krčál - czech translation<br />
* [http://www.viliam.bur.sk/ Viliam Búr] - slovak translation<br />
* Vladimír Slávik - czech translation<br />
* Vlad Glagolev (Stelz) - russian translation<br />
* vonHalenbach - german translation<br />
* William Dupré - french translation<br />
* wint3r - swedish translation<br />
* [mailto:ydirson_AT_altern.org Yann Dirson] - french translation<br />
* Yuji Matsumoto - japanese translation<br />
* Zas - french translation<br />
<br />
== Other Contributions ==<br />
* Ben Anderman (crimson_penguin) - unit list<br />
* Cyril Bouthors (CyrilB) - debian packager, patron<br />
* Dacyn - scenario designer<br />
* Darryl Dixon - packager<br />
* edge - packager<br />
* Francesco Gigli (Jaramir) - wiki, wesnoth.slack.it<br />
* Frédéric Wagner<br />
* Jay Hopping - packager<br />
* Jeff Breidenbach (Jab) - Bilinear interpolation<br />
* Joshua Northey (Becephalus) - multiplayer maps<br />
* Laurent Wacrenier (lwa) - Mac OS X packager<br />
* Marcin Konicki (ahwayakchih) - BeOS packager<br />
* Marcus Phillips (Sithrandel) - Mac OS X packager (for v1.0 and before)<br />
* Mark Michelsen (skovbaer) - slackware packager<br />
* Miguel Zapico (elricz) - unit list translations<br />
* Peter Groen (pg) - multiplayer maps<br />
* Ruben Philipp Wickenhäuser (The Very Uhu) - multiplayer maps<br />
* Sam Phillips (dark172) - creation of campains and multiplayer maps<br />
* Tom Chance (telex4) - multiplayer maps, scenario balancing<br />
* Vlad Glagolev (Stelz) - OpenBSD packager<br />
<br />
{{Home}}</div>Baufohttps://wiki.wesnoth.org/index.php?title=User:Baufo&diff=16203User:Baufo2007-06-29T12:47:13Z<p>Baufo: </p>
<hr />
<div>* Name: Thomas Baumhauer<br />
* Location: Vienna, Austria<br />
* Email: baufo AT THE HOST gmx DOT at<br />
* Weblog: [http://baufo.freehostia.com baufo.freehostia.com]<br />
<br />
== Contributions ==<br />
* Multiplayer content<br />
** Defense of the Goblin ([http://www.wesnoth.org/forum/viewtopic.php?t=12566 forum thread])<br />
** The Dwarvish Treasure ([http://www.wesnoth.org/forum/viewtopic.php?t=12681 forum thread])<br />
** (and some plain maps)<br />
* Singleplayer content<br />
** Currently maintaining Descent into Darkness ([http://www.wesnoth.org/forum/viewtopic.php?t=13776 forum thread])<br />
* Coding<br />
** Friendslist for multiplayer<br />
** (and some minor fixes)</div>Baufohttps://wiki.wesnoth.org/index.php?title=InterfaceActionsWML&diff=13906InterfaceActionsWML2007-02-18T10:12:25Z<p>Baufo: </p>
<hr />
<div>{{WML Tags}}<br />
== Interface actions ==<br />
<br />
Interface actions are actions that do not have an effect on gameplay;<br />
instead, they show something to the player. The main interface tags<br />
are '''[message]''' and '''[objectives]''', but several other tags affect<br />
the interface also.<br />
<br />
== [message] ==<br />
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.<br />
<br />
The following key/tags are accepted for [message]:<br />
* standard unit filter - 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).<br>'''[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.<br />
<br />
* ''speaker'' an alternative to standard unit filter<br />
** 'narrator' the dialog box is displayed without a caption for the unit speaking or a unit image<br />
** 'unit' the primary unit for the event is speaking<br />
** 'second_unit' the secondary unit for the event is speaking<br />
<br />
* ''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 ''' " ''')<br />
* ''image'' (default: profile image of speaker) the image to display next to the message.<br />
* ''caption'' (default: name of speaker) the caption to display under the image. Name to be displayed.<br />
* ''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. {{DevFeature}}<br />
* ''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.<br />
* '''[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.<br />
** ''message'' (translatable) the text displayed for the option (see [[DescriptionWML]])<br />
** ''show_always'' if no then this option will only be displayed if the conditional statement in this tag is passed (see [[InternalActionsWML]])<br />
** '''[command]''' an element containing actions which are executed if the option is selected.<br />
<br />
Text formatting options for '''[message]'''. These can also be used in unit names (user_description), objectives, and such.<br />
* An asterisk (*) as the first character causes the line to be boldfaced.<br />
* An at symbol (@) as the first character causes the line to be green, as done with victory conditions.<br />
* A pound symbol (#) as the first character causes the line to be red, as done with defeat conditions.<br />
* A backquote (`) as the first character causes the line to be smaller.<br />
* If used, the caption key text is boldfaced.<br />
* 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!"''<br />
<br />
== [objectives] ==<br />
The other tag used for plot development is '''[objectives]'''.<br />
The '''[objectives]''' tag overwrites any previously set objectives,<br />
and displays text which should describe the objectives of the scenario.<br />
Scenario objectives are displayed on the player's first turn after the tag is used,<br />
or as part of the event if it triggers during that player's turn.<br />
Objectives can also be accessed at any time in a scenario using the<br />
"Scenario Objectives" game menu option, making this tag useful for<br />
scenario-specific information that the player may need to refer to during play.<br />
<br />
This tag renders the ''objectives'' attribute of [scenario] obsolete (see ''objectives'', [[ScenarioWML]]).<br />
Instead of using ''objectives'', use '''[objectives]''' to set scenario objectives inside a prestart event.<br />
It can also be used to overwrite the starting objectives mid-scenario.<br />
<br />
Attributes of '''[objectives]''':<br />
* ''side'' Default '0'. The side to set the objectives for. A value of 0 sets objectives for all sides.<br />
* ''summary'' Displayed first in the objectives text, this should describe the basic objective for the overall scenario. Can be omitted.<br />
* ''note'' Displayed last in the objectives text, this is sometimes used for hints or additional information. Can be omitted.<br />
* ''victory_string'' Default ' _ "Victory:"', this text precedes the victory objectives.<br />
* ''defeat_string'' Default ' _ "Defeat:"', this text precedes the defeat objectives.<br />
* ''silent'' Default: not present. If set to "yes", the objectives are silently changed. Else, they will be shown to the user when appropriate.<br />
<br />
Tags of '''[objectives]''':<br />
* '''[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.<br />
** ''description'' text for the specific win or loss condition.<br />
** ''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'')<br />
<br />
<br />
== Other interface tags ==<br />
<br />
The following tags are also action tags:<br />
* '''[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.<br />
** ''x'', ''y'' the location to place the item.<br />
** ''image'' the image (in ''images/ ''as .png) to place on the hex.<br />
** ''halo'' an image to place centered on the hex. Use this instead of ''image'' if the image is bigger than the hex.<br />
* '''[removeitem]''' removes any graphical items on a given hex<br />
** ''x'', ''y'' the hex to remove items off<br />
* '''[print]''' displays a message across the screen. The message will disappear after a certain time.<br />
** ''text'' (translatable) the text to display.<br />
** ''size'' (default=12) the pointsize of the font to use<br />
** ''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.<br />
** ''red'', ''green'', ''blue'' (default=0,0,0) the color to display the text in. Values vary from 0-255.<br />
* '''[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.<br />
** ''type'' the type of the unit whose image to use<br />
** ''x'' a comma-seperated list of x locations to move along<br />
** ''y'' a comma-seperated list of y locations to move along (x and y values are matched pairs)<br />
** ''side'' the side of the fake unit, used for team colouring the fake unit<br />
* '''[hide_unit]''' makes the given unit become invisible. Useful in conjunction with '''[move_unit_fake]''' to move a leader unit into position on-screen. Only one unit may be hidden at a time.<br />
** ''x'', ''y'' location of the unit to be hidden. (NOT a standard unit filter! Just x and y.)<br />
* '''[unhide_unit]''' stops the currently hidden unit from being hidden.<br />
* '''[scroll]''' Scroll a certain number of pixels in a given direction. Useful for earthquake/shaking effects.<br />
** ''x'', ''y'' the number of pixels to scroll along the x and y axis<br />
* '''[scroll_to]''' Scroll to a given hex<br />
** ''x'', ''y'' the hex to scroll to<br />
** ''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.<br />
* '''[scroll_to_unit]''' Scroll to a given unit<br />
** standard unit filter<br />
** ''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.<br />
* '''[sound]''' Plays a sound<br />
** ''name'' the filename of the sound to play (in ''sounds/'' as .wav or .ogg)<br />
* '''[music]''' Switches to playing different music<br />
** ''name'' the filename of the music to play (in ''music/'' as .ogg)<br />
** see [[MusicListWML]] for the correct syntax<br />
* '''[colour_adjust]''' tints the colour of the screen.<br />
** ''red'', ''green'', ''blue'' values from -255 to 255, the amount to tint by for each colour<br />
* '''[delay]''' pauses the game<br />
** ''time'' the time to pause in milliseconds<br />
* '''[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).<br />
** ''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).<br />
* '''[unit_overlay]''' sets an image that will be drawn over a particular unit, and follow it around<br />
** ''x'', ''y'' the location of the unit to overlay on<br />
** ''image'' the image to place on the unit<br />
* '''[remove_unit_overlay]''' removes a particular overlayed image from a unit<br />
** ''x'', ''y'' the location of the unit to remove an overlay from<br />
** ''image'' the image to remove from the unit<br />
* '''[animate_unit]''' uses the custom animation of a unit to animate it on screen (if the unit has the corresponding animation)<br />
** ''flag'' the key to find the good custom animation in the unit description see the '''[extra_anim]''' description in [[AnimationWML]]<br />
** '''[filter]''' a standard unit filter see [[FilterWML]] by default, the unit at the event location will be animated. You can use this tag to choose what unit to animate<br />
* '''[label]''' places a label on the map.<br />
** ''x'', ''y'' the location of the label<br />
** ''text'' what the label should say<br />
<br />
== See Also ==<br />
* [[DirectActionsWML]]<br />
* [[InternalActionsWML]]<br />
* [[EventWML]]<br />
* [[ReferenceWML]]<br />
<br />
<br />
[[Category: WML Reference]]</div>Baufohttps://wiki.wesnoth.org/index.php?title=Wesnoth_Acronyms_and_Slang&diff=11508Wesnoth Acronyms and Slang2006-09-02T07:35:48Z<p>Baufo: /* Forum Language */</p>
<hr />
<div>Use the following list to demystify the various (mostly wesnoth specific) acronyms you may run into at the forum.<br />
<br />
<!-- NOTE TO EDITORS: Please try to keep an alphabetic order to simplify manual searching --><br />
<br />
== Official Campaigns ==<br />
<br />
*EI - "The Eastern Invasion" (campaign name)<br />
*HttT - "Heir to the Throne" (campaign name)<br />
** BoP - "Bay of Pearls" (scenario in "Heir to the Throne" campaign)<br />
** DD - "Dwarven Doors" (scenario in "Heir to the Throne" campaign)<br />
** HotNE - "Home of the North Elves" (scenario in "Heir to the Throne" campaign)<br />
** IotD - "Isle of the Damned" (scenario in "Heir to the Throne" campaign)<br />
** RtW - "Return to Wesnoth" (scenario in "Heir to the Throne" campaign)<br />
** SoE - "Siege of Elensefar" (scenario in "Heir to the Throne" campaign)<br />
** SoF - "Scepter of Fire" (scenario in "Heir to the Throne" campaign)<br />
** TotC - "Test of the Clans" (scenario in "Heir to the Throne" campaign)<br />
** VoD - "Valley of Death" (scenario in "Heir to the Throne" campaign)<br />
*SG - "The South Guard" (campaign name)<br />
*TRoW - "The Rise of Wesnoth" (campaign name)<br />
*TB - "A Tale of Two Brothers" (campaign name)<br />
*UtBS - "Under the Burning Suns" (campaign name)<br />
<br />
== Unofficial Campaigns ==<br />
<br />
*FtF - "Flight to Freedom" (campaign name)<br />
*LOW - "Legends of Wesmere" (campaign name)<br />
*SE - "Saving Elensefar" (campaign name)<br />
*SoF - "Scepter of Fire" (campaign name)<br />
<br />
== Forum Language ==<br />
<br />
*AAU - Allies Are Useless<br />
*AMLA - After Maximum Level Advancement<br />
*AH - All Hits <br />
*AoH - Age of Heros<br />
*BfW - Battle for Wesnoth (the name of the game)<br />
*BWH - Been suggested before. We think it's a good idea. Hope to add it eventually.<br />
*CtH - Chance to Hit (also C2H)<br />
*CtbH - Chance to be Hit (also C2bH)<br />
*CtK - Chance to Kill (also C2K)<br />
*CtbK - Chance to be Killed (also C2bK)<br />
*CVS - Old term for up-to-date Wesnoth: [[WesnothCVS]]<br />
*EP - Elvish Pillager, moderator and great man :) at forum<br />
*FoW - Fog of War (i.e. fog)<br />
*FFA - Free For All (playing a map with >2 players without teams)<br />
*HAPMA - Hexes Are Possibly Miles Across - http://www.wesnoth.org/forum/viewtopic.php?t=1882<br />
*HP - Hit points<br />
*IIRWIIR - It Is Ready When It Is Ready<br />
*KISS - Keep It Simple, Stupid: Applies to coding, not game rules (although indirectly it does): see [[WesnothPhilosophy]]<br />
*MP - Movement points<br />
*MP - Multiplayer<br />
*MOP - Monster of perfection<br />
*MoL - Mage of Light<br />
*N3T - No 3-Teams; A belief stating that contests between exactly three opposing forces are inherently unbalanced<br />
*OAB - Options are Bad; In reference to gameplay, not user interface options. Mostly used by Turin. See also [[FrequentlyProposedIdeas]] (idea #1)<br />
*OFWRA - Old Flame War Revival Alert; In other words, we have discussed this before and have no interest in discussing it again, especially if it got ugly<br />
*OT - Off Topic: can refer to either the forum (http://www.wesnoth.org/forum/viewforum.php?f=11) or spam<br />
*RIPLIB - Reduction In Power when Leveling Is Bad: means that when a unit upgrades, at least one of its options should be strictly superior to the original unit. [http://www.wesnoth.org/forum/viewtopic.php?t=1423 Reference 1] / [http://www.wesnoth.org/forum/viewtopic.php?t=7205 Reference 2]<br />
*RPG - Role Playing Game - [http://www.wesnoth.org/forum/viewtopic.php?t=4385 1)] Wesnoth's experience system. <nowiki>2)</nowiki> An "RPG-style" game on the MP server means the primary focus will be walking your leader-units through a scripted storyline involving map exploration and lots of WML.<br />
*RTFM - Read The Manual<br />
*RTS - Real Time Strategy Game - not Wesnoth<br />
*SP - Single Player (Campaigns)<br />
*SVN - Term for up-to-date Wesnoth [[WesnothSVN]] ([[What_Is_SVN]])<br />
*TBS - Turn Based Strategy Game - Wesnoth<br />
*TOD - Time of Day<br />
*TWP - The Wesnoth Philosophy: [[WesnothPhilosophy]]<br />
*UMC - User Made Campaign (any campaign not packaged with Wesnoth)<br />
*WC - Walking Corpses<br />
*WICOT - WML is capable of this (the requested feature is already possible to script, so no need to hard-code it in C++)<br />
*WINR - Wesnoth Is Not Realistic<br />
*WIN_ - Wesnoth Is Not... (Warcraft, Lord of the Rings, medieval Europe, an RPG, a wargame, a war simulation, etc.)<br />
*WML - Wesnoth Markup Language: [[ReferenceWML]]<br />
*XP - Experience<br />
*ZOC - Zone of Control<br />
<br />
== General Acronyms ==<br />
<br />
*AFAICT - As Far As I Can Tell(A statement with a disclaimer on truthfulness)<br />
*AFAIK - As Far As I Know (A statement with a disclaimer on truthfulness)<br />
*BTW - By the Way (A statement with a disclaimer on relevance)<br />
*OtOH - On the Other Hand (A contrast)<br />
*EV - Expected Value<br />
*IIRC - If I Recall Correctly (A statement with a disclaimer on truthfulness)<br />
*IMHO - In My Humble Opinion (A statement with a disclaimer on objectiveness)<br />
*IMO - In My Opinion (A statement with a disclaimer on objectiveness)<br />
*NYSPOS - No, you stupid piece of **** (An impolite refutation hidden in an acronym)<br />
<br />
== See Also ==<br />
<br />
* Enter other resources in here.</div>Baufohttps://wiki.wesnoth.org/index.php?title=FAQ&diff=10139FAQ2006-06-18T19:20:22Z<p>Baufo: /* How do I download user campaigns? */</p>
<hr />
<div>=Frequently Asked Questions=<br />
<br />
== General ==<br />
<br />
===What is Battle for Wesnoth?===<br />
Battle for Wesnoth is a fantasy turn-based strategy game.<br />
<br />
===What license is the game distributed under?===<br />
The project is distributed under the [http://www.fsf.org/copyleft/gpl.html GPL]. All contributors retain copyright on the portions of the project that they contribute.<br />
<br />
===How to get informed about new releases?===<br />
Subscribe to new releases at [http://freshmeat.net/subscribe/38720/?url=%2Fprojects%2Fwesnoth%2F Freshmeat].<br />
<br />
===A new version is out, but where is the download for [Windows, Mac OS, etc.]?===<br />
The downloads are NOT part of the official project. The BFW team only releases the game's source code. Binary executables or applications are always contributed by community volunteers. If not for these volunteers, there would never be any downloads for us to enjoy. The volunteers compile the game and upload it on their own time, and sometimes they cannot do this in a timely fashion (or at all, at times) Although there are usual packagers designated for each operating system, there are times when other members of the community are asked to step in and contribute when the usual people cannot.<br />
<br />
Every time a new version is released, the usual volunteers are always notified by the project leaders. '''Please refrain from making forum posts asking where your download is''' because it doesn't help anything - the packagers already know, and they will get to it as soon as they can. In the past, the Windows and Mac communities have come together to produce home-grown unofficial builds for the community to use, and the renewed interest in community and learning how to compile is generally a good thing.<br />
<br />
===Why doesn't Wesnoth have my favorite feature?===<br />
Because we are building this game for ourselves, to suit our own preferences. We're not building the game for you, in large part because this is our hobby, not our job; whether you like it or not is immaterial to us.<br />
You may wonder, then, what the point is of soliciting ideas, as we do on the forum. We, the developers, have certainly come up with many good ideas on our own, but our players often do as well, and generally ones we don't think of ourselves. If a player comes up with an idea we like, we might implement it. Not because they asked for it, but because of its own merits as an addition to our game.<br />
<br />
The beautiful thing about the license our game is distributed under, as compared to closed-source, commercial games, is that if you want that feature badly enough, you can take the code and art of our game and modify it yourself; you are free to re-use any work in Wesnoth, as long as you follow the rules of the [http://www.fsf.org/copyleft/gpl.html GPL]. From this, you can build a game exactly the way that you like. Just don't expect us to build that game for you. Building this game is our hobby, not our profession, and you did not pay us to make it; rather, we are the ones who have paid for it, in time and labor.<br />
<br />
===Do you want help making this game? How can I help?===<br />
Yes, we want your help. Whether you're a programmer, artist, musician, writer, translator, level designer, playtester, or just have some great suggestions, you're welcome to contribute. How? You can:<br />
* join the [http://www.wesnoth.org/wiki/Project Project]<br />
* share your point of view at the [http://www.wesnoth.org/forum/ Forum]<br />
* talk with us on [irc://irc.wesnoth.org/wesnoth IRC]<br />
* report bugs you find at [[ReportingBugs]]<br />
* update the wiki<br />
* play against us via the Multiplayer menu<br />
* vote for Wesnoth at your favorite gaming web site<br />
* Spread the word!<br />
<br />
=== What are the system requirements? ===<br />
<br />
We are not completely certain, but an x86 running at 600MHz with 128MB RAM should be adequate. Slower machines will have trouble scrolling large maps or processing AI turns with many units. See the [http://www.wesnoth.org/forum/viewtopic.php?t=7384 forum thread] about minimum and recommended system requirements.<br />
<br />
=== I'm bored; how do I speed the game up? ===<br />
<br />
There are several preferences you can change to shorten the time that the AI takes to make its moves. "Accelerated Speed" will make units move and fight faster. "Skip AI Moves" will not show the AI's units moving from hex to hex. Finally, you can turn off all combat animations via the "Show Combat" option on the Advanced tab.<br />
<br />
=== My computer is too slow; how do I speed the game up? ===<br />
<br />
First, turn off the music and sound effects. Turning off the color cursors will make your cursor respond faster. If scrolling the map is slow, run the game in "Full Screen" mode, not in a window. Turn off combat animations via the "Show Combat" option on the Advanced tab. You can try turning off halos and combat results, but this might make gameplay more difficult.<br />
<br />
== Gameplay and Controls ==<br />
<br />
=== How do I learn to play? ===<br />
<br />
If you just want to jump right in, start the game and play the tutorial. If you like reading documentation, see [[WesnothManual]], which is also distributed as a PDF file. At any time while playing, you can select help from the menu button (or hit F1). The online help is quite extensive and provides information on terrains, weapons, traits, abilities, units and a good overview of how to play.<br />
<br />
=== My unit leveled up but didn't improve. What happened? ===<br />
<br />
This is called "After Maximum Level Advancement" or AMLA for short. While most level 0, 1, and 2 units can advance, some cannot. However, some level 3 units can advance to level 4, or even 5. You can see whether a unit can advance further by right clicking and selecting "description."<br />
<br />
After a unit reaches the highest level it can get, every time it gains 100 experience it gains 3 hitpoints. It does not heal when this happens. This is a minor bonus so that experience gained by maxed out units is not altogether wasted. It is generally better to give experience to lower level units, rather than continue to advanced units that have reached their maximum level.<br />
<br />
If the unit in question is the Necrophage, this is not a bug. The Necrophage eats the corpses of the dead, allowing it to periodically completely heal. Leveling into itself is how this is carried out.<br />
<br />
=== I tried to trap an enemy with several weak units, but it still escaped. What happened? ===<br />
<br />
Most units exert a zone of control (or ZOC). IF an enemy moves into one of the six adjacent hexes, the zone of control will prevent it from moving any farther. However some weak units are level 0, meaning they are so weak that they do not have a ZOC. You can still surround an enemy unit entirely with level 0 units to keep it from escaping, but if there is any gap in your ranks, it could escape.<br />
<br />
Also, some units have the "skirmish" ability, which allows them to ignore ZOCs.<br />
<br />
=== How can I see where an enemy unit can move next turn? ===<br />
<br />
During you turn you can click on an enemy unit. Wesnoth will highlight all the hexes the unit can move to in the next turn. This is useful when trying to arrange your units to block an enemy's movement.<br />
<br />
=== There's too much luck in this game! ===<br />
<br />
Sooner or later, you will become frustrated when your archmage with four 70% attacks misses all four times. This does not mean that the AI is cheating or the random number generator is futzed. It means you are noticing random negative events more than positive ones. During the development of the game, many mathematicians have done sophisticated statistical analysis of the combat system. Likewise, programmers have examined the random number generator. Wesnoth has been deliberately designed so that the streaks of "bad" and "good" luck are a part of the gameplay.<br />
<br />
Since Wesnoth is GPLed, it is possible that, after the 1.0 release, a new development team will "fork" the source and produce a version more like Heroes of Might & Magic, with no randomness. Until then, don't charge with your horsemen against rock trolls at night...<br />
<br />
=== The (random unit) is overpowered/underpowered! ===<br />
<br />
The development team has spent years tweaking the units in the game. Each unit has had its gold cost, attack types, combat damage, defensive values, resistances, upgrade paths, and other stats carefully scrutinized and loudly discussed in the forum. However, the game code and the units were being modified right up until the 1.0 release, so some unbalanced units may have slipped through.<br />
<br />
If you have evidence to back up your claim, search the forum for past discussions about this unit, and then try posting.<br />
<br />
=== The (random scenario) is too hard/easy! ===<br />
<br />
See above answer about random units.<br />
<br />
=== What do the different difficulty levels do? ===<br />
<br />
That depends on the scenario. Usually, the opponent will get more money and be able to recruit higher-level units at higher difficulty levels, and you will have fewer turns available.<br />
<br />
== Maps, Scenarios and Campaigns ==<br />
<br />
=== How do I beat scenario _______ ? ===<br />
<br />
If you are stuck on a scenario in a campaign, you'll probably find a walkthrough at [[MainlineScenarios]]. Or check out the "Strategies and Tips" forum at http://www.wesnoth.org/forum/viewforum.php?f=3<br />
<br />
=== Are there any tools to help me create maps and scenarios? ===<br />
Yes, there is a tool called wesnoth_editor. It is a normal map-editor that should be a good help for creating the plain maps. For creating the scenarios there already is a scenario-editor included in the mac build. But this editor is rather outdated and it exists only for MacOS X. At the moment some community members are working on creating a nice and working scenario editor. You can have a look at the [http://www.wesnoth.org/forum/viewtopic.php?t=6925 forum post] about this tool. You will also find more info at [[CampGen]].<br />
<br />
=== How do I download user campaigns? ===<br />
Choose "Campaigns" in the main Wesnoth menu. Then scroll down to the bottom and choose "Get More Campaigns..." or since 1.1.5 there is a "Get add-ons" button in the main menu. This connects you to the campaign server. In the campaign server you can view a list of all available campaigns and download them, as well as posting or deleting your own campaigns. If you are behind a firewall you may not be able to connect the the campaign server; in this case try contacting the author of the campaign via the forums to see if there is another way you can get the campaign.<br />
<br />
=== I already created a campaign and published it on the campaign server. How can I get translations for the campaign? ===<br />
Just have a look at [[WesCamp]]. This project is the easiest way to get translations for your campaign. All the info you need you can find at [[WesCamp]].<br />
<br />
===How do I place an object or unit on my map with the map editor?===<br />
You can't. You need to make a multiplayer scenario file. There are more details on the [[BuildingMaps|maps]] page.<br />
<br />
== Multiplayer ==<br />
<br />
===How to find players for multiplayer game?===<br />
Hang around for a while on multiplayer servers and you might find someone to play with. If you observe other people playing you will get informed when someone joins the servers. Maybe you find someone willing to play in the irc channel dedicated to mp: #wesnoth-mp at irc.freenode.net.<br />
You can also join #wesnoth at irc.freenode.net.<br />
<br />
===How can I make my computer into a dedicated Wesnoth server?===<br />
<br />
To setup a dedicated Wesnoth server, you have to compile the game with the "--enable-server" flag, and after you install, simply run wesnothd from the console. This will start the server, listening on TCP port 15000. To compile the server only you can use the flags "--disable-game --enable server". If you aren't using a linux or mac operating system, there are a few ways you can compile on Windows...here is one way http://www.wesnoth.org/wiki/CompilingWesnoth/CrossCompiling<br />
<br />
===Which versions of Wesnoth can play together?===<br />
<br />
I'm on a MAC, and my friends are on XP. I would like to play together with them. Is this currently possible? <br />
<br />
YES! All you need is to have the same version number.<br />
<br />
For a list of Mac-XP-compatible games (including BfW) see: http://www.insidemacgames.com/forum/index.php?showtopic=21818<br />
<br />
== Translations ==<br />
<br />
===I selected an asian translation and am not able to see the letters correctly. What happened?===<br />
<br />
Since the size of the necessary fonts is too large, you'll need to download them separately (if you don't already have them). After that, simply copy the font to the '''fonts/''' directory in your wesnoth installation.<br />
* Chinese font: [ftp://cle.linux.org.tw/pub/fonts/ttf/unicode/Arphic/gkai00mp.ttf gkai00mp.ttf]<br />
* Japanese font: [http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/sqs-xml/sqs-font/sazanami-gothic.ttf sazanami-gothic.ttf]<br />
<br />
If you have futher questions have a look at [[WesnothAsianLanguages|this]] page.<br />
<br />
== Other Questions You Have ==<br />
<br />
The best way to get answers to less-frequently asked questions is by visiting the [http://www.wesnoth.org/forum BFW forum]. There are plenty of people willing to help. Make sure you read ALL of the forum sticky notes and announcements before posting.</div>Baufo