The Battle for Wesnoth Wiki - User contributions [en]

User:Xan

2010-07-16T21:48:23Z

Xan:

===Planned:===
*Take over the world after everyone else.

===Completed:===
*[http://arcune.org/files/wesnoth/update.cpp Unit WML Updater]

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

SummerOfCodeIdeas

2008-03-27T00:33:09Z

Xan: /* Multiplayer Server */

This is a compilation of ideas from ML. Needs to be refined (more detailed description, deliverables, workload estimation?):

== I want to be one of your Google Summer of Code students, what should I do... ==

Here is a quick list of things to do to get you started
* Create an account on gna.org
* Create an account on the wesnoth forum
* Join the irc channel (#wesnoth-dev on irc.freenode.net) and introduce yourself. We will not give formal interviews, but we will clearly favor people we have learnt to know during the selection process
* Contact one of our SummerOfCode people (Ivanovic, Sirp, Boucman, Mordante) to have your forum nick marked as a Summer of code student

* Start a wiki page about your idea, add a link on the bottom of this page and add this information on it:
** List your account names (gna, forum, irc nick) so that we can recognize you
** Fill the questionnaire on this page: [[SoC_Information_for_Google#Does_your_organization_have_an_application_template_you_would_like_to_see_students_use.3F_If_so.2C_please_provide_it_now.| List of questions to answer]]
** Detail your idea as much as possible, look at other students pages, and please give milestones and studies you've done

* Though not mandatory, it is highly advisable to go to the [[EasyCoding]] and [[NotSoEasyCoding]] pages and implement one of these ideas (or any idea of similar scope) so we have an idea how you work. Be sure to use your gna account when submitting these patches so we know who it is coming from. You can also implement some features from our feature request database at gna. When you implement something, also list it on your own page with a reference to the patch.

* Once you have everything done here and think your idea is okay, go to [http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants to page at google] to submit your application. You have to submit it before '''Monday, March 31, 2008''' or you have no chance to get in!

== List of Ideas for the Project (Suggestions from the wesnoth developers) ==

Here is only a short description of possible Ideas we have, each has a page of its own with a more detailed version on it.

=== Writing an AI based on the formula AI ===

Wesnoth has always had a simple C++ based AI. David (our lead developer) has been working on a simple language to write AI in Wesnoth: [[FormulaAI]]

The Wesnoth AI is used as an opponent in most campaigns, and as such is an important piece of code for the Wesnoth project. Unfortunately, because the skills required to understand and modify it are rather arcane, it is also one of the most neglected parts of the Wesnoth code. This is a place where a lot of research and useful work could be done. But keep in mind that [[WhyWritingAWesnothAIIsHard|writing an AI for Wesnoth is difficult]].

[[SoC Ideas FormulaAI]] - Full version of the idea, with detailed information

=== Extending the Multiplayer server ===

Our multiplayer community is generally strong and healthy, but we believe its growth is limited by some problems in the interface of the multiplayer lobby.

[[SoC Ideas Multiplayer server]] - Full version of the idea, with detailed information

=== Scenario/Campaign editor ===

Currently, in order to create campaign or multiplayer scenarios, it is necessary to manually edit WML files - XML-like configuration files. The goal of this project would be to create a graphical editor to make the creative process easier.

[[SoC Ideas Scenario and Campaign Editor]] - Full version of the idea, with detailed information

=== Addon server ===
Wesnoth has an addon server which offers users to upload user
made content (UMC). This allows all other users of Wesnoth
to easily download and install this content. The server was
originally written for user-made campaigns but contains a lot
more types of addons nowadays. Both the server side and the
client side need to be improved.

[[SoC Ideas Addon Server]] - Full version of the idea, with detailed information

=== Map editor ===
The map editor in Wesnoth serves two goals, making it easy to create
a new map and helping the terrain artists to test their new terrains.

[[SoC_Ideas_Map_Editor]] - Full version of the idea, with detailed information

=== Other possible ideas to be fleshed out ===
A MapGenerator rewrite - better scalable for outdoor maps, plus the possibility to define areas (similar to the caverns in the cave generator) etc.

=== Make your own ideas ===
If you have your own idea the best thing is to join IRC wesnoth-dev at irc.freenode.net and discuss the idea with the developers there. If the developers think your idea is interesting and like the feature you can start to turn it into a full proposal. Once done discuss it again on IRC so the developers can accept your idea.

== Information about our Project ==
The information we provided google with about our project can be looked up at the site [[SoC Information for Google]].

Also see the [[DeveloperResources]] link (from the [[Project]] page).

== People to bug on IRC ==
We have prepared a list of people with their "area of competence". This is to give you an idea on which areas those people can be of help for you. Of course you should always just ask in the IRC chan, but those are the most likely ones to answer questions in the respective area. And here is the list:

[[SoC People to bug on IRC]]

== GSoC Student Applicant Ideas ==

Every student interested to work on Wesnoth as part of Summer of Code should create a page of his own where several things should be listed. Here is a short list of what should be mentioned on the list (the more info for us, the better...):

* Who are you? Please list your IRC and forum nickname in here and describe yourself so that we get you to know.
* What do you want to work on? Please flesh out your personal ideas, so that we get to know what you plan to work on.
* If you already submitted patches, please list those so that we have a reference.

===[[SoC Ideas FormulaAI|Formula AI]]===
====[[FormulaAIandAdaptation]] (Alesis-Novik) ====
The new idea and aproach using strategic and inside game knowledge

==== [[FormulaAIandDynamicScripting]] (barbarianhero) ====
This project idea uses Formula AI and Dynamic Scripting to create a tunable and adaptive AI.

====[[FormulaAIBaseAI]] (Dragonking) ====
Developing smart and pluggable AI, which would be really easy tweakable by Scenario and Campaign Developers

====[[Building A Strategic Planner with Formula AI|FormulaAIPlanner]] (TVincent) ====
This project idea uses (and maybe extends) Formula AI to create a strategic, responsive AI of the Planner model.

===[[SoC Ideas Multiplayer server|Multiplayer Server]]===
====[[ExtendingMultiplayerServer]] (dudegaurav) ====
This project proposal incorporates several ideas on how to refine the current Multiplayer Server !
====[[MultiplayerServerLobbyInterface]] (Xan) ====
Improving the Multiplayer Lobby, with an emphasis on simplicity, ease-of-use, and scalability

===[[SoC Ideas Scenario and Campaign Editor|Scenario/Campaign Editor]]===
====[[ExtensibleScenarioEditor]] (david.hilton) ====
On a conceptual level, this idea combines a finite state machine editor with a code generator to create scenarios.

====[[pyQTScenarioEditor]] (Malle) ====
That's me!

====[[RujasuScenarioEditor]] (rujasu) ====
Scenario editor that will coordinate with the look and feel of the Wesnoth game.

====[[CampaignEditor]] (jkiv) ====

Click and drag! CLICK! AND! DRAG!

===[[SoC Ideas Addon Server|Addon Server]]===
====[[AddonServerSocial]] (lao) ====
Improving addon Server/Client by adding some social content.

====[[AddonServer]] (giebfried) ====
This project is to improve the server and client sides of the addon server, as suggested above.

===[[SoC Ideas Map Editor|Map Editor]]===
====[[EvolutionaryMapEditor]] (xonev) ====
An evolutionary approach to improving the map editor.

====[[VimzardMapEditor]] (vimzard) ====
A better random map generator, some essential features and a tie-in with the Scenario Editor.

====[[NewMapEditor]] (Cecen) ====
This is basically a rewrite of the current map editor with various added features and tweaks to both increase the versatility of the editor and make it easier for the user to create maps with.

====[[MapEditorRewrite]] (dlr365)====
A rewrite of the map editor, then taking it in the direction of a combined map/scenario editor for both quick scenarios and more complex ones.

===Map Generator===
====[[RandomCampaignGenerator]] (kartik thakore, refining idea) ====
Procedural map generation that will hope to give writers better control over the random map generator using an interface.

===Other===
====[[WesnothStatistics]] (radx) ====
Project related to Wesnoth statistics (campaign) submission, gathering and presentation.

[[Category:Summer of Code|*]]

MultiplayerServerLobbyInterface

2008-03-27T00:30:49Z

Xan: New page: == Introduction == *Basics **My name is Dominic Bolin and I was born in and reside in the US. I am currently 19 years old, and interested in learning most theoretical and applied science...

== Introduction ==

*Basics
**My name is Dominic Bolin and I was born in and reside in the US. I am currently 19 years old, and interested in learning most theoretical and applied sciences, especially programming, computer science, and artificial intelligence. I am now in my second year of studying Liberal Arts at Thomas Aquinas College, California. I first learned to program with the help of and by working with my older brothers, three of whom have done programming, both individually and for groups, and one who is a professional programmer with more than ten years of experience. I am interested in participating in the Google Summer of Code program in order to continue learning over the summer and to contribute to the Battle of Wesnoth, as well as to interact with the Wesnoth community, which in my experience has been very enjoyable, and to earn some money. You can contact me either on the forum or IRC, where my nick is Xan, or by email to dbolin_D0T_m_ATT_gmail_D0T_com.

*Experience
**What programs/software have you worked on before?
***I have previously worked on the Battle for Wesnoth, and also many other projects, such as a Latin flashcards program, and a program for viewing and altering 3D geometrical figures.
**Have you developed software in a team environment before? (As opposed to hacking on something on your own)
***I have both developed software with my brothers, and with small groups of other people, as well as the Battle for Wesnoth group.
**Have you participated in the Google Summer of Code before? As a mentor or a student? In what project? Were you successful? If not, why?
***This is my first application to the Google Summer of Code.
**What development model would you use (e.g. keywords: V-model, XP programming, agile programming, iterative; with the help of prototyping, formal specifications, tests, etc.).
***I prefer extreme programming with an iterative style.

*Open Source
**Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.
***I have done some work for the Battle for Wesnoth already, for example, bug fixes and error checking, some performance improvements and profiling, and improvements to the MP server and numerous extensions to WML.

*Gaming experience
**Are you a gamer?
***Yes. I prefer games which emphasize strategic and tactical thinking, as well as puzzles and thing which similarly require deep thought.
**What type of opponents do you prefer?
***I prefer to play against human opponents rather than against AI, though I do enjoy finding the patterns to the movements and reactions of the AI, in order to play against them more efficiently.
**Are you more interested in story or gameplay?
***I am more interested in gameplay than in the story, though I have to like the story in order to play a single player game, and have only played the mainline campaign of BfW and a couple others.
**Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.
***I have played Wesnoth since version 0.93, mostly multiplayer games because I enjoy playing with people much more than by myself, and because the strategies used are much more varied.

*Communication skills
**Though most of our developers are not native English speakers, English is the project's working language. Describe your fluency level in written English.
***I have an above average proficiency in written English, and am able to express my thoughts in a variety of ways.
**Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.
***As far as I know, I’ve never had any problems with other players or developers of Wesnoth, and I try to ensure that I understand others’ positions before critiquing or making assertions concerning them. I have also played online a lot, and usually have no problems cooperating with other players.
**Do you give constructive advice?
***Before even giving advice, I try to be sure that I fully understand the other person’s position, and when I do give advice, make sure that I am not misunderstood and give the reasons behind my thinking. In my experience, most advice/criticisms I have given have been received well and to the improvement of the other.
**Do you receive advice well?
***I always am willing to receive advice from others with experience in the field in question, and if I am wrong about a particular point, I like to be shown that so that I can avoid making the same mistake in the future.
**Are you good at sorting useful criticisms from useless ones?
***I believe I am very good at distinguishing useful criticism from useless: there are always reasons for things, and even when the critic does not state the reason for his opinion, usually I can see what he is thinking, and how it applies (if at all) to the subject.

*Project
**Did you select a project from our list? If that is the case, what project did you select?
***I chose to improve the interface of the multiplayer lobby.
**Why did you choose this project?
***The MP lobby has always seemed to me to be one of the less polished points of the game, and somewhat clumsy and difficult to use. I would like to rework the lobby, both to extend its capabilities and to apply to it the principle behind the whole development of Wesnoth: simplicity and ease-of-use.
**Include an estimated timeline for your work on the project
***The milestones proposed by me are [[#Milestones|listed below]]. Since I already have some experience with the multiplayer side of Wesnoth, I will relatively quickly be able to propose particular improvements both in general and a particular implementation, and since I have some experience with the code itself, after a solution is decided upon, I will be able to begin coding it almost immediately.
**Include as much technical detail about your implementation as you can
***At this point, I have no concrete implementation in mind for any of the improvements that might be made.
**What do you expect to gain from this project?
***Additional experience in C++, networking, and user interface design.
**What would make you stay in the Wesnoth community after the conclusion of SOC?
***I have already worked for the Wesnoth community before in various ways, and although now I am very busy throughout the school year, I do have some time free in the summer to contribute and help out with Wesnoth development.

*Practical considerations
**Are you familiar with any of the following tools?
***Subversion
****Yes, about 3 years of experience.
***C++
****I have more than 3 years of C/C++ experience.
***Python
****I have occasionally worked with python when it happens to be involved in the projects I have worked on .
**Which tools do you normally use for development? Why do you use them?
***I normally develop on Windows, using Dev-c++ , Code::Blocks, or Visual Studio.
**What programming languages are you fluent in?
***C/C++, Lua, BASIC, Euphoria.
**What spoken languages are you fluent in?
*** English.
**At what hours are you awake (please specify in UTC)
***Usually I'm awake between 15 and 8 UTC, and will be available on IRC between about 3 and 7 UTC.
**Would you mind talking with your mentor on telephone / internet phone?
***I would not mind.

== Idea Description ==

=== Required knowledge and talent ===

*A fair amount of experience with C++ is required, since Wesnoth uses some advanced C++ features and is based on BOOST and SDL: I believe I have sufficient experience of C++ in general, as well as a good understanding of the Wesnoth code itself, as I have done considerable work with it previously.
*Experience with multiplayer games, in order to have a good idea of what multiplayer lobbies of other games look like, and a good idea of the social behaviors of MP communities: I have played many different games online, some with similar numbers of players to Wesnoth, and others with greater numbers, and have a good idea of what players like and dislike with respect to the interface and usability.

=== Milestones ===

*Determining the changes to made to the lobby which must be agreed to by most if not all the developers. This will be done by talking to various players and developers about their own opinions on the current state of the lobby and the changes they would like to see, taking into account practical considerations and future scalability, as well as comparison to other multiplayer lobbies/communities.

*Deciding upon a particular implementation for each of the proposed changes. Again, each of these must be agreed to by the developers. The implementations will be focused on simplicity, ease-of-use, and functionality.

*Actual code for each change; this is likely to be the bulk of the work to be done, so as particular changes to the lobby are decided upon, multiple milestones may be added for different stages of the improvement of the lobby.

[[Category:Summer of Code]]

User:Xan

2007-06-29T19:44:56Z

Xan: /* Work In Progress: */

==Work In Progress:==
*Factions
** Frost Elves
** Faction X
*Spacenoth

===Planned:===
*Releasing the first version of [http://arcune.org/forum/index.php Spacenoth]
*Take over the world after everyone else.

===Completed:===
*[http://arcune.org/files/wesnoth/update.cpp Unit WML Updater]

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

List & description of [[Developers]]

User:Xan

2007-06-29T19:44:32Z

Xan:

==Work In Progress:==
*WML Enhancement
** Unit WML
*Factions
** Frost Elves
** Faction X
*Spacenoth

===Planned:===
*Releasing the first version of [http://arcune.org/forum/index.php Spacenoth]
*Take over the world after everyone else.

===Completed:===
*[http://arcune.org/files/wesnoth/update.cpp Unit WML Updater]

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

List & description of [[Developers]]

User:Xan

2007-06-29T19:44:17Z

Xan:

StartingPoints

2006-08-14T14:24:22Z

Xan: Reverted edit of Liuhecai, changed back to last version by NeoPhile

__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?movetypes Movement, defense and resistance tables]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
** [[Complete_Faction_List_%28unfinished%29]] - list all user made factions
* [[WesnothAcronyms|Wesnoth Acronyms (by category)]] - common wesnothian acronyms explained
* [[WesnothAcronyms(alphabetic)|Wesnoth Acronyms (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 single player campaigns
* [[MultiplayerCampaigns]] - how to make your own multiplayer campaigns
* [[BuildingScenarios]] - how to make your own scenarios
* [[BuildingUnits]] - how to make your own units
* [[UnitAnalysis]] - tool to analyze units
* [[WesnothMapEditor]] - summary of controls
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[Create_Art#Art_Tutorials|Art Tutorials]] - help in creating art
* [[GraphicLibrary]] - unit and terrain images posted on the forums
* [[Tiles_Status]] - terrain tiles: proposed and in progress.

== Improving the Game ==
* [[ReportingBugs]] - use Gna
* To submit a feature request, use http://bugs.wesnoth.org
* [[FrequentlyProposedIdeas]] - before you propose an idea, check here!
==== 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

== 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].
* [[Trailer]] - the Wesnoth trailer

== 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]

== About this Wiki ==
* [[Help:Editing|Editing]] - learn how to edit pages
* [[Sandbox]] - experiment with the wiki
* [[WikiMigration]] - we were looking for a replacement for our old wiki (and ended up using Mediawiki)

User:Xan

2006-08-04T21:42:28Z

Xan: /* Work In Progress: */

==Work In Progress:==
*WML Enhancement
** Unit WML
*Factions
** Frost Elves
** Faction X
*Spacenoth

===Planned:===
*Releasing the first version of [http://arcune.org/forum/index.php Spacenoth]
*Take over the world after everyone else.

===Completed:===
*[http://arcune.org/files/wesnoth/update.cpp Unit WML Updater]

== See Also == [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=101476 Xan's forum profile]
List & description of [[Developers]]

Download

2006-07-27T18:13:36Z

Xan: /* Mac OS X */

Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here.

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. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.0.x_branch.29|Stable Branch]] | [[Download#Development|Development Branch]]

== Stable (1.0.x branch) ==
The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.0.x branch is compatible to each other. This will not happen in the development branch.

Version 1.0.2 is the latest stable version, updated with several important bugfixes. This version is recommended for most players since the 1.0.x online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Source code ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.2.tar.gz?download Current stable version] (1.0.2, 38.2 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== [[BeOS]] ====
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0.2-BeOS-x86.pkg.zip?download Current stable version] (1.0.2, 42.3MB)

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

==== Mac OS X ====
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.0.2.dmg?download Current stable version] (1.0.2, PPC, 53.6 MB)
* [http://lwa.retiaire.org/wesnoth/Wesnoth_MacOSX_1.0.2-lwa.dmg Current stable version - alternate] (1.0.2, PPC, 44MB)
* [http://lwa.retiaire.org/wesnoth/Wesnoth_MacOSX_1.0.2_lite-lwa.dmg Current stable version - lite] (1.0.2, PPC, no art or music, 25MB)

==== MS Windows ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-windows-1.0.2.exe?download Current stable version] (1.0.2, 37.0MB)

==== FreeBSD ====
* /usr/ports/games/wesnoth (1.0.1, 37.3MB)

==== Miscellaneous ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.2.tar.gz.md5?download Source code md5sum]
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0.2-BeOS-x86.pkg.zip.md5?download BeOS md5sum]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code Xdelta for the source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#MS_Windows Xdelta for the Windows binary]

== Development ==
Version 1.1.8 is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.0.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth.

==== Source code ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.8.tar.gz?download Current Version] (1.1.8, 70 MB)
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.7.tar.gz?download Previous Version] (1.1.7, 70 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.8_windows.exe?download Current Version] (1.1.8, 58.7 MB)
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.7-windows.exe?download Previous Version] (1.1.7, 58.1 MB)

==== Mac OS X ====
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.8.dmg?download Current Version] (1.1.8, Universal, 73.2MB)
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.8_lite.dmg?download Current version - lite] (1.1.8, Universal, no art or music, 43.3MB)
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.7.dmg?download Previous Version] (1.1.7, Universal, 69MB)
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.7_lite.dmg?download Previous version - lite] (1.1.7, Universal, no art or music, 39MB)

==== GNU/Linux ====
* 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 the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== AmigaOS4 ====
* [http://www.amigasoft.net/downloads/Wesnoth.lzh Current Version] (1.1.7, 79MB)

==== OS/2 & eComStation ====
* [http://www.os2world.com/smedley/wesnoth-1.1.7-os2.zip Current Version] (1.1.7, 71MB)

==== Miscellaneous ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.5.tar.gz.md5?download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code Xdelta for the source code]
* [http://sourceforge.net/project/showfiles.php?group_id=89495 SourceForge page for current and all previous versions]

== 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]]
* [[WesnothSVN]] - bleeding edge version from SVN

Download

2006-07-27T18:11:44Z

Xan: /* Development */

Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here.

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. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.0.x_branch.29|Stable Branch]] | [[Download#Development|Development Branch]]

== Stable (1.0.x branch) ==
The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.0.x branch is compatible to each other. This will not happen in the development branch.

Version 1.0.2 is the latest stable version, updated with several important bugfixes. This version is recommended for most players since the 1.0.x online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Source code ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.2.tar.gz?download Current stable version] (1.0.2, 38.2 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== [[BeOS]] ====
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0.2-BeOS-x86.pkg.zip?download Current stable version] (1.0.2, 42.3MB)

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

==== Mac OS X ====
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.0.2.dmg?download Current stable version] (1.0.2, PPC, 53.6 MB)
* [http://lwa.retiaire.org/wesnoth/Wesnoth_MacOSX_1.0.2-lwa.dmg Current stable version - alternate] (1.0.2, PPC, 44MB)
* [http://lwa.retiaire.org/wesnoth/Wesnoth_MacOSX_1.0.2_lite-lwa.dmg Current stable version - lite] (1.0.2, PPC, no art or music, 25MB)

==== MS Windows ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-windows-1.0.2.exe?download Current stable version] (1.0.2, 37.0MB)

==== FreeBSD ====
* /usr/ports/games/wesnoth (1.0.1, 37.3MB)

==== Miscellaneous ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.2.tar.gz.md5?download Source code md5sum]
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0.2-BeOS-x86.pkg.zip.md5?download BeOS md5sum]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code Xdelta for the source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#MS_Windows Xdelta for the Windows binary]

== Development ==
Version 1.1.8 is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.0.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth.

==== Source code ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.8.tar.gz?download Current Version] (1.1.8, 70 MB)
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.7.tar.gz?download Previous Version] (1.1.7, 70 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.8_windows.exe?download Current Version] (1.1.8, 58.7 MB)
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.7-windows.exe?download Previous Version] (1.1.7, 58.1 MB)

==== Mac OS X ====
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.7.dmg?download Current Version] (1.1.7, Universal, 69MB)
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.7_lite.dmg?download Current version - lite] (1.1.7, Universal, no art or music, 39MB)
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.5.dmg?download Previous Version] (1.1.5, Universal, 69.4MB)
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.5_lite.dmg?download Previous version - lite] (1.1.5, Universal, no art or music, 39.4MB)

==== GNU/Linux ====
* 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 the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== AmigaOS4 ====
* [http://www.amigasoft.net/downloads/Wesnoth.lzh Current Version] (1.1.7, 79MB)

==== OS/2 & eComStation ====
* [http://www.os2world.com/smedley/wesnoth-1.1.7-os2.zip Current Version] (1.1.7, 71MB)

==== Miscellaneous ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.5.tar.gz.md5?download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code Xdelta for the source code]
* [http://sourceforge.net/project/showfiles.php?group_id=89495 SourceForge page for current and all previous versions]

== 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]]
* [[WesnothSVN]] - bleeding edge version from SVN

GettingStarted

2006-07-17T13:49:16Z

Xan: Reverted edit of Nightmare, changed back to last version by Xan

{| style="float:right;"
|
__TOC__
|}
The Battle for Wesnoth is a turn-based strategy game with a fantasy theme.

''Build up a great army'', gradually turning raw recruits into hardened veterans. In later games, recall your toughest warriors and form a deadly host against whom none can stand! Choose units from a large pool of specialists, and hand-pick a force with the right strengths to fight well on different terrains against all manner of opposition.

Fight to regain the throne of Wesnoth, of which you are the legitimate heir, or use your dread power over the Undead to dominate the land of mortals, or lead your glorious Orcish tribe to victory against the humans who dared despoil your lands … Wesnoth has many different sagas waiting to be played out. You can create your own custom units, and write your own scenarios – or even full-blown campaigns. You can also challenge your friends – or strangers – and fight in epic ''multi-player'' fantasy battles.

=== Welcome to Wesnoth ===
==== The Land of Wesnoth ====
The Land of Wesnoth is generally divided into three areas: the northlands, which are generally lawless; the kingdom of Wesnoth and its occasional principality, Elensfar; and the domain of the Southwest elves.

The Kingdom of Wesnoth lies in the center of the land. Its borders are the Great River to the north, the Lower Hills in the east and south, the Green Swamp to the southwest, and the Ocean to the west. Elensefar, that sometime province of Wesnoth, is bordered by the Great River to the north, a loosely defined line with Wesnoth to the east, the Bay of Pearls to the south, and the ocean to the west. There is no government of the Northlands. Various groups of orcs, dwarves, barbarian men and even elves populate the region. The northern and eastern borders are not defined, the southern border is the Great River, and the western border is the Ocean.

As you travel around the land you will encounter peaceful villages where you can heal your troops and obtain a good income to support your army. You will also have to cross mountains and rivers, either on foot or mounted, push through forests, hills and tundra, or brazenly cross open grassland. In each of these areas different creatures have adapted to live there and can travel more easily and fight better when they are in familiar terrain. In the hills, mountains and underground caves orcs and dwarves are most at home. In the forests the elves reign supreme while in the oceans and rivers mermen and nagas control the waves.

==== The Creatures of Wesnoth ====

The world of Wesnoth contains several races that have joined forces into different factions. Here, Elf and Dwarf fight side by side against Orc and Human. In most campaigns, you will mostly control units from one faction, but often you will have a recruit list with units mixed in from other factions, and will not have some units from a faction available. Basically, your recruit list is determined by the plot of the campaign, not by a predetermined ruleset.

Sometimes factions make alliances with others, so you may face more than one faction in a scenario.

[Expand and draw on information in [[RaceDescriptions]].]

=== Finding Your Way Around Battle For Wesnoth ===
<div class="thumb tright"><div>
[http://exong.net/wesnoth-attach/files/splash111_1152_744.jpg http://exong.net/wesnoth-attach/files/splash111_300_159.jpg]
<div class="thumbcaption"><div align="center">The Main Menu<br>(Click to enlarge)</div></div></div>
</div>
When Wesnoth first starts it displays an initial background and a column of buttons called the Main Menu. The buttons only work with a mouse. For the impatient, we recommend you: click the 'Language' button to set your language; then click the 'Tutorial' button to run the tutorial; and then play the campaign, 'The Two Brothers' by clicking the 'Campaign' button and selecting it from the list provided.

The Main Menu buttons are:

*Tutorial
:The tutorial is a real, but basic, game which teaches you some of the basic controls needed to play the game. Winning or losing is not important here, but learning what to do is. Click the Tutorial button to play. In the Tutorial you are in the role of the young prince Konrad, learning from the Elder Mage Delfador - pay attention or he might turn you into a newt.

*Campaign
:Wesnoth was primarily designed to play campaigns. Campaigns are a series of connected scenarios. Click this button to start a new campaign. You will be presented with a list of campaigns available on your computer (more can be downloaded if you wish). Select your campaign and click OK to start or Cancel to quit.

:Each campaign has a difficulty level: easy, medium (normal), and hard. We recommend medium as this level is challenging, but not difficult. You may not change the difficulty during the campaign. Once you have selected the difficulty, you will start with the first scenario of the campaign. You can find walkthroughs or descriptions of the available campaigns at:
::* [[MainlineScenarios]]
::* [[UserScenarios]]
::* [[BeginnerScenarios]]

*Multiplayer
:Click this button to play single scenarios against one or more opponents. You can play the games over the internet or at your computer, against computer or human opponents. When you select this button a dialogue will appear and allow you to choose how you want to play the scenario. To learn more, see [[#Multiplayer|Multiplayer]].

*Load
:Click this button to load a previously saved game. You will be shown a dialogue listing saved games. Select the game and click Ok to load and continue, or Cancel to return to the Main Menu.

:If you select a replay game, you can check the Replay check box. The loaded game will make all the moves from the beginning while you watch.

*Language
:Click this button, select your language, and click OK to use it, or Cancel to continue with the current language. The first time Wesnoth starts, it defaults to English, but once you change it, it will start in that language.

*Preferences

:Click here to change default settings. These are explained in more detail in [[PlayingBattleForWesnoth#Preferences|the Manual]].

*About
:Click this button for a list of major Wesnoth contributors. You may find most of them at irc.freenode.org:6667 on #wesnoth. Or visit http://www.wesnoth.org for news, forums, and Wiki updates. The project is hosted on https://gna.org/projects/wesnoth, where you can download the latest production or developer release, review and report problems (bugs).

*Quit
:Click this button to close Wesnoth.

This getting started guide provides a basic introduction to Battle for Wesnoth. You can find more details about playing the game in the [[WesnothManual|Manual]].

=== Play a Game ===
There are two basic ways to play Battle for Wesnoth:
*Play a sequence of connected scenarios, known as a campaign, against the computer
*Play a single scenario against computer or human opponents

==== Campaigns ====

Campaigns can take a long time to complete. Typical campaigns have about 10-20 scenarios. The main advantage with campaigns is that they allow you to develop your army. As you complete each scenario, the remaining units at the end are saved for you to use in the next scenario.
If you choose not to use a unit at all during a scenario it is carried over
to the next, so you don't lose units you don't use.

The campaign is the primary form in which Wesnoth is intended to be played, is probably the most enjoyable, and is the recommended way for new players to learn the game.

==== Scenarios ====

A single scenario takes about 30 minutes to 2 hours to complete.
This is the fastest way to play, but your units are not saved and you cannot use
campaign units. You can play scenarios against the computer or against other players either over the internet or at your computer. Scenarios are accessed through the 'Multiplayer' button on the main menu.

===== Multiplayer =====
Multiplayer games are played against other players via the Internet (you can also run them on your LAN if you have one). These games are co-ordinated through the [[Improved_Manual#Campaign_Server|Wesnoth campaign server]].
Multiplayer games can take anything from 1 hour to 10 hours, depending on
how many players there are (and the size of the map). The average time is between 3 to 7 hours.
Games can be saved and loaded as many times as you like.
So, it's possible for some games to last 1 or 2 weeks, even though
the play time is only a few hours. You cannot carry over
units in multiplayer from one scenario to the next, so building up
your army's strength is possible only within the scenario.

===== Hotseat =====
Hotseat games are similar to Multiplayer games except everyone plays at the same computer by taking turns in the 'hotseat'. Hotseat games will take about the same time to play as games played over the Internet.

===== Human vs AI =====
You can also play any of the campaign scenarios against AI opponents rather than human players. This can be a good way to become familiar with the various maps that are used for multiplayer games before playing against real opponents. It can also be used as a simple way to explore the capabilities of units from the different factions by choosing which faction you will play and which faction your opponents are in these games.

==== The Game Screen ====

Regardless of whether you are playing a scenario or a campaign, the basic layout of the game screen is the same. The majority of the screen is filled with a map which shows all of the action that takes place in the game. Around the map are various elements which provide useful information about the game and are described in more detail below.

Across the top of the screen from left to right are the following items:
#Menu button
#Actions button
#Turn counter *
#Your gold
#Your total villages
#Your total units
#Your upkeep
#Your income
#Current hex type
#Current hex position

Down the right of the screen from top to bottom are:
#Full map, scaled *
#Time of day indicator
#Unit profile for last selected unit*
#End Turn button *

(Items marked with a * are currently undocumented)

*Menu button: Displays a drop-down menu with the following options:

#Scenario Objectives: Lists the victory and defeat conditions.
#Statistics
#Unit List: Lists your active units, including their map position.
#Status Table: Summary list of visible player units, villages, income etc.
#Save Game: Write the current game position to disk.
#Load Game
#Preferences: see [[PlayingBattleForWesnoth#Preferences|the Manual]] for details.
#Help
#Quit Game: Close the game, without saving, and return to the Main menu.

*Actions button: Displays a drop-down menu with the following options:
#Next unit
#Recruit: Lists units your commander can recruit from a keep.
#Recall (Campaign only): Lists units your commander can recall from a keep.
#Show enemy moves
#Best possible enemy moves
#End Turn: On your turn, select it to end your turn.

*Your gold, villages, units, upkeep, and income
:Quick way to check how your army is doing. A negative income means you'll lose gold, a positive means you gain gold. Upkeep is the gold you pay your units. Villages shows how many you own, each village will give you Gold.

*Current hex
:Shows the terrain type and position of the hex pointed to by the mouse. If a unit is on the hex, its resistance on that terrain is shown after the position. The position is in column, row order.

*Time of day indicator
:Putting your mouse over the indicator will bring up a tooltip showing the effect of the time of day. Wesnoth has a 6-turn day and different alignments have bonuses depending on the time of day.

==== Recruit and Recall ====
When you first start a scenario or campaign you will only have a few units on the map. One of these will be your commander (identified by a little crown icon). Your commander is usually placed in a castle on a special hex called a keep. Whenever your commander is on a keep (not only your own, but also the keep of any enemy castles you capture) and you have enough gold, you can recruit units for your army. In later scenarios you can recall experienced units that survived earlier scenarios. From here, you can start to build your army to conquer the enemy.

The first thing you will probably want to do is recruit your first unit. Press 'ctrl-r' (or right click on an empty castle hex and select 'recruit') and you will be able to recruit a unit from a list of all the units available to you. Each recruit is placed on an empty castle square. Once you have filled the castle, you cannot recruit any more until units move off. Your opponent's commander is similarly placed on its castle keep and will begin by recruiting its troops -- so don't dilly-dally looking at the scenery, there's a battle to be won.

At the end of each successful scenario, all your remaining troops are
automatically saved. At the start of the next scenario you may
recall them in a similar way to recruiting. Recalled troops are often more
experienced than recruits and usually a better choice.

==== Your Army ====

All game types use the same soldiers, called units. Each unit is identified
by Race, Level, and Class. Each unit has strengths and weaknesses,
based on their Resistance, current Terrain, and Level.
Full details are in the [[UnitTables]] and [[MoveTypeTables]].

==== Life and Death - Experience ====

As your troops gain battle experience, they will learn more skills and
become stronger. They will also die in battle, so you'll need to
recruit and recall more when that happens. But choose wisely, for each has
strengths and weaknesses a cunning opponent will quickly exploit.

==== Money ====
Your army does not fight for free. It costs you money to recruit units and money to maintain them. You start each scenario with money carried over from previous scenarios (although each scenario ensures you have at least a minimum amount of gold to start if you didn't carry over enough from previous scenarios) and can gain more by meeting scenario objectives quickly and, during a scenario, by controlling villages. Each village you control will give you two gold pieces income per turn. When you first start a scenario it is usually worthwhile to gain control of as many villages as you can to ensure you have sufficient income to wage war. You can see your current gold and current income at the top of the screen as described in the section on [[#The_Game_Screen|the Game Screen]]. More information can be found in [[PlayingBattleForWesnoth#Gold|the manual]].

==== Save and Load ====
At the start of each scenario, you have the option to save it.
If you are defeated, you may load it and try again. Once you have succeeded,
you will again be asked to save the next scenario and play that.
If you have to stop playing during a scenario, you can save your turn
and load it again later. Just remember, a good BFW player never needs to
save '''during''' a scenario. However, most beginners tend to do so rather
often. ;)

=== Getting the Most Fun Out of the Game ===

Remember, the idea of a game is to have fun! Here are some recommendations
from the development team on how to get the most fun out of the game:

* Consider playing the campaign on 'Medium' difficulty level, especially if you have prior experience with strategy games. We feel you'll find it much more rewarding.
* Don't sweat it too much when you lose some units. The campaign was designed to accomodate the player losing some units along the way.
* Don't abuse saved games. Long ago, Wesnoth only allowed saving the game at the end of a scenario. Mid-scenario saving was added as a convenience to use if you had to continue the game another day, or to protect against crashes. We do not recommend loading mid-scenario saved games over and over because your White Mage keeps getting killed. Learn to protect your White Mage instead, and balance risks! That is part of the strategy.
* If you must load a saved game, we recommend going back to the start of the scenario, so that you choose a new strategy that works, rather than simply finding random numbers that favor you.
* But remember, the aim is to have fun! You may have different tastes than the developers, so do what you enjoy most! If you enjoy loading the saved game every time you make a mistake, looking for the 'perfect' game where you never lose a unit, by all means, go right ahead!

==== At the start of a scenario ====
* First, read the scenario objectives. Sometimes you do not have to kill enemy leaders instead it is enough that you survive number of turns, or pick up a particular object
* Look at the map: the terrain, the position of your leader and the other leader.
* Then, begin to recruit units. Cheap units are useful to soak up the first wave of an enemy's attack; advanced units can then be brought in as support. Fast units can be used as scouts, for exploring the map and to quickly conquer villages.

==== During the scenario ====
* Try to capture and keep control of as many villages as possible to keep the gold coming in
* Keep units in packs so the enemy cannot attack from as many sides, and so you can outnumber each enemy unit. Put your units in a line so that the enemy cannot attack any one of your unit from more than two sides.
* Different units have different strengths and weaknesses depending on terrain and who they are attacking; right click on units and select "Describe unit" to learn more
* You can use lower level units as cannon fodder, to slow down enemy. e.g. you can use them to block enemy reaching your important units
* You can cause damage to enemies with advanced units and then finish them with lower level units - to give them more experience (and finally make them advance to next level)
* When you have a White Mage (advances from Mage) or Druid (advances from Shaman), put it in the middle of a circle of units to heal them as they move across the map
* Losing units is expected, even advanced units
* Time of day really matters:
** lawful units do more damage at day and less damage at night
** chaotic units do more damage at night and less damage at day
** remember to always check the time of day on the right side of the screen. Plan ahead - think about what it's going to be next turn as well as this turn.
* Some units are resistant or vulnerable to different kind of attacks. Mounted units are weak vs pierce attacks. Fire and holy destroy undeads. To see how much a unit resists an attack type, right click on the unit, select 'Unit Description', then select 'Resistance'. It will show you how resistant a unit is to different types of attacks.

==== Healing ====
An important part of succeeding at Battle for Wesnoth is keeping your units healthy. When your units take damage you can heal them by moving them onto villages or next to special healing units (e.g. the Elvish Shaman and White Mage). Some other units you will encounter, such as Trolls, have the ability to heal themselves naturally. You can find more detailed information about healing in [[PlayingBattleForWesnoth#Healing|Chapter 2]].

==== Winning a scenario ====
* Advanced units are needed to quickly kill enemy commanders, and to avoid losing lots of units.
* The quicker you win a scenario, the more gold you get; you will get more gold from winning early than from all of the map's villages for the rest of the turns.
* Killing all enemy leaders usually gives instant victory.

==== More general tips ====
* After slaughtering scenarios (where you take lots of punishment) there are usually "breathing room" scenarios where you can rather easily gain some gold and experience (advanced units)
* Advanced units have higher upkeep than lower level units (1 gp per level), loyal units are an exception.

<noinclude>

=== See Also ===
* [[WesnothManual]]
* [[AdvancedTactics]]

{{Play}}
</noinclude>

Create

2006-07-17T13:49:15Z

Xan: Reverted edit of Nightmare, changed back to last version by Sjl

{| style="float:right"
|
__TOC__
|}
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.

It should also be noted that '''we need a lot of help creating artwork for the core of the game.''' The current projects we are working on are [http://www.wesnoth.org/forum/viewtopic.php?t=9162 listed here]. We'll happily help you out, if you take a swing at them.

== 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
* [[WesnothTranslations|Translations]] - work on translating Wesnoth

== 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]
* [[Complete Faction List (unfinished)|Complete Faction List]]

== 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 ==
* [[ExternalUtilities| External Utilities]] - some extra tools for easier creating stuff
* [[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}}

BuildingMaps

2006-07-17T13:49:15Z

Xan: Reverted edit of Nightmare, changed back to last version by Sparr

This is all you need to know about maps:

# A map is just a bunch of letters arranged in a rectangle (the rectangle is known as the "map data")
# There are two ways to save this rectangle in a file

Seriously now, here are the details.

== Wesnoth map data format ==

Map data is used to represent maps in Wesnoth. The encoding for maps has a specific format:

* A map data file consists of any number of lines, each with the same number of characters.
* Each character must be either a letter specified in a ''letter'' key specifying a terrain (see [[TerrainLettersWML]]), or a digit.
* When the file is interpreted, each letter will be replaced by the terrain it refers to.
* Each nonzero digit ''n'' where ''n'' = 1, 2, 3, ... will be replaced by keep, with the leader of side ''n'' placed on the keep.

Since text file tiles are squares while game tiles are hexes, some tiles must be shifted.
Tiles in even-numbered columns are shifted down 1/2 of a tile.
For example, to have a road of connected dirt ('r') tiles, the map data would look like this:

rrgggggg
ggrrgggg
ggggrrgg
ggggggrr

== Creating a map ==

This is not the Matrix. You do not need to look at encoded maps. The source code and most binary distributions come with the official graphical map editor. Using the map editor tends to be straightforward, judging from the feedback received from novice mapmakers. However, if you do encounter problems locating or using the editor, please ask for help on the [http://www.wesnoth.org/forum forum].

After the map is created, you may find it easier to make small tweaks by editing the textual map data directly.

Making good, balanced, interesting maps is another task altogether, and if someone wants to take a stab at sharing insight about this art, please do so.

== Using map data ==

Map data is used in two ways.
# It is used as an input to the key ''map_data'' (see [[ScenarioWML]]).
# Files consisting entirely of map data can be read and edited easily by the [[WesnothMapEditor]].
#* Files in the folder '''''userdata''/editor/maps/''' which consist entirely of map data can be played in multiplayer as user maps.

==== The map_data key ====

The first way is to use the map_data key. A campaign scenario starts with the '''[scenario]''' tag. A multiplayer map scenario starts with the '''[multiplayer]''' tag. Each tag takes the key ''map_data''. The value of the ''map_data'' key is the map data enclosed in quotes. Here is an example:
map_data="111111111111111111"

==== Standalone map file ====

The second way to store a map is in a text file that consists '''only''' of the map data. The advantage of this method is that it's simple. If you drop one of the map files in '''''userdata''/editor/maps/''', the game will find it automatically in multiplayer. On the other hand, this method also works with more complex scenarios. If there is a scenario file somewhere (campaign or multiplayer) that has a line similar to the following:
map_data="{@editor/''map_filename''}"
then all of the map data in the file is inserted between the quote marks.

== Discussion: Scenario File vs Standalone ==

Campaign writers can't write campaigns without scenarios, so campaigns will always use the ''map_data'' key, either with the raw data in quotes or a preprocessor symbol {} pointing to the standalone file.

Multiplayer mapmakers, however, '''have a choice'''. If you want to place an object or unit on the map, you must create a scenario file starting with the '''[multiplayer]''' tag and containing the ''map_data'' key therein. You lose the simplicity of the standalone map file, but you gain tremendous power. Not only can you add units and objects, you can set allies, experience modifiers, add a map description, and add custom events (among other things). The question, "How do I place an object on the map with the map editor" is such a common question that I am sorry this information is buried so deeply here. But, now that you know you can seek out an example of a multiplayer map scenario file to use as an example. The game comes with many maps of each type. Check out [[BuildingMultiplayer]] for more information.

== See Also ==

* [[Create]]
* [[ScenarioWML]]
* [[ReferenceWML]]

{{Create}}

WML Abilities

2006-07-01T13:15:46Z

Xan: /* Bloodlust */

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

=== Knockback {{DevFeature}} ===

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

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

Note that this uses the macros ''OPPOSITE_SIDE'', ''IF'', ''IF_HAVE_UNIT'' and ''STORE_UNIT_VAR'' from the [[WML Utilities]] page.

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

[filter]
{FILTER}
[/filter]

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

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

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

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

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

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

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

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

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

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

=== Charm {{DevFeature}} ===

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

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

{CHARM (type=Troll Whelp) fist}

Note that this uses the macros ''IF'', ''STORE_UNIT_VAR'' and ''MODIFY_UNIT'' from the [[WML Utilities]] page.

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

[filter]
{FILTER}
[/filter]

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

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

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

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

{CLEAR_VARIABLE varname}
[/then]
)}

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

[event]
name=side turn
first_time_only=no

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

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

variable=possibly_charmed
kill=no
[/store_unit]

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

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

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

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

=== Bloodlust ===

Bloodlust is a very simple ability. If a unit that has bloodlust kills an enemy unit when attacking, it may attack again, provided that there are more enemy units adjacent to it. Uses the MODIFY_UNIT macro from the [[WML Utilities]] page.

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

{BLOODLUST (type=Dwarvish Ulfserker)}

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

[filter_second]
{FILTER}
[/filter_second]

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

WML Abilities

2006-07-01T13:12:08Z

Xan: /* Charm {{DevFeature}} */

GettingStarted

2006-05-29T18:24:03Z

Xan: Reverted edit of TRSaMBa, changed back to last version by Xan

WesnothTranslations

2006-05-09T12:34:34Z

Xan: Reverted edit of Bobdole, changed back to last version by Sophie

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Nico Oliver - [mailto:wesnothafATgmailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:ziberpunkATziberghettoDOTdhisDOTorg]
* [[BulgarianTranslation|Bulgarian]] maintainer: Georgi Dimitrov (oblak) - [mailto:oblakATgbgDOTbg]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: Firen, [mailto:qhy@hotmail.co.uk]
* [[CzechTranslation|Czech]] - maintainer: Oto Buchta (tapik) - [mailto:tapikATbuchtoviDOTcz]
* [[DanishTranslation|Danish]] maintainer: Anders K. Madsen (madsen) - [mailto:madsenATlillesvinDOTnet]
* [[DutchTranslation|Dutch]] - maintainer: Maarten Albrecht (bloom) - [mailto:maartenalbrechtATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=970 ott] - No mail address specified
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Joset Zamora (sophie^) - [mailto:sophieUNDERSCOREgeekATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Matias Parmala - [mailto:matiasDOTparmalaATppDOTinetDOTfi]
* [[FrenchTranslation|French]] - maintainer: Guillaume Massart (Piou2fois) - [mailto:massartDOTguillaumeATwanadooDOTfr]
* [[GalicianTranslation|Galician]] - maintainer: Jacobo Fernandez (Xacobe) - [mailto:xacobe_gzAThotmailDOTcom]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Nobody, currently
* [[HebrewTranslation|Hebrew]] maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Széll Tamás (TomJoad) - [mailto:tomiATdigiflexDOThu]
* [[ItalianTranslation|Italian]] - maintainer: Americo Iacovizzi (DarkAmex) - [mailto:americo_iacovizziATliberoDOTit]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: Kim Woong - [mailto:jojowarezAThotmailDOTcom]
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Karol "grzywacz" Nowak - [mailto:grzywaczATsulDOTuniD0TlodzDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[RussianTranslation|Russian]] - maintainer: Alexandr Menovchicov - [mailto:vamATkypiDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srecko Toroman (freecraft)- [mailto:freecraftATgmailDOTcom]
* [[SlovakTranslation|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: David Martinez (ender/Jo-Con-El) - [mailto:enderATdebianDOTorg]
* [[SwedishTranslation|Swedish]] - maintainer: Stefan Bergström (tephlon) - [mailto:stefanDOTbergstromATgmailDOTcom]
* [[TurkishTranslation|Turkish]] - maintainer: Selim Farsakoglu - [mailto:farsakogluATwebDOTde]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (svn)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]

WhatArePlayersSaying Old

2006-05-09T12:34:28Z

Xan: Reverted edit of Bobdole, changed back to last version by Ivanovic

"Lots of potential"

"Now it's in development and its good, when it's done it'll be great. The team that work on this project (the coders,
graphic artists, porters) are pretty passionate about this and that's part of what makes it so great, bugs are
continually being worked out at a good pace and new features are implemented quickly, especially considering that they
basically do this for free. Another reason why this is so great is that it's a free, open-source, multiplatform project."

"At it's current state a lot of things could be better, the graphics, the GUI, and the documentation, although I found it
to be pretty stable. All things considered though, especially that it's still a beta, the entire BoW team should be
commended."

-- Kishina about 0.7.8 at [[VersionTracker]].com

"One to try!"

"The numerous changes have improved virtually every area of the game. It is maturing into an extremely fine game."

"This is definitely one to try."

-- [[BornAgain]] about 0.7.7 at [[VersionTracker]].com

"what's up with the game telling me i need v. .72 to play multiplayer when v. .72 doesn't *exist* yet?? how does v. .71
of the game know v. .72's going to be able to play multiplayer??"

"these folks are windoze developers - that much is clear."

-- plaintiger about 0.7.2 at [[VersionTracker]].com

"Maybe that is because..."

"...the Mac OS X version lags a bit behind the Windoze and Linux versions? BoW 0.72 is available for Win and Linux since
April 8th"

-- haemophilus about 0.7.2 at [[VersionTracker]].com

"Lots of improvements!"

"Hey, the Mac version just jumped to 0.7.3 Multiplayer.. was that really such a long wait? Give the developer(s) a
little slack geesh! It takes time to develope multiplatform."

"With so many improvements it shoulda been v0.8"

-- Xapplimatic about 0.7.3 at [[VersionTracker]].com

"it is easy to play. i have ADD and don't deal well with games that require me to think about 17,000,000 things at once;
this game makes commanding a whole bunch of units spread out over a map much easier and less harrowing than some others
i've tried. the graphics aren't exactly cutting-edge, but they're not primitive either - quite fine, i think...and the
gameplay's simple - you basically just generate units, move, and fight. BFW doesn't make you think about a lot of
extraneous stuff - it just lets you relax and play. i'm not really even into this kind of game any more; i just try one
once in a while to make sure i won't like it - and i like BFW. not everybody's tastes are the same, and i can't really
know what you like in a game, but i recommend downloading this one - start the d/l before you go to bed or something and
just let it go for however long it takes - and checking it out. it's quite likeable"

-- [[AppleBeer]] about 0.6.99.5CVS at [[VersionTracker]].com

"open source Master of Monsters"

"There was a console game about 15 years ago called Master of Monsters. fantasy TBS. hex map with terrain tiles. You
play a leader who summons critters (elves, wizards, trolls, etc) to fight for you. Critters gain experience and progress
to stronger forms. If this sounds fun to you, Wesnoth does it quite well."

-- fuy about 0.7.1 at [[VersionTracker]].com

"Great fun"

"The story is great and the depth involved with different units having certain strengths is admirable...i recomend it to
anyone who can have fun without high polygon counts and eyecandy"

-- Mavent04 about 0.6.99 at [[VersionTracker]].com

"It is quite nice"

"This is pretty impressive for a freeware game. It also runs without any problem in OSX 1.5. Any additional improvements
from the author would only be icing on the cake"

-- hkim about 0.6.1 at [[VersionTracker]].com

"Nice little game, can't beat the price"

"Cute turn-based tactical game in the tradition of Strategic Conquest, with quality comparable to [[FreeCiv]]"

-- fuy about 0.5.2CVS at [[VersionTracker]].com

"Way to go"

"This fixes all the glitches that bugged me with the previous 0.5 version. The AI seems a bit tougher though, which
isn't a bad thing. I love the unit experience level aspect. Keep up the good work, people"

-- pdot about 0.5.2CVS at [[VersionTracker]].com

"A lot of potential"

"Some interface and performance issues aside, Wesnoth has the makings of a nice tactics game in the Ogre Battle genre.
One of the better open source productions, with a nice-looking tileset and decent game dynamics already in place."

-- [[EricWong]] about 0.5 at [[VersionTracker]].com

"Cool game"

"Ok, as for the game. For me - cool. Fast, stable, good entertainment. I was played it Yesterday and I like it. And its
price - unbeatable :))) Keep up good work :)"

-- mroczny about 0.4.9CVS2 at [[VersionTracker]].com

"It took a little getting used to the 10 year old graphics, but in terms of fun, it's pretty good. It reminds me of a
mix between Warlords and Warcraft. There are speed issues with the game. For instance, waiting for the AI enemies to
move and attack takes way too long. It's helpful to see what the computer is doing, but a speed-up in that area would
make the game more enjoyable. There's also a problem with responsiveness of the mouse. I find myself clicking the same
unit or option more than once. As for stability, it ran fine the 2 times I played the tutorial, but it's stalling right
now in the first campaign scenario. I switched to Firebird to write this review while it is the computer's turn and it's
stalling. I was surfing the net earlier while the game was running so I guess it's just a random glitch. I look forward
to playing the next version"

-- pdot about 0.4.9CVS2 at [[VersionTracker]].com

"Awesome game"

-- Nice about 0.7.7 at [[MacGameFiles]].com

"Simple, easy to learn, yet plenty of room for tactics. Multiplayer is also fun and easy, provided you get a friend on
the server at the same time as you."

-- Shadowdancer about 0.7.2 at [[MacGameFiles]].com

"This bored the crap out of me. And there doesn't seem to be a way to move your units all at once. One at a time, one at
a time. I mean, bravo for the open source effort, but, make it more fun... and make it with less fantasy dork-cheese
(big punchline, "Elf: Humans are obviously less skilled." HAHAHAHA OH.. wait.. that's not funny.)"

-- citric about 0.7.2 at [[MacGamefiles]].com

"How do you propose to "make it more fun", citric? Multiplayer is a blast and single-player is good, too... This is one
of the best turn-based strategy games out there."

-- Ol'Sammy about 0.7.2 at [[MacGameFiles]].com

"Great game. The pinnacle of open-source gaming."

-- Gafgarion about 0.6.99.5 at [[MacGameFiles]].com

"Absolutely love it. It had some visual glitches at first, but this version fixed them. Now that I can play in windowed
mode, I find the game to be a great way to kill time, and the story so far has me wanting to see more."

-- Naman about 0.6.99.4 at [[MacGameFiles]].com

"It's a fantasy strategy game with rpg elements (units level and can be carried over into following missions (in
campaigns)).. And it has elves! Bloody cool looking elves!"

"And it's available for a lot of platforms. Mac, Windows, Linux.. and there's a multiplayer feature, too!"

-- Na'enthos Telenin at World of Warcraft Roleplaying Association forum

"Heh, not a bad game...reminds me of Ogre Tactics."

-- Marn Skullstomp at World of Warcraft Roleplaying Association forum

"looks alittle low tech dont it?"

-- Larod at World of Warcraft Roleplaying Association forum

"Yeah, but just because it's 2D and stuff doesn't mean it can't be fun."

-- Marn Skullstomp at World of Warcraft Roleplaying Association forum

"I have been playing it the whole day and I really enjoy it. It is fun and really hard to beat. I am in the orcish
campaign. "

-- Dharko at World of Warcraft Roleplaying Association forum

"W3 wasn't all good of a RTS anyway. This game is better."

-- Gothic-Shadow at World of Warcraft Roleplaying Association forum

"I will be soon enough. I'm still learning and playing through some of the campaign. Damn this game is fun."

-- Kazrak Heldenhammer at World of Warcraft Roleplaying Association forum

"Fun game... although it sometimes gets pretty damn hard"

-- Kaeldorn at World of Warcraft Roleplaying Association forum

"Fun game, but orcs are a bit overpowered."

-- Fenix Fireborn at World of Warcraft Roleplaying Association forum

"Hey! I saw you on the wesnoth forums. How did you find this site? Let alone at the same time we were talking about
wesnoth. Are you psychic?"

-- Kazrak Heldenhammer at World of Warcraft Roleplaying Association forum

"We have eyes and ears reporting to us... we are everywhere =)"

-- Miyo at World of Warcraft Roleplaying Association forum

"the best game I have ever played"

"For a long time i've wanted to play a clever and original tactical game. Wesnoth is all of that... and it comes with a
nice storyline too!! Well, what else can i say, i don't have time for this... i gotta play :-P"

-- Onnellinen at The Linux Game Tome

"Fabulous Game"

"Most fun I have every had playing a turn based strategy game."

-- lisap511 at The Linux Game Tome

"Good fun!!!!!!!"

"Very original and well done game. Excellent sound, graphics and gameplay. Hours of fun."

-- mdhowe at The Linux Game Tome

"Best free Linux game"

"Great work ! That is the best free Linux game I've ever played."

-- [[ScaChi]] at The Linux Game Tome

"Impressive work!"

"Awesome strategy game. A must-play for everyone who enjoys a turn-based challenge of exceptional quality! :)"

-- Cironir at The Linux Game Tome

"I am Impressed!!!!"

"After more the a Year reading the Linux game tome, i finnaly created a account to rate this Game. It ist great!!! 5
Stars from Austria for this masterpiece of Software. At last there are some Words that are not Translated to German. Do
you need a Tranlater?"

-- xeniac at The Linux Game Tome

"Musics! Argh!"

"An awesome game, but I can't play it, because the musics break my ears and nerves. The theme music is great, and some
other musics are good too, but eg. wesnoth-3 wesnoth-4 and wesnoth-6 are awful! Please recompose them."

-- Anonymous at The Linux Game Tome

"This is awesome"

-- Anonymous at The Linux Game Tome

"This game is a stupendous achievement!"

"This one is set to be your new favorite. I can't wait for some of the new campaign scenarios. Don't wait for the 1.0
release, do yourself a favor and download and compile this one ASAP. Holy cow this game is great!"

-- Dou9st3r at The Linux Game Tome

"Great game - what more is to be said?"

-- [[TomSauer]] at The Linux Game Tome

"Wesnoth is one of the best fantasy turn-based strategy games I've ever played. Can't wait for it to reach 1.0!"

-- jbmesserly at The Linux Game Tome

"Awesome Game!!! Provides Linux with what it lacks... Quality gaming"

-- z9484 at The Linux Game Tome

"Great"

"Wesnoth battle is A great game! I hope the guys to continoue their good job!"

-- Anonymous at The Linux Game Tome

"just awesome and getting better :)"

-- lynx_lupo at The Linux Game Tome

"Best freeware game I've yet played"

"The "easy" level could be a bit easier, however :) But by no means is the "easy" level outragously difficult, as it is
in freeciv."

-- mathandmetal at The Linux Game Tome

"Great gameplay"

"Simple rules, but many interesting tactics. Graphics are clear and pleasant and the game is very polished. This is my
favorite hex-tactics game."

-- karlb at The Linux Game Tome

"Simple, but awesome"

"I love it :) Pretty graphics for a free game."

-- deline at The Linux Game Tome

"excellent game, i loved it. Reminds me of old classics like the first warcraft mixed with a little Myth+Magic.kinda.
anyhoo, xcellent game, with no unreasonable dependencys, in fact modern distros will have them already in most cases, or
will be able get them through rpm/rpmdrake or apt-get. Install was pleasant also. If i had time i would love to create
level sets for it:-)"

-- rokknroll at The Linux Game Tome

"excellent game"

"Nice graphic and well developed scenarious. I love the game and played it to the end in two days. I like the level
structure of the units. But it's a pity that there are max tree levels, five or seven will be O.K."

-- Anonymous at The Linux Game Tome

"Great game!!"

"Graphics are great and it is easy to get used to play. The interface can be translated to many languages. A must
download game!"

-- Anonymous at The Linux Game Tome

"This game has great playability - I keep returning to it. And it runs fine on my old Pentium 1."

-- m487396 at The Linux Game Tome

"KISS"

"This game is exactly like I like games to be - rich, but still simply, lot of fun for beginners and advanced alike. The
KISS principle makes this game almost perfect - and ideas, hard work etc. make it absolutely perfect :) Thank you."

-- Anonymous at The Linux Game Tome

"Great game"

"If you like this kind of game, it's a must-try."

-- Errabes at The Linux Game Tome

"I just can say that this is a great pice of work! Spent nights on playing the campaign!"

-- mschmitt at The Linux Game Tome

"Excellent, but need to improve"

"Very nice, I spent some hours on the campaign. I'll collect some suggestions and send them to the authors. This game is
well-designed and implemented. It just suffers for its small life-time (version number seems correct). I'm sure that
once at version 1.0 this game will be one of the best around!"

-- johnny at The Linux Game Tome

"Unbelievable!"

"Just download it and try it! Believe it: this game is the best of its class and its very very very much polished! Yes,
it doesn't look like the average free software games! Excelent work guys!"

-- terrible at The Linux Game Tome

"cool!"

"Amazingly polished.... much better that your average open-source game. Looking foward to 1.0 , although it's already
loads of fun! :D"

-- Anonymous at The Linux Game Tome

"Great game!!!"

"Great work!!! One of the nicest Games (commercial or not) I have ever played - getting better by the minute ;)))
Cheers, afa"

-- afa at The Linux Game Tome

"Excellent"

"This is a great game. Good strategy concept, good graphics and sound. And most important: very addictive and playable.
Keep up the good work."

-- mbabuskov at The Linux Game Tome

"Excellent as Bexcellent"

"Keep up the good work! This game is truly appreciated. It is extremely qualatatious (meaning it is full of quality)."

-- Anonymous at The Linux Game Tome

"Really an excellent game - my choice for relax moment from work."

-- Polaris at The Linux Game Tome

"I need a game which could be played on my piii notebook. I need a game which could be played in Linux. And I found
wesnoth. I like this game. Very Good."

-- zhangyuan at The Linux Game Tome

"Incredible"

"This game has good graphics, excellent gameplay, nice single-player campaigns (which is a rarity for free games), the
code and data infrastructure is great, and the community really pushes hard. This is the Next Big Thing, I'm pretty
sure. Oh, and of course I'm addicted. Hey, this has something like 115 different units! And character development! And
they're so damnably cute..."

-- therealmawa at The Linux Game Tome

"Very nice game"

"I like the campaing mode of the game very much. It's the first game where I've encountered a campaing mode in which the
result in one level defines the chances for next one. Only downside is that it consumes too much free time. ;-)"

-- torangan at The Linux Game Tome

"Absolutely addictive"

"Installed it and played 10 hours straight, forgetting everything else around me."

-- basramm at The Linux Game Tome

"My whole family really enjoys this game, particularly the oldest three children, my 9yo boy, and 12 and 13yo girls. It
fires up their imaginations -- my boy has started introducing Wesnoth characters into his sketches. Maybe some of his
art will someday make it into the game. :)"

"It would be a stretch to call this game "educational", but I do appreciate any game that makes the kids think. At
first, I didn't think my 9yo was really "getting it", as he was struggling with the first scenario in the campaign even
on "easy" play level. But after giving him some tips, now he has made quite a bit of progress through the campaign, and
I am encouraged to see that he is continuing to learn what to pay attention to as he plays."

"Also of particular benefit to our family is the multiplayer mode -- my 12yo lives in with her mom about an hour's drive
away, and their cousins live too far away to visit, so we've been trying to get together to play whenever we can. We
still have some issues here to work out (mostly with Windows, and likely OS-related, not problems with the game itself,
as I know my brother in the US has an oldish version) but the developers have been quite responsive on the irc channel
#wesnoth at irc.freenode.net whenever we have encountered problems."

"I'm certainly going to include this in Debian Jr. now that I have seen that my kids love it."

"Kudos to the whole Wesnoth community for helping make this game a tremendous success, especially the Debian guys I work
with who have polished up the package, helped provide and maintain a woody backport, and have kept up with upstream
releases, often releasing on the same day the release is announced."

-- synrg at The Linux Game Tome

"I've been looking for a decent turn-based tactical-strategy game for ages, and the other day someone pointed me at
this. Hoorah - it's a decent turn-based tactical-strategy game. Still not the Lords Of Chaos or Laser Squad game I'm
*really* looking for, but it's excellent all the same."

-- [[RavenBlack]] at The Linux Game Tome

"This is bye far the best free turn based fantasy ame i ever played.. it almost brings tears to my eyes."

-- kerrigan at The Linux Game Tome

posts 0-50 browsed through in The Linux Game Tome, 51-131 to go.

== See Also ==

* [[WesnothLSM]]

Create Music

2006-05-09T12:34:27Z

Xan: Reverted edit of Bobdole, changed back to last version by Turin

Musicians usually meet on the [http://www.wesnoth.org/forum/viewforum.php?f=14 Music development forum]. This is the best place to discuss new music and potential contributions.

Current information for musicians is found in the [[Project|Project section]]

== Format ==

In-game music is in .ogg format, which is similar to the .mp3 format, only it's [http://www.vorbis.com/faq/#artist completely free]. Sound effects are in .wav format, but ''can be'' in .ogg format -- this is crucial information for a campaign writer trying to reduce download size.

== Style ==

New music composed for Wesnoth should be orchestral with realistic sounding samples, and 3 to 6 minutes in length. For an idea of the direction the developers are looking to take Wesnoth's music in, check out [http://aleksi.free.fr/Wesnoth/ Aleksi's] and [http://www.timothypinkham.com/Wesnoth/ TimothyP's] recent contributions.

== See Also ==
* [[Create]]
* [[Project]]

WhatArePlayersSaying

2006-05-09T12:34:26Z

Xan: Reverted edit of Bobdole, changed back to last version by Jordi

== What this page really is about ==
There have been many comments from Wesnoth players all over the world. It looks like Wesnoth is one reason that several linux projects are improving only slowly. We really want to say sorry to all the Debian-Devs out there that ceased being productive. And of course we will give some proof for this thesis. On this page you will find several comments taken from magazines, blogs and comments made by users from all over the world.

== That is what Magazines and Websites write about Wesnoth==

=== Holarse ===
Here is what the german linux-gaming site [http://www.holarse.de Holarse] writes about the release of Wesnoth 1.0:
<blockquote>Finally the turnbased fantasy-strategy game Wesnoth has reached the version 1.0 [...]
It for sure came to the reputation of being the "best linux-game" ever because of its good graphics
and interesting storyline.</blockquote>
The complete article can be found [http://polska.merseine.nu/h2006/space/start/2005-10-04/2#Wesnoth_1.0 here] (only in german).

=== IDG ===
The swedish computer news site [http://www.idg.se idg] writes about the 1.0 release for Mac:
<blockquote>The Battle for Wesnoth is a fantasy strategy game where you can choose between many different characters
and by that different campaigns</blockquote>
The complete article can be found [http://www.idg.se/ArticlePages/200510/05/20051005130340_MW/20051005130340_MW.dbp.asp here] (only in swedish).

=== IMG (Inside Mac Games) ===
[http://www.insidemacgames.com/ Inside Mac Games] [http://www.insidemacgames.com/reviews/view.php?ID=642 reviews] Wesnoth.

=== linux-gamers.net ===
An [http://www.linux-gamers.net/modules/news/article.php?storyid=992 article] about the release of Wesnoth 1.0 at [http://www.linux-gamers.net linux-gamers] reads like this:
<blockquote>The popular free round based strategy game Battle for Wesnoth has been released in Version 1.0.
Battle for Wesnoth is one of the most popular games unter [sic] the GPL. The game does not need to
fear the comparison with commercialy available games of the same genre.</blockquote>

=== LWN ===
[http://www.lwn.net Linux Weekly News] [http://lwn.net/Articles/154429/ reviews] Wesnoth 1.0.

=== PC4War ===
The august issue of the french magazine [http://www.PC4War.com PC4War] includes a one-page review of Wesnoth:
<blockquote>«an excellent turn-based fantasy game, whose characteristics are essentially to be free, and evolutive!»</blockquote>
The complete article [http://www.wesnoth.org/images/wesnoth_pc4war.jpg is also available].

=== The Mac Observer ===
[http://www.macobserver.com The Mac Observer] [http://www.macobserver.com/columns/slackersguide/2005/20051014.shtml reviews] Wesnoth 1.0

== Wesnoth appears in several blogs ==
* Games are bad for Debian. Especially time-killers like wesnoth. They make me very unproductive, even though I'm not playing any of the higher difficulties, I cannot resist the urge to play through all campaigns [...]
found in this [http://blog.drinsama.de/erich/en/2005062801-wesnoth blog]

* If you want to stay productive don't ever run the following command:
sudo aptitude install wesnoth ; wesnoth
Is "Kills all my time" a good reason for a RC-Bug? I mean, if you install it, you can hardly stop playing, therefore it renders all other installed software useless. I think wesnoth should be removed ASAP from the archive...

found in the [http://blog.schmehl.info//2005/09/30#wesnoth blog] of Alexander Tolimar Schmehl

* [...] My opinion: It makes addicted! Check it out!

found in this [http://sven.formvision.de/blog/archives/55-Rundenbasierte-Strategie-The-Battle-for-Wesnoth.html blog] (only in german)

* Battle for Wesnoth seems to become a real threat for the Debian project. More and more Debian developers get sucked into the world of elves, dwaves, orcs, zombies and mages — and only few return...

found in this [http://www.hermann-uwe.de/blog/my-wesnoth-replays-online blog]

*Do not under any circumstances apt-get install wesnoth! It’s quite addictive and very good. Currently worried about getting anything done for the next… errrr… year? It’s been ages since I’ve really gotten into a game. I think this may actually be one I’ll get pretty into. Rock on Wesnoth developers!

found in this [http://www.flamingspork.com/blog/?p=418 blog]

== Players do comment about Wesnoth ==
* Stable, beautiful (graphics, sounds and music), neither too easy nor too hard, cool story and characters, usable interface, great tutorial... This is one of the best games I've ever played.
A comment at The Linux Game Tome submitted by blop

* Wow, this game is amazing! I wish I'd gotten it earlier !! It has a really professional look and feel.
A comment at The Linux Game Tome submitted by bigfatdude

* found the game in the net: played it for hours (and still playing it). showed it to my kids: they still play and always want the newest version (they know most units stats... like they knew all the pokemons). showed it to my friends: lots of ’em like and play it (the ’over 30’ fraction). kids showed it to their friends: guess what happend... (the ’under 15’ fraction).
Taken out of the [http://www.wesnoth.org/forum/viewtopic.php?t=7770&start=23 Wesnoth Forum], written by Xytan

* It's been fantastic watching this come together. Talented programmers, artists, musicians, campaign/story developers - Wesnoth is a really special example of how open source can accomplish great things. Thanks to Dave and all the others who have worked hard to create this game!
Taken out of the [http://www.wesnoth.org/forum/viewtopic.php?t=7770&start=26 Wesnoth Forum], written by Nothsa

== See Also ==
* [[WhatArePlayersSaying_Old| Some older Comments]]
* [[Play]]

StartingPoints

2006-05-09T12:34:25Z

Xan: Reverted edit of Bobdole, changed back to last version by Scott

__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?movetypes Movement, defense and resistance tables]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
** [[Complete_Faction_List_%28unfinished%29]] - list all user made factions
* [[WesnothAcronyms|Wesnoth Acronyms (by category)]] - common wesnothian acronyms explained
* [[WesnothAcronyms(alphabetic)|Wesnoth Acronyms (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
* [[UnitAnalysis]] - tool to analyze units
* [[WesnothMapEditor]] - summary of controls
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[Create_Art#Art_Tutorials|Art Tutorials]] - help in creating art
* [[GraphicLibrary]] - unit and terrain images posted on the forums
* [[Tiles_Status]] - terrain tiles: proposed and in progress.

== Improving the Game ==
* [[ReportingBugs]] - use Gna
* To submit a feature request, use http://bugs.wesnoth.org
* [[FrequentlyProposedIdeas]] - before you propose an idea, check here!
==== 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

== 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].
* [[Trailer]] - the Wesnoth trailer

== 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]

== About this Wiki ==
* [[Help:Editing|Editing]] - learn how to edit pages
* [[Sandbox]] - experiment with the wiki
* [[WikiMigration]] - we were looking for a replacement for our old wiki (and ended up using Mediawiki)

WesnothBinariesLinux

2006-05-09T12:34:24Z

Xan: Reverted edit of Bobdole, changed back to last version by Rjw5934

= GNU/Linux =
Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.

=== Arch Linux ===
* For the official pkg from [extra]: <code>pacman -S wesnoth</code>
* dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.

=== Debian ===
* <code>apt-get install wesnoth</code> or
* <code>aptitude install wesnoth</code>
* [http://packages.debian.org/wesnoth Official packages]
* [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]
===> about this backport, maybe an issue with an unresolvable dependancy, the "ttf-dejavu" package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]

====> 8 October: adding

deb http://ftp.tr.debian.org/debian/ unstable main
deb-src http://ftp.tr.debian.org/debian/ unstable main

to /etc/apt/sources.list,

Package: wesnoth
Pin: version 1.0-1sarge*
Pin-Priority: 1001

Package: wesnoth-data
Pin: version 1.0-1sarge*
Pin-Priority: 1001

Package: *
Pin: release a=stable
Pin-Priority: 700

Package: *
Pin: release a=testing
Pin-Priority: 650

Package: *
Pin: release a=unstable
Pin-Priority: 600

to /etc/apt/preferences and then installing ttf-dejavu with

apt-get install -t unstable ttf-dejavu

worked for me ;-)

====Compiling====
If you want to install the latest Development version you may have to compile it yourself. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].

'''To install the dependencies :'''
<code>aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev</code>

Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by

<code>aptitude install gettext</code>

If someone may confirm that ...

'''To compile it :'''
If you have already installed and older version of wesnoth, uninstall it by :

<code>aptitude purge wesnoth</code>

Note that will remove all your wesnoth configuration.
Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.
Now, it's very easy :

cd /usr/src
tar -xvzf wesnoth-1.x.x.tar.gz
cd wesnoth-1.x.x
./configure
make
make install

You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.

=== Ubuntu ===

Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the latest stable release. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:
*Upgrade to the Dapper Drake, or
*Use the Breezy-Backports repository,
*Use an unofficial repository, or
*Build from the source per Debian above, or
*Use the generic binary for GNU/Linux found on the [[Download]] page.

Of these options, the final one is most likely the easiest at this time, while building from source is the most reliable.

See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.

Do not attempt to install the debian package and associated dependencies using ''dpkg'' as you will break your environment!

====Compiling====
If you choose to build the source you should add the a flag to ''configure'' to ensure your installation puts the data in the same place as the official installation path:

cd /usr/src
tar -xvzf wesnoth-1.x.x.tar.gz
cd wesnoth-1.x.x
./configure --datadir=/usr/share/games ...
make
sudo make install

=== Fedora Core ===
Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.
* <code>yum install wesnoth wesnoth-tools wesnoth-server</code>
* Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/

=== Gentoo ===
* <code>emerge wesnoth</code>

=== klik ===
* The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no "installation" (the base system remains untouched); its created "AppDir" bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:
** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to "klik" it, type ''klik://wesnoth'' into your Browser
** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to "klik" it, type ''klik://wesnoth-latest'' into your Browser

=== Mandrake (cooker) ===
* <code>urpmi wesnoth</code>
* Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/
* Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/

=== Slackware 10.2 ===
sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy
* '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/

=== [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===
* '''Wesnoth 1.0.2 & 1.1.2 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 & 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):'''
<br>
* Wesnoth Stable & Devel for SuSE 9.3:
** http://www.unixboard.de/files/suse-rpms/9.3/wesnoth-1.0.2-1.i386.rpm for [[SuSE]] 9.3
** http://www.unixboard.de/files/suse-rpms/9.3/wesnoth-1.1.2-1.i386.rpm for [[SuSE]] 9.3
<br>
* Wesnoth Stable & Devel for SuSE 10.0:
** http://www.unixboard.de/files/suse-rpms/10.0/wesnoth-1.0.2-1.i386.rpm for [[SuSE]] 10.0
** http://www.unixboard.de/files/suse-rpms/10.0/wesnoth-1.1.2-1.i386.rpm for [[SuSE]] 10.0
<br>

'''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''

=== Xandros Linux ===

*This disto for wesnoth-1.1.1 works well with Xandros 3

* 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.1.1-x86-Opkg.tar.gz?download

*Here is a disto for version 1.0.2 that works with Xandros
** [http://www.eskimo.com/~alpinist/Xandros/wesnoth_1.0.2-1_i386.deb

*Here is a disto for version .7 that works with Xandros
**[http://support.xandros.com/downloads/desktop_2.0/user_contrib/boylinux/binary-i386/wesnoth_0.7-1_i386.deb

*Xandros 3 has the distro for wesnoth .9 available through Xandros Networks

=== Yoper Linux ===
All versions built for Yoper 2.2.0-6, although they should install on 2.1.
Please let kernowyon know via the Yoper forums if you get any problems
Latest 1.0.2 version
* http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm
1.0.1 version
* http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm
Earlier version
*http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm

=== Binaries for all distributions ===
* 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.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]
** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz]
** This is NOT a static binary distribution, it resolves dependencies at runtime.
* Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)

=== Other ===
* [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]

= See Also =
* [[CompilingWesnoth]]
* [[Download]]

Community

2006-05-09T12:34:22Z

Xan: Reverted edit of Bobdole, changed back to last version by Allefant

== Forums ==
[http://www.wesnoth.org/forum/ Wesnoth official forum]

== IRC ==
If you don't know what IRC is, check out [http://www.irchelp.org/ irchelp].

* [irc://irc.freenode.net/wesnoth #wesnoth]
* [irc://irc.freenode.net/wesnoth-dev #wesnoth-dev]

You can also see the [http://irclog.wesnoth.org/ logs].

== Mailing Lists ==
* [https://mail.gna.org/listinfo/wesnoth-dev/ wesnoth-dev] ([https://mail.gna.org/public/wesnoth-dev/ archives],[http://lists.nongnu.org/archive/html/wesnoth-dev/ old pre-gna! archives])
* [https://mail.gna.org/listinfo/wesnoth-commits/ wesnoth-svn-commits] ([https://mail.gna.org/public/wesnoth-commits/ archives],[http://lists.nongnu.org/archive/html/wesnoth-cvs-commits/ old pre-gna! archives])

== Wiki ==
[[Create]]

How to play Knalgans

2006-05-09T12:34:21Z

Xan: Reverted edit of Bobdole, changed back to last version by JW

==General Knalgan strategies:==
On the first turn when you have a random opponent it is good to get a mixture of units that will be good in any situation. A Gryphon, a Dwarvish Fighter (DF), a Dwarvish Thunderer (DT), a Poacher, and a Dwarvish Ulfserker (DU) recruit would be an example of such a recruit. When you discover what faction your opponent is, go to the appropriate section below for more advice.

Obviously, you'll want to stay in hills and mountains with Dwarves at all times, unless on village. With Outlaws, stay on non-grass terrain - mostly forests as your Dwarves will occupy the hils and mountains. Use Gryphons to plug other hexes with his 50% defense.

Neutrality and high defense, hp and resists make your Dwarves a powerful force. There is no time they are weak if they are on the right terrain. Your units can endure more blows, and more attempted blows than most other units in the game. Use this to your advantage and finish off the weaker opposing units and then ZOC and heal if you can. Ulfs are great utility killers against any unit with weak or no melee attacks. Remember they cost 19, so use them wisely.

With Knalgans, generally counter-attacks are the best attacks. They can sustain a lot of damage before they die, so the first wave of an opponents attack is likely not to kill any of your units. This will allow you to pick off particular units you wish to get rid of before your opponents next turn. Focus on killing their high damage units first, if possible, if not, kill and weaken as many units as possible to decrease the chances of success for your opponent on his second turn of the attack.

==Knalgans versus Undead==
If you know you're playing against Undead, the smartest thing to do is to recruit an ulfserker. He will automatically kill any Dark Adept (DA) that he attacks. He is also good for taking on Ghosts during day, or even Ghouls. Here are units you will want to recruit to counter Undead units:

[b]Dwarvish Ulfserker:[/b] counters Dark Adepts, and most other UD units in daytime. Don't recruit many unless the opponent has no Skeletons. Skeletons can kill an ulf even in day. Ulfs are also expensive, so you don't want to trade them 1-for-1 with Undead units, unless you get a Ghost.

[b]Dwarvish Fighter:[/b] counters Skeletons, Skele Archers, and is just a good high hp unit that can soak up nighttime damage for your front line.

[b]Dwarvish Guardsman:[/b] Do not recruit this unit if you are fighting Undead. His Pierce damage is less useful than even Blade against Undead. His low damage also makes him a bad unit to counter-attack with.

[b]Dwarvish Thunderer:[/b] This is a good unit to have in your front line in mountains. His 70% defense and decent resists should keep him alive from nighttime Skele attacks, and his 18-1 ranged will make Dark Adepts take a risk to come after you. They are also good to attack Ghosts, as 2 ranged hits will kill them - which even works at night.

[b]Thief:[/b] Do not recruit this unit when fighting against Undead.

[b]Poacher:[/b] A utility unit versus Undead. It's good for finishing Ghosts and killing Walking Corpses. It can also be used to pick at Skeletons and Ghouls. Money is spent better on other units, but don't forget that he may be useful.

[b]Footpad:[/b] This weak character is really only useful versus Undead as a cheap scout. His Impact damage is good against Skeletons and Skele Archers, and he has the added bonuses of being Chaotic (which deals more damage when Undead try to advance at night), and being hard to hit. His best utility is his ranged attack versus Skeletons at night, and that's only 6-2. Recruiting 1 on your first turn to grab villages is likely the only use you'll get from this guy, unless you need a unit to occupy forest hexes (which dwarves do very poorly at 30% defense).

[b]Gryphon:[/b] Probably not the best expenditure of gold versus Undead, but they do serve many purposes that can justify their cost: they give extended view of battle, allowing you to know what is coming and to counter appropriately; they are good for getting behind enemy lines to finish hurt Dark adepts; They serve as good ZOC units for plains and forest hexes. Unlike the Footpad they do not have negative resistance to Blade and Pierce - the weapons of skeletons.

Generally you'll want a good dose of Dwarvish Fighters, a few Thunderers, throw in a Gryphon for vision/utility, an ulf or two, and maybe a Poacher or Footpad. Dwarfs are really what you want to use mostly for their high hp and decent resists. This helps them survive the nightttime onslaught, and their neutrality will give them good damage in defense and also to press the attack at day. Don't be afraid to ulf a ghost in daytime - you won't see the CTK, but it will be good if your ulf is at high hp - and it will be nearly certain if he is Strong.

==Knalgans versus Rebels==
This is one of the trickiest matchups to play. Both factions are Neutral, so neither has an advantageous time of day to attack (with their main units). To win this battle you will need smart recruits and good unit placement, as well as a little luck; the same goes for your opponent. Knalgans have what I would consider a slight advantage with the "one unit must die" Ulfsersker, but Rebel defense as well as heal, slow, and magic could factor to your demise. Look for opportunities grab mountains and hills, especially if the have no forest next to them. Forests are your biggest enemy, so occupy them with your Outlaw counterparts or Gryphons.

[b]Dwarvish Ulfserker:[/b] counters Mages, Elvish Shaman, and often times Elvish Archers. Again, don't recruit too many of these, as Elvish Fighters will easily come back to finish you up, and they are 5 gold cheaper. If you get a chance to take out a mage, do so. Not only will you gain 1 gold in attrition, but another unit will likely have to expose itself or get hurt to finish you off. Elvish Archers should be #2 on the "to kill" list, and they are sometimes worth jeopardizing your ulf for if you catch one of them off of forest. Again, the reasoning is you only lose 2 gold in the trade and the opponent must waste moves and usually hp in order to finish you. Again, they may also expose themselves. You might be able to get away with ulfing Woses if it's nighttime and you're in mountain. Make sure he isn' a Quick, Intelligent Ulf, and check the CTK as always.

[b]Dwarvish Fighter:[/b] Again, these are the meat of your forces. Any front without one of these will succumb to Elvish Fighters. Dwarfs beat Elves 1-on-1, but they are more expensive. They are good damage soakers and damage dealers. Stay on preferred terrain at all times.

[b]Dwarvish Guardsman:[/b] Guardsmen are great for holding frontline villages and chokepoints - with backup. A lone Guardsman can hold out for a turn, if lucky 2 or 3, while on a town, but he deals very little damage in return, especially against the ranged specialized Rebels. Recruit 1 if necessary, and no more than 2. They just aren't worth the lack of offensive/counter-attack units.

[b]Dwarvish Thunderer:[/b] Another staple. This unit is great against Rebels with luck. Stick him on a mountain and Elves will hurt themselves trying to remove you. They aren't so great for dependable offense, but their counter-attacks are great.

[b]Thief:[/b] Unlike when fighting Undead, you'll want 1 or 2 of these guys depending on your play style. At night, a combo of thieves can destroy Woses, Elvish Archers, Mages, and Shaman. Keep them in the forest hexes your opponent will want, but not in daytime.

[b]Poacher:[/b] I like using Poachers to fill up forest hexes and to attack Elvish Fighters. Their main usefulness is as a counter-attacking utility unit to grab forest and press at night. They are cheap, somewhat weak, but deal more dependable offensive damage than the Thunderer. 5-4 at night is equivalent to a 17 gold Elvish Archer, and you only spend 14.

Whichever Chaotic unit if any you use, make sure to protect them at day.

[b]Footpad:[/b] Don't recruit this unit when fighting Rebels.

[b]Gryphon:[/b] These monsters are more useful against Rebels than Undead. Their utility lies in fighting any water battles against the weak Merman Hunters, scouting, taking opportunistic attacks agaist poorly placed Elves, and if you find a hurt Wose, you may cosider attacking one - even though Gryphons have a weakness for Impact. At night they do essentiall equal damage to each other, and you may not be able to get the finishing blow with one of your slower units. Do so as a calculated risk when you only need 1 hit to kill. Otherwise it's quite a risk.

Recruit a Gryphon (maybe 2 if there's enough water or the towns are spread out) first turn along with a mix of DFs, DTs, a DU, and perhaps a DG, or some Outlaws. If your opponent purchases scouts, feel lucky - they are next to useless against you. Beware of ambushes, and don't scout unsure forests with your Gryphon in daytime. Take as much tactical forest as you can with the appropriate units, and make a stranglehold on mountains. Ulf when you get a good chance, and be ready to counter in day as well as pressing at night. Each battle will play out differently in this matchup according to what your opponent recruits, so see what he has early, and keep track of any Woses. Also, do not let your Ulf be slowed or he is certainly dead.

==Knalgans versus Drakes==
These guys are big and nasty. They will burn and freeze you. Thunderers will be your main weapon, but he will require support units as well.

[b]Dwarvish Ulfserker:[/b] Good for killing Augrs, scouts, and maybe Burners. Not really a good choice against Drakes in general, but can serve purposes.

[b]Dwarvish Fighter:[/b] A good unit to use against saurians, but generally the DF is not how you want to go against Drakes.

[b]Dwarvish Guardsman:[/b] Guardsmen are worth the price against Drakes. They're Pierce goes through their resistance, and a Strong one actually gets an additional point of damage on top of the point he gets for having the Strong trait (but not against Clashers). A couple of these are an alright buy, especially if you plop them on villages.

[b]Dwarvish Thunderer:[/b] This should be your unit of choice versus Drakes. A DT does 20-1 damage to Drakes in ranged, and Burners will do (6/5/3)-4 damage in return. DTs have much better defense than Burners, but do suffer from having 8 less hp. DTs have the benefit of costing 4 less gold though. You'll want to use their "luck" attack on the easily hit Drakes as much as possible. Thunderers should be the meat of your army.

[b]Thief:[/b] Not really useful against the Drakes, they are best used to counter Saurian Augrs, which are better countered by using Dwarven Fighters. No real need to recruit any.

[b]Poacher:[/b] Another great unit against Drakes. Their attack at night deals a good 5-4 against all Drakes. Having better defense on Forest and villages, 1 or 2 of these guys aren't a bad idea.

[b]Footpad:[/b] Don't recruit this unit when fighting Drakes.

[b]Gryphon:[/b] Useful for early village grabbing, Gryphons also can be used against the weak Saurians or Drake Burners. These flyers are probably the only way you'll hunt down retreating hurt Drakes. Don't recruit too many due to their cost and lack of a ranged defensive weapon. Drakes can ZOC these units far better than any other faction.

Recruit a Gryphon, and a good mix of DTs, DGs, a Poacher or 2, and maybe a DF. Your opponent will likely get some Saurian mages to take away your high defense advantage, so having that DF around to take them out is usually quite helpful along with the Gryphon. Basically, recruit Pierce, Pierce, and more Pierce. Maintain your advantageoud defensive terrain as much as possible, because if you don't, and you put yourself on an even playing field in that respect, you will quickly be torn apart by the Drakes superior daytime damage and hp. The daytime onslaught will be brutal, so prepare for a counter-attack and try to keep your Guardsmen up front to utilize their Steadfast. It will be the difference between 7-4 and 6-4 daytime Burner damage and 6-4 to 5-4 daytime non-Strong Clasher damage. The Guardsmen also have 8 more hp than the Thunderers. If you can level a Guardsman (with 4 kills at 70% xp, or 3 kills and 1 battle if he's Intelligent), you will have a nearly undefeatable roadblock to use at your disposal.

==Knalgans versus Knalgans==
A tough battle. Dwarves have great defense, and no way to combat great defense. The high hp and the resists will make this a game needing a lot of strikes to kill. Don't think you'll be able to rush in and win - you're going to need intelligent unit placement and again, some luck. Focus on levelling (non-Gryphon) units if possible as the added damage will be needed.

[b]Dwarvish Ulfserker:[/b] As always, one of these utility guys isn't a bad buy. Catch a thunderer off his perch, or a Thief or Poacher in daytime, and that's one less unit to deal with.

[b]Dwarvish Fighter:[/b] One of these is a must. Use it against any unit. These guys are hard to kill.

[b]Dwarvish Guardsman:[/b] Use these to hold villages and frustrate your opponent.

[b]Dwarvish Thunderer:[/b] Use these to siege enemy villages or poke at DFs or Gryphons.

[b]Thief:[/b] Not a good buy unless used to counter Thunderers and Poachers. Their Blade attack does little to Dwarves unless backstabbing at night (8-3). Better to use DFs for melee.

[b]Poacher:[/b] An alright cheap buy for ranged forest grabbing.

[b]Footpad:[/b] Don't buy this unit even if your opponent is bothering you with Gryphons. You can get 3+ Footpads for the price of 2 Gryphons, but it's not worth it. The weakness to Impact guarantees at least a 4-2 attack with these guys even in daytime, but unfortunately, unless you get bonus hp from traits, they will die in 2 hits from Gryphons, so it is still a risky buy - especially since they are useless against all other Knalgans. Just say no once again.

[b]Gryphon:[/b] Useful as yuor only scout unit. Use these to get behind enemy lines to village steal, kill the wounded, or to ZOC a Dwarf on bad terrain. These guys are also good forest and plains holders for crucial areas that your Dwarves will fare poorly on.

Recruit a Gryphon, a DG, a DT, a DF, probably a DU, and a mix of other useful units. This game will be won through maintaining the hills and mountain, getting and keeping a money advantage, levelling a unit, and by waiting for your opponent to take a risk that they shouldn't. Keep them off of your mountains at any cost. If they get there you will spend precious moves, attacks, and hp trying to take them off. It's usually better to ignore enemies on mountains than to fight them.

==Knalgans versus Loyalists==
Defend in day, strike at night. That's how the battle will go. Beware the Horseman and Mage and be prepared to counter these heavy daytime hitters.Again, an Ulf can be your best friend, especially if you can catch a Horseman at night or a Mage.

[b]Dwarvish Ulfserker:[/b] If you get one, don't get it until turn 2 or later. Grabbing one in your initial recruit will only make him be impotent during the first few truns of daytime. Ulfs you will use to kill Mages, grind up horse meat at night, as well as get rid of Bowmen - though they shuoldn't be recruiting many. You shouldn't need more than 1 unless they go mad with Mages.

[b]Dwarvish Fighter:[/b] Good to fight Spearmen, having these guys is a necessity. These are also your best unit to defend against Heavy Infantry.

[b]Dwarvish Guardsman:[/b] Get one of these guys. These will make your front line immune to Horsemen. Also useful to counter-attack Cavalry, Mages, and Bowmen. If HI get close enough, milk xp off of them with your ranged. The level will come faster than you expect.

[b]Dwarvish Thunderer:[/b] Get 1 or 2. Good against essentially all of the Loyalist units, the Pierce ranged is even better against the 2 mounted units.

[b]Thief:[/b] These guys can be used against most Loyalist units at night, but avoid trying to backstab Spearmen. Even at night their firststrike can get nasty on this low hp unit. I recommend the Poacher instead of this guy.

[b]Poacher:[/b] A great unit to counter-attack Loyalists and press at night. His multiple strikes are of better use against the high defense Fencer, though his ranged Pierce is best against the mounted units. His attack does a modest 3-4 to HI at night (compared to a Thunderers 11-1), and this unit that you'll want to use against Spearmen outside of day as well. Although they will be weak during day, they serve many purposes and are well worth the 14 gold.

[b]Footpad:[/b] Do not recruit this unit when fighting Loyalists.

[b]Gryphon:[/b] Useful as scouts mainly, you can use these to run down hurt horses, go for 1-attack-kills on Fencers (9% chance if they have no bonus hp), or again, to try to hold important grassland hexes. Beware during day though, as HI, Mages, and Horsemen can all tear Gryphons apart quickly. Recruit no more than 1.

Recruit a DF, a DT, a DG, and a Gryphon depending on the layout of villages. Fill out your army with what you think will serve you best for that particular battle. Water battles will be nearly pointless. Cheap Mermen with higher defense will easily rout your Gryphon(s). Avoid sea battles unless you can taunt a Merman within range of a ranged unit (who can stand on decent terrain). A Gryphon's extra sight is good for spotting long range Horsemen, so it usually is worth having one around, but recruit no more than one. They don't counter any unit very cost-efficiently, so use it primarily as a scout and utility unit.

You'll want to press as hard as you can at night, moreso than even against Drakes. The reason for this is that Loyalists have no level 1 Neutral or Chaotic units. Every unit the opposing player has will suffer a penalty at night - unless he has a Sergeant behind his front line. Because of this possibility, don't press too close to his castle until you have maintained a monetary advantage, as you will start losing units more rapidly when he comes back at you with an additional +25%. Put your guardsman up front - this will dissuade any Charges. Keep a DF or DU nearby in case the player chooses to siege you with Mages. Spearmen that attack a DG in day will deal nearly equal damage to each other, which can add up quickly. counter any advance with Thunderers and Poachers. Don't expose your Dwarves to poor terrain or they will die.

You'll want to whittle away at HI with Poachers and DTs and you'll want to give the killing blow to a Fighter. Upgrading DFs should be your #1 priority as they are your best defense and counter to the easy Spearman spam. The massive hp on the level 2 will also give it the ability to withstand attacking HI and Mages.

Basically, Loyalists have an incredible amount of versatility. You'll have to play smart and counter-attack very well in order to win. Deal free damage when you can, and limit the number of hexes you can be attacked from - especially during day. Start commencing your attack before night actually breaks. You'll want to maximize your advantage over those 2 turns, so make sure they don't creep away before night hits. As always, stay on good terrain, and make sure Fencers can't skirmish around to kill any weak units you may be hiding.

==Knalgans versus Northerners==
They biggest problem you will have with Northerners will be their numbers. Northies will gladly trade units with you and gain a monetary advantage. Make them depend on luck by staying on good terrain, and their high upkeep may start to become a factor.

[b]Dwarvish Ulfserker:[/b] Recruit one of these guys if you're really having a problem finishing their units off, or your opponent likes to use Assassins. He's expensive, and Northerners and melee oriented, so most of their units will be able to take a majority of this units hp away, if not kill him. Assassins Poison will quickly deteriorate your army's hp though, so having one may prove valuable. Since Assassins cost 17 gold you'll only lose 2 in attrition, and you'll likely take lots of hp from another unit with you.

[b]Dwarvish Fighter:[/b] Again a necessity. His damage dealt in defense is how you'll deal a majority of your damage. If possible, get a rotation of these guys in the front line. You'll deal more damage than your opponent on average, but he will come with more units - 4 Grunts cost the same as 3 DFs.

[b]Dwarvish Guardsman:[/b] Another good guys to have 1 of if not more. He can survive nighttime assaults better than the fighter, and will still do respectable damage back to the enemy. Use your ranged attack on Grunts to make them turn around and heal.

[b]Dwarvish Thunderer:[/b] Nice to have. Their combination of good resists and ranged damage make them good counter-attackers. For cheaper ranged counter-attackers, use Poachers as they will also be used to hold forest hexes. Recruiting DTs may crowd your hill hexes, especially since that's what the Northies will be grabbing.

[b]Thief:[/b] Not a great buy against Northies. His melee only nature along with his Chaotic alignment make him most effective in the same way Northeners are. Avoid the urge to recruit these guys.

[b]Poacher:[/b] Again, these guys you'll want to recruit a few of. When the Northies come after you at night, you can make a strong counter-attack with their 5-4 ranged.

[b]Footpad:[/b] This guy can be a utility unit against Northerners, but the money is better spent elsewhere. Footpads can harass Grunts and Wolfs, take forest hexes, and block Assassins from poisoning your Dwarves. Not the best buy, but you may be able to get your money's worth.

[b]Gryphon:[/b] Again, it's usually good to have one of these guys to scout, plug up grassland, and be a defensive damage dealer. He's also good for trapping/killing Assassins and being a target for their poison.

The biggest thing you need to worry about will be Poison. If you get a good foothold on mountains and hills, Poison will be the weapon of choice to knock you offyour perch. Be ready to fill in with a replacement unit, and try to kill assassins before any other units. Melee strikes will have to get through your resistance - poison does not. You also don't deal any damage back when poison hits you.

Recruit a DF and a mix of other good units. Stay on towns or mountains for the first assault to minimize the effect any poison will have and reduce the chance of it hitting. Let your opponent attack you, and then counter-attack with your Poachers and DTs if you have them - even DGs ranged will add up. Ulf Assassins whenever you get a decent chance, as the Poison will hurt more than their melee attacks.

Allow your opponent to attack you from forest hexes if they are next to mountains that you occupy. Your 70% defense will outdo his 50% defense, and his confidence will be higher to attack since he won't be on grass. Even if an Assassin uses that hex, if an Ulf is within reach, he should be able to take him out from on top the mountain.

To kill Trolls, you will want to focus exclusively on them until they die. It is best to ignore them and kill others than to only do a minimal amoun of damage to Trolls each turn. Their regeneration will give them essentially limitless hp if you do this. Kill his friends and then focus on him. If there are several, take them out one at a time. Try to avoid water battles with Nagas, unless there is only 1. You won't want any Gryphons you get to be ZOCd, especially where you cannot help them, so be cautious with water battles.

To sum up, kill poisoners, get units that deal good melee damage in defense, and get good counter-attacking ranged units

Back to The "How to play..." Series.

ReportingBugs

2006-05-09T12:34:18Z

Xan: Reverted edit of Bobdole, changed back to last version by Allefant

== Where to report bugs ==
The prefered way to report bugs is through our bug tracking system on Gna, but you can also post your problem to the forums.
* [http://bugs.wesnoth.org/ Wesnoth bugs page on Gna]
* [http://www.wesnoth.org/forum/viewforum.php?f=4 Wesnoth forum - Technical Support]

== Needed information ==
* What version of the game are you running?
* Have you built (from sources) the game by yourself? gcc/g++ version? SDL library versions?
* What operating system are you using? What version/release of that operating system?
* Can you reproduce the problem? If you can please provide steps to do it.
On special request another note: Use common sense! If you know the information can't be relevant to your report simply omit it.

== Guidelines for reporting bugs ==
# First, please make sure the bug you are reporting has not already been fixed (consult http://changelog.wesnoth.org/ to see the history of changes to the game).
# If it hasn't been fixed yet, please check that the bug hasn't already been reported, by [bugs.wesnoth.org].
# If your bug or feature request hasn't been fixed and has not yet been submitted, please go ahead and report it.
# Please post only one bug per bug report. If you have multiple bugs that are related, you can cross reference them.

Note that feature requests should usually be discussed on the forums first, or they will generally be ignored until there is evidence that such a feature would be generally liked.

Keep bug reports to the point, and make sure your bug is easily reproducible given the information you provide. Clearly written, reproducible single bug reports will get attention before those reports that mix several different bugs into one report, or that are incomprehensible.

If there is already an existing bug report, do not hesitate to add a comment with your details - this way we know when some bug is getting "popular".

''Please login to Gna! before reporting bugs''

An account at Gna! is free and takes very little time to set up. You can submit anonymous bug reports, but then you will have to keep an eye on the bug report in case developers ask for clarification, which will delay your bug being fixed. If you login, you will receive notifications of any changes to your bug reports, which speeds things up considerably.

=== In-play problems ===
If it is in-play problem that you can reproduce, save the game and send the savegame to us with details how to reproduce the problem from the savegame.

=== Problems with scenarios ===
If it is a problem with a contributed scenario (like the ones on the Campaign Server), please report the problem to the maintainer of the scenario, not as a bug in Wesnoth itself. Bugs in the [[MainlineScenarios]] should be reported in the bug tracker.

=== Multiplayer out-of-sync errors ===
* We need wesnoth stdout/stderr output from person who got the error (if you started wesnoth in terminal stdout/stderr is in that terminal).
* We need savegame from person who got the error.
* Savegame from some other player if possible.
* The person who got the error should report the bug, other players can then add their savegames to that bug.

=== Segfault ===
* In Unix follow the instructions at [[DebuggingWesnoth]] to generate information to send to a developer.
* In NT based OS's (including Win2k, XP) you enable/configure core dumps by running 'drwtsn32', the location of the dumps can be changed there.
* In Mac OS X, you can enable Crash Reporter -- the output is a backtrace. Run Applications -> Utilities -> Console to see log output. See http://www.mozilla.org/mailnews/osxinfo.html for information on how to enable Crash Reporter.

=== Sending savegames, screenshots, coredumps, etc ===
* Please compress the files (bzip2, gzip, zip).
* You can attach files if you submit your bug through Gna!, else
* Put them on some web or ftp server where we can download them.
* You can attach files to forum posts.
* As a last resort you can send them via email to: [mailto:davidnwhite_AT_verizon.net]

== Bug protocol ==

* When adding a new bug, please choose either "Bug" or "Feature Request" as its Category; it may not be noticed if you leave the Category as "None".
* We use the Status values "None" (awaiting action), "Fixed", "Won't Fix", "Invalid" (not a bug), "Works For Me" (unreproducible), or "Need Info".
* A bug which is fixed is marked "Fixed" by a developer, probably the one committing the fix or reviewing it.
* A bug present in a release is marked "Closed" only upon a new release containing the fix.
* Any bug present only in [[WesnothSVN]] is marked "Closed" when it is fixed.

GettingStarted

2006-05-09T12:34:18Z

Xan: Reverted edit of Bobdole, changed back to last version by Allefant

Download

2006-05-09T12:34:15Z

Xan: Reverted edit of Bobdole, changed back to last version by Allefant

Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here.

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. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.0.x_branch.29|Stable Branch]] | [[Download#Development|Development Branch]]

== Stable (1.0.x branch) ==
The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.0.x branch is compatible to each other. This will not happen in the development branch.

Version 1.0.2 is the latest stable version, updated with several important bugfixes. This version is recommended for most players since the 1.0.x online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Source code ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.2.tar.gz?download Current stable version] (1.0.2, 38.2 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== [[BeOS]] ====
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0.2-BeOS-x86.pkg.zip?download Current stable version] (1.0.2, 42.3MB)

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

==== Mac OS X ====
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.0.2.dmg?download Current stable version] (1.0.2, 53.6 MB)
* [http://lwa.retiaire.org/wesnoth/Wesnoth_MacOSX_1.0.2-lwa.dmg Current stable version - alternate] (1.0.2, 44MB)
* [http://lwa.retiaire.org/wesnoth/Wesnoth_MacOSX_1.0.2_lite-lwa.dmg Current stable version - lite] (1.0.2, no art or music, 25MB)

==== MS Windows ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-windows-1.0.2.exe?download Current stable version] (1.0.2, 37.0MB)

==== FreeBSD ====
* /usr/ports/games/wesnoth (1.0.1, 37.3MB)

==== Miscellaneous ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.0.2.tar.gz.md5?download Source code md5sum]
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth-1.0.2-BeOS-x86.pkg.zip.md5?download BeOS md5sum]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code Xdelta for the source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#MS_Windows Xdelta for the Windows binary]

== Development ==
Version 1.1.2a is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.0.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth.

==== Source code ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.2a.tar.bz2?download Current Version] (1.1.2a, 59.7 MB)
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.1.tar.gz?download Previous Version] (1.1.1, 50.7 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-windows-1.1.2a.exe?download Current Version] (1.1.2a, 55.9 MB)
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-windows-1.1.1.exe?download Previous Version] (1.1.1, 45.1 MB)

==== Mac OS X ====
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.2a.dmg?download Current Version] (1.1.2a, Universal, 68.7MB)
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.2a1_lite.dmg?download Current version - lite] (1.1.2a, Universal, no art or music, 38.2MB)
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.1-lwa3.dmg?download Previous version] (1.1.1, PPC only, 65.2 MB)
* [http://prdownloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.1.1_lite-lwa.dmg?download Previous version - lite] (1.1.1, PPC only, no art or music, 46.1 MB)

==== GNU/Linux ====
* 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 the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== AmigaOS4 ====
* [http://www.os4depot.net/share/game/strategy/wesnoth_exe.lha Previous version - exe] (1.1.1 - game, 4.7MB)
* [http://www.os4depot.net/share/game/strategy/wesnoth_data.lha Previous version - data] (1.1.1 - data files, 10MB)

==== Miscellaneous ====
* [http://prdownloads.sourceforge.net/wesnoth/wesnoth-1.1.2a.tar.bz2.md5?download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code Xdelta for the source code]
* [http://sourceforge.net/project/showfiles.php?group_id=89495 SourceForge page for current and all previous versions]

== 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]]
* [[WesnothSVN]] - bleeding edge version from SVN

Create

2006-05-09T12:34:15Z

Xan: Reverted edit of Bobdole, changed back to last version by Allefant

Description

2006-05-09T12:34:13Z

Xan: Reverted edit of Bobdole, changed back to last version by Allefant

== What is Battle for Wesnoth? ==

The Battle for Wesnoth is a turn-based strategy game with a fantasy theme.

<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-0.8.4-halo.jpg http://www.wesnoth.org/images/sshots/wesnoth-0.8.4-halo-175.jpg]
<div class="thumbcaption">Silver Mage in action</div></div>
</div>

Build up a great army, gradually turning raw recruits into hardened veterans. In later games, recall your toughest warriors and form a deadly host against whom none can stand! Choose units from a large pool of specialists, and hand-pick a force with the right strengths to fight well on different terrains against all manner of opposition.

Wesnoth has many different sagas waiting to be played out. Fight to regain the throne of Wesnoth, of which you are the legitimate heir... step into the boots of a young officer sent to guard a not-so-sleepy frontier outpost... vanquish a horde of undead warriors unleashed by a foul necromancer, who also happens to have taken your brother hostage... guide a band of elvish survivors in an epic quest to find a new home.

200+ unit types. 16 races. 6 major factions. Hundreds of years of history. The world of Wesnoth is absolutely huge and limited only by your creativity - make your own custom units, compose your own maps, and write your own scenarios or even full-blown campaigns. You can also challenge up to 8 friends - or strangers - and fight in epic ''multi-player'' fantasy battles.

== Features ==

<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-0.8.4-burningsuns.png http://www.wesnoth.org/images/sshots/wesnoth-0.8.4-burningsuns-175.jpg]
<div class="thumbcaption">Under the Burning Suns</div></div>
</div>

* Build up a formidable fighting force, starting from a single leader and a small amount of gold.
* Over 200 unit types in six major factions, all with distinctive abilities, weapons and spells.
* Experienced units gain powerful new abilities as they advance.
* Several multi-player options available, including internet play.
* Scores of different custom-designed maps, and unlimited random maps.
* Hundreds of campaign scenarios available for download via a simple in-game procedure.
* 'Fog of war' feature available for a true test of generalship.
* Sophisticated mark-up language lets advanced users make their own maps, factions or campaigns.
* Excellent language support – 20 different languages currently available.
* GNU/Linux, Windows, MacOSX, BeOS, Solaris, FreeBSD, OpenBSD and NetBSD compatible.

{{Play}}

Play

2006-05-09T12:34:12Z

Xan: Reverted edit of Bobdole, changed back to last version by JW

== Getting Battle for Wesnoth ==
* [[Description|About the project]]
* [[Download|Downloads and Source Code Page]]
* [[CompilingWesnoth| Compiling Wesnoth]]

== Playing Battle for Wesnoth ==
<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-1.0-urug.jpg http://www.wesnoth.org/images/sshots/wesnoth-1.0-urug-175.jpg]
<div class="thumbcaption">The Elves Besieged</div></div>
</div>

* [[GettingStarted|Get Started]]
* [[WesnothManual|Game Manual]]
* [[BasicStrategy|Basic Tactics]]
* [[MainlineScenarios|Walkthroughs of Official Campaigns]]
* [[UserScenarios | User-made Add-On Campaigns]]
* [[FAQ]]

== Advanced Players ==
* [[CommandMode|Debugging and Multiplayer Command Reference]]
* [[AdvancedTactics|Advanced Tactics]]
* [http://wesnoth.slack.it/units.cgi Units Reference] (temporarily messed up)
* [[MultiplayerServers|Multiplayer Servers]]
* [[How to play...|The "How to play" Series]]

== The world of Wesnoth ==
<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-map-1.jpg http://www.wesnoth.org/images/sshots/wesnoth-map-1-175.jpg]
<div class="thumbcaption"> Wesnoth and Surrounding Lands</div></div>
</div>

* [[WesnothHistory|The history of Wesnoth]]
* [[WesnothGeography|The geography of Wesnoth]]
* [[RaceDescriptions|The races of creatures in Wesnoth]]
* [[WesnothPoetry|Wesnothian poetry]]

== Miscellaneous ==
* [[WhatArePlayersSaying|Comments from Wesnoth Players]]
* [[WesnothReviews|Third party Wesnoth reviews]]
* [[Screenshots]]
* [[FAQ#Do_you_want_help_making_this_game.3F_How_can_I_help.3F|Help to improve the game]]

__NOTOC__
{{Home}}

AiWML

2006-05-09T12:34:11Z

Xan: Reverted edit of Bobdole, changed back to last version by Placid

{{WML Tags}}
== AI phases ==

When the AI does its turn, it has several 'phases'.
In debug mode, these phases are shown in the upper-left corner.

=== Combat phase ===
It decides who is in range to attack, and whether it's worth attacking them

=== Healing phase ===
It locates injured units and sees if they can be moved to villages to heal

=== Village capturing phase ===
It locates units, and sees if they are in range of villages which they can capture

=== Retreating phase ===
It sees if any units are in grave danger/hopelessly outnumbered, and if they are, it retreats them

=== Movement/targetting phase ===
It decides upon 'targets', assigns those targets values, and moves units toward targets based on how easy it is to get to the targets, and how valuable the targets are.

== the [ai] tag ==

The [ai] tag is used inside a [side] tag, and it's contents define how the AI controlling that side acts. You can use multiple [ai] tags and have them apply during different turns or times of day, for example to set an undead side's caution higher and aggression lower during the day, or to boost the aggressiveness of a side when they receive reinforcements on a specific turn.

The following key/tags can be used in an '''[ai]''' tag:
* ''time_of_day'' the time(s) of day when the AI should use the parameters given in this [ai] tag. Possible values are listed in data/schedules.cfg (See [[TimeWML]]).

* ''turns'' during which turns the AI should use the parameters given in this [ai] tag. This takes the same syntax of dashes(-) and commas(,) as is described under Filtering Locations in [[FilterWML]], except of course they apply to turns not locations.

* ''ai_algorithm'' allows an alternate AI algorithm (cannot be created with WML) to be used. Besides the default, the game comes with only ''idle_ai'', which makes the AI do nothing and can be used to create a passive, unmoving side. Cannot be applied only to a set of turns or a given time of day using the keys ''turns'' and ''time_of_day'', but must be given either in an [ai] tag without the aforementioned keys or outside [ai] tags inside the [side] tag.

* ''recruitment_pattern'' This key takes a list containing the possible inputs 'scout', 'fighter', 'archer', 'healer' and 'mixed fighter'. This tells the AI in what order it should recruit different types of units. The AI considers each unit to be one of these types. The type is listed in the unit file in data/units/ (See also [[UnitWML]]).

<ul><li> ''aggression'' This key affects how an AI player will fight.
<br>
It determines how an AI considers the difference between its units and its opponents
by taking the value ''1 - AI unit value in proportion to opponent unit value''.
('Unit value' here means that the AI weights its decision on the chance to kill
a unit or be killed, using a combination of its own units.)
So, to make an AI which considers its units worthless i.e.
only cares about how much damage attacks inflict,
set aggression at ''1 - 0 = 1.0''.
This is the highest meaningful value for aggression; although it is insane, it is used on many HttT levels.
If an AI set on this value can inflict 1 damage and take 0, or inflict 2 damage and take 20 himself,
he'll take the latter option.
To make an AI which considers its units equally as valuable as its opponent's i.e.
only attacks if he feels he can inflict more damage than he receives,
set aggression at ''1 - 1 = 0.0''.
Although an AI which considers its opponent's units worthless is impossible under this scheme,
an AI which, for example, considers its units twice as valuable as its opponent's
can be represented by aggression ''1 - 2 = -1.0''.
having to be able to inflict more damage than he takes for it to be worth his while.
The default is ''1 - 1/2 = 0.5'', which means the AI is content with dealing only
half the damage to his opponent of that which he himself takes.
</ul>

* ''caution'' A number 0.0 or higher (default=0.25) that affects how cautious the AI is in various ways. If it is higher, the AI will want to retreat more (especially to a better defensive terrain), it will dislike moving out of a defensive terrain to attack more, and, if grouping is enabled, it forms bigger groups to protect from enemies when going to a target.

* ''village_value'' A number 0 or higher (default=1) which determines how much the AI tries to capture villages.

* ''leader_value'' A number 0 or higher (default=3) which determines how much the AI targets enemy leaders.

* ''villages_per_scout'' A number 0 or higher which determines how many scouts the AI recruits. Defaults to 4. If 0, the AI doesn't recruit scouts to capture villages.

* ''recruitment_ignore_bad_movement'' if 'yes', the AI will not analyse the terrain to see if the unit is suitable for it.

* ''recruitment_ignore_bad_combat'' if 'yes', the AI will not analyse the units the enemy has fielded to see if the unit is suitable for fighting them.

* ''passive_leader'' if 'yes' the AI leader will never move or attack, except to obey [leader_goal]s.

* ''attack_depth'' a number from 1 to 6, default 5. This is how many units will be thought about to attack a single unit. If the attack is completed, the AI on another round of thinking may still decide to attack that unit again with other units. Note that in battles, a unit usually can't be attacked from all six sides anyway, so any high attack_depth will be about the same. If attack_depth is low, the AI won't want to attack unwounded units very much, because it doesn't think it can kill them in the attack.

* ''simple_targetting'' When the AI decides what targets to move towards with which units, it considers all its units that can move, sequentially. For each unit, it decides what the best target for it to go towards is. If not 'yes', it will check if any other units would be better to go towards that target than the unit it is currently considering.

* ''scout_village_targetting'' The AI multiplies the value of village targets for scouts by this value. The default is 3.

* ''grouping'' how the AI should try to group units
** 'offensive' (the default): Makes the AI try to group units together before attacking.
** 'defensive': Makes the AI group units together very conservatively, and only advances much beyond its castle if it has overwhelming force.
** 'no': Makes the AI not use grouping behaviour. This is what it used to be like.

* ''protect_leader'' and ''protect_leader_radius'' - the way these parameters work, is to target any enemy units that come within 'protect_leader_radius' of the AI leader with a value of 'protect_leader' on the units. The default for these values are 1.0 and 20.

* '''[protect_location]''' gives the AI a location to protect. Note that the AI will NOT station any units around the location, it will only send units to attack any enemy units that come within the guarding radius of the target.
** ''x'', ''y'' standard coordinates. These indicate the location the AI is protecting,
** ''radius'' indicates the radius around it to protect
** ''value'' indicates the importance of protecting this location

* '''[protect_unit]''' gives the AI a set of units to protect. Note once again that the AI will not place units around the unit if there are no enemies nearby.
** standard unit filter- the unit(s) to protect
** ''radius'' indicates the radius around it to protect
** ''value'' indicates the importance of protecting this unit

* '''[target]''' Any number of [target] tags can be used to set a target for the AI. For anything related to 'values', set them relative to other targets. An AI is willing to dedicate twice as many resources and travel twice as far to get a target worth '2.0' as it is a target worth '1.0'.
** standard unit filter
** value: A number greater than 0 (default=1) which determines how much the AI tries to kill all units which pass the filter.

* '''[avoid]''' Makes the AI avoid a specific location or unit.
** ''x'', ''y'' standard coordinates- A location for the AI to avoid moving to. The AI will never move a unit to this location except for trying to move its leader to a keep.
** standard unit filter- A set of units for the AI to avoid moving to. This feature is currently not implemented.

* '''[leader_goal]''' Makes the AI try to move its leader to a specific location (as in the goal of The Elves Besieged).
** ''x'', ''y'' the location for the AI to move its leader to

== See Also ==

* [[ReferenceWML]]

Template:WML Tags

2006-05-09T12:34:10Z

Xan: Reverted edit of Bobdole, changed back to last version by Allefant

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

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

Support

2006-05-09T12:34:06Z

Xan: Reverted edit of Bobdole, changed back to last version by Allefant

__NOTOC__
There are many ways to get help. From online documentation to support from the community on IRC or forums.

== Wiki Resources ==
* [[Play|Online Players Guide]] - game manual, walkthroughs, strategy guides, and more
* [[Create|Content-Creation Guide]] - manual showing how to create new campaigns for Wesnoth

== Reporting Bugs ==
If you are experiencing problems, you should consider [[ReportingBugs|reporting a bug]].

== Community ==
=== Forums ===
* [http://www.wesnoth.org/forum/ Wesnoth official forum]
* [[WesnothAcronyms|Wesnoth Acronyms]] - forum lingo - [[WesnothAcronyms%28alphabetic%29|(in alphabetical order)]]

=== IRC ===
If you don't know what IRC is, check out [http://www.irchelp.org/ irchelp].

* [irc://irc.freenode.net/wesnoth #wesnoth]
* [irc://irc.freenode.net/wesnoth-dev #wesnoth-dev]

* [irc://irc.tweakers.net/wesnoth #wesnoth (Dutch channel)]

You can also see the [http://irclog.wesnoth.org/ logs].

=== Mailing Lists ===
* [https://mail.gna.org/listinfo/wesnoth-dev/ wesnoth-dev] ([https://mail.gna.org/public/wesnoth-dev/ archives])
* [https://mail.gna.org/listinfo/wesnoth-commits/ wesnoth-commits] ([https://mail.gna.org/public/wesnoth-commits/ archives])

=== Other Servers List ===
see [http://www.wesnoth.org/wiki/MultiplayerServers here]

{{Home}}

Distributing content

2006-05-09T12:33:53Z

Xan: Reverted edit of Bobdole, changed back to last version by Drake Raider

== The Forum ==

The [http://www.wesnoth.org/forum/ BFW forum] is a good way to distribute small creations, like single multiplayer maps. Larger creations, like unit packs or campaigns, should be compressed before uploading them. Note that you may encounter a size limit on attachments.

Also, there is a [http://www.wesnoth.org/forum/viewtopic.php?t=2014 legal announcement] that you should read before distributing anything on the forum. Basically, by posting you say that you own the license to what you are posting, and that you are licensing it under the [http://www.gnu.org/copyleft/gpl.html General Public License].

== The Campaign Server ==

The campaign server is the preferred way to distribute your creations, but it is more suited for larger projects. It currently lacks advanced organization features such as filtering and reviewing, so adding hundreds of little things makes it harder to find anything. Basically, the server should not be used to post single maps, units, songs, or artwork, but map packs, campaigns, entire eras, music packs, and unit packs are fine.

Once you are ready to publish, here is how you access the campaign server:
# Open Wesnoth
# Select "Campaign" from the main menu
# Select "Get More Campaigns" (the last entry in the list of campaigns)
# Select "Publish Campaign: ''Your Campaign Name''" (the last entry in the list of campaigns)

Anything you distribute on the server will be upload from and downloaded to the ''userdata''/data/campaigns directory regardless of what it is (units, maps, campaign, etc). For this reason, you need three things in the campaigns directory to distribute via the server:
# A .cfg file, for example MyCampaign.cfg
# A .pbl file, for example MyCampaign.pbl
# A folder, for example MyCampaign

==== General Reading ====
* [[BuildingCampaignsThePBLFile|General information about the .pbl file]] - It has a campaign flavor, but it is adaptable to any content
* [[PblWML|Syntax reference for the .pbl file]]

==== Content-specific instructions ====
* Campaign - see the [[BuildingCampaigns|Buidling Campaigns Article]]
** [[BuildingCampaignsDistribution|About distributing campaigns]]
* Multiplayer era - see the [[BuildingFactions#Adding_a_whole_new_era_with_its_own_factions_-_modular|MP Era Article]]
* Unit pack - see the [[BuildingUnits#Distributing_your_unit|Units Article]]
* Map pack - see the
* Others?

(If I don't have BFW on the computer I'm working on, but I have it on a different computer, on which I don't Know how to find it's "./wesnoth/userdata" folder, how do I publish my Campaigns?-Drake Raider)

==== License ====
You should note that by uploading anything to the campaign server, you say that you own the license to all content in your upload and that it is under the GPL. Whenever you upload or update your content pack, you will have to say "OK" to this statement: "All campaigns uploaded to this server must be licensed under the terms of the GNU General Public License (GPL). By uploading content to this server, you certify that you have the right to placethe content under the conditions of the GPL, and choose to do so."

== See Also ==

* [[Create]]
* [[BuildingCampaignsDistribution]]
* [[BuildingCampaignsThePBLFile]]
* [[PblWML]]

FAQ

2006-05-09T12:33:52Z

Xan: Reverted edit of Bobdole, changed back to last version by Allefant

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

===A new version is out, but where is the download for [Windows, Mac OS, etc.]?===
The downloads are NOT part of the official project. The BFW team only releases the game's source code. Binary executables or applications are always contributed by community volunteers. If not for these volunteers, there would never be any downloads for us to enjoy. The volunteers compile the game and upload it on their own time, and sometimes they cannot do this in a timely fashion (or at all, at times) Although there are usual packagers designated for each operating system, there are times when other members of the community are asked to step in and contribute when the usual people cannot.

Every time a new version is released, the usual volunteers are always notified by the project leaders. '''Please refrain from making forum posts asking where your download is''' because it doesn't help anything - the packagers already know, and they will get to it as soon as they can. In the past, the Windows and Mac communities have come together to produce home-grown unofficial builds for the community to use, and the renewed interest in community and learning how to compile is generally a good thing.

===Why doesn't Wesnoth have my favorite feature?===
Because we are building this game for ourselves, to suit our own preferences. We're not building the game for you, in large part because this is our hobby, not our job; whether you like it or not is immaterial to us.
You may wonder, then, what the point is of soliciting ideas, as we do on the forum. We, the developers, have certainly come up with many good ideas on our own, but our players often do as well, and generally ones we don't think of ourselves. If a player comes up with an idea we like, we might implement it. Not because they asked for it, but because of its own merits as an addition to our game.

The beautiful thing about the license our game is distributed under, as compared to closed-source, commercial games, is that if you want that feature badly enough, you can take the code and art of our game and modify it yourself; you are free to re-use any work in Wesnoth, as long as you follow the rules of the [http://www.fsf.org/copyleft/gpl.html GPL]. From this, you can build a game exactly the way that you like. Just don't expect us to build that game for you. Building this game is our hobby, not our profession, and you did not pay us to make it; rather, we are the ones who have paid for it, in time and labor.

===Do you want help making this game? How can I help?===
Yes, we want your help. Whether you're a programmer, artist, musician, writer, translator, level designer, playtester, or just have some great suggestions, you're welcome to contribute. How? You can:
* join the [http://www.wesnoth.org/wiki/Project Project]
* share your point of view at the [http://www.wesnoth.org/forum/ Forum]
* talk with us on [irc://irc.wesnoth.org/wesnoth IRC]
* report bugs you find at [[ReportingBugs]]
* update the wiki
* play against us via the Multiplayer menu
* vote for Wesnoth at your favorite gaming web site
* Spread the word!

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

We are not completely certain, but an x86 running at 600MHz with 128MB RAM should be adequate. Slower machines will have trouble scrolling large maps or processing AI turns with many units. See the [http://www.wesnoth.org/forum/viewtopic.php?t=7384 forum thread] about minimum and recommended system requirements.

=== I'm bored; how do I speed the game up? ===

There are several preferences you can change to shorten the time that the AI takes to make its moves. "Accelerated Speed" will make units move and fight faster. "Skip AI Moves" will not show the AI's units moving from hex to hex. Finally, you can turn off all combat animations via the "Show Combat" option on the Advanced tab.

=== My computer is too slow; how do I speed the game up? ===

First, turn off the music and sound effects. Turning off the color cursors will make your cursor respond faster. If scrolling the map is slow, run the game in "Full Screen" mode, not in a window. Turn off combat animations via the "Show Combat" option on the Advanced tab. You can try turning off halos and combat results, but this might make gameplay more difficult.

== Gameplay and Controls ==

=== How do I learn to play? ===

If you just want to jump right in, start the game and play the tutorial. If you like reading documentation, see [[WesnothManual]], which is also distributed as a PDF file. At any time while playing, you can select help from the menu button (or hit F1). The online help is quite extensive and provides information on terrains, weapons, traits, abilities, units and a good overview of how to play.

=== My unit leveled up but didn't improve. What happened? ===

This is called "After Maximum Level Advancement" or AMLA for short. While most level 0, 1, and 2 units can advance, some cannot. However, some level 3 units can advance to level 4, or even 5. You can see whether a unit can advance further by right clicking and selecting "description."

After a unit reaches the highest level it can get, every time it gains 100 experience it gains 3 hitpoints. It does not heal when this happens. This is a minor bonus so that experience gained by maxed out units is not altogether wasted. It is generally better to give experience to lower level units, rather than continue to advanced units that have reached their maximum level.

If the unit in question is the Necrophage, this is not a bug. The Necrophage eats the corpses of the dead, allowing it to periodically completely heal. Leveling into itself is how this is carried out.

=== I tried to trap an enemy with several weak units, but it still escaped. What happened? ===

Most units exert a zone of control (or ZOC). IF an enemy moves into one of the six adjacent hexes, the zone of control will prevent it from moving any farther. However some weak units are level 0, meaning they are so weak that they do not have a ZOC. You can still surround an enemy unit entirely with level 0 units to keep it from escaping, but if there is any gap in your ranks, it could escape.

Also, some units have the "skirmish" ability, which allows them to ignore ZOCs.

=== How can I see where an enemy unit can move next turn? ===

During you turn you can click on an enemy unit. Wesnoth will highlight all the hexes the unit can move to in the next turn. This is useful when trying to arrange your units to block an enemy's movement.

=== There's too much luck in this game! ===

Sooner or later, you will become frustrated when your archmage with four 70% attacks misses all four times. This does not mean that the AI is cheating or the random number generator is futzed. It means you are noticing random negative events more than positive ones. During the development of the game, many mathematicians have done sophisticated statistical analysis of the combat system. Likewise, programmers have examined the random number generator. Wesnoth has been deliberately designed so that the streaks of "bad" and "good" luck are a part of the gameplay.

Since Wesnoth is GPLed, it is possible that, after the 1.0 release, a new development team will "fork" the source and produce a version more like Heroes of Might & Magic, with no randomness. Until then, don't charge with your horsemen against rock trolls at night...

=== The (random unit) is overpowered/underpowered! ===

The development team has spent years tweaking the units in the game. Each unit has had its gold cost, attack types, combat damage, defensive values, resistances, upgrade paths, and other stats carefully scrutinized and loudly discussed in the forum. However, the game code and the units were being modified right up until the 1.0 release, so some unbalanced units may have slipped through.

If you have evidence to back up your claim, search the forum for past discussions about this unit, and then try posting.

=== The (random scenario) is too hard/easy! ===

See above answer about random units.

=== What do the different difficulty levels do? ===

That depends on the scenario. Usually, the opponent will get more money and be able to recruit higher-level units at higher difficulty levels, and you will have fewer turns available.

== Maps, Scenarios and Campaigns ==

=== How do I beat scenario _______ ? ===

If you are stuck on a scenario in a campaign, you'll probably find a walkthrough at [[MainlineScenarios]]. Or check out the "Strategies and Tips" forum at http://www.wesnoth.org/forum/viewforum.php?f=3

=== Are there any tools to help me create 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]].

=== How do I download user campaigns? ===
Choose "Campaigns" in the main Wesnoth menu. Then scroll down to the bottom and choose "Get More Campaigns...". This connects you to the campaign server. In the campaign server you can view a list of all available campaigns and download them, as well as posting or deleting your own campaigns. If you are behind a firewall you may not be able to connect the the campaign server; in this case try contacting the author of the campaign via the forums to see if there is another way you can get the campaign.

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

===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.

== 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 can I make my computer into a dedicated Wesnoth server?===

To setup a dedicated Wesnoth server, you have to compile the game with the "--enable-server" flag, and after you install, simply run wesnothd from the console. This will start the server, listening on TCP port 15000. To compile the server only you can use the flags "--disable-game --enable server". If you aren't using a linux or mac operating system, there are a few ways you can compile on Windows...here is one way http://www.wesnoth.org/wiki/CompilingWesnoth/CrossCompiling

===Which versions of Wesnoth can play together?===

I'm on a MAC, and my friends are on XP. I would like to play together with them. Is this currently possible?

YES! All you need is to have the same version number.

For a list of Mac-XP-compatible games (including BfW) see: http://www.insidemacgames.com/forum/index.php?showtopic=21818

== Translations ==

===I selected an asian translation and am not able to see the letters correctly. What happened?===

Since the size of the necessary fonts is too large, you'll need to download them separately (if you don't already have them). After that, simply copy the font to the '''fonts/''' directory in your wesnoth installation.
* Chinese font: [ftp://cle.linux.org.tw/pub/fonts/ttf/unicode/Arphic/gkai00mp.ttf gkai00mp.ttf]
* Japanese font: [http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/sqs-xml/sqs-font/sazanami-gothic.ttf sazanami-gothic.ttf]

If you have futher questions have a look at [[WesnothAsianLanguages|this]] page.

== Other Questions You Have ==

The best way to get answers to less-frequently asked questions is by visiting the [http://www.wesnoth.org/forum BFW forum]. There are plenty of people willing to help. Make sure you read ALL of the forum sticky notes and announcements before posting.

Project

2006-05-09T12:33:49Z

Xan: Reverted edit of Bobdole, changed back to last version by Viliam

The Battle for Wesnoth is a [http://gna.org/projects/wesnoth/ Gna! project]. See also the [http://freshmeat.net/projects/wesnoth/ project] and [http://freshmeat.net/project-stats/view/38720/ stats] at [http://www.freshmeat.net/ freshmeat].

There are also Wesnoth pages in other languages:
[http://wesnothfr.ww7.be/ French],
[http://wesnoth.fw.hu/ Hungarian],
[http://wikiwiki.jp/wesnoth/ Japanese],
[http://www.wesnoth.pl/ Polish],
[http://perso.wanadoo.es/wesnoth/ Spanish].

== Artists ==
Graphic artists and musicians usually meet on the [http://www.wesnoth.org/forum/ forum].
* [http://www.wesnoth.org/forum/viewforum.php?f=9 Artwork development forum]
* [http://www.wesnoth.org/forum/viewforum.php?f=14 Music development forum]

== Developers ==
Coders can help fixing [http://bugs.wesnoth.org bugs], adding new features...
* [[CodingStandards]]
* [[Roadmap]]
* [http://devdocs.wesnoth.org/ Documentation] - generated and uploaded two times every day (05:05 and 17:05 GMT+2).

== Translators ==
* [[WesnothTranslations]]
* [http://gettext.wesnoth.org Statistics]
* [[WesCamp|Translating User made Campaigns (featuring wescamp-i18n)]]

{{Home}}

Credits

2006-05-09T11:03:20Z

Xan: Reverted edit of Bobdole, changed back to last version by Jetryl

{| style="float:right"
|
__TOC__
|}
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 ==
====Coders, (minor and major)====
* Alfredo Beaumont (ziberpunk) - autotools
* András Salamon ([[User:Ott|ott]]) - QA, bug fixing, subediting, game mechanics
* 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
* David Philippi (Torangan) - internationalization manager, wescamp
* [mailto:davidnwhite_AT_verizon.net David White] (Sirp) - founder, lead developer, scenario designer
* Dominic Bolin (Xan) - programmer
* Guillaume Melquiond (silene) - coding, bug fixes
* Jérémy Rosen (Boucman) - coder
* Jörg Hinrichs (Yogi Bear/YogiHH) - coder
* Jon Daniel (forcemstr) - coder, bug fixes
* [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
* 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
* [mailto:ydirson_AT_altern.org Yann Dirson] - gettext support, tinygui

====Miscellaneous====
* Benjamin Drieu (benj) - campaign writer (wrote "Son of the Black Eye")
* [mailto:dragonking_AT_o2.pl Bartek Waresiak] (Dragonking) - multiplayer balancing
* Crossbow/Miyo - administrator, release manager
* Francisco Muñoz (fmunoz) - artwork manager, many images, scenario designer (also listed below)
* Hogne Håskjold (frame) - terrain designer (also listed below)
* [mailto:isaac_AT_sindominio.net Isaac Clerencia] - administrator, release manager
* James Spencer (Shade) - campaign writer (wrote "The Rise of Wesnoth")
* Joseph Simmons (Turin) - campaign writer, some graphics (wrote "The Eastern Invasion," and others)
* Mark Michelsen (skovbaer) - internationalization manager
* Mike Quiñones (Doc Paterson) - multiplayer balancing, multiplayer maps
* [mailto:Crazy-Ivanovic_AT_gmx.net Nils Kneuper] (Ivanovic) - internationalization manager
* Richard Kettering (Jetryl) - artwork manager, many images (also listed below)
* Richard S. (Noy) - multiplayer balancing
* Scott Klempner - campaign maintainer
* Soliton - multiplayer balancing
* [mailto:susanna.bjorverud_AT_telia.com Susanna Björverud] (sanna) - internationalization manager

====Unclassified====
* Jan Zvánovec (jaz)
* John B. Messerly (jbm)
* [mailto:jorda_AT_ettin.org Jordà Polo] (ettin)
* J.R. Blain (Cowboy)
* Maksim Orlovich (SadEagle)
* Zas

== Artists ==
==== Major Contributors ====
* Francisco Muñoz (fmunoz) - Founding Artist and former lead artist, worked consistently on all aspects till around v0.7-0.9.
* Richard Kettering (Jetryl) - Current art director/slave, major focus on sprites, portraits, buildings, and icons
* Hogne Håskjold (frame/freim) - Current director of terrain art, made much of the current terrains (esp. mountains)
* J.W. Bjerk [http://www.wesnoth.org/wiki/User:Eleazar (Eleazar)] - terrain (esp Chasm, Cave, Water), sprite animations, many general graphics tasks
* James Woo (Pickslide) - portraits (major focus on orcs and campaigns)
* Jason Lutes - portraits (major focus on humans, some campaign portraits)
* ?? (Neoriceisgood) - sprite creator and animator (major focus on drakes, dwarves, saurians)
* Peter Geinitz (Shadow/Wayfarer) - sprite creator and animator

==== Moderate Contributors ====
* Alex Jarocha-Ernst (Jormungandr) - portraits
* Eli Dupree (Elvish Pillager) - sprites and animations
* Pekka Aikio (pekka) - tiles, esp. castles, and attack icons
* Michael Gil de Muro (grp21) - portraits (for the campaign "The Rise of Wesnoth")
* Robert Bolin (Zebulon) - tiles, sprite editing and animations
* Christophe Anjard (Christophe33) - made many of the old (c. v0.6) terrains, and some sprites for the dwarves
* Johann de Venecia (Johann) - drew the new campaign story art for HttT

==== Minor Contributors ====
* Gerald Clears (Smok'em Jags) - sprite animator
* Jesse Holland (Kestenvarn) - map illustrator, designed the current map for HttT
* Mark Goodenough (Ranger M) - Sprite animator
* Murray Cook (Zhukov) - Sprite animator
* Andrew James Patterson (Kamahawk) - sprites
* Diego Brea (Cobretti) - sprite creator/animator
* ?? (antwerpz) - sprite creator/animator for old saurian units
* Moritz Göbelbecker (mog) - improved encampment
* Gareth Miller (Gafgarion) - made some early sprites/tiles
* James Barton (Sangel) - sprites
* John Muccigrosso (Eponymous Archon) - made some early sprites, such as the human bowmen
* ?? (Slainte) - made sprites for c. v0.6 mages, also made many of the old attack icons
* ?? (Svetac) - made many of the old attack icons
* Johanna Manninen (lohari) - edited tiles, ported freeciv tiles used in very early versions of wesnoth

==== Very Minor Contributors ====
* Gideon Chia (Deonjo) - new "units" icon for general status bar
* John-Robert Funck (XJaPaN) - sprite animator
* Jonatan Alamà (tin) - made red logo used until before v1.0
* Jimmy Olsson (Azlan) - made old icons for windows version
* Randall Walls (slightcrazed) - sprite animator
* Jason Frailey (Valdroni) - made scorpion portrait
* Nicholas Kerpan (Thrawn) - made human theif portrait
* (Highhole) - revised storm trident
* Irwin Ismail (Swordy) - original projectile/attack icon for chakram

==== Unclassified ====

* Stephen Stone - [graphics]

== Musicians ==
* Aleksi Aubry-Carlson (Aleksi) - music coordinator/composer
* Joseph Toscano (zhaymusic.com) - music
* Pau Congost - music
* Fredrik Lindroth - music
* Timothy Pinkham (TimothyP)

== 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
* Benoît Timbert (Noyga) - 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
* Claudio Terra - brazilian portuguese 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
* Gaute Jao (Bombadil) - norwegian 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
* Kim Woong (Kazya) - korean 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
* Joshua Northey (Becephalus) - multiplayer maps
* Marcin Konicki (ahwayakchih) - BeOS packager
* Marcus Phillips (Sithrandel) - Mac OS X packager
* Mark Michelsen (skovbaer) - slackware packager
* 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}}

User:Xan

2006-04-05T13:56:05Z

Xan: /* Work In Progress: */

==Work In Progress:==
*WML Enhancement
** Unit Abilities
** Weapon Specials
** Unit WML
*Factions
** Frost Elves
** Faction X
*Spacenoth

===Planned:===
*Releasing the first version of [http://arcune.org/forum/index.php Spacenoth]
*Take over the world after everyone else.

===Completed:===
*[http://arcune.org/files/wesnoth/update.cpp Unit WML Updater]

== See Also == [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=101476 Xan's forum profile]
List & description of [[Developers]]

UnitTypeWML

2006-04-01T01:47:35Z

Xan: /* Attacks */

{{WML Tags}}
== The [unit] tag ==

Each '''[unit]''' tag defines one unit type.

Unit animation syntax is described in [[AnimationWML]].

The following key/tags are recognized:
{| class="gallery" style="text-align:left;"
|-
! [[ability]]
| a list of the unit's abilities. See [[AbilitiesWML]] for a description of abilities.
|-
! [[advancefrom]]
| allows a campaign-specific unit to be spliced into an already existing advancement tree. It should generally be used only inside a campaign ifdef, to prevent changes to other campaigns. This tag makes changes to the ''advanceto'' and ''experience'' keys of a base unit to make it advance into this unit. It takes these keys:<br> ** ''unit'' the id of the base unit from which this unit advances. This adds the unit into the list of units which ''unit'' can advance into.<br>** [[experience]] is optional. If present and lower than the experience already required for the base unit to advance, then the experience to advance is lowered. Note: this will also lower the experience required to advance to other units which the base unit can advance into.
|-
! [[advanceto]]
| When this unit has experience greater than or equal to [[experience]], it is replaced by a unit with 0 experience of the type that the value of [[advanceto]] refers to. All modifications that have been done to the unit are applied to the unit it is replaced by.
|-
! alignment
| how the unit's damage should be affected by its lawful bonus (See [[TimeWML]]).
|-
! cost
| when a player recruits a unit of this type, the player loses ''cost'' gold. If this would cause gold to drop below 0, the unit cannot be recruited.
|-
! experience
| When this unit has experience greater than or equal to ''experience'', it is replaced by a unit with 0 experience of the type that the value of ''advanceto'' refers to. All modifications that have been done to the unit are applied to the unit it is replaced by.
|-
! gender
| has a value of either ''male'' or ''female'', and determines which of the keys ''male_names'' and ''female_names'' should be read. When a unit of this type is recruited, it will be randomly assigned a name by the random name generator, which will use these names as a base.
|-
! hitpoints
| the maximum HP that the unit has, and the HP it has when it is created.
|-
! id
|the value of the ''type'' key for units of this type. An ''id'' should consist only of alphanumerics and underscores. ''type'' keys are found in [[SingleUnitWML]] and [[FilterWML]].
|-
! level
| the amount of upkeep the unit costs. After this unit fights, its opponent gains ''level'' experience. See also kill_experience ([[GameConfigWML]]), and leadership ([[AbilitiesWML]]).
|-
! movement
| the number of move points that this unit recieves each turn.
|-
! movetype
| See '''[[movetype]]''', [[UnitsWML]]. Note that the tags '''[[movement_costs]]''', '''[[defense]]''', and '''[[resistance]]''' can be used to modify this movetype.
|-
! name
|(translatable) displayed in the Status Table for units of this type.
|-
! num_traits
| the number of traits that units of this type should receive when they are recruited, overriding the value set in the [race] tag.
|-
! race
| See '''[race]''', [[UnitsWML]]. Also used in standard unit filter (see [[FilterWML]]).
|-
! unit_description
| (translatable) the text displayed in the unit descriptor box for this unit. Default 'No description available...'.
|-
! usage
| the way that the AI should recruit this unit, as determined by the scenario designer. (See ''recruitment_pattern'', [[AiWML]]). The following are conventions on usage:<br> ** 'scout' Fast,<br> ** 'fighter' <br>Melee fighter, ** 'archer' Ranged fighter,<br> ** 'mixed fighter' Melee and ranged fighter, and<br> ** 'healer' Specialty 'heals' or 'cures'.
|-
! zoc
| {{DevFeature}} if "yes" the unit will have a zone of control regardless of level. If present but set to anything other than "yes," the unit will have no zone of control. If the tag is omitted, zone of control is dictated by unit level (level 0 = no zoc, level 1+ = has zoc).
|}
==== After max level advancement (AMLA) ====
* '''[advancement]''' describes what happens to a unit when it reaches the XP required for advancement. It is considered as an advancement in the same way as advancement described by ''advanceto''; however, if the player chooses this advancement, the unit will have one or more effects applied to it instead of advancing.
** ''id'' normal internationalization id.
** ''description'' a description (see [[DescriptionWML]]) displayed as the option for this advancement if there is another advancement option that the player must choose from; otherwise, the advancement is chosen automatically and this key is irrelevant.
** ''max_times'' default 1. The maximum times the unit can be awarded this advancement.
** ''require_amla'' {{DevFeature}} An optional list of AMLA ''id'' keys that act as prerequisites for this advancement to become available. Order is not important, and an AMLA id can be repeated any number of times to indicate that another advancement must be chosen several times before this advancement option will become available.
*** example: ''require_amla=tough,tough,incr_damage'' assumes there exist other [advancement] options called ''id=tough'' and ''id=incr_damage''. Once ''tough'' is chosen twice and ''incr_damage'' is chosen once, then the current [advancement] will become available.
*** ''require_amla=tough,incr_damage,tough'' is an equivalent way of expressing this.
** '''[effect]''' A modification applied to the unit whenever this advancement is chosen. See [[EffectWML]]

==== Attacks ====
* '''[attack]''' one of the unit's attacks.
** ''description'' a translatable text for name of the attack, to be displayed to the user.
** ''name'' the name of the attack. Used as a default description, if ''description'' is not present, and to determine the default icon, if ''icon'' is not present (if ''name=x'' then ''icon=attacks/x.png'' is assumed unless present). Non-translatable. Used for the ''has_weapon'' key; see [[FilterWML]]
** ''type'' the damage type of the attack. Used in determining resistance to this attack (see '''[resistances]''', [[UnitWML]]). Possible values are 'blade', 'pierce', 'impact', 'fire', 'cold', and 'holy'.
** ''special'' the special ability of the attack. Currently having more than 1 ability is not supported. See [[AbilitiesWML]] for a list of possible values.
** ''icon'' the image to use as an icon for the attack in the attack choice menu, as a path relative to the images directory.
** ''range'' the range of the attack. Used to determine the enemy's retaliation, which will be of the same type. Also displayed on the status table in parentheses; 'short'(default) displays "melee", while 'long' displays "ranged". {{DevFeature}}: range can be anything. Standard values are now "melee" and "ranged". From now on, ''short'' and ''long'' will be treated as totally different ranges. You can create any number of ranges now (with any name), and units can only retaliate against attacks for which they have a corresponding attack of the same range. This value is translatable.
** ''damage'' the damage of this attack
** ''number'' the number of strikes per attack this weapon has
For those two following settings, the engine usually chooses the attack with the best average total damages * weight (default weight = 1.0).
** ''attack_weight'' helps the AI to choose which attack to use when attacking; highly weighted attacks are more likely to be used. {{DevFeature}}: Setting it to 0 disables the attack on attack
** ''defense_weight'' used to determine which attack is used for retaliation. This affects gameplay, as the player is not allowed to determine his unit's retaliation weapon. {{DevFeature}}: Setting it to 0 disable the attacks on defense

** '''[animation]'''
:: This describes an animation for this attack. If multiple animations are present, one will be randomly chosen each time the unit attacks. See [[AnimationWML]] for possible keys.

* '''[defend]''' See [[AnimationWML]]
* '''[death]''' See [[AnimationWML]]
* '''[teleport_anim]''' See [[AnimationWML]]
* '''[extra_anim]''' See [[AnimationWML]]
* '''[event]''' See [[EventWML]]

* '''[variation]''' Defines a variation of a unit. Variations are invoked with an [effect] tag. They are currently used for graphical variations (giving character sprites new weapons) but theoretically you could do anything with it.
** ''variation_name'' The name of the variation.
: All other keys in '''[variation]''' are the same as for '''[unit]''' itself.

* '''[male]''', '''[female]''' They can contain all '''[unit]''' tags, to specify a variation of different gender for a unit.

== See Also ==

* [[AnimationWML]]
* [[ReferenceWML]]
* [[TerrainWML]]

[[Category: WML Reference]]

GettingStarted

2006-03-09T22:36:44Z

Xan: /* Getting the Most Fun Out of the Game */

The Battle for Wesnoth is a turn-based strategy game with a fantasy theme.

''Build up a great army'', gradually turning raw recruits into hardened veterans. In later games, recall your toughest warriors and form a deadly host against whom none can stand! Choose units from a large pool of specialists, and hand-pick a force with the right strengths to fight well on different terrains against all manner of opposition.

Fight to regain the throne of Wesnoth, of which you are the legitimate heir, or use your dread power over the Undead to dominate the land of mortals, or lead your glorious Orcish tribe to victory against the humans who dared despoil your lands … Wesnoth has many different sagas waiting to be played out. You can create your own custom units, and write your own scenarios – or even full-blown campaigns. You can also challenge your friends – or strangers – and fight in epic ''multi-player'' fantasy battles.

=== Finding Your Way Around Wesnoth ===
When Wesnoth first starts it displays an initial background and a column of buttons called the Main Menu. The buttons only work with a mouse. The Main Menu buttons are:

*Tutorial
:The tutorial is a real, but basic, game which teaches you some of the basic controls needed to play the game. Winning or losing is not important here, but learning what to do is. Click the Tutorial button to play. In the Tutorial you are in the role of the young prince Konrad, learning from the Elder Mage Delfador - pay attention or he might turn you into a newt.

*Campaign
:Wesnoth was primarily designed to play campaigns. Campaigns are a series of connected scenarios. Click this button to start a new campaign. You will be presented with a list of campaigns available on your computer (more can be downloaded if you wish). Select your campaign and click OK to start or Cancel to quit.

:Each campaign has a difficulty level: easy, medium (normal), and hard. We recommend medium as this level is challenging, but not difficult. You may not change the difficulty during the campaign. Once you have selected the difficulty, you will start with the first scenario of the campaign.

:To learn more on Campaigns, see 'Playing a Campaign' and 'Load'. You can also find walkthroughs or descriptions of the available scenarios at:
::* [[MainlineScenarios]]
::* [[UserScenarios]]
::* [[BeginnerScenarios]]

*Multiplayer
:Click this button to play single scenarios against one or more opponents. You can play the games over the internet or at your computer, against computer or human opponents. When you select this button a dialogue will appear and allow you to choose how you want to play the scenario. To learn more, see [[#Multiplayer|Multiplayer]].

*Load
:Click this button to load a previously saved game. You will be shown a dialogue listing saved games. Select the game and click Ok to load and continue, or Cancel to return to the Main Menu.

:If you select a replay game, you can check the Replay check box. The loaded game will make all the moves from the beginning while you watch.

*Language
:Click this button, select your language, and click OK to use it, or Cancel to continue with the current language. The first time Wesnoth starts, it defaults to English, but once you change it, it will start in that language.

*Preferences

:Click here to change default settings. These are explained in more detail in [[PlayingBattleForWesnoth#Preferences|the Manual]].

*About
:Click this button for a list of major Wesnoth contributors. You may find most of them at irc.freenode.org:6667 on #wesnoth. Or visit http://www.wesnoth.org for news, forums, and Wiki updates. The project is hosted on http://savannah.gnu.org/projects/wesnoth , where you can download the latest production or developer release, review and report problems (bugs).

*Quit
:Click this button to close Wesnoth.

'''For the impatient, we recommend you set your language, run the tutorial, and then play a campaign.'''

This getting started guide provides a basic introduction to Battle for Wesnoth. You can find more details about playing the game in the [[WesnothManual|Manual]].

=== Play a Game ===
There are two basic ways to play Battle for Wesnoth:
*Play a sequence of connected scenarios, known as a campaign, against the computer
*Play a single scenario against computer or human opponents

==== Campaigns ====

Campaigns can take a long time to complete. Typical campaigns have about 20 to 30 scenarios. The main advantage with campaigns is that they allow you to develop your army. As you complete each scenario, the remaining units at the end are saved for you to use in the next scenario.
If you choose not to use a unit at all during a scenario it is carried over
to the next, so you don't lose units you don't use.

The campaign is the primary form in which Wesnoth is intended to be played, is probably the most enjoyable, and is the recommended way for new players to learn the game.

==== Scenarios ====

A single scenario takes about 30 minutes to 2 hours to complete.
This is the fastest way to play, but your units are not saved and you cannot use
campaign units. You can play scenarios against the computer or against other players either over the internet or at your computer. Scenarios are accessed through the 'Multiplayer' button on the main menu.

===== Multiplayer =====

Multiplayer games can take anything from 1 hour to 10 hours, depending on
how many players there are (and the size of the map). The average time is between 3 to 7 hours.
Games can be saved and loaded as many times as you like.
So, it's possible for some games to last 1 or 2 weeks, even though
the play time is only a few hours. Currently, you cannot carry over
units in multiplayer from one scenario to the next, so building up
your army's strength is possible only within the scenario.

===== Hotseat =====

Hotseat games will take about the same time to play as games played remotely.
The time will be greatly affected by the size of the map.

===== Human vs AI =====

If you are new to Wesnoth, but have experience playing turn-based hex combat games, here is a way to find out how the terrain and units interact:

# Go to Multiplayer, and play the AI on one of the larger maps.
# Choose "Rebels". Give yourself two or three times as much gold as you give the AI. Set the leveling percentage to 70% and "gold per village" to 2x if you want to practice with the "standard" multiplayer settings.
# Experiment with the different factions (which will give you different units) and fighting against different opponents.
# When you consistently overrun the AI, move the gold back to normal or even give the AI more. This will prepare you for the campaigns and to a much lesser extent for multiplayer against other humans.

==== The Game Screen ====

Regardless of whether you are playing a scenario or a campaign, the basic layout of the game screen is the same. The majority of the screen is filled with a map which shows all of the action that takes place in the game. Around the map are various elements which provide useful information about the game and are described in more detail below.

Across the top of the screen from left to right are the following items:
#Menu button
#Actions button
#Turn counter *
#Your gold
#Your total villages
#Your total units
#Your upkeep
#Your income
#Current hex type
#Current hex position

Down the right of the screen from top to bottom are:
#Full map, scaled *
#Time of day indicator
#Unit profile for last selected unit*
#End Turn button *

(Items marked with a * are currently undocumented)

*Menu button: Displays a drop-down menu with the following options:

#Scenario Objectives: Lists the victory and defeat conditions.
#Statistics
#Unit List: Lists your active units, including their map position.
#Status Table: Summary list of visible player units, villages, income etc.
#Save Game: Write the current game position to disk.
#Load Game
#Preferences: see [[PlayingBattleForWesnoth#Preferences|the Manual]] for details.
#Help
#Quit Game: Close the game, without saving, and return to the Main menu.

*Actions button: Displays a drop-down menu with the following options:
#Next unit
#Recruit: Lists units your commander can recruit from a keep.
#Recall (Campaign only): Lists units your commander can recall from a keep.
#Show enemy moves
#Best possible enemy moves
#End Turn: On your turn, select it to end your turn.

*Your gold, villages, units, upkeep, and income
:Quick way to check how your army is doing. A negative income means you'll lose gold, a positive means you gain gold. Upkeep is the gold you pay your units. Villages shows how many you own, each village will give you Gold.

*Current hex
:Shows the terrain type and position of the hex pointed to by the mouse. If a unit is on the hex, its resistance on that terrain is shown after the position. The position is in column, row order.

*Time of day indicator
:Putting your mouse over the indicator will bring up a tooltip showing the effect of the time of day. Wesnoth has a 6-turn day and different alignments have bonuses depending on the time of day.

=== Save and Load ===
At the start of each scenario, you have the option to save it.
If you are defeated, you may load it and try again. Once you have succeeded,
you will again be asked to save the next scenario and play that.
If you have to stop playing during a scenario, you can save your turn
and load it again later. Just remember, a good BFW player never needs to
save '''during''' a scenario. However, most beginners tend to do so rather
often. ;)

=== Recruit and Recall ===
At the start of each scenario, your commander is placed in a castle on a
special hex called a keep. From here, you can recruit or recall
your troops. Each recruit is placed on an empty castle square. Once you
have filled the castle, you cannot recruit any more until units move off.
Your opponent's commander is similarly placed on its castle keep and able
to recruit troops. When you right-click on an empty castle hex, a context
menu will come up that includes "recruit". Use the menu that comes up to
recruit more units. You must wait until your next turn to move recruits
off your castle.

At the end of each successful scenario, all your remaining troops are
automatically saved for you. At the start of the next scenario you may
recall them in a similar way to recruiting. Recalled troops are often more
experienced than recruits and usually a better choice.

You may only recruit and recall when your commander is on the castle's keep
hex. Since most castles have a keep, you can move your commander to any
castle's keep to recruit and recall.


=== Factions and Races ===

The world of Wesnoth contains several races that have joined forces
into different factions. Here, Elf and Dwarf fight side by side against Orc
and Human. In most campaigns, you will mostly control units from one
faction, but often you will have a recruit list with units mixed in from
other factions, and will not have some units from a faction available.
Basically, your recruit list is determined by the plot of the campaign,
not by a predetermined ruleset.

Sometimes factions make alliances with others, so you may face more
than one faction in a scenario.



=== Life and Death - Experience ===

As your troops gain battle experience, they will learn more skills and
become stronger. They will also die in battle, so you'll need to
recruit and recall more when that happens. But choose wisely, for each has
strengths and weaknesses a cunning opponent will quickly exploit.




=== Army Units ===

All game types use the same soldiers, called units. Each unit is identified
by Race, Level, and Class. Each unit has strengths and weaknesses,
based on their Resistance, current Terrain, and Level.
Full details are in the [[UnitTables]] and [[MoveTypeTables]].

=== Getting the Most Fun Out of the Game ===

Remember, the idea of a game is to have fun! Here are some recommendations
from the development team on how to get the most fun out of the game:

* Consider playing the campaign on 'Medium' difficulty level, especially if you have prior experience with strategy games. We feel you'll find it much more rewarding.
* Don't sweat it too much when you lose some units. The campaign was designed to accomodate the player losing some units along the way.
* Don't abuse saved games. Long ago, Wesnoth only allowed saving the game at the end of a scenario. Mid-scenario saving was added as a convenience to use if you had to continue the game another day, or to protect against crashes. We do not recommend loading mid-scenario saved games over and over because your White Mage keeps getting killed. Learn to protect your White Mage instead, and balance risks! That is part of the strategy.
* If you must load a saved game, we recommend going back to the start of the scenario, so that you choose a new strategy that works, rather than simply finding random numbers that favor you.
* But remember, the aim is to have fun! You may have different tastes than the developers, so do what you enjoy most! If you enjoy loading the saved game every time you make a mistake, looking for the 'perfect' game where you never lose a unit, by all means, go right ahead!

==== At the start of a scenario ====
* First, read the scenario objectives. Sometimes you do not have to kill enemy leaders instead it is enough that you survive number of turns, or pick up a particular object
* Look at the map: the terrain, the position of your leader and the other leader.
* Then, begin to recruit units. Cheap units are useful to soak up the first wave of an enemy's attack; advanced units can then be brought in as support. Fast units can be used as scouts, for exploring the map and to quickly conquer villages.

==== During the scenario ====
* Try to capture and keep control of as many villages as possible to keep the gold coming in
* Keep units in packs so the enemy cannot attack from as many sides, and so you can outnumber each enemy unit. Put your units in a line so that the enemy cannot attack any one of your unit from more than two sides.
* Different units have different strengths and weaknesses depending on terrain and who they are attacking; right click on units and select "Describe unit" to learn more
* You can use lower level units as cannon fodder, to slow down enemy. e.g. you can use them to block enemy reaching your important units
* You can cause damage to enemies with advanced units and then finish them with lower level units - to give them more experience (and finally make them advance to next level)
* When you have a White Mage (advances from Mage) or Druid (advances from Shaman), put it in the middle of a circle of units to heal them as they move across the map
* Losing units is expected, even advanced units
* Time of day really matters:
** lawful units do more damage at day and less damage at night
** chaotic units do more damage at night and less damage at day
** remember to always check the time of day on the right side of the screen. Plan ahead - think about what it's going to be next turn as well as this turn.
* Some units are resistant or vulnerable to different kind of attacks. Mounted units are weak vs pierce attacks. Fire and holy destroy undeads. To see how much a unit resists an attack type, right click on the unit, select 'Unit Description', then select 'Resistance'. It will show you how resistant a unit is to different types of attacks.

==== Healing ====
An important part of succeeding at Battle for Wesnoth is keeping your units healthy. When your units take damage you can heal them by moving them onto villages or next to special healing units (e.g. the Elvish Shaman and White Mage). Some other units you will encounter, such as Trolls, have the ability to heal themselves naturally. You can find more detailed information about healing in [[PlayingBattleForWesnoth#Healing|Chapter 2]].

==== Winning a scenario ====
* Advanced units are needed to quickly kill enemy commanders, and to avoid losing lots of units.
* The quicker you win a scenario, the more gold you get; you will get more gold from winning early than from all of the map's villages for the rest of the turns.
* Killing all enemy leaders usually gives instant victory.

==== More general tips ====
* After slaughtering scenarios (where your ass gets seriously kicked) there are usually "breathing room" scenarios where you can rather easily gain some gold and experience (advanced units)
* Advanced units have higher upkeep than lower level units (1 gp per level), loyal units are an exception.

<noinclude>

=== See Also ===
* [[WesnothManual]]
* [[AdvancedTactics]]

{{Play}}
</noinclude>

SideWML

2006-02-18T16:10:54Z

Xan: /* the [side] tag */

== the [side] tag ==

The [side] tag is used to describe a side in a particular scenario.

The following keys are recognized:

* ''description'' the sides non translateable name.

* ''user_description'' the sides translateable name.

* ''save_id'' default ''description'' (fallback to "Unknown"). The ID of the side with respect to the previous and next scenarios. Used to determine and store recall/recruitment list, gold. Also used for the side's displayed name in the victory gold-calculation dialog. See also ''persistent''.

* ''side'' a digit. The leader of this side is placed on the tile represented by this digit (see [[BuildingMaps]]). When defining sides, they must be defined in order since the side number is checked against the number of sides seen so far.

* ''controller'' how moves for this side should be inputted.
** 'ai' the Wesnoth AI makes this side's moves. This is the default setting.
** 'human' a player controls this side's moves.
** 'null' the side doesn't get a turn to move and doesn't have a leader generated from the contents of the [side] tag. (It still can get units from [unit] tags in the [side] tag.)

* ''allow_player'' if equal to 'no', then the game creation will not allow this player to be modified. {{DevFeature}}

* ''team_name'' a non translatable string representing the teams description. Sides with the same team_name are allied. Default ''side''.

* ''user_team_name'' a translatable string representing the teams description. This has no effect on alliances. Default ''team_name''.

* ''colour'' if you want side 4 to be the same colour as side 2 normally is, put colour=2.

* ''recruit'' a list of unit types. At the beginning of the scenario, the side gains recruitment of these units.

* ''gold'' the starting gold for this side. Default 100. (If gold is carried over from a previous scenario, this value is the minimum starting gold.)

* ''income'' the base income for this side, default 0. This is added to ''base_income'', '''[game_config]''' to determine the side's base income. (see [[GameConfigWML]]).

* ''fog'' if 'yes', this side cannot see any tiles it is not within vision of, except at the start.

* ''shroud'' if 'yes', this side cannot see any tiles it has not moved within sight of.

* ''shroud_data'' describes the area which this team has de-shrouded.

* ''village_gold'' the amount of gold given to this side per village it controls per turn. Default specified in ''village_gold'', '''[game_config]''' ([[GameConfigWML]]).

* ''share_maps'' whether sides allied with this side see all terrains that this side sees, if they are on shroud.

* ''share_view'' whether sides allied with this side see the units that this side sees, if they are on FoW (fog).

* ''name'', ''id'', ''leader'' not used; see [[EraWML]].

* ''music'' music to play for this player. Default specified in [scenario] (see [[ScenarioWML]]).

* ''persistent'' default '0'; when '''controller=human''', this is always '1'. If '1', the side gets a recall/recruitment list, gold from the previous scenario. Also, the gold it gets (including end-of-level bonus) will be stored for the next scenario. See also ''save_id''.

* '''[ai]''' if '''controller=ai''', gives parameters to the AI. See [[AiWML]].

* '''[village]''' describes a village the side begins in control of.
** ''x'', ''y'' the location of the village.

* '''[unit]''' describes a unit which begins on the side. See [[SingleUnitWML]]. If the side has a recall list and the unit is not given a location, it will start on the recall list. Note that the ''side'' attribute under '''[unit]''' will be ignored, as the side will come from the ''side'' attribute of '''[side]'''.

* ''no_leader'' if "no" (default), then keys describing a unit which will begin on the side's keep will be described in the remainder of the '''[side]''' tag, See [[SingleUnitWML]]. Note that if the keys ''x'', ''y'' are included, the leader will begin there regardless of keep location. If this side has a recall list from a previous level, then the recall list will be searched for a leader (using canrecruit) and if one is found it will be used instead of the one described in the '''[side]''' tag.

== See Also ==
* [[EraWML]]
* [[ScenarioWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

User:Xan

2006-02-02T23:29:55Z

Xan: /* Work In Progress: */

==Work In Progress:==
*WML Enhancement
** Unit Abilities
*Factions
** Frost Elves
** Faction X
*Spacenoth

===Planned:===
*Releasing the first version of [http://arcune.org/forum/index.php Spacenoth]
*Take over the world after everyone else.

===Completed:===
*[http://arcune.org/files/wesnoth/update.cpp Unit WML Updater]

== See Also == [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=101476 Xan's forum profile]
List & description of [[Developers]]

EventWML

2006-01-31T16:16:28Z

Xan: /* the [event] tag */

== the [event] tag ==

This tag is a subtag of [scenario] which is used to describe a set of actions
which trigger at a certain point in the scenario.

keys and tags that describe when the event should trigger:
<ul><li> ''name'' this is not like a normal 'name' key. It is a basic description of when the event will trigger.
* ''prestart'' the event is triggered before a scenario 'starts' -- before anything is shown on the screen at all. You can use this event to set up things like village ownership. For things displayed on-screen such as character dialog, use 'start'.
* ''start'' this event triggers after the map is shown but before the scenario begins
* ''new turn'' this event triggers whenever the last player ends their turn. See also '''first_time_only=no'''. When the last player ends their turn, before any events of this type trigger, the value of the WML variable '''turn_number''' is set to the number of the turn that is beginning.
* ''side turn'' this event triggers when any player ends their turn. When a player ends their turn, before any events of this type trigger, the value of the WML variable '''side_number''' is set to the number of the side of the player about to take their turn.
* ''turn ''X'''' this event triggers at the start of turn ''X''. ''X'' cannot be 1.
* ''time over'' this event triggers on turn ''turns''. (''turns'' is specified in [scenario])
* ''enemies defeated'' this event triggers when all units with '''canrecruit=1''' (i.e. all leaders) not allied with side 1 are killed.
* ''victory'' in this scenario, any tag of the form '''[endlevel] result=victory [/endlevel]''' will be automatically preceded by all actions in this tag. It helps debugging if the victory event allows you to safely advance to any of the possible next maps after using the ":n" command. Scenarios where key units are picked up before the victory, or where some action chosen earlier determines which map to advance to, make it hard to quickly test scenarios in a campaign. (See also [endlevel], [[DirectActionsWML]])
* ''defeat'' in this scenario, any tag of the form '''[endlevel] result=defeat [/endlevel]''' will be automatically preceded by all actions in this tag. (See also [endlevel], [[DirectActionsWML]])

Events with the following trigger types can be filtered on (see [[FilterWML]]).
Whenever one of these events is triggered,
the position of ''primary_unit'' is stored in the variables 'x1' and 'y1',
and the position of ''secondary_unit'' is stored in 'x2' and 'y2'.

* ''moveto'' triggers after ''primary_unit'' moves. Usually the location of ''primary_unit'' is also filtered on; remember that this is the location that ''primary_unit'' lands on, not the location it started on or any location it travels on.
* ''sighted'' this event triggers when ''primary_unit'' moves to a location where ''secondary_unit'' is in ''primary_unit'''s sight range.
* ''attack'' this event triggers when ''primary_unit'' attacks ''secondary_unit''.
* ''attacker_hits'' {{DevFeature}} this event triggers when the attacker (''primary_unit'') hits the defender (''secondary_unit'').
* ''attacker_misses'' {{DevFeature}} same as ''attacker_hits'', but is triggered when the attacker misses.
* ''defender_hits'' {{DevFeature}} this event triggers when the attacker (''primary_unit'') is hit in retaliation by the defender (''secondary_unit'').
* ''defender_misses'' {{DevFeature}} same as ''defender_hits'', but is triggered when the defender misses.
* ''attack_end'' {{DevFeature}} is similar to ''attack'', but is instead triggered after the fight, not before. Note that if either unit is killed during the fight, this event triggers before any ''die'' events.
* ''stone'' this event triggers when ''primary_unit'' is hit by an attack with the 'stones' ability (See ''stones'', [[AbilitiesWML]]) by ''secondary_unit'' (''secondary_unit'' is the unit with the 'stones' ability.)
* ''die'' this event triggers when ''primary_unit'' is killed by ''secondary_unit''.
* ''capture'' this event triggers when ''primary_unit'' captures a village. The village may have been previously neutral, or previously owned by another side; merely moving into your own villages does not constitute a capture.
* ''recruit'' this event triggers when ''primary_unit'' is recruited or recalled. (That is, when a unit is recruited or recalled, it will trigger this event and this event's filter will filter that unit.)
* ''advance'' {{DevFeature}} this event triggers just before ''primary_unit'' is going to advance to another unit.
* ''post_advance'' {{DevFeature}} this event triggers just after ''primary_unit'' has advanced to another unit.

An '''[allow_undo]''' tag anywhere within a moveto event will cancel any lack of undo functionality the event would have
caused. It is up to the scenario designer to avoid abusing this command by allowing undo on events that shouldn't be
undoable. The results of doing this may be strange. This actually does have functionality beyond aesthetics like
signs: suppose you have an event that performs some action depending on the condition of an 'if' statement. This event
might be executed on every single move, but the body of the 'if' statement entered only in a few cases. Previously
this would completely disable undo for the entire scenario, while now it can be made to only disable undo in the cases
where the event mutates the scenario.
</li></ul>

''Primary_unit'' can be referred to as '''unit''' and ''Secondary_unit'' can be referred to as '''second_unit''' in [message] tags. For example:
[event]
name=die
[message]
speaker=second_unit
message="Hahaha, I finally killed you!"
[/message]

[message]
speaker=unit
message="It's not over yet! I'll come back to haunt you!"
[/message]
[/event]

These keys and tags are more complex ways to filter when an event should trigger:
* ''first_time_only'' whether the event should be removed from the scenario after it is triggered. Default is 'yes'.
* '''[filter]''' the event will only trigger if ''primary_unit'' matches this filter.
** standard unit filter - attributes for [filter] are described in [[FilterWML]]
* '''[filter_second]''' is like [filter], but for ''secondary_unit''.
** standard unit filter
* '''[special_filter]''' and '''[special_filter_second]''' {{DevFeature}} can be used to set some additional filtering criteria for ''primary_unit'' and ''secondary_unit'' that are not generally available in a standard unit filter. Can be used in events ''attack'', ''attacker_hits'', ''attacker_misses'', ''defender_hits'', ''defender_misses'' and ''attack_end''.
** ''weapon'' the name of the weapon used.
** ''terrain'' the letter of the terrain the unit is on.

After the trigger conditions have been met, all action tags within the [event] tag are executed in the order they are written in.

There are 3 main types of actions: internal actions ([[InternalActionsWML]]) which are used by WML internally,
display actions ([[InterfaceActionsWML]]) which show something to the user,
and direct actions ([[DirectActionsWML]]) which have a direct effect on gameplay.

Several actions use standard filters to find out which units
to execute the command on. These are denoted by the phrases
"standard unit filter" and "standard location filter".

== See Also ==

* [[DirectActionsWML]]
* [[InternalActionsWML]]
* [[InterfaceActionsWML]]
* [[FilterWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

User:Xan

2006-01-25T16:43:37Z

Xan: /* Work In Progress: */

==Work In Progress:==
*WML Enhancement
** Unit Abilities
*Factions
** Frost Elves
** Faction X

===Planned:===
*Releasing the first version of [http://arcune.org/forum/index.php Spacenoth]
*Take over the world after everyone else.

===Completed:===
*[http://arcune.org/files/wesnoth/update.cpp Unit WML Updater]

== See Also == [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=101476 Xan's forum profile]
List & description of [[Developers]]

User:Xan

2006-01-23T19:01:02Z

Xan:

==Work In Progress:==
*WML Enhancement
** Unit Abilities

===Planned:===
*Releasing the first version of [http://arcune.org/forum/index.php Spacenoth]
*Take over the world after everyone else.

===Completed:===
*[http://arcune.org/files/wesnoth/update.cpp Unit WML Updater]

== See Also == [http://www.wesnoth.org/forum/profile.php?mode=viewprofile&u=101476 Xan's forum profile]
List & description of [[Developers]]

DirectActionsWML

2006-01-23T18:49:40Z

Xan: /* 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]]. An additional key 'random_traits' is allowed, which when set to 'yes' will randomly generate traits for the unit based on its type.
* '''[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

2006-01-22T21:23:36Z

Xan: /* [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)
** ''mode'' defaults to always_clear, which clears the variable, whether or not a match is found. If mode is set to replace, the variable will only be cleared if a match is found. If mode is set to append, the variable will not be cleared.
** ''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]]

Credits

2005-12-31T17:17:46Z

Xan: /* 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
* Dominic Bolin (Xan) - programmer
* 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}}