The Battle for Wesnoth Wiki - User contributions [en]

AnOrcishIncursion

2011-04-14T00:28:29Z

Mountain King: /* A Detour Through the Swamp */

If you feel comfortable with turn-based games, especially ones featuring units moving on a hex map, then you can play the Tutorial and then dive right into "Medium" to get a feel for the elements of the game. After you have played a few scenarios and are ready to hone your skills, try reading [[AdvancedTactics]]. You should also be familiar with the basics in [[WesnothManual]] -- this is a walkthrough, not an exposition of basic game mechanics.

Each scenario has an individual forum thread where you can provide feedback to the authors. You can find these [http://www.wesnoth.org/forum/viewtopic.php?f=22&t=20249 here].

=== Defend the Forest ===
* Objectives: Defeat Urugha, the enemy leader
* Lose if: Erlornas dies or turns run out
* Turns: 24
* Starting units: Erlornas and an Elvish Rider

This is a simple 'Kill the enemy leader' scenario. The main objective in the first couple scenarios in this campaign is to develop your shaman line recruits, so you should recruit a fairly even mix of fighters, archers, and shamans. Normally as Rebels you would recruit many more fighters, but in this campaign you can be assured of lots of forest, so you don't need quite as many of them. As always, plan your starting recruits so that you can get the most villages quickly (many require a quick archer to reach expediently, unfortunately).

The battle is quickly over. Watch for the enemy Grunts as they have the highest damage dealing potential, and some Wolf Riders may try to steal your village. Try to milk the enemy leader for XP at the end, especially on your Shamans. If he's slowed, he's not much of a threat, even at night. Finish early for a nice bonus.

=== Assassins ===
* Objectives: Defeat Ghalrsa, the enemy leader
* Lose if: Erlornas dies or turns run out
* Turns: 24
* Starting units: Erlornas and another unit
Hopefully you're entering this scenario with a good hunk of XP on your units, if not level 2s already. Your primary goal is to get a Druid quickly in this scenario - the AI uses Orcish Assassins, which will poison you. A Druid will make this far less painful than if you were relying solely on your Shamans.

It is up to you where to make your stand, but try to get the enemy to fight from the river. Even if you lose a unit or two, the return damage he will deal hitting them in the river is quite tremendous and will greatly weaken their forces. Especially on the higher levels of difficulty, consider recruiting quite a bit more than one castleful for this scenario as the enemy will have units aplenty. This enemy leader isn't quite so easy to milk so finish it as quickly as possible.

=== Wasteland ===

* Objectives: Defeat Gnargha, the Orcish Warlord
* Lose if: Erlornas dies or turns run out
* Turns: 24
* Starting units: Erlornas and another unit

This is an interesting scenario - no villages. Check your income in the top: it's all you're going to get. The next scenario is possible with minimum starting gold but painful, especially if you don't have leveled troops that you're willing to lose. This is slightly offset by the gold bonus you will (hopefully) get at the end of the scenario. This scenario is as much an exercise in gold management as anything else. Keep in mind that some troops may level and try to stay under your income as much as possible with your upkeep. Multiple level 1s may be better than your leveled units in some cases. A Druid, of course, is a necessity with the lack of villages.

Establish your units in the middle "island" of forest. With some healers behind your line you should easily absorb the wave of attackers then take out the leader.

When you finish, you will get a small gold bonus that was laying around the orcish camp.

=== Valley of Trolls ===
* Objectives: Defeat the two Troll leaders
* Lose if: Erlornas dies or turns run out
* Turns: 24
* Starting units: Erlornas and another unit

Largely regarded as the first truly difficult scenario by many beginners, this has stumped many by either waves of Troll Whelps or truly scary adult Trolls, depending on your difficulty. What may not be obvious to you is that the troll AI has been set up to NOT USE the two mountain hexes that border their caves, but only the path through the middle. Once you realize this it is far easier to setup a nice bottleneck for them.

The troops from the shaman line should make good use of their slow attack. A slowed troll is much more survivable.

Good luck! Try to eliminate the blue troll quickly so that the teal one will be a sole target.

[stupidjaguar] I agree with all of the above. The scenario becomes much easier if you use the Sorceress line and Elornas, because of the Trolls' vulnerabilities to arcane damage. Slow them with Shamen and Druids, then take them out with faerie fire.

[cph] Maybe the bottleneck approach above works for the Easy skill, but I don't think it's suitable for Challenging. Instead, it's a divide-and-conquer level. Send a scout west over the river to grab villages and distract the west trolls, and throw the rest of your forces in a quick knock-out against the east trolls. Remember to recall some L2 or near-to-levelling up units with good ranged damage: you want to be able to take out trolls in 1 or two turns. It would help to level up Erlornas before you get here, as he does more ranged damage at L3.

=== Linaera the Quick ===
* Objectives: Defeat the enemy leaders
* Lose if: Erlornas or Linaera die or turns run out
* Turns: 24
* Starting units: Erlornas, another unit, Linaera and three Mages

This is a fun scenario lending you a very handy unit, the Silver Mage. Be careful not to lose her and use her as a surprise attacker. The AI does not understand that a Silver Mage can appear from any of your villages, so when she's not teleporting around the map grabbing more villages for you keep her on a village so that she's handy to aid in a strike on an unsuspecting AI unit.

You may start off with low gold after last scenario, so start off slow, especially on higher difficulty levels. Let them come to you instead of you rushing them. You have plenty of time to take the rest of the map once the first wave has pummeled you.

[comments by elvish_sovereign] If your low on gold (which you might be because of the previous scenario), try this strategy if you need some quick cash. Depending on the amount of gold you have, get one or two scouts. Recruit fighters with the rest of your gold. Place Linaera on one of the villages you start with. The orc leader will start recruiting and sending units down to attack you. Use your fighters to lure the enemy units first south and then west. When all of the enemy units are attacking your fighters, use your scout(s) to rush up north and aim to grab the village at 9,5: the village right above the enemy leader. Once your scout leaves that village teleport Linaera to the village and kill the leader. Try not to let the scout(s) die because they also can shoot the leader with their bow(s). This way I finished the scenario (on hard) on turn 6, giving me loads of gold for the next scenario.

=== A Detour Through the Swamp ===

* Objectives: Defeat Keremal the Lich
* Lose if: Erlornas or Linaera die or turns run out
* Turns: 24
* Starting units: Erlornas, Linaera and any surviving Mages

Pretty simple 'kill the enemy leader' scenario again. This campaign has a lot of them. Be careful of the undead at night - they pack a serious punch, but they're much less scary in the daytime. Your best unit will be your Mages. The final boss is a toughy. The only thing you really have that can hurt him is your Mages, with Linaera being by far the best as a Silver Mage (she resists the Lich attack quite a bit!). Get in a gang around him and then try to finish him off in one turn. If that fails, try again. You'll probably have heavy casualties finishing him if you're new to fighting Liches, and beware using melee attacks on him (he'll heal when he hits you), even if his ranged attack is truly terrifyingly powerful. Again, slowing the Lich will help a lot.

[comments by scorchgeek]
Erlornas and Elvish Sorceresses also do heavy damage to undead. I sacrificed all my mages in the previous scenario and at first thought I would have to go back and repeat it, but as I had 2 Sorceresses, I did fine in the end.

[comments by Mountain_King]
If you decide to do a shamans-only challenge on this campaign, this scenario is loads easier. Sorceresses + Shamans make quick work of even revenants. Don't be afraid to bring Erlornas to use his faerie fire either. You should have an enchantress or two at this point, which when combined with Linaera will take out the lich very easily.

=== Showdown ===
* Objectives: Defeat the Orcish Sovereign
* Lose if: Erlornas dies or turns run out
* Turns: 24
* Starting units: Erlornas, Linaera, another unit and 4 Elvish Rangers

Another kill the enemy leader, but with a twist: you get 4 loyal Rangers to sneak around the backside for an assassination! If you have any rangers of your own, send them along to and use the rest of your forces as a diversion to the southwest. If played well you can actually just destroy his army at the moment, but it's always fun to pop out of the trees and surround the bewildered AI.

[[Category: Campaigns - Walkthroughs]]
[[Category:Campaigns - An Orcish Incursion]]

WesnothTranslations

2011-04-12T18:03:35Z

Mountain King: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: CloudiDust - [mailto:cloudidustATgmailDOTcom], we have a Chinese forum here [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: 楊綮銘 (Taiwan) - [mailto:steven2880ATgmailDOTcom]
* [[CroatianTranslation|Croatian]] - maintainer: (needs a maintainer)
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Alexander van Gessel (AI/AI0867) - [mailto:AI0867_AT_gmail.com]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: Steven Panek (Espreon) - [mailto:Majora700ATgmailDOTcom]
* [[EnglishShawTranslation|English (Shaw)]] - maintainer: Arc Riley - [mailto:ArcRileyATubuntu.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Manuel Ortega - [mailto:manuelATelarteDOTcoop]
* [[EstonianTranslation|Estonian]] - maintainer: Kaido Kikkas (UncleOwl) - [mailto:kaidoDOTkikkasATkakupesaDOTnet]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:samu.voutilainenATgmailDOTcom]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] - translation team mailing list [mailto:wesnothATmlDOTfreeDOTfr]
* [[FriulianTranslation|Friulian]] - maintainer: Michele Calligaris (MayBug) - [mailto:michele.calligaris-CAIUT-gmail.com]
* [[GalicianTranslation|Galician]] - maintainer: Adrián Chaves Fernández (Gallaecio) - [mailto:adriyetichavesATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:konsnoslATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Udvari Gábor [mailto:gaborDOTudvariATgmailDOTcom]
* [[IcelandicTranslation|Icelandic]] - maintainer: Gabríel A. Pétursson [mailto:gabrielpATsimnetDOTis]
* [[IndonesianTranslation|Indonesian]] - maintainer: Yuristyawan Pambudi Wicaksana [mailto:yuris_wicaksana@yahoo.com]
* [[IrishTranslation|Irish]] - maintainer: Carson "Mountain_King" [mailto:tree_ringsATrocketmailDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: IWAI, Masaharu (iwaim) - [mailto:iwaim.subATgmailDOTcom], Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: mistzone - [mailto:drier22ATgmailDOTcom]
* [[LatinTranslation|Latin]] - maintainer: Michael Babich ([[User:Aethaeryn|Aethaeryn]])
* [[LatvianTranslation|Latvian]] - maintainer: Reinis Danne - [mailto:rei4danATgmailDOTcom]
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MarathiTranslation|Marathi]] - maintainer: Sujit R Jadhav - [mailto:sujitrjadhavATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov (Mythological)
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[OldEnglishTranslation|Old English]] - maintainer: Steven Panek (Espreon) - [mailto:Majora700ATgmailDOTcom]
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Diego Inácio Goergen - [mailto:thegoergenATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RomanianTranslation|Romanian]] - maintainer: Alexandru Szasz [mailto:alexxedATgmailDOTcom]
* [[RussianTranslation|Russian]] - maintainer: Victor Sergienko [mailto:singalenATgmailDOTcom]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[SlovakTranslation#Preklad|Slovak]] - maintainer: Aceman
* [[SlovenianTranslation|Slovenian]] - maintainer: Klemen Košir (nNa) - [mailto:klemen.nnaATgmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: (needs a maintainer; contact Espreon, who is '''not''' the maintainer, for more information: [mailto:Majora700ATgmailDOTcom])
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[UkrainianTranslation|Ukrainian]] - maintainer: Sergiy Tkach (Apromix)
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Huynh Yen Loc (hhyloc) - [mailto:nightgaunt13ATgmailDOTcom]

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

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[ImageLocalization]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]
* [[CharactersStorys| Character descriptions for Translators (Spoiler Warning)]]
* [[TextdomainStatus]]

[[Category:Translations|*]]

SpellingMistakes

2011-04-03T16:40:36Z

Mountain King: /* Other (unit descriptions, ...) */

This page is meant to be a list of spelling mistakes in campaigns and other translatable texts in the en_US development version of the game.

Note: The house style of Wesnoth uses a good many words and constructions that are archaic, poetic, or dialectal. If you speak modern English as a second language you may incorrectly read these as errors. Please see [[NotSpellingMistakes]] for a list of things you will encounter that may look like spelling or usage errors but are not. Note that the mainline campaigns are now using correct typography, including sexed quotes and en and em dashes. These will appear as three byte sequences if you are not using a viewer that supports UTF-8.

==Mainline Campaigns==

===An Orcish Incursion===

===Dead Water===

===Delfador's Memoirs===
S13: "This was ill tidings for men and Elves alike."
This was -> These were

===Descent into Darkness===

===Eastern Invasion===
S1: "In the days of the king Garard I..."
king Garard I -> King Garard I

===Heir to the Throne===

===Liberty===

===Northern Rebirth===
S05a: "The hole wasn’t big enough for me to go through but one you little guys you might fit."
one you little guys you might fit -> one of you little guys might fit
S07a: "That’s why we have come here, to seek yours and your brothers help in defeating the orcs."
yours and your brothers -> your and your brother's
S09a: "Pff, foolish human. What in the world gave you that idea."
idea. -> idea?

===Sceptre of Fire===
S5: "Och, its some o’ them cave-dwarves."
its -> it’s

* scenario 4 (line 157) ''That makes sense, I guess you '''would''' to plan the sceptre’s design... what in particular do you want him to do?''

That makes sense, I guess you would want to plan the sceptre’s design... What in particular do you want him to do?

===Son of the Black Eye===

===The Hammer of Thursagan===

===The Legend of Wesmere===
S3: "How can they dare to brake the treaty!" brake -> break

===The Rise of Wesnoth===

===The South Guard===

===Two Brothers===

===Under the Burning Suns===

==Wesnoth Game==

===Editor===

===Help===
* somewhere in the help textdomain
''Original text:'' (..) Far to the west in the <del>the </del>Great Ocean is a huge archipelago called (..)
''Proposed replacement:'' (..) Far to the west in the Great Ocean <ins>there </ins>is a huge archipelago called (..)

===Tutorial===

===Manual===

===Manpages===

===Units===

===1.10 Announcement===

===Other (unit descriptions, ...)===

* Mechanical units generally have mechan'''o'''cal as their only trait. Since mechanical units don’t really have life, drain, poison and plague has no effect upon them.
mechanocal -> mechanical *fixed in development version

* The lieutenant's description says "Trained at swords and crossbows..." which is rather poor grammar. Might "Trained in swords and crossbows..." be better?

===Multiplayer maps===

===Translation code bugs===

==Unofficial campaigns==

===Invasion from the unknown===

SpellingMistakes

2011-04-03T16:39:41Z

Mountain King: /* Units */

This page is meant to be a list of spelling mistakes in campaigns and other translatable texts in the en_US development version of the game.

Note: The house style of Wesnoth uses a good many words and constructions that are archaic, poetic, or dialectal. If you speak modern English as a second language you may incorrectly read these as errors. Please see [[NotSpellingMistakes]] for a list of things you will encounter that may look like spelling or usage errors but are not. Note that the mainline campaigns are now using correct typography, including sexed quotes and en and em dashes. These will appear as three byte sequences if you are not using a viewer that supports UTF-8.

==Mainline Campaigns==

===An Orcish Incursion===

===Dead Water===

===Delfador's Memoirs===
S13: "This was ill tidings for men and Elves alike."
This was -> These were

===Descent into Darkness===

===Eastern Invasion===
S1: "In the days of the king Garard I..."
king Garard I -> King Garard I

===Heir to the Throne===

===Liberty===

===Northern Rebirth===
S05a: "The hole wasn’t big enough for me to go through but one you little guys you might fit."
one you little guys you might fit -> one of you little guys might fit
S07a: "That’s why we have come here, to seek yours and your brothers help in defeating the orcs."
yours and your brothers -> your and your brother's
S09a: "Pff, foolish human. What in the world gave you that idea."
idea. -> idea?

===Sceptre of Fire===
S5: "Och, its some o’ them cave-dwarves."
its -> it’s

* scenario 4 (line 157) ''That makes sense, I guess you '''would''' to plan the sceptre’s design... what in particular do you want him to do?''

That makes sense, I guess you would want to plan the sceptre’s design... What in particular do you want him to do?

===Son of the Black Eye===

===The Hammer of Thursagan===

===The Legend of Wesmere===
S3: "How can they dare to brake the treaty!" brake -> break

===The Rise of Wesnoth===

===The South Guard===

===Two Brothers===

===Under the Burning Suns===

==Wesnoth Game==

===Editor===

===Help===
* somewhere in the help textdomain
''Original text:'' (..) Far to the west in the <del>the </del>Great Ocean is a huge archipelago called (..)
''Proposed replacement:'' (..) Far to the west in the Great Ocean <ins>there </ins>is a huge archipelago called (..)

===Tutorial===

===Manual===

===Manpages===

===Units===

===1.10 Announcement===

===Other (unit descriptions, ...)===

* Mechanical units generally have mechan'''o'''cal as their only trait. Since mechanical units don’t really have life, drain, poison and plague has no effect upon them.
mechanocal -> mechanical *fixed in development version

===Multiplayer maps===

===Translation code bugs===

==Unofficial campaigns==

===Invasion from the unknown===

SpellingMistakes

2011-04-03T16:39:17Z

Mountain King: /* Units */

This page is meant to be a list of spelling mistakes in campaigns and other translatable texts in the en_US development version of the game.

Note: The house style of Wesnoth uses a good many words and constructions that are archaic, poetic, or dialectal. If you speak modern English as a second language you may incorrectly read these as errors. Please see [[NotSpellingMistakes]] for a list of things you will encounter that may look like spelling or usage errors but are not. Note that the mainline campaigns are now using correct typography, including sexed quotes and en and em dashes. These will appear as three byte sequences if you are not using a viewer that supports UTF-8.

==Mainline Campaigns==

===An Orcish Incursion===

===Dead Water===

===Delfador's Memoirs===
S13: "This was ill tidings for men and Elves alike."
This was -> These were

===Descent into Darkness===

===Eastern Invasion===
S1: "In the days of the king Garard I..."
king Garard I -> King Garard I

===Heir to the Throne===

===Liberty===

===Northern Rebirth===
S05a: "The hole wasn’t big enough for me to go through but one you little guys you might fit."
one you little guys you might fit -> one of you little guys might fit
S07a: "That’s why we have come here, to seek yours and your brothers help in defeating the orcs."
yours and your brothers -> your and your brother's
S09a: "Pff, foolish human. What in the world gave you that idea."
idea. -> idea?

===Sceptre of Fire===
S5: "Och, its some o’ them cave-dwarves."
its -> it’s

* scenario 4 (line 157) ''That makes sense, I guess you '''would''' to plan the sceptre’s design... what in particular do you want him to do?''

That makes sense, I guess you would want to plan the sceptre’s design... What in particular do you want him to do?

===Son of the Black Eye===

===The Hammer of Thursagan===

===The Legend of Wesmere===
S3: "How can they dare to brake the treaty!" brake -> break

===The Rise of Wesnoth===

===The South Guard===

===Two Brothers===

===Under the Burning Suns===

==Wesnoth Game==

===Editor===

===Help===
* somewhere in the help textdomain
''Original text:'' (..) Far to the west in the <del>the </del>Great Ocean is a huge archipelago called (..)
''Proposed replacement:'' (..) Far to the west in the Great Ocean <ins>there </ins>is a huge archipelago called (..)

===Tutorial===

===Manual===

===Manpages===

===Units===

The lieutenant's description says "Trained at swords and crossbows..." which is rather poor grammar. Might "Trained in swords and crossbows..." be better?

===1.10 Announcement===

===Other (unit descriptions, ...)===

* Mechanical units generally have mechan'''o'''cal as their only trait. Since mechanical units don’t really have life, drain, poison and plague has no effect upon them.
mechanocal -> mechanical *fixed in development version

===Multiplayer maps===

===Translation code bugs===

==Unofficial campaigns==

===Invasion from the unknown===

User:Mountain King

2011-03-04T21:00:53Z

Mountain King:

I am me. You are you. Need I say more?

I am the current maintainer of the Irish (Gaeilge or simply ga) translation of Battle for Wesnoth.

WesnothTranslations

2011-03-04T20:53:38Z

Mountain King: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: CloudiDust - [mailto:cloudidustATgmailDOTcom], we have a Chinese forum here [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: 楊綮銘 (Taiwan) - [mailto:steven2880ATgmailDOTcom]
* [[CroatianTranslation|Croatian]] - maintainer: (needs a maintainer)
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Alexander van Gessel (AI/AI0867) - [mailto:AI0867_AT_gmail.com]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: Steven Panek (Espreon) - [mailto:Majora700ATgmailDOTcom]
* [[EnglishShawTranslation|English (Shaw)]] - maintainer: Arc Riley - [mailto:ArcRileyATubuntu.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Manuel Ortega - [mailto:manuelATelarteDOTcoop]
* [[EstonianTranslation|Estonian]] - maintainer: Kaido Kikkas (UncleOwl) - [mailto:kaidoDOTkikkasATkakupesaDOTnet]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:samu.voutilainenATgmailDOTcom]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] - translation team mailing list [mailto:wesnothATmlDOTfreeDOTfr]
* [[FriulianTranslation|Friulian]] - maintainer: Michele Calligaris (MayBug) - [mailto:michele.calligaris-CAIUT-gmail.com]
* [[GalicianTranslation|Galician]] - maintainer: Adrián Chaves Fernández (Gallaecio) - [mailto:adriyetichavesATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:konsnoslATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Udvari Gábor [mailto:gaborDOTudvariATgmailDOTcom]
* [[IcelandicTranslation|Icelandic]] - maintainer: Gabríel A. Pétursson [mailto:gabrielpATsimnetDOTis]
* [[IndonesianTranslation|Indonesian]] - maintainer: Yuristyawan Pambudi Wicaksana [mailto:yuris_wicaksana@yahoo.com]
* [[IrishTranslation|Irish]] - maintainer: Carson "Mountain_King" [mailto:tree_rings@rocketmail.com]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: IWAI, Masaharu (iwaim) - [mailto:iwaim.subATgmailDOTcom], Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: mistzone - [mailto:drier22ATgmailDOTcom]
* [[LatinTranslation|Latin]] - maintainer: Michael Babich ([[User:Aethaeryn|Aethaeryn]])
* [[LatvianTranslation|Latvian]] - maintainer: Reinis Danne - [mailto:rei4danATgmailDOTcom]
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MarathiTranslation|Marathi]] - maintainer: Sujit R Jadhav - [mailto:sujitrjadhavATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov (Mythological)
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Diego Inácio Goergen - [mailto:thegoergenATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RomanianTranslation|Romanian]] - maintainer: Alexandru Szasz [mailto:alexxedATgmailDOTcom]
* [[RussianTranslation|Russian]] - maintainer: Victor Sergienko [mailto:singalenATgmailDOTcom]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[SlovakTranslation#Preklad|Slovak]] - maintainer: Aceman
* [[SlovenianTranslation|Slovenian]] - maintainer: Klemen Košir (nNa) - [mailto:klemen.nnaATgmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Pedro Llorens (PeterPorty) [mailto:p_llorens@hotmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[UkrainianTranslation|Ukrainian]] - maintainer: Sergiy Tkach (Apromix)
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Huynh Yen Loc (hhyloc) - [mailto:nightgaunt13ATgmailDOTcom]

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

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[ImageLocalization]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]
* [[CharactersStorys| Character descriptions for Translators (Spoiler Warning)]]
* [[TextdomainStatus]]

[[Category:Translations|*]]

Elensefar

2010-12-02T19:32:53Z

Mountain King:

Elensefar is a coastal city-state among the realm of Wesnoth, situated along the Great River Delta. It is believed to have been founded soon after humans came to the Great Continent. Its name, Elensefar, also shows some connections to the elves, as the elvish capital of Lintanir forest is named Elensia. In addition, Delfador even once referred to it as the "Elense city-state", further showing connections to the elves. In all likelihood, Elensefar is a mixed city, containing populations of both elves and men.

The main city-state is a part of the broader province of Elensefar, including the surrounding lands. Its Eastern border is the city Carcyn, a point sometimes disputed by Wesnoth. Along the north lies the Great River, while the south stretches to the Bay of Pearls. The Western end of the province is the shore of the Great Ocean. Though it often allies with Wesnoth (and is considered by many to be entirely subject to Weldyn), it is not always under complete control of the Wesnothian Crown. Indeed, on more than one occasion the diverse rulers of the city have taken pains to distance themselves from Weldyn. Two such notable occasions were in 123 YW (under the leadership of the elf Meneldur) and 501 YW (under Lord Maddock), when Elenesfar directly announced itself an independent power from Wesnoth, being somewhat at odds with that great country.

One notable person to lead Elensefar was the elf Meneldur. An outcast from the Wesmere elves, he lived in the city for ten years as a sailor until it was captured by orcs in 122 YW. Setting sail once again, Meneldur found the aid of a piratical mage known as "Black the Red". After a long voyage gaining help from Black's less-than-desirable friends, Meneldur retook the city in 123 YW, and declared it independent from Wesnoth. It wasn't until forty years had gone by, in 163 YW, that Elensefar rejoined itself to the Crown of Wesnoth.

Elensefar

2010-12-02T19:20:24Z

Mountain King: made the page actually have some information

Elensefar is a coastal city-state among the realm of Wesnoth, situated along the Great River Delta. It is believed to have been founded soon after humans came to the Great Continent. Its name, Elensefar, also shows some connections to the elves, as the elvish capital of Lintanir forest is named Elensia. In addition, Delfador even once referred to it as the "Elense city-state", further showing connections to the elves. In all likelihood, Elensefar is a mixed city, containing populations of both elves and men.

The main city-state is a part of the broader province of Elensefar, including the surrounding lands. Though it often allies with Wesnoth (and is considered by many to be entirely subject to Weldyn), it is not always under complete control of the Wesnothian Crown. Indeed, on more than one occasion the diverse rulers of the city have taken pains to distance themselves from Weldyn. Two such notable occasions were in 123 YW (under the leadership of the elf Meneldur) and 501 YW (under Lord Maddock), when Elenesfar directly announced itself an independent power from Wesnoth, being somewhat at odds with that great country.

One notable person to lead Elensefar was the elf Meneldur. An outcast from the Wesmere elves, he lived in the city for ten years as a sailor until it was captured by orcs in 122 YW. Setting sail once again, Meneldur found the aid of a piratical mage known as "Black the Red". After a long voyage gaining help from Black's less-than-desirable friends, Meneldur retook the city in 123 YW, and declared it independent from Wesnoth. It wasn't until forty years had gone by, in 163 YW, that Elensefar rejoined itself to the Crown of Wesnoth.

Saving Elensefar

2010-11-29T20:40:02Z

Mountain King: /* Saving Elensefar */

== Saving Elensefar ==

''The tale of Meneldur's great Sea Voyage''

another campaign by turin

Meneldur, the Elven Mariner, has docked in the city of Elensefar to discuss matters with the Admiral. Years ago he
removed himself from the Elven lands and assembled a motley crew of elven archers, spearman and fencers to roam the
seas, defending Elensefar which he has pledged his allegiance to. During the night when his ship The Explorer was in the harbor, the sound of harsh yells could be heard, and the air smelled of burning pitch. Elensefar was conquered, but Meneldur vowed to return some day and retake his adopted homeland...

Current version as is 0.9 (released 9-29-05) downloadable from the campaign server. It will work with 1.0rc1+, and probably with several earlier versions. Note: User trewe updated version 1.3.3 of this campaign, which is on the 1.8 add-on server.

This campaign has a semilinear plot design. On the mainmap, you control where you move, and land on islands to
reprovision your ship. There are ships of the enemy navy trying to attack you, and when they do you fight them in a sea battle.

Currently there are 22 scenarios:
* 4 of these are are mandatory (2 at the beginning and 2 at the end)
* 13 are islands, all of which are optional
* 1 is "The High Seas", which functions like the mainmap of most campaigns
* 1 is where you go to when enemy ships attack you
* 3 are scripting scenarios (like the "Elven Council" scenario in HttT)

Your eventual objective is to go to an island Black the Red (someone you meet early on) has told you about, to get aid in saving Elensefar.

The campaign is scenario-complete. Plotwise, it was finished as of version 0.7.6 (3-10-05).

If anyone has balancing suggestions, typo fixes, or bug reports, post them in the thread (
http://wesnoth.org/forum/viewtopic.php?t=3072&start=0 ) or email me: joe AT lsimmons DOT net.

== See Also ==

* [[UserCampaigns]]

[[Category:Campaigns]]

User:Mountain King

2010-11-29T20:20:05Z

Mountain King: Created page with 'I am me. You are you. Need I say more?'

I am me. You are you. Need I say more?

BuildingScenariosAdvanced

2010-11-29T20:16:12Z

Mountain King: /* GetText & Translations */

{{BuildingScenariosNav}}

= Building scenarios: Advanced =

== '''TODO:''' ==
This contained a repetition of what was already inside [[BuildingScenariosIntermediate]]
This should contain:
* (more) information about making & using preprocessors ([[PreprocessorRef]])
* information on guidelines concerning the general layout of a scenario file
* advanced filtering
* ...

Ayone who feels like writing something, go ahead

== Advanced Events ==

===Internal Actions===
See [[InternalActionsWML]] for a complete list of all tags and values. In what follows, the basics of variable creation and manipulation are explained.

====Variables====
(This can be skipped if you're familiar with the concept of variables)

(See [[VariablesWML]] for more)

What are variables? Variables are basically names. And with those names, we associate a certain value. You can compare this with the words, because words are associated with (several) objects, people, feelings, ... So a variable is just a way of communication: you and the computer (the Wesnoth engine really) are communicating with each other!

The most important aspect of variables is that they can change with time. (If they don't we call them constants.) Because they change, we can use them to trigger events, or to detect something has happened. You did this already in [[BuildingScenariosIntermediate]], using the [event] tag. We only wanted to trigger the actions inside the [event] when Konrad moved onto tile 4,8. To do so we had to make use of the variables x,y and description.

Most variables provided by the engine are associated with a certain tag and can thus only be used inside them.

====Manipulating====
These three actions can be executed in one single tag: ''''[set_variable]''''
Say we wanted to store 'Hello World' in a variable named ''message_to_the_world''. This is how we would do this:
[event]
.
.
.
[set_variable]
#The name of our variable:
name=message_to_the_world
#The value of message_to_the_world, notice the underscore!
value= _ "Hello World!"
[/set_variable]
.
.
.
[/event]
Now, if we want to change the value to something else later on, e.g. 'Goodbye World', we can use the exact same code as above.
If we want to add something to our message we need to use this:

[event]
.
.
.
[set_variable]
name=message_to_the_world
value= _ "$message_to_the_world Have a nice day!"
[/set_variable]
.
.
.
[/event]
We've been using text variables (called strings) for now. But we can also store numbers and do some basic math with them. The following example clarifies this:

[event]
.
.
.
[set_variable]
name=number_x
value=10
[/set_variable]
[set_variable]
name=number_x
add=-9
[/set_variable]
[set_variable]
name=number_x
multiply=200
[/set_variable]
[set_variable]
name=number_x
multiply=0.5
[/set_variable]
.
.
.
[/event]
In the above, we set a variable named ''number_x'' to the value of 10. We subtract 9 (=1), multiply with 200 (=200) and divide by two (or multiply with 0.5) resulting in 100.

====Using Variables====
Now that we know how to create and manipulate variables, we'll learn how to use them.
First of all, you need to know what variables you always have at your disposal! In an event tag, these variables are
* '''side_number''': the number of the current player's side (may be empty during start or prestart events)
* '''turn_number''': the number of the current turn (may be empty during start or prestart events)
* '''x1''': this is the x-coordinate of the location where the most recent event was triggered
* '''y1''': this is the y-coordinate of the location where the most recent event was triggered
* '''x2''': this is the x-coordinate of the location that assisted in triggering the most recent event
* '''y2''': this is the y-coordinate of the location that assisted in triggering the most recent event
* '''unit''': inside an event, this is the unit at $x1,$y1
* '''second_unit''': inside an event, this is the unit at $x2,$y2
* '''this_unit''': inside a standard unit filter, this is the unit currently being considered for a possible match.

Some of these are only containers for other variables. The ''unit'' variable is an example. You can acces those 'sub'-variables by using dots:
unit.hitpoints
unit.side
...

We will use $unit in an example to show you how you can use all this:
[scenario]
.
.
.
[event]
#A unit moves onto a tile:
name=moveto
[filter]
x,y=25,26
[/filter]

[set_variable]
name=unit.hitpoints
add=-5
[/set_variable]
[set_variable]
name=unit.status.poisoned
value=yes
[/set_variable]

#After we have changed the values, we need to apply them.
#We do this by using the unstore_unit tag like this:
[unstore_unit]
variable=$unit
find_vacant=no
[/unstore_unit]
[/event]
#We're finished!
.
.
.
[/scenario]

There's one tag you don't know yet, and that's the '''[unstore_unit]''' tag. To explain this tag I'll explain it's counterparts; '''[store_unit]'''. [store_unit] stores a unit, or several units, in a variables you choose. You can then manipulate those variables as described above. However, you will need to apply these changes, and this is done by using the [unstore_unit] tag. For more see [http://www.wesnoth.org/wiki/InternalActionsWML#.5Bevent.5D InternalActions].



== [[GetText]] & Translations ==
[http://www.wesnoth.org/forum/viewtopic.php?t=11445 As Viliam pointed out] (reordered his words):

Translating programs has two steps. The first step is making [...] scenarios that are
possible to translate; preferably easy to translate. [...] The second
step is the translating of the texts... leave this to translators.

So, as a campaign/scenario developer you have to make sure your campaign will be easy to translate. You can achieve this very easily by preceding all text the user might see on the screen with an underscore. This indicates it is a translatable string. [[GetText]] will then be able to look up a translation, based on your localization settings.
To make it ever more clear, here's an example:
.
.
.
[message]
speaker=Konrad
message= _ "I am mighty Konrad! I fought many dummies and now I will fight you!"
[/message]
.
.
.

The message key contains the words that will be displayed when Konrad speaks. So this is a translatable string. So it is preceded with an underscore.

Viliam also said:

The most important rule of all is: Do not split sentences.
In some languages placing a word in a sentence requires more than mere string concatenation.
Some languages use [http://en.wikipedia.org/wiki/Declension declension].

== Quick Tag Index ==
'''[[ScenarioWML]]''' the top level tags [scenario], [multiplayer], [test], and [tutorial]
:* [[EventWML]] how to describe an event
:** [[FilterWML]]
:** [[DirectActionsWML]], [[InterfaceActionsWML]], [[InternalActionsWML]]
:* [[SideWML]] how to describe a side
:** [[SingleUnitWML]]
:** [[BuildingScenariosShroudData]]
:* [[MapGeneratorWML]] the random map generator
:* [[TimeWML]] how to describe a day
:* [[IntroWML]] how to describe the intro screen
:* [[UtilWML]] a set of preprocessors you can use

== See Also ==
* [[ScenarioWML]], [[SyntaxWML]] & [[ReferenceWML]]
* [[BuildingScenarios]]

[[Category:Create]]

BuildingScenariosIntermediate

2010-11-29T20:14:39Z

Mountain King: /* Advanced Sides */

{{BuildingScenariosNav}}

= Building scenarios: Intermediate =
In this tutorial we will dig somewhat deeper into the secrets of WML and scenario building: events, explaining the use of some special attributes, setting up somewhat more advanced sides, ...

== Events ==
You can trigger certain actions that occur during a scenario using the events mechanism. Let us look at an example of a simple event. Suppose you wanted Konrad to say "it's getting cold" when he moves to the location (4,8):

[event]
name=moveto
[filter]
id=Konrad
x=4
y=8
[/filter]
[message]
speaker=Konrad
message= _ "It's getting cold"
[/message]
[/event]

First you have the name of the event.
Here, we have a 'moveto' event, meaning it is fired every time a unit moves somewhere.
For a list of the different possible event names, see [[EventWML]]

Of course, we don't want this to be fired every single time some unit moves somewhere! So, we use the '''[filter]''' tag to filter out what kind of moveto event we want.
How filters are used is described in [[FilterWML]].

== Special attributes ==

Note that generally, a set of actions is triggered only once.
You can make a set of actions be triggered every time the event occurs
by adding the attribute '''first_time_only=no''' in the event.

Also, whenever an event is triggered, the player cannot undo the move, even if it was a moveto event. We could make a scenario where moves cannot be undone by adding the event

[event]
name=moveto
first_time_only=no
[/event]

(which would not do anything, but would prevent the player from undoing moves)

The event:

[event]
name=enemies defeated
[endlevel]
result=victory
bonus=yes
[/endlevel]
[/event]

is an implied trigger and appears automatically at the end of each scenario.
To prevent this event, add the attribute '''victory_when_enemies_defeated=no''' inside the main tag (usually [scenario]).

The attribute '''disallow_recall=yes''' prevents the player from recalling units in this scenario.

The attributes '''fog=yes''' and '''shroud=yes''' can be put in a '''[side]''' tag to make that side have fog of war/shroud. (Fog of war prevents seeing all enemy movement, shroud prevents seeing all of the map.)

== Advanced Sides ==

Ok, so as you have seen in [[BuildingScenariosSimple]], you can setup what the human player and AI player start with, and some simple options for controlling how the AI works. From the '''[side]''' tag listed below you can see we are going to learn some more interesting things that can be controlled from there. I'm not going to explain all the keys, just the new ones.

[scenario]
.
.
.

[side]
type=Lich
id=Galga
side=2
canrecruit=yes

#ifdef EASY
recruit=Skeleton,Revenant,Blood Bat,Ghost,Bone Shooter
recruitment_pattern=fighter,fighter,archer,scout
gold=300
#endif

#ifdef NORMAL
recruit=Skeleton,Revenant,Chocobone,Blood Bat,Wraith,Bone Shooter,Dark Adept
recruitment_pattern=fighter,fighter,archer,scout
gold=500
#endif

#ifdef HARD
recruit=Skeleton,Revenant,Chocobone,Wraith,Bone Shooter,Dark Adept
recruitment_pattern=fighter,fighter,archer,scout
gold=700
#endif

aggression=1.0
village_value=0.0
leader_value=50.0
enemy=1
[/side]
[/scenario]

As you can see from the above listing, the '''[side]''' tag can get a little complex.
The '''#ifdef''' is relatively simple to understand. If the user is playing EASY then everything between '''#ifdef EASY''' and '''#endif''' is set and the others are ignored. If the user is playing NORMAL then everything between '''#ifdef NORMAL''' and '''#endif''' is set and the others are ignored. Finally if the user is playing HARD then everything between '''#ifdef HARD''' and '''#endif''' is set and the others are ignored. This allows a scenario to be configured differently for each level of gameplay the user may choose. There are also two new keys listed, '''village_value''' and '''leader_value'''.

Lets get into some more interesting stuff. The map files hold the ground tiles. This is the very bottom layer of things. The units walking around during a game are on the very top layer. This is all well and good, but wouldn't it be nice to be able to place some unique items on the map? What if you wanted to place a building, or a potion, or anything somewhere in your scenario? Well you can! Using the '''[item]''' tag:

[scenario]
.
.
.

[item]
x=31
y=43
image=item-holywater.png
[/item]

.
.
.
[/scenario]

The '''[item]''' tag is actually very simple to use, as you can see from above. There are three keys, the first two are '''x''' and '''y'''. They are the location on the map. The third key is '''image'''. This it the image file to place in that location. This image must be located in the images directory. Ok, that was simple wasn't it?

Now you have enough information to make some interesting looking scenarios with tuned AI players. This is a big step. Next we are going to learn how to make your newly created scenario fit nicely into a campaign. This involves making the intro shown before the scenario is played a bit more descriptive. This is all done from within the '''[story]''' tag.

[scenario]
.
.
.

[story]
[part]
story= _ "... but one of the Orcs survived long enough to send the news to the queen..."
image=misc/story6.png
[/part]
.
.
.
[/story]
.
.
.
[/scenario]

The story tag contains the story told before the player starts the scenario. You can ommit this, then you will skip the introductionary screens. A story tag exists out of parts (inside [part] tags). Each part can contain several keys describing what content it has got. See [[IntroWML]] for more information.

== See Also ==
* [[ScenarioWML]] & [[SyntaxWML]]
* [[BuildingScenarios]]

[[Category:Create]]

BuildingScenariosIntermediate

2010-11-29T20:13:54Z

Mountain King: /* Events */

{{BuildingScenariosNav}}

= Building scenarios: Intermediate =
In this tutorial we will dig somewhat deeper into the secrets of WML and scenario building: events, explaining the use of some special attributes, setting up somewhat more advanced sides, ...

== Events ==
You can trigger certain actions that occur during a scenario using the events mechanism. Let us look at an example of a simple event. Suppose you wanted Konrad to say "it's getting cold" when he moves to the location (4,8):

[event]
name=moveto
[filter]
id=Konrad
x=4
y=8
[/filter]
[message]
speaker=Konrad
message= _ "It's getting cold"
[/message]
[/event]

First you have the name of the event.
Here, we have a 'moveto' event, meaning it is fired every time a unit moves somewhere.
For a list of the different possible event names, see [[EventWML]]

Of course, we don't want this to be fired every single time some unit moves somewhere! So, we use the '''[filter]''' tag to filter out what kind of moveto event we want.
How filters are used is described in [[FilterWML]].

== Special attributes ==

Note that generally, a set of actions is triggered only once.
You can make a set of actions be triggered every time the event occurs
by adding the attribute '''first_time_only=no''' in the event.

Also, whenever an event is triggered, the player cannot undo the move, even if it was a moveto event. We could make a scenario where moves cannot be undone by adding the event

[event]
name=moveto
first_time_only=no
[/event]

(which would not do anything, but would prevent the player from undoing moves)

The event:

[event]
name=enemies defeated
[endlevel]
result=victory
bonus=yes
[/endlevel]
[/event]

is an implied trigger and appears automatically at the end of each scenario.
To prevent this event, add the attribute '''victory_when_enemies_defeated=no''' inside the main tag (usually [scenario]).

The attribute '''disallow_recall=yes''' prevents the player from recalling units in this scenario.

The attributes '''fog=yes''' and '''shroud=yes''' can be put in a '''[side]''' tag to make that side have fog of war/shroud. (Fog of war prevents seeing all enemy movement, shroud prevents seeing all of the map.)

== Advanced Sides ==

Ok, so as you have seen in [[BuildingScenariosSimple]], you can setup what the human player and AI player start with, and some simple options for controlling how the AI works. From the '''[side]''' tag listed below you can see we are going to learn some more interesting things that can be controlled from there. I'm not going to explain all the keys, just the new ones.

[scenario]
.
.
.

[side]
type=Lich
description=Galga
side=2
canrecruit=yes

#ifdef EASY
recruit=Skeleton,Revenant,Blood Bat,Ghost,Bone Shooter
recruitment_pattern=fighter,fighter,archer,scout
gold=300
#endif

#ifdef NORMAL
recruit=Skeleton,Revenant,Chocobone,Blood Bat,Wraith,Bone Shooter,Dark Adept
recruitment_pattern=fighter,fighter,archer,scout
gold=500
#endif

#ifdef HARD
recruit=Skeleton,Revenant,Chocobone,Wraith,Bone Shooter,Dark Adept
recruitment_pattern=fighter,fighter,archer,scout
gold=700
#endif

aggression=1.0
village_value=0.0
leader_value=50.0
enemy=1
[/side]
[/scenario]

As you can see from the above listing, the '''[side]''' tag can get a little complex.
The '''#ifdef''' is relatively simple to understand. If the user is playing EASY then everything between '''#ifdef EASY''' and '''#endif''' is set and the others are ignored. If the user is playing NORMAL then everything between '''#ifdef NORMAL''' and '''#endif''' is set and the others are ignored. Finally if the user is playing HARD then everything between '''#ifdef HARD''' and '''#endif''' is set and the others are ignored. This allows a scenario to be configured differently for each level of gameplay the user may choose. There are also two new keys listed, '''village_value''' and '''leader_value'''.

Lets get into some more interesting stuff. The map files hold the ground tiles. This is the very bottom layer of things. The units walking around during a game are on the very top layer. This is all well and good, but wouldn't it be nice to be able to place some unique items on the map? What if you wanted to place a building, or a potion, or anything somewhere in your scenario? Well you can! Using the '''[item]''' tag:

[scenario]
.
.
.

[item]
x=31
y=43
image=item-holywater.png
[/item]

.
.
.
[/scenario]

The '''[item]''' tag is actually very simple to use, as you can see from above. There are three keys, the first two are '''x''' and '''y'''. They are the location on the map. The third key is '''image'''. This it the image file to place in that location. This image must be located in the images directory. Ok, that was simple wasn't it?

Now you have enough information to make some interesting looking scenarios with tuned AI players. This is a big step. Next we are going to learn how to make your newly created scenario fit nicely into a campaign. This involves making the intro shown before the scenario is played a bit more descriptive. This is all done from within the '''[story]''' tag.

[scenario]
.
.
.

[story]
[part]
story= _ "... but one of the Orcs survived long enough to send the news to the queen..."
image=misc/story6.png
[/part]
.
.
.
[/story]
.
.
.
[/scenario]

The story tag contains the story told before the player starts the scenario. You can ommit this, then you will skip the introductionary screens. A story tag exists out of parts (inside [part] tags). Each part can contain several keys describing what content it has got. See [[IntroWML]] for more information.

== See Also ==
* [[ScenarioWML]] & [[SyntaxWML]]
* [[BuildingScenarios]]

[[Category:Create]]

BuildingScenariosSimple

2010-11-29T20:12:35Z

Mountain King: /* First part */

{{BuildingScenariosNav}}

= Learning things step by step =

Here we will show you a very simple scenario file and explain each line of it.
The file is not fully functional, but it will show the basics needed to describe what a scenario is all about.

'''Before reading this, it might prove useful to read something about the syntax of the Wesnoth Markup Language: [[SyntaxWML]]'''

== First part ==

<blockquote>
<pre>
<nowiki>
[scenario]

id=01_test-1
next_scenario=02_test-more

name=A Simple Test Scenario
map_data="{~add-ons/Test_Campaign/maps/testmap}"
turns=20

{DAWN}
{MORNING}
{AFTERNOON}
{DUSK}
{FIRST_WATCH}
{SECOND_WATCH}

music=wesnoth-1.ogg

[event]
name=prestart
[objectives]
side=1
[objective]
description= _ "Defeat Enemy Leader"
condition=win
[/objective]
[objective]
description= _ "Death of Konrad"
condition=lose
[/objective]
[objective]
description= _ "Turns run out"
condition=lose
[/objective]
[/objectives]
[/event]
</nowiki>
</pre>

''continued below''
     ↓ ↓ ↓
</blockquote>
Every scenario must be enclosed in a tag; the <code>[scenario]</code> tag is used for campaign scenarios. The first set of attributes in the scenario tag describe the very basics of this scenario:

* <code>id</code> (short for ''identifier'') is the computer's name for your scenario and is not displayed during the game. However, it will be used to display game statistics (they will be graphed at http://stats.wesnoth.org in numerical order, so it's also a good idea to give the <code>id</code>'s a number). This name is also referenced in other tags and files, ''e.g.,'' inside a <code>[campaign]</code> tag using the <code>first_scenario</code> attribute (see [[BuildingCampaignsTheCampaignFile]]) or inside a <code>[scenario]</code> tag using the <code>next_scenario</code> attribute (see below).

* The value of the <code>next_scenario</code> attribute is the <code>id</code> (see above) of the scenario that is played after this one is won. Units from this scenario will be available for recall (unless you modify the recall list, but that's stuff for later). If your scenario is not part of a campaign, or if this is the last scenario you should either skip this line or put <code>next_scenario=null</code> inside the file. This will tell the game to display the ''End'' screen when this scenario is won.

* The value of the <code>name</code> attribute is shown on the introduction screen before each scenario is played (this may contain a picture of a map or anything else you fancy. See [[BuildingScenariosIntermediate]] for an explanation on how to do that). It's also used to generate the default names of saved files for the level.

* The next attribute, <code>map_data</code> is a little tricky. Normally, the map data (the text that is used to generate a map) goes directly inside of the quotation marks. However, it is often useful to keep that map data in a separate file, and then include that file (still inside the quotation marks) using a [[PreprocessorRef|preprocesser]] command. The code <code>{@campaigns/Test_Campaign/maps/testmap}</code> does just that, telling the wesnoth engine to look in the file <code>campaigns/Test_Campaign/maps/testmap</code> for the map data. The <code>@</code> symbol tells wesnoth to search for the map file in both the ''userdata'' directory and the ''gamedata'' directory (see [[EditingWesnoth]] and [[PreprocessorRef]] for more information). You can create and edit map files using wesnoth's built-in [[Editor2|map editor]] (see [[BuildingMaps]] for more information).

* Finally, the last attribute in the top set of keys is <code>turns</code>. This is the number of turns a player is given to finish the scenario (it can be changed during the game, but again, that is stuff for later). If the player fails to finish the scenario in the given time, he has lost (''i.e.,'' the ''defeat'' event is triggered. See [[EventWML]] for more.)

The next section is a group of macros which will be processed by Wesnoth's [[PreprocessorRef|preprocesser]]. Macros are essentially [[WML]] shortcuts. They allow you to define certain pieces of code which can be re-used whenever they are needed. Wesnoth provides you with a whole series of standard, pre-written macros to make life easier, but you yourself can write them too (again, stuff for later).
Let's get back to this example! The macros listed above describe how a day in this scenario will progress. The list of macros above is the normal day used throughout Wesnoth. If you want the entire scenario to take place at night, remove all the macros except for <code>{SECOND_WATCH}</code>. Doing this might, for example, be useful if you've set Konrad to fight the Undead and also want the Undead to have the upper hand throughout the scenario. Remember, though, by setting this to a single time of day rather than the normal diurnal progression shown above, your scenario will effectively take place during one day (or night) rather than across many days as most scenarios do.

The <code>music</code> attribute takes for its value the name of a music file (see [[MusicListWML]] for more). This file must be in the <code>music/</code> directory and must be in [http://en.wikipedia.org/wiki/Ogg Ogg] format.

A tag you'll get to know very well when making scenarios is <code>[event]...[/event]</code>. <code>event</code> tags are used to describe what should be done when various sorts of ''events'' take place. The specific type of event is stated in the <code>event</code>'s <code>name</code> attribute. In this case we're describing the so-called <code>prestart</code> event. This event occurs just ''after'' all the introduction screens for the scenario have been shown but just ''before'' the map itself is displayed. This prestart event is used to set the scenario's objectives, i.e. the contents of the ''Scenario Objectives Dialog'' that will appear once the scenario begins. The purpose of the Scenario Objectives Dialog is to inform the player what must be accomplished to win the scenario and what circumstances bring about defeat. These winning and losing circumstances are defined using the <code>[objectives]</code> tag (N.B. that <code>objectives</code> is plural). Further, each circumstance is defined in its own <code>[objective]</code> (N.B. the singular here) tag with winning circumstances setting <code>condition</code> to <code>win</code>, and with losing circumstances setting it to <code>lose</code>. In the example above, <code>objectives</code> states victory to be "Defeat Enemy Leader". For defeat, however, <code>[objectives]</code> gives the player ''two'' possibilities: either "Death of Konrad" or "Turns run out" (any number of either winning or losing <code>[objective]</code> tags may be given). Accordingly, the Scenario Objectives Dialog will look vaguely like:

<table border=1><tr><td>
'''A Simple Test Scenario'''
 '''Victory:'''
 Defeat Enemy Leader
 '''Defeat:'''
 Death of Konrad
 Turns run out
 
        
        
      [ OK ]
</td></tr></table>

Note that the <code>[objectives]</code> tag doesn't define the circumstances of victory or defeat to the game engine. It merely tells the player what they are. Special victory or defeat conditions will have to be coded into the scenario using various [event]s.

The <code>side</code> attribute in <code>[objectives]</code> indicates that the conditions defined here by the <code>[objective]</code> tags are for the faction or alliance ''side 1'' alone (see below). In a single-player game, side 1 would usually indicate the player's faction or alliance). The underscore ("_") facilitates translation using [[GetText|Gettext]].

== Second part ==
So far so good! The last necessary part describes what the players (both human and
computer) start with, what they can do, and what they can't do. Each of the players is described in a <code>[side]</code> tag with the word ''side'' referring to a player's faction, band, or horde.

<blockquote>
    ↑ ↑ ↑
 ''continued from above''
<pre>
<nowiki>
[side]
side=1
controller=human
team_name=2
user_team_name= _ "Konrad's forces"

type=Commander
id=Konrad
canrecruit=yes

recruit=Elvish Fighter,Elvish Archer,Horseman,Mage,Elvish Shaman

{GOLD 100 50 0}
{INCOME 10 5 0}
[/side]
[/scenario]
</nowiki>
</pre>
</blockquote>

Above you can see a sample <code>[side]</code> for the human player, Konrad. The first group of attributes in the <code>[side]</code> tag pertains to the side generally:
* <code>side</code>: the leader of this side is placed on the tile represented by this digit (see [[BuildingMaps]]). It's a number from 1 to 9.
* <code>controller</code> takes either of two possible values: <code>human</code> or <code>ai</code> (''i.e.,'' ''artificial intelligence'', meaning your computer). If you don't specify this attribute, <code>ai</code> is the default.
* <code>team_name</code> describes which team the side is on. It defaults to the same number as <code>side</code>, but setting it to <code>2</code> allies this side with side 2 (if you haven't changed the <code>team_name</code> of side 2).
* <code>user_team_name</code> is the name displayed when you view the side stats (by pressing <tt>alt+s</tt> during gameplay). The underscore ("_") facilitates translation using [[GetText|Gettext]].

The next group of attributes describe the leader of this side:
* <code>canrecruit</code>: This attribute can be set to <code>yes</code> or <code>no</code> (the boolean equivalents <code>1</code> and <code>0</code> or <code>true</code> and <code>false</code> also work). If this is set to <code>no</code>, the leader won't be able to recruit (not much of a leader then, is he?). Any side without a <code>canrecruit=yes</code> attribute statement automatically loses, so be sure to include this attribute.
* <code>type</code> describes what type of unit the leader will be. The possible values are listed in [http://units.wesnoth.org the Wesnoth unit tables].
* <code>id</code> is the name and identifier of the leader.

In a campaign, all of these "leader-describing" attributes are ignored for human players (except <code>canrecruit</code>), since the leader from the previous scenario is carried over into the current one. The exception to this is, of course, the first scenario, because there is no leader from previous scenarios. However, the <code>type</code> attribute is still necessary to prevent the scenario from crashing, so be sure to include it.

The last attribute, <code>recruit</code>, is a comma-separated list of [http://units.wesnoth.org unit types]. These types will become the side's recruitment list. This too is only necessary in a human player's first scenario, because the recruit list is carried over from one scenario to the next.

Finally, two macros are called. The first, <code>GOLD</code> takes three positive numbers. These indicate the amount of money the player will start with on the <var>easy</var>, <var>normal</var>, and <var>hard</var> difficulty levels, respectively. For a human-controlled side (<code>controller=human</code>), this specifies only the minimum amount of gold. The actual amount the player starts with can be larger if the player has retained gold from previous scenarios. The second macro, <code>INCOME</code>, is analogous to <code>GOLD</code> but for the base income. The defaults values for <code>GOLD</code> and <code>INCOME</code> are 100 gold and 2 base income, respectively.

== Making it all work ==
To make this scenario playable, we need to make a campaign for it (see [[BuildingCampaignsTheCampaignFile]]).
This should '''not''' be stored in the main directory <tt>data/campaigns</tt> but rather inside <tt>userdata/data/campaigns</tt>. This prevents the breaking of mainline campaigns or, even worse, the entire game (see [[BuildingCampaignsDirectoryStructure]]).
Please note that all files (''i.e.'', the campaign file and the scenario files for each level) must be saved with the file extension <tt>.cfg</tt> (''e.g.'', <tt>testcampaign.cfg</tt>).
The following is a short, example campaign file:

[campaign]
name= _ "Test Campaign"
first_scenario=test-1
define=CAMPAIGN_TEST_CAMPAIGN
difficulties=EASY,NORMAL,HARD
difficulty_descriptions= _ "&elvish-fighter.png=Easy;*&elvish-hero.png=Medium;&elvish-champion.png=Hard"
icon=elvish-fighter.png
[/campaign]
#ifdef CAMPAIGN_TEST_CAMPAIGN
{~campaigns/test_campaign/scenarios}
#endif

The <code>[campaign]</code> tag describes the campaign. The first attribute, <code>name</code>, is displayed in the campaign selector box during gameplay. The second, <code>first_scenario</code>, is set to the ID number of the first scenario of the campaign. Subsequent scenarios are referenced by the <code>next_scenario</code> attribute of their immediately preceding scenarios (see above in the first part of this tutorial). Since the first scenario, obviously, doesn't have a predecessor, it is referenced here in the <code>campaign</code> tag. To allow wesnoth to actually find the first scenario we need to include the scenarios directory of our campaign. The last statement of the campaign file does that. The inclusion is best guarded by a preprocessor symbol ([[PreprocessorRef]]) that is unique to this campaign so all the scenarios get only included when this campaign is actually selected by the player. The preprocessor symbol for a campaign is given by the <code>define</code> key.

The attribute <code>difficulties=EASY,NORMAL,HARD</code> tells Wesnoth to use the value <code>EASY</code> if the first difficulty choice is chosen during gameplay, <code>NORMAL</code> if the second is chosen, and <code>HARD</code> if the third is chosen.
The expression <code>#ifdef</code> can be used later to test the value of this attribute (see [[PreprocessorRef]]).
It is recommended that you do not use any names other than <code>EASY</code>, <code>NORMAL</code>, or <code>HARD</code> for your macros because doing so will cause some standard macros, such as <code>{GOLD}</code> and <code>{INCOME}</code>, to not work properly.

Two optional attributes are <code>difficulty_descriptions</code> and <code>icon</code>.
As its value, <code>icon</code> holds the filename of an image to represent this campaign which will be displayed in the campaign list during gameplay.
The <code>difficulty_descriptions</code> attribute must have in its value the same number of (quote-enclosed) list items as <code>difficulties</code> has in its (not quote-enclosed) list items. This list length for both attributes is most commonly three. Also note that the list for <code>difficulty_desciptions</code> is not only quote-enclosed, but its items are separated by semicolons rather than commas. Unsurprising, in our example during gameplay <tt>elvish-fighter.png</tt> would display associated with the easy level, <tt>elvish-hero.png</tt> with normal, and <tt>elvish-champion.png</tt> with hard.

Each list item in <code>difficulty_description</code> begins with an ampersand ("&"). This is followed by the filename of the image, then an equal sign ("="), and finally the text to display (i.e., "Easy". Take note that text displayed for the easy level is not "EASY": the text used is that in <code>difficulty_descriptions</code>, not <code>difficulties</code>. Similary, the normal level's text is "Medium").

Optionally you may place an asterisk ("*") before one of list items of <code>difficulty_desciptions</code> which will cause that corresponding difficulty level to be selected as the default during gameplay. In the example above, the normal level (along with its elvish hero) is selected as the default.

== See Also ==
* [[BuildingMaps]] & [[WesnothMapEditor]]
* [[ScenarioWML]] & [[SyntaxWML]]
* [[BuildingScenarios]]

[[Category:Create]]