StartingPoints
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 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
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
- Units - Units stats and advance trees
- RaceDescriptions - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
- GraphicLibrary - unit and terrain images posted on the forums
- Wesnoth Acronyms (by category) - common wesnothian acronyms explained
- WesnothAcronyms (alphabetic) - common wesnothian acronyms explained
Tweaking the Game
- UserScenarios - user-written scenarios, campaigns and game modifications
- ReferenceWML - all about Wesnoth Markup Language
- BuildingCampaigns - how to make your own campaigns
- BuildingScenarios - how to make your own scenarios
- WesnothMapEditor - summary of controls
- CastleTutorial - how to create tileable castles and other castle-like tilesets
- ExternalUtilities - scripts to help create scenarios, campaigns, and graphics
Improving the Game
- ReportingBugs - use Savannah
Developer information
- DeveloperResources - useful links
- Changelog - the most recent changes made to the game
- WesnothCVS - accessing the source code
- HackingWesnoth - guide for programmers
- CodingStandards - for programmers
- UnitDescriptionRewriting - coordinating the revision
- Missing unit animations and sounds - what's available and what's missing
- WritingYourOwnAI - write a C++ plugin
- ThemeSystem - customizing the screen layout for the game and the editor
- ReleasingWesnoth - steps to follow to release a new version
- WesnothPackagersGuide - guidelines for packaging Wesnoth for different platforms
- WesnothPreferences
Game translations
- GettextForTranslators - how to translate Wesnoth under GetText
- WesnothTranslations - 11 complete, 2 almost complete, 7 more than halfway, 10 partial
- WesCamp - a project for translating user-made campaigns
Ideas
- FrequentlyProposedIdeas - before you propose an idea, check here!
- NewUnits - units that exist only in theory
- NewTerrains - tile status
- To submit a feature request, use http://bugs.wesnoth.org
About the Game
- WesnothPhilosophy - Dave on Wesnoth
- WesnothHistory - the Ages of Wesnoth
- WesnothGeography - description of Wesnoth and surrounding lands
- #wesnoth - our IRC channel
Other
- UsefulLinks
- WesnothLSM - presentation at LSM
- Wesnoth player's map - add yourself to the map!
- Wikipedia entry for Wesnoth
- WikiMigration - we are looking for a replacement