The Battle for Wesnoth Wiki - User contributions [en]

Support

2009-10-12T08:18:13Z

Blueblaze: Noted freenode/other servers

__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.
* [[StartingPoints|Starting Points]] - List of pages to serve as starting point for diving deeply into the wiki...
* [[MP_CodeOfConduct | Multiplayer Information ]] - Info about server moderators, useful MP commands, and our online Code of Conduct.

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

== Community ==

When asking for help with some technical problem in the game forums, please provide the following information:
* which operating system do you use (e.g. Windows, Linux, Mac OSX)
* which version of Wesnoth do you use (it is displayed in the bottom left corner of title screen)
* contents of file "stderr.txt"
** on MS Windows, it is here: "C:\Program Files\Wesnoth\stderr.txt"

=== Forums ===
* [http://www.wesnoth.org/forum/ Official Wesnoth forums]
* [[Wesnoth_Acronyms_and_Slang|Wesnoth Acronyms]] - forum lingo
* [http://www.wesnoth.cn Chinese wesnoth forums]
* [http://wif.altervista.org/index.php Wesnoth Italian Forums (W.I.F)]
* [http://www.wesnothlife.ru/forum/ Russian Wesnoth Forums]

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

All of the following channels use the freenode IRC network unless otherwise noted.

* [irc://irc.freenode.net/wesnoth #wesnoth] this channel is for general conversation amongst Wesnoth users and developers alike.
* [irc://irc.freenode.net/wesnoth-dev #wesnoth-dev] the development discussion channel. Most contributors and developers (WML, C++ and art people alike) hang around here, exchanging ideas and code patches.
* [irc://irc.freenode.net/wesnoth-mp #wesnoth-mp] the multiplayer servers' status and development discussion channel.
* [irc://irc.freenode.net/wesnoth-writing #wesnoth-writing] the channel for discussion of improving Wesnoth's writing
* [irc://irc.freenode.net/wesnoth-music #wesnoth-music]
* [irc://irc.freenode.net/wesnoth-umc-dev #wesnoth-umc-dev] the look-alike of #wesnoth-dev for the [http://www.wesnoth.org/forum/viewtopic.php?f=8&t=21413 Wesnoth User-made Add-ons Development] repository.
* [irc://irc.tweakers.net/wesnoth #wesnoth (Dutch channel)] Connect to irc.tweakers.net network
* [irc://irc.freenode.net/wesnoth-de #wesnoth-de (German channel)] the German look-alike of #wesnoth, mainly used by German-speaking users and translators.
* [irc://irc.freenode.net/wesnoth-pl #wesnoth-pl (Polish channel)] as above, but Polish
* [irc://irc.syrolnet.org/WIF #WIF (Italian channel)] Connect to irc.sylornet.org network
* [irc://irc.freenode.net/wesnoth-gl #wesnoth-gl (Galician channel)]
You can also see the [http://irclog.wesnoth.org/ logs] of the #wesnoth, #wesnoth-de, #wesnoth-dev and #wesnoth-umc-dev channels.

=== Mailing Lists ===
* [https://mail.gna.org/listinfo/wesnoth-dev/ wesnoth-dev] ([https://mail.gna.org/public/wesnoth-dev/ archives]): the mailing list for discussing mainline development issues; it is not intended for bug reports or feature requests. See [[ReportingBugs]] for those.
* [https://mail.gna.org/listinfo/wesnoth-commits/ wesnoth-commits] ([https://mail.gna.org/public/wesnoth-commits/ archives]): all commits made to the mainline SVN repository are automatically echoed in this list for those who want or need to keep track of them. New developers and contributors are required to subscribe to this list.
* [https://mail.gna.org/listinfo/wesnoth-i18n/ wesnoth-i18n] ([https://mail.gna.org/public/wesnoth-i18n/ archives]): the internationalization (i18n) mailing list; all translation team maintainers and the i18n managers should subscribe and keep track of announcements and discussions taking place in this list.

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

[[Category:Troubleshooting and Bugs]]

User:Blueblaze

2009-08-06T16:30:35Z

Blueblaze: Updated zombie survival to 1.2

Here is a list of all the addons I have completed for Wesnoth. This list will continue to be updated with each new release so feel free to watch this page to keep up to date.
 
 '''1.6.x Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=26415 Conquest]
 Version 1.0: July 26, 2009
 Type: Non-standard
 Players: 1-9p
 This game is not a Risk clone, but simply draws on the ideas and concepts that fuel the game. Gameplay involves only 3 units, simplified combat, simple economy, but a battles of epic proportions. The package includes 2 maps: a modified version of a well known world map and a map of Europe created by myself.
 
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=25112 Zombie Survival]
 Version 1.2: August 6, 2009
 Version 1.1: April 24, 2009
 Version 1.0: April 17, 2009
 Type: Non-standard
 Players: 1-6p
 A simple concept of surviving the waves of zombies until you can defeat the enemy leader. Select custom units and upgrade your character to ensure the survival of your party.
 [http://www.wesnoth.org/forum/download/file.php?id=30250 Map Screen Shot]
 
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24942 Survival Fusion 2]
 Version: 2.0 [Released: April 10, 2009]
 Type: Non-standard
 Players: 2-4p
 Unique gameplay inspired by the board game Risk.
 [http://www.wesnoth.org/forum/download/file.php?id=30055 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24804 Empires]
 Version: 1.1 [Released: July 17, 2009] - Added 2 new maps
 Version: 1.0 [Released: April 3, 2009]
 Type: Non-standard
 Players: 2-9p
 Sequel to the popular Survival Fusion. Survive the incoming waves of enemies while fending off your opponents.
 [http://www.wesnoth.org/forum/download/file.php?id=29829 Map Screen Shot (Deep Island)]
 
 
 
 '''Older Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=20686 Living Caves]
 1.4.x - Version: 1.0 [Released: March 29, 2008]
 Type: Non-standard
 Players: 4p - 2v2 with 1 AI
 Every aspect of the game is randomized for a new experience every game.
 [http://www.wesnoth.org/forum/download/file.php?id=21740 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x - Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Level One Era]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: Era
 This era allows you to use the default level one units as your starting heros. This era also adds a monster faction for you to select heros from as well. This era works great for RPGs but also will work well on any map as recruitment has been enabled as well.
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x - Version: 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x - Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x - Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

User:Blueblaze

2009-07-26T06:49:17Z

Blueblaze: Added Empires updated and Conquest

Here is a list of all the addons I have completed for Wesnoth. This list will continue to be updated with each new release so feel free to watch this page to keep up to date.
 
 '''1.6.x Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=26415 Conquest]
 Version 1.0: July 26, 2009
 Type: Non-standard
 Players: 1-9p
 This game is not a Risk clone, but simply draws on the ideas and concepts that fuel the game. Gameplay involves only 3 units, simplified combat, simple economy, but a battles of epic proportions. The package includes 2 maps: a modified version of a well known world map and a map of Europe created by myself.
 
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=25112 Zombie Survival]
 Version 1.1: April 24, 2009
 Version 1.0: April 17, 2009
 Type: Non-standard
 Players: 1-6p
 A simple concept of surviving the waves of zombies until you can defeat the enemy leader. Select custom units and upgrade your character to ensure the survival of your party.
 [http://www.wesnoth.org/forum/download/file.php?id=30250 Map Screen Shot]
 
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24942 Survival Fusion 2]
 Version: 2.0 [Released: April 10, 2009]
 Type: Non-standard
 Players: 2-4p
 Unique gameplay inspired by the board game Risk.
 [http://www.wesnoth.org/forum/download/file.php?id=30055 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24804 Empires]
 Version: 1.1 [Released: July 17, 2009] - Added 2 new maps
 Version: 1.0 [Released: April 3, 2009]
 Type: Non-standard
 Players: 2-9p
 Sequel to the popular Survival Fusion. Survive the incoming waves of enemies while fending off your opponents.
 [http://www.wesnoth.org/forum/download/file.php?id=29829 Map Screen Shot (Deep Island)]
 
 
 
 '''Older Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=20686 Living Caves]
 1.4.x - Version: 1.0 [Released: March 29, 2008]
 Type: Non-standard
 Players: 4p - 2v2 with 1 AI
 Every aspect of the game is randomized for a new experience every game.
 [http://www.wesnoth.org/forum/download/file.php?id=21740 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x - Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Level One Era]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: Era
 This era allows you to use the default level one units as your starting heros. This era also adds a monster faction for you to select heros from as well. This era works great for RPGs but also will work well on any map as recruitment has been enabled as well.
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x - Version: 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x - Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x - Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

User:Blueblaze

2009-04-24T16:10:20Z

Blueblaze: Corrected player amount for zombie survival

Here is a list of all the addons I have completed for Wesnoth. This list will continue to be updated with each new release so feel free to watch this page to keep up to date.
 
 '''1.6.x Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=25112 Zombie Survival]
 Version 1.1: April 24, 2009
 First Release: April 17, 2009
 Type: Non-standard
 Players: 1-6p
 A simple concept of surviving the waves of zombies until you can defeat the enemy leader. Select custom units and upgrade your character to ensure the survival of your party.
 [http://www.wesnoth.org/forum/download/file.php?id=30250 Map Screen Shot]
 
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24942 Survival Fusion 2]
 Version: 2.0 [Released: April 10, 2009]
 Type: Non-standard
 Players: 2-4p
 Unique gameplay inspired by the board game Risk.
 [http://www.wesnoth.org/forum/download/file.php?id=30055 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24804 Empires]
 Version: 1.0 [Released: April 3, 2009]
 Type: Non-standard
 Players: 2-9p
 Sequel to the popular Survival Fusion. Survive the incoming waves of enemies while fending off your opponents.
 [http://www.wesnoth.org/forum/download/file.php?id=29829 Map Screen Shot (Deep Island)]
 
 
 
 '''Older Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=20686 Living Caves]
 1.4.x - Version: 1.0 [Released: March 29, 2008]
 Type: Non-standard
 Players: 4p - 2v2 with 1 AI
 Every aspect of the game is randomized for a new experience every game.
 [http://www.wesnoth.org/forum/download/file.php?id=21740 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x - Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Level One Era]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: Era
 This era allows you to use the default level one units as your starting heros. This era also adds a monster faction for you to select heros from as well. This era works great for RPGs but also will work well on any map as recruitment has been enabled as well.
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x - Version: 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x - Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x - Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

User:Blueblaze

2009-04-24T16:09:36Z

Blueblaze: Added Zombie Survial to the list

Here is a list of all the addons I have completed for Wesnoth. This list will continue to be updated with each new release so feel free to watch this page to keep up to date.
 
 '''1.6.x Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=25112 Zombie Survival]
 Version 1.1: April 24, 2009
 First Release: April 17, 2009
 Type: Non-standard
 Players: 2-6p
 A simple concept of surviving the waves of zombies until you can defeat the enemy leader. Select custom units and upgrade your character to ensure the survival of your party.
 [http://www.wesnoth.org/forum/download/file.php?id=30250 Map Screen Shot]
 
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24942 Survival Fusion 2]
 Version: 2.0 [Released: April 10, 2009]
 Type: Non-standard
 Players: 2-4p
 Unique gameplay inspired by the board game Risk.
 [http://www.wesnoth.org/forum/download/file.php?id=30055 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24804 Empires]
 Version: 1.0 [Released: April 3, 2009]
 Type: Non-standard
 Players: 2-9p
 Sequel to the popular Survival Fusion. Survive the incoming waves of enemies while fending off your opponents.
 [http://www.wesnoth.org/forum/download/file.php?id=29829 Map Screen Shot (Deep Island)]
 
 
 
 '''Older Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=20686 Living Caves]
 1.4.x - Version: 1.0 [Released: March 29, 2008]
 Type: Non-standard
 Players: 4p - 2v2 with 1 AI
 Every aspect of the game is randomized for a new experience every game.
 [http://www.wesnoth.org/forum/download/file.php?id=21740 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x - Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Level One Era]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: Era
 This era allows you to use the default level one units as your starting heros. This era also adds a monster faction for you to select heros from as well. This era works great for RPGs but also will work well on any map as recruitment has been enabled as well.
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x - Version: 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x - Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x - Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

User:Blueblaze

2009-04-12T07:47:05Z

Blueblaze: Fixed typo

Here is a list of all the addons I have completed for Wesnoth. This list will continue to be updated with each new release so feel free to watch this page to keep up to date.
 
 '''1.6.x Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24942 Survival Fusion 2]
 Version: 2.0 [Released: April 10, 2009]
 Type: Non-standard
 Players: 2-4p
 Unique gameplay inspired by the board game Risk.
 [http://www.wesnoth.org/forum/download/file.php?id=30055 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24804 Empires]
 Version: 1.0 [Released: April 3, 2009]
 Type: Non-standard
 Players: 2-9p
 Sequel to the popular Survival Fusion. Survive the incoming waves of enemies while fending off your opponents.
 [http://www.wesnoth.org/forum/download/file.php?id=29829 Map Screen Shot (Deep Island)]
 
 
 
 '''Older Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=20686 Living Caves]
 1.4.x - Version: 1.0 [Released: March 29, 2008]
 Type: Non-standard
 Players: 4p - 2v2 with 1 AI
 Every aspect of the game is randomized for a new experience every game.
 [http://www.wesnoth.org/forum/download/file.php?id=21740 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x - Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Level One Era]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: Era
 This era allows you to use the default level one units as your starting heros. This era also adds a monster faction for you to select heros from as well. This era works great for RPGs but also will work well on any map as recruitment has been enabled as well.
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x - Version: 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x - Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x - Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

User:Blueblaze

2009-04-12T07:40:18Z

Blueblaze: Added Survival Fusion 2

Here is a list of all the addons I have completed for Wesnoth. This list will continue to be updated with each new release so feel free to watch this page to keep up to date.
 
 '''1.6.x Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24942 Survival 2]
 Version: 2.0 [Released: April 10, 2009]
 Type: Non-standard
 Players: 2-4p
 Unique gameplay inspired by the board game Risk.
 [http://www.wesnoth.org/forum/download/file.php?id=30055 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=24804 Empires]
 Version: 1.0 [Released: April 3, 2009]
 Type: Non-standard
 Players: 2-9p
 Sequel to the popular Survival Fusion. Survive the incoming waves of enemies while fending off your opponents.
 [http://www.wesnoth.org/forum/download/file.php?id=29829 Map Screen Shot (Deep Island)]
 
 
 
 '''Older Add-ons:'''
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=20686 Living Caves]
 1.4.x - Version: 1.0 [Released: March 29, 2008]
 Type: Non-standard
 Players: 4p - 2v2 with 1 AI
 Every aspect of the game is randomized for a new experience every game.
 [http://www.wesnoth.org/forum/download/file.php?id=21740 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x - Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Level One Era]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: Era
 This era allows you to use the default level one units as your starting heros. This era also adds a monster faction for you to select heros from as well. This era works great for RPGs but also will work well on any map as recruitment has been enabled as well.
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x - Version: 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x - Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x - Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

User:Blueblaze

2009-04-03T05:39:50Z

Blueblaze: Minor format editting

User:Blueblaze

2009-04-03T05:38:47Z

Blueblaze: New map released: Empires

User:Blueblaze

2009-03-26T18:25:23Z

Blueblaze: Fixed intro message

User:Blueblaze

2008-03-29T18:03:44Z

Blueblaze: Added Living Caves

Here is a list of all the addons I have completed for Wesnoth. This list will continue to be updated with each new release so feel free to watchlist this page to keep up to date.
 
 
 Released Addons:
 
 [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=20686 Living Caves]
 1.4.x - Version: 1.0 [Released: March 29, 2008]
 Type: Standard with Variation
 Players: 4p - 2v2 with 1 AI
 Every aspect of the game is randomized for a new experience every game.
 [http://www.wesnoth.org/forum/download/file.php?id=21740 Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x - Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Level One Era]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: Era
 This era allows you to use the default level one units as your starting heros. This era also adds a monster faction for you to select heros from as well. This era works great for RPGs but also will work well on any map as recruitment has been enabled as well.
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x - Version: 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x - Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x - Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

Tools for Creating Music

2008-03-28T03:08:54Z

Blueblaze: /* Samples */ Added non-free samples

== Hardware ==

== Software ==
=== Non-Free ===
Pro-grade (thus quite costly) applications:
* [http://www.steinberg.net/983_1.html Cubase] Mac / Windows
* [http://www.apple.com/logicstudio/logicpro/ Logic Studio] Mac
* [http://www.cakewalk.com/Products/SONAR/default.asp Sonar] Windows
* [http://www.digidesign.com/index.cfm?navid=24&langid=100& ProTools] Mac / Windows
Less expensive alternatives:
* [http://www.cockos.com/reaper/ REAPER] Mac / Windows
* [http://www.flstudio.com/ FL Studio] Windows

=== Free ===
* [http://ardour.org/ Ardour] Linux
* [http://audacity.sourceforge.net/ Audacity] - Cross platform digital audio editor

== Samples ==
=== Non-Free ===
* [http://www.garritan.com/GPO.html Garritan Personal Orchestra] $200 Full orchestral samples.

* [http://www.eastwestsamples.com/details.php?cd_index=797 East West Samples (Platinum, Gold, Silver)] Check other websites for much lower prices than retail. One of the most expensive, but most powerful samples commercially available.

=== Free ===
* [http://hosted.filefront.com/gtownsounds G-Town Percussion] Excellent orchestral percussion sounds.

* [http://www.northernsounds.com/forum/showthread.php?t=51293 Celtic Harp] Beautiful 250MB celtic harp soundfont (d/l links are in the thread; there's also a giga version available)

* [http://come.to/bovbjerg Soeren Bovbjerg's Pianos] A few pianos in sf2/gig format. Sound good considering their size.

* Very good clarinet by Mats Helgesson (the site requires registration):
** [http://www.sf2midi.com/index.php?page=sdet&id=7017 Maestro clarinet Legato]
** [http://www.sf2midi.com/index.php?page=sdet&id=6675 Maestro clarinet Breath]
** [http://www.sf2midi.com/index.php?page=sdet&id=6674 Maestro clarinet Staccato]

* [http://lesitedeburnie.free.fr/matshelgesson-maestro-en.html Maestro Concert Grand] 985MB concert grand piano by Mats Helgesson.

* [http://www.sf2midi.com/index.php?page=sdet&id=9337 Alex Glockenspiel] A nice little glockenspiel.

* [http://www.emulatorxone.com/free_emulator_x_sounds/free_emulator_x_sounds.htm EmulatorXone Trumpet] 60 meg solo trumpet in emulatorX format.

* [http://www.sf2midi.com/index.php?page=sdet&id=6050 Douglas Concert Timpani] Very good timpani freebie from Naturalstudio.

* [http://www.projectsam.com/ Project SAM] A number of pro-quality freebies, among other things some really cool percussion samples. Registration required.

[[Category:Music]]

Tools for Creating Music

2008-03-14T00:51:09Z

Blueblaze: /* Free */ Fixed syntax

== Hardware ==

== Software ==
=== Non-Free ===
Pro-grade (thus quite costly) applications:
* [http://www.steinberg.net/983_1.html Cubase] Mac / Windows
* [http://www.apple.com/logicstudio/logicpro/ Logic Studio] Mac
* [http://www.cakewalk.com/Products/SONAR/default.asp Sonar] Windows
* [http://www.digidesign.com/index.cfm?navid=24&langid=100& ProTools] Mac / Windows
Less expensive alternatives:
* [http://www.cockos.com/reaper/ REAPER] Mac / Windows
* [http://www.flstudio.com/ FL Studio] Windows

=== Free ===
* [http://ardour.org/ Ardour] Linux
* [http://audacity.sourceforge.net/ Audacity] - Cross platform digital audio editor

== Samples ==
=== Non-Free ===
=== Free ===
* [http://hosted.filefront.com/gtownsounds G-Town Percussion] Excellent orchestral percussion sounds.

* [http://www.northernsounds.com/forum/showthread.php?t=51293 Celtic Harp] Beautiful 250MB celtic harp soundfont (d/l links are in the thread; there's also a giga version available)

* [http://come.to/bovbjerg Soeren Bovbjerg's Pianos] A few pianos in sf2/gig format. Sound good considering their size.

* Very good clarinet by Mats Helgesson (the site requires registration):
** [http://www.sf2midi.com/index.php?page=sdet&id=7017 Maestro clarinet Legato]
** [http://www.sf2midi.com/index.php?page=sdet&id=6675 Maestro clarinet Breath]
** [http://www.sf2midi.com/index.php?page=sdet&id=6674 Maestro clarinet Staccato]

* [http://lesitedeburnie.free.fr/matshelgesson-maestro-en.html Maestro Concert Grand] 985MB concert grand piano by Mats Helgesson.

* [http://www.sf2midi.com/index.php?page=sdet&id=9337 Alex Glockenspiel] A nice little glockenspiel.

* [http://www.emulatorxone.com/free_emulator_x_sounds/free_emulator_x_sounds.htm EmulatorXone Trumpet] 60 meg solo trumpet in emulatorX format.

* [http://www.sf2midi.com/index.php?page=sdet&id=6050 Douglas Concert Timpani] Very good timpani freebie from Naturalstudio.

* [http://www.projectsam.com/ Project SAM] A number of pro-quality freebies, among other things some really cool percussion samples. Registration required.

[[Category:Music]]

Tools for Creating Music

2008-03-14T00:50:33Z

Blueblaze: /* Free */ added link

== Hardware ==

== Software ==
=== Non-Free ===
Pro-grade (thus quite costly) applications:
* [http://www.steinberg.net/983_1.html Cubase] Mac / Windows
* [http://www.apple.com/logicstudio/logicpro/ Logic Studio] Mac
* [http://www.cakewalk.com/Products/SONAR/default.asp Sonar] Windows
* [http://www.digidesign.com/index.cfm?navid=24&langid=100& ProTools] Mac / Windows
Less expensive alternatives:
* [http://www.cockos.com/reaper/ REAPER] Mac / Windows
* [http://www.flstudio.com/ FL Studio] Windows

=== Free ===
* [http://ardour.org/ Ardour] Linux
* [http://audacity.sourceforge.net/ Audacity] - Cross platform Digital Audio Editor

== Samples ==
=== Non-Free ===
=== Free ===
* [http://hosted.filefront.com/gtownsounds G-Town Percussion] Excellent orchestral percussion sounds.

* [http://www.northernsounds.com/forum/showthread.php?t=51293 Celtic Harp] Beautiful 250MB celtic harp soundfont (d/l links are in the thread; there's also a giga version available)

* [http://come.to/bovbjerg Soeren Bovbjerg's Pianos] A few pianos in sf2/gig format. Sound good considering their size.

* Very good clarinet by Mats Helgesson (the site requires registration):
** [http://www.sf2midi.com/index.php?page=sdet&id=7017 Maestro clarinet Legato]
** [http://www.sf2midi.com/index.php?page=sdet&id=6675 Maestro clarinet Breath]
** [http://www.sf2midi.com/index.php?page=sdet&id=6674 Maestro clarinet Staccato]

* [http://lesitedeburnie.free.fr/matshelgesson-maestro-en.html Maestro Concert Grand] 985MB concert grand piano by Mats Helgesson.

* [http://www.sf2midi.com/index.php?page=sdet&id=9337 Alex Glockenspiel] A nice little glockenspiel.

* [http://www.emulatorxone.com/free_emulator_x_sounds/free_emulator_x_sounds.htm EmulatorXone Trumpet] 60 meg solo trumpet in emulatorX format.

* [http://www.sf2midi.com/index.php?page=sdet&id=6050 Douglas Concert Timpani] Very good timpani freebie from Naturalstudio.

* [http://www.projectsam.com/ Project SAM] A number of pro-quality freebies, among other things some really cool percussion samples. Registration required.

[[Category:Music]]

DeveloperResources

2008-02-25T22:02:45Z

Blueblaze: /* General */ fixed link to Wesnoth_Acronyms_and_Slang

== General ==
* Forum - http://forum.wesnoth.org
* Wiki :
** http://www.wesnoth.org/wiki/Main_Page
** [[GettingStarted]]
** [[FrequentlyProposedIdeas]] - summary of past often-repeated forum discussions
** [[Wesnoth_Acronyms_and_Slang]]

== Game - Play ==
* units - http://units.wesnoth.org/
* unit list - http://zapicm.freeshell.org/stable/
* movement types & resistance - http://zapicm.freeshell.org/stable/data/

== Game - Create content ==
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

== Communication, Feedback ==
* Gna! links
** Gna! - bugs and feature requests - http://bugs.wesnoth.org/
** Gna! - patches - http://patches.wesnoth.org/

* Mailing lists:
** wesnoth-dev - https://mail.gna.org/listinfo/wesnoth-dev/
** wesnoth-commits - https://mail.gna.org/listinfo/wesnoth-commits/

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

== Code, Development ==
* changelog - http://changelog.wesnoth.org/
* Up-to-date commit messages : http://cia.vc/stats/project/wesnoth
* Documentation generator [[Doxygen]]
** generated code documentation - http://devdocs.wesnoth.org
* gettext status - http://gettext.wesnoth.org/

* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* Standard Template Library - http://www.sgi.com/tech/stl/
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [[WesnothSVN]] - SVN instructions
* Gna! - websvn - http://websvn.wesnoth.org/ Web-Access to svn
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
* [[HackingWesnoth]]
* [[CodingStandards]]

[[Category:Committers]]

How to play Rebels

2008-02-25T22:02:01Z

Blueblaze: /* General Rebel Strategies: */ fixed link to Wesnoth_Acronyms_and_Slang

==General Rebel Strategies:==

On the first turn when you have a random opponent it is good to get a mixture of units. A Scout, Merman, Archer, 2 Fighters, and a Mage 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.

[[Rebels]] have good to great defense in forest. Try to keep them there whenever possible, as obvious as that is. Even the easily hit '''Wose''' has his best defense (still hit more often than missed) in forest.

Elves are Neutral in alignment, so attack when your opponent is at their weakest. The '''Mage''', '''Wose''', and '''Merman''' are Lawful however, so take this into consideration if you recruit these units. You will be strongest in the day, but if your opponent is also strongest in the day it is usually best to fight at night.

One of the Rebels' greatest strengths is their abundance of ranged attacks in harmony with the Dextrous trait. This characteristic gives Rebels frequent chances to attack without taking retaliation damage. It also guarantees any opponent attacking you will take some damage in return.

Rebels also have good mobility, their Scout having the highest level 1 movement in the game (9 moves). The deadly '''Archer''' is also gifted with 6 - both are also graced with the speedy woodland movetype. Use this mobility to your advantage early by taking a village advantage and later by [[Wesnoth_Acronyms_and_Slang|ZOC]]ing your opponents weakened units.

If you happen to use '''Elvish Captain''' as a leader (or to level up a '''Fighter'''), take the advantage of his Leadership. He's one of the fastest leaders, so on small maps can get to fighting line in 2 turns. Not that amazing himself, his Leadership gives nearby units +25% bonus. That's an advantage you use day-night cycle for, that's the difference between retreat and attack. When properly positioned, he can boost 3 or even 4 units a turn. Of course, this works best combined with other advantages like time of day or good unit unit matchup. Mages and Woses under his banner tear Undead in halfs.

There's always need for a trick. '''Shamans''' do three good things:
* +4 healing is never bad (though they rarely level up to give you +8);
* slow enemy units, which halves their movement and damage for a turn. The more powerful or quick your enemy is, the more useful the ability becomes;
* they have 70% defense in Forests, so, when in bad need, can stop non-magical enemies with own ZoC.

==Rebels vs Undead==
Your lot of Piercing damage is useless against their units dealing most damage - Skeletons. So no point in fighting Skeletons with Elves.
Your weapon are Woses and Mages. Opponent has no hard counter, but their "weak" units still do good: Skeletons for your Mages, Dark Adepts and Ghouls for Woses. Remember that Ghoul's poison stops Wose from regenerating for a turn. That's 8 damage in addition to its 3.

As always, you need a couple of Scouts to capture villages. Don't get with them into fight: if one lures two opponent's units from your main force, it's fine.

Shaman is always good for her healing and slowing, and does Impact damage.

Keep your Woses high on HP. Wose is slow - 4 base movement - so it takes ages to deliver him to fighting lines, more then delivering a Mage. Count as if you get a Wose 2 turns later. Still, it's your main strike force again most of Undead.

Another Undead's option is Walking Corpses. They do good damage for the money, have no upkeep and sometimes can 'recruit' your people. There's no clear counter except Archers, but archers are weak in this matchup. Just watch for your unit hit points and retreat timely.

So start with 2 Woses, 1-2 Scouts, Mage, Shaman and someone of your choice: Mage, Fighter or Merman.

==Rebels vs Knalgans==

One of the tricks with the rebels vs. knalgans is to '''really''' use the shamans to their full potential. It comes in two forms; first, shamans in forest are surprisingly durable; they have the defense and hitpoints of a thief, but lack the weakness to physical weapons. That, '''and''' they have retaliatory slowing on ranged (and can slow some of the worse melee attackers). Especially shamans in pairs, or even better - shamans backed up by a druid, can nearly stop a small group of melee dwarves from progressing into forest.

Shamans allow you to do one game-changing thing, which is that you can slow a dangerous melee unit, and then attack said melee unit with your fighters. Normally, attacking a dwarven fighter on grass, with your elven fighter, would be a "fair fight", and thus would be very stupid for you to engage in - the general trick to winning a game like wesnoth is to engage your units in combat only when you can arrange a fight that '''isn't''' fair. Usually it's terrain, or being outnumbered that does this, but shamans allow you to, for the space of one turn, make a normally fair fight suddenly very unfair in your favor. It allows you to do this where other factions cannot manage this, such as on open ground.

With shamans, you want to slow as many units as you can; but chiefly you'll want to find whichever "dangerous unit" is the most accessible for you to assign units to attack, and so long as you can keep most of the enemy from retaliating (say, if you slow their three hardest melee hitters), slow him, and then break rank with whatever you can attack the thing with. You'll end the turn with a few lightly scratched fighters (missing maybe 4-8 hp each), and your enemy will either have a nearly or completely dead fighter/gryphon. And conveniently, if those fighters ended their combat next to shamans, you will quickly recoup said "scratches". Woses are also very useful for these kinds of tactics - you can slow their victim, and whatever damage they receive will likely be 8hp or below. A corollary to this is that if you ever have the chance, slow an ulf, and immediately eliminate him with a fighter/wose - it's nearly a free kill.

As usual, if at all possible, get a druid, and get a captain. These level-2 abilities really enhance the elves' capability; the captain, for example, generally negates the effect of the dwarves' armor. The druid's a bit mean when applied to units with 60-70% defense (it's like turning all forest tiles into villages). These kinds of level-2 abilities are something the dwarves don't have access to, so use them to your advantage whenever possible. After you get one captain and one druid, you'll generally want to make any other level-ups into heroes and sorceresses, to give you a bit more firepower (and in the case of the former, something that can actually tank decently for the elves).

==Rebels vs Drakes==
You are in not-too-good position:
* Drakes have good speed (can grab villages quickly) and have good HP;
* Which is worse, '''Saurian Skirmisher''' kills your only village-grabber, '''Scout''', in 5 blows, while always has good defense and speed, so you'll have to retreat Scout and lose some gold;
* You don't have Cold attack which Drakes are vulnerable to;

To exploit Drakes' lesser weakness, to Pierce, have more '''Archers''' then '''Fighters'''. Though, Fighters are cheap, do a good backfire, and one can level up to '''Captain'''.

Have '''Shamans''' to slow '''Clashers''' and '''Fighters'''.

Have '''Scout''' or two. In this matchup it's especially important to keep good amount of villages.

If opponent goes for '''Saurians''', recruit '''Mage''' or two. They pick Saurians out of swamps very well.

==See also==
[[How_to_play...]] series.

[[How to play Mages]]

[[Category:Playing Wesnoth]]

Support

2008-02-25T22:00:34Z

Blueblaze: /* Forums */ fixed link to Wesnoth_Acronyms_and_Slang

__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
* [[StartingPoints|Starting Points]] - List of pages to serve as starting point for diving deeply into the wiki...

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

== Community ==

When asking for help with some technical problem in the game forums, please provide the following information:
* which operating system do you use (e.g. Windows, Linux, Mac OSX)
* which version of Wesnoth do you use (it is displayed in the bottom left corner of title screen)
* contents of file "stderr.txt"
** on MS Windows, it is here: "C:\Program Files\Wesnoth\stderr.txt"

=== Forums ===
* [http://www.wesnoth.org/forum/ Official Wesnoth forums]
* [[Wesnoth_Acronyms_and_Slang|Wesnoth Acronyms]] - forum lingo
* [http://www.wesnoth.cn Chinese wesnoth forums]

=== 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.freenode.net/wesnoth-mp #wesnoth-mp]

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

* [irc://irc.freenode.net/wesnoth.cn #wesnoth (Chinese 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])
* [https://mail.gna.org/listinfo/wesnoth-i18n/ wesnoth-i18n] ([https://mail.gna.org/public/wesnoth-i18n/ archives])

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

[[Category:Troubleshooting and Bugs]]

PL:HomePage

2008-02-25T21:53:06Z

Blueblaze: /* Informacje */ Fixed link to Wesnoth_Acronyms_and_Slang

__NOTOC__
Ostatnia edycja : 09:52, 16 March 2007 (CET)
{{tpl}}
Bitwa o Wesnoth jest turową grą strategiczną w klimatach fantasy.

Pokonaj wszystkich wrogich przywódców wykorzystując świetnie dobraną grupę jednostek jednocześnie zarządzając złotem i ilością kontrolowanych wiosek. Każda jednostka ma swoje silne i słabe strony, aby wygrac rozmieść swoje wojska jak nakorzystniej jednocześnie uniemożliwiając to przeciwnikowi. Wraz ze wzrostem doświadczenia twoje jednostki zyskują nowe możliwości i stają się silniejsze. Graj we własnym językutestując umiejętności w starciu ze sprytną sztuczną inteligencją lub dołącz do do społeczności graczy sieciowych. Twórz własne jednostki, scenariusze i kampanie dzieląc się nimi z innymi.

Bitwa o Wesnoth jest wydana na licencji [http://www.gnu.org/licenses/licenses.html#GPL GPL]. Gotowe pakiety są dostępne dla większości systemów operacyjnych (Windows, Mac OS X, GNU/Linux), możesz też zbudować własny z kodów źródłowych.

== Zdobywanie Gry ==
==== Pobieranie ====
* [[Download|Pobierz (''en'')]] - pobierz najnowsze kody źródłowe i wiele plików binarnych
** [[WesnothBinaries|WesnothBinarnie (''en'')]] - prekompilowany dla GNU/Linux, BeOS, PDAs, ...
** [[WesnothBinariesLinux|WesnothBinarnieLinux (''en'')]] - prekompilowany dla wielu dystrybucji GNU/Linux

==== Kompilowanie ====
* [[CompilingWesnoth|KompilowanieWesnoth (''en'')]] - dla Unix, Mac, Windows, GNU/Linux, PDAs, ...
* [[DebuggingWesnoth|OdpluskwianieWesnoth (''en'')]] - dla GNU/Linux i systemów Unixopodobnych
* [[WesnothOnLinuxPDAs|WesnothDlaLinuxaNaPDA (''en'')]] - dla serii Qtopia/OPIE i thepdaXrom/Zaurus C

== Granie w Wesnoth ([[PL:Play|Graj (''en'')]]) ==

==== Dla Nowych Graczy ====
* [[GettingStarted|Poczatki (''en'')]] - przeczytaj najpierw!
* [[WesnothManual|PodręcznikWesnoth (''en'')]] - zasady
* [[MainlineCampaigns|ScenariuszePodstawowe (''en'')]] - podpowiedzi do kampani dostarczanych z grą

==== Dla Nie-Tak-Znowu-Nowych Graczy ====
* [[AdvancedTactics|ZaawansowanaTaktyka (''en'')]] - jak pokonać SI i innych ludzi
* [[MultiplayerServers|SerweryMultiplayer]] - gdzie można zagrać z innymi ludźmi w internecie

==== Informacje ====
* [[HotKeysSystem|SkrótyKlawiaturowe (''en'')]] - skróty klawiaturowe
* [[CommandMode|TrybPoleceń (''en'')]] - lista poleceń których można użyć w grze
* [[ServerAdministration|AdministracjaSerwerem (''en'')]] - komendy które upoważnieni użytkownicy mogą wykorzystać do administracji serwerem
* [http://zapicm.freeshell.org Jednostki (''en'')] - drzewo promocji jednostek i statystyki
** [http://zapicm.freeshell.org/dev Wersja rozwojowa (''en'')]
** [http://zapicm.freeshell.org/stable Wesja stabilna (''en'')]
** [http://zapicm.freeshell.org/trunk Najnowsza wersja (''en'')]
* [[RaceDescriptions|OpisyRas (''en'')]] - Elfy, Ludzie, Krasnoludy, Orki, Smoki, Nieumarli, Inne
** [[Complete_Faction_List_%28unfinished%29|(Prawie)KompletnaListaFrakcji (''en'')]] - lista wszystkich (prawie) frakcji stworzonych przez użytkowników
* [[Wesnoth_Acronyms_and_Slang|SkrótyWesnoth (''en'')]] - popularne skróty występujące w grze i społeczności

== Modyfikowanie Gry ([[PL:Create|Stwórz (''en'')]]) ==

* [[UserScenarios|ScenariuszeUżytkowników]] - scenariusze, kampanie i modyfikacje gry stworzone przez społeczność
* [[ReferenceWML|EncyklopediaWML]] i [[AlphabeticalWML|WMLAlfabetycznie]] - wszystko o WML (języku znaczników Wesnoth)
* [[ReferencePythonAPI|EncyklopediaPythonAPI]] - nadchodzący interfejs Pythona do SI
* [[BuildingCampaigns|BudowanieKampanii]] - jak stworzyć własną kampanię dla jednego gracza
* [[MultiplayerCampaigns|KampanieDlaWieluGraczy]] - jak stworzyć kampanię do trybu wieloosobowego
* [[BuildingScenarios|BudowanieScenariusza]] - jak stworzyć własny scenariusz
* [[BuildingUnits|BudowanieJednostek]] - jak stworzyć własne jednostki
* [[UnitAnalysis|AnalizaJednostek]] - narzędzie do analizy jednostek
* [[WesnothMapEditor|EdytorMap]] - opis interfejsu
* [[ExternalUtilities|ProgramyUżytkowe]] - skrypty pomocne przy tworzeniu kampani, scenariuszy i grafik
* [[Create_Art#Art_Tutorials|SamouczkiGraficzne]] - pomoc w tworzeniu grafiki
* [[GraphicLibrary|BibliotekaGrafiki]] - ikony jednostek i terenu zamieszczone na forum
* [[Tiles_Status|StatusTerenu]] - elementy terenu proponowane i będące w trakcie prac

== Poprawianie Gry ==
* [[ReportingBugs|ZgłaszanieBłędów]] - używamy Gna
* prośby o dodanie nowego elementu do gry zamieszczamy na http://bugs.wesnoth.org
* [[FrequentlyProposedIdeas|CzęstoZgłaszanePomysły]] - zanim coś zaproponujesz sprawdź czy nie ma tego tutaj!
==== Informacja Dla Developerów ====
* [[DeveloperResources|ZasobyDlaDeveloperów]] - pożyteczne odnośniki
* [http://changelog.wesnoth.org Changelog|ListaZmian] - najnowsze zmiany w grze
* [[WesnothSVN]] - dostęp do kodu źródłowego
* [[HackingWesnoth|ModyfikowanieWesnoth]] - przewodnik programisty
* [[CodingStandards|StandartKodowania]] - dla programistów
* [[UnitDescriptionRewriting|UaktualnianieOpisówJednostek]] - koordynacja korekt
* [http://wesnoth.slack.it/missing.cgi Missing unit animations and sounds|BrakująceAnimacjeIDźwiękiJednostek] - co jest dostępne i czego brakuje
* [[WritingYourOwnAI|NapiszWłasnąSI]] - jako plugin C++
* [[ThemeSystem|SystemMotywów]] - dostosowywanie rozmieszczenia elementów na ekranie w edytorze i grze
* [[ReleasingWesnoth|PublikowanieWesnoth]] - kroki które należy podjąć, żeby opublikować nową wersję
* [[WesnothPackagersGuide|PrzewodnikDlaTwórcówPaczek]] - wskazówki do przygotowywania Wesnoth dla różnych platform
* [[EasyCoding|ProsteKodowanie]] - błędy oraz elementy łatwe w implementacji dla początkujących koderów
* [[NotSoEasyCoding|NieTakProsteKodowanie]] - Błędy oraz elementy możliwe do wykonania, którym brakuje kogoś kto by nad nimi popracował
* [[WesnothGL]] - przewodnik do programowania Wesnoth w OpenGL

==== Tłumaczenia Gry ====
* [[GettextForTranslators|GettextDlaTłumaczy]] - jak przetłumaczyć Wesnoth w [[GetText]]
* [[WesnothTranslations|Tłumaczenia]] - 11 zakończonych, 2 prawie gotowych, 7 w połowie, 10 częściowych
* [[WesCamp]] - projekt tłumaczenia kampanii stworzonych przez użytkowników.

== O Grze ==
* [[WesnothPhilosophy|Filozofia]] - Dave o Wesnoth
* [[WesnothHistory|Historia]] - wieki Wesnoth
* [[WesnothGeography|Geografia]] - opis Wesnoth i otaczających krain
* [[WesnothReviews|Recenzje]] - niezależne recenzje
* [irc://irc.wesnoth.org/wesnoth #wesnoth] - nasz kanał IRC
* [[Donate|Wesprzyj]] lub [http://cafepress.com/wesnoth KupProduktyZLogo].
* [[Trailer]] - trailer Wesnoth

== Inne ==
* [[UsefulLinks|PrzydatneOdnośniki]]
* [[WesnothLSM]] - prezentacja na LSM
* [http://wesnoth.slack.it/?WesnothPlayerMap MapaGraczy] - dodaj siebie do mapy!
* [http://en.wikipedia.org/wiki/Battle_for_Wesnoth WpisWWikipedii]
* [[WikiHaiku]]

== O tej Wiki ==
* [[Help:Editing|Edycja]] - naucz się edytować strony
* [[Sandbox|Piaskownica]] - poeksperymentuj
* [[WikiMigration|Migracja]] - szukaliśmy zastępstwa dla starego silnika (i znaleźliśmy MediaWiki)

StartingPoints

2008-02-25T21:33:35Z

Blueblaze: /* Reference */ Fixed Wesnoth_Acronyms_and_Slang link

__NOTOC__

What would you like to learn about Wesnoth in this wiki? [[Play]] it, [[create]] with it, [[support]] for it, [[project]] resources about it, [[credits]] of it.

This is a page with starting points to exploring this wiki about The Battle for Wesnoth. In addition to the wiki, there's also a [http://www.wesnoth.org homepage], a [http://www.wesnoth.org/forum forum], and a [http://gna.org/projects/wesnoth/ Gna project page].

* [[Special:Categories|List of all page categories in this wiki]]
* [[Special:Allpages|List of all pages in this wiki]]

== 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, ...
* [[UsingSourceinstall]] - using GNU Source Installer to automate installation and upgrades from source (Unix-likes only)
* [[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
* [[MainlineCampaigns]] - 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
* [[Replays]] - archive of replays new and old
* [[How to play...]] - learn more about various faction vs faction strategies

==== Reference ====
* [[HotKeysSystem]] - keyboard shortcuts
* [[CommandMode]] - commands you can use in-game
* [[ServerAdministration]] - commands that authenticated users can use to administer the server
* [http://zapicm.freeshell.org Units] - Units advancement trees and stats
** [http://zapicm.freeshell.org/dev Development version]
** [http://zapicm.freeshell.org/stable Stable version]
** [http://server.wesnoth.org/~wesnoth/trunk Trunk version]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
** [http://www.wesnoth.org/wiki/Category:Factions] - list all user made factions
* [[Wesnoth_Acronyms_and_Slang|Wesnoth Acronyms and Slang]] - common wesnothian acronyms and slang explained

== Tweaking the Game ([[Create]]) ==
==== Scenarios & Campaigns ====
* [[UserScenarios]] - user-written scenarios, campaigns and game modifications
* [[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
==== References ====
* [[ReferenceWML]] and [[AlphabeticalWML]] - all about Wesnoth Markup Language
* [[ReferencePythonAPI]] - upcoming Python interface for AI
==== Tools & Utilities ====
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[WesnothMapEditor]] - summary of controls
==== Art related ====
* [[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!
* [http://www.wesnoth.org/wiki/ReportingBugs#Guidelines_for_suggesting_features Guidelines for suggesting features] - To submit a feature request, use http://bugs.wesnoth.org
==== 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
* [[DeveloperGuide]] - for those who received SVN commit rights
* [[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
* [[WesnothFormulaAIBranch]] - Guide to the experimental formula AI branch
* [[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
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them
* [[WesnothGL]] - Guide to programming the Wesnoth OpenGL branch

==== Game translations ====
* [[GettextForTranslators]] - how to translate Wesnoth under [[GetText]]
* [[WesnothTranslations]] - completely unknown stats...
* [[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
* [[WesnothFigures]] - notable figures of valorous and infamous deeds in Wesnoth
* [[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]]
* [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]
* [[WikiHaiku]]

== 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)
* [http://www.wesnoth.org/forum/viewtopic.php?t=19462 Obsolete] - help in updating the wiki for v1.4

Wesnoth Acronyms and Slang

2008-02-25T21:14:48Z

Blueblaze: /* See Also */

Use the following list to demystify the various (mostly wesnoth specific) acronyms you may run into at the forum.



== Names of Mainline Campaigns and Scenarios ==

*AoI - "An Orcish Incursion"
*DiD - "Descent into Darkness"
*EI - "The Eastern Invasion"
*HttT - "Heir to the Throne"
** BoP - "Bay of Pearls"
** DD - "Dwarven Doors"
** HotNE - "Home of the North Elves"
** IotD - "Isle of the Damned"
** RtW - "Return to Wesnoth"
** SoE - "Siege of Elensefar"
** SoF - "Scepter of Fire"
** TotC - "Test of the Clans"
** VoD - "Valley of Death"
*NR - "Northern Rebirth"
*SoF - "Sceptre of Fire"
*SotBE - "Son of the Black Eye"
*TB - "A Tale of Two Brothers"
*THoT - "The Hammer of Thurgasan"
*TRoW - "The Rise of Wesnoth"
*TSG - "The South Guard"
*UtBS - "Under the Burning Suns"

== Unofficial Campaigns ==

*FtF - "Flight to Freedom" (campaign name)
*IftU - "Invasion from the Unknown" (campaign name)
*LoW - "Legend of Wesmere" (campaign name)
*SE - "Saving Elensefar" (campaign name)

== Unit Names ==

*bird - usually Gryphon Rider/Master (knaglans), or occasionally a Falcon or Eagle Rider from the [[Extended Era]] Aragwaith and Kalifa factions.
*DA - Dark Adept (undead)
*fish - Merman (loyalists or rebels) or Naga Fighter (northerners)
*gunner - Dwarvish Thunderer/Thunderguard/Dragonguard (knaglans)
*HI - Heavy Infantryman (loyalists)
*MoL - Mage of Light (loyalists or rebels)
*Ulf - Dwarvish Ulfserker (knaglans)
*WC - Walking Corpse (undead)
*zombie - Walking Corpse

== Other, Wesnoth-specific ==

*AMLA - After Maximum Level Advancement
*AoH - Age of Heroes
*BfW - Battle for Wesnoth (the name of the game)
*BWH - Been suggested before. We think it's a good idea. Hope to add it eventually.
*CABD - Can Already Be Done, e.g., you can already create custom unit abilities via WML.
*CtH - Chance to Hit (also C2H)
*CtBH - Chance to Be Hit (also C2BH)
*CtK - Chance to Kill (also C2K)
*CtBK - Chance to Be Killed (also C2BK)
*DA - Dark Adept (a unit from the Undead faction)
*EP - Elvish Pillager, moderator and great man :) at forum
*FoW - Fog of War (i.e. fog)
*FFA - Free For All (playing a map with >2 players without teams)
*FPI - Frequently Posted Idea (read the [http://www.wesnoth.org/forum/viewtopic.php?t=1158|FPI Post] from the Ideas Forum)
*HANE—EtH - Hexes Are Not Evil - Embrace the Hex
*HAPMA - Hexes Are Possibly Miles Across - http://www.wesnoth.org/forum/viewtopic.php?t=1882
*HP - Hit points
*IIRWIIR - It Is Ready When It Is Ready
*KISS - Keep It Simple, Stupid: Applies to coding, not game rules (although indirectly it does): see [[WesnothPhilosophy]]
*MP - Multiplayer or Movement Points
*N3T - No 3-Teams; A belief stating that contests between three equal and opposing forces are inherently unbalanced
*OAB - Options Are Bad; In reference to gameplay, not user interface options. Mostly used by Turin. See also [[FrequentlyProposedIdeas]] (idea #1)
*OFWRA - Old Flame War Revival Alert; In other words, we have discussed this before and have no interest in discussing it again, especially if it got ugly
* OOS - Out Of Synch - an error generated by Wesnoth. OOS errors occur when game data for one player is different/incompatible from the others
*RiPLIB - Reduction in Power when Levelling Is Bad: means that when a unit upgrades, at least one of its options should be strictly superior to the original unit. [http://www.wesnoth.org/forum/viewtopic.php?t=1423 Reference 1] / [http://www.wesnoth.org/forum/viewtopic.php?t=7205 Reference 2]
*RPG - Role Playing Game - [http://www.wesnoth.org/forum/viewtopic.php?t=4385 1)] Wesnoth's experience system. <nowiki>2)</nowiki> An "RPG-style" game on the MP server means the primary focus will be walking your leader-units through a scripted storyline involving map exploration and lots of WML.
*SP - Single Player (Campaigns)
*ToD - Time of Day
*TWP - The Wesnoth Philosophy: [[WesnothPhilosophy]]
*UMC - User Made Campaign or User Made Content (any add-on not packaged with Wesnoth)
*WC - Walking Corpses
*WICOT - WML is capable of this (the requested feature is already possible to script, so no need to hard-code it in C++)
*WINR - Wesnoth Is Not Realistic
*WIN_ - Wesnoth Is Not... (Warcraft, Lord of the Rings, medieval Europe, an RPG, a wargame, a war simulation, etc.)
*WML - Wesnoth Markup Language: [[ReferenceWML]]
*XP - Experience
*ZoC - Zone of Control

== General Acronyms ==

*AFaICT - As Far as I Can Tell (A statement with a disclaimer on truthfulness)
*AFaIK - As Far as I Know (A statement with a disclaimer on truthfulness)
*AfK - Away from the Keyboard
*ASaP - As Soon as Possible
*BRB - Be Right Back
*BtW - By the Way (A statement with a disclaimer on relevance)
*EV - Expected Value
*FYI - For Your Information
*GtG - Got to Go
*IIRC - If I Recall Correctly (A statement with a disclaimer on truthfulness)
*IMHO - In My Humble Opinion (A statement with a disclaimer on objectiveness)
*IMO - In My Opinion
*LTNS - Long Time No See
*OMG - Oh My God
*OT - Off Topic: can refer either to the forum category (http://www.wesnoth.org/forum/viewforum.php?f=11) or to spam
*OtOH - On the Other Hand (A contrast)
*RotFL - Rolling on the Floor Laughing; also RoFL
*RNG - Random Number Generator
*RtFM - Read the F***ing Manual
*RTS - Real Time Strategy Game - as opposed to a turn-based game like Wesnoth
*SVN - Subversion -- the bleeding-edge up-to-the-minute current version of Wesnoth [[WesnothSVN]] ([[What_Is_SVN]])
*TBS - Turn Based Strategy Game, like Wesnoth

[[Category:World of Wesnoth]]

PL:HomePage

2008-02-25T21:14:05Z

Blueblaze: /* Informacje */ Removed unnecessary phrase

__NOTOC__
Ostatnia edycja : 09:52, 16 March 2007 (CET)
{{tpl}}
Bitwa o Wesnoth jest turową grą strategiczną w klimatach fantasy.

Pokonaj wszystkich wrogich przywódców wykorzystując świetnie dobraną grupę jednostek jednocześnie zarządzając złotem i ilością kontrolowanych wiosek. Każda jednostka ma swoje silne i słabe strony, aby wygrac rozmieść swoje wojska jak nakorzystniej jednocześnie uniemożliwiając to przeciwnikowi. Wraz ze wzrostem doświadczenia twoje jednostki zyskują nowe możliwości i stają się silniejsze. Graj we własnym językutestując umiejętności w starciu ze sprytną sztuczną inteligencją lub dołącz do do społeczności graczy sieciowych. Twórz własne jednostki, scenariusze i kampanie dzieląc się nimi z innymi.

Bitwa o Wesnoth jest wydana na licencji [http://www.gnu.org/licenses/licenses.html#GPL GPL]. Gotowe pakiety są dostępne dla większości systemów operacyjnych (Windows, Mac OS X, GNU/Linux), możesz też zbudować własny z kodów źródłowych.

== Zdobywanie Gry ==
==== Pobieranie ====
* [[Download|Pobierz (''en'')]] - pobierz najnowsze kody źródłowe i wiele plików binarnych
** [[WesnothBinaries|WesnothBinarnie (''en'')]] - prekompilowany dla GNU/Linux, BeOS, PDAs, ...
** [[WesnothBinariesLinux|WesnothBinarnieLinux (''en'')]] - prekompilowany dla wielu dystrybucji GNU/Linux

==== Kompilowanie ====
* [[CompilingWesnoth|KompilowanieWesnoth (''en'')]] - dla Unix, Mac, Windows, GNU/Linux, PDAs, ...
* [[DebuggingWesnoth|OdpluskwianieWesnoth (''en'')]] - dla GNU/Linux i systemów Unixopodobnych
* [[WesnothOnLinuxPDAs|WesnothDlaLinuxaNaPDA (''en'')]] - dla serii Qtopia/OPIE i thepdaXrom/Zaurus C

== Granie w Wesnoth ([[PL:Play|Graj (''en'')]]) ==

==== Dla Nowych Graczy ====
* [[GettingStarted|Poczatki (''en'')]] - przeczytaj najpierw!
* [[WesnothManual|PodręcznikWesnoth (''en'')]] - zasady
* [[MainlineCampaigns|ScenariuszePodstawowe (''en'')]] - podpowiedzi do kampani dostarczanych z grą

==== Dla Nie-Tak-Znowu-Nowych Graczy ====
* [[AdvancedTactics|ZaawansowanaTaktyka (''en'')]] - jak pokonać SI i innych ludzi
* [[MultiplayerServers|SerweryMultiplayer]] - gdzie można zagrać z innymi ludźmi w internecie

==== Informacje ====
* [[HotKeysSystem|SkrótyKlawiaturowe (''en'')]] - skróty klawiaturowe
* [[CommandMode|TrybPoleceń (''en'')]] - lista poleceń których można użyć w grze
* [[ServerAdministration|AdministracjaSerwerem (''en'')]] - komendy które upoważnieni użytkownicy mogą wykorzystać do administracji serwerem
* [http://zapicm.freeshell.org Jednostki (''en'')] - drzewo promocji jednostek i statystyki
** [http://zapicm.freeshell.org/dev Wersja rozwojowa (''en'')]
** [http://zapicm.freeshell.org/stable Wesja stabilna (''en'')]
** [http://zapicm.freeshell.org/trunk Najnowsza wersja (''en'')]
* [[RaceDescriptions|OpisyRas (''en'')]] - Elfy, Ludzie, Krasnoludy, Orki, Smoki, Nieumarli, Inne
** [[Complete_Faction_List_%28unfinished%29|(Prawie)KompletnaListaFrakcji (''en'')]] - lista wszystkich (prawie) frakcji stworzonych przez użytkowników
* [[WesnothAcronyms|SkrótyWesnoth (''en'')]] - popularne skróty występujące w grze i społeczności

== Modyfikowanie Gry ([[PL:Create|Stwórz (''en'')]]) ==

* [[UserScenarios|ScenariuszeUżytkowników]] - scenariusze, kampanie i modyfikacje gry stworzone przez społeczność
* [[ReferenceWML|EncyklopediaWML]] i [[AlphabeticalWML|WMLAlfabetycznie]] - wszystko o WML (języku znaczników Wesnoth)
* [[ReferencePythonAPI|EncyklopediaPythonAPI]] - nadchodzący interfejs Pythona do SI
* [[BuildingCampaigns|BudowanieKampanii]] - jak stworzyć własną kampanię dla jednego gracza
* [[MultiplayerCampaigns|KampanieDlaWieluGraczy]] - jak stworzyć kampanię do trybu wieloosobowego
* [[BuildingScenarios|BudowanieScenariusza]] - jak stworzyć własny scenariusz
* [[BuildingUnits|BudowanieJednostek]] - jak stworzyć własne jednostki
* [[UnitAnalysis|AnalizaJednostek]] - narzędzie do analizy jednostek
* [[WesnothMapEditor|EdytorMap]] - opis interfejsu
* [[ExternalUtilities|ProgramyUżytkowe]] - skrypty pomocne przy tworzeniu kampani, scenariuszy i grafik
* [[Create_Art#Art_Tutorials|SamouczkiGraficzne]] - pomoc w tworzeniu grafiki
* [[GraphicLibrary|BibliotekaGrafiki]] - ikony jednostek i terenu zamieszczone na forum
* [[Tiles_Status|StatusTerenu]] - elementy terenu proponowane i będące w trakcie prac

== Poprawianie Gry ==
* [[ReportingBugs|ZgłaszanieBłędów]] - używamy Gna
* prośby o dodanie nowego elementu do gry zamieszczamy na http://bugs.wesnoth.org
* [[FrequentlyProposedIdeas|CzęstoZgłaszanePomysły]] - zanim coś zaproponujesz sprawdź czy nie ma tego tutaj!
==== Informacja Dla Developerów ====
* [[DeveloperResources|ZasobyDlaDeveloperów]] - pożyteczne odnośniki
* [http://changelog.wesnoth.org Changelog|ListaZmian] - najnowsze zmiany w grze
* [[WesnothSVN]] - dostęp do kodu źródłowego
* [[HackingWesnoth|ModyfikowanieWesnoth]] - przewodnik programisty
* [[CodingStandards|StandartKodowania]] - dla programistów
* [[UnitDescriptionRewriting|UaktualnianieOpisówJednostek]] - koordynacja korekt
* [http://wesnoth.slack.it/missing.cgi Missing unit animations and sounds|BrakująceAnimacjeIDźwiękiJednostek] - co jest dostępne i czego brakuje
* [[WritingYourOwnAI|NapiszWłasnąSI]] - jako plugin C++
* [[ThemeSystem|SystemMotywów]] - dostosowywanie rozmieszczenia elementów na ekranie w edytorze i grze
* [[ReleasingWesnoth|PublikowanieWesnoth]] - kroki które należy podjąć, żeby opublikować nową wersję
* [[WesnothPackagersGuide|PrzewodnikDlaTwórcówPaczek]] - wskazówki do przygotowywania Wesnoth dla różnych platform
* [[EasyCoding|ProsteKodowanie]] - błędy oraz elementy łatwe w implementacji dla początkujących koderów
* [[NotSoEasyCoding|NieTakProsteKodowanie]] - Błędy oraz elementy możliwe do wykonania, którym brakuje kogoś kto by nad nimi popracował
* [[WesnothGL]] - przewodnik do programowania Wesnoth w OpenGL

==== Tłumaczenia Gry ====
* [[GettextForTranslators|GettextDlaTłumaczy]] - jak przetłumaczyć Wesnoth w [[GetText]]
* [[WesnothTranslations|Tłumaczenia]] - 11 zakończonych, 2 prawie gotowych, 7 w połowie, 10 częściowych
* [[WesCamp]] - projekt tłumaczenia kampanii stworzonych przez użytkowników.

== O Grze ==
* [[WesnothPhilosophy|Filozofia]] - Dave o Wesnoth
* [[WesnothHistory|Historia]] - wieki Wesnoth
* [[WesnothGeography|Geografia]] - opis Wesnoth i otaczających krain
* [[WesnothReviews|Recenzje]] - niezależne recenzje
* [irc://irc.wesnoth.org/wesnoth #wesnoth] - nasz kanał IRC
* [[Donate|Wesprzyj]] lub [http://cafepress.com/wesnoth KupProduktyZLogo].
* [[Trailer]] - trailer Wesnoth

== Inne ==
* [[UsefulLinks|PrzydatneOdnośniki]]
* [[WesnothLSM]] - prezentacja na LSM
* [http://wesnoth.slack.it/?WesnothPlayerMap MapaGraczy] - dodaj siebie do mapy!
* [http://en.wikipedia.org/wiki/Battle_for_Wesnoth WpisWWikipedii]
* [[WikiHaiku]]

== O tej Wiki ==
* [[Help:Editing|Edycja]] - naucz się edytować strony
* [[Sandbox|Piaskownica]] - poeksperymentuj
* [[WikiMigration|Migracja]] - szukaliśmy zastępstwa dla starego silnika (i znaleźliśmy MediaWiki)

StartingPoints

2008-02-25T21:13:00Z

Blueblaze: /* Reference */ Removed unnecessary phrase

__NOTOC__

What would you like to learn about Wesnoth in this wiki? [[Play]] it, [[create]] with it, [[support]] for it, [[project]] resources about it, [[credits]] of it.

This is a page with starting points to exploring this wiki about The Battle for Wesnoth. In addition to the wiki, there's also a [http://www.wesnoth.org homepage], a [http://www.wesnoth.org/forum forum], and a [http://gna.org/projects/wesnoth/ Gna project page].

* [[Special:Categories|List of all page categories in this wiki]]
* [[Special:Allpages|List of all pages in this wiki]]

== 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, ...
* [[UsingSourceinstall]] - using GNU Source Installer to automate installation and upgrades from source (Unix-likes only)
* [[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
* [[MainlineCampaigns]] - 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
* [[Replays]] - archive of replays new and old
* [[How to play...]] - learn more about various faction vs faction strategies

==== Reference ====
* [[HotKeysSystem]] - keyboard shortcuts
* [[CommandMode]] - commands you can use in-game
* [[ServerAdministration]] - commands that authenticated users can use to administer the server
* [http://zapicm.freeshell.org Units] - Units advancement trees and stats
** [http://zapicm.freeshell.org/dev Development version]
** [http://zapicm.freeshell.org/stable Stable version]
** [http://server.wesnoth.org/~wesnoth/trunk Trunk version]
* [[RaceDescriptions]] - Elves, Humans, Dwarves, Orcs, Drakes, Undead, Others
** [http://www.wesnoth.org/wiki/Category:Factions] - list all user made factions
* [[WesnothAcronyms|Wesnoth Acronyms]] - common wesnothian acronyms explained

== Tweaking the Game ([[Create]]) ==
==== Scenarios & Campaigns ====
* [[UserScenarios]] - user-written scenarios, campaigns and game modifications
* [[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
==== References ====
* [[ReferenceWML]] and [[AlphabeticalWML]] - all about Wesnoth Markup Language
* [[ReferencePythonAPI]] - upcoming Python interface for AI
==== Tools & Utilities ====
* [[ExternalUtilities]] - scripts to help create scenarios, campaigns, and graphics
* [[WesnothMapEditor]] - summary of controls
==== Art related ====
* [[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!
* [http://www.wesnoth.org/wiki/ReportingBugs#Guidelines_for_suggesting_features Guidelines for suggesting features] - To submit a feature request, use http://bugs.wesnoth.org
==== 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
* [[DeveloperGuide]] - for those who received SVN commit rights
* [[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
* [[WesnothFormulaAIBranch]] - Guide to the experimental formula AI branch
* [[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
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them
* [[WesnothGL]] - Guide to programming the Wesnoth OpenGL branch

==== Game translations ====
* [[GettextForTranslators]] - how to translate Wesnoth under [[GetText]]
* [[WesnothTranslations]] - completely unknown stats...
* [[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
* [[WesnothFigures]] - notable figures of valorous and infamous deeds in Wesnoth
* [[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]]
* [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]
* [[WikiHaiku]]

== 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)
* [http://www.wesnoth.org/forum/viewtopic.php?t=19462 Obsolete] - help in updating the wiki for v1.4

Download

2008-02-03T18:59:08Z

Blueblaze: /* MS Windows */ Removed the windows binary link

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. Torrents are also unofficial.

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.2_branch.29|Stable Branch]] | [[Download#Development_.281.3_branch.29|Development Branch]]

== Stable (1.2 branch) ==

We're coming up on a stable 1.4 release, so this branch is no longer in development. There will be no further releases except in the unlikely case of a security emergency.

==== Source code ====
* [http://downloads.sourceforge.net/wesnoth/wesnoth-1.2.8.tar.bz2?download Current stable version] (1.2.8, 69.7 MB)
* [http://downloads.sourceforge.net/wesnoth/wesnoth-1.2.7.tar.bz2?download Previous stable version] (1.2.7, 69.7 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== [[BeOS]] ====
* The current version (1.2.8) is not available yet.
* [http://zeta-games.com/index.php?option=com_remository&Itemid=28&func=fileinfo&id=24 Previous stable version] (1.2.1, 70.11 MB)
* [http://downloads.sourceforge.net/wesnoth/Wesnoth-1.0.2-BeOS-x86.pkg.zip?download Older stable version, not compatible with 1.2] (1.0.2, 42.3 MB)

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

==== OpenBSD ====
'''Note:''' OpenBSD-current is required to play with these binaries:
* [http://downloads.sourceforge.net/wesnoth/wesnoth-openbsd--1.2.8.tgz?download Current stable version ] (1.2.8, 74.9 MiB)
* [ftp://pkg@ftp.enqlave.net/wesnoth-1.2.8.tgz Current stable version (mirror @ Enqlave) ] (1.2.8, 74.9 MiB)
* [http://downloads.sourceforge.net/wesnoth/wesnoth-openbsd--1.2.7.tgz?download Previous stable version ] (1.2.7, 75.0 MiB)
* [ftp://pkg@ftp.enqlave.net/wesnoth-1.2.7.tgz Previous stable version (mirror @ Enqlave) ] (1.2.7, 75.0 MiB)

==== FreeBSD ====
* There is a lot of versions available as FreeBSD package. Look to the [http://www.freebsd.org/cgi/ports.cgi?query=wesnoth&stype=all ports] for the latest version.

==== OS/2 & eComStation ====
* The current version (1.2.8) not available yet.
* [http://download.smedley.info/wesnoth-1.2.5-os2.zip Previous stable version (1.2.5)] (1.2.5, 70 MB)

==== Mac OS X ====
Be aware that OSX 10.3.9+ is required to play with these binaries.
* [http://downloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.2.8d.dmg?download Current stable version] (1.2.8, Universal, 80.7 MB)
* [http://downloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.2.8f_lite.dmg?download Current stable version - lite] (1.2.8, Universal, no art or music, 51.7 MB)
* [http://downloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.2.7.dmg?download Previous stable version] (1.2.7, Universal, 80.8 MB)
* [http://downloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.2.7_lite.dmg?download Previous stable version - lite] (1.2.7, Universal, no art or music, 51.5 MB)

==== MS Windows ====
* [http://downloads.sourceforge.net/wesnoth/wesnoth-1.2.8-windows.exe?download Current version] (1.2.8, 63.0 MB)
* [http://downloads.sourceforge.net/wesnoth/wesnoth-1.2.7-windows.exe?download Previous version] (1.2.7, 63.1 MB)

==== AmigaOS4 ====
* The current version (1.2.8) is not available yet.
* [http://os4depot.net/index.php?function=showfile&file=game/strategy/wesnoth.lha Previous stable version ] (1.2.5, 63 MB)

==== Syllable ====
* The current version (1.2.8) is not available yet.
* [http://www.syllable-software.info/download.php?view.28 Previous stable version] (1.2.6, 60.8 MB)

==== Miscellaneous ====
* [http://downloads.sourceforge.net/wesnoth/wesnoth-1.2.8.tar.bz2.md5?download Source code 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 (1.3 branch) ==

Version 1.3.x 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.2.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://downloads.sourceforge.net/wesnoth/wesnoth-1.3.15.tar.bz2?download Current Version] (1.3.15, 114.6 MB)
* [http://downloads.sourceforge.net/wesnoth/wesnoth-1.3.14.tar.bz2?download Previous Version] (1.3.14, 113.7 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* The current version (1.3.15) is not available yet.
* [http://downloads.sourceforge.net/wesnoth/wesnoth-1.3.14a-windows.exe?download Previous version] (1.3.14a, 106.2 MB)
* [http://www.exong.net/builds/index.php?dir=&sort=date&order=desc Daily SVN snapshots] (only the .exe, in addition you need an SVN checkout to use it; currently there are no updates for those snapshots because the contributer creating the binaries does not have the time to do so anymore)

==== Mac OS X ====
* The current version (1.3.15) is not available yet.
* [http://downloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.3.14.dmg?download Previous Version] (1.3.14, Universal, 126.4 MB)
* [http://downloads.sourceforge.net/wesnoth/Wesnoth_MacOSX_1.3.14_lite.dmg?download Previous Version - lite] (1.3.14, Universal, no art or music, 66.7 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.

==== (Open)Solaris ====
* The current version (1.3.15) is not available yet.
* [http://downloads.sourceforge.net/wesnoth/wesnoth-opensolaris-1.3.12.i386.pkg.bz2?download Older version for x86] (1.3.12, OpenSolaris package for x86, 97.6 MB)

==== AmigaOS4 ====
* The current version (1.3.15) is not available yet.
* [http://os4depot.net/index.php?function=showfile&file=game/strategy/wesnoth-devel.lha Older Version] (1.3.12, 105 MB)

==== OS/2 & eComStation ====
* The current version not available.
* [http://download.smedley.info/wesnoth-1.1.8-os2.zip Older Version] (1.1.8, 66 MB)

==== Syllable ====
* The current version (1.3.15) is not available yet.
* [http://www.syllable-software.info/download.php?view.32 Older Version] (1.3.8, 82.2 MB)

==== Miscellaneous ====
* [http://downloads.sourceforge.net/wesnoth/wesnoth-1.3.15.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

InternalActionsWML

2008-02-01T16:33:40Z

Blueblaze: /* [event] */ Minor edit

{{WML Tags}}
== 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

* '''[have_location]''' {{DevFeature}} a location passing this filter exists
** standard location filter

* '''[and]''' If an [and] is present, all must evaluate to true in order for the [if] to evaluate true. Useful as a bracket for complex conditions, but not strictly necessary.
** condition tags as in [if] - if these evaluate to true, [and] evaluates to true.

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

* '''[not]''' If a [not] is present, none must evaluate to true in order for the [if] to evaluate true.
** condition tags as in [if] - if these evaluate to true, [not] evaluates to false.

* {{DevFeature}} '''[and],[or],[not]''' - the behavior is changing in the development version, where all top-level filters will support in-order conditional handling of and, or, and not. One important thing to remember with the new syntax is, if you have multiple [or]s, you no longer should wrap your first conditional statement into an [or] block.

* '''[variable]''' tests something about the value of a WML variable (see [[VariablesWML]])
** ''name'' the name of the variable to test the value of Only one of the following keys should be used for comparing the value of the variable to another value:
** ''equals'' $name is equal (string wise) to this
** ''not_equals'' $name is not equal to this
** ''greater_than'' $name is numerically greater than this
** ''less_than'' $name is less than this
** ''greater_than_equal_to'' $name is not less than this
** ''less_than_equal_to'' $name is not greater than this
** ''numerical_not_equals'' $name is greater than or less than this
** ''numerical_equals'' $name is not greater than or less than this
** ''boolean_equals'' {{DevFeature}} $name has the same boolean value (e.g. off, false, 0, no)
** ''contains'' {{DevFeature}} $name contains this string

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 only interprets dollars signs if it is the very first character, and then the entire value must be a simple variable name. (in 1.3.2, has the same effect as format. Use literal for no substitution)
** ''literal'' set the variable to the given value (can be numeric or string). This does not interpret any dollars signs. {{DevFeature}}
** ''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 number. To divide, multiply by the inverse eg: 4/2 = 4 * 1/2 = 4 * 0.5. To negate, multiply by -1. The result is an integer.
** ''divide'' {{DevFeature}} divide the variable by the given number. The result is an integer.
** ''modulo'' {{DevFeature}} returns the remainder of an integer division. Both variables need to be an integer, the result is also an integer. eg 5 % 2 = 1.
** ''random'' the variable will be randomly set. You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'. You may provide a range of numbers (integers), e.g. 'random=3..5'. 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''.
** ''rand'' {{DevFeature}} does the same as random, but has better MP support. See [[BuildingMultiplayerExamples]] for more info on the MP case. '''It is highly recommended that you use this feature for randomization.'''
** ''time=stamp'' {{DevFeature}} Retrieves a timestamp in milliseconds since wesnoth was started, can be used as timing aid. Don't try to use this as random value in MP since it will cause an OOS.

* '''[store_unit]''' stores details about units into game variables. 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. 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]

:All keys and tags in the unit definition may be manipulated, including some others. Here is a sample list. If you have a doubt about what keys are valid or what the valid value range is for each key, code a [store_unit] event, save the game, and examine what keys are in the file.
:* advanceto
:* alignment
:* alpha
:* attacks_left
:* canrecruit
:* controller
:* cost
:* description
:* experience
:* facing
:* flying
:* fog
:* gender
:* get_hit_sound
:* gold
:* goto_x
:* goto_y
:* hitpoints
:* id
:* image
:* image_defensive
:* income
:* language_name (same as the name key in the unit config)
:* level
:* max_attacks
:* max_experience
:* max_hitpoints
:* max_moves
:* movement
:* movement_type
:* moves
:* race
:* resting
:* shroud
:* side
:* team_name
:* type
:* unit_description
:* unrenamable
:* usage
:* value
:* x
:* y
:* zoc
:* [advancement]
:* [/advancement]
:* [movement_costs]
:* [/movement_costs]
:* [defense]
:* [/defense]
:* [resistance]
:* [/resistance]
:* [variables]
:* [/variables]
:* [status]
:* [/status]
:* [attack]
:* [/attack]
:* [modifications_description]
:* [/modifications_description]
:* [modifications]
:* [/modifications]

* '''[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', 'y', and 'terrain' (the terrain type for a starting location is always 'K' unless it has been changed)
** ''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' (the position) and 'terrain' (the terrain type).
** 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. '''''[[User:SkeletonCrew#Branch_terrain|(SVN terrain only)]]''''' Here the list will be a comma separated list of terrains.
** ''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_villages]''' {{DevFeature}} Stores a series of locations of villages that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** ''owner_side'' a side number. If present, only villages owned by this side will be choosen. If owner_side=0, store the unowned villages.
** ''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, villages will only be chosen if the letter of the terrain type of that location is listed. '''''[[User:SkeletonCrew#Branch_terrain|(SVN terrain only)]]''''' Here the list will be a comma separated list of terrains.
* '''[store_gold]''' stores the gold for a certain side in a variable. ({{DevFeature}} : this tag is no longer available)
** ''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
* '''[store_side]''' stores information about a certain side in a variable. The variable will contain the member variables 'name', 'team_name', 'gold' and 'income'. ({{DevFeature}} : in SVN trunk, after 1.3.9 release, this tag's resultant variable was extended to contain the members 'fog', 'shroud', 'user_team_name', 'colour', 'controller', 'village_gold' and 'recruit'.)
** ''side'' the side whose information should be stored
** ''variable'' the name of the variable to store the information 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. Tags and variables of stored units can also be cleared, meaning that [trait]s and [object]s, for example, can be removed.
** ''name'' the name of the variable to clear.
* '''[role]''' tries to find a unit to assign a role to. 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]]). 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]]

[[Category: WML Reference]]

InternalActionsWML

2008-02-01T16:32:11Z

Blueblaze: /* [event] */ Strongly emphasize the use of the new random.

{{WML Tags}}
== 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

* '''[have_location]''' {{DevFeature}} a location passing this filter exists
** standard location filter

* '''[and]''' If an [and] is present, all must evaluate to true in order for the [if] to evaluate true. Useful as a bracket for complex conditions, but not strictly necessary.
** condition tags as in [if] - if these evaluate to true, [and] evaluates to true.

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

* '''[not]''' If a [not] is present, none must evaluate to true in order for the [if] to evaluate true.
** condition tags as in [if] - if these evaluate to true, [not] evaluates to false.

* {{DevFeature}} '''[and],[or],[not]''' - the behavior is changing in the development version, where all top-level filters will support in-order conditional handling of and, or, and not. One important thing to remember with the new syntax is, if you have multiple [or]s, you no longer should wrap your first conditional statement into an [or] block.

* '''[variable]''' tests something about the value of a WML variable (see [[VariablesWML]])
** ''name'' the name of the variable to test the value of Only one of the following keys should be used for comparing the value of the variable to another value:
** ''equals'' $name is equal (string wise) to this
** ''not_equals'' $name is not equal to this
** ''greater_than'' $name is numerically greater than this
** ''less_than'' $name is less than this
** ''greater_than_equal_to'' $name is not less than this
** ''less_than_equal_to'' $name is not greater than this
** ''numerical_not_equals'' $name is greater than or less than this
** ''numerical_equals'' $name is not greater than or less than this
** ''boolean_equals'' {{DevFeature}} $name has the same boolean value (e.g. off, false, 0, no)
** ''contains'' {{DevFeature}} $name contains this string

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 only interprets dollars signs if it is the very first character, and then the entire value must be a simple variable name. (in 1.3.2, has the same effect as format. Use literal for no substitution)
** ''literal'' set the variable to the given value (can be numeric or string). This does not interpret any dollars signs. {{DevFeature}}
** ''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 number. To divide, multiply by the inverse eg: 4/2 = 4 * 1/2 = 4 * 0.5. To negate, multiply by -1. The result is an integer.
** ''divide'' {{DevFeature}} divide the variable by the given number. The result is an integer.
** ''modulo'' {{DevFeature}} returns the remainder of an integer division. Both variables need to be an integer, the result is also an integer. eg 5 % 2 = 1.
** ''random'' the variable will be randomly set. You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'. You may provide a range of numbers (integers), e.g. 'random=3..5'. 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''.
** ''rand'' {{DevFeature}} does the same as random, but has better MP support. See [[BuildingMultiplayerExamples]] for more info on the MP case. '''It is highly recommended that you use this for random.'''
** ''time=stamp'' {{DevFeature}} Retrieves a timestamp in milliseconds since wesnoth was started, can be used as timing aid. Don't try to use this as random value in MP since it will cause an OOS.

* '''[store_unit]''' stores details about units into game variables. 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. 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]

:All keys and tags in the unit definition may be manipulated, including some others. Here is a sample list. If you have a doubt about what keys are valid or what the valid value range is for each key, code a [store_unit] event, save the game, and examine what keys are in the file.
:* advanceto
:* alignment
:* alpha
:* attacks_left
:* canrecruit
:* controller
:* cost
:* description
:* experience
:* facing
:* flying
:* fog
:* gender
:* get_hit_sound
:* gold
:* goto_x
:* goto_y
:* hitpoints
:* id
:* image
:* image_defensive
:* income
:* language_name (same as the name key in the unit config)
:* level
:* max_attacks
:* max_experience
:* max_hitpoints
:* max_moves
:* movement
:* movement_type
:* moves
:* race
:* resting
:* shroud
:* side
:* team_name
:* type
:* unit_description
:* unrenamable
:* usage
:* value
:* x
:* y
:* zoc
:* [advancement]
:* [/advancement]
:* [movement_costs]
:* [/movement_costs]
:* [defense]
:* [/defense]
:* [resistance]
:* [/resistance]
:* [variables]
:* [/variables]
:* [status]
:* [/status]
:* [attack]
:* [/attack]
:* [modifications_description]
:* [/modifications_description]
:* [modifications]
:* [/modifications]

* '''[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', 'y', and 'terrain' (the terrain type for a starting location is always 'K' unless it has been changed)
** ''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' (the position) and 'terrain' (the terrain type).
** 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. '''''[[User:SkeletonCrew#Branch_terrain|(SVN terrain only)]]''''' Here the list will be a comma separated list of terrains.
** ''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_villages]''' {{DevFeature}} Stores a series of locations of villages that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** ''owner_side'' a side number. If present, only villages owned by this side will be choosen. If owner_side=0, store the unowned villages.
** ''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, villages will only be chosen if the letter of the terrain type of that location is listed. '''''[[User:SkeletonCrew#Branch_terrain|(SVN terrain only)]]''''' Here the list will be a comma separated list of terrains.
* '''[store_gold]''' stores the gold for a certain side in a variable. ({{DevFeature}} : this tag is no longer available)
** ''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
* '''[store_side]''' stores information about a certain side in a variable. The variable will contain the member variables 'name', 'team_name', 'gold' and 'income'. ({{DevFeature}} : in SVN trunk, after 1.3.9 release, this tag's resultant variable was extended to contain the members 'fog', 'shroud', 'user_team_name', 'colour', 'controller', 'village_gold' and 'recruit'.)
** ''side'' the side whose information should be stored
** ''variable'' the name of the variable to store the information 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. Tags and variables of stored units can also be cleared, meaning that [trait]s and [object]s, for example, can be removed.
** ''name'' the name of the variable to clear.
* '''[role]''' tries to find a unit to assign a role to. 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]]). 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]]

[[Category: WML Reference]]

EffectWML

2008-01-30T04:37:43Z

Blueblaze: /* the [effect] tag */ Updated remove_attacks based on fix for bug #10922, revision 23341

{{WML Tags}}
== the [effect] tag ==

The tag [effect] is used to describe one modification to a unit.
Any number of [effect] tags can be used to describe a complete
modification.
Modifications are permanent changes to a unit;
currently there is no way of removing a modification.

The following keys are always recognized for [effect]:
* ''unit_type'' only apply this effect if the affected unit's type name matches ''unit_type'' (can be a list of types).
* ''times'' {{DevFeature}} describes how much time the effect is applied. The default is to apply the effect once. Other possible value : "per level" which means that the effect is applied level times, where level is the unit level.
* ''apply_to'' describes what the effect actually affects.
[effect] uses different keys depending on the value of ''apply_to''. ''apply_to'' can take the following values:
* "new_attack" will use all other keys and tags as the description of an attack that will be added to the unit. See [attack] in [[UnitWML]].
* ''remove_attacks'' {{DevFeature}} remove the matching attacks. All tags from the attack filter construct will be used to match the attack; see [[FilterWML]]. Do not use a [filter] tag otherwise it will not work properly.
* "attack" find an attack and modify it. All tags from the attack filter construct will be used to match the attack; see [[FilterWML]]. After that, the following keys and tags can be used to modify the attack. Note: do not use a [filter] tag. Just put the keys you want to filter on inside the [effect] tag.
** ''set_name'' change the attack's name (ie identifier). ({{DevFeature}} this doesn't change the weapon's description like in 1.2)
** ''set_description'' {{DevFeature}} change the attack's description (ie displayed name).
** ''set_type'' change the attack type. Values are 'blade', 'pierce', 'impact', 'fire', 'cold', and 'holy'.
** ''set_special'' change the attack's specials. See [[AbilitiesWML]] for a list of possible values. Note that you can only set the normal specials defined in ''data/abilities.cfg'', not custom ones.
** ''[set_specials]'' {{DevFeature}} change the attack's specials. The specials to add are given exactly as in the [specials] tag.
*** ''mode'' if ''append'', adds the given specials to the attack. If ''replace'', replaces the existing specials with the given ones. Default ''replace''.
** ''remove_specials'' {{DevFeature}} remove the listed specials. The value of this key is the coma-separated list of the id of the specials to remove. This key is always evaluated before a [set_specials] tags in the same [effect]
** ''increase_damage'' increases the attack's damage. This can be positive or negative, so you can use it to decrease damage as well. If it ends in a percent(''''%''''), the change in damage will be a percentage ratio of the attack's original damage.
** ''increase_attacks'' increases the number of attack strikes. Like ''increase_damage'', it can be positive or negative, or a percentage.
** ''attack_weight'' change the attack's attack_weight. See [attack] in [[UnitWML]] for explainations about attack_weight.
** ''defense_weight'' change the attack's defense_weight. See [attack] in [[UnitWML]] for explainations about defense_weight.
* "hitpoints" modifies the unit's HP and/or max HP.
** ''increase'' the amount to increase the unit's HP.
** ''heal_full'' if present and not set to "no" the unit will be put back to full HP.
** ''increase_total'' will increase the total HP of the unit. Can be specified either as a negative or a positive value. It can also be specified as a percentage of the current total; i.e. "-50%" will cut max HP in half.
** ''violate_maximum'' it the unit ends up with more than its max HP after these modifications, and this key is present (set to any non-null value, ex. 'yes'), the unit's HP won't be lowered to its max HP.
* "movement" modifies the unit's movement points.
** ''increase'' maximum movement is increased by this amount. It can be positive, negative, or specified as a percentage.
** ''set'' maximum movement is set to a specific value.
* "max_experience" affects the amount of XP the unit needs for the next level.
** ''increase'' how to change the xp; again it can be negative, positive or a percentage.
* "loyal" no keys associated. The affected unit will be loyal i.e have an upkeep of 0.
* "movement_costs" speed through specific terrain is modified
** ''replace'' If set to "true", any new values replace the old ones. Otherwise, new values are added to old values (negative values allowed).
** [set_specials]
** [movement_costs] a subtag that describes the new movement costs just like in [[UnitWML]] for describing a unit type
* "defense" Sets unit chance to be hit in specific terrain (100 - defense value)
** ''replace'' If set to "true", any new values replace the old ones. Otherwise, new values are added to old values (negative values allowed).
** [defense] a subtag that describes the new defense just like in [[UnitWML]] for describing a unit type
* "resistance" Sets percent damage taken from combat
** ''replace'' If set to "true", any new values replace the old ones. Otherwise, new values are added to old values (negative values allowed).
** [resistance] a subtag that describes the new resistance just like in [[UnitWML]] for describing a unit type
* "variation" switches the unit into one of its variations.
** ''name'' the name of the variation to invoke.
* "status" modifies the status affecting the unit.
** ''add'' a list of status modifications to add. Beware, these may be reapplied later, such as when the unit is recalled or levels up; if in an event, you can use [[InternalActionsWML|[store_unit]]] and [[DirectActionsWML|[unstore_unit]]], modifying unit.status.name directly, to avoid this, or if you are creating the unit, you can just add it to the unit's [status] tag in the [unit] tag. These are listed in [status], [[SingleUnitWML]].
** ''remove'' a list of status modifications to remove.
* ''zoc'' {{DevFeature}} toggle the zone of control.
** ''value'' new value for zoc (0=disable, other=enable).
* ''profile'' {{DevFeature}} customize the profile for this unit type
** ''portrait'' new image to display when the unit speaks
** ''description'' sets the text to display when hovering over the unit's type in the righthand pane
* "new_ability" {{DevFeature}} Adds one or more abilities to a unit.
** [abilities] A subtag that contains the ability definitions.
* "remove_ability" {{DevFeature}} Removes one or more abilities from a unit. Abilities are not reference counted: added, added, removed = gone.
** [abilities] A subtag that contains the ability definitions. Strictly speaking, all that is needed is the id= inside some tag.
* ''new_animation'' {{DevFeature}} contain animations that will be added to the unit
* "image_mod" modify the image path function([[ImagePathFunctionWML]]) of all the unit's frames
** ''replace'' the image path function to be used, e.g. "RC(magenta>red)"

== See Also ==

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

[[Category: WML Reference]]

InterfaceActionsWML

2008-01-30T04:00:55Z

Blueblaze: /* [message] */ Changed caption description; now says beside image instead of under image.

{{WML Tags}}
== Interface actions ==

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

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

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

* ''speaker'' an alternative to standard unit filter
** 'narrator' the dialog box is displayed without a caption for the unit speaking or a unit image
** 'unit' the primary unit for the event is speaking
** 'second_unit' the secondary unit for the event is speaking

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

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

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

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

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

Tags of '''[objectives]''':
* '''[objective]''' describes a win or loss condition. Most scenarios have multiple win or loss conditions, so use a separate [objective] subtag for each line; this helps with translations.
** ''description'' text for the specific win or loss condition.
** ''condition'' The color and placement of the text. Values are 'win'(colored green, placed after ''victory_string'') and 'lose'(colored red, placed after ''defeat_string'')

== [set_menu_item] {{DevFeature}} ==
This tag is used to add a custom option in the right-click context menu which can then be used to trigger arbitrary WML commands.

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

== Other interface tags ==

The following tags are also action tags:
* '''[item]''' makes a graphical item appear on a certain hex. Note this only places the graphics for an item. It does not make the item do anything. Use a moveto event to make moving onto the item do something.
** ''x'', ''y'' the location to place the item.
** ''image'' the image (in ''images/ ''as .png) to place on the hex.
** ''halo'' an image to place centered on the hex. Use this instead of ''image'' if the image is bigger than the hex.
* '''[removeitem]''' removes any graphical items on a given hex
** ''x'', ''y'' the hex to remove items off
* '''[print]''' displays a message across the screen. The message will disappear after a certain time.
** ''text'' (translatable) the text to display.
** ''size'' (default=12) the pointsize of the font to use
** ''duration'' (default=50) the length of time to display the text for. This is measured in the number of 'frames'. A frame in Wesnoth is usually displayed for around 30ms.
** ''red'', ''green'', ''blue'' (default=0,0,0) the color to display the text in. Values vary from 0-255.
* '''[move_unit_fake]''' moves an image of a unit along a certain path on the map. The path does not need to be a continuous list of adjacent hexes, so for example only the start and end points can be given, in which case the straightest line between those points will be calculated and used.
** ''type'' the type of the unit whose image to use
** ''x'' a comma-seperated list of x locations to move along
** ''y'' a comma-seperated list of y locations to move along (x and y values are matched pairs)
** ''side'' the side of the fake unit, used for team colouring the fake unit
* '''[hide_unit]''' makes the given unit become invisible. Useful in conjunction with '''[move_unit_fake]''' to move a leader unit into position on-screen. Only one unit may be hidden at a time.
** ''x'', ''y'' location of the unit to be hidden. (NOT a standard unit filter! Just x and y.)
* '''[unhide_unit]''' stops the currently hidden unit from being hidden.
* '''[scroll]''' Scroll a certain number of pixels in a given direction. Useful for earthquake/shaking effects.
** ''x'', ''y'' the number of pixels to scroll along the x and y axis
* '''[scroll_to]''' Scroll to a given hex
** ''x'', ''y'' the hex to scroll to
** ''check_fogged'' whether to scroll even to locations covered in fog or shroud. Possible values ''true'' (don't scroll to fog) and ''false'' (scroll even to fog), with ''false'' as the default.
* '''[scroll_to_unit]''' Scroll to a given unit
** standard unit filter
** ''check_fogged'' whether to scroll even to locations covered in fog or shroud. Possible values ''true'' (don't scroll to fog) and ''false'' (scroll even to fog), with ''false'' as the default.
* '''[sound]''' Plays a sound
** ''name'' the filename of the sound to play (in ''sounds/'' as .wav or .ogg)
** ''repeat'' {{DevFeature}} repeats the sound for a specified additional number of times (default=0)
* '''[sound_source]''' {{DevFeature}} Creates a sound source. "Sound sources" is a general name for a mechanism, which makes possible for map elements to emit sounds according to some rules, where "map elements" can be specific locations or terrain types. For now, only sound sources tied to locations are supported.
** ''id'' a unique identification key of the sound source
** ''sounds'' a list of comma separated, randomly played sounds associated with the sound source
** ''delay'' a numerical value (in milliseconds) of the minimal delay between two playbacks of the source's sound if the source remains visible on the screen; if one scrolls out and back in, the source will be considered as ready to play
** ''chance'' a percentage (a value from 0 to 100) describing the chance of the source being activated every second after the delay has passed or when the source's location appears on the screen (note that it cannot play more than one file at the same time)
** ''check_fogged'' possible values "true" and "false" - if true the source will not play if its locations are fogged/shrouded
** ''x,y'' a standard location filter for the locations associated with the sound source
* '''[remove_sound_source]''' {{DevFeature}} Removes a previously defined sound source.
** ''id'' the identification key of the sound source to remove
* '''[music]''' Switches to playing different music
** ''name'' the filename of the music to play (in ''music/'' as .ogg)
** see [[MusicListWML]] for the correct syntax
* '''[colour_adjust]''' tints the colour of the screen.
** ''red'', ''green'', ''blue'' values from -255 to 255, the amount to tint by for each colour
* '''[delay]''' pauses the game
** ''time'' the time to pause in milliseconds
* '''[redraw]''' redraws the screen (this normally isn't done during events, although some of the other interface actions cause the screen or parts of it to be redrawn).
** ''side'' if used, recalculates fog and shroud for that side. Useful if you for example spawn friendly units in the middle of an event and want the shroud to update accordingly (otherwise units that spawn inside fog would remain invisible for the duration of the event, since the fog would not automatically get cleared around them).
* '''[unit_overlay]''' sets an image that will be drawn over a particular unit, and follow it around
** ''x'', ''y'' the location of the unit to overlay on
** ''image'' the image to place on the unit
* '''[remove_unit_overlay]''' removes a particular overlayed image from a unit
** ''x'', ''y'' the location of the unit to remove an overlay from
** ''image'' the image to remove from the unit
* '''[animate_unit]''' uses the custom animation of a unit to animate it on screen (if the unit has the corresponding animation)
** ''flag'' the key to find the good custom animation in the unit description see the '''[extra_anim]''' description in [[AnimationWML]] Standar anims can be triggered with the following keywors ''leading recruited standing idling levelin levelout healing healed poisoned movement defend attack death victory pre_teleport post_teleport''
** '''[filter]''' a standard unit filter see [[FilterWML]] by default, the unit at the event location will be animated. You can use this tag to choose any other unit to animate
** '''[primary_attack]''' if this tag is not present, the filter for animation will be triggered with no attack. If it is here, all attacks from the unit will be filtered, and a matching one will be used to filter the animation
** '''[secondary_attack]''' same for the second attack
** ''hit'' the hit type to filter unit on
** ''text'' a text to hover during the animation
** ''text_color'' r,g,b value for the text color
** ''with_bars'' whether to display the status bars or not.
* '''[label]''' places a label on the map.
** ''x'', ''y'' the location of the label
** ''text'' what the label should say
** ''team_name'' if specified, the label will only be visible to the given team.
* '''[deprecated_message]''' {{DevFeature}} shows a deprecated message in the message area, this feature is only intended to be used to warn about deprecated macros in mainline. The message is not translatable.
** ''message'' the message to show.
* '''[debug_message]''' {{DevFeature}} outputs a message to Wesnoth's console output. Intended for campaign designers to output silent text to the console, without annoying the player; then, that text might contain information useful for later bug-reporting.
** ''message'' the message to show
** ''logger'' the Wesnoth engine output logger that should catch the text; this might be 'err' (the errors log level), 'warn'/'wrn' (the warnings log level) or anything else (the information log level). Not all information will be displayed depending on the log level chosen when starting Wesnoth.

== See Also ==
* [[DirectActionsWML]]
* [[InternalActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

Contrib:Archenemy

2008-01-06T22:34:16Z

Blueblaze: Removed broken image

== Archenemy ==

User:Blueblaze

2008-01-03T09:27:50Z

Blueblaze: Cleaned up page some, added some more info

Here is a list of all the addons I have completed for Wesnoth. This list will continue to be updated with each new release so feel free to watchlist this page to keep up to date.
 
 
 Released Addons:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x - Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Level One Era]
 1.3.x - Version: 1.0 [Released: January 1, 2008]
 Type: Era
 This era allows you to use the default level one units as your starting heros. This era also adds a monster faction for you to select heros from as well. This era works great for RPGs but also will work well on any map as recruitment has been enabled as well.
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x - Version: 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x - Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x - Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

User:Blueblaze

2008-01-03T09:25:29Z

Blueblaze: Added more stuff

Released Addons:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Level One Era]
 1.3.x Version: 1.0 [Released: January 1, 2008]
 Type: Era
 This era allows you to use the default level one units as your starting heros. This era also adds a monster faction for you to select heros from as well. This era works great for RPGs but also will work well on any map as recruitment has been enabled as well.
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x Version 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

User:Blueblaze

2008-01-03T09:21:52Z

Blueblaze: Added another map

Released Maps:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x Version: 1.0 [Released: January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19209&start=0 Gauntlet Legends]
 1.3.x Version: 1.0 [Released: January 1, 2008]
 Type: RPG
 Players: 5p - Team vs. CPU
 Battle your way through the dungeon to obtain your freedom. Slay the evil who opposes you to become victorious.
 ''No Map Screenshot Yet''
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.3.x Version 2.1 [Last Update: December 24, 2007] [Released: September 20, 2007]
 1.2.x Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - Team vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x Version: 1.0a [Released: September 13, 2007]
 Type: Survival
 Players: 4p - FFA Players vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]

User:Blueblaze

2008-01-03T09:13:53Z

Blueblaze: Adding new maps and updates

Released Maps:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=19230 Wesboard]
 1.3.x Version: 1.0 [Released January 3, 2008]
 Type: Advanced Rumble
 Players: 2p - 1 vs. 1
 Fast, furious, and addicting 1v1 action with changing terrain.
 [http://exong.net/wesnoth-attach/files/wesboard_488.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.2.x Version: 2.0 [Released August 30, 2007]
 1.3.x Version 2.0c [Released September 20, 2007]
 Type: Solo unit survival
 Players: 6p - 6 vs. CPU
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x Version: 1.0a [Released September 13, 2007]
 Type: Survival
 Players: 4p - FFA vs. CPU
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]
 
 
 Other Projects:
 
 Went through every Contrib page in Graphic Library, tagged and removed every broken image. [Completed August 2007]

User:Blueblaze

2007-09-20T16:27:44Z

Blueblaze:

Current Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17505 Advanced RPG]
 Large scale single player RPG for Wesnoth, more information about the project in official thread.
 
 
 Finished Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 1.2.x Version: 1.0a [Released September 13, 2007]
 Type: Survival
 Players: 4p - FFA vs. cpu
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 1.2.x Version: 2.0 [Released August 30, 2007]
 1.3.x Version 2.0c [Released September 20, 2007]
 Type: Solo unit survival
 Players: 6p - 6 vs. cpu
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 Went through every Contrib page in Graphic Library, tagged and removed every broken image. [Completed August 2007]

User:Blueblaze

2007-09-20T16:26:48Z

Blueblaze: Realigned some stuff

Current Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17505 Advanced RPG]
 Large scale single player RPG for Wesnoth, more information about the project in official thread.
 
 
 Finished Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 Version: 1.0a [Released September 13, 2007]
 Type: Survival
 Players: 4p - FFA vs. cpu
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 Version: 2.0 - 1.2.x [Released August 30, 2007]
 Version 2.0c - 1.3.x [Released September 20, 2007]
 Type: Solo unit survival
 Players: 6p - 6 vs. cpu
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 Went through every Contrib page in Graphic Library, tagged and removed every broken image. [Completed August 2007]

User:Blueblaze

2007-09-20T16:25:57Z

Blueblaze: Released version 2.0c for Battle Dome (1.3.x)

Current Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17505 Advanced RPG]
 Large scale single player RPG for Wesnoth, more information about the project in official thread.
 
 
 Finished Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 Version: 1.0a [Released September 13, 2007]
 Type: Survival
 Players: 4p - FFA vs. cpu
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 Version: 2.0 [1.2.x Released August 30, 2007] | Version 2.0c 1.3.x [Released September 20, 2007]
 Type: Solo unit survival
 Players: 6p - 6 vs. cpu
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 Went through every Contrib page in Graphic Library, tagged and removed every broken image. [Completed August 2007]

User:Blueblaze

2007-09-18T15:29:05Z

Blueblaze:

Current Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17505 Advanced RPG]
 Large scale single player RPG for Wesnoth, more information about the project in official thread.
 
 
 Finished Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 Version: 1.0a [Released September 13, 2007]
 Type: Survival
 Players: 4p - FFA vs. cpu
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 Version: 2.0 [1.2.x Released August 30, 2007 | 1.3.x Released September 18, 2007]
 Type: Solo unit survival
 Players: 6p - 6 vs. cpu
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 Went through every Contrib page in Graphic Library, tagged and removed every broken image. [Completed August 2007]

User:Blueblaze

2007-09-18T15:28:35Z

Blueblaze: Released Battle Dome to 1.3.x

Current Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17505 Advanced RPG]
 Large scale single player RPG for Wesnoth, more information about the project in official thread.
 
 
 Finished Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 Version: 1.0a [Released September 13, 2007]
 Type: Survival
 Players: 4p - FFA vs. cpu
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 Version: 2.0 [Released August 30, 2007 | 1.3.x Released September 18, 2007]
 Type: Solo unit survival
 Players: 6p - 6 vs. cpu
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 Went through every Contrib page in Graphic Library, tagged and removed every broken image. [Completed August 2007]

User:Blueblaze

2007-09-14T00:59:08Z

Blueblaze: Fixed link

Current Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17505 Advanced RPG]
 Large scale single player RPG for Wesnoth, more information about the project in official thread.
 
 
 Finished Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?p=251751 Survival Fusion]
 Version: 1.0a [Released September 13, 2007]
 Type: Survival
 Players: 4p - FFA vs. cpu
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - 6 vs. cpu
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 Went through every Contrib page in Graphic Library, tagged and removed every broken image. [Completed August 2007]

User:Blueblaze

2007-09-14T00:58:16Z

Blueblaze: Added Survival Fusion to the list.

Current Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17505 Advanced RPG]
 Large scale single player RPG for Wesnoth, more information about the project in official thread.
 
 
 Finished Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=251751 Survival Fusion]
 Version: 1.0a [Released September 13, 2007]
 Type: Survival
 Players: 4p - FFA vs. cpu
 Survive the incoming waves of enemies while fending off your opponents.
 [http://exong.net/wesnoth-attach/files/survivalfusion_161.png Map Screen Shot]
 
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 Version: 2.0 [Released August 30, 2007]
 Type: Solo unit survival
 Players: 6p - 6 vs. cpu
 Survive the incoming waves of enemies, teamwork is the key to success.
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]
 
 
 Went through every Contrib page in Graphic Library, tagged and removed every broken image. [Completed August 2007]

Talk:The Observer

2007-09-09T03:15:48Z

Blueblaze:

This is The Observer's discussions page. Feel free to post here, or in the [http://www.wesnoth.org/forum/viewtopic.php?t=17626= forum topic].

Funny how the Published Daily turned into Published Weekly :p, Also you shouldn't steal Wikipedia's headline page for Wesnoth (mainly because it really doesn't apply and fit very well). --[[User:Blueblaze|Blueblaze]] 05:13, 9 September 2007 (CEST)

Talk:The Observer

2007-09-09T03:13:51Z

Blueblaze:

User:Blueblaze

2007-09-03T16:46:08Z

Blueblaze:

User:Blueblaze

2007-09-03T16:42:37Z

Blueblaze:

User:Blueblaze

2007-09-03T16:41:05Z

Blueblaze:

Current Projects:
 
 
 Finished Projects:
 
 [http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
 Version: 2.0
 Type: Solo unit survival
 Players: 6p - 6 vs. cpu
 
 Survive the incoming waves of enemies, teamwork is the key to success.
 
 [http://exong.net/wesnoth-attach/files/mappic_128.png Map Screen Shot]

User:Blueblaze

2007-09-03T16:39:56Z

Blueblaze:

User:Blueblaze

2007-09-03T16:37:29Z

Blueblaze:

Current Projects:

Finished Projects:

[http://www.wesnoth.org/forum/viewtopic.php?t=17669 Battle Dome]
Version: 2.0
Type: Solo unit survival
Players: 6p - 6 vs. cpu

[[Image:http://exong.net/wesnoth-attach/files/mappic_128.png]]

BuildingCampaignsTheCampaignFile

2007-08-13T21:53:23Z

Blueblaze: /* Next: */ Cleaned up the bottom of the page, some bad code was put in.

Each campaign must contain a WML file which contains a [campaign] tag. In order for the campaign to be translatable, it must also contain a [textdomain] tag, which should precede the [campaign] tag.

This file contains the information the game needs to find the rest of the bits of your campaign scattered in other files and put them together to have a playable campaign. Much information about this file can be found in the [[CampaignWML]] entry. What follows is a description of each line of the campaign file and an explanation of what it does.

For our purposes I'll assume we've already created a campaign called simple_campaign with the directory structure outlined in [[BuildingCampaignsDirectoryStructure]].

The first line of the campaign file is the [textdomain] WML tag, which specifies where the game should look for translations to the strings in the campaign. The textdomain tag specifies a name for the textdomain, which is what is used in the [campaign] tag, and in f ex campaign scenarios to connect the strings with translations. The textdomain should be unique, and start with 'wesnoth-', to ensure that it does not conflict with other textdomains that might be specified on a given system.
The textdomain also specifies a path to the directory where the compiled translation files will be stored. This should be a file inside the campaign directory.

Ex.
[textdomain]
name="wesnoth-Simple_Campaign"
path="data/campaigns/simple_campaign/translations"
[/textdomain]

Then follows the [campaign] WML tag that lets the game know this is a campaign:

[campaign]

First associate the campaign with the textdomain you have just defined:
#textdomain wesnoth-Simple_Campaign

The next group of lines uniquely identifies the campaign:

name= _ "A Simple Campaign"
define=CAMPAIGN_SIMPLE_CAMPAIGN

[In earlier version, there was also ''id'' which was a unique identifier used for translation, but now has no effect.]

''name'' is the name of your campaign that the user will see. It must be in quotation marks and be preceded by an underscore to facilitate translation. ''define'' creates a key that lets the game know when a user has selected to play a scenario from your campaign. More on it in a bit. If you are missing any of these your campaign will not work correctly.

The next group gives the user information about your campaign when he selects it from the campaign menu:

icon=a_wesnoth_icon.png
image= simple_campaign_logo.png
description= _ "Some text about my campaign!"

''icon'' is a reference to any of the standard Wesnoth images. It will be displayed in the campaign selection menu. When appropriate, it should use [[ImagePathFunctionWML]] to give the icon a team color instead of magenta. ''image'' is an image that will be displayed when a user clicks on the campaign. ''description'' is a text description that will be shown to the user at the same time as ''image''. Note that none of these three are strictly necessary, but they do make your campaign look nice and professional.

difficulties=EASY,NORMAL,HARD
difficulty_descriptions={MENU_IMG_TXT2 *&units/human-loyalists/peasant.png~TC(1,magenta) _"Civilian" _"(trivial)"} +
";" + {MENU_IMG_TXT2 units/human-loyalists/spearman.png~TC(1,magenta) _"Soldier" _"(simple)"} +
";" + {MENU_IMG_TXT2 units/human-loyalists/pikeman.png~TC(1,magenta) _"Veteran" _"(easy)"}

''difficulties'' creates three definitions for three different difficulty levels. For more information on difficulty levels and balancing see [[BuildingCampaignsBalancing]].

first_scenario=the_first_scenario

''first_scenario'' is a reference to the scenario ''id'' of the scenario that you intend to be loaded and played first.
This line is essential. Note that while　you are debugging and testing your campaign, it's often useful to change this line to the scenario you're working on so　you don't have to play through all
the scenarios that come before it. (You could also just play through your campaign saving at each level.)

[/campaign]

That's all that needs to be in the [campaign] tag, so we can close it here.

There's more we want to do, though: we've　got to tell Wesnoth where our various
additional files are located (i.e. our maps, scenarios, units, images, and sounds).

You should put everything not in the [campaign] tag inside
#ifdef CAMPAIGN_SIMPLE_CAMPAIGN
...
#endif
so that your custom macros, WML code, and inclusion of files do not affect other campaigns and slow the game down. The only exception to this is the [binary_path] tag specifying the path to custom images in your campaign, but you should only put this outside the #ifdef if you need custom images for the campaign selection menu and the difficulty selection menu. Otherwise even this belongs inside the #ifdef.

A fairly minimal #ifdef section might just contain a link to your scenarios.

#ifdef CAMPAIGN_SIMPLE_CAMPAIGN

{@campaigns/simple_campaign/scenarios}

#endif

The {@campaigns/simple_campaign/scenarios} line just looks in your campaign's "scenarios" directory and parses any .cfg files it finds there (see [[BuildingScenarios]] for information on making your scenario files). If you have any other .cfg files (macros, custom terrains, etc.), you can link them in a similar way. If you want to use custom units however, you will have to link them from inside a [+units] tag (using the "+" adds them to wesnoth's stored units - this is important) like so:

[+units]
{@campaigns/simple_campaign/units}
[/units]

== Next: ==
* [[BuildingCampaignsThePBLFile]]

== See Also ==

* [[BuildingCampaignsDirectoryStructure]]
* [[BuildingCampaigns]]

BuildingCampaignsTheCampaignFile

2007-08-13T21:51:37Z

Blueblaze: Changed ?TC() in one of the examples to ~TC()

Each campaign must contain a WML file which contains a [campaign] tag. In order for the campaign to be translatable, it must also contain a [textdomain] tag, which should precede the [campaign] tag.

This file contains the information the game needs to find the rest of the bits of your campaign scattered in other files and put them together to have a playable campaign. Much information about this file can be found in the [[CampaignWML]] entry. What follows is a description of each line of the campaign file and an explanation of what it does.

For our purposes I'll assume we've already created a campaign called simple_campaign with the directory structure outlined in [[BuildingCampaignsDirectoryStructure]].

The first line of the campaign file is the [textdomain] WML tag, which specifies where the game should look for translations to the strings in the campaign. The textdomain tag specifies a name for the textdomain, which is what is used in the [campaign] tag, and in f ex campaign scenarios to connect the strings with translations. The textdomain should be unique, and start with 'wesnoth-', to ensure that it does not conflict with other textdomains that might be specified on a given system.
The textdomain also specifies a path to the directory where the compiled translation files will be stored. This should be a file inside the campaign directory.

Ex.
[textdomain]
name="wesnoth-Simple_Campaign"
path="data/campaigns/simple_campaign/translations"
[/textdomain]

Then follows the [campaign] WML tag that lets the game know this is a campaign:

[campaign]

First associate the campaign with the textdomain you have just defined:
#textdomain wesnoth-Simple_Campaign

The next group of lines uniquely identifies the campaign:

name= _ "A Simple Campaign"
define=CAMPAIGN_SIMPLE_CAMPAIGN

[In earlier version, there was also ''id'' which was a unique identifier used for translation, but now has no effect.]

''name'' is the name of your campaign that the user will see. It must be in quotation marks and be preceded by an underscore to facilitate translation. ''define'' creates a key that lets the game know when a user has selected to play a scenario from your campaign. More on it in a bit. If you are missing any of these your campaign will not work correctly.

The next group gives the user information about your campaign when he selects it from the campaign menu:

icon=a_wesnoth_icon.png
image= simple_campaign_logo.png
description= _ "Some text about my campaign!"

''icon'' is a reference to any of the standard Wesnoth images. It will be displayed in the campaign selection menu. When appropriate, it should use [[ImagePathFunctionWML]] to give the icon a team color instead of magenta. ''image'' is an image that will be displayed when a user clicks on the campaign. ''description'' is a text description that will be shown to the user at the same time as ''image''. Note that none of these three are strictly necessary, but they do make your campaign look nice and professional.

difficulties=EASY,NORMAL,HARD
difficulty_descriptions={MENU_IMG_TXT2 *&units/human-loyalists/peasant.png~TC(1,magenta) _"Civilian" _"(trivial)"} +
";" + {MENU_IMG_TXT2 units/human-loyalists/spearman.png~TC(1,magenta) _"Soldier" _"(simple)"} +
";" + {MENU_IMG_TXT2 units/human-loyalists/pikeman.png~TC(1,magenta) _"Veteran" _"(easy)"}

''difficulties'' creates three definitions for three different difficulty levels. For more information on difficulty levels and balancing see [[BuildingCampaignsBalancing]].

first_scenario=the_first_scenario

''first_scenario'' is a reference to the scenario ''id'' of the scenario that you intend to be loaded and played first.
This line is essential. Note that while　you are debugging and testing your campaign, it's often useful to change this line to the scenario you're working on so　you don't have to play through all
the scenarios that come before it. (You could also just play through your campaign saving at each level.)

[/campaign]

That's all that needs to be in the [campaign] tag, so we can close it here.

There's more we want to do, though: we've　got to tell Wesnoth where our various
additional files are located (i.e. our maps, scenarios, units, images, and sounds).

You should put everything not in the [campaign] tag inside
#ifdef CAMPAIGN_SIMPLE_CAMPAIGN
...
#endif
so that your custom macros, WML code, and inclusion of files do not affect other campaigns and slow the game down. The only exception to this is the [binary_path] tag specifying the path to custom images in your campaign, but you should only put this outside the #ifdef if you need custom images for the campaign selection menu and the difficulty selection menu. Otherwise even this belongs inside the #ifdef.

A fairly minimal #ifdef section might just contain a link to your scenarios.

#ifdef CAMPAIGN_SIMPLE_CAMPAIGN

{@campaigns/simple_campaign/scenarios}

#endif

The {@campaigns/simple_campaign/scenarios} line just looks in your campaign's "scenarios" directory and parses any .cfg files it finds there (see [[BuildingScenarios]] for information on making your scenario files). If you have any other .cfg files (macros, custom terrains, etc.), you can link them in a similar way. If you want to use custom units however, you will have to link them from inside a [+units] tag (using the "+" adds them to wesnoth's stored units - this is important) like so:

[+units]
{@campaigns/simple_campaign/units}
[/units]

== Next: ==
* [[BuildingCampaignsThePBLFile]]

[http://www.example.com link title]
----
--[[User:Dfrf|Dfrf]] 17:16, 15 December 2006 (CET)== See Also ==

* [[BuildingCampaignsDirectoryStructure]]
* [[BuildingCampaigns]]
yyy''Italic text'''''Bold text'''[[Link title]]

User:Blueblaze

2007-07-23T14:31:27Z

Blueblaze:

Currently working on Expansion RPG Era for Wesnoth 1.2.x (tenative name)

Currently tagging pages in GraphicLibrary which have broken images. Planning to remove the images in 2 weeks if they are not online again.

User:Blueblaze

2007-07-22T22:51:37Z

Blueblaze:

Currently working on Expansion RPG Era for Wesnoth 1.2.x (tenative name)