The Battle for Wesnoth Wiki - User contributions [en]

WesnothReviews

2007-12-11T17:24:17Z

Ott: /* English */ add TidBITS

== Catalan ==

* BULMA: [http://bulma.net/body.phtml?nIdNoticia=2242 La Batalla per Wesnoth, estratègia en estat pur], October 2005, BfW 1.0

== Czech ==

* root.cz: [http://www.root.cz/clanky/battle-for-wesnoth/ Battle for Wesnoth], April 2004, BfW 0.7
* AbcLinuxu: [http://www.abclinuxu.cz/clanky/hry-a-zabava/battle-for-wesnoth Battle for Wesnoth], November 2005, BfW 1.0
* LinuxEXPRES: [http://www.linuxexpres.cz/bitva-o-wesnoth Bitva o Wesnoth], March 2006, BfW 1.0.2
* root.cz: [http://www.root.cz/clanky/battle-for-wesnoth-verze-1-0/ Battle for Wesnoth verze 1.0], April 2006, BfW 1.0.2

== English ==

* Tea Leaves: [http://www.tgr.com/weblog/archives/000034.html Review: The Battle for Wesnoth], March 2004, BfW 0.6.x
* PCBurn: [http://pcburn.com/game_review-Battle_for_Wesnoth.php Game Review: Battle for Wesnoth], March 2004, BfW 0.6.99.2
* The Mac Mind: [http://www.themacmind.com/modules.php?op=modload&name=News&file=article&sid=631&mode=nested&order=0&thold=0 Open Source Games: The Battle for Wesnoth], December 2004, BfW 0.8.8
* Linux Weekly Newsletter: [http://lwn.net/Articles/154429/ The Battle for Wesnoth hits 1.0], October 2005, BfW 1.0
* Macworld.co.uk: [http://www.macworld.co.uk/news/index.cfm?NewsID=12886&Page=1&pagePos=1 Free open-source gamer's treat unleashed], October 2005, BfW 1.0
* TidBITS: [http://www.tidbits.com/tb-issues/TidBITS-808.html Strategy for Free], December 2005, BfW 1.0
* Inside Mac Games: [http://www.insidemacgames.com/reviews/view.php?ID=642 Battle For Wesnoth], October 2005, BfW 1.0
* Macobserver: [http://www.macobserver.com/columns/slackersguide/2005/20051014.shtml The Slacker's Guide - Desert Combat and Wesnoth], October 2005, BfW 1.0
* OS Reviews: [http://www.osreviews.net/reviews/games/wesnoth Hero of Strategy Games], April 2006, BfW 1.0.2
* everything2: [http://www.everything2.com/index.pl?node_id=1677196 Two reviews], dated September 2004 (BfW 0.8.3) and August 2006 (BfW 1.0.2)
* Reloaded: [http://www.reloaded.org/rate/68/5/], BfW 1.0.2
* Home of the underdogs: [http://www.the-underdogs.info/game.php?id=5290]
* Runtime HQ: [http://www.runtime-hq.com/index.php?option=com_content&task=view&id=27&Itemid=39]
* Free Software Magazine: [http://www.freesoftwaremagazine.com/articles/wesnoth_interview_player The Battle for Wesnoth is on in the days that never were], April 2006, BfW 1.0.2
* 100% Seji: [http://my.opera.com/Seji/blog/now-playing-battle-for-wesnoth Battle for Wesnoth], May 2007, BfW 1.2.4
* Opensoft: [http://open-soft.org/reviews/games/turn-based-strategy-battle-for-wesnoth Turn-Based Strategy: Battle for Wesnoth], June 2007, BfW 1.2.4
* Phoronix: [http://www.phoronix.com/scan.php?page=article&item=890&num=1 The Battle For Wesnoth] October 2007, BfW 1.2.6
* Simple Thoughts: [http://blog.taragana.com/index.php/archive/game-review-tips-battle-for-wesnoth/ Game Review & Tips: The Battle for Wesnoth] November 2007, BfW 1.2.4
* TidBITS: [http://db.tidbits.com/article/9335 Open Source Mac Gaming: 10 Free Games Reviewed] December 2007

== French ==

* JeuxLibres.net: [http://jeuxlibres.net/showgame/battle_for_wesnoth.html The Battle For Wesnoth ], 27 May 2004, BfW 0.7.x (update each version)
* Jeux-Stratégie.com: [http://www.jeux-strategie.com/The_Battle_For_Wesnoth.1734.0.html The Battle For Wesnoth ], October 2004, BfW 0.8.5
* Framasoft: [http://www.framasoft.net/article2293.html The Battle for Wesnoth], July 2005, BfW 0.9
* PC4War,[http://www.wesnoth.org/images/wesnoth_pc4war.jpg The Battle for Wesnoth 0.9.3], August 2005, BfW 0.9.3
* Jouer.org: [http://www.jouer.org/Jeux-Gratuits/Battle-For-Wesnoth-00505.html Battle For Wesnoth], November 2005, BfW 1.0.1

== German ==
* OS-ISO.DE: [http://os-iso.de/wesnoth-strategie-p-99.html Battle for Wesnoth: Beschreibung/Screenshots] January 2007 BfW 1.2.1 (auch download)
* HOLARSE: [http://www.holarse-linuxgaming.de/h2006/space/The+Battle+for+Wesnoth The Battle for Wesnoth], December 2006, BfW 1.2 (it's a wiki, date is last update)
* Games4Mac: [http://games4mac.de/content_g4m/reviews/battle_for_wesnoth.php Battle for Wesnoth], October 2005, BfW 1.0
* Linuxuser.de: [http://www.linux-user.de/ausgabe/2006/07/066-wesnoth/index.html Strategen gefragt], July 2006, BfW 1.0.2

== Polish ==

* wyzimir: [http://wyzimir.jogger.pl/2005/11/08/bitwa-o-wesnoth/ Bitwa o Wesnoth], listopad(??) 2005, BfW 1.1-svn

== Russian ==

* ЛКИ: [http://www.lki.ru/guide.php?id=2270 Battle for Wesnoth], April 2006, BfW 1.0

== Slovak ==

* Viliam Búr: [http://bur.blog.sme.sk/c/22376/Bitka-o-Wesnoth.html Bitka o Wesnoth], October 2005, BfW 1.0
* Viliam Búr: [http://bur.blog.sme.sk/c/74037/Bitka-o-Wesnoth-verzia-12.html Bitka o Wesnoth, verzia 1.2], December 2006, BfW 1.2

== Spanish ==

* JuegosLibres.net: [http://www.juegoslibres.net/estrategia/battle-for-wesnoth-vive-tu-propia-batalla.html Battle for Wesnoth: vive tu propia batalla], May 2006, BfW 1.0.2
* Mouse Digital: [http://www.mouse.cl/2005/productos/12/09/index.asp La batalla de Wesnoth], December 2006, BfW 1.0.2
* Meristation: [http://www.meristation.com/v3/des_analisis.php?id=cw4600fdf7c1637&idj=cw4600f9efed5b6&pic=PC Una batalla épica], March 2007, BfW 1.2.3

== Multilingual ==

* Wikipedia ([http://ca.wikipedia.org/wiki/The_battle_of_Wesnoth Catalan], [http://cs.wikipedia.org/wiki/Battle_for_Wesnoth Czech], [http://da.wikipedia.org/wiki/Battle_for_Wesnoth Danish], [http://en.wikipedia.org/wiki/Battle_for_Wesnoth English], [http://fi.wikipedia.org/wiki/Taistelu_Wesnothista Finnish], [http://fr.wikipedia.org/wiki/Battle_for_Wesnoth French], [http://de.wikipedia.org/wiki/Battle_for_Wesnoth German], [http://he.wikipedia.org/wiki/%D7%94%D7%A7%D7%A8%D7%91_%D7%A2%D7%9C_%D7%95%D7%A1%D7%A0%D7%95%D7%AA%27 Hebrew], [http://it.wikipedia.org/wiki/Battle_for_Wesnoth Italian], [http://no.wikipedia.org/wiki/Battle_for_Wesnoth Norwegian], [http://pl.wikipedia.org/wiki/Battle_for_Wesnoth Polish], [http://ru.wikipedia.org/wiki/Battle_for_Wesnoth Russian], [http://sk.wikipedia.org/wiki/Bitka_o_Wesnoth Slovak], [http://es.wikipedia.org/wiki/Battle_for_Wesnoth Spanish], [http://sv.wikipedia.org/wiki/Kampen_om_Wesnoth Swedish])

== See Also ==
* [[WhatArePlayersSaying]]? - Quotes from newssites, blogs and players
* [[Play]]

User:Ott

2006-12-27T14:12:46Z

Ott: update

I worked on Battle for Wesnoth during 2004 and 2005, mainly bug fixing, documentation, translation and tweaking numerical calculations. A lot of time also went into behind-the-scenes maintenance, including overseeing the bug database and changelog, tracking down and fixing out of sync and other code errors, subediting game text, and improving game help. I am proud to have been part of the team getting 1.0 out the door, and also stayed a while longer to ensure 1.0.2 had complete translations for British English, Magyar and Afrikaans.

It's great to see that the game has continued to improve, on to 1.2 and hopefully beyond.

== Articles ==
Some of my writing about the game may be worth reading:
* [http://www.wesnoth.org/forum/viewtopic.php?p=91620#91620 Distribution of damage] details the problems with the old damage model, culminating in [http://www.wesnoth.org/forum/viewtopic.php?t=4240 The RATE damage model] (with resistances at the end) used in the game since 0.8.10.
* [http://www.wesnoth.org/forum/viewtopic.php?t=5867 Calculating %-to-kill] and a [http://www.wesnoth.org/forum/viewtopic.php?t=8273 %-to-kill] consider how to calculate the probability that units in a skirmish kill each other (or survive) -- a nontrivial problem!
* [http://www.wesnoth.org/forum/viewtopic.php?p=78398#78398 Overview of postings about in-game random number generation] gives an overview of this frequently discussed issue. See also another [https://gna.org/bugs/?func=detailitem&item_id=4664#comment1 short note] related to this.
* [http://www.wesnoth.org/forum/viewtopic.php?p=53968#53968 Analysing anomalies in game statistics] culminated in discovering some bugs with the statistics in the game, and a script to analyse statistics for anomalies.
* Rant about [http://www.wesnoth.org/forum/viewtopic.php?p=113959#113959 slow] being too complex, and an [http://www.wesnoth.org/forum/viewtopic.php?p=115789#115789 alternative proposal for slow] is still being discussed.
* [[Status of User Scenarios]]
* [http://www.wesnoth.org/forum/viewtopic.php?p=117192#117192 Programming challenge: healing algorithm] and [http://www.wesnoth.org/forum/viewtopic.php?p=117761#117761 part 2] discuss the flaws in the current healing algorithm and identify the kernel of the problem that needs to be solved to improve it.

== See Also ==
* [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=970 ott's forum profile]
* [[About]]

Credits

2005-12-29T14:00:57Z

Ott: /* Developers */

In July 2003, '''David White''' released the first version of Wesnoth. Since then, many people have joined the project, contributing in very different ways.

== Developers ==
* Alfredo Beaumont (ziberpunk) - autotools
* András Salamon ([[User:Ott|ott]]) - QA, bug fixing, subediting, game mechanics
* [mailto:dragonking_AT_o2.pl Bartek Waresiak] (Dragonking) - multiplayer developer
* Benjamin Drieu (benj) - scenario designer
* Benoît Timbert (Noyga) - coder
* Bram Ridder (Morloth) - editor improvements
* [[User:bruno|Bruno Wolff III]] - Campaign web interface, [[MainlineScenarios#The_Dark_Hordes|The Dark Hordes]] maintainer, bug fixing, minor coder
* Cédric Duval - coder, internationalization manager
* Crossbow/Miyo - administrator, release manager
* David Philippi (Torangan) - internationalization manager, wescamp
* [mailto:davidnwhite_AT_verizon.net David White] (Sirp) - founder, lead developer, scenario designer
* Francisco Muñoz (fmunoz) - artwork manager, original units, scenario designer
* Guillaume Melquiond (silene) -
* Hogne Håskjold (frame) - terrain designer
* [mailto:isaac_AT_sindominio.net Isaac Clerencia] - administrator, release manager
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - internationalization manager
* James Spencer (Shade) - scenario designer
* Jan Zvánovec (jaz) -
* Jérémy Rosen (Boucman) - coder
* John B. Messerly (jbm) -
* [mailto:forcemaster_AT_gmx.net Jon Daniel] (forcemstr) -
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) -
* Joseph Simmons (Turin) - scenario designer, graphics
* Jörg Hinrichs (Yogi Bear/YogiHH) - coder
* J.R. Blain (Cowboy) -
* [mailto:mcnabb_AT_gravity.psu.edu J.W.C. McNabb] (Darth Fool) - coder, graphics
* Justin Zaun (jzaun) - coder, scenario designer
* [mailto:erl_AT_erl.se Kristoffer Erlandsson] (erl) - help system, editor
* Maksim Orlovich (SadEagle) -
* Mark Michelsen (skovbaer) - internationalization manager
* Nicolas Weeger (ryo) - Python API
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - several parts of the code, notably terrain graphics code
* Richard Kettering (Jetryl) - artwork coordinator, several graphics
* Richard S. (Noy) - multiplayer developer
* Scott Klempner - campaign maintainer
* Soliton - multiplayer developer
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - internationalization manager
* [mailto:ydirson_AT_altern.org Yann Dirson] - gettext support, tinygui
* Zas -

== Artists ==
* Aleksi - music coordinator
* Alex Jarocha-Ernst (Jormungandr) - portraits
* Andrew James Patterson (Kamahawk) - sprites
* antwerp - sprites
* Christophe Anjard - sprites
* Diego Brea (Cobretti) - sprites
* Eli Dupree (Elvish Pillager) - sprites
* Fredrik Lindroth - music
* Gareth Miller (Gafgarion) - sprites
* James Barton (Sangel) - sprites
* James Woo (Pickslide) - portraits
* Jason Lutes - portraits
* Jimmy Olsson (Azlan) - icons
* Johanna Manninen (lohari) - tiles
* John Muccigrosso (Eponymous Archon) - sprites
* John-Robert Funck (XJaPaN) - sprites
* Jonatan Alamà (tin) - logo
* Joseph Toscano (zhaymusic.com) - music
* J.W. Bjerk (Eleazar) - tiles, graphics
* Michael Gil de Muro (grp21) - portraits
* Neorice - sprites
* Pau Congost - music
* Pekka Aikio - tiles
* Peter Geinitz (Shadow) - sprites
* Robert Bolin (Zebulon) - tiles
* Slainte - sprites
* Stephen Stone - [graphics]
* Svetac - [graphics]

== Translators ==
* adson - hungarian translation
* İhsan Akın - turkish translation
* Alessio D'Ascanio (otaku) - italian translation
* Alexander Alexiou (Santi) - greek translation
* Alexander Kjäll (capitol) - swedish translation
* Alexandr Menovchicov - russian translation
* Alfredo Beaumont (ziberpunk) - basque translation
* Ambra Viviani Loos - brazilian portuguese translation
* Americo Iacovizzi (DarkAmex) - italian translation
* Anders K. Madsen (madsen) - danish translation
* András Salamon ([[User:Ott|ott]]) - afrikaans, english and hungarian translation
* Andre Schmidt (schmidta) - german translation
* Anežka Bubeníčková (Bubu) - czech translation
* Ankka - finnish translation
* Anton Tsigularov (Atilla) - bulgarian translation
* Arkadiusz Danilecki (szopen) - polish translation
* Arne Deprez - dutch translation
* Artur R. Czechowski - polish translation
* Aurélien Brevers (Breversa) - french translation
* Azamat Hackimov - russian translation
* Bartek Waresiak (Dragonking) - polish translation
* Beer (Eddi) - hungarian translation
* Benoit Astruc - french translation
* Bjarke Sørensen (basher) - danish translation
* Boris Stumm (quijote_) - german translation
* BOrsuk - polish translation
* Cédric Duval - french translation
* Carles Company (brrr) - catalan translation
* Celso Goya - brazilian portuguese translation
* Christoph Berg (chrber) - german translation
* Claus Aranha - brazilian portuguese translation
* crys0000 - italian translation
* Dan Rosàs Garcia (focks) - catalan translation
* Daniel López (Azazelo) - catalan translation
* DaringTremayne - french translation
* David Martínez Moreno - spanish translation
* David Nečas (Yeti) - czech translation
* dentro - hungarian translation
* Enes Akın (yekialem) - turkish translation
* Erik J. Mesoy (Circon) - norwegian translation
* Eugenio Favalli (ElvenProgrammer) - italian translation
* Federico Tomassetti - italian translation
* Flamma - spanish translation
* Franciso Muñoz (fmunoz) - spanish translation
* François Orieux - french translation
* Gabriel Rodríguez (Chewie) - spanish translation
* Georgi Dimitrov (oblak)- bulgarian translation
* Gerfried Fuchs (Alfie) - german translation
* Gilluin - hungarian translation
* Guillaume Duwelz-Rebert - french translation
* [mailto:massart.guillaume_AT_wanadoo.fr Guillaume Massart (Piou2fois)] - french translation
* Guillaume Melquiond (silene) - french translation
* Hallvard Norheim Bø (Lysander) - norwegian translation
* Håvard Korsvoll - norwegian translation
* Huang huan (unicon) - chinese translation
* Ilya Kaznacheev - russian translation
* isazi - italian translation
* Iván Herrero (navitux) - spanish translator
* Jaka Kranjc (lynx) - slovenian translation
* Jan Greve (Jan) - german translation
* Jan-Heiner Laberenz (jan-heiner) - german translation
* Jean Privat (Tout) - french translation
* Jean-Luc Richard (Le Gnome) - french translation
* Jérémy Rosen (Boucman) - french translation
* Jesper Fuglsang Wolff (ulven) - danish translation
* Jonatan Alamà (tin) - catalan translation
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) - catalan translation coordinator
* Jose Gordillo (kilder) - spanish and catalan translation
* Jose Manuel Gomez (joseg) - spanish translation
* Julien Moncel - french translation
* Julien Tailleur - french translation
* Julen Landa (genars) - basque translation
* Kai Ensenbach (Pingu) - german translation
* Kékkői László (BlackEvil) - hungarian translation
* Karol Nowak (grzywacz) - polish translation
* Katerina Sykioti - greek translation
* Kertész Csaba - hungarian translation
* Khiraly - hungarian translation
* kko - finnish translation
* Konstantinos Karasavvas - greek translation
* Kosif - turkish translation
* Kovács Dániel - hungarian translation
* krix - hungarian translation
* Lala - dutch translation
* Leo Danielson (Lugo Moll) - swedish translation
* Lim Choon Kiat - 林俊杰 - chinese translation
* Lukáš Faltýnek - czech translation
* Maarten Albrecht - dutch translation
* Mark Michelsen (skovbaer) - danish translation
* Mark Polo (mpolo) - latin translation
* Mark Recasens - catalan translation
* Mart Tõnso - estonian translation
* Martin Šín - czech translation
* Mathias Bundgaard Svensson (freaken) - danish translation
* Matias Parmala - finnish translation
* methinks - polish translation
* Michał Jedynak (Artanis) - polish translation
* Michel Loos - brazilian portuguese translation
* Mikel Olasagasti (Hey_neken) - basque translation
* Mintaka - czech translation
* Naoki Iimura - japanese translation
* Nico Oliver - afrikaans translation
* Nicolas Boudin (Blurgk) - french translation
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - german translation
* Nobuhito Okada - japanese translation
* [mailto:tapik_AT_buchtovi.cz Oto Buchta] ([[User:Tapik|tapik]]) - czech translation
* Pau Rul·lan Ferragut - catalan translation
* Paweł Stradomski - polish translation
* Paweł Tomak - polish translation
* paxed - finnish translation
* Petr Kopač (Ferda) - czech translation
* Petr Kovár (Juans) - czech translation
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - french translation
* Pieter Vermeylen (Onne) - dutch translation
* Pınar Yanardağ (moonquelle) - turkish translation
* Renato Cunha - brazilian portuguese translation
* Roel Thijs (Roel) - dutch translation
* RokStar - italian translation
* Roman Tuchin (Sankt) - russian translation
* Rudolf Orság - czech translation
* Ruben Philipp Wickenhäuser (The Very Uhu) - german translation
* Sérgio de Miranda Costa - brazilian portuguese translation
* Selim Farsakoğlu - turkish translation
* Sofronius - czech translation
* Spiros, Giorgis - greek translation
* Srecko Toroman (FreeCraft) - serbian translation
* Stefan Bergström (tephlon) - swedish translation
* Stephan Grochtmann (Schattenstephan) - german translation
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - swedish translation
* Susanne Mesoy (Rarlgland) - norwegian translation
* Széll Tamás (TomJoad) - hungarian translation
* Tiago Souza (Salvador) - brazilian portuguese translation
* Tobe Deprez - dutch translation
* Vít Komárek - czech translation
* Vít Krčál - czech translation
* Viliam Bur - slovak translation
* wint3r - swedish translation
* [mailto:ydirson_AT_altern.org Yann Dirson] - french translation
* Yuji Matsumoto - japanese translation
* Zas - french translation

== Other Contributions ==
* Ben Anderman (crimson_penguin) - unit list
* Dacyn - scenario designer
* Cyril Bouthors (CyrilB) - debian packager, patron
* Darryl Dixon - packager
* edge - packager
* Francesco Gigli (Jaramir) - wiki, wesnoth.slack.it
* Frédéric Wagner
* Jay Hopping - packager
* Jeff Breidenbach (Jab) - Bilinear interpolation
* Marcin Konicki (ahwayakchih) - BeOS packager
* Marcus Phillips (Sithrandel) - Mac OS X packager
* Mark Michelsen (skovbaer) - slackware packager
* Mike Quinones (Doc Paterson) - multiplayer maps
* Peter Groen (pg) - multiplayer maps
* Ruben Philipp Wickenhäuser (The Very Uhu) - multiplayer maps
* Tom Chance (telex4) - multiplayer maps, scenario balancing
* Sam Phillips (dark172) - creation of campains and multiplayer maps

{{Home}}

Credits

2005-12-29T13:58:23Z

Ott: /* Developers */

In July 2003, '''David White''' released the first version of Wesnoth. Since then, many people have joined the project, contributing in very different ways.

== Developers ==
* Alfredo Beaumont (ziberpunk) - autotools
* András Salamon ([[User:Ott|ott]]) - QA and bug fixing, subediting, translator
* [mailto:dragonking_AT_o2.pl Bartek Waresiak] (Dragonking) - multiplayer developer
* Benjamin Drieu - scenario designer
* Benoît Timbert (Noyga) - coder
* Bram Ridder (Morloth) - editor improvements
* [[User:bruno|Bruno Wolff III]] - Campaign web interface, [[MainlineScenarios#The_Dark_Hordes|The Dark Hordes]] maintainer, bug fixing, minor coder
* Cédric Duval - coder, internationalization manager
* Crossbow/Miyo - administrator, release manager
* David Philippi (Torangan) - internationalization manager, wescamp
* [mailto:davidnwhite_AT_verizon.net David White] (Sirp) - founder, lead developer, scenario designer
* Francisco Muñoz (fmunoz) - artwork manager, original units, scenario designer
* Guillaume Melquiond (silene) -
* Hogne Håskjold (frame) - terrain designer
* [mailto:isaac_AT_sindominio.net Isaac Clerencia] - administrator, release manager
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - internationalization manager
* James Spencer (Shade) - scenario designer
* Jan Zvánovec (jaz) -
* Jérémy Rosen (Boucman) - coder
* John B. Messerly -
* [mailto:forcemaster_AT_gmx.net Jon Daniel] (forcemstr) -
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) -
* Joseph Simmons (Turin) - scenario designer, graphics
* Jörg Hinrichs (Yogi Bear/YogiHH) - coder
* J.R. Blain (Cowboy) -
* [mailto:mcnabb_AT_gravity.psu.edu J.W.C. McNabb] (Darth Fool) - coder, graphics
* Justin Zaun (jzaun) - coder, scenario designer
* [mailto:erl_AT_erl.se Kristoffer Erlandsson] (erl) - help system, editor
* Maksim Orlovich (SadEagle) -
* Mark Michelsen (skovbaer) - internationalization manager
* Nicolas Weeger (ryo) - Python API
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - several parts of the code, notably terrain graphics code
* Richard Kettering (Jetryl) - artwork coordinator, several graphics
* Richard S. (Noy) - multiplayer developer
* Scott Klempner - campaign maintainer
* Soliton - multiplayer developer
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - internationalization manager
* [mailto:ydirson_AT_altern.org Yann Dirson] - gettext support, tinygui
* Zas -

== Artists ==
* Aleksi - music coordinator
* Alex Jarocha-Ernst (Jormungandr) - portraits
* Andrew James Patterson (Kamahawk) - sprites
* antwerp - sprites
* Christophe Anjard - sprites
* Diego Brea (Cobretti) - sprites
* Eli Dupree (Elvish Pillager) - sprites
* Fredrik Lindroth - music
* Gareth Miller (Gafgarion) - sprites
* James Barton (Sangel) - sprites
* James Woo (Pickslide) - portraits
* Jason Lutes - portraits
* Jimmy Olsson (Azlan) - icons
* Johanna Manninen (lohari) - tiles
* John Muccigrosso (Eponymous Archon) - sprites
* John-Robert Funck (XJaPaN) - sprites
* Jonatan Alamà (tin) - logo
* Joseph Toscano (zhaymusic.com) - music
* J.W. Bjerk (Eleazar) - tiles, graphics
* Michael Gil de Muro (grp21) - portraits
* Neorice - sprites
* Pau Congost - music
* Pekka Aikio - tiles
* Peter Geinitz (Shadow) - sprites
* Robert Bolin (Zebulon) - tiles
* Slainte - sprites
* Stephen Stone - [graphics]
* Svetac - [graphics]

== Translators ==
* adson - hungarian translation
* İhsan Akın - turkish translation
* Alessio D'Ascanio (otaku) - italian translation
* Alexander Alexiou (Santi) - greek translation
* Alexander Kjäll (capitol) - swedish translation
* Alexandr Menovchicov - russian translation
* Alfredo Beaumont (ziberpunk) - basque translation
* Ambra Viviani Loos - brazilian portuguese translation
* Americo Iacovizzi (DarkAmex) - italian translation
* Anders K. Madsen (madsen) - danish translation
* András Salamon ([[User:Ott|ott]]) - afrikaans, english and hungarian translation
* Andre Schmidt (schmidta) - german translation
* Anežka Bubeníčková (Bubu) - czech translation
* Ankka - finnish translation
* Anton Tsigularov (Atilla) - bulgarian translation
* Arkadiusz Danilecki (szopen) - polish translation
* Arne Deprez - dutch translation
* Artur R. Czechowski - polish translation
* Aurélien Brevers (Breversa) - french translation
* Azamat Hackimov - russian translation
* Bartek Waresiak (Dragonking) - polish translation
* Beer (Eddi) - hungarian translation
* Benoit Astruc - french translation
* Bjarke Sørensen (basher) - danish translation
* Boris Stumm (quijote_) - german translation
* BOrsuk - polish translation
* Cédric Duval - french translation
* Carles Company (brrr) - catalan translation
* Celso Goya - brazilian portuguese translation
* Christoph Berg (chrber) - german translation
* Claus Aranha - brazilian portuguese translation
* crys0000 - italian translation
* Dan Rosàs Garcia (focks) - catalan translation
* Daniel López (Azazelo) - catalan translation
* DaringTremayne - french translation
* David Martínez Moreno - spanish translation
* David Nečas (Yeti) - czech translation
* dentro - hungarian translation
* Enes Akın (yekialem) - turkish translation
* Erik J. Mesoy (Circon) - norwegian translation
* Eugenio Favalli (ElvenProgrammer) - italian translation
* Federico Tomassetti - italian translation
* Flamma - spanish translation
* Franciso Muñoz (fmunoz) - spanish translation
* François Orieux - french translation
* Gabriel Rodríguez (Chewie) - spanish translation
* Georgi Dimitrov (oblak)- bulgarian translation
* Gerfried Fuchs (Alfie) - german translation
* Gilluin - hungarian translation
* Guillaume Duwelz-Rebert - french translation
* [mailto:massart.guillaume_AT_wanadoo.fr Guillaume Massart (Piou2fois)] - french translation
* Guillaume Melquiond (silene) - french translation
* Hallvard Norheim Bø (Lysander) - norwegian translation
* Håvard Korsvoll - norwegian translation
* Huang huan (unicon) - chinese translation
* Ilya Kaznacheev - russian translation
* isazi - italian translation
* Iván Herrero (navitux) - spanish translator
* Jaka Kranjc (lynx) - slovenian translation
* Jan Greve (Jan) - german translation
* Jan-Heiner Laberenz (jan-heiner) - german translation
* Jean Privat (Tout) - french translation
* Jean-Luc Richard (Le Gnome) - french translation
* Jérémy Rosen (Boucman) - french translation
* Jesper Fuglsang Wolff (ulven) - danish translation
* Jonatan Alamà (tin) - catalan translation
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) - catalan translation coordinator
* Jose Gordillo (kilder) - spanish and catalan translation
* Jose Manuel Gomez (joseg) - spanish translation
* Julien Moncel - french translation
* Julien Tailleur - french translation
* Julen Landa (genars) - basque translation
* Kai Ensenbach (Pingu) - german translation
* Kékkői László (BlackEvil) - hungarian translation
* Karol Nowak (grzywacz) - polish translation
* Katerina Sykioti - greek translation
* Kertész Csaba - hungarian translation
* Khiraly - hungarian translation
* kko - finnish translation
* Konstantinos Karasavvas - greek translation
* Kosif - turkish translation
* Kovács Dániel - hungarian translation
* krix - hungarian translation
* Lala - dutch translation
* Leo Danielson (Lugo Moll) - swedish translation
* Lim Choon Kiat - 林俊杰 - chinese translation
* Lukáš Faltýnek - czech translation
* Maarten Albrecht - dutch translation
* Mark Michelsen (skovbaer) - danish translation
* Mark Polo (mpolo) - latin translation
* Mark Recasens - catalan translation
* Mart Tõnso - estonian translation
* Martin Šín - czech translation
* Mathias Bundgaard Svensson (freaken) - danish translation
* Matias Parmala - finnish translation
* methinks - polish translation
* Michał Jedynak (Artanis) - polish translation
* Michel Loos - brazilian portuguese translation
* Mikel Olasagasti (Hey_neken) - basque translation
* Mintaka - czech translation
* Naoki Iimura - japanese translation
* Nico Oliver - afrikaans translation
* Nicolas Boudin (Blurgk) - french translation
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - german translation
* Nobuhito Okada - japanese translation
* [mailto:tapik_AT_buchtovi.cz Oto Buchta] ([[User:Tapik|tapik]]) - czech translation
* Pau Rul·lan Ferragut - catalan translation
* Paweł Stradomski - polish translation
* Paweł Tomak - polish translation
* paxed - finnish translation
* Petr Kopač (Ferda) - czech translation
* Petr Kovár (Juans) - czech translation
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - french translation
* Pieter Vermeylen (Onne) - dutch translation
* Pınar Yanardağ (moonquelle) - turkish translation
* Renato Cunha - brazilian portuguese translation
* Roel Thijs (Roel) - dutch translation
* RokStar - italian translation
* Roman Tuchin (Sankt) - russian translation
* Rudolf Orság - czech translation
* Ruben Philipp Wickenhäuser (The Very Uhu) - german translation
* Sérgio de Miranda Costa - brazilian portuguese translation
* Selim Farsakoğlu - turkish translation
* Sofronius - czech translation
* Spiros, Giorgis - greek translation
* Srecko Toroman (FreeCraft) - serbian translation
* Stefan Bergström (tephlon) - swedish translation
* Stephan Grochtmann (Schattenstephan) - german translation
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - swedish translation
* Susanne Mesoy (Rarlgland) - norwegian translation
* Széll Tamás (TomJoad) - hungarian translation
* Tiago Souza (Salvador) - brazilian portuguese translation
* Tobe Deprez - dutch translation
* Vít Komárek - czech translation
* Vít Krčál - czech translation
* Viliam Bur - slovak translation
* wint3r - swedish translation
* [mailto:ydirson_AT_altern.org Yann Dirson] - french translation
* Yuji Matsumoto - japanese translation
* Zas - french translation

== Other Contributions ==
* Ben Anderman (crimson_penguin) - unit list
* Dacyn - scenario designer
* Cyril Bouthors (CyrilB) - debian packager, patron
* Darryl Dixon - packager
* edge - packager
* Francesco Gigli (Jaramir) - wiki, wesnoth.slack.it
* Frédéric Wagner
* Jay Hopping - packager
* Jeff Breidenbach (Jab) - Bilinear interpolation
* Marcin Konicki (ahwayakchih) - BeOS packager
* Marcus Phillips (Sithrandel) - Mac OS X packager
* Mark Michelsen (skovbaer) - slackware packager
* Mike Quinones (Doc Paterson) - multiplayer maps
* Peter Groen (pg) - multiplayer maps
* Ruben Philipp Wickenhäuser (The Very Uhu) - multiplayer maps
* Tom Chance (telex4) - multiplayer maps, scenario balancing
* Sam Phillips (dark172) - creation of campains and multiplayer maps

{{Home}}

DeveloperResources

2005-12-29T13:54:15Z

Ott:

* code documentation, created with Doxygen - http://devdocs.wesnoth.org/
* units - http://units.wesnoth.org/
* unit list - http://wesnoth.slack.it/unitlist.cgi
* movement types & resistance - http://wesnoth.slack.it/movetypes.cgi
* gettext status - http://gettext.wesnoth.org/
* changelog - http://changelog.wesnoth.org/
* forum - http://forum.wesnoth.org/
* [[FrequentlyProposedIdeas]] - summary of past often-repeated forum discussions
* [[BuildingScenarios]] and related useful forum discussions: [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development], [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* Standard Template Library - http://www.sgi.com/tech/stl/
* [[ExternalUtilities]]
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [[WesnothCVS]] - CVS instructions
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)

* Gna! links
** bugs and feature requests - http://bugs.wesnoth.org/
** patches - http://patches.wesnoth.org/
** websvn - http://websvn.wesnoth.org/

* Mailing lists:
** wesnoth-dev - http://lists.nongnu.org/mailman/listinfo/wesnoth-dev
** wesnoth-cvs-commits - http://lists.nongnu.org/mailman/listinfo/wesnoth-cvs-commits/
** wesnoth-bugs - http://lists.nongnu.org/mailman/listinfo/wesnoth-bugs/
** wesnoth-patches - http://lists.nongnu.org/mailman/listinfo/wesnoth-patches/
** wesnoth-wiki-changes - http://lists.nongnu.org/mailman/listinfo/wesnoth-wiki-changes/

* IRC: [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] (alias to irc.freenode.net)
** IRC logs - http://irclog.wesnoth.org/

* wesnothd logs (devsrv) - https://devsrv.wesnoth.org/
* wesnothd log tail (devsrv) - https://devsrv.wesnoth.org/cgi-bin/wesnoth-ccze.cgi

* [[Developers]]

User:Ott

2005-12-29T13:35:32Z

Ott:

My main work on Battle for Wesnoth has been bug fixing, documentation, translation and tweaking numerical calculations. I spent a lot of time in the year leading up to the release of 1.0 doing janitorial work, including maintaining the bug database and changelog, tracking down and fixing out of sync and other code errors, subediting game text, and improving game help.

== Articles ==
Some of my writing about the game may be worth reading:
* [http://www.wesnoth.org/forum/viewtopic.php?p=91620#91620 Distribution of damage] details the problems with the old damage model, culminating in [http://www.wesnoth.org/forum/viewtopic.php?t=4240 The RATE damage model] (with resistances at the end) used in the game since 0.8.10.
* [http://www.wesnoth.org/forum/viewtopic.php?t=5867 Calculating %-to-kill] and a [http://www.wesnoth.org/forum/viewtopic.php?t=8273 %-to-kill] consider how to calculate the probability that units in a skirmish kill each other (or survive) -- a nontrivial problem!
* [http://www.wesnoth.org/forum/viewtopic.php?p=78398#78398 Overview of postings about in-game random number generation] gives an overview of this frequently discussed issue. See also another [https://gna.org/bugs/?func=detailitem&item_id=4664#comment1 short note] related to this.
* [http://www.wesnoth.org/forum/viewtopic.php?p=53968#53968 Analysing anomalies in game statistics] culminated in discovering some bugs with the statistics in the game, and a script to analyse statistics for anomalies.
* Rant about [http://www.wesnoth.org/forum/viewtopic.php?p=113959#113959 slow] being too complex, and an [http://www.wesnoth.org/forum/viewtopic.php?p=115789#115789 alternative proposal for slow] is still being discussed.
* [[Status of User Scenarios]]
* [http://www.wesnoth.org/forum/viewtopic.php?p=117192#117192 Programming challenge: healing algorithm] and [http://www.wesnoth.org/forum/viewtopic.php?p=117761#117761 part 2] discuss the flaws in the current healing algorithm and identify the kernel of the problem that needs to be solved to improve it.

== See Also == [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=970 ott's forum profile]
[[Developers]]

User:Ott

2005-12-29T11:59:43Z

Ott: /* Future Plans */

WesnothManual

2005-12-28T15:03:36Z

Ott: /* See Also */

''This document is kept in synch with the MANUAL file distributed with the game -- please do not edit.''

If you are new to ''Battle for Wesnoth'' you might want to read the [[GettingStarted]] guide first.

== Controls ==

F1 The Battle for Wesnoth Help
Arrow keys Scroll
Left click Select unit, move unit
Right click Main menu, cancel action
Middle click Center on pointer location
Escape Exit game, exit menu, cancel message
ctrl-r Recruit unit
ctrl-shift-r Repeat last recruit
alt-r Recall unit
u Undo last move (only deterministic moves can be undone)
r Redo move
m Message another player (in multiplayer)
M Message your allies (in multiplayer)
alt-m Message everyone in the game (in multiplayer)
n Cycle through units that have movement left
N Cycle through units that have movement left, in reverse order
space End unit turn and cycle to next unit that has movement left
alt-e End this player's turn (Wesnoth 0.9.4 and earlier)
alt-space End this player's turn (Wesnoth 0.9.5 and later)
ctrl-space Hold unit position; skip this unit when cycling through units
ctrl-v Show enemy moves (where the enemy can move next turn)
ctrl-b Show potential enemy moves, if your units were not on the map
ctrl-f Toggle full screen/windowed mode
ctrl-a Toggle accelerated game mode
ctrl-s Save game
ctrl-l Load game

/ Search
t Continue interrupted unit move
z Zoom in
x Zoom out
c Reset zoom to default
ctrl-n Rename unit
1-7 Show how far currently selected unit can move in that many turns
l Move to leader unit
d Describe current unit
ctrl-d View defensive ratings of current unit against attacks
ctrl-g Toggle grid
alt-k Toggle shroud
ctrl-k Update shroud
alt-l Attach a text label to a terrain hex
alt-s Show status table
ctrl-t Show terrain table
ctrl-m Toggle muting of game sounds
: Command mode, see http://www.wesnoth.org/wiki/CommandMode

== Orbs ==

On the top of the energy bar shown next to each unit of yours is an orb.
This orb is:
* green if you control the unit and it hasn't moved this turn,
* yellow if you control the unit and it has moved this turn, but could still move further or attack,
* red if you control the unit, but it has used all its movement this turn, or
* blue if the unit is an ally you do not control.

Enemy units have no orb on the top of their energy bar.

== Description ==

The game takes place over a series of battles, or scenarios.
Each scenario pits your troops against the troops of one or
more adversaries. Each side begins with one leader in their keep.

== Gold ==

Each side is given some amount of gold to begin with,
and receives 2 gold pieces per turn, plus 1 more gold piece for
every village that side controls.

Each unit also has an upkeep cost.
The upkeep cost is generally equal to the level of the unit,
unless the unit has the 'Loyal' trait (see below).
Units that are not recalled or recruited - i.e. that lead the side
or join the side voluntarily - usually have the Loyal trait.
Upkeep is only paid if the total upkeep of a
side's units is greater than the number of villages that side controls.
Upkeep paid is the difference between the number
of villages and the upkeep cost.

So, the formula for determining the income per turn is

2 + villages - maximum(0,upkeep - villages)

where upkeep is equal to the sum of the levels of all your non-loyal units.

If the upkeep cost is greater than the number of villages+2 then the side
starts losing gold, if it is equal, no income is gained or lost.

== Recruiting and Recalling ==

Units may be recruited with gold, as long as the leader is on a keep,
and there is at least one vacant castle hex in the castle the leader is
in. Right-click in the empty hex and select Recruit to recruit new
units from the list that is presented. The cost to Recruit depends on
the unit, but is usually between 10 and 20 gold.

After you complete a scenario, all surviving units will be available to
you in the next scenario. Right-click and select Recall to recall units
from previous scenarios. Recalling costs 20 pieces of gold. A Recalled
unit retains its previous Level, Experience Points, and
(sometimes) any magic items acquired, but will arrive with full hitpoints.

You are not able to move or attack with a unit on the turn you recruit
or recall that unit.

== Unit Specialties ==

Unit specialties are described under Unit Description in-game.

== Traits ==

Units have traits which reflect aspects of their character.
Traits are assigned randomly to units when they are created.
Most units receive two traits. The possible traits are as follows:

Strong does 1 extra damage per strike in melee, and has 2 extra hitpoints
Quick has one extra movement point, but 10% fewer hitpoints
Resilient has 7 more hitpoints
Intelligent requires 20% less experience to advance a level (not Trolls)

There are also some traits that are not assigned randomly:

Loyal has zero upkeep cost
Dextrous does 1 extra damage per strike in ranged combat (Elves only)
Undead immune to poison (Undead only)

== Moving ==

When a unit is clicked on, all the places it can move to on the current
turn become lit up, while everywhere it can't move is marked in grey.
You can then click on the hex you want it to move to.
Moving onto a village that is neutral or owned by an enemy will take
ownership of it.
If you select a destination which is beyond reach in the current turn,
the unit will enter 'goto-mode' and continue moving towards
that destination in subsequent turns.
You can easily undo goto movements in the beginning of your turn;
goto can be broken by selecting unit and choosing a new destination.

You may not move through hexes adjacent to enemy units
(their Zone of Control) without stopping.
However, level 0 units have no Zone of Control.

== Fighting ==

If you move next to an enemy unit, you may attack it.
Click on your unit that is next to an enemy unit, and click on
the enemy you want to attack.
Every unit has one or more weapons it can attack with.
Some weapons, such as swords, are melee weapons, and some weapons,
such as bows, are ranged weapons.

If you attack with a melee weapon, the enemy you attack
will be able to strike back at you with its melee weapon.
If you attack with a ranged weapon, the
enemy will be able to attack back with its ranged weapon, if it has one.

Different types of attacks do different amounts of damage,
and a certain number of strikes may be made with each weapon.
For instance, an Elvish Fighter does 5 points of damage with
its sword every time it hits, and can strike 4 blows with the sword
in one exchange. This is generally written as 5-4,
meaning 5 damage per hit, and 4 strikes.

Every unit has a chance of being hit based on the terrain it is in.
For instance, units in castles and villages have a lower chance of
being hit, and Elves in forest have a low chance of being hit.
To see a unit's defense rating (i.e. chance not to be hit) in terrain,
click on the unit, and then mouse over the terrain you're
interested in, and the defense rating will be displayed as a
percentage value in the status pane, as well as shown over the terrain hex.

== Alignment ==

Every unit has an alignment: lawful, neutral, or chaotic. Alignment
affects how units perform at different times of day. Neutral units are
unaffected by the time of day. Lawful units do more damage during the
day and less at night. Chaotic units do more damage at night and less
during the day.

The two "day" and "night" phases are differentiated as Morning,
Afternoon and First Watch, Second Watch, by the positions of the sun and
moon in the time of day graphic.

The following table shows the effects of different times of the
day on the damage dealt by lawful and chaotic units:

| turn | day-phase | lawful | chaotic |
| ---------------------------------------------------------- |
| 1 | dawn | -- | -- |
| 2 | day (Morning) | +25% | -25% |
| 3 | day (Afternoon) | +25% | -25% |
| 4 | dusk | -- | -- |
| 5 | night (First Watch) | -25% | +25% |
| 6 | night (Second Watch) | -25% | +25% |

For example:
consider a fight between a Lawful and a Chaotic unit when both
have a base damage of 12. At dawn and dusk, both will do 12 points
of damage if they hit. During Morning or Afternoon, the
Lawful unit will do (12 * 1.25) or 15 points, while the Chaotic unit
will do (12 * 0.75) or 9 points. During First or Second Watch, the
Lawful unit would do 9 points compared to the Chaotic unit's 15.

If an equivalent Neutral unit were fighting, it would always do 12 points
of damage regardless of the hour.

== Healing ==

Injured units in villages will recover 8 hitpoints every turn.
Injured units that are adjacent to units with the 'heal' or 'cure'
abilities will also heal. A unit that does not move or fight during
a turn is 'resting' and will recover 2 hitpoints.
Hitpoints recovered through 'resting' are added on top of hitpoints
recovered through healing or regenerating.

A unit with the 'heals' ability may heal up to 8 hitpoints total per turn.
A unit with the 'cures' ability may heal up to 18 hitpoints total per turn.

Units next to unit(s) with the 'heals' ability will recover a maximum of
4 hitpoints per turn; units next to unit(s) with the 'cures' ability will
recover a maximum of 8 hitpoints per turn.
The more units around a unit that can heal, the less each one will be healed.

An example of 'heals' with multiple adjacent units:

Two units next to a 'healer' will receive 4 hitpoints each.

3 units next to a 'healer' will NOT receive 4 hitpoints each:
two will receive 3 hitpoints and one will receive 2 hitpoints.

A unit may be healed a maximum of 8 hitpoints per turn,
with a possible 2 hitpoints extra if resting.
Trolls, which have the regenerate ability, will
only recover 8 hitpoints when residing in a village, not 16.
Nor will a unit inside a village get extra healing from
adjacent healers.

'Heals' prevents poison from causing damage while 'cures' removes poison.
When poison is cured or prevented the unit does not gain or lose hitpoints on
that turn due to healing/poisoning.

For more information see the in-game help.

== Experience ==

Units are awarded experience for fighting.
After obtaining enough experience, they will advance a level
and become more powerful.
The amount of experience gained depends on the level of the enemy
unit and the outcome of the battle: if a unit kills its opponent,
it receives 8 experience points per level of the enemy
(4 if the enemy is level 0), while units that survive a battle
without killing their opponents are awarded 1 experience point
per level of the enemy. In other words:

| enemy level | kill bonus | fighting bonus |
| ----------------------------------------- |
| 0 | 4 | 0 |
| 1 | 8 | 1 |
| 2 | 16 | 2 |
| 3 | 24 | 3 |
| 4 | 32 | 4 |
| 5 | 40 | 5 |
| 6 | 48 | 6 |

== Multiplayer ==

You can host multiplayer games with your client or
connect to the wesnoth game server and setup your game there.
If you host a game with your client, other players need to
be able to connect to your port 15000 using TCP. If you are
behind a firewall, you will probably need to change your
firewall settings to allow incoming connections to port 15000,
and tell your firewall to forward such traffic to the machine
hosting the game.
You should not need to make firewall changes to join games
hosted on a public server or by someone else.

Public Official servers:
server.wesnoth.org most recent release of the game
devsrv.wesnoth.org up-to-date CVS version of the game

Additional servers are listed at http://wesnoth.slack.it/?[[MultiplayerServers]]

Setting up a multiplayer game

* Step 1: select multiplayer from main screen and choose to either:
** a) join official server and create game,
** b) join any other server or game hosted by another player,
** c) select to host game on your client,
** d) create a multiplayer game on your own computer as a hotseat game, or
** e) play against the computer.
* Step 2: select map and configure game settings
(fog of war, shroud, gold per village).
* Step 3: configure players (teams/alliances, starting gold, faction)
and then wait for all players set to 'network player' to join the game.
You will see "network player" replaced with their nicknames as they join.
* Step 4: click [I'm Ready].

== Campaign Server ==

You can fetch additional campaigns by selecting Campaign from the title
screen, and in the campaign menu, selecting Get More Campaigns. This
will attempt to make a TCP connection to port 15002 of the campaign
server ('''campaigns.wesnoth.org''') so you need to ensure your firewall
allows this. The campaigns are contributed by users and not all will
work properly on the current release of the game -- check the forums at
if you are having problems.

== Other Resources ==

In-game Help is available in scenarios, press the Help hotkey or select
Help from the menu. The overall homepage of the project is at
http://www.wesnoth.org/ and this links to many other pages related to
the game. Of these, our wiki at http://wiki.wesnoth.org/ contains
contributed walkthroughs and tips for playing the game, the unit
advancement tree, information about making your own scenarios and
campaigns, how to contribute as a developer or a translator, and much
more. You can also join us to chat on IRC at irc.wesnoth.org in channel #wesnoth or join our forum community at http://forum.wesnoth.org/ where
you can discuss the game with over 2000 forum members. The forums also
contain a searchable archive of tens of thousands of posts, spanning
over two years -- an invaluable source of information.

== See Also ==
* http://forum.wesnoth.org/
* [irc://irc.wesnoth.org/wesnoth #wesnoth IRC channel]
* http://www.wesnoth.org/
* [[WesnothMan|wesnoth(6) man page]]

{{Play}}

StartingPoints

2005-12-10T10:30:09Z

Ott: /* Other */

__NOTOC__
Battle for Wesnoth is a turn-based fantasy strategy game.

Defeat all enemy leaders using a well-chosen cadre of troops,
taking care to manage your resources of gold and villages.
All units have their own strengths and weaknesses; to win,
deploy your forces to their best advantage while
denying your foes the chance to do the same. As units gain
experience, they acquire new abilities and become more
powerful. Play in your own language and test your skill
against a smart computer opponent, or join Wesnoth's large
community of on-line players.
Create your own custom units, scenarios or campaigns,
and share them with others.

Battle for Wesnoth is released under the
[http://www.gnu.org/licenses/licenses.html#GPL GPL].
Prebuilt packages are available for most operating systems,
including Windows, Mac OS X, and GNU/Linux, or you can build
your own from source code.

== Getting the Game ==
==== Downloading ====
* [[Download]] - get the most recent source-files and many binaries
** [[WesnothBinaries]] - precompiled for GNU/Linux, BeOS, PDAs, ...
** [[WesnothBinariesLinux]] - precompiled for many GNU/Linux distributions

==== Compiling ====
* [[CompilingWesnoth]] - on Unix, Mac, Windows, GNU/Linux, PDAs, ...
* [[DebuggingWesnoth]] - on GNU/Linux and Unix-like systems
* [[WesnothOnLinuxPDAs]] - on the Qtopia/OPIE and thepdaXrom/Zaurus C series

== Playing the Game ([[Play]]) ==

==== For New Players ====
* [[GettingStarted]] - read me first!
* [[WesnothManual]] - the rules
* [[MainlineScenarios]] - walkthroughs for the game-supplied campaigns

==== For Not-So-New Players ====
* [[AdvancedTactics]] - beating the AI and other people
* [[MultiplayerServers]] - where to play against other people online

==== Reference ====
* [[HotKeysSystem]] - keyboard shortcuts
* [[CommandMode]] - commands you can use in-game
* [[ServerAdministration]] - commands that authenticated users can use to administer the server
* [http://wesnoth.slack.it/units.cgi Units] - Units advancement trees and stats
** [http://wesnoth.slack.it/units.cgi?page=frames Wesnoth Unit List] ([http://wesnoth.slack.it/units.cgi?page=list without frames])
** [http://wesnoth.slack.it/units.cgi?factions Factions]
** [http://wesnoth.slack.it/units.cgi?movetypes Movement, defense and resistance tables]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
* [[GraphicLibrary]] - unit and terrain images posted on the forums
**[[UnsortedContrib]] - Unsorted Contributions
**[[GameArt]] - Art for the main game
* [[WesnothAcronyms|Wesnoth Acronyms (by category)]] - common wesnothian acronyms explained
* [[WesnothAcronyms(alphabetic)|WesnothAcronyms (alphabetic)]] - common wesnothian acronyms explained

== Tweaking the Game ([[Create]]) ==

* [[UserScenarios]] - user-written scenarios, campaigns and game modifications
* [[ReferenceWML]] and [[AlphabeticalWML]] - all about Wesnoth Markup Language
* [[ReferencePythonAPI]] - upcoming Python interface for AI
* [[BuildingCampaigns]] - how to make your own campaigns
* [[BuildingScenarios]] - how to make your own scenarios
*[[BuildingUnits]] - how to make your own units
* [[WesnothMapEditor]] - summary of controls
* [[CastleTutorial]] - how to create tileable castles and other castle-like tilesets
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[UnitAnalysis]] - tool to analyze units

== Improving the Game ==
* [[ReportingBugs]] - use Gna
==== Developer information ====
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [[WesnothSVN]] - accessing the source code
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[UnitDescriptionRewriting]] - coordinating the revision
* [http://wesnoth.slack.it/missing.cgi Missing unit animations and sounds] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[WesnothPreferences]]

==== Game translations ====
* [[GettextForTranslators]] - how to translate Wesnoth under [[GetText]]
* [[WesnothTranslations]] - 11 complete, 2 almost complete, 7 more than halfway, 10 partial
* [[WesCamp]] - a project for translating user-made campaigns

==== Ideas ====
* [[FrequentlyProposedIdeas]] - before you propose an idea, check here!
* [[NewUnits]] - units that exist only in theory
* [[NewTerrains]] - tile status
* To submit a feature request, use http://bugs.wesnoth.org

== About the Game ==
* [[WesnothPhilosophy]] - Dave on Wesnoth
* [[WesnothHistory]] - the Ages of Wesnoth
* [[WesnothGeography]] - description of Wesnoth and surrounding lands
* [[WesnothReviews]] - third party reviews of Wesnoth
* [irc://irc.wesnoth.org/wesnoth #wesnoth] - our IRC channel
* [[Donate]] or [http://cafepress.com/wesnoth buy Wesnoth merchandise].

== Other ==
* [[UsefulLinks]]
* [[WesnothLSM]] - presentation at LSM
* [http://wesnoth.slack.it/?WesnothPlayerMap Map of Wesnoth player locations] - add yourself to the map!
* [http://en.wikipedia.org/wiki/Battle_for_Wesnoth Wikipedia entry for Wesnoth]
* [[WikiMigration]] - we were looking for a replacement for our old wiki (and ended up using Mediawiki)

== About this Wiki ==
* [[Help:Editing|Editing]] - learn how to edit pages
* [[Sandbox]] - experiment with the wiki

WesnothReviews

2005-12-10T10:29:25Z

Ott:

* [http://www.tidbits.com/ TidBITS] 9 December 2005: http://www.tidbits.com/tb-issues/TidBITS-808.html
* [http://www.macworld.co.uk/news/index.cfm?NewsID=12886&Page=1&pagePos=1 MacWorld UK review] October 2005, BfW 1.0
* [http://www.insidemacgames.com/reviews/view.php?ID=642 Inside Mac Games review] 26 October 2005, BfW 1.0
* [http://www.macobserver.com/columns/slackersguide/2005/20051014.shtml The Slacker's Guide - Desert Combat and Wesnoth] October 2005, BfW 1.0
* PC4War (Frech magazine), August 2005 issue: [http://www.wesnoth.org/images/wesnoth_pc4war.jpg scanned review]
* [http://www.framasoft.net/article2293.html Framasoft review] (French) July 2005, BfW 0.9
* [http://www.themacmind.com/modules.php?op=modload&name=News&file=article&sid=631&mode=nested&order=0&thold=0 The Mac Mind review] December 2004
* [http://www.jeux-strategie.com/The_Battle_For_Wesnoth.1734.0.html Jeux-Stratégie.com] (french) October 2004
* [http://www.tgr.com/weblog/archives/000034.html Tea Leaves review] March 2004
* [http://pcburn.com/game_review-Battle_for_Wesnoth.php PCBurn review] BfW 0.6.99.2

StartingPoints

2005-12-10T06:55:19Z

Ott: /* Other */

__NOTOC__
Battle for Wesnoth is a turn-based fantasy strategy game.

Defeat all enemy leaders using a well-chosen cadre of troops,
taking care to manage your resources of gold and villages.
All units have their own strengths and weaknesses; to win,
deploy your forces to their best advantage while
denying your foes the chance to do the same. As units gain
experience, they acquire new abilities and become more
powerful. Play in your own language and test your skill
against a smart computer opponent, or join Wesnoth's large
community of on-line players.
Create your own custom units, scenarios or campaigns,
and share them with others.

Battle for Wesnoth is released under the
[http://www.gnu.org/licenses/licenses.html#GPL GPL].
Prebuilt packages are available for most operating systems,
including Windows, Mac OS X, and GNU/Linux, or you can build
your own from source code.

== Getting the Game ==
==== Downloading ====
* [[Download]] - get the most recent source-files and many binaries
** [[WesnothBinaries]] - precompiled for GNU/Linux, BeOS, PDAs, ...
** [[WesnothBinariesLinux]] - precompiled for many GNU/Linux distributions

==== Compiling ====
* [[CompilingWesnoth]] - on Unix, Mac, Windows, GNU/Linux, PDAs, ...
* [[DebuggingWesnoth]] - on GNU/Linux and Unix-like systems
* [[WesnothOnLinuxPDAs]] - on the Qtopia/OPIE and thepdaXrom/Zaurus C series

== Playing the Game ([[Play]]) ==

==== For New Players ====
* [[GettingStarted]] - read me first!
* [[WesnothManual]] - the rules
* [[MainlineScenarios]] - walkthroughs for the game-supplied campaigns

==== For Not-So-New Players ====
* [[AdvancedTactics]] - beating the AI and other people
* [[MultiplayerServers]] - where to play against other people online

==== Reference ====
* [[HotKeysSystem]] - keyboard shortcuts
* [[CommandMode]] - commands you can use in-game
* [[ServerAdministration]] - commands that authenticated users can use to administer the server
* [http://wesnoth.slack.it/units.cgi Units] - Units advancement trees and stats
** [http://wesnoth.slack.it/units.cgi?page=frames Wesnoth Unit List] ([http://wesnoth.slack.it/units.cgi?page=list without frames])
** [http://wesnoth.slack.it/units.cgi?factions Factions]
** [http://wesnoth.slack.it/units.cgi?movetypes Movement, defense and resistance tables]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
* [[GraphicLibrary]] - unit and terrain images posted on the forums
**[[UnsortedContrib]] - Unsorted Contributions
**[[GameArt]] - Art for the main game
* [[WesnothAcronyms|Wesnoth Acronyms (by category)]] - common wesnothian acronyms explained
* [[WesnothAcronyms(alphabetic)|WesnothAcronyms (alphabetic)]] - common wesnothian acronyms explained

== Tweaking the Game ([[Create]]) ==

* [[UserScenarios]] - user-written scenarios, campaigns and game modifications
* [[ReferenceWML]] and [[AlphabeticalWML]] - all about Wesnoth Markup Language
* [[ReferencePythonAPI]] - upcoming Python interface for AI
* [[BuildingCampaigns]] - how to make your own campaigns
* [[BuildingScenarios]] - how to make your own scenarios
*[[BuildingUnits]] - how to make your own units
* [[WesnothMapEditor]] - summary of controls
* [[CastleTutorial]] - how to create tileable castles and other castle-like tilesets
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[UnitAnalysis]] - tool to analyze units

== Improving the Game ==
* [[ReportingBugs]] - use Gna
==== Developer information ====
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [[WesnothSVN]] - accessing the source code
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[UnitDescriptionRewriting]] - coordinating the revision
* [http://wesnoth.slack.it/missing.cgi Missing unit animations and sounds] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[WesnothPreferences]]

==== Game translations ====
* [[GettextForTranslators]] - how to translate Wesnoth under [[GetText]]
* [[WesnothTranslations]] - 11 complete, 2 almost complete, 7 more than halfway, 10 partial
* [[WesCamp]] - a project for translating user-made campaigns

==== Ideas ====
* [[FrequentlyProposedIdeas]] - before you propose an idea, check here!
* [[NewUnits]] - units that exist only in theory
* [[NewTerrains]] - tile status
* To submit a feature request, use http://bugs.wesnoth.org

== About the Game ==
* [[WesnothPhilosophy]] - Dave on Wesnoth
* [[WesnothHistory]] - the Ages of Wesnoth
* [[WesnothGeography]] - description of Wesnoth and surrounding lands
* [[WesnothReviews]] - third party reviews of Wesnoth
* [irc://irc.wesnoth.org/wesnoth #wesnoth] - our IRC channel
* [[Donate]] or [http://cafepress.com/wesnoth buy Wesnoth merchandise].

== Other ==
* [[UsefulLinks]]
* [[WesnothLSM]] - presentation at LSM
* [http://wesnoth.slack.it/?WesnothPlayerMap Map of Wesnoth player locations] - add yourself to the map!
* [http://en.wikipedia.org/wiki/Battle_for_Wesnoth Wikipedia entry for Wesnoth]
* [[WikiMigration]] - we were looking for a replacement for our old wiki (and ended up using Mediawiki)
* [[Media Coverage]] about the game

== About this Wiki ==
* [[Help:Editing|Editing]] - learn how to edit pages
* [[Sandbox]] - experiment with the wiki

User:Ott

2005-12-03T11:21:20Z

Ott: /* See Also */

My main work on Battle for Wesnoth has been bug fixing, documentation, translation and tweaking numerical calculations. I spent a lot of time in the year leading up to the release of 1.0 doing janitorial work, including maintaining the bug database and changelog, tracking down and fixing out of sync and other code errors, subediting game text, and improving game help.

== Articles ==
Some of my writing about the game may be worth reading:
* [http://www.wesnoth.org/forum/viewtopic.php?p=91620#91620 Distribution of damage] details the problems with the old damage model, culminating in [http://www.wesnoth.org/forum/viewtopic.php?t=4240 The RATE damage model] (with resistances at the end) used in the game since 0.8.10.
* [http://www.wesnoth.org/forum/viewtopic.php?t=5867 Calculating %-to-kill] and a [http://www.wesnoth.org/forum/viewtopic.php?t=8273 %-to-kill] consider how to calculate the probability that units in a skirmish kill each other (or survive) -- a nontrivial problem!
* [http://www.wesnoth.org/forum/viewtopic.php?p=78398#78398 Overview of postings about in-game random number generation] gives an overview of this frequently discussed issue. See also another [https://gna.org/bugs/?func=detailitem&item_id=4664#comment1 short note] related to this.
* [http://www.wesnoth.org/forum/viewtopic.php?p=53968#53968 Analysing anomalies in game statistics] culminated in discovering some bugs with the statistics in the game, and a script to analyse statistics for anomalies.
* Rant about [http://www.wesnoth.org/forum/viewtopic.php?p=113959#113959 slow] being too complex, and an [http://www.wesnoth.org/forum/viewtopic.php?p=115789#115789 alternative proposal for slow] is still being discussed.
* [[Status of User Scenarios]]
* [http://www.wesnoth.org/forum/viewtopic.php?p=117192#117192 Programming challenge: healing algorithm] and [http://www.wesnoth.org/forum/viewtopic.php?p=117761#117761 part 2] discuss the flaws in the current healing algorithm and identify the kernel of the problem that needs to be solved to improve it.

== Future Plans ==
Some of the things I am hoping to work on:
* an efficient way to calculate or estimate the probability of killing another unit in a skirmish, so it can be used by the AI,
* fixing some long-standing but irritating problems (especially related to the user interface),
* a campaign focused on strategy and small maps rather than roleplaying,
* removing the dependency on FreeSans so we can move to DejaVu completely (by fixing SDL_ttf's broken code to calculate line spacing),
* stamping out any further causes of out of sync errors, and
* tidying up the build system.

== See Also == [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=970 ott's forum profile]
[[Developers]]

User:Ott

2005-12-03T11:15:27Z

Ott: /* Articles */

My main work on Battle for Wesnoth has been bug fixing, documentation, translation and tweaking numerical calculations. I spent a lot of time in the year leading up to the release of 1.0 doing janitorial work, including maintaining the bug database and changelog, tracking down and fixing out of sync and other code errors, subediting game text, and improving game help.

== Articles ==
Some of my writing about the game may be worth reading:
* [http://www.wesnoth.org/forum/viewtopic.php?p=91620#91620 Distribution of damage] details the problems with the old damage model, culminating in [http://www.wesnoth.org/forum/viewtopic.php?t=4240 The RATE damage model] (with resistances at the end) used in the game since 0.8.10.
* [http://www.wesnoth.org/forum/viewtopic.php?t=5867 Calculating %-to-kill] and a [http://www.wesnoth.org/forum/viewtopic.php?t=8273 %-to-kill] consider how to calculate the probability that units in a skirmish kill each other (or survive) -- a nontrivial problem!
* [http://www.wesnoth.org/forum/viewtopic.php?p=78398#78398 Overview of postings about in-game random number generation] gives an overview of this frequently discussed issue. See also another [https://gna.org/bugs/?func=detailitem&item_id=4664#comment1 short note] related to this.
* [http://www.wesnoth.org/forum/viewtopic.php?p=53968#53968 Analysing anomalies in game statistics] culminated in discovering some bugs with the statistics in the game, and a script to analyse statistics for anomalies.
* Rant about [http://www.wesnoth.org/forum/viewtopic.php?p=113959#113959 slow] being too complex, and an [http://www.wesnoth.org/forum/viewtopic.php?p=115789#115789 alternative proposal for slow] is still being discussed.
* [[Status of User Scenarios]]
* [http://www.wesnoth.org/forum/viewtopic.php?p=117192#117192 Programming challenge: healing algorithm] and [http://www.wesnoth.org/forum/viewtopic.php?p=117761#117761 part 2] discuss the flaws in the current healing algorithm and identify the kernel of the problem that needs to be solved to improve it.

== Future Plans ==
Some of the things I am hoping to work on:
* an efficient way to calculate or estimate the probability of killing another unit in a skirmish, so it can be used by the AI,
* fixing some long-standing but irritating problems (especially related to the user interface),
* a campaign focused on strategy and small maps rather than roleplaying,
* removing the dependency on FreeSans so we can move to DejaVu completely (by fixing SDL_ttf's broken code to calculate line spacing),
* stamping out any further causes of out of sync errors, and
* tidying up the build system.

== See Also == [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=970 ott's forum profile]

User:Ott

2005-12-03T10:52:38Z

Ott:

My main work on Battle for Wesnoth has been bug fixing, documentation, translation and tweaking numerical calculations. I spent a lot of time in the year leading up to the release of 1.0 doing janitorial work, including maintaining the bug database and changelog, tracking down and fixing out of sync and other code errors, subediting game text, and improving game help.

== Articles ==
Some of my writing about the game may be worth reading:
* [http://www.wesnoth.org/forum/viewtopic.php?p=91620#91620 Distribution of damage]
* [http://www.wesnoth.org/forum/viewtopic.php?t=5867 Calculating %-to-kill] and a [http://www.wesnoth.org/forum/viewtopic.php?t=8273 %-to-kill], a more recent version
* [http://www.wesnoth.org/forum/viewtopic.php?p=78398#78398 Overview of postings about in-game random number generation]
* [http://www.wesnoth.org/forum/viewtopic.php?p=53968#53968 Analysing anomalies in game statistics]
* [http://www.wesnoth.org/forum/viewtopic.php?t=4240 The RATE damage model] (used in-game since 0.8.10)
* rant about [http://www.wesnoth.org/forum/viewtopic.php?p=113959#113959 slow] being too complex, and an [http://www.wesnoth.org/forum/viewtopic.php?p=115789#115789 alternative proposal for slow]
* [[Status of User Scenarios]]

== Future Plans ==
Some of the things I am hoping to work on:
* an efficient way to calculate or estimate the probability of killing another unit in a skirmish, so it can be used by the AI,
* fixing some long-standing but irritating problems (especially related to the user interface),
* a campaign focused on strategy and small maps rather than roleplaying,
* removing the dependency on FreeSans so we can move to DejaVu completely (by fixing SDL_ttf's broken code to calculate line spacing),
* stamping out any further causes of out of sync errors, and
* tidying up the build system.

== See Also == [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=970 ott's forum profile]

Download

2005-11-30T08:05:32Z

Ott: /* See also */

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient.

== Source code ==
* Wesnoth 1.0.2: [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.2.tar.gz?download wesnoth-1.0.2.tar.gz] (38.2MB) [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.2.tar.gz.md5?download md5sum]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code Xdelta]
* [[CompilingWesnoth]] - how to compile the source code

== [[BeOS]] ==
* Wesnoth 1.0.2 for BeOS: [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0.2-BeOS-x86.pkg.zip?download Wesnoth-1.0.2-BeOS-x86.pkg.zip] (42.3MB) [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0.2-BeOS-x86.pkg.zip.md5?download md5sum]

== GNU/Linux ==
* A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz]
** (do _*_NOT_*_ try to install to a subdirectory of the package's directory. Trust me on this :-( )
** Actually, you don't need to install it at all, you can run it in place.

* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at [[WesnothBinariesLinux]] for more informations about the binaries for your Distribution.

== Mac OS X ==
* Wesnoth 1.0.2 for Mac OS X:
** [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.0.2.dmg?download Sourceforge-hosted build] by Sithrandel (53.6 MB)
** [http://lwa.retiaire.org/wesnoth/Wesnoth_MacOSX_1.0.2-lwa.dmg Wesnoth_MacOSX_1.0.2-lwa.dmg] by lwa (44MB)
** [http://lwa.retiaire.org/wesnoth/Wesnoth_MacOSX_1.0.2_lite-lwa.dmg Wesnoth_MacOSX_1.0.2_lite-lwa.dmg] by lwa (game only, music and large story images removed) (25MB)

== MS Windows ==
* Wesnoth 1.0.1 for Microsoft Windows: [http://prdownloads.sourceforge.net/wesnoth/wesnoth-windows-1.0.1.exe?download wesnoth-windows-1.0.1.exe] (38.1MB)

== FreeBSD ==
* Wesnoth 1.0.1 for FreeBSD: /usr/ports/games/wesnoth (37.3MB)

== AmigaOS4 ==
* Wesnoth 1.0rc1 for AmigaOS4: http://www.os4depot.net/share/game/strategy/wesnoth.lha (37.7MB)

== License ==
This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org/ Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== See also ==
* [http://sourceforge.net/project/showfiles.php?group_id=89495 SourceForge downloads]
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [http://sourceforge.net/project/showfiles.php?group_id=89495 Previous releases]
* [[WesnothSVN]] - bleeding edge version from SVN

DirectActionsWML

2005-11-25T17:39:36Z

Ott: /* Direct actions */

== Direct actions ==

Direct actions are actions that have a direct effect on gameplay.

The following tags are actions:
* '''[endlevel]''' ends the scenario.
** ''result'' before the scenario is over, all events with ''name=result'' are triggered. The message ''result_message'' with the heading ''result_heading'' (see [[LanguageWML]]) are displayed. If ''result=victory'', the player progresses to the next level; if ''result=defeat'', the game returns to the main menu. These last two are rarely used: ''result=continue'' behaves identically to ''result=victory'' except the player's gold is not reduced to 80%, and it does not bring up a "Victory" message or the gold changing message (since it doesn't change); ''result=continue_no_save'' works similarly, except the player is not asked whether to save the game, and is taken directly to the next scenario without any messages. Unless ''result=defeat'', the following keys can also be used:
** ''bonus'' whether the player should get bonus gold (maximum possible gold that could have been earned by waiting the level out).
** ''next_scenario'' (default specified in '''[scenario]''' tag) the ID of the next scenario that should be played. All units that side 1 controls at this point become available for recall in ''next_scenario''.
* '''[unit]''' places a unit on the map. For syntax see [[SingleUnitWML]].
* '''[recall]''' recalls a unit. The unit is recalled free of charge, and is placed near the leader.
** ''standard unit filter'' the first matching unit will be recalled. If no units match this tag is ignored.
** ''x,y'' the unit is placed here instead of next to the leader.
** ''show'' if not "no", display the unit being recalled.
* '''[teleport]''' teleports a unit on map.
** '''[filter]''' (standard unit filter) all units matching the filter will be teleported.
** ''x,y'' the position to teleport to.
* '''[terrain_mask]''' changes the terrain on the map. See [[TerrainMaskWML]].
* '''[terrain]''' changes the terrain on the map.
** ''letter'' the character of the terrain to use. See [[TerrainLettersWML]] to see what letter a type of terrain uses.
** standard location filter- the area to change the terrain of.
* '''[gold]''' give one side gold.
** ''amount'' the amount of gold to give.
** ''side'' (default=1) the number of the side to give the gold to.
* '''[unstore_unit]''' creates a unit from a game variable, and activates it on the playing field. This must be a specific variable describing a unit, and may not be an array -- to unstore an entire array, iterate over it. The variable is not cleared. See also [store_unit], [while] and [clear_variable] in [[InternalActionsWML]].
** ''variable'' the name of the variable.
** ''find_vacant'' whether the unit should be placed on the nearest vacant tile to its specified location. If this is set to 'no'(default), then any unit on the same tile as the unit being unstored will be destroyed.
* '''[allow_recruit]''' allows a side to recruit units it couldn't previously recruit.
** ''type'' the types of units that the side can now recruit.
** ''side'' (default=1) the number of the side that is being allowed to recruit the units.
* '''[disallow_recruit]''' prevents a side from recruiting units it could previously recruit.
** ''type'' the types of units that the side can no longer recruit.
** ''side'' (default=1) the number of the side that may no longer recruit the units.
* '''[set_recruit]''' sets the units a side can recruit.
** ''recruit'' the types of units that the side can now recruit.
** ''side'' (default=1) the number of the side that is having its recruitment set.
* '''[modify_side]''' modifies some details of a given side in the middle of a scenario. '''The following listed properties are the only properties that [modify_side] can affect!'''
** ''side'' (default=1) the number of the side that is to be changed.
** ''income'' the income given at the begining of each turn.
** ''team_name'' the team in which the side plays the scenario.
** ''gold'' the amount of gold the side owns.
* '''[capture_village]''' changes the ownership of a village.
** ''side'' the side that takes control of the village. If not given, the village will become neutral.
** ''x, y'' the location of the village.
* '''[kill]''' Removes all units that match the filter from the game.
** standard unit filter
** ''animate'' if 'yes', displays the unit dying (fading away).
** ''fire_event'' if 'yes', triggers any appropriate 'die' events (See [[EventWML]]).
* '''[unstone]''' Unstones all units that match the filter.
** '''[filter]''' (standard unit filter) all units matching the filter will be unstoned. If no unit matches the filter, then nothing happens (probably). If absent, all units on the map are unstoned.
* '''[object]''' gives some unit an object and removes all items on the tile the unit is on.
** ''id'' when the object is picked up, a flag is set for ''id''. The object cannot be picked up if a flag for ''id'' has been set. This means that any object with an id can only be used once, even if first_time_only=no is set for the event. This restriction is per level. In a campaign objects with the same id can be assigned once per level.
** '''[effect]''' one or more effect elements may be listed. See [[EffectWML]] for a description of [effect].
** ''duration'' if 'level', effects only last until the end of the level.
** '''[filter]''' (standard unit filter) the first unit found that matches the filter will be given the object. If no unit matches the filter, then a message is displayed and the object is not removed.
** ''silent'' whether or not messages should be suppressed. Default is "no".
** ''image'' the displayed image of the object.
** ''name'' (translatable) displayed as a caption of the image.
** ''description'' (translatable) displayed as a message of the image.
** ''cannot_use_message'' (translatable) displayed instead of '''description''' if no unit passes the filter test.
** Currently the object action is only supposed to be called by moveto events. If you try to call it from other events you may have problems.
** If you do not supply a filter, the object action will be applied to a unit at the location of the moveto event. Currently this isn't recommended as it is not clear that this will continue working this way. Instead it is better to explicitly include a location filter.
** The object action does not act on units in the recall list. There is a feature request in to allow this, but it is not clear whether or not it will be accepted.
* '''[remove_shroud]''' removes some shroud from the map for a certain side (only relevant for sides that have shroud=yes).
** ''side'' (default=1) the side for which to remove shroud.
** standard location filter- the range of tiles for which shroud should be removed.
* '''[place_shroud]''' places some shroud on the map for a certain side (only relevant for sides that have shroud=yes).
** ''side'' (default=1) the side for which to place shroud.
** standard location filter- the range of tiles on which shroud should be placed.
* '''[allow_undo]''' allows the player to undo the event that this tag is inside. Has an effect only inside moveto events. If the move is undone, only the position of the unit will be restored; any altered variables or changes to the game will remain changed after the move is undone. Therefore, it is advised that you do not use '''[allow_undo]''' before or after usage of other actions from [[DirectActionsWML]]. If you modify a variable(i.e. [[InternalActionsWML]]), set it back before using '''[allow_undo]'''. However, you can check a conditional, and only allow undo if you do not use the actions.

== See Also ==

* [[InternalActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

InternalActionsWML

2005-11-25T17:28:16Z

Ott: /* [event] */

== Internal actions ==

Internal actions are actions that WML uses internally that do not directly affect gameplay, for example storing a variable.

The internal actions '''[if]''', '''[while]''', and '''[event]''' describe when/whether sets of actions should be executed.

== [if] ==

Executes different sets of actions based on whether the conditions described in the condition tags are true or not.

Condition tags:
* '''[have_unit]''' a unit passing this filter with >0 HP exists
** standard unit filter

* '''[or]''' If an [or] is present, one must evaluate to true in order for the [if] to evaluate true
** condition tags as in [if] - if these evaluate to true, [or] evaluates to true.

* '''[variable]''' tests something about the value of a WML variable (see [[VariablesWML]])
** ''name'' the name of the variable to test the value of<br>Only one of these keys should be used:
** ''equals'' $name is equal (string wise) to ''equals''
** ''not_equals'' $name is not equal to ''not_equals''
** ''greater_than'' $name is numerically greater than ''greater_than''
** ''less_than'' $name is less than ''less_than''
** ''greater_than_equal_to'' $name is not less than ''greater_than_equal_to''
** ''less_than_equal_to'' $name is not greater than ''less_than_equal_to''
** ''numerical_not_equals'' $name is greater than or less than ''numerical_not_equals''
** ''numerical_equals'' $name is not greater than or less than ''numerical_equals''

After condition tags:
* '''[then]''' contains a set of action tags which should be executed if all conditions are true, or all conditions in any single [or] are true
* '''[else]''' contains a set of action tags which should be executed if any condition is false, and all [or] tags are false

== [while] ==

executes commands if all conditions are true.
Continues to execute them until a condition is not true.

Executes a maximum of 1024 iterations per invocation.
Condition tags are the same as for [if]

After condition tags:
* '''[do]''' contains actions that should be executed repeatedly until some condition is false.

The [while] tag is useful for iterating over an array.
An ''array'' is a list of values.
The ''number''th value in the array ''array'' is stored in the WML variable '''''array''[number]'''.
Note that if ''number'' is the value of the variable ''variable'',
the expression '''$''array''[$variable]''' will return the ''number''th value in ''array''.
The macros 'FOREACH' and 'NEXT' ([[UtilWML]]) can be used to iterate over an array;
i.e. run a set of actions once per element of the array.

== [event] == this adds a new event to the scenario.
The event is in the normal format for an '''[event]''' tag (See [[EventWML]]).
This is useful if you want an event that can only be triggered when a prior event is fulfilled

These tags describe actions that affect the values of WML variables
(see [[VariablesWML]] for information on WML variables,
and [[UtilWML]] for convenient macro shortcuts for some of these):
* '''[set_variable]''' manipulates a WML variable.
** ''name'' the name of the variable to manipulate
** ''value'' set the variable to the given value (can be numeric or string). This does not interpret any dollars signs.
** ''format'' set the variable to the given value. Interprets the dollar sign to a higher degree than most actions. (see [[VariablesWML]])
** ''to_variable'' Fully processes its value as in ''format'', and then gets the variable with that name.
** ''add'' add the given amount to the variable. To subtract, add a negative number.
** ''multiply'' multiply the variable by the given amount. To divide, multiply by a decimal. To negate, multiply by -1.
** ''random'' the variable will be randomly set.<br>You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'.<br>You may provide a range of numbers (integers), e.g. 'random=3..5'.<br>You may combine these, e.g. 'random=100,1..9', in which case there would be 1/10th chance of getting 100, just like for each of 1 to 9. Dollars signs are only normally interpreted here, so it is harder to have a dynamically determined range. You would need to create the random-string with ''format''.

* '''[store_unit]''' stores details about units into game variables.<br>Common usage is to manipulate a unit by using [store_unit] to store it into a variable, followed by manipulation of the variable, and then [unstore_unit] to re-create the unit with the modified variables.<br>Note: stored units also exist on the field, and modifying the stored variable will not automatically change the stats of the units. You need to use [unstore_unit]. See also [unstore_unit], [[DirectActionsWML]], and '''FOREACH''', [[UtilWML]]
** '''[filter]''' (standard unit filter) all units matching this filter will be stored. If there are multiple units, they will be stored into an array of variables.
** ''variable'' the name of the variable into which to store the unit(s)
** ''kill'' if 'yes' the units that are stored will be removed from play. This is useful for instance to remove access to a player's recall list, with the intent to restore the recall list later.
:When a unit is stored, the following values may be manipulated with '''[set_variable]'''
:* description
:* experience
:* facing
:* gender
:* canrecruit
:* overlays
:* goto_x
:* goto_y
:* hitpoints
:* moves
:* resting
:* side
:* type
:* unrenamable
:* upkeep
:* user_description
:* x
:* y
:* [variables]
:* [status]
:* [modifications]
Variables, status, and modifications are children of the stored unit variable. Example:
[set_variable]
name=unit_store.status.poisoned
value=yes
[/set_variable]

* '''[store_starting_location]''' Stores the starting location of a side's leader in a variable. The variable is a composite type which will have members 'x' and 'y'.
** ''side'' the side whose starting location is to be stored
** ''variable'' (default='location'): the name of the variable to store the location in
* '''[store_locations]''' Stores a series of locations that pass certain criteria into an array. Each member of the array has members 'x' and 'y'.
** standard location filter- a location or location range which specifies the locations to store. You must specify this or no locations will be stored.
** ''variable'' the name of the variable (array) into which to store the locations
** ''terrain'' a series of terrain characters. (See [[TerrainLettersWML]] for possible values.) If present, locations will only be chosen if the letter of the terrain type of that location is listed.
** ''radius'' if present, any locations which are within ''radius'' hexes of the location filter will also be stored
** '''[filter]''' (standard unit filter) only locations with units on them that match the filter will be stored. Use a blank filter to only store locations with units.
* '''[store_gold]''' stores the gold for a certain side in a variable.
** ''side'' (default=1) the side for which the gold should be stored
** ''variable'' (default='gold') the name of the variable to store the gold in
* '''[clear_variable]''' This will delete the given variable or array. This is good to use to clean up the set of variables -- e.g. a well-behaved scenario will delete any variables that shouldn't be kept for the next scenario before the end of the scenario.
** ''name'' the name of the variable to clear.
* '''[role]''' tries to find a unit to assign a role to.<br>This is useful if you want to choose a non-major character to say some things during the game. Once a role is assigned, you can use '''role=''' in a unit filter to identify the unit with that role (See [[FilterWML]]).<br>However, there is no guarantee that roles will ever be assigned. You can use '''[have_unit]''' (see [if]) to see whether a role was assigned. This tag uses a Standard Unit Filter with the modification to order the search by type, mark only the first unit found with the role, and the role attribute is not used in the search. If for some reason you want to search for units that have or don't have existing roles, you can use one or more [not] filters. The will check recall lists in addition to units on the map. In normal use, you will probably want to include a ''side'' attribute to force the unit to be on a particular side.
** ''role'' the value to store as the unit's role. This role is not used in the Standard Unit Filter when doing the search for the unit to assign this role to.
** ''type'' a comma-separated list of possible types the unit can be. If any types are given, then units will be searched by type in the order listed. If no type is given, then no particular order with respect to type is guaranteed.

== See Also ==
* [[VariablesWML]]
* [[DirectActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

FilterWML

2005-11-25T17:18:42Z

Ott: /* Filtering Units */

== Filtering in WML ==

A ''filter'' is a special WML block.
Filters are used to describe a set of units, hexes, or weapons.
Filters are defined as matching something if all the keys in the filter match that thing.
For example, if a unit filter contains two keys,
a unit must match both of the keys in order to match the filter.

== Filtering Units ==

Filters are often used in action tags (see [[EventWML]]).
In this case the phrase "standard unit filter" is used in place of the set of standard keys.
Sometimes a filter is used to find the first unit that matches the filter;
for example, the '''[recall]''' tag recalls that unit.

Standard unit filters are also used in the tags '''[filter]''' and '''[filter_second]'''.
These are subtags of '''[event]''' which describe when the event should trigger.
Most event names (see [[EventWML]]) have units related to them called "primary unit" and "secondary unit".
In order for an event to be triggered, ''primary unit'' must match the filter contained in '''[filter]''',
and ''secondary unit'' must match the filter contained in '''[filter_second]'''.

When a unit filter is applied to a map, first it applies to all units on the field,
based on their coordinates.
Next it applies to units in the recall list.
This is important to remember as it means, for example,
that the tag '''[kill]''' can be used to kill units in the recall list.

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

* ''description'' unit matches the given description. This is the same as ''description'' in the [unit] tag. Note that it is independent of ''user_description'', which can be internationalized independent of this. See [[SingleUnitWML]].
* ''speaker'' alias for description
* ''type'' matches the unit's type name (can be a list of types)
* ''race'' the race of the unit type.<br>Races are listed in the unit files ('''data/units/''')
* ''ability'' unit has a given ability; see [[AbilitiesWML]]
* ''side'' the unit is on the given side (can be a list)
* ''has_weapon'' the unit has a weapon with the given name
* ''canrecruit'' 1 if the unit can recruit (i.e. is a leader)
* ''gender'' female if the unit is female rather than the default of male
* ''role'' the unit has been assigned the given role; see '''[role]''', [[InternalActionsWML]]
* '''[not]''' this subtag contains another filter.<br>If the content of this filter is matched, the parent's filter won't be, and vice-versa.
* '''[filter]''' standard location filter - the tile that the unit is standing on matches the location filter.
* You are limited to having one ''description'', however this can be worked around. If you have several specific units you want excepted from matching, use a separate [not] subfilter for each one. If you want to match any of several specific units, you can apply DeMorgan's law and do the test by having a [not] subfilter and then below that another [not] subfilter for each unit you want included. For example to kill ([kill] uses the standard unit filter) all units except Gwiti Ha'atel and Tanar you can do the following:
[kill]
[not]
description=Gwiti Ha'atel
[/not]
[not]
description=Tanar
[/not]
[/kill]
:And similarly if you wanted to kill both Gwiti Ha'atel and Tanar, but no one else you could do the following:
[kill]
[not]
[not]
description=Gwiti Ha'atel
[/not]
[not]
description=Tanar
[/not]
[/not]
[/kill]
:although this is probably easier achieved using two tags:
[kill]
description=Gwiti Ha'atel
[/kill]
[kill]
description=Tanar
[/kill]

== Filtering Locations ==

As you have seen, standard unit filter can contain a location filter.
Several actions, such as '''[terrain]''', also use location filters.
Location filters are represented on this site by the phrase "standard location filter".

The following keys are used:
* ''x'' the first coordinate
* ''y'' the second coordinate

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

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

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

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

== Filtering Weapons ==

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

These keys are used as filter input for weapon filters.

* ''range'' a range to filter
** 'short' only melee weapons pass
** 'long' only ranged weapons pass
* ''name'' filter on the attack's name.
See '''data/units/''' or http://wesnoth.slack.it/unitlist.cgi
to find the name of a particular unit's attack.
* ''type'' filter on the attack's type.
Values are 'blade', 'pierce', 'impact', 'fire', 'cold', and 'holy'.
* ''special'' filter on the attack's special power.
For values see [[AbilitiesWML]].

== See Also ==

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

SyntaxWML

2005-11-22T13:44:10Z

Ott:

Wesnoth syntax has two basic elements: ''tags'' and ''attributes''.
Further, ''attributes'' consist of ''keys'' and ''values''.
Tag names and keys cannot contain whitespace.
Any line beginning with a pound ('''#''') sign is considered by
WML as a comment, except for preprocessor declarations beginning
with #.
* '''[tag-name] ''data'' [/tag-name]''' is a tag. Tags are used to partition information. A ''top level'' tag is one that is not inside any other tag. Each top level tag describes something about the game. Different tags work differently. For information about how a certain tag works, see [[ReferenceWML]].
* '''[+tag-name] ''data'' [/tag-name]''' means that ''data'' will be considered as part of the data for the most recent [''tag-name''] tag. The ''data'' of '''[+tag-name]''' will be considered as coming after all data in '''[tag-name]''', so attributes of '''[+tag-name]''' will replace attributes of the original '''[tag-name]'''.
* '''''key=value newline''''' is an ''attribute'', or an assignment of a value to a key. When this line is processed, the value of ''key'' for the tag that the attribute is in is set or changed to ''value''. All text from '=' until the end of the line is considered to be part of ''value''. Note that ''key'' is not a WML variable (with the exception of [[VariablesWML]]); the value it is set to has a use which is determined by C++ code, not WML code. In order to change the value of a WML variable, you need to use '''[set_variable]''' (see [[InternalActionsWML]]). '''There should be no space between the key and the '=' symbol!''' If there is whitespace, the attribute assignment is ignored. Note that ''key'' should contain only alphanumerics or underscores (''a-zA-Z0-9_''); no ''+'' or ''-'' characters are allowed.
* '''''key1,key2,key3=value1,value2,value3 newline''''' is a multiple assignment. If there are extra keys, they will be set to an empty value. If there are extra values the last key will be set to the comma separated list of all remaining values. It is the same as
key1=value1
key2=value2
key3=value3

Although a value can be just text corresponding to a function of
its key (these values are displayed in quotes (') in
[[ReferenceWML]]), a value can also be encoded:
* '''"''multiple-line-value''"''' a multiple-line value must be enclosed in quotes, to prevent it being interpreted as a single-line value. Note that ''multiple-line-value'' doesn't have to have multiple lines; it can simply be a single-line value enclosed in quotes for clarity.
* '''''_ "text"''''' is a ''translatable'' value. ''text'' is English (US) text that will be displayed in-game at some point. Gettext (see [[GetText]]) is used to determine what to display if English (US) is not the current language.
* '''''value-1 + value-2''''' can be used to concatenate two different strings. If you want to have a value that actually has a plus sign ('''+''') in it, you need to enclose the string containing the '''+''' character in quotes (see '''''"multiple-line-value"''''' above).
* '''''$variable-name''''' a ''variable'' value depends on the value of the WML variable ''variable-name''. See [[VariablesWML]] for more information on WML-variable based values.

Example:
[scenario]
id=Elves Besieged
[side]
side,gold=1,100
[/side]
[+side]
recruit=Elvish Fighter,Elvish Archer
[/side]
[/scenario]
In this example, [scenario] is a top level tag. When these
lines are read, WML will know that there is a scenario with
the ID "Elves Besieged". Later, when WML is told to play
that scenario, it will read the [side] tag and give 100 gold
to side 1. Then it will read the [+side] tag.
It interprets this tag as belonging to side 1, since the
most recent [side] belonged to side 1. So the [+side] tag
allows side 1 to recruit Elvish Fighters and Elvish Archers.
(Then it will crash, as the leader of side 1 has no unit type.
But this isn't really important.)

Notes: Normally the order and indentation of attributes and tags
does not matter, as long as the levels within tags are not changed.
So the above example could have been written:
[scenario]
[side]
gold=100
side=1
[/side]
id=Elves Besieged
[/scenario]
Data inside tags should be separated with tabbing; see [[ConventionsWML]].

== See Also ==

* [[PreprocessorRef]]
* [[ReferenceWML]]

User:Ott

2005-11-22T11:36:19Z

Ott:

User:Ott

2005-11-17T20:24:55Z

Ott:

DebugMode

2005-11-15T03:51:48Z

Ott:

== Debug Mode ==

Running the game with commandline option ''--debug'' or ''-d''
enables '''debug mode''' within the game.

Debug mode displays additional information. It also enables
context menu options to create units anywhere on the map, changing unit sides, and some additional [[CommandMode]] commands. If you create units in debug mode, you can then use the :unit command to set the unit's attributes (see [[CommandMode]]).

Debug mode can also be enabled within the game using :debug (see [[CommandMode]]), and on Mac versions of the game, by holding down the Option key when starting Wesnoth.

''' Debug mode is disabled when you play a network multiplayer game. '''

== Building the game with extra debugging ==

The game can be built to support debugging by supplying ''--enable-debug'' as an argument to ''configure'' during the build process. Currently this enables a few code snippets for the benefit of an external debugging tool like ''gdb'',
and calls the compiler with ''-g'' and ''-O0'' flags.
You probably don't want to strip a debugging build, since the symbols are needed for the debugging tool.

An unstripped debug build on linux is over 80MB, compared to 2-3MB stripped. It is a good idea to run a debug build of the game if you do development, since it can be necessary to diagnose serious problems.

== See Also ==

* [[CommandMode]]
* [[DeveloperResources]]

MultiplayerServers

2005-11-14T09:27:52Z

Ott:

The game server runs on TCP port 15000 by default.

== Public Official servers ==
; server.wesnoth.org : most recent release of the game (the same server as devsrv.wesnoth.org)
; <nowiki>server.wesnoth.org:14999</nowiki> : up-to-date CVS version of the game, uses port 14999

== Alternative servers setup by users ==
; soliton.homelinux.org : most recent release of the game, dynamic IP (if not online, just ask Soliton on [irc://irc.freenode.org#wesnoth #wesnoth])
; wesnothfr.ww7.be : v1.0 dedicated server in france ([irc://irc.freenode.org#wesnothfr #wesnothfr])
; wesnoth.geeknode.org : v0.9.3 dedicated server ([irc://irc.geeknode.org#wesnoth #wesnoth])

StartingPoints

2005-11-14T09:24:36Z

Ott: /* Other */

__NOTOC__
Battle for Wesnoth is a turn-based fantasy strategy game.

Defeat all enemy leaders using a well-chosen cadre of troops,
taking care to manage your resources of gold and villages.
All units have their own strengths and weaknesses; to win,
deploy your forces to their best advantage while
denying your foes the chance to do the same. As units gain
experience, they acquire new abilities and become more
powerful. Play in your own language and test your skill
against a smart computer opponent, or join Wesnoth's large
community of on-line players.
Create your own custom units, scenarios or campaigns,
and share them with others.

Battle for Wesnoth is released under the
[http://www.gnu.org/licenses/licenses.html#GPL GPL].
Prebuilt packages are available for most operating systems,
including Windows, Mac OS X, and GNU/Linux, or you can build
your own from source code.

== Getting the Game ==
==== Downloading ====
* [[Download]] - get the most recent source-files and many binaries
** [[WesnothBinaries]] - precompiled for GNU/Linux, BeOS, PDAs, ...
** [[WesnothBinariesLinux]] - precompiled for many GNU/Linux distributions

==== Compiling ====
* [[CompilingWesnoth]] - on Unix, Mac, Windows, GNU/Linux, PDAs, ...
* [[DebuggingWesnoth]] - on GNU/Linux and Unix-like systems
* [[WesnothOnLinuxPDAs]] - on the Qtopia/OPIE and thepdaXrom/Zaurus C series

== Playing the Game ([[Play]]) ==

==== For New Players ====
* [[GettingStarted]] - read me first!
* [[WesnothManual]] - the rules
* [[MainlineScenarios]] - walkthroughs for the game-supplied campaigns

==== For Not-So-New Players ====
* [[AdvancedTactics]] - beating the AI and other people
* [[MultiplayerServers]] - where to play against other people online

==== Reference ====
* [[HotKeysSystem]] - keyboard shortcuts
* [[CommandMode]] - commands you can use in-game
* [[ServerAdministration]] - commands that authenticated users can use to administer the server
* [http://wesnoth.slack.it/units.cgi Units] - Units advancement trees and stats
** [http://wesnoth.slack.it/units.cgi?page=frames Wesnoth Unit List] ([http://wesnoth.slack.it/units.cgi?page=list without frames])
** [http://wesnoth.slack.it/units.cgi?factions Factions]
** [http://wesnoth.slack.it/units.cgi?movetypes Movement, defense and resistance tables]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
* [[GraphicLibrary]] - unit and terrain images posted on the forums
**[[UnsortedContrib]] - Unsorted Contributions
**[[GameArt]] - Art for the main game
* [[WesnothAcronyms|Wesnoth Acronyms (by category)]] - common wesnothian acronyms explained
* [[WesnothAcronyms(alphabetic)|WesnothAcronyms (alphabetic)]] - common wesnothian acronyms explained

== Tweaking the Game ([[Create]]) ==

* [[UserScenarios]] - user-written scenarios, campaigns and game modifications
* [[ReferenceWML]] and [[AlphabeticalWML]] - all about Wesnoth Markup Language
* [[ReferencePythonAPI]] - upcoming Python interface for AI
* [[BuildingCampaigns]] - how to make your own campaigns
* [[BuildingScenarios]] - how to make your own scenarios
*[[BuildingUnits]] - how to make your own units
* [[WesnothMapEditor]] - summary of controls
* [[CastleTutorial]] - how to create tileable castles and other castle-like tilesets
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[UnitAnalysis]] - tool to analyze units

== Improving the Game ==
* [[ReportingBugs]] - use Gna
==== Developer information ====
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [[WesnothSVN]] - accessing the source code
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[UnitDescriptionRewriting]] - coordinating the revision
* [http://wesnoth.slack.it/missing.cgi Missing unit animations and sounds] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[WesnothPreferences]]

==== Game translations ====
* [[GettextForTranslators]] - how to translate Wesnoth under [[GetText]]
* [[WesnothTranslations]] - 11 complete, 2 almost complete, 7 more than halfway, 10 partial
* [[WesCamp]] - a project for translating user-made campaigns

==== Ideas ====
* [[FrequentlyProposedIdeas]] - before you propose an idea, check here!
* [[NewUnits]] - units that exist only in theory
* [[NewTerrains]] - tile status
* To submit a feature request, use http://bugs.wesnoth.org

== About the Game ==
* [[WesnothPhilosophy]] - Dave on Wesnoth
* [[WesnothHistory]] - the Ages of Wesnoth
* [[WesnothGeography]] - description of Wesnoth and surrounding lands
* [[WesnothReviews]] - third party reviews of Wesnoth
* [irc://irc.wesnoth.org/wesnoth #wesnoth] - our IRC channel

== Other ==
* [[UsefulLinks]]
* [[WesnothLSM]] - presentation at LSM
* [http://wesnoth.slack.it/?WesnothPlayerMap Map of Wesnoth player locations] - add yourself to the map!
* [http://en.wikipedia.org/wiki/Battle_for_Wesnoth Wikipedia entry for Wesnoth]
* [[WikiMigration]] - we were looking for a replacement for our old wiki (and ended up using Mediawiki)

== About this Wiki ==
* [[Help:Editing|Editing]] - learn how to edit pages
* [[Sandbox]] - experiment with the wiki

User:Ott

2005-11-12T08:56:47Z

Ott:

For now, see [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=970 my forum profile].

Some of my Wesnoth forum postings may be worth reading:
* [http://www.wesnoth.org/forum/viewtopic.php?p=91620#91620 Distribution of damage]
* [http://www.wesnoth.org/forum/viewtopic.php?t=5867 Calculating %-to-kill] and a [http://www.wesnoth.org/forum/viewtopic.php?t=8273 %-to-kill], a more recent version
* [http://www.wesnoth.org/forum/viewtopic.php?p=78398#78398 Overview of postings about in-game random number generation]
* [http://www.wesnoth.org/forum/viewtopic.php?p=53968#53968 Analysing anomalies in game statistics]
* [http://www.wesnoth.org/forum/viewtopic.php?t=4240 The RATE damage model] (used in-game since 0.8.10)
* rant about [http://www.wesnoth.org/forum/viewtopic.php?p=113959#113959 slow] being too complex

I was also originally responsible for the [[Status of User Scenarios]] page.

Create

2005-11-12T08:03:25Z

Ott: /* Read this first! */

Interested in creating your own scenarios and campaigns? One of Wesnoth's best features is its extensibility. Players can create new maps, units, races, scenarios, art, music, and even entire campaigns. Access to the "guts" of the game is both simple and difficult; if you have an ASCII text editor you have everything you need to build your own world. However, learning the Wesnoth Markup Language (WML) takes some effort. This section will guide you through the process of creating and distributing your own content.

== Read this first! ==
Before you modify or add anything, it is important to understand how the game stores and organizes its data. This article will explain the game's directory structure and introduce the ''userdata'' directory.
* [[EditingWesnoth]]

== What can I create, and how? ==

<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth_editor-1.jpg http://www.wesnoth.org/images/sshots/wesnoth_editor-1-175.jpg]
<div class="thumbcaption">Battle for Wesnoth Map editor</div></div>
</div>

* [[BuildingMaps|Maps]] - the layout of terrain tiles
* [[BuildingScenarios|Scenarios]] - a scenario makes things happen on a map, making it playable
* [[BuildingCampaigns|Campaigns]] - how to put it all together into a campaign
* [[BuildingMultiplayer|Multiplayer Maps and Scenarios]] - a specialized look at maps and scenarios
* [[BuildingUnits|Units]]
* [[BuildingFactions|Multiplayer factions and eras]]
* [[Create Art|Art]] - complete with ''tutorials!''
* [[Create Music|Music]]
* [[Distributing content]] - all about the campaign server

== What have others done? ==
Quick descriptions of the campaigns and scenarios that have been published on the campaign server.
* [[UserScenarios|User contributed campaigns]]
This there are a multitude multiplayer maps and discussion of the campaigns on the [http://www.wesnoth.org/forum Wesnoth forum]
* [http://www.wesnoth.org/forum/viewforum.php?f=15 Multiplayer development forum]
* [http://www.wesnoth.org/forum/viewforum.php?f=8 Scenario and campaign development forum]

== The world of Wesnoth ==
Many campaigns do not take place in Wesnoth, but many do. There is definitely a certain flavor to campaigns that are intended to take place somewhere in the world of Wesnoth. Stake out a time period or a map locale and tell a story.
* [[WesnothHistory|The history of Wesnoth]]
* [[WesnothGeography|The geography of Wesnoth]]
* [[RaceDescriptions|The races of creatures in Wesnoth]]
* [[WesnothPoetry|Wesnothian poetry]]

== Miscellaneous ==
* [[ReferenceWML|WML Reference]] - a quicklink
* [[FAQ#Scenario_and_Campaigns|FAQ]] - if you have a question, post it
* Campaign server [http://wolff.to/campaigns/list.html web interface] - An alternate way to download user campaigns
* [[Status_of_User_Scenarios| Status of User Scenarios]] - Lists which usercampaigns are working and which ones are broken
{{Home}}

StartingPoints

2005-11-12T07:59:01Z

Ott: /* Reference */

__NOTOC__
Battle for Wesnoth is a turn-based fantasy strategy game.

Defeat all enemy leaders using a well-chosen cadre of troops,
taking care to manage your resources of gold and villages.
All units have their own strengths and weaknesses; to win,
deploy your forces to their best advantage while
denying your foes the chance to do the same. As units gain
experience, they acquire new abilities and become more
powerful. Play in your own language and test your skill
against a smart computer opponent, or join Wesnoth's large
community of on-line players.
Create your own custom units, scenarios or campaigns,
and share them with others.

Battle for Wesnoth is released under the
[http://www.gnu.org/licenses/licenses.html#GPL GPL].
Prebuilt packages are available for most operating systems,
including Windows, Mac OS X, and GNU/Linux, or you can build
your own from source code.

== Getting the Game ==
==== Downloading ====
* [[Download]] - get the most recent source-files and many binaries
** [[WesnothBinaries]] - precompiled for GNU/Linux, BeOS, PDAs, ...
** [[WesnothBinariesLinux]] - precompiled for many GNU/Linux distributions

==== Compiling ====
* [[CompilingWesnoth]] - on Unix, Mac, Windows, GNU/Linux, PDAs, ...
* [[DebuggingWesnoth]] - on GNU/Linux and Unix-like systems
* [[WesnothOnLinuxPDAs]] - on the Qtopia/OPIE and thepdaXrom/Zaurus C series

== Playing the Game ([[Play]]) ==

==== For New Players ====
* [[GettingStarted]] - read me first!
* [[WesnothManual]] - the rules
* [[MainlineScenarios]] - walkthroughs for the game-supplied campaigns

==== For Not-So-New Players ====
* [[AdvancedTactics]] - beating the AI and other people
* [[MultiplayerServers]] - where to play against other people online

==== Reference ====
* [[HotKeysSystem]] - keyboard shortcuts
* [[CommandMode]] - commands you can use in-game
* [[ServerAdministration]] - commands that authenticated users can use to administer the server
* [http://wesnoth.slack.it/units.cgi Units] - Units advancement trees and stats
** [http://wesnoth.slack.it/units.cgi?page=frames Wesnoth Unit List] ([http://wesnoth.slack.it/units.cgi?page=list without frames])
** [http://wesnoth.slack.it/units.cgi?factions Factions]
** [http://wesnoth.slack.it/units.cgi?movetypes Movement, defense and resistance tables]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
* [[GraphicLibrary]] - unit and terrain images posted on the forums
**[[UnsortedContrib]] - Unsorted Contributions
**[[GameArt]] - Art for the main game
* [[WesnothAcronyms|Wesnoth Acronyms (by category)]] - common wesnothian acronyms explained
* [[WesnothAcronyms(alphabetic)|WesnothAcronyms (alphabetic)]] - common wesnothian acronyms explained

== Tweaking the Game ([[Create]]) ==

* [[UserScenarios]] - user-written scenarios, campaigns and game modifications
* [[ReferenceWML]] and [[AlphabeticalWML]] - all about Wesnoth Markup Language
* [[ReferencePythonAPI]] - upcoming Python interface for AI
* [[BuildingCampaigns]] - how to make your own campaigns
* [[BuildingScenarios]] - how to make your own scenarios
*[[BuildingUnits]] - how to make your own units
* [[WesnothMapEditor]] - summary of controls
* [[CastleTutorial]] - how to create tileable castles and other castle-like tilesets
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[UnitAnalysis]] - tool to analyze units

== Improving the Game ==
* [[ReportingBugs]] - use Gna
==== Developer information ====
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [[WesnothSVN]] - accessing the source code
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[UnitDescriptionRewriting]] - coordinating the revision
* [http://wesnoth.slack.it/missing.cgi Missing unit animations and sounds] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[WesnothPreferences]]

==== Game translations ====
* [[GettextForTranslators]] - how to translate Wesnoth under [[GetText]]
* [[WesnothTranslations]] - 11 complete, 2 almost complete, 7 more than halfway, 10 partial
* [[WesCamp]] - a project for translating user-made campaigns

==== Ideas ====
* [[FrequentlyProposedIdeas]] - before you propose an idea, check here!
* [[NewUnits]] - units that exist only in theory
* [[NewTerrains]] - tile status
* To submit a feature request, use http://bugs.wesnoth.org

== About the Game ==
* [[WesnothPhilosophy]] - Dave on Wesnoth
* [[WesnothHistory]] - the Ages of Wesnoth
* [[WesnothGeography]] - description of Wesnoth and surrounding lands
* [[WesnothReviews]] - third party reviews of Wesnoth
* [irc://irc.wesnoth.org/wesnoth #wesnoth] - our IRC channel

== Other ==
* [[UsefulLinks]]
* [[WesnothLSM]] - presentation at LSM
* [http://wesnoth.slack.it/?WesnothPlayerMap Wesnoth player's map] - add yourself to the map!
* [http://en.wikipedia.org/wiki/Battle_for_Wesnoth Wikipedia entry for Wesnoth]
* [[WikiMigration]] - we are looking for a replacement

== About this Wiki ==
* [[Help:Editing|Editing]] - learn how to edit pages
* [[Sandbox]] - experiment with the wiki

StartingPoints

2005-11-12T07:56:29Z

Ott: /* Tweaking the Game (Create) */

__NOTOC__
Battle for Wesnoth is a turn-based fantasy strategy game.

Defeat all enemy leaders using a well-chosen cadre of troops,
taking care to manage your resources of gold and villages.
All units have their own strengths and weaknesses; to win,
deploy your forces to their best advantage while
denying your foes the chance to do the same. As units gain
experience, they acquire new abilities and become more
powerful. Play in your own language and test your skill
against a smart computer opponent, or join Wesnoth's large
community of on-line players.
Create your own custom units, scenarios or campaigns,
and share them with others.

Battle for Wesnoth is released under the
[http://www.gnu.org/licenses/licenses.html#GPL GPL].
Prebuilt packages are available for most operating systems,
including Windows, Mac OS X, and GNU/Linux, or you can build
your own from source code.

== Getting the Game ==
==== Downloading ====
* [[Download]] - get the most recent source-files and many binaries
** [[WesnothBinaries]] - precompiled for GNU/Linux, BeOS, PDAs, ...
** [[WesnothBinariesLinux]] - precompiled for many GNU/Linux distributions

==== Compiling ====
* [[CompilingWesnoth]] - on Unix, Mac, Windows, GNU/Linux, PDAs, ...
* [[DebuggingWesnoth]] - on GNU/Linux and Unix-like systems
* [[WesnothOnLinuxPDAs]] - on the Qtopia/OPIE and thepdaXrom/Zaurus C series

== Playing the Game ([[Play]]) ==

==== For New Players ====
* [[GettingStarted]] - read me first!
* [[WesnothManual]] - the rules
* [[MainlineScenarios]] - walkthroughs for the game-supplied campaigns

==== For Not-So-New Players ====
* [[AdvancedTactics]] - beating the AI and other people
* [[MultiplayerServers]] - where to play against other people online

==== Reference ====
* [[HotKeysSystem]] - keyboard shortcuts
* [[CommandMode]] - commands you can use in-game
* [[ServerAdministration]] - commands that authenticated users can use to administer the server
* [http://wesnoth.slack.it/units.cgi Units] - Units stats and advance trees
** [http://wesnoth.slack.it/units.cgi?page=frames Wesnoth Unit List]
** ([http://wesnoth.slack.it/units.cgi?page=list without frames])
** [http://wesnoth.slack.it/units.cgi Experience Tree]
** [http://wesnoth.slack.it/units.cgi?factions Factions]
** [http://wesnoth.slack.it/units.cgi?movetypes Movement, defense and resistance tables]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
* [[GraphicLibrary]] - unit and terrain images posted on the forums
**[[UnsortedContrib]] - Unsorted Contributions
**[[GameArt]] - Art for the main game
* [[WesnothAcronyms|Wesnoth Acronyms (by category)]] - common wesnothian acronyms explained
* [[WesnothAcronyms(alphabetic)|WesnothAcronyms (alphabetic)]] - common wesnothian acronyms explained

== Tweaking the Game ([[Create]]) ==

* [[UserScenarios]] - user-written scenarios, campaigns and game modifications
* [[ReferenceWML]] and [[AlphabeticalWML]] - all about Wesnoth Markup Language
* [[ReferencePythonAPI]] - upcoming Python interface for AI
* [[BuildingCampaigns]] - how to make your own campaigns
* [[BuildingScenarios]] - how to make your own scenarios
*[[BuildingUnits]] - how to make your own units
* [[WesnothMapEditor]] - summary of controls
* [[CastleTutorial]] - how to create tileable castles and other castle-like tilesets
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[UnitAnalysis]] - tool to analyze units

== Improving the Game ==
* [[ReportingBugs]] - use Gna
==== Developer information ====
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [[WesnothSVN]] - accessing the source code
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[UnitDescriptionRewriting]] - coordinating the revision
* [http://wesnoth.slack.it/missing.cgi Missing unit animations and sounds] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[WesnothPreferences]]

==== Game translations ====
* [[GettextForTranslators]] - how to translate Wesnoth under [[GetText]]
* [[WesnothTranslations]] - 11 complete, 2 almost complete, 7 more than halfway, 10 partial
* [[WesCamp]] - a project for translating user-made campaigns

==== Ideas ====
* [[FrequentlyProposedIdeas]] - before you propose an idea, check here!
* [[NewUnits]] - units that exist only in theory
* [[NewTerrains]] - tile status
* To submit a feature request, use http://bugs.wesnoth.org

== About the Game ==
* [[WesnothPhilosophy]] - Dave on Wesnoth
* [[WesnothHistory]] - the Ages of Wesnoth
* [[WesnothGeography]] - description of Wesnoth and surrounding lands
* [[WesnothReviews]] - third party reviews of Wesnoth
* [irc://irc.wesnoth.org/wesnoth #wesnoth] - our IRC channel

== Other ==
* [[UsefulLinks]]
* [[WesnothLSM]] - presentation at LSM
* [http://wesnoth.slack.it/?WesnothPlayerMap Wesnoth player's map] - add yourself to the map!
* [http://en.wikipedia.org/wiki/Battle_for_Wesnoth Wikipedia entry for Wesnoth]
* [[WikiMigration]] - we are looking for a replacement

== About this Wiki ==
* [[Help:Editing|Editing]] - learn how to edit pages
* [[Sandbox]] - experiment with the wiki

WesnothRepository

2005-11-12T07:53:34Z

Ott: /* Update */

== SVN ==

Wesnoth development currently uses the Subversion
software tool to keep developers in sync with each other. See the
[http://svnbook.org SVN book] for
more on how to use Subversion.

== Browse the code ==

There are currently two main streams of development: trunk (1.1.x) and branch (1.0.x). There is also a branch for a Python interface to the AI. You can use your web browser to navigate through the source code:

http://svn.gna.org/viewcvs/wesnoth/

== Download ==

To check out trunk into a directory ''wesnoth'':
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth

or to check out the 1.0 branch into a directory ''wesnoth-1.0'':
svn co http://svn.gna.org/svn/wesnoth/branches/1.0 wesnoth-1.0

More info on the repository: https://gna.org/svn/?group=wesnoth

== Update ==

Do this from inside the ''wesnoth'' or ''wesnoth-1.0'' directory where you checked out the repository:
svn update

Note that when you update from Subversion, you should always run 'autogen.sh' if ''configure.ac'' or any of the ''Makefile.am'' files were changed. It is safest to 'make clean' before updating, then update and finally run 'autogen.sh', 'configure' and 'make'.

You may be able to skip the 'autogen.sh' and the 'make clean' if the makefiles and ''configure.ac'' have not changed. If only minor changes were made then even the 'configure' step is optional.

== See Also ==

* [[CompilingWesnoth]]
* [[UsingAutotools]]

WesnothRepository

2005-11-12T07:51:58Z

Ott:

== SVN ==

Wesnoth development currently uses the Subversion
software tool to keep developers in sync with each other. See the
[http://svnbook.org SVN book] for
more on how to use Subversion.

== Browse the code ==

There are currently two main streams of development: trunk (1.1.x) and branch (1.0.x). There is also a branch for a Python interface to the AI. You can use your web browser to navigate through the source code:

http://svn.gna.org/viewcvs/wesnoth/

== Download ==

To check out trunk into a directory ''wesnoth'':
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth

or to check out the 1.0 branch into a directory ''wesnoth-1.0'':
svn co http://svn.gna.org/svn/wesnoth/branches/1.0 wesnoth-1.0

More info on the repository: https://gna.org/svn/?group=wesnoth

== Update ==

Do this from inside the ''wesnoth'' or ''wesnoth-1.0'' directory where you checked out the repository:
svn update

Note that when you update from Subversion, you should always run 'autogen.sh' if ''configure.ac'' or any of the ''Makefile.am'' files were changed. It is safest to 'make clean' before updating, then run 'autogen.sh', 'configure' and 'make'.

You may be able to skip the 'autogen.sh' and the 'make clean' if the makefiles and ''configure.ac'' have not changed. If only minor changes were made then even the 'configure' step is optional.

== See Also ==

* [[CompilingWesnoth]]
* [[UsingAutotools]]

WesnothRepository

2005-11-12T07:44:50Z

Ott: /* Download */

== SVN ==

Wesnoth development currently uses the Subversion
software tool to keep developers in sync with each other. See the
[http://svnbook.org SVN book] for
more on how to use Subversion.

== Browse the code ==

You can use your web browser to navigate through the source code:

http://svn.gna.org/viewcvs/wesnoth/

== Download ==

There are currently two main streams of development: trunk (1.1.x) and branch (1.0.x). There is also a branch for a Python interface to the AI. To check out trunk into a directory ''wesnoth'':
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth

or to check out the 1.0 branch into a directory ''wesnoth-1.0'':
svn co http://svn.gna.org/svn/wesnoth/branches/1.0 wesnoth-1.0

More info on the repository: https://gna.org/svn/?group=wesnoth

== Update ==

Do this from inside the ''wesnoth'' or ''wesnoth-1.0'' directory where you checked out the repository:
svn update

Note that when you update from Subversion, you should always run 'autogen.sh' if ''configure.ac'' or any of the ''Makefile.am'' files were changed. It is safest to 'make clean' before updating, then run 'autogen.sh', 'configure' and 'make'.

You may be able to skip the 'autogen.sh' and the 'make clean' if the makefiles and ''configure.ac'' have not changed. If only minor changes were made then even the 'configure' step is optional.

== See Also ==

* [[CompilingWesnoth]]
* [[UsingAutotools]]

WesnothRepository

2005-11-12T07:43:08Z

Ott: /* Update */

== SVN ==

Wesnoth development currently uses the Subversion
software tool to keep developers in sync with each other. See the
[http://svnbook.org SVN book] for
more on how to use Subversion.

== Browse the code ==

You can use your web browser to navigate through the source code:

http://svn.gna.org/viewcvs/wesnoth/

== Download ==

There are currently two main streams of development: trunk (1.1.x) and branch (1.0.x). There is also a branch for a Python interface to the AI. To check out trunk:
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth

or to check out the 1.0 branch:
svn co http://svn.gna.org/svn/wesnoth/branches/1.0 wesnoth-1.0

More info on the repository: https://gna.org/svn/?group=wesnoth

== Update ==

Do this from inside the ''wesnoth'' or ''wesnoth-1.0'' directory where you checked out the repository:
svn update

Note that when you update from Subversion, you should always run 'autogen.sh' if ''configure.ac'' or any of the ''Makefile.am'' files were changed. It is safest to 'make clean' before updating, then run 'autogen.sh', 'configure' and 'make'.

You may be able to skip the 'autogen.sh' and the 'make clean' if the makefiles and ''configure.ac'' have not changed. If only minor changes were made then even the 'configure' step is optional.

== See Also ==

* [[CompilingWesnoth]]
* [[UsingAutotools]]

WesnothRepository

2005-11-12T07:41:44Z

Ott: /* Update */

== SVN ==

Wesnoth development currently uses the Subversion
software tool to keep developers in sync with each other. See the
[http://svnbook.org SVN book] for
more on how to use Subversion.

== Browse the code ==

You can use your web browser to navigate through the source code:

http://svn.gna.org/viewcvs/wesnoth/

== Download ==

There are currently two main streams of development: trunk (1.1.x) and branch (1.0.x). There is also a branch for a Python interface to the AI. To check out trunk:
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth

or to check out the 1.0 branch:
svn co http://svn.gna.org/svn/wesnoth/branches/1.0 wesnoth-1.0

More info on the repository: https://gna.org/svn/?group=wesnoth

== Update ==

Do this from inside the "wesnoth" directory where you checked out the repository:
svn update

Note that when you update from Subversion, you should always run 'autogen.sh' if ''configure.ac'' or any of the ''Makefile.am'' files were changed. It is safest to 'make clean' before updating, then run 'autogen.sh', 'configure' and 'make'.

You may be able to skip the 'autogen.sh' and the 'make clean' if the makefiles and ''configure.ac'' have not changed. If only minor changes were made then even the 'configure' step is optional.

== See Also ==

* [[CompilingWesnoth]]
* [[UsingAutotools]]

WesnothRepository

2005-11-12T07:41:01Z

Ott: /* Download */

== SVN ==

Wesnoth development currently uses the Subversion
software tool to keep developers in sync with each other. See the
[http://svnbook.org SVN book] for
more on how to use Subversion.

== Browse the code ==

You can use your web browser to navigate through the source code:

http://svn.gna.org/viewcvs/wesnoth/

== Download ==

There are currently two main streams of development: trunk (1.1.x) and branch (1.0.x). There is also a branch for a Python interface to the AI. To check out trunk:
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth

or to check out the 1.0 branch:
svn co http://svn.gna.org/svn/wesnoth/branches/1.0 wesnoth-1.0

More info on the repository: https://gna.org/svn/?group=wesnoth

== Update ==

Do this from the "wesnoth" directory:
svn update

Note that when you update from Subversion, you should always run 'autogen.sh' if ''configure.ac'' or any of the ''Makefile.am'' files were changed. It is safest to 'make clean' before updating, then run 'autogen.sh', 'configure' and 'make'.

You may be able to skip the 'autogen.sh' and the 'make clean' if the makefiles and ''configure.ac'' have not changed. If only minor changes were made then even the 'configure' step is optional.

== See Also ==

* [[CompilingWesnoth]]
* [[UsingAutotools]]

WesnothRepository

2005-11-12T07:40:19Z

Ott: /* Update */

== SVN ==

Wesnoth development currently uses the Subversion
software tool to keep developers in sync with each other. See the
[http://svnbook.org SVN book] for
more on how to use Subversion.

== Browse the code ==

You can use your web browser to navigate through the source code:

http://svn.gna.org/viewcvs/wesnoth/

== Download ==

There are currently two main streams of development: trunk (1.1.x) and branch (1.0.x). There is also a branch for a Python interface to the AI. To check out trunk:

svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth

or to check out the 1.0 branch:

svn co http://svn.gna.org/svn/wesnoth/branches/1.0 wesnoth

More info on the repository: https://gna.org/svn/?group=wesnoth

== Update ==

Do this from the "wesnoth" directory:
svn update

Note that when you update from Subversion, you should always run 'autogen.sh' if ''configure.ac'' or any of the ''Makefile.am'' files were changed. It is safest to 'make clean' before updating, then run 'autogen.sh', 'configure' and 'make'.

You may be able to skip the 'autogen.sh' and the 'make clean' if the makefiles and ''configure.ac'' have not changed. If only minor changes were made then even the 'configure' step is optional.

== See Also ==

* [[CompilingWesnoth]]
* [[UsingAutotools]]

WesnothRepository

2005-11-12T07:35:14Z

Ott: /* Download */

== SVN ==

Wesnoth development currently uses the Subversion
software tool to keep developers in sync with each other. See the
[http://svnbook.org SVN book] for
more on how to use Subversion.

== Browse the code ==

You can use your web browser to navigate through the source code:

http://svn.gna.org/viewcvs/wesnoth/

== Download ==

There are currently two main streams of development: trunk (1.1.x) and branch (1.0.x). There is also a branch for a Python interface to the AI. To check out trunk:

svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth

or to check out the 1.0 branch:

svn co http://svn.gna.org/svn/wesnoth/branches/1.0 wesnoth

More info on the repository: https://gna.org/svn/?group=wesnoth

== Update ==

Do this from the "wesnoth" directory:
svn up

Note that when you update from Subversion, you should always run 'autogen.sh' and
'make clean' before 'configure' and 'make'.
If you don't do this, the game may crash or behave strangely.
You may be able to skip the 'autogen.sh' if the makefiles and ''configure.ac''
have not changed, and 'make clean' is becoming less critical also.

== See Also ==

* [[CompilingWesnoth]]
* [[UsingAutotools]]

StartingPoints

2005-11-12T07:30:37Z

Ott: /* Developer information */

__NOTOC__
Battle for Wesnoth is a turn-based fantasy strategy game.

Defeat all enemy leaders using a well-chosen cadre of troops,
taking care to manage your resources of gold and villages.
All units have their own strengths and weaknesses; to win,
deploy your forces to their best advantage while
denying your foes the chance to do the same. As units gain
experience, they acquire new abilities and become more
powerful. Play in your own language and test your skill
against a smart computer opponent, or join Wesnoth's large
community of on-line players.
Create your own custom units, scenarios or campaigns,
and share them with others.

Battle for Wesnoth is released under the
[http://www.gnu.org/licenses/licenses.html#GPL GPL].
Prebuilt packages are available for most operating systems,
including Windows, Mac OS X, and GNU/Linux, or you can build
your own from source code.

== Getting the Game ==
==== Downloading ====
* [[Download]] - get the most recent source-files and many binaries
** [[WesnothBinaries]] - precompiled for GNU/Linux, BeOS, PDAs, ...
** [[WesnothBinariesLinux]] - precompiled for many GNU/Linux distributions

==== Compiling ====
* [[CompilingWesnoth]] - on Unix, Mac, Windows, GNU/Linux, PDAs, ...
* [[DebuggingWesnoth]] - on GNU/Linux and Unix-like systems
* [[WesnothOnLinuxPDAs]] - on the Qtopia/OPIE and thepdaXrom/Zaurus C series

== Playing the Game ([[Play]]) ==

==== For New Players ====
* [[GettingStarted]] - read me first!
* [[WesnothManual]] - the rules
* [[MainlineScenarios]] - walkthroughs for the game-supplied campaigns

==== For Not-So-New Players ====
* [[AdvancedTactics]] - beating the AI and other people
* [[MultiplayerServers]] - where to play against other people online

==== Reference ====
* [[HotKeysSystem]] - keyboard shortcuts
* [[CommandMode]] - commands you can use in-game
* [[ServerAdministration]] - commands that authenticated users can use to administer the server
* [http://wesnoth.slack.it/units.cgi Units] - Units stats and advance trees
** [http://wesnoth.slack.it/units.cgi?page=frames Wesnoth Unit List]
** ([http://wesnoth.slack.it/units.cgi?page=list without frames])
** [http://wesnoth.slack.it/units.cgi Experience Tree]
** [http://wesnoth.slack.it/units.cgi?factions Factions]
** [http://wesnoth.slack.it/units.cgi?movetypes Movement, defense and resistance tables]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
* [[GraphicLibrary]] - unit and terrain images posted on the forums
**[[UnsortedContrib]] - Unsorted Contributions
**[[GameArt]] - Art for the main game
* [[WesnothAcronyms|Wesnoth Acronyms (by category)]] - common wesnothian acronyms explained
* [[WesnothAcronyms(alphabetic)|WesnothAcronyms (alphabetic)]] - common wesnothian acronyms explained

== Tweaking the Game ([[Create]]) ==

* [[UserScenarios]] - user-written scenarios, campaigns and game modifications
* [[ReferenceWML]] - all about Wesnoth Markup Language
* [[ReferencePythonAPI]] - upcoming Python interface for AI
* [[BuildingCampaigns]] - how to make your own campaigns
* [[BuildingScenarios]] - how to make your own scenarios
*[[BuildingUnits]] - how to make your own units
* [[WesnothMapEditor]] - summary of controls
* [[CastleTutorial]] - how to create tileable castles and other castle-like tilesets
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[UnitAnalysis]] - tool to analyze units

== Improving the Game ==
* [[ReportingBugs]] - use Gna
==== Developer information ====
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [[WesnothSVN]] - accessing the source code
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[UnitDescriptionRewriting]] - coordinating the revision
* [http://wesnoth.slack.it/missing.cgi Missing unit animations and sounds] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[WesnothPreferences]]

==== Game translations ====
* [[GettextForTranslators]] - how to translate Wesnoth under [[GetText]]
* [[WesnothTranslations]] - 11 complete, 2 almost complete, 7 more than halfway, 10 partial
* [[WesCamp]] - a project for translating user-made campaigns

==== Ideas ====
* [[FrequentlyProposedIdeas]] - before you propose an idea, check here!
* [[NewUnits]] - units that exist only in theory
* [[NewTerrains]] - tile status
* To submit a feature request, use http://bugs.wesnoth.org

== About the Game ==
* [[WesnothPhilosophy]] - Dave on Wesnoth
* [[WesnothHistory]] - the Ages of Wesnoth
* [[WesnothGeography]] - description of Wesnoth and surrounding lands
* [[WesnothReviews]] - third party reviews of Wesnoth
* [irc://irc.wesnoth.org/wesnoth #wesnoth] - our IRC channel

== Other ==
* [[UsefulLinks]]
* [[WesnothLSM]] - presentation at LSM
* [http://wesnoth.slack.it/?WesnothPlayerMap Wesnoth player's map] - add yourself to the map!
* [http://en.wikipedia.org/wiki/Battle_for_Wesnoth Wikipedia entry for Wesnoth]
* [[WikiMigration]] - we are looking for a replacement

== About this Wiki ==
* [[Help:Editing|Editing]] - learn how to edit pages
* [[Sandbox]] - experiment with the wiki

EditingWesnoth

2005-11-11T17:55:11Z

Ott: /* Windows */

== Game and User Directories ==

Wherever you install the game, there will be a game data directory that contains, of course, the game's data. This directory should have the following subdirectories: data, music, sounds, and images. There are several others, but these are the important ones. In this wiki, the terms "game data", wesnoth/data, or ./data refers to the wesnoth/data directory. You normally do not need to modify these files, but you can if you want to modify a unit or something.

The user data directory allows you to add custom content without modifying the game's own files. Each OS puts its user data directory in a different place. In this wiki, "user data", ''userdata''/''subdirectory'', or (occasionally) ~wesnoth/ refer to this directory.

=== Where is my '''game''' data directory? ===

====Windows====
Usually C:\Program Files\Wesnoth\data but it will be different if you installed the game in a different location: look for the data folder in the folder where you installed the game.

====Mac OS X====
Downloaded from sourceforge: command-click on the application icon. Select "Show Package Contents." Select "Contents" then "Resources." <br>
Command line build: /usr/local/share/wesnoth

====Linux====
/usr/local/share/wesnoth <br>
From apt-get: /usr/share/games/wesnoth <br>
other distributions?

=== Where is my '''user''' data directory? ===

====Windows====
c:\Program Files\Wesnoth\userdata

====Mac OS X====
Downloaded from sourceforge: ~/Library/Preferences/Wesnoth <br>
Command line build: ~/.wesnoth

====Linux====
~/.wesnoth

== Game data ==

The major directories you need to know about are wesnoth/data, wesnoth/data/units, wesnoth/data/campaigns, wesnoth/data/maps, wesnoth/data/scenarios, wesnoth/images

Become familiar with what is in ./data/campaigns, ./data/scenarios, and ./data/maps. These have the officially distributed campaigns and multiplayer maps. If you ever want to examine or edit one of the scenario configuration files, this is where you would go. For example, a common question is how a new player can give himself more turns or gold in scenario X. This is where you would go to do that.

Two very important directories are ./data/units and ./images. You have the ability to drop new units or images in these directories and have the game recognize them. When specifying an image for something, you do so relative to ./images.

=== Game Configuration ===

Some information is stored in files in the ./data directory itself:
* amla.cfg - global definition for After Max-Level Advancement (currently 3 hp per 100 XP)
* fonts.cfg - defines which fonts the game can use
* game.cfg
* help.cfg - the entire help system document
* items.cfg - macros for common objects and items used in the game, also available for campaign writer use
* multiplayer.cfg - defines the multiplayer eras and factions
* names.cfg - lists of name fragments that are randomly put together to create random-sounding names. Segregated by race and gender
* scenario-test.cfg - a simple test scenario. Run it with the command wesnoth -t
* schedules.cfg - defines the global day-night cycle
* terrain.cfg - defines the terrain types
* terrain-graphics.cfg - defines terrain layering and usage of random terrain
* tips.cfg - the contents of the Tome of Wesnoth
* traits.cfg - defines all traits used globally in the game
* utils.cfg - some common macros used in the game, also available for campaign writer use
* units.cfg - defines the races, which traits each race has, and the movement types (which set defenses, resistances, and movement costs)

For more information about game configuration:
* themes/: [[ThemeSystem]]
* maps/: [[BuildingMaps]]
* scenarios/: [[BuildingScenarios]]
* translations/: [[WesnothTranslations]]
* units/: [[BuildingUnits]]
* game.cfg: [[WesnothGameConfigure]]

== User Data ==
The user data directory can do a lot of things. The game looks here for several things:
* ''userdata''/data/campaigns - campaign configuration files and subdirectories
* ''userdata''/data/editor/maps - multiplayer standalone maps (map data only)
* ''userdata''/data/units - drop your custom units here, and they will be visible to the game
* ''userdata''/data/images - drop your custom images here, and they will be visible to the game

The ''userdata''/data/campaigns directory is particularly useful. A single configuration file here can selectively point to an entire subdirectory tree of units, images, sounds, scenarios, and macros. This allows you to wall off parts. Content included in the userdata units or images directories will be available globally whether you want it or not. Content included in the campaigns directory won't be loaded unless the game is told to do it.

For example, assume you have a campaign called MyCampaign. This is what the ''userdata''/data/campaigns directory looks like:
* ''userdata''/data/campaigns/MyCampaign.cfg - a text file
* ''userdata''/data/campaigns/MyCampaign/ - a subdirectory
** ''userdata''/data/campaigns/MyCampaign/scenarios
** ''userdata''/data/campaigns/MyCampaign/units
** ''userdata''/data/campaigns/MyCampaign/images
** ''userdata''/data/campaigns/MyCampaign/music
** ''userdata''/data/campaigns/MyCampaign/sounds
** ''userdata''/data/campaigns/MyCampaign/utils

MyCampaign.cfg will have something called the "campaign ifdef", which is a syntax structure that instructs the game to search ''userdata''/data/campaigns/MyCampaign/ for data. More about this is found in [[BuildingCampaigns]]. However, it is important to understand the different capabilites of the user data directory.

== See Also ==

* [[Create]]

User:Ott

2005-11-11T17:40:16Z

Ott:

For now, see [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=970 my forum profile].

Some of my Wesnoth forum postings may be worth reading:
* [http://www.wesnoth.org/forum/viewtopic.php?p=91620#91620 Distribution of damage]
* [http://www.wesnoth.org/forum/viewtopic.php?t=5867 Calculating %-to-kill] and a [http://www.wesnoth.org/forum/viewtopic.php?t=8273 %-to-kill], a more recent version
* [http://www.wesnoth.org/forum/viewtopic.php?p=78398#78398 Overview of postings about in-game random number generation]
* [http://www.wesnoth.org/forum/viewtopic.php?p=53968#53968 Analysing anomalies in game statistics]
* [http://www.wesnoth.org/forum/viewtopic.php?t=4240 The RATE damage model] (used in-game since 0.8.10)

I was also originally responsible for the [[Status of User Scenarios]] page.

HelpWML

2005-11-11T16:48:36Z

Ott: /* the toplevel [help] tag */

== The toplevel [help] tag ==

The [help] tag describes the Wesnoth help system.
Each of the three subtags [toplevel], [section] and [topic] describe an element of the help system.

* '''[toplevel]''' The toplevel tag denotes sections and topics that should be shown immediately when the "Help" button is clicked on (see the "help" action, [[ThemeWML]]). The sections referenced within this tag are read recursively, including all subsections.
** ''sections'' a list of IDs of the sections to include recursively.
** ''topics'' a list of IDs of the topics to show as not being included in a section; i.e. top-level topics.
* '''[section]''' The section tag describes a section in the help browser. A section contains subsections and/or topics.
** ''id'' is the unique ID for this section.
** ''title'' (translatable) is the title of the section. It is displayed in the left menu.
** ''sections'' is a list of IDs of the sections that should be this section's subsections.
** ''topics'' is a list of IDs of the topics that should be included in this section.
* '''[topic]''' The topic tag describes one topic, i.e, one help page. The keys that are meaningful in the topic tag:
** ''id'' is the unique ID for this topic.
** ''title'' (translatable) is the title of the topic. It is displayed in the left menu and as a header in the text area.
** ''text'' (translatable) is the contents of the topics. May contain markup described below.

== Help System Topic Markup ==

The markup that is allowed in the text key within a topic tag is in XML, a markup language similar to WML. Note that this is the only time that markup language is used as a value. To convert WML into XML, you need to make some changes:

- change brackets ('''[''', ''']''') into angle brackets('''<''', '''>''')

- change ''newline'' into space(''' ''')

- all values with spaces must be in quotes. This is because spaces are actually newlines.

Due to limitations of the wiki (it is coded using XML), the WML for the topic markup will be described rather than
the XML. However, you still need to use XML to code the topic.

The following key/tags are accepted for ''text'':
* '''[ref]''' creates a cross reference to another topic, a cross reference will not show up if the topic it refers to is not visible.
** ''dst'' the ID of the topic to reference.
** ''text'' the text to display as a link to ''dst''; i.e. when ''text'' is clicked on the page ''dst'' will be linked to.
** ''force'' shows the cross reference even though the referred topic is not shown.
* '''[jump]''' when this text is selected, the input position along the X axis is moved. Can be used for example to create columns of things. A jump is ignored if it would bring the input position to an invalid position.
** ''to'' the X coordinate of the text area to jump to. If it can't be done on the current row, the input position is moved down one line.
** ''amount'' the number of pixels to jump forward
* '''[img]''' insert an image in the topic
** ''src'' the path to the image relative to the '''images/''' directory.
** ''align'' the position of the image with respect to the page. Values are ''here'', ''left'', ''middle'', and ''right''.
** ''float'' whether the image should float(have text filled in around it) or not (be seen as included in a line).
* '''[format]''' describes a group of text in a different format. Can be used to describe different colors and font sizes.
** ''bold'' whether the text should be displayed in bold('''bold''').
** ''italic'' whether the text should be displayed in italics(''italics'').
** ''color'' the color of the text. Only a few colors are currently supported: ''white''(default), ''green'', ''red'', ''yellow'', and ''black''.
** ''font_size'' the height of the text in pixels. Default 9(?)
** ''text'' the text to be displayed using this format.
* '''[italic]''' a shortcut to '''[format]''' which inputs only the ''text'' key. Uses the attribute '''italic=yes'''
* '''[bold]''' like [italic], but uses '''bold=yes'''
* '''[header]''' like [italic], but uses both the attributes '''bold=yes''' and '''font_size=13'''(?)

Example:
[help]
[toplevel]
sections=introduction,gameplay
topics=about
[/toplevel]
[section]
id=gameplay
sections=combat
topics=income_and_upkeep,time_of_day,terrain
[/section]
[topic]
id=terrain
title=Terrain
text="<ref>dst=income_and_upkeep text='Link to Income and Upkeep topic'</ref>"
[/topic]
[/help]

== See Also ==

* [[ReferenceWML]]

HelpWML

2005-11-11T16:47:51Z

Ott: /* Help System Topic Markup */

== the toplevel [help] tag ==

The [help] tag describes the Wesnoth help system.
Each of the three subtags [toplevel], [section] and [topic] describe an element of the help system.

* '''[toplevel]''' The toplevel tag denotes sections and topics that should be shown immediately when the "Help" button is clicked on (see the "help" action, [[ThemeWML]]). The sections referenced within this tag are read recursively, including all subsections.
** ''sections'' a list of IDs of the sections to include recursively.
** ''topics'' a list of IDs of the topics to show as not being included in a section; i.e. top-level topics.
* '''[section]''' The section tag describes a section in the help browser. A section contains subsections and/or topics.
** ''id'' is the unique ID for this section.
** ''title'' (translatable) is the title of the section. It is displayed in the left menu.
** ''sections'' is a list of IDs of the sections that should be this section's subsections.
** ''topics'' is a list of IDs of the topics that should be included in this section.
* '''[topic]''' The topic tag describes one topic, i.e, one help page. The keys that are meaningful in the topic tag:
** ''id'' is the unique ID for this topic.
** ''title'' (translatable) is the title of the topic. It is displayed in the left menu and as a header in the text area.
** ''text'' (translatable) is the contents of the topics. May contain markup described below

== Help System Topic Markup ==

The markup that is allowed in the text key within a topic tag is in XML, a markup language similar to WML. Note that this is the only time that markup language is used as a value. To convert WML into XML, you need to make some changes:

- change brackets ('''[''', ''']''') into angle brackets('''<''', '''>''')

- change ''newline'' into space(''' ''')

- all values with spaces must be in quotes. This is because spaces are actually newlines.

Due to limitations of the wiki (it is coded using XML), the WML for the topic markup will be described rather than
the XML. However, you still need to use XML to code the topic.

The following key/tags are accepted for ''text'':
* '''[ref]''' creates a cross reference to another topic, a cross reference will not show up if the topic it refers to is not visible.
** ''dst'' the ID of the topic to reference.
** ''text'' the text to display as a link to ''dst''; i.e. when ''text'' is clicked on the page ''dst'' will be linked to.
** ''force'' shows the cross reference even though the referred topic is not shown.
* '''[jump]''' when this text is selected, the input position along the X axis is moved. Can be used for example to create columns of things. A jump is ignored if it would bring the input position to an invalid position.
** ''to'' the X coordinate of the text area to jump to. If it can't be done on the current row, the input position is moved down one line.
** ''amount'' the number of pixels to jump forward
* '''[img]''' insert an image in the topic
** ''src'' the path to the image relative to the '''images/''' directory.
** ''align'' the position of the image with respect to the page. Values are ''here'', ''left'', ''middle'', and ''right''.
** ''float'' whether the image should float(have text filled in around it) or not (be seen as included in a line).
* '''[format]''' describes a group of text in a different format. Can be used to describe different colors and font sizes.
** ''bold'' whether the text should be displayed in bold('''bold''').
** ''italic'' whether the text should be displayed in italics(''italics'').
** ''color'' the color of the text. Only a few colors are currently supported: ''white''(default), ''green'', ''red'', ''yellow'', and ''black''.
** ''font_size'' the height of the text in pixels. Default 9(?)
** ''text'' the text to be displayed using this format.
* '''[italic]''' a shortcut to '''[format]''' which inputs only the ''text'' key. Uses the attribute '''italic=yes'''
* '''[bold]''' like [italic], but uses '''bold=yes'''
* '''[header]''' like [italic], but uses both the attributes '''bold=yes''' and '''font_size=13'''(?)

Example:
[help]
[toplevel]
sections=introduction,gameplay
topics=about
[/toplevel]
[section]
id=gameplay
sections=combat
topics=income_and_upkeep,time_of_day,terrain
[/section]
[topic]
id=terrain
title=Terrain
text="<ref>dst=income_and_upkeep text='Link to Income and Upkeep topic'</ref>"
[/topic]
[/help]

== See Also ==

* [[ReferenceWML]]

HelpWML

2005-11-11T16:40:11Z

Ott: /* the toplevel [help] tag */

== the toplevel [help] tag ==

The [help] tag describes the Wesnoth help system.
Each of the three subtags [toplevel], [section] and [topic] describe an element of the help system.

* '''[toplevel]''' The toplevel tag denotes sections and topics that should be shown immediately when the "Help" button is clicked on (see the "help" action, [[ThemeWML]]). The sections referenced within this tag are read recursively, including all subsections.
** ''sections'' a list of IDs of the sections to include recursively.
** ''topics'' a list of IDs of the topics to show as not being included in a section; i.e. top-level topics.
* '''[section]''' The section tag describes a section in the help browser. A section contains subsections and/or topics.
** ''id'' is the unique ID for this section.
** ''title'' (translatable) is the title of the section. It is displayed in the left menu.
** ''sections'' is a list of IDs of the sections that should be this section's subsections.
** ''topics'' is a list of IDs of the topics that should be included in this section.
* '''[topic]''' The topic tag describes one topic, i.e, one help page. The keys that are meaningful in the topic tag:
** ''id'' is the unique ID for this topic.
** ''title'' (translatable) is the title of the topic. It is displayed in the left menu and as a header in the text area.
** ''text'' (translatable) is the contents of the topics. May contain markup described below

== Help System Topic Markup ==

The markup that is allowed in the text key within a topic tag is in XML, a markup language similar to WML.
Note that this is the only time that markup language is used as a value.
To convert WML into XML, you need to make some changes:

- change brackets ('''[||, ||]||) into angle brackets(||<||, ||>''')

- change ''newline'' into space(''' ''')

- all values with spaces must be in quotes. This is because spaces are actually newlines

Due to limitations of the wiki (it is coded using XML), the WML for the topic markup will be described rather than
the XML.
However, you still need to use XML to code the topic.

The following key/tags are accepted for ''text'':
* '''[ref]''' create a cross reference to another topic, a cross reference will not show up if the topic it refers to not
is visible.
** ''dst'' the ID of the topic to reference.
** ''text'' the text to display as a link to ''dst//;i.e. when ''text'' is clicked on the page ''dst'' will be linked to.
** ''force'' show the cross reference even though the referred topic is not shown.
* '''[jump]''' when this text is selected, the input position along the X axis is moved.
Can be used for example to create columns of things.
A jump is ignored if it would bring the input position to an invalid position.
** ''to'' the X coordinate of the text area to jump to.
If it can't be done on the current row, the input position is moved down one line.
** ''amount'' the number of pixels to jump forward
* '''[img]''' insert an image in the topic
** ''src'' the path to the image relative to the '''images/''' directory.
** ''align'' the position of the image with respect to the page. Values are 'left', 'middle', and 'right'.
** ''float'' whether the image should float(have text filled in around it) or not(be seen as included in a line).
* '''[format]''' describes a group of text in a different format.
Can be used to describe different colors and font sizes
** ''bold'' whether the text should be displayed in bold('''bold''')
** ''italic'' whether the text should be displayed in italics(//italics'')
** ''color'' the color of the text.
Only a few colors are currently supported: 'white'(default), 'green', 'red', 'yellow', and 'black'.
** ''font_size'' the height of the text in pixels. Default 9(?)
** ''text'' the text to be displayed using this format
* '''[italic]|| a shortcut to ||[format]''' which inputs only the ''text'' key.
Uses the attribute '''italic=yes'''
* '''[bold]|| like [italic], but uses ||bold=yes'''
* '''[header]|| like [italic], but uses both the attributes ||bold=yes|| and ||font_size=13(?)'''

Example:
[help]
[toplevel]
sections=introduction,gameplay
topics=about
[/toplevel]
[section]
id=gameplay
sections=combat
topics=income_and_upkeep,time_of_day,terrain
[/section]
[topic]
id=terrain
title=Terrain
text="<ref>dst=income_and_upkeep text='Link to Income and Upkeep topic'</ref>"
[/topic]
[/help]

== See Also ==

* [[ReferenceWML]]

Download

2005-10-03T17:55:34Z

Ott: /* Mac OS X */

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient.

== Source code ==
* Wesnoth 1.0: [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.tar.gz?download wesnoth-1.0.tar.gz] (39.1MB) [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.tar.gz.md5?download md5sum]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code Xdelta]
* [[CompilingWesnoth]] - how to compile the source code

== [[BeOS]] ==
* Wesnoth 1.0rc1 for BeOS: [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0rc1-BeOS-x86.pkg.zip?download Wesnoth-1.0rc1-BeOS-x86.pkg.zip] (39.65MB) [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0rc1-BeOS-x86.pkg.zip.md5?download md5sum]

== GNU/Linux ==
* A distribution-independent binary for any somewhat modern GNU/Linux on i386 is available: [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0rc1-i386-Opkg.tar.gz?download wesnoth-1.0rc1-i386-Opkg.tar.gz]
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at [[WesnothBinariesLinux]] for more informations about the binaries for your Distribution.

== Mac OS X ==
* Wesnoth 1.0 for Mac OS X:
** [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.0.dmg?download Sourceforge-hosted build] by Sithrandel (50.2 MB)
* Wesnoth 1.0rc1 for Mac OS X:
** [ftp://victor.teaser.fr/pub/lwa/wesnoth/Wesnoth_MacOSX_1.0rc1.dmg Wesnoth_MacOSX_1.0rc1.dmg] by lwa (40MB)
** [ftp://victor.teaser.fr/pub/lwa/wesnoth/Wesnoth_MacOSX_1.0rc1_lite.dmg Wesnoth_MacOSX_1.0rc1_lite.dmg] by lwa (game only, music and large story images removed) (23MB)

== MS Windows ==
* Wesnoth 1.0 for Microsoft Windows: [http://prdownloads.sourceforge.net/wesnoth/wesnoth-windows-1.0.exe?download wesnoth-windows-1.0.exe] (38.9MB)

== AmigaOS4 ==
* Wesnoth 1.0rc1 for AmigaOS4: http://www.amigasoft.net/downloads/wesnoth.rar (37.7MB)

== License ==
This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org/ Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [http://sourceforge.net/project/showfiles.php?group_id=89495 Previous releases]
* [[WesnothSVN]] - bleeding edge version from SVN

__NOTOC__

Download

2005-10-03T17:53:46Z

Ott: 1.0rc1->1.0

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient.

== Source code ==
* Wesnoth 1.0: [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.tar.gz?download wesnoth-1.0.tar.gz] (39.1MB) [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.tar.gz.md5?download md5sum]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code Xdelta]
* [[CompilingWesnoth]] - how to compile the source code

== [[BeOS]] ==
* Wesnoth 1.0rc1 for BeOS: [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0rc1-BeOS-x86.pkg.zip?download Wesnoth-1.0rc1-BeOS-x86.pkg.zip] (39.65MB) [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0rc1-BeOS-x86.pkg.zip.md5?download md5sum]

== GNU/Linux ==
* A distribution-independent binary for any somewhat modern GNU/Linux on i386 is available: [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0rc1-i386-Opkg.tar.gz?download wesnoth-1.0rc1-i386-Opkg.tar.gz]
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at [[WesnothBinariesLinux]] for more informations about the binaries for your Distribution.

== Mac OS X ==
* Wesnoth 1.0rc1 for Mac OS X:
** [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.0.dmg?download Sourceforge-hosted build] by Sithrandel (50.2 MB)
** [ftp://victor.teaser.fr/pub/lwa/wesnoth/Wesnoth_MacOSX_1.0rc1.dmg Wesnoth_MacOSX_1.0rc1.dmg] by lwa (40MB)
** [ftp://victor.teaser.fr/pub/lwa/wesnoth/Wesnoth_MacOSX_1.0rc1_lite.dmg Wesnoth_MacOSX_1.0rc1_lite.dmg] by lwa (game only, music and large story images removed) (23MB)

== MS Windows ==
* Wesnoth 1.0 for Microsoft Windows: [http://prdownloads.sourceforge.net/wesnoth/wesnoth-windows-1.0.exe?download wesnoth-windows-1.0.exe] (38.9MB)

== AmigaOS4 ==
* Wesnoth 1.0rc1 for AmigaOS4: http://www.amigasoft.net/downloads/wesnoth.rar (37.7MB)

== License ==
This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org/ Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [http://sourceforge.net/project/showfiles.php?group_id=89495 Previous releases]
* [[WesnothSVN]] - bleeding edge version from SVN

__NOTOC__

FAQ

2005-09-19T19:45:37Z

Ott: /* What are the system requirements? */

=Frequently Asked Questions=

== General ==

===What is Battle for Wesnoth?===
Battle for Wesnoth is a fantasy turn-based strategy game.

===What license is the game distributed under?===
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.

===How to get informed about new releases?===
Subscribe to new releases at [http://freshmeat.net/subscribe/38720/?url=%2Fprojects%2Fwesnoth%2F Freshmeat].

===Why does Wesnoth not have my favorite feature?===
Because we are building this game for ourselves and for our preferences, not for you. If you like the game as we like it - that is good. If you hate the game - that is also fine.
So what is the point of asking for ideas? Because the developers are just common people, although we come up with many ideas, our players certainly do as well, and often ones we don't think of ourselves. If a player comes up with an idea we like - we might implement it. Not because you asked for it - we do it because we like the feature.
At the moment there will be no features added because of the feature freeze in preparation for the release of v1.0. But after the release, there will be many new things again.
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], to build the game that you like. Don't expect us to build that game for you. Building this game is our hobby, not our profession - you did not pay us to make it; rather, we are the ones who have paid for it, in time and labor.

===Do you want help making this game? How can I help?===
Yes we do. Whether you're a programmer, artist, musician, translator, or want to playtest, design levels, or provide ideas, you're welcome to contribute. Spreading the word, joining the [http://savannah.nongnu.org/projects/wesnoth/ development], sharing points of view at the [http://www.wesnoth.org/forum/ forum], discussing with us in [irc://irc.wesnoth.org/wesnoth IRC] (#wesnoth at irc.freenode.net), playing the game and reporting, voting for Wesnoth at different gaming sites...

=== What are the system requirements? ===

We are not completely certain, but an x86 running at 600MHz with 128MB RAM should be adequate. See the [http://www.wesnoth.org/forum/viewtopic.php?t=7384 forum thread] about minimum and recommended system requirements.

=== Post more questions here ===

== Scenario and Campaigns ==

=== Are there any Tools that do help me creating maps and scenarios? ===
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]].

=== I already created a campaign and published it on the campaign server. How can I get translations for the campaign? ===
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]].

=== Post more questions here ===

== Multiplayer ==

===How to find players for multiplayer game?===
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.
You can also join #wesnoth at irc.freenode.net.

===How do I place an object or unit on my map with the map editor?===
You can't. You need to make a multiplayer scenario file. There are more details on the [[BuildingMaps|maps]] page.

=== Post more questions here ===

== Translations ==

=== Post your questions here ===

FAQ

2005-09-19T19:43:42Z

Ott: /* Post more questions here */

=Frequently Asked Questions=

== General ==

===What is Battle for Wesnoth?===
Battle for Wesnoth is a fantasy turn-based strategy game.

===What license is the game distributed under?===
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.

===How to get informed about new releases?===
Subscribe to new releases at [http://freshmeat.net/subscribe/38720/?url=%2Fprojects%2Fwesnoth%2F Freshmeat].

===Why does Wesnoth not have my favorite feature?===
Because we are building this game for ourselves and for our preferences, not for you. If you like the game as we like it - that is good. If you hate the game - that is also fine.
So what is the point of asking for ideas? Because the developers are just common people, although we come up with many ideas, our players certainly do as well, and often ones we don't think of ourselves. If a player comes up with an idea we like - we might implement it. Not because you asked for it - we do it because we like the feature.
At the moment there will be no features added because of the feature freeze in preparation for the release of v1.0. But after the release, there will be many new things again.
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], to build the game that you like. Don't expect us to build that game for you. Building this game is our hobby, not our profession - you did not pay us to make it; rather, we are the ones who have paid for it, in time and labor.

===Do you want help making this game? How can I help?===
Yes we do. Whether you're a programmer, artist, musician, translator, or want to playtest, design levels, or provide ideas, you're welcome to contribute. Spreading the word, joining the [http://savannah.nongnu.org/projects/wesnoth/ development], sharing points of view at the [http://www.wesnoth.org/forum/ forum], discussing with us in [irc://irc.wesnoth.org/wesnoth IRC] (#wesnoth at irc.freenode.net), playing the game and reporting, voting for Wesnoth at different gaming sites...

=== What are the system requirements? ===

We are not completely certain, but an x86 running at 600MHz with 128MB RAM should be adequate. See the [http://www.wesnoth.org/forum/viewtopic.php?t=7500 forum thread] about minimum and recommended system requirements.

=== Post more questions here ===

== Scenario and Campaigns ==

=== Are there any Tools that do help me creating maps and scenarios? ===
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]].

=== I already created a campaign and published it on the campaign server. How can I get translations for the campaign? ===
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]].

=== Post more questions here ===

== Multiplayer ==

===How to find players for multiplayer game?===
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.
You can also join #wesnoth at irc.freenode.net.

===How do I place an object or unit on my map with the map editor?===
You can't. You need to make a multiplayer scenario file. There are more details on the [[BuildingMaps|maps]] page.

=== Post more questions here ===

== Translations ==

=== Post your questions here ===

Credits

2005-09-19T19:00:57Z

Ott:

In July 2003, '''David White''' released the first version of Wesnoth. Since then, many people have joined the project, contributing in very different ways.

== Developers ==
* Alfredo Beaumont (ziberpunk) - autotools
* András Salamon ([[User:Ott|ott]]) - general QA and bug fixing, subediting
* Benjamin Drieu - scenario designer
* Bram Ridder (Morloth) - editor improvements
* Cédric Duval - coder, internationalization manager
* Crossbow/Miyo - administrator, release manager
* David Philippi (Torangan) - internationalization manager, wescamp
* [mailto:davidnwhite_AT_verizon.net David White] (Sirp) - founder, lead developer, scenario designer
* Francisco Muñoz (fmunoz) - artwork manager, original units, scenario designer
* Guillaume Melquiond (silene) -
* Hogne Håskjold (frame) - terrain designer
* [mailto:isaac_AT_sindominio.net Isaac Clerencia] - administrator, release manager
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - internationalization manager
* James Spencer (Shade) - scenario designer
* Jan Zvánovec (jaz) -
* John B. Messerly -
* [mailto:forcemaster_AT_gmx.net Jon Daniel] (forcemstr) -
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) -
* Joseph Simmons (Turin) - scenario designer, graphics
* J.R. Blain (Cowboy) -
* [mailto:mcnabb_AT_gravity.psu.edu J.W.C. McNabb] (Darth Fool) - coder, graphics
* Justin Zaun (jzaun) - coder, scenario designer
* Kristoffer Erlandsson (erl) - help system
* Maksim Orlovich (SadEagle) -
* Mark Michelsen (skovbaer) - internationalization manager
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - several parts of the code, notably terrain graphics code
* Richard Kettering (Jetryl) - artwork coordinator, several graphics
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - internationalization manager
* [mailto:ydirson_AT_altern.org Yann Dirson] - gettext support, tinygui
* Zas -

== Artists ==
* Aleksi - music coordinator
* Alex Jarocha-Ernst (Jormungandr) - portraits
* Andrew James Patterson (Kamahawk) - sprites
* antwerp - sprites
* Christophe Anjard - sprites
* Diego Brea (Cobretti) - sprites
* Eli Dupree (Elvish Pillager) - sprites
* Fredrik Lindroth - music
* Gareth Miller (Gafgarion) - sprites
* James Barton (Sangel) - sprites
* James Woo (Pickslide) - portraits
* Jason Lutes - portraits
* Jimmy Olsson (Azlan) - icons
* Johanna Manninen (lohari) - tiles
* John Muccigrosso (Eponymous Archon) - sprites
* John-Robert Funck (XJaPaN) - sprites
* Jonatan Alamà (tin) - logo
* Joseph Toscano (zhaymusic.com) - music
* J.W. Bjerk (Eleazar) - tiles
* Michael Gil de Muro (grp21) - portraits
* Neorice - sprites
* Pau Congost - music
* Peter Geinitz (Shadow) - sprites
* Slainte - sprites
* Stephen Stone - [graphics]
* Svetac - [graphics]

== Translators ==
* adson - hungarian translation
* İhsan Akın - turkish translation
* Alessio D'Ascanio (otaku) - italian translation
* Alexander Alexiou (Santi) - greek translation
* Alexander Kjäll (capitol) - swedish translation
* Alexandr Menovchicov - russian translation
* Alfredo Beaumont (ziberpunk) - basque translation
* Ambra Viviani Loos - brazilian portuguese translation
* Americo Iacovizzi (DarkAmex) - italian translation
* Anders K. Madsen (madsen) - danish translation
* András Salamon ([[User:Ott|ott]]) - afrikaans, english and hungarian translation
* Andre Schmidt (schmidta) - german translation
* Ankka - finnish translation
* Anton Tsigularov (Atilla) - bulgarian translation
* Arne Deprez - dutch translation
* Artur R. Czechowski - polish translation
* Aurélien Brevers (Breversa) - french translation
* Azamat Hackimov - russian translation
* Bartek Waresiak (Dragonking) - polish translation
* Beer (Eddi) - hungarian translation
* Benoit Astruc - french translation
* Bjarke Sørensen (basher) - danish translation
* Boris Stumm (quijote_) - german translation
* BOrsuk - polish translation
* Cédric Duval - french translation
* Carles Company (brrr) - catalan translation
* Celso Goya - brazilian portuguese translation
* Christoph Berg (chrber) - german translation
* Claus Aranha - brazilian portuguese translation
* crys0000 - italian translation
* Dan Rosàs Garcia (focks) - catalan translation
* Daniel López (Azazelo) - catalan translation
* DaringTremayne - french translation
* David Martínez Moreno - spanish translation
* David Nečas (Yeti) - czech translation
* dentro - hungarian translation
* Enes Akın (yekialem) - turkish translation
* Erik J. Mesoy (Circon) - norwegian translation
* Eugenio Favalli (ElvenProgrammer) - italian translation
* Federico Tomassetti - italian translation
* Flamma - spanish translation
* Franciso Muñoz (fmunoz) - spanish translation
* François Orieux - french translation
* Gabriel Rodríguez (Chewie) - spanish translation
* Georgi Dimitrov (oblak)- bulgarian translation
* Gerfried Fuchs (Alfie) - german translation
* Gilluin - hungarian translation
* Guillaume Duwelz-Rebert - french translation
* Guillaume Massart (Piou2fois) - french translation
* Guillaume Melquiond (silene) - french translation
* Hallvard Norheim Bø (Lysander) - norwegian translation
* Håvard Korsvoll - norwegian translation
* Ilya Kaznacheev - russian translation
* isazi - italian translation
* Jaka Kranjc (lynx) - slovenian translation
* Jan Greve (Jan) - german translation
* Jan-Heiner Laberenz (jan-heiner) - german translation
* Jean Privat (Tout) - french translation
* Jean-Luc Richard (Le Gnome) - french translation
* Jérémy Rosen (Boucman) - french translation
* Jesper Fuglsang Wolff (ulven) - danish translation
* Jonatan Alamà (tin) - catalan translation
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) - catalan translation coordinator
* Jose Gordillo (kilder) - spanish and catalan translation
* Jose Manuel Gomez (joseg) - spanish translation
* Julien Moncel - french translation
* Julien Tailleur - french translation
* Julen Landa (genars) - basque translation
* Kai Ensenbach (Pingu) - german translation
* Kékkői László (BlackEvil) - hungarian translation
* Karol Nowak (grzywacz) - polish translation
* Katerina Sykioti - greek translation
* Kertész Csaba - hungarian translation
* Khiraly - hungarian translation
* kko - finnish translation
* Konstantinos Karasavvas - greek translation
* Kosif - turkish translation
* Kovács Dániel - hungarian translation
* krix - hungarian translation
* Lala - dutch translation
* Leo Danielson (Lugo Moll) - swedish translation
* Lim Choon Kiat - 林俊杰 - chinese translation
* Lukáš Faltýnek - czech translation
* Maarten Albrecht - dutch translation
* Mark Michelsen (skovbaer) - danish translation
* Mark Polo (mpolo) - latin translation
* Mark Recasens - catalan translation
* Mart Tõnso - estonian translation
* Martin Šín - czech translation
* Mathias Bundgaard Svensson (freaken) - danish translation
* Matias Parmala - finnish translation
* methinks - polish translation
* Michał Jedynak (Artanis) - polish translation
* Michel Loos - brazilian portuguese translation
* Mikel Olasagasti (Hey_neken) - basque translation
* Mintaka - czech translation
* Naoki Iimura - japanese translation
* Nico Oliver - afrikaans translation
* Nicolas Boudin (Blurgk) - french translation
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - german translation
* Nobuhito Okada - japanese translation
* Pau Rul·lan Ferragut - catalan translation
* Paweł Stradomski - polish translation
* Paweł Tomak - polish translation
* paxed - finnish translation
* Petr Kopač (Ferda) - czech translation
* Petr Kovár (Juans) - czech translation
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - french translation
* Pieter Vermeylen (Onne) - dutch translation
* Renato Cunha - brazilian portuguese translation
* Roel Thijs (Roel) - dutch translation
* RokStar - italian translation
* Roman Tuchin (Sankt) - russian translation
* Rudolf Orság - czech translation
* Ruben Philipp Wickenhäuser (The Very Uhu) - german translation
* Sérgio de Miranda Costa - brazilian portuguese translation
* Selim Farsakoğlu - turkish translation
* Sofronius - czech translation
* Spiros, Giorgis - greek translation
* Srecko Toroman (FreeCraft) - serbian translation
* Stefan Bergström (tephlon) - swedish translation
* Stephan Grochtmann (Schattenstephan) - german translation
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - swedish translation
* Susanne Mesoy (Rarlgland) - norwegian translation
* Széll Tamás (TomJoad) - hungarian translation
* Tiago Souza (Salvador) - brazilian portuguese translation
* Tobe Deprez - dutch translation
* Vít Komárek - czech translation
* Vít Krčál - czech translation
* Viliam Bur - slovak translation
* wint3r - swedish translation
* [mailto:ydirson_AT_altern.org Yann Dirson] - french translation
* Yuji Matsumoto - japanese translation
* Zas - french translation

== Other Contributions ==
* Bartek Waresiak (Dragonking) - multiplayer balancing
* Ben Anderman (crimson_penguin) - unit list
* Dacyn - scenario designer
* Cyril Bouthors (CyrilB) - debian packager, patron
* Darryl Dixon - packager
* edge - packager
* Francesco Gigli (Jaramir) - wiki, wesnoth.slack.it
* Frédéric Wagner
* Jay Hopping - packager
* Marcin Konicki (ahwayakchih) - BeOS packager
* Marcus Phillips (Sithrandel) - Mac OS X packager
* Mark Michelsen (skovbaer) - slackware packager
* Mike Quinones (Doc Paterson) - multiplayer maps
* Peter Groen (pg) - multiplayer maps
* Richard S. (Noy) - multiplayer balancing
* Ruben Philipp Wickenhäuser (The Very Uhu) - multiplayer maps
* Tom Chance (telex4) - multiplayer maps, scenario balancing

{{Home}}

User:Ott

2005-09-16T16:31:18Z

Ott:

For now, see [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=970 my forum profile].

Some of my Wesnoth forum postings may be worth reading:
* [http://www.wesnoth.org/forum/viewtopic.php?p=91620#91620 Distribution of damage]
* [http://www.wesnoth.org/forum/viewtopic.php?t=5867 Calculating %-to-kill]
* [http://www.wesnoth.org/forum/viewtopic.php?p=78398#78398 Overview of postings about in-game random number generation]
* [http://www.wesnoth.org/forum/viewtopic.php?p=53968#53968 Analysing anomalies in game statistics]
* [http://www.wesnoth.org/forum/viewtopic.php?t=4240 The RATE damage model] (used in-game since 0.8.10)

I'm also responsible for the [[Status of User Scenarios]] page.

Credits

2005-09-13T15:42:26Z

Ott: /* Developers */

In July 2003, '''David White''' released the first version of Wesnoth. Since then, many people have joined the project, contributing in very different ways.

== Developers ==
* Alfredo Beaumont (ziberpunk) - autotools
* Benjamin Drieu - scenario designer
* Bram Ridder (Morloth) - editor improvements
* Cédric Duval - coder, internationalization manager
* Crossbow/Miyo - administrator, release manager
* David Philippi (Torangan) - internationalization manager, wescamp
* [mailto:davidnwhite_AT_verizon.net David White] (Sirp) - founder, lead developer, scenario designer
* Francisco Muñoz (fmunoz) - artwork manager, original units, scenario designer
* Guillaume Melquiond (silene) -
* Hogne Håskjold (frame) - terrain designer
* [mailto:isaac_AT_sindominio.net Isaac Clerencia] - administrator, release manager
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - internationalization manager
* James Spencer (Shade) - scenario designer
* Jan Zvánovec (jaz) -
* John B. Messerly -
* [mailto:forcemaster_AT_gmx.net Jon Daniel] (forcemstr) -
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) -
* Joseph Simmons (Turin) - scenario designer, graphics
* J.R. Blain (Cowboy) -
* [mailto:mcnabb_AT_gravity.psu.edu J.W.C. McNabb] (Darth Fool) - coder, graphics
* Justin Zaun (jzaun) - coder, scenario designer
* Kristoffer Erlandsson (erl) - help system
* Maksim Orlovich (SadEagle) -
* Mark Michelsen (skovbaer) - internationalization manager
* [[User:Ott|ott]] - general QA and bug fixing, subediting
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - several parts of the code, notably terrain graphics code
* Richard Kettering (Jetryl) - artwork coordinator, several graphics
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - internationalization manager
* [mailto:ydirson_AT_altern.org Yann Dirson] - gettext support, tinygui
* Zas -

== Artists ==
* Aleksi - music coordinator
* Alex Jarocha-Ernst (Jormungandr) - portraits
* Andrew James Patterson (Kamahawk) - sprites
* antwerp - sprites
* Christophe Anjard - sprites
* Diego Brea (Cobretti) - sprites
* Eli Dupree (Elvish Pillager) - sprites
* Fredrik Lindroth - music
* Gareth Miller (Gafgarion) - sprites
* James Barton (Sangel) - sprites
* James Woo (Pickslide) - portraits
* Jason Lutes - portraits
* Jimmy Olsson (Azlan) - icons
* Johanna Manninen (lohari) - tiles
* John Muccigrosso (Eponymous Archon) - sprites
* John-Robert Funck (XJaPaN) - sprites
* Jonatan Alamà (tin) - logo
* Joseph Toscano (zhaymusic.com) - music
* J.W. Bjerk (Eleazar) - tiles
* Michael Gil de Muro (grp21) - portraits
* Neorice - sprites
* Pau Congost - music
* Peter Geinitz (Shadow) - sprites
* Slainte - sprites
* Stephen Stone - [graphics]
* Svetac - [graphics]

== Translators ==
* adson - hungarian translation
* İhsan Akın - turkish translation
* Alessio D'Ascanio (otaku) - italian translation
* Alexander Alexiou (Santi) - greek translation
* Alexander Kjäll (capitol) - swedish translation
* Alexandr Menovchicov - russian translation
* Alfredo Beaumont (ziberpunk) - basque translation
* Ambra Viviani Loos - brazilian portuguese translation
* Americo Iacovizzi (DarkAmex) - italian translation
* Anders K. Madsen (madsen) - danish translation
* Andre Schmidt (schmidta) - german translation
* Ankka - finnish translation
* Anton Tsigularov (Atilla) - bulgarian translation
* Arne Deprez - dutch translation
* Artur R. Czechowski - polish translation
* Aurélien Brevers (Breversa) - french translation
* Azamat Hackimov - russian translation
* Bartek Waresiak (Dragonking) - polish translation
* Beer (Eddi) - hungarian translation
* Benoit Astruc - french translation
* Bjarke Sørensen (basher) - danish translation
* Boris Stumm (quijote_) - german translation
* BOrsuk - polish translation
* Cédric Duval - french translation
* Carles Company (brrr) - catalan translation
* Celso Goya - brazilian portuguese translation
* Christoph Berg (chrber) - german translation
* Claus Aranha - brazilian portuguese translation
* crys0000 - italian translation
* Dan Rosàs Garcia (focks) - catalan translation
* Daniel López (Azazelo) - catalan translation
* DaringTremayne - french translation
* David Martínez Moreno - spanish translation
* David Nečas (Yeti) - czech translation
* dentro - hungarian translation
* Enes Akın (yekialem) - turkish translation
* Erik J. Mesoy (Circon) - norwegian translation
* Eugenio Favalli (ElvenProgrammer) - italian translation
* Federico Tomassetti - italian translation
* Flamma - spanish translation
* Franciso Muñoz (fmunoz) - spanish translation
* François Orieux - french translation
* Gabriel Rodríguez (Chewie) - spanish translation
* Georgi Dimitrov (oblak)- bulgarian translation
* Gerfried Fuchs (Alfie) - german translation
* Gilluin - hungarian translation
* Guillaume Duwelz-Rebert - french translation
* Guillaume Massart (Piou2fois) - french translation
* Guillaume Melquiond (silene) - french translation
* Hallvard Norheim Bø (Lysander) - norwegian translation
* Håvard Korsvoll - norwegian translation
* Ilya Kaznacheev - russian translation
* isazi - italian translation
* Jaka Kranjc (lynx) - slovenian translation
* Jan Greve (Jan) - german translation
* Jan-Heiner Laberenz (jan-heiner) - german translation
* Jean Privat (Tout) - french translation
* Jean-Luc Richard (Le Gnome) - french translation
* Jérémy Rosen (Boucman) - french translation
* Jesper Fuglsang Wolff (ulven) - danish translation
* Jonatan Alamà (tin) - catalan translation
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) - catalan translation coordinator
* Jose Gordillo (kilder) - spanish translation
* Jose Manuel Gomez (joseg) - spanish translation
* Julien Moncel - french translation
* Julien Tailleur - french translation
* Julen Landa (genars) - basque translation
* Kai Ensenbach (Pingu) - german translation
* Kékkői László (BlackEvil) - hungarian translation
* Karol Nowak (grzywacz) - polish translation
* Katerina Sykioti - greek translation
* Kertész Csaba - hungarian translation
* Khiraly - hungarian translation
* kko - finnish translation
* Konstantinos Karasavvas - greek translation
* Kosif - turkish translation
* Kovács Dániel - hungarian translation
* krix - hungarian translation
* Lala - dutch translation
* Leo Danielson (Lugo Moll) - swedish translation
* Lim Choon Kiat - 林俊杰 - chinese translation
* Lukáš Faltýnek - czech translation
* Maarten Albrecht - dutch translation
* Mark Michelsen (skovbaer) - danish translation
* Mark Polo (mpolo) - latin translation
* Mark Recasens - catalan translation
* Mart Tõnso - estonian translation
* Martin Šín - czech translation
* Mathias Bundgaard Svensson (freaken) - danish translation
* Matias Parmala - finnish translation
* methinks - polish translation
* Michał Jedynak (Artanis) - polish translation
* Michel Loos - brazilian portuguese translation
* Mikel Olasagasti (Hey_neken) - basque translation
* Mintaka - czech translation
* Naoki Iimura - japanese translation
* Nico Oliver - afrikaans translation
* Nicolas Boudin (Blurgk) - french translation
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - german translation
* Nobuhito Okada - japanese translation
* [[User:Ott|ott]] - afrikaans, english and hungarian translation
* Pau Rul·lan Ferragut - catalan translation
* Paweł Stradomski - polish translation
* Paweł Tomak - polish translation
* paxed - finnish translation
* Petr Kopač (Ferda) - czech translation
* Petr Kovár (Juans) - czech translation
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - french translation
* Pieter Vermeylen (Onne) - dutch translation
* Renato Cunha - brazilian portuguese translation
* Roel Thijs (Roel) - dutch translation
* RokStar - italian translation
* Roman Tuchin (Sankt) - russian translation
* Rudolf Orság - czech translation
* Ruben Philipp Wickenhäuser (The Very Uhu) - german translation
* Sérgio de Miranda Costa - brazilian portuguese translation
* Selim Farsakoğlu - turkish translation
* Sofronius - czech translation
* Spiros, Giorgis - greek translation
* Srecko Toroman (FreeCraft) - serbian translation
* Stefan Bergström (tephlon) - swedish translation
* Stephan Grochtmann (Schattenstephan) - german translation
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - swedish translation
* Susanne Mesoy (Rarlgland) - norwegian translation
* Széll Tamás (TomJoad) - hungarian translation
* Tiago Souza (Salvador) - brazilian portuguese translation
* Tobe Deprez - dutch translation
* Vít Komárek - czech translation
* Vít Krčál - czech translation
* Viliam Bur - slovak translation
* wint3r - swedish translation
* [mailto:ydirson_AT_altern.org Yann Dirson] - french translation
* Yuji Matsumoto - japanese translation
* Zas - french translation

== Other Contributions ==
* Bartek Waresiak (Dragonking) - multiplayer balancing
* Ben Anderman (crimson_penguin) - unit list
* Dacyn - scenario designer
* Cyril Bouthors (CyrilB) - debian packager, patron
* Darryl Dixon - packager
* edge - packager
* Francesco Gigli (Jaramir) - wiki, wesnoth.slack.it
* Frédéric Wagner
* Jay Hopping - packager
* Marcin Konicki (ahwayakchih) - BeOS packager
* Marcus Phillips (Sithrandel) - Mac OS X packager
* Mark Michelsen (skovbaer) - slackware packager
* Mike Quinones (Doc Paterson) - multiplayer maps
* Noy - multiplayer balancing
* Peter Groen (pg) - multiplayer maps
* Ruben Philipp Wickenhäuser (The Very Uhu) - multiplayer maps
* Tom Chance (telex4) - multiplayer maps, scenario balancing

Credits

2005-09-13T14:52:49Z

Ott: /* Translators */

In July 2003, '''David White''' released the first version of Wesnoth. Since then, many people have joined the project, contributing in very different ways.

== Developers ==
* Alfredo Beaumont (ziberpunk) - autotools
* Benjamin Drieu - scenario designer
* Bram Ridder (Morloth) - editor improvements
* Cédric Duval - coder, internationalization manager
* Crossbow/Miyo - administrator, release manager
* David Philippi (Torangan) - internationalization manager, wescamp
* [mailto:davidnwhite_AT_verizon.net David White] (Sirp) - founder, lead developer, scenario designer
* Francisco Muñoz (fmunoz) - artwork manager, original units, scenario designer
* Guillaume Melquiond (silene) -
* Hogne Håskjold (frame) - terrain designer
* [mailto:isaac_AT_sindominio.net Isaac Clerencia] - administrator, release manager
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - internationalization manager
* James Spencer (Shade) - scenario designer
* Jan Zvánovec (jaz) -
* John B. Messerly -
* [mailto:forcemaster_AT_gmx.net Jon Daniel] (forcemstr) -
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) -
* Joseph Simmons (Turin) - scenario designer, graphics
* J.R. Blain (Cowboy) -
* [mailto:mcnabb_AT_gravity.psu.edu J.W.C. McNabb] (Darth Fool) - coder, graphics
* Justin Zaun (jzaun) - coder, scenario designer
* Kristoffer Erlandsson (erl) - help system
* Maksim Orlovich (SadEagle) -
* Mark Michelsen (skovbaer) - internationalization manager
* [[User:Ott|ott]]
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - several parts of the code, notably terrain graphics code
* Richard Kettering (Jetryl) - artwork coordinator, several graphics
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - internationalization manager
* [mailto:ydirson_AT_altern.org Yann Dirson] - gettext support, tinygui
* Zas -

== Artists ==
* Aleksi - music coordinator
* Alex Jarocha-Ernst (Jormungandr) - portraits
* Andrew James Patterson (Kamahawk) - sprites
* antwerp - sprites
* Christophe Anjard - sprites
* Diego Brea (Cobretti) - sprites
* Eli Dupree (Elvish Pillager) - sprites
* Fredrik Lindroth - music
* Gareth Miller (Gafgarion) - sprites
* James Barton (Sangel) - sprites
* James Woo (Pickslide) - portraits
* Jason Lutes - portraits
* Jimmy Olsson (Azlan) - icons
* Johanna Manninen (lohari) - tiles
* John Muccigrosso (Eponymous Archon) - sprites
* John-Robert Funck (XJaPaN) - sprites
* Jonatan Alamà (tin) - logo
* Joseph Toscano (zhaymusic.com) - music
* J.W. Bjerk (Eleazar) - tiles
* Michael Gil de Muro (grp21) - portraits
* Neorice - sprites
* Pau Congost - music
* Peter Geinitz (Shadow) - sprites
* Slainte - sprites
* Stephen Stone - [graphics]
* Svetac - [graphics]

== Translators ==
* adson - hungarian translation
* İhsan Akın - turkish translation
* Alessio D'Ascanio (otaku) - italian translation
* Alexander Alexiou (Santi) - greek translation
* Alexander Kjäll (capitol) - swedish translation
* Alexandr Menovchicov - russian translation
* Alfredo Beaumont (ziberpunk) - basque translation
* Ambra Viviani Loos - brazilian portuguese translation
* Americo Iacovizzi (DarkAmex) - italian translation
* Anders K. Madsen (madsen) - danish translation
* Andre Schmidt (schmidta) - german translation
* Ankka - finnish translation
* Anton Tsigularov (Atilla) - bulgarian translation
* Arne Deprez - dutch translation
* Artur R. Czechowski - polish translation
* Aurélien Brevers (Breversa) - french translation
* Azamat Hackimov - russian translation
* Bartek Waresiak (Dragonking) - polish translation
* Beer (Eddi) - hungarian translation
* Benoit Astruc - french translation
* Bjarke Sørensen (basher) - danish translation
* Boris Stumm (quijote_) - german translation
* BOrsuk - polish translation
* Cédric Duval - french translation
* Carles Company (brrr) - catalan translation
* Celso Goya - brazilian portuguese translation
* Christoph Berg (chrber) - german translation
* Claus Aranha - brazilian portuguese translation
* crys0000 - italian translation
* Dan Rosàs Garcia (focks) - catalan translation
* Daniel López (Azazelo) - catalan translation
* DaringTremayne - french translation
* David Martínez Moreno - spanish translation
* David Nečas (Yeti) - czech translation
* dentro - hungarian translation
* Enes Akın (yekialem) - turkish translation
* Erik J. Mesoy (Circon) - norwegian translation
* Eugenio Favalli (ElvenProgrammer) - italian translation
* Federico Tomassetti - italian translation
* Flamma - spanish translation
* Franciso Muñoz (fmunoz) - spanish translation
* François Orieux - french translation
* Gabriel Rodríguez (Chewie) - spanish translation
* Georgi Dimitrov (oblak)- bulgarian translation
* Gerfried Fuchs (Alfie) - german translation
* Gilluin - hungarian translation
* Guillaume Duwelz-Rebert - french translation
* Guillaume Massart (Piou2fois) - french translation
* Guillaume Melquiond (silene) - french translation
* Hallvard Norheim Bø (Lysander) - norwegian translation
* Håvard Korsvoll - norwegian translation
* Ilya Kaznacheev - russian translation
* isazi - italian translation
* Jaka Kranjc (lynx) - slovenian translation
* Jan Greve (Jan) - german translation
* Jan-Heiner Laberenz (jan-heiner) - german translation
* Jean Privat (Tout) - french translation
* Jean-Luc Richard (Le Gnome) - french translation
* Jérémy Rosen (Boucman) - french translation
* Jesper Fuglsang Wolff (ulven) - danish translation
* Jonatan Alamà (tin) - catalan translation
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin) - catalan translation coordinator
* Jose Gordillo (kilder) - spanish translation
* Jose Manuel Gomez (joseg) - spanish translation
* Julien Moncel - french translation
* Julien Tailleur - french translation
* Julen Landa (genars) - basque translation
* Kai Ensenbach (Pingu) - german translation
* Kékkői László (BlackEvil) - hungarian translation
* Karol Nowak (grzywacz) - polish translation
* Katerina Sykioti - greek translation
* Kertész Csaba - hungarian translation
* Khiraly - hungarian translation
* kko - finnish translation
* Konstantinos Karasavvas - greek translation
* Kosif - turkish translation
* Kovács Dániel - hungarian translation
* krix - hungarian translation
* Lala - dutch translation
* Leo Danielson (Lugo Moll) - swedish translation
* Lim Choon Kiat - 林俊杰 - chinese translation
* Lukáš Faltýnek - czech translation
* Maarten Albrecht - dutch translation
* Mark Michelsen (skovbaer) - danish translation
* Mark Polo (mpolo) - latin translation
* Mark Recasens - catalan translation
* Mart Tõnso - estonian translation
* Martin Šín - czech translation
* Mathias Bundgaard Svensson (freaken) - danish translation
* Matias Parmala - finnish translation
* methinks - polish translation
* Michał Jedynak (Artanis) - polish translation
* Michel Loos - brazilian portuguese translation
* Mikel Olasagasti (Hey_neken) - basque translation
* Mintaka - czech translation
* Naoki Iimura - japanese translation
* Nico Oliver - afrikaans translation
* Nicolas Boudin (Blurgk) - french translation
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - german translation
* Nobuhito Okada - japanese translation
* [[User:Ott|ott]] - afrikaans, english and hungarian translation
* Pau Rul·lan Ferragut - catalan translation
* Paweł Stradomski - polish translation
* Paweł Tomak - polish translation
* paxed - finnish translation
* Petr Kopač (Ferda) - czech translation
* Petr Kovár (Juans) - czech translation
* [mailto:philippe.plantier_AT_naema.org Philippe Plantier] ([[User:Ayin|Ayin]]) - french translation
* Pieter Vermeylen (Onne) - dutch translation
* Renato Cunha - brazilian portuguese translation
* Roel Thijs (Roel) - dutch translation
* RokStar - italian translation
* Roman Tuchin (Sankt) - russian translation
* Rudolf Orság - czech translation
* Ruben Philipp Wickenhäuser (The Very Uhu) - german translation
* Sérgio de Miranda Costa - brazilian portuguese translation
* Selim Farsakoğlu - turkish translation
* Sofronius - czech translation
* Spiros, Giorgis - greek translation
* Srecko Toroman (FreeCraft) - serbian translation
* Stefan Bergström (tephlon) - swedish translation
* Stephan Grochtmann (Schattenstephan) - german translation
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - swedish translation
* Susanne Mesoy (Rarlgland) - norwegian translation
* Széll Tamás (TomJoad) - hungarian translation
* Tiago Souza (Salvador) - brazilian portuguese translation
* Tobe Deprez - dutch translation
* Vít Komárek - czech translation
* Vít Krčál - czech translation
* Viliam Bur - slovak translation
* wint3r - swedish translation
* [mailto:ydirson_AT_altern.org Yann Dirson] - french translation
* Yuji Matsumoto - japanese translation
* Zas - french translation

== Other Contributions ==
* Bartek Waresiak (Dragonking) - multiplayer balancing
* Ben Anderman (crimson_penguin) - unit list
* Dacyn - scenario designer
* Cyril Bouthors (CyrilB) - debian packager, patron
* Darryl Dixon - packager
* edge - packager
* Francesco Gigli (Jaramir) - wiki, wesnoth.slack.it
* Frédéric Wagner
* Jay Hopping - packager
* Marcin Konicki (ahwayakchih) - BeOS packager
* Marcus Phillips (Sithrandel) - Mac OS X packager
* Mark Michelsen (skovbaer) - slackware packager
* Mike Quinones (Doc Paterson) - multiplayer maps
* Noy - multiplayer balancing
* Peter Groen (pg) - multiplayer maps
* Ruben Philipp Wickenhäuser (The Very Uhu) - multiplayer maps
* Tom Chance (telex4) - multiplayer maps, scenario balancing