The Battle for Wesnoth Wiki - User contributions [en]

PortugueseContinentalTranslation

2020-02-14T20:57:32Z

Trewe: Clean up

==Bem-Vindo==

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar ativamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Ativos====

* trewe (maintainer) [mailto:sjrs456ATyahooDOTfr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.isATgmailDOTcom]
* Carlos Sousa
* Luís Passos
* lokakuu
* alfalb (tradutor/revisor de prova) [mailto:alfredoDOTsilvaATskyDOTcom]
* Manuela Silva [mailto:manuelaPONTOsilvaAROBAskyPONTOcom]

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou através do IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente, pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada por e-mail ou na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controlo [http://git-scm.com/ Git] e os ficheiros atuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans Github].

Após terem obtido o(s) ficheiro(s) *.po(s) estes podem ser abertos com o editor preferido para começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal], são bons exemplos de programas de código aberto e plataforma múltipla que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o ''patch'' para o responsável pelo projeto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objetivos dos cenários e dos comandos gerais são sempre dirigidos ao utilizador com o sujeito subentendido.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. Exceções podem sempre existir dependo do contexto.

A tradução existente das unidades pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades] que é automaticamente gerada periodicamente.

===Discurso direto===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (exceções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjetivação.

Dragos - Metafóricos

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialeto transmontano

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

===Datas do Jogo===

{|
| BW (Before Wesnoth)
| AW (Antes do Reino de Wesnoth)
|-
| AW (After Wesnoth)
| CW ([segundo a] Cronologia de Wesnoth / nas crónicas de Wesnoth)
|-
|}

==Estado da tradução==

=== Lista de Traduções ===

A lista seguinte, pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?version=master&package=&lang=pt Estatísticas da tradução]

[[WesnothTranslations]]

== Hiperligações Diversas ==

[[Category:Translations]]

TheEasternInvasion

2016-06-06T14:19:32Z

Trewe: /* Escape Tunnel */ Its 200 gold in the stable branch

:''This walkthrough has been updated for version 1.12.0.''

In this campaign you play the role of Gweddry, a human Sergeant who has the responsibility of dealing with a powerful Lich who wants to destroy Wesnoth. As a sargeant, Gweddry has the potential to level up into a Grand Marshal, a level 4 unit that can empower his troops significantly through Leadership. You start with the support of a White Mage named Dacyn, who will be by your side throughout the campaign.

As any other walkthrough, this document describes plot details that can be considered spoilers. This is particularly true for this campaign, since it contains quite a few surprises along the way, and at some points you will have to make choices that will have important repercussions for later scenarios. You may wish to read ahead to see what you will be facing. In particular, you might wish to read about the scenarios ''Captured'', ''Evacuation'' and ''Weldyn Under Attack'' in order to plan ahead.

You will encounter different types of enemies, mostly undead units (especially towards the beginning and the end of the campaign), as well as orcs and trolls. Mages and Heavy Infantrymen will provide the backbone of your army. You'll probably want to level up at least one extra Mage of Light (other than Dacyn), and a few Arch/Silver Mages and Iron Maulers. You can also recruit Spearman, Cavalryman and Horseman units (the latter a few scenarios into the campaign), but their importance is perhaps less pronounced in many of the scenarios.

You will encounter a few tough challenges along the way, so be prepared, and be careful assigning experience to your units, especially during the first few scenarios.

=== The Outpost ===

* Objectives: Defend the outpost, then move Gweddry to the trapdoor.
* Lose if: Gweddry or Dacyn dies, or turns run out.
* Turns: 16.
* Starting units: Gweddry, Dacyn.

The best approach is to recruit heavy infantry and optionally a mage. Build a line using the heavy infantry, using the castle hexes and other hexes to the northwest. When and if you have more money available later, purchase additional heavy infantry.

Just hold out for the enemy attack during night time; only rotate wounded units if possible, but do not counter-attack. At dawn, start your counter-attack without worrying too much about keeping the original line intact. Instead, try to level 2 or 3 HI to Shock Troopers. The enemy's forces quickly will cease to be any danger to yours.

On turn 7, Dacyn will mysteriously disappear, and you'll briefly meet Mal-Ravanal, the leader of the undead. On turn 10 (easy) or 12 (hard) the white mage returns and points out a trap door to exit the level. (Note that this trap door will be near your starting fort, so you'll either need to hold the fort or be prepared to get back to it by turn 16).

Use the remaining turns to level as many units as possible and only move your leader onto the trap door in the very last turn. You may be able to finish with a couple of shock troopers, another white mage, or a level 2 Gweddry.

On challenging, this scenario is quite, hmm, challenging. You can try purchasing a couple of calvary to use as a diversionary force, capturing enemy villages and running away, taunting and distracting the enemy, and sacrificing them if necessary to save your more valuable units.

=== Escape Tunnel ===
* Objectives: Move Gweddry to the end of the tunnel.
* Lose if: Gweddry or Dacyn dies, or turns run out.
* Turns: 26/24/22 (easy/medium/hard).
* Starting units: Gweddry, Dacyn.
* Other:
** Permanent holy amulet in north.
** Treasure of 200 gold in southeast (50 in 1.13).

This scenario occurs in a small cave occupied by trolls and dwarves. You start on the far west of the map, and your mission is to take Gweddry all the way to the opposite side.

Take some time to choose your supporting units, depending on which ones you want to level up the quickest. Heavy Infantry are excellent frontline units, but the downside is that they move very slowly in caves. However, since Gweddry is the only unit that ''has'' to get quickly to the far east, this might not be a big problem. You can also go for a group of mostly Mages, and a couple of Spearmen. One keep of units in total should easily be enough—there's also a convenient keep with one castle tile to recruit additional units in the middle of the map, in case you need it during the battle.

The map is quite small. A little east from your keep the path is forked into three directions: north is a small area with a holy amulet, east is the troll keep and south is the dwarven keep. These two last paths will merge again to the east, leading to the exit, where Gweddry needs to go. The dwarves are friendly and will help you fight your enemies.

Given that you will probably be using inexperienced units, it's perhaps best to avoid going directly into the troll keep, but you can hold your position near the crossroads, on the southern path, where you can easily witness a lot of action between trolls, dwarves and undead (who are following you and show up on turn 6 from the west). The different armies will all fight each other. If you want to take a defensive stance, after having moved all your units south position one strong unit (a spearman or HI) at the end of the path leading south (so only one unit a turn can attack him) and position the White Mage right behind him to heal it every turn. These two units should easily keep of the enemies following you until the end of the scenario.

The holy amulet to the north is a very useful item, which will make all the attacks (melee and ranged) of the unit that picks it up of type ''arcane''—and, unlike in other campaigns, this holy amulet is permanent! Send a quick Spearman there or Gweddry. Giving Gweddry the holy amulet (instead of a Spearman) allows him to level very quickly, which is important, since he can advance to Grand Marshal. This gives benefits in other ways on a number of later scenarios as well, such as the scenario ''The Crossing'', where you can get an easy first turn kill against the undead leader and take his castle.

Move Gweddry to the northeast escorted by other units, to help him fight individual trolls if necessary, but before moving him to the end of the cave (which ends the level) send one of your units to the cave south–east, past the funny signpost warning you of the troll hole. In the cave you will discover a chest containing a troll treasure amounting to 200 gold.

[Thrash: Alternately, I used predominately Heavy Infantry on this level. I found (on medium) they were tough enough to hold the central cave and pretty much beat the trolls into submission long enough for Gweddry to run north to the the amulet and then cover his retreat south, only then recruiting a mage when the troll numbers were lower. With other units, I had problems with the trolls overrunning them and getting Gweddry trapped to the north. Also a heavy infantry in the village by your starting fort will hold off the undead for a long time.]

=== An Unexpected Appearance ===
* Objectives: Defeat either enemy leader.
* Lose if: Gweddry or Dacyn dies or turns run out.
* Turns: 20.
* Starting units: Gweddry, Dacyn.
* Other:
** Your next scenario depends on which leader you defeat.

In this scenario you have to defeat one of the dark sorcerers on the edges of the map. Your next scenario will depend on the enemy you choose to kill. Killing the one to the west will take you to the ''Elven Alliance'' scenario, while the one to the east takes you to ''The Undead Border Patrol''.

Going east is more difficult, especially on hard, but brings you more reward, such as the chance to go to Mal-Ravanal's Capital, which gives you the opportunity to get extra experience (a lot for whoever survives) and a loyal Paladin and several Knights.

First kill Mal-Tar to get your keep. To do this, shoot him with Dacyn and attack him with Gweddry's melee. If you don't kill him the first turn, second turn kill him with Dacyn so Gweddry can recruit. You will be fighting a mix of undead and bats, so recruit Heavy Infantry and Mages (if you gave the amulet to a Spearman in the previous scenario, recall him, too). Dacyn might be wounded, so send him to a village. Don't worry, he can fend for himself, since the bats usually arrive one at a time and he can kill one per turn.

On easy or medium (or hard going west), the attackers should be no problem, so focus on leveling units. If you move quickly you should only need to fight the attackers from one leader. Of course you can have some of your units double back to engage the second set.

=== Diverging Campaign Path ===

==== Elven Alliance ====
* Objectives: Defeat enemy leader.
* Lose if: Gweddry, Dacyn or Volas dies or turns run out.
* Turns: 24/22/20 (easy/medium/hard)
* Starting units: Gweddry, Dacyn.

The Orc's warning about the assassin is overrated; Volas can probably take care of it himself, although you might want to leave ONE unit near him to make sure. The assassin disappears into the forest, but you won't bump into him, he'll just reappear near the elf leader on turn 6.

Recruit / recall a wide assortment of units, mostly mages, spearmen and cavalry. Send mages and spearmen up to fight the opponent, send cavalry down as scouts. Any heavy infantry should go up to fight also; they will probably arrive late, and be good for reinforcements when the first troops are wounded.

Align the troops in the forest, so that the enemy will be on grass; this gives you a tactical advantage. Use Dacyn to heal those who need it most - those on the corners, and any mages who are on the front lines.

There is a village at {20,8} that can prove tactically very useful, because the elves usually fight somewhere near it.
The elves are defeated most of the time, and the orcs claim this village; it is crucial to kill the orc on this village and take it over with a resilient spearman, or a HI.

Once you have gotten past turn 6, it will be day, and the orcs will be very easy to defeat. When the assassin appears, you may ignore it unless you have a unit close-by. In that case, use it to fight the assassin. Keep pressing up. It is possible to kill the orcish leader by turn 9 for a nice gold bonus.

==== The Undead Border Patrol ====
* Objective: Defeat either enemy leader.
* Lose if: Gweddry or Dacyn dies, or turns run out.
* Turns: 20.
* Starting units: Gweddry, Dacyn.
* Other:
** Your next scenario depends on which leader you defeat.

This scenario also depends on which way you want to go. There is a Dark Sorcerer in the north-west corner and a Lich in the south-east corner. Defeating the Lich will give you the chance to go to ''Mal-Ravanal's Capital'', a challenging but rewarding scenario, while defeating the sorcerer is easier, and takes you directly to ''The Northern Outpost''.

If going NW, it is fairly straightforward. The enemy is relatively weak. Do the same as in Unexpected Appearance—you may recruit a couple of suicide cavalrymen to distract the bats. One will probably get enough XP to be worth recalling. Because of the open terrain, it is recommended to use mostly heavy infantry and spearmen with the holy amulet on this level and few mages. However, as in most scenarios against undead, white mages are very useful. Try to get the opponent to fight you from the sand; this gives you a significant advantage.

If you go East, expect to take some time getting over the river and through the swamp. A small force recruited to defend the fort will keep troops from the NW off of your backside and they'll pick up a good amount of experience in the process.

===== Mal-Ravanal's Capital =====
* Objective: Escape from the capital by killing one of the two dark sorcerers.
* Lose if: Gweddry or Dacyn dies, or turns run out.
* Turns: 26.
* Starting units: Gweddry, Dacyn.

Only reachable from ''The Undead Border Patrol'' scenario, but you may skip it and go directly to ''Northern Outpost''.

The main reason to get here is to acquire a cavalry force of one Paladin (a loyal unit) and five Knights. Focus on freeing the horsemen as quickly as possible. To do this, kill the 6 Revenants guarding the cages (they will not move unless you attack them first), but note the number of Knights available is reduced by one for each of your troops that die *after you rescue the first one*. You might want to make sure any expendable troops are "expended" before this. Each rescued unit pops in with full moves.

The regular Time of Day cycle does not apply here. Instead, dusk and night are twice as long as usual, so adjust your tactics accordingly. Most importantly, try to finish the mission quickly.

''Comments'': This is a very challenging scenario. I started with only 100 gold, so I recalled one Mage, two Shock Troopers, one Heavy Infantry, and my holy Halberdier. I defended the starting castle for about 10 turns until the Revenants had made their way over to me. Upon killing several of them, I freed some imprisoned Knights and a Paladin. I moved my forces to kill the Death Knight, and then split my forces. I sent one group to attack Mal-Ravanal and the other to kill the Necromancer in the NW corner. By turn 30, my Eastern assault force was in postion to attack Mal-Ravanal. However, when I attacked him I wasn't able to defeat him. When I was ready, I killed the NW Necromancer and progressed to ''The Northern Outpost''.

If you just want to rescue the paladin and 5 knights and get out (in 1.6), this is how I finished that by turn 8. The horses were captive in 6 cages, 4 in a northern loop and 2 in a southern loop. First turn, I sent a quick shock trooper, quick heavy, and a white mage (not Dacyn) around the northern loop, looping from bottom to top. I looped that way to clear the middle ASAP and escape the oncoming troops. Also first turn, I sent 3 shock troopers around the southern loop, looping from top to bottom. If you encounter resistance, kill it quick or run as required, and instead focus on killing the guards fast, which conveniently don't hit back. On turn 2, I recruited another keep full of recruits and immediately sent everyone else to take out the northwestern leader. Time it so you kill the northwestern leader just as the last horses are rescued. It is by no means easy, but this way I managed to lose only a few HI types while picking up all 6 horses.

[elvish_sovereign] (1.8.2 Normal) An alternate strategy for the above if you have more leveled mages than leveled HI's. It also requires that you gave the Holy Amulet to Gweddry. I sent a single quick Shock Trooper due south (recruited on the southern-most hex on the starting castle), which promptly took out the southern Revenant on turn 3. Forget about the villages, it'll only delay you. I sent Dacyn due north, a quick RM go take out the second from the bottom Revenant, and a quick HI and a WM with Gweddry to take out the middle-couple Revenants. I also recruited two HI's to stop the advance and distract the two Dark Sorcerers' troops. After Gweddry and the WM take out the third from the bottom Revenant, send that Knight south. After taking out the Revenant with the RM, send the RM, Shock Trooper, and the three Knights in the direction of the SW Dark Sorcerer. Meanwhile, Gweddry, the WM, and the HI take out the third from the top Revenant, and then get Gweddry the hell outta there with the WM. have Dacyn free the Paladin first, then have the remaining Knights, HI, and the Paladin take out the remaining Revenant and hold out in the north. As Gweddry is fleeing and the final Revenants are being felled, break through the SW Dark Sorcerer's lines (which should be easy if you distracted them properly) with the RM and the Shock Trooper, and send the three Knights to knock him into oblivion. I finished on turn 8 with no losses, but had some near-death moments.

[Thrash] My take on just getting the paladin and 5 knights quickly is you want to send units in parallel to attack the NW enemy and free as many of the knights at the same time. The trick is you free the knights and then kill the NW leader right after before all your troops get overwhelmed by units from the East. Time of day is critical - if you can get to the revenants before dusk, a white mage or shock trooper can kill them in one turn, after that it will take two turns or a little help (like a previously freed knight). Gweddry, even with an amulet, will probably take 3 turns to kill one, but with his one turn head start, that's OK. With one fort of recruits (2 white mages and 4 shock troopers), I was able to free 5 of the 6 and kill the NW enemy leader on turn 6. I sent 3 shock troopers and a white mage at the NW enemy, diverting one of those to freeing the 6th knight probably would have gotten me 6 out of the 6.

=== The Northern Outpost ===
* Objectives:
** Find the outlaw leader in the villages and kill him.
** Defeat the undead leader.
* Lose if: Gweddry, Dacyn or Owaec dies, or turns run out.
* Turns: 20.
* Starting units: Gweddry, Dacyn, Terraent.
* Other:
** A holy amulet is located on the south-west.
** Horseman units can now be recruited.
** Owaec joins your team after the fight is over.

This scenario is reachable from the ''Elven Alliance'', ''The Undead Border Patrol'', and ''Mal-Ravanal's Capital'' scenarios.

Here, there are two enemies that you must defeat: the undead and the outlaws. It is a good idea to create a separate task force for each.

The undead are fairly straightforward to defeat, and in any case Owaec usually does a good part of the work. To finish off the undead, it's useful to have a white mage, since Dacyn will be busy with his special spell to reveal the outlaws for this scenario. If you don't have a white mage, you can try recruiting a few mages or else go back one or more scenarios and promote a mage to white mage. In addition to the mages or white mage, recall whomever picked up the holy amulet in one of the previous scenarios and have them accompany Gweddry to the southeast. If Gweddry is the one with the holy amulet and you have a white mage, then you can supplement them with a mage. You should also send a cavalryman/horseman or quick spearman to pick up the new holy amulet in the southwest.

By contrast to the undead, the outlaws require a novel strategy. Recruit/recall fast units, e.g., cavalry and horsemen. You may supplement them by recalling quick spearmen and quick shock troopers. The challenge is that criminals will sometimes appear randomly around the villages you flag. Therefore, before flagging a village, make sure you have several healthy units around it. Note that you will get a chance to kill any newly appeared outlaws before they get a move. Outlaws will not appear in the villages that Owaec flags, so don't worry about him uncovering enemies for you. Send your outlaw hunting posse up the eastern side of the map flagging villages and fighting the bandits. One of the villages has the assassin that is the outlaw leader, and there are a lot of villages, so speed is of the essence.

Once your undead task force has finished the undead, form them into a second outlaw hunting posse, transferring units as needed from the first posse. When you come across the village where the bandit leader hides, divert any available units to the battle, as the bandits have a bite.

Note: A Cavalry force (such as the one acquired in Mal-Ravanal's Capital) makes short work of the bandits. Lower level units have trouble against the bandits, especially at night.

Also note, that from this scenario on you can recruit horsemen. You might want to level up a paladin or two, for fast mobile undead removal services (and quick leader assassination).

[Thrash] When I played, Oweac only recruited a couple mages, so he needed significant help as they get slaughtered quickly - I'd say 3-4 units. Also you don't really need to surround a village before flagging it, just have units in range to sweep in and attack if bandits pop out; this can save you some turns as move around as you can send one unit in to flag a village and move the rest on if nothing appears. Finally, the outlaw leader ran away when I played, so be prepared to chase him down.

=== Two Paths ===
* Objective: Defeat either enemy leader.
* Lose if: Gweddry, Dacyn or Owaec dies, or turns run out.
* Turns: 18/17/16 (easy/medium/hard).
* Starting units: Gweddry, Dacyn, Owaec.
* Other:
** Your next scenario depends on which leader you defeat.

You must choose between going north to attack the orc leader or going north-west to attack the undead leader.

One option is going north on the very east side of the map trying to fight your enemies from solid ground and mountains while they stand on sand ground with weak defense. As your troops move very slowly on this terrain, you will likely take some heavy losses however, as your enemies keep surrounding you. Also this will presumably take too many turns to reach the orc leader in time.

Thus the preferred choice is to recall a couple of shock troopers and white mages and move them on the path to the north-west in a tight formation towards the undead leader. Once you survived the first enemy onslaught without loosing units, the rest of this scenario becomes rather easy as the remaining enemies come one by one. Make sure to keep on moving fast to the north-west to reach the undead leader before turns run out.

On hard (and version 1.8.3), what will probably work better is an all-out suicidal calvary charge to assassinate the undead leader as quickly as possible.

It's worth noting that killing the orc leader results in what appears to be an easier and more rewarding subsequent scenario (The Crossing) than killing the undead leader (Undead Crossing).

=== Diverging Campaign Path ===

==== Undead Crossing ====
* Objective: Defeat the enemy leader.
* Lose if: Gweddry, Dacyn or Owaec dies or turns run out.
* Turns: 18.
* Starting units: Gweddry, Dacyn, Owaec.

You need to cross the river, but not without first defeating a necromancer who is occupying a small island to the north.

A good general strategy can be something like the following: recall a couple of quick swordsmen (or about-to-level quick spearmen), two white mages, a red mage or multiple regular mages, and any units with holy amulets. Shock troopers are too slow. Send these units as quickly as possible northwest through the swamp towards the eastern crossing. Meanwhile, recruit/recall calvary. The calvary should run as fast as possible along the southern board edge (so as to not attract undue attention from bats and swimming undead) and then up the western crossing. You can divert a couple of calvary and Owaec to snatch up villages and then those units can join the eastern assault.

Now, this scenario has a nasty surprise... Once you have fought off the bats and skeletons, you will find this was not all, as the undead leader summons a number of cuttlefish monsters (1, 2 or 4 according to the difficulty level: easy, medium or hard respectively), which appear in the water between the two crossings. These always appear on turn number 10. Be very careful where to position your troops as the cuttlefish have a very nasty melee attack.

You have at least three options for the crossing. Option 1 is to just try to get a couple of your calvary across each of the two crossings, while the rest of your units run like hell away from the water and swamp. Option 2 is to send across more units while tossing a spearman into the water as bait. Option 3 is to fight the cuttlefish, which is extremely hazardous. For a fight, maneuver your units to encourage the cuttlefish to separate, then use good melee troops backed by Gweddry (for leadership) and a white mage to kill them one at a time. Good luck. Make sure you leave your units enough time to cross the river and kill the undead leader before turns run out.

==== The Crossing ====
* Objective: Get Gweddry and Owaec across the river.
* Lose if: Gweddry, Dacyn or Owaec dies or turns run out.
* Turns: 24.
* Starting units: Gweddry, Dacyn, Owaec.
* Other:
** Special bonuses if the objective is completed while the Ogre leader is still alive.

The challenge for this scenario is crossing a wide river, where units are very vulnerable, and have very restricted mobility (particularly horses). On the northern bank of the river you will find orcs and ogres, who will fight each other given the opportunity. To the south you will find an undead leader, who will receive reinforcements by turn 8.

I had only 100 gold, so recruited some units and went straight north from turn one on. The fighting in the water was quite hard, with some orcs coming down from the north. The un-dead only appeared when I was in the middle of the river, so no encounter with them, and the ogre's helped get rid of the orcs on the north side. (Allefant)

If you have Holy Gweddry, you can (sometimes) get a 1st turn kill on the 1st undead leader, scarf up all the villages, and return to kill the 2nd undead forces before their leader can recruit anything. If you don't, the second undead leader will recruit lots of level two units. The orcs will start out across the river, but usually most of them turn back to fight the ogre reinforcements. Waiting till their first wave hits your shore and wiping them out in the water will probably leave you just enough time to cross the river and find there are only 2 or 3 enemy units left besides the leaders.

[Thrash] I don't think the above is realistic in 1.8.3. The leader is a Revenant with 47HP, both Gweddry (lvl 2) and Oweac (lvl 1) together would have to hit 100% to dish that out in one turn. He does come out to grab a village though, and Dacyn can make short work of him on turn 2.

Make sure to cover your rear flank with some expendable troops (such as Heavy Infantry) as the undead can move more quickly through the water than your units. Alternately, if you kill the first wave of undead quickly enough (by turn 3), you can make it across the river before the second wave catches you from behind.

Another strategy is to go straight into the water after killing the first undead leader using the deep water in the middle of the path to seperate the orc forces. You go to the right with Gweddry and Owaec and some support troops while letting the ogres kill many of the orcs in your way. Knights and a Paladin can hold off the orcs enough to get across while the undead behind you are not an issue.

If the ogre leader is alive at the end of the scenario, he agrees to help you, which results in the following bonuses: he joins you as a loyal unit, you get two free Ogres, and you skip ''Training the Ogres'' scenario and go directly to ''Xenophobia''.

[Thrash] I had problems with the Ogre leader dying before I could get to him. Sending Oweac into the river on turn 1 seemed to draw enough of the orcs south to solve this problem.

[Hipparchos] Agreed this is the only way to save the ogre leader (all others are too slow). I played this several ways before deciding the easiest is to recruit/recall only units with 6+ movement (horsemen, cavalrymen, fast mages and fast spearmen) which move 2 hexes through the water. Send them immediately south to the undead keep and defeat the units there in the first few turns. Then occupy the keep and wait for the reinforcements while one horseman goes west to take villages. With no keep, the reinforcements are small and easy to defeat. Then you have no problems to your rear as your fast units catch up to Oweac and cross the river. You'll take some hits on the far bank but should get through in time to keep the ogres alive.

=== Training the Ogres ===
* Objective: Capture the ogres.
* Lose if: Gweddry, Dacyn or Owaec dies.
* Turns: Unlimited.
* Starting units: Gweddry, Dacyn, Owaec.
* Other:
** To add ogres to your army, "capture" them by ZoC-locking them.

This can be a confusing scenario to understand. Basically, your three units just have to survive. However, if you want to be able to recall ogres later, you need to "capture" them by surrounding them. Any ogre which cannot move more than one hex in every direction will be added to your recall list. Ogres which reach the rocky borders will "escape".

Ogres are especially mobile on mountains (such as in the scenario ''Lake Vrug'') and in caves (in the scenario ''Captured''). Being of neutral alignment, ogres can be helpful at night (especially in the scenario ''Weldyn Under Attack''). It's best to capture at least two.

=== Xenophobia ===
* Objective: Defeat all enemy leaders.
* Lose if: Gweddry, Dacyn or Owaec die or turns run out.
* Turns: 40/36/32 (easy/medium/hard).
* Starting units: Gweddry, Dacyn, Owaec, Terraent, Grug.
* Other:
** A holy amulet near the orcs' keep.

This is a fun and silly level as all parties in the scenario (i.e. elves, orcs, drawves, and yourself) decide to fight each other instead of forming alliances. The scenario is not very difficult, so you can use this time to gain some experience for your units and pick up another permanent holy amulet (in the north, roughly in the middle between the dwarf and the orc keep).

You have two obvious options: attack the elves first or the dwarves first. Don't worry, they will be distracted by the orcs. After you kill the first leader, proceed to the orcs and then finish off the remaining leader.

Attacking the elves first has the advantage that they have the richest lands, i.e., the most villages, so it means more gold for you by the end of the scenario. It has the side effect that you're more likely to face a live orc leader relative to if you had attacked the dwarves first, as the elves are pretty good at killing him.

Attacking the dwarves first has the advantage that it's probably easier, since the orc leader is more likely to die at the hands of the elves. It has the disadvantage that you have to spend time getting out of the dwarven mountains and then you will ultimately fight a lot of elves, though most of them will have come out of their forests by then.

In either case, you have a lot of ground to cover, so try to do without any non-quick shock troopers. Calvary, white mages, red mages and spearman track units (preferably quick) are all good.

By the end of this scenario, it's very useful to have Gweddry at least on level 3, allowing you to use his leadership ability on other units like ogres (who reach their maximum at level 2). Leveling up a group of key units will also be very important for the upcoming scenario ''Captured'', where you won't be able to recruit, but a group of your most experienced veterans will have to fight their way out of a cave. You may want to prepare several mages and knights.

=== Lake Vrug ===
* Objective: Defeat the trolls and gryphons, and move Dacyn to the stronghold
* Lose if: Gweddry, Dacyn or Owaec dies, or turns run out.
* Turns: 30.
* Starting units: Gweddry, Dacyn, Owaec, Terraent, Grug.
* Other:
** The stronghold provides 100 gold.

This is a very confusing hide and seek scenario that could take you several pointless restarts until you have finally discover the enemy leaders.

There are three keeps, all north of the river. The troll leader has his keep on the northeast (go to the right into the mountains directly after crossing the bridge). To find the other two keeps, go west right after crossing the river; if you stay close to the southern line of mountains, you'll find the gryphon keep pretty easily. Finally, there is a stronghold straight north from the gryphons, and Dacyn must reach this fortress to complete the level.

Gryphons are vulnerable to the impact damage of heavy infantry and shock troopers, so recall two or three, preferably quick ones. Also recall another white mage to supplement Dacyn and as many ogres as possible, because they are probably the most useful unit for this scenario. The reason is simple: the enemy keeps are surrounded by high mountains which some of your troops cannot pass, but which the ogres handle quite easily. You might also want to recruit a horseman to scout ahead, although using that money for another mage or ogre may be a better investment.

The action for this scenario can be divided into two phases. The first phase will be surviving the first onslaught of gryphons and trolls coming your way. This will start around turn 4 with quite a number of gryphons appearing from the northwest. On hard, the onslaught will be especially difficult to handle. When you see the first gryphon swoop out of the fog, watch out! This means many others are coming behind. So, fall back away from the fog and form a defensive line that will eventually become a circle. Keep in mind that you can grab good terrain, i.e., the mountains, as gryphons are only too happy to attack you wherever you are, and your ogres will hold up well there. Once you have wounded units, position your heavy units such as shock troopers and ogres very tighly around them, as the gryphons really have quite a large moving range and thus mercilessly slay unprotected injured units.

Just when you thought you had the gryphons wrapped up, here come the trolls across the bridge. They may be only a minor nuisance on medium or easy, but on hard it's a strain facing a large number of trolls with troops bloodied by the swarm of gryphons. Trolls are really no match for your shock troopers, however, who happily troll-crack away. Place these troopers on the grassland tiles on the edge of the river, so the trolls coming from the bridge will be forced to attack from unfavorable terrain for them (ice).

Once you have dealt with this first wave of enemies, the remaining phase consists in crossing the river, finding the enemy leaders and finishing them off, which will be much easier in comparison. Unfortunately, the shock troopers won't do you much good in this end phase. When taking the enemy keeps, use the ogres, who can move well on the high mountains, unlike most of your other units.

=== Captured ===
* Objective: Rescue Gweddry, Dacyn, and Owaec, then escape through the south-west tunnel.
* Lose if: Gweddry, Dacyn or Owaec dies, or turns run out.
* Turns: Unlimited, then 16.
* Starting units: Rescue leader and two sidekicks.
* Other:
** No recruiting, but a group of your veterans will be available.
** A holy amulet to the south.

Three of your recall troops will escape from a cell and plot a rescue operation. The scenario tries to select a level 3, level 2, and level 1 unit, but it is possible to end up with many variations. This group only needs to fight an orcish grunt and a few bats as they travel west, then south. Shortly after they encounter the orcish trash heap, one of your rescuers will don a disguise to sneak past the troll guards.

The disguised unit can open a cell door to release the prisoners within. Try to select a cell containing ogres; a quick ogre has the best chance of reaching and opening another cell in the same turn. Your three heroes will also be freed, and either Dacyn or Gweddry can reach the final cell to release the last of your troops. You'll be surrounded by Troll Warriors, and unlikely to do enough damage to kill them in the first turn. Sacrifice some of your less experienced troops to block the trolls from reaching any important units.

Victory occurs when Gweddry moves through the exit in the southwest corner. There is a holy necklace in the southeast. Preferably grab the holy amulet with a horseman or something similar. He will come in very hand in later scenarios (if he survives the next scenario, that is).

If you have a large group of recallable units, loses in this scenario are not a big deal, as you're only going to be able to bring a fraction of your recall list past the next scenario, which is likely to kill off all but a few veterans. However, the steady stream of orc reinforcements can provide one last chance to level key units for ''Evacuation'', the next scenario.

=== Evacuation ===
* Objective: Destroy the bridge or defeat all enemies.
* Lose if: Gweddry, Dacyn or Owaec dies, or turns run out.
* Turns: 12.
* Starting units: Gweddry, Dacyn, Owaec, Terraent, Grug, Engineer.
* Other:
** Every unit not on the south side of the river when the bridge is destroyed will be lost (including units in your recall list).

There are two options in this scenario: you can either defeat all enemy leaders or blow up the bridge in the south. If you finish by passing the bridge, all your units that are not on the south side of the river by the time you blow up the bridge are killed by the explosion. Cruelly, this includes your nonrecalled units! Of the two options, killing all the enemy leaders is preferable if you can pull it off, so that you can keep your nonrecalled troops.

This is one of those scenarios many deem "impossible", but it is by no means impossible, even on hard. However, you must wrap your mind around an unpleasant truth: it may be necessary to accept heavy losses of high level troops. You should have a large number of level 2 and 3 units to recall to start this scenario, level 2 units with high experience and close to level up are your best asset.

Whichever option you take, watch out for the very tight time limit of 12 turns. And watch out for the level 3 trolls, as they can (and frequently will) instantly kill almost any of your units. Best fight them with mages or arcane damage dealing cavalry. Your cavalry units have a lot of impact resistance (30% and 40%) and can deal with trolls, especially if you gave amulets to cavalry or field a Paladin.

You can (in 1.12.2) lure out the Eastern and the Southern leader on turn 1, killing both during the next turn. Deal as much damage to the remaining troops of East and South during the day, so you may survive the night.

The second option - blowing up the bridge - is quite a bit easier to pull off, especially on hard or low gold. Run south with a sufficient amount of screening units and hopefully some units, not too slow units, to be evacuated. Focus on running the engineer, using other units to block for him, creating a ZOC corridor. Keep in mind that almost everyone is expendable. Use combat sparingly, just where you need to open a hole or where you see an opportunity to level up and heal. The scenario features a very large keep, so don't dilly-dally.

If you finish the scenario with just the required units plus about three level 3 units, don't panic. You can indeed finish the rest of the scenarios, even on hard, starting with just a few level 3's. Note that the next scenario, ''The Drowned Plains'', is good for leveling raw recruits. However, if you have a lot of level 3's, it would certainly be easier to tackle another upcoming "impossible" scenario, namely ''Weldyn Besieged'', so you may wish to replay ''Evacuation'' to get a better result.

WanderingHero: While this scenario is cruel, its not as asinine as it appears. You've already beaten the hardest scenarios of the campaign, so you dont have much to worry. Try saving a white mage, and maybe a Knight thats close to Paladin or a Paladin, but its hardly essential. Your heavy armors and ogres can be used to wall the enemy. Although the situation looks grim and the dialogue is grim, you actually near the end, the worst is behind you. You'll see the chequered flag soon enough.

=== The Drowned Plains ===
* Objective: Defeat Khrakrahs.
* Lose if: Gweddry, Dacyn or Owaec dies, or turns run out.
* Turns: 28/26/24 (easy/medium/hard).
* Starting units: Gweddry, Dacyn, Owaec, Terraent, Grug, Engineer.

Khrakrahs is a level-4 Skeletal Dragon that will be found in or near the castle (located on an island in the south). In getting there, you need to proceed slowly and carefully through the swamp. That is because there are lots of fairly high level undead hidden there, waiting to ambush your troops. Don't panic. They are easy to take one at a time, and you can offer the killing blow to troops that you are eager to promote. Think twice about trying to maneuver more units around the back of the one you're trying to kill, as there may be more ambushing undead there.

The dragon wanders around near the castle but only attacks units which he can kill instantly. If only strong units come near him, he tries to flee. Because of the fog the major challenge of this scenario is finding him and then getting him surrounded so he cannot just move away again. Once you have him trapped like this, slaying him should be easy using your stronger units —preferrably using impact weapons because the dragon has a low resistance there. Magical attacks from your magi are also very effective against the dragon.

This scenario is a good opportunity for all the units with holy amulets you still have with you. Use them against the ambushers. Since there's a good early finish bonus, just recruit a keep of your best anti-undead units, find and kill the dragon and reap the reward.

=== Approaching Weldyn ===
* Objective: Get Gweddry to Weldyn.
* Lose if: Gweddry, Dacyn, Owaec or Konrad II dies, or turns run out.
* Turns: 24.
* Starting units: Gweddry, Dacyn, Owaec, Terraent, Grug, Engineer.

The objective is simple enough; Gweddry has to reach the castle occupied by Konrad II. This is simply a matter of moving him there quickly. The end.

There is no challenge here, but with undead around you can pick up some XP with your fast moving arcane-enhanced troops (i.e., the ones that picked up holy amulets in earlier scenarios.) Try not to overrecruit or dilly-dally, though, as you need all the gold you can get for the next scenario, ''Weldyn Under Attack''.

=== The Council ===

Only plot in this. You see the inside of the castle.

=== Weldyn Under Attack ===
* Objective: Survive until end of turns.
* Lose if: Gweddry, Dacyn, Owaec or Konrad II dies.
* Turns: 18.
* Starting units: Gweddry, Dacyn, Owaec, Terraent, Grug, Engineer, Konrad II.
* Other:
** At the end of this scenario you will have to choose whether to fight Mal-Ravanal directly in a duel, or repel his invasion with all you've got. This dictates the final scenario you'll play for this campaign.

At scenario start, you find your keep in the center of an island. Three allied leaders also have their keeps on the island around yours. There are three enemy leaders with equal amounts of gold at their disposal. The southwestern enemy leader is the only one that recruits nightgaunts, the southeastern enemy leader is the only one that recruits bats, and the northern leader is the only one that recruits Spectres.

The time of day cycle is 3 times longer than usual in this scenario, and it starts at dusk, so the first 3 turns are at dusk, and then it stays nighttime (first and second watch) during most of the scenario, which is painful with the damage the undead will unleash.

Your strategy should be to kill off one of the leaders and his troops, so that you can take over his defensive position. It's probably easiest to take the northern keep.

The backbone of your army will be heavy infantry track units, mages, and mages of light. On the first turn, recall one of each, plus three calvary units to the rear, preferably quick. Send the calvary to rob your allies of their villages. They won't mind. Later, the calvary can run around to distract the enemy. Send your heavy infantry types, mages, and mages of light towards the target enemy stronghold. You should supplement them with any units with arcane attacks: arch mages, silver mages, white mages, and any units that picked up amulets in previous scenarios.

You probably will not be able to assassinate the leader before he is out of gold. When he dashes out to attack, check his gold. If he's broke, you might wish to ignore him for a turn or two while you kill off other units.

After you take over the stronghold, you may be able to recruit some more troops, if you saved some gold and/or did a good job capturing villages with your cavalry. Note that saving gold is of no use for ''The Duel'', so spend it now. Next, you should start preparing for the assault waves of the other two leaders. The combined assault waves may be more than your forces can survive. Therefore, while your main force braces itself, you should send out some ogres, cavalry, and/or silver mages as distractions, mostly along the board edges. They can even get in a few kills.

For your main force, unless you have taken over the southwestern keep, you need to think about the invisible, infiltrating, backstabbing Nightgaunts that are now headed your way. Have your units form a block with their back to the board edge. Round the corners of the block towards the enemy (so that you don't have one unit face four attacks.) Keep your whole line solid and heavily wounded units buried deep inside.

In addition to Nightgaunts, you have the threat of Banebows, which can do 52 ranged damage in one turn. However, they are fairly easily killed with proper strategy. Move a mage of light adjacent to blind the Banebow (i.e., remove its +25% bonus) and provide light for your lawful unit's attack (i.e., remove its -25% adjustment.) Move a shock trooper (or similar, preferably arcane enhanced) adjacent to the banebow and mage of light. Move a general up to lend leadership to the attacker. You may kill the Banebow in one attack. Otherwise, if the Banebow is quite wounded, you can use the mage of light to finish it off.

If you lose when you try to make a stand, you could instead try splitting your forces in two to attack the remaining two leaders. Some players have had success with this, killing the last leader by turn 14 or 15. Just remember that the objective is to survive until the end of turns, and Nightgaunts may be a problem. Killing all three leaders is a victory though and will earn you a early finish bonus of 54/turn, which is important if you go on to ''Weldyn Besieged''.

If you have one or two silver mages available, they are quite useful in this scenario. The map is rather large so have some fast-moving units like horsemen run through enemy territory and capture individual villages. Then use the teleport ability of your silver mage to perform hit-and-run (or rather: hit-and-teleport) attacks. Make sure you do not get him killed, though, by holding out too long after attacking. Make good use of Gweddry's leadership ability (he should be a Grand Marshal by now), and of Konrad's Sceptre of Fire to get rid of the most dangerous enemies coming your way.

At the end of the scenario, you must choose between challenging Mal-Ravanal to a duel (''The Duel'') or defending Weldyn against the final undead attack (''Weldyn Besieged''). ''Weldyn Besieged'' is intended as a challenging final scenario; players without a good recall list and sizable warchest will find ''The Duel'' much more accommodating.

=== Diverging Campaign Path ===

==== The Duel ====
* Objective: Defeat Mal-Ravanal while Dacyn is nearby.
* Lose if: Gweddry or Dacyn dies, or Dacyn is not nearby when Mal-Ravanal is defeated.
* Turns: Unlimited.
* Starting units: Gweddry, Dacyn.
* Other:
** You can only recruit for the first turn.

This is a somewhat strange scenario: you get to recall/recruit exactly five units and then have to fight Mal-Ravanal and his six chosen troops. Mal-Ravanal will recruit mostly level 3 units so this looks difficult. However, it is, in fact, quite manageable. Your goal is to attack first and hit hard—you should be able to eliminate two or three enemy units before they even get the chance to attack.

Except for Konrad II, you will have all of your units available in the recall list (including Owaec). Recall mages of light and other high-level arcane troops. Advance onto the battlefield, but stop just short of the enemies' range. After the enemies move closer, concentrate your attacks on a few of their units, particularly those with the strongest attacks. "Cowardly" Gweddry may be able to grant leadership bonuses to your troops, however he should probably refrain from actual fighting so he does not accidentally get killed.

Try to finish the fight quickly, as Mal-Ravanal plays unfair and every so often recruits another 3 units, albeit not so tough as the first batch of 6. If you position a weak unit within Mal-Ravanal's movement range the arrogant lich will gleefully charge out onto the battlefield and leave himself wide open for your counterattack.

==== Weldyn Besieged ====
* Objective: Defeat Mal-Ravanal while Dacyn is nearby.
* Lose if: Gweddry, Dacyn, Owaec or Konrad II dies, any enemy unit reaches your keep, or Dacyn is not nearby when Mal-Ravanal is defeated.
* Turns: Unlimited.
* Starting units: Gweddry, Dacyn, Owaec, Terraent, Grug, Konrad II.

This battle is intended as a substantial challenge, and is inadvisable with low gold or an inadequate recall list. You face off against seven enemy leaders, with the goal of finding and eliminating Mal-Ravanal among them. The liches' names aren't revealed until they are attacked, and Mal-Ravanal is more likely to be revealed later in the scenario (the names are randomly assigned when you attack). Attacking a lich gives it a small boost of gold, but killing the wrong lich gives every other lich extra gold.

A quick scout unit can charge past the undead hordes to attack and identify a lich. Once you've found Mal-Ravanal, send Dacyn and any mounted arcane-attack units to attack. You can draw Mal-Ravanal out of the keep by positioning a sacrificial horseman nearby. Once the lich is out in the open, your arcane damage cavalry should have no trouble finishing the battle in a single turn.

Meanwhile you'll need the rest of your troops to hold the central keep against the undead onslaught. If you can spare the funds, a few sacrificial troops can delay the incoming enemies on one side, giving you the opportunity to focus your firepower on the undead approaching from the other side(s). Note, however, that each enemy killed causes the lich to recruit another. If things turn grim, retreat to the castle and make your final stand.

[[Category:Campaigns]]
[[Category:Campaigns - Walkthroughs]]

DirectActionsWML

2015-12-12T19:26:08Z

Trewe: /* [endlevel] */ bonus= enhacenment

{{WML Tags}}
== Direct actions ==

Direct actions are actions that have a direct effect on gameplay. They can be used inside of [[EventWML|events]].

The following tags are actions:

=== [endlevel] ===
Ends the scenario.
* '''result''': before the scenario is over, all events with ''name=result'' are triggered. If ''result=victory'', the player progresses to the next level (i.e., the next scenario in single player); if ''result=defeat'', the game returns to the main menu.

When the result is "victory" the following keys can be used:
* '''bonus''': whether the player should get bonus gold (maximum possible gold that could have been earned by waiting the level out). The default is bonus=yes. {{DevFeature1.13|2}} Alternatively, an integrer, defining the bonus percentage (1.0 meaning full).
* '''carryover_report''': whether the player should receive a summary of the scenario outcome, the default is carryover_report=yes.
* '''save''': whether a start-of-scenario save should be created for the next scenario, the default is save=yes. Do not confuse this with saving of replays for the current scenario.
* '''replay_save''': whether a replay save for the current scenario is allowed, the default is replay_save=yes. If yes, the player's settings in preferences will be used to determine if a replay is saved. If no, will override and not save a replay.
* '''linger_mode''': If ...=yes, the screen is greyed out and there's the possibility to save before advancing to the next scenario, the default is linger_mode=yes.
* '''reveal_map''': (Multiplayer only) (Default is 'yes') If 'no', shroud doesn't disappear when game ended.
* '''next_scenario''': (default specified in '''[scenario]''' tag) the ID of the next scenario that should be played. All units that side 1 controls at this point become available for recall in ''next_scenario''.
* '''carryover_percentage''': by default 80% of the gold is carried over to the next scenario, with this key the amount can be changed.
* '''carryover_add''': if true the gold will be added to the starting gold the next scenario, if false the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is false.
* '''music''': (default specified in '''[scenario]''' or '''[game_config]''' tags) a comma-separated list of music tracks from which one will be chosen and played once after any events related to the end of level result are executed; by default, victory_music is used on victory, and defeat_music on defeat.
* '''end_credits''': Whether to display the credits screen at the end of a single-player campaign. Defaults to ''yes''. Note that this has cumulative effects over the campaign - it persists even if the endlevel does not trigger the end of the campaign. See also [[CampaignWML]].
* '''end_text''': (translatable) Text that is shown centered in a black screen at the end of a campaign. Defaults to "The End". Note that this has cumulative effects over the campaign - it persists even if the endlevel does not trigger the end of the campaign. See also [[CampaignWML]].
* '''end_text_duration''': Delay, in milliseconds, before displaying the game credits at the end of a campaign. In other words, for how much time '''end_text''' is displayed on screen. Defaults to 3500. Note that this has cumulative effects over the campaign - it persists even if the endlevel does not trigger the end of the campaign. See also [[CampaignWML]].
* <strike>'''[next_scenario_settings]''': Any tags or attribute children of this optional argument to [endlevel] are merged into the scenario/multiplayer tag of the *next* scenario. This allows you to e.g. reconfigure the [side] tags or settings, just before load. </strike> This feature was removed in 1.11.17, it might be redesigned and reintroduced.
* <strike>'''[next_scenario_append]''': Any tags of this optional argument are appended at high level to the next scenario. This is most appropriate for [event] tags, although you may find other uses. Example test scenario for these features: https://gna.org/support/download.php?file_id=20119 </strike> This feature was removed in 1.11.17, it might be redesigned and reintroduced.
* '''[result]''' {{DevFeature1.13|0}} Allows specification of a side specific result, this is for competitive multiplayer scenarios/campaigns where it might happen that one player wins but another player loses. The following attributes are accepted and have the same effect as in '''[endlevel]''':
** '''result'''
** '''bonus'''
** '''carryover_percentage'''
** '''carryover_add'''

And there is also
** '''side''' The number of the side for which these results should apply.

=== [unit] ===
Places a unit on the map. For syntax see [[SingleUnitWML]].
* {{Short Note:Predefined Macro|GENERIC_UNIT}}
* '''to_variable''': spawn directly into a variable instead of on the map.

=== [recall] ===
Recalls a unit taking into account any [http://wiki.wesnoth.org/SingleUnitWML filter_recall] of the leader. The unit is recalled free of charge, and is placed near its leader, e.g., if multiple leaders are present, near the first found which would be able to normally recall it.

If neither a valid map location is provided nor a leader on the map would be able to recall it, the tag is ignored.

* [[StandardUnitFilter]]: the first matching unit will be recalled. If no units match this tag is ignored. Do not use a [filter] tag. If a comma separated list is given, every unit currently considered for recall is checked against all the types (not each single one of the types against all units).
* '''x,y''': the unit is placed here instead of next to the leader.
* '''show''': yes/no, default yes: whether the unit is animated (faded in) or instantly displayed
* '''fire_event''': boolean yes|no (default no); whether any according prerecall or recall events shall be fired.
* '''check_passability''': (boolean yes|no, default yes): If yes, checks for terrain passability when placing the unit (a nearby passable hex is chosen).

=== [teleport] ===
Teleports a unit on map. {{Short Note:Predefined Macro|TELEPORT_UNIT}}
* '''[filter]''': [[StandardUnitFilter]] the first unit matching this filter will be teleported.
* '''x,y''': the position to teleport to. If that position is not empty, some other location will be chosen.
* '''clear_shroud''': should shroud be cleared on arrival
* '''animate''': should a teleport animation be played (if the unit doesn't have a teleport animation, it will fade out/fade in)
* '''check_passability''': (boolean yes|no, default yes): normally, units will not be teleported into terrain that is impassable for them. Setting this attribute to "no" permits it.

(Note: There is also a ability named teleport, see [[AbilitiesWML]].)

=== [terrain_mask] ===
Changes the terrain on the map. See [[TerrainMaskWML]].

=== [terrain] ===
Changes the terrain on the map.
* '''terrain''': the character of the terrain to use. See [[TerrainCodesWML]] to see what letter a type of terrain uses.
* [[StandardLocationFilter]]. This [[StandardLocationFilter]]'s terrain= key is used for the new terrain, filtering by terrain can be done with a nested [[StandardLocationFilter]]: [and]terrain=terrain_string_to_be_filtered_for.
* '''layer''': (overlay|base|both, default=both) only change the specified layer.
* '''replace_if_failed''': (default=no) When replacing just one layer failed, try to replace the whole terrain. If '''terrain''' is an overlay only terrain, use the default_base as base layer. If the terrain has no default base, do nothing.

If you want to remove the overlays from a terrain and leave only the base, use:
layer=overlay
terrain="^"

<b>Note:</b> When a hex changes from a village terrain to a non-village terrain, and a team owned that village it loses that village. When a hex changes from a non-village terrain to a village terrain and there is a unit on that hex it does not automatically capture the village. The reason for not capturing villages it that there are too many choices to make; should a unit loose its movement points, should capture events be fired. It is easier to do this as wanted by the author in WML.

=== [gold] ===
Gives sides gold.
* '''amount''': the amount of gold to give.
* '''side''': (default=1) the number of the side to give the gold to. Can be a comma-separated list of sides. note: Default side=1 for empty side= is deprecated.
* [[StandardSideFilter]] tags and keys; default for empty side= is all sides, as usual in a SSF.

=== [unstore_unit] ===
Creates a unit from a game variable, and activates it on the playing field. This must be a specific variable describing a unit, and may not be an array -- to unstore an entire array, iterate over it. The variable is not cleared. See also [[InternalActionsWML#.5Bstore_unit.5D|[store_unit]]], [[ConditionalActionsWML#.5Bwhile.5D|[while]]] and [[InternalActionsWML#.5Bclear_variable.5D|[clear_variable]]].
* '''variable''': the name of the variable.
* '''find_vacant''': whether the unit should be placed on the nearest vacant tile to its specified location. If this is set to 'no'(default), then any unit on the same tile as the unit being unstored will be destroyed.
* '''check_passability''': (boolean yes|no, default yes): If yes, checks for terrain passability when placing the unit. This key has no effect if find_vacant=no (no check performed then). Before 1.9 this key is always "no".
* '''text''': (translatable) floating text to display above the unit, such as a damage amount
* '''male_text''', '''female_text''': {{DevFeature1.13|2}} (translatable) gender-specific versions of the above
* '''red''', '''green''', '''blue''': (default=0,0,0) the color to display the text in. Values vary from 0-255. You may find it convenient to use the {COLOR_HARM} or {COLOR_HEAL} macro instead. (Use {COLOR_HARM} or {COLOR_HEAL} instead of the whole red,green,blue= line.)
* '''advance''': (default=true) if true the unit is advanced if it has enough XP. When modifying XP make sure to do it from inside a [[EventWML#Multiplayer_safety|synchronized event]] or it may lead to OOS errors especially when several advancement paths exist. Note that advance and post advance events are called, so infinite loops can happen.
* '''fire_event''': (boolean yes|no, default no) Whether any advance/post advance events shall be fired if an advancement takes place, no effect otherwise.
* '''animate''': (boolean yes|no, default yes) Whether "levelout" and "levelin" (or fade to white and back) animations shall be played if an advancement takes place, no effect otherwise.
* '''x''' ,'''y''': override unit location, "x,y=recall,recall" will put the unit on the unit's side's recall list.
Units can be unstored with negative (or zero) hit points. This can be useful if modifying a unit in its last_breath event (as the unit's death is already the next step), but tends to look wrong in other cases. In particular, it is possible to have units with negative hit points in play. Such units are aberrations, subject to unusual behavior as the game compensates for them. (For example, such units are currently automatically hit–and killed–in combat.) The details of the unusual behavior are subject to change between stable releases without warning.

=== [allow_recruit] ===
Allows a side to recruit units it couldn't previously recruit.
* '''type''': the types of units that the side can now recruit.
* '''side''': (default=1) the number of the side that is being allowed to recruit the units. This can be a comma-separated list note: Default side=1 for empty side= is deprecated.
* [[StandardSideFilter]] tags and keys; default for empty side= is all sides, as usual in a SSF.

=== [allow_extra_recruit] ===
Allows a leader to recruit units it couldn't previously recruit.
These types add to the types the leader can recruit because of [side]recruit=.
* '''extra_recruit''': the types of units that the unit can now recruit.
* '''[[StandardUnitFilter]]''': All units matching this filter are modified. Does not match on recall list units.

=== [disallow_recruit] ===
Prevents a side from recruiting units it could previously recruit.
* '''type''': the types of units that the side can no longer recruit. {{DevFeature1.13|0}} If omitted, all recruits for matching sides will be disallowed.
* '''side''': (default=1) the number of the side that may no longer recruit the units. This can be a comma-separated list note: Default side=1 for empty side= is deprecated.
* [[StandardSideFilter]] tags and keys; default for empty side= is all sides, as usual in a SSF.

=== [disallow_extra_recruit] ===
Prevents a leader from recruiting units it could previously recruit.
* '''extra_recruit''': the types of units that the side can no longer recruit.
* '''[[StandardUnitFilter]]''': All units matching this filter are modified. Does not match on recall list units.

=== [set_recruit] ===
Sets the units a side can recruit.
* '''recruit''': the types of units that the side can now recruit.
* '''side''': (default=1) the number of the side that is having its recruitment set. This can be a comma-separated list. note: Default side=1 for empty side= is deprecated.
* [[StandardSideFilter]] tags and keys; default for empty side= is all sides, as usual in a SSF.

=== [set_extra_recruit] ===
Sets the units a leader can recruit.
* '''extra_recruit''': the types of units that the leader can now recruit.
* '''[[StandardUnitFilter]]''': All units matching this filter are modified. Does not match on recall list units.

=== [modify_side] ===
Modifies some details of a given side in the middle of a scenario. '''The following listed properties are the only properties that [modify_side] can affect!'''
* '''side''': (default=1) the number of the side that is to be changed. note: Default side=1 for empty side= is deprecated.
* '''[filter_side]''' with a [[StandardSideFilter]] as argument
* '''income''': the income given at the begining of each turn.
* '''recruit''': a list of unit types, replacing the side's current recruitment list.
* '''team_name''': the team in which the side plays the scenario.
* '''user_team_name''': a translatable string representing the team's description. This has no effect on alliances. Defaults to ''team_name''.
* '''gold''': the amount of gold the side owns.
* '''village_gold''': the income setting per village for the side.
* '''controller''': the identifier string of the side's controller. Uses the same syntax of the ''controller'' key in the [[SideWML|[side]]] tag.
* '''fog''': a boolean string (yes/no) describing the status of Fog for the side.
* '''shroud''': a boolean string describing the status of Shroud for the side.
* '''hidden''': a boolean string specifying whether side is shown in status table.
* '''color''': a team color range specification, name (e.g. "red", "blue"), or number (e.g. "1", "2") for this side. The default color range names, numbers, and definitions can be found in data/core/team_colors.cfg.
* '''[ai]''': sets/changes AI parameters for the side. Only parameters that are specified in the tag are changed, this does not reset others to their default values. Uses the same syntax as described in [[AiWML]]. Note that [modify_side][ai] works for all simple AI parameters and some, but not all, of the composite ones. If in doubt, use [http://wiki.wesnoth.org/AiWML#Adding_and_Deleting_Aspects_with_the_.5Bmodify_ai.5D_Tag [modify_ai]] instead, which always works.
* '''switch_ai''': replaces a side ai with a new AI from specified file(ignoring those AI parameters above). Path to file follows the usual WML convention.
* '''reset_maps''': If set to "yes", then the shroud is spread to all hexes, covering the parts of the map that had already been explored by the side, including hexes currently seen. (Seen hexes will be cleared at the end of most events; they can also be manually cleared with {{tag|InterfaceActionsWML|redraw}}.) This is only effective if shroud is on, but this is evaluated after shroud= (and before shroud_data=).
* '''reset_view''': If set to "yes", then the fog of war is spread to all hexes, covering the parts of the map that had already been seen this turn by the side, including hexes currently seen, excluding hexes affected by multi-turn {{tag|DirectActionsWML|lift_fog}}. (Seen hexes will be cleared at the end of most events; they can also be manually cleared with {{tag|InterfaceActionsWML|redraw}}.) This is only effective if fog is on, but this is evaluated after fog=.
* '''share_maps''': change the share_maps side attribute. Be sure to use shroud=yes for that side and have it as an ally
* '''share_view''': change the share_view side attribute. Be sure to use fog=yes for that side and have it as an ally
* '''shroud_data''': changes to the side's shroud, using the same format as when defining the [side].
* '''suppress_end_turn_confirmation''': Boolean value controlling whether or not a player is asked for confirmation when skipping a turn.
* '''scroll_to_leader''': Boolean value controlling whether or not the game view scrolls to the side leader at the start of their turn when present.
* '''flag''': Flag animation for villages owned by this side (see [[SideWML|[side]]]).
* '''flag_icon''': Flag icon used for this side in the status bar (see [[SideWML|[side]]]).
* '''village_support''': The number of unit levels this side is able to support (does not pay upkeep on) per village it controls.

=== [modify_turns] ===
Modifies the turn limit in the middle of a scenario.
* '''value''': the new turn limit.
* '''add''': if used instead of ''value'', specifies the number of turns to add to the current limit (can be negative).
* '''current''': changes the current turn number after applying turn limit modifications, if any. It is not possible to change the turn number to exceed the turn limit (1 <= current turns <= max turns).

=== [allow_end_turn] ===
Allows human players to end their turn through the user interface if they were previously affected by the '''[disallow_end_turn]''' action. This action doesn't take any arguments.

=== [disallow_end_turn] ===
Disallows human players to end their turn through the user interface. This action doesn't take any arguments.

=== [capture_village] ===
Changes the ownership of a village.
* [[StandardLocationFilter]]: all village locations matching the filter are affected.
* '''side''': the side that takes control of the village. This side needs to have a leader (canrecruit=yes). If the side key is not given, the village will become neutral (unless [filter_side] is present, in which case that side fiter decides, see below).
* '''[filter_side]''' with [[StandardSideFilter]] tags and keys as arguments; if both this tag and inline side= are present it's an error. Otherwise, the first matching side gets ownership (or the village becomes neutral if none match).
* '''fire_event''' (boolean yes|no, default: no): Whether any capture events shall be fired.

=== [kill] ===
Removes all units (including units in a recall list) that match the filter from the game.
* [[StandardUnitFilter]]: Selection criterion; do not use a [filter] tag.
* '''animate''': if 'yes', displays the unit dying (fading away).
* '''fire_event''': if 'yes', triggers any appropriate 'die' events (See [[EventWML]]). Note that events are only fired for killed units that have been on the map (as opposed to recall list).
* '''[secondary_unit]''' with a [[StandardUnitFilter]] as argument. Do not use a [filter] tag. Has an effect only if fire_event=yes. The first on-map unit matching the filter becomes second_unit in any fired die and last breath events. If an on-map unit matches and if there are several units killed with a single [kill] tag, second_unit is this same unit for all of them. If no on-map unit matches or [secondary_unit] isn't present, the variable second_unit in each of the die and last breath events is always the same as the variable unit (the dying unit).

=== [move_unit] ===
works like the MOVE_UNIT macro.
* [[StandardUnitFilter]] as argument; do not use a [filter] tag. All units matching the filter are moved. If the target location is occupied, the nearest free location is chosen.
* '''to_x''' (unsigned integer): The units are moved to this x coordinate. Can be a comma-separated list, in which case the unit follows this given path during the move.
* '''to_y''' (unsigned integer): The units are moved to this y coordinate. Can be a comma-separated list.
* '''fire_event''' (optional, boolean yes|no, default no): Whether any according moveto events shall be fired. The target location ($x1, $y1 in the event) may not be the same location that the unit was tried to be moved to, if the original target location is occupied or impassable.
* '''check_passability''' (boolean yes|no, default yes): Whether the terrain the unit is moved to should be checked for suiting the unit. (If it does not, a nearby suitable hex is chosen.)
* '''force_scroll''': Whether to scroll the map or not even when [[InterfaceActionsWML#.5Block_view.5D|[lock_view]]] is in effect or ''Follow Unit Actions'' is disabled in ''Advanced Preferences''. Defaults to using [[InterfaceActionsWML#.5Bmove_unit_fake.5D|[move_unit_fake]]]'s default value.

=== [modify_ai] ===
Changes AI objects (aspects, goals, candidate actions or stages) for a specified side. See [[AiWML#Adding_and_Deleting_Aspects_with_the_.5Bmodify_ai.5D_Tag|AiWML]] for full description.

* '''action''' (string): Takes values 'add', 'change', 'delete' or 'try_delete' to do just that for the AI object.
* '''path''' (string): Describes which AI object is to be modified.
* '''[facet]''', '''[goal]''', '''[candidate_action]''' or '''[stage]''': Details about the AI object to be modified.
* [[StandardSideFilter]] tags and keys; default for empty side= is all sides, as usual in a SSF.

=== [modify_unit] ===
works similar to the MODIFY_UNIT macro.
* '''[filter]''' with a [[StandardUnitFilter]] as argument. All units matching this filter are modified. Matches on recall list units too.
* Accepts generally the syntax inside of wml unit variables created by [store_unit] which can be viewed in a savefile or by using the :inspect command. It can add [trait]s and [object]s without needing to wrap them inside a [modifications] tag, and their effects are applied immediately. Cannot remove things. Subtags with the same name must be written in the correct order to match them with the tag they are supposed to modify.
example usage (see also the test scenario):
[modify_unit]
[filter]
x,y=38,6
[/filter]
hitpoints=10
{TRAIT_HEALTHY}
[/modify_unit]

The unit which is currently modified is accessible via $this_unit, e.g. hitpoints = "$($this_unit.hitpoints / 2)" to set the hitpoints of all units to half of their particular maxima. This this_unit variable is independent from the this_unit variable available in the SUF used to determine which units to modify (first all matching units are gathered, and then all those are modified).

note: The syntax allowed is somehow vague. Just try things and possibly correct/add/modify this documentation. (a [http://forums.wesnoth.org/viewtopic.php?f=21&t=31676& forum thread] discusses some related issues).

=== [transform_unit] ===
Transforms every unit matching the filter to the given unit type. Keeps intact hit points, experience and status. If the unit is transformed to a non-living type (undead or mechanical), it will be also unpoisoned. Hit points will be changed if necessary to respect the transformed unit's maximum hit points.
* [[StandardUnitFilter]]: do not use a [filter] tag.
* '''transform_to''': the unit type in which all the units matching the filter will be transformed. If missing, the units will follow their normal advancement.

=== [petrify] ===

* [[StandardUnitFilter]] as an argument. Do not use a [filter] tag. All units matching this filter are petrified. Recall list units are included.

=== [unpetrify] ===
* [[StandardUnitFilter]] as an argument. Do not use a [filter] tag. All units matching this filter are unpetrified. Recall list units are included.

=== [object] ===
Gives some unit an object which modifies their stats in some way.
* '''id''': (Optional) when the object is picked up, a flag is set for ''id''. The object cannot be picked up if a flag for ''id'' has been set. This means that any object with an id can only be used once, even if first_time_only=no is set for the event. This restriction is per scenario. In a campaign objects with the same id can be assigned once per scenario. For filtering objects, custom key can be used, such as item_id.
* '''delayed_variable_substitution''' (boolean yes|no, default no): If set to "yes", the wml block contained in this [object] is not variable-substituted at execution time of the event where this [object] is within. You need this to work around a bug when adding ABILITY_TELEPORT via an [object] or when using [object][effect][filter]with a $this_unit (see http://gna.org/bugs/index.php?18893).
* '''[effect]''': one or more effect elements may be listed. See [[EffectWML]] for a description of [effect].
* '''duration''':
**if 'scenario', effects only last until the end of the level (note : 'level' is the scenario, so this doesn't mean it last until the unit levels-up).
**if 'forever' or not set, effects never wear off.
** if 'turn', effects only last until the start of the unit's next turn (when the unit refreshes movement and attacks). (Like other start-of-turn behavior, objects with a duration of "turn" won't expire before turn 2.)
** {{DevFeature1.13|1}} if 'turn end' or 'turn_end', effects only last until the end of the unit's next turn (exactly like the slowed status).
* '''[filter]''' with a [[StandardUnitFilter]] as argument. The first unit found that matches the filter will be given the object. Only on-map units are considered. If no unit matches or no [filter] is supplied, it is tried to apply the object to the unit at the $x1,$y1 location of the event where this [object] is in. The case of no unit being at that spot is handled in the same way as no unit matching a given filter ([else] commands executed, cannot_use_message displayed)
* '''[then]''': a subtag that lets you execute actions if the filter conditions are met. The most common action that should be inside here is a '''[remove_item]''' tag, but you could probably put any tags that otherwise work in a [then] tag.
* '''[else]''': a subtag that lets you execute actions if the filter conditions are *not* met.
* '''silent''': whether or not messages should be suppressed. Default is "no". {{DevFeature1.13|2}} If no description is provided, this defaults to true, but can still be overridden.
* '''image''': the displayed image of the object.
* '''name''': (translatable) displayed as a caption of the image.

* '''description''': (translatable) displayed as a message of the image.
* '''cannot_use_message''': (translatable) displayed instead of '''description''' if no unit passes the filter test.
* '''no_write''': {{DevFeature1.13|1}} (bool, default false). If true, the contents of [effect] will be applied to the relevant unit, but the [object] tag will not be written to unit.modifications. This renders duration= irrelevant.

=== [remove_shroud] ===
Removes some shroud from the map for a certain side (only relevant for sides that have shroud=yes).
* '''side''': (default=1) the side for which to remove shroud. This can be a comma-separated list of sides. note: Default side=1 for empty side= is deprecated.
* '''[filter_side]''' with a [[StandardSideFilter]] as argument
* [[StandardLocationFilter]]: the range of tiles for which shroud should be removed

=== [place_shroud] ===
Places some shroud on the map for a certain side (only relevant for sides that have shroud=yes).
* '''side''': (default=1) the side for which to place shroud. This can be a comma-separated list. note: Default side=1 for empty side= is deprecated.
* '''[filter_side]''' with a [[StandardSideFilter]] as argument
* [[StandardLocationFilter]]: the range of tiles on which shroud should be placed

=== [lift_fog] ===
Lifts the fog of war from parts of the map for a certain side (only relevant for sides that have fog=yes), allowing a player to witness what occurs there even if that player has no units within vision range.
* '''[filter_side]''' with a [[StandardSideFilter]] indicating which sides should be affected.
* [[StandardLocationFilter]]: the tiles from which fog should be lifted.
* '''multiturn''': ''yes/no, default:no''. The default (not multiturn) causes fog to be removed in the same way that normal vision works; the cleared tiles will remain cleared until fog is recalculated (which normally happens when a side ends its turn). When multiturn is set to "yes", the cleared tiles remain clear until {{tag||reset_fog}} cancels the clearing. This allows tiles to remain clear for multiple turns, or to be refogged before the end of the current turn (without also refogging all tiles). Multiturn lifted fog is not shared with allies (even when share_view=yes).

=== [reset_fog] ===
The primary use of this tag is to remove multiturn lifted fog (created by {{tag||lift_fog}}), which causes the fog to reset to what it would have been had WML not interfered. (That is, hexes that a side's units could not see at any point this turn will be re-fogged, while seen hexes remain defogged.)
* '''[filter_side]''' with a [[StandardSideFilter]] indicating which sides should be affected.
* [[StandardLocationFilter]]: the fog reset will be restricted to these tiles.
* '''reset_view''': ''yes/no, default: no'' If set to "yes", then in addition to removing multiturn fog, the side's current view is canceled (independent of the SLF). This means that all hexes will become fogged for the side unless multiturn fog exists outside the tiles selected by the SLF. Normally, one would want the currently seen hexes to become clear of fog; this is done automatically at the end of many events, and it can be done manually with {{tag|InterfaceActionsWML|redraw}}.
Omitting both the SSF and the SLF would cancel all earlier uses of [lift_fog].
Additionally setting reset_view="yes" would cause the side's entire map to be fogged (unless an ally keeps hexes clear by sharing its view).

=== [allow_undo] ===

Normally when an event with a handler fires, the player's undo stack is cleared, preventing all actions performed so far from being undone. Including this tag in the event handler prevents the stack from being cleared for this reason, allowing the player to undo actions. (However, the stack might still be cleared for other reasons, such as fog being cleared or combat occurring.) In the common cases, this means '''[allow_undo]''' allows the current action to be undone even though an event was handled. There is a less common case, though — specifically when handling a menu item, where there is no current action — and in this case, '''[allow_undo]''' means merely that earlier actions can still be undone.
* Using this tag in a menu item has an additional side effect in 1.11. Starting with version 1.11.1, executing a WML menu item normally counts as doing something as far as the "you have not started your turn yet" dialog is concerned. However, a menu item whose handler includes '''[allow_undo]''' will not count.

The types of actions that can be undone are movement, recruitment, recalling, and dismissing a unit from the recall list. If an action is undone, only the position (or existence) of the involved unit will be restored; any altered variables or changes to the game will remain changed after the action is undone. It is up to the scenario designer to avoid abusing this command.
* Technically, if '''[allow_undo]''' is inside an '''[event]''' with ''first_time_only=yes'' (the default setting), and the user undoes the event, then the state of the game has changed in this way: the event will not fire a second time, even though the user undid the action the first time.

Due to a bug in 1.12 (https://gna.org/bugs/?23323) '''[allow_undo]''' should not be used in events that use one of the following things brcause it might cause OOS:
* [message] with [option]s
* [get_global_variable]
* wesnoth.syncronize_choice

=== [heal_unit] ===
Heal a unit. The variable '''$heal_amount''' will be set to the exact number of points healed (i.e can be lesser than the parameter '''amount''' if the unit is fully healed). $heal_amount contains only the number of hitpoints the first unit that was found got healed.
* '''[filter]''': [[StandardUnitFilter]] All matching on-map units are healed. If no filter is supplied, it is tried to take the unit at $x1, $y1.
* '''[filter_second]''': [[StandardUnitFilter]] all the units matching the filter ''and'' having the ''heals'' ability will have their animation played (if ''animate'' is set to true) for each of the units healed.
* '''amount''': (integer, default full) the maximum points the unit(s) will be healed. Can't set below 1 or above max_hitpoints. If "full", sets hitpoints to max_hitpoints. Before 1.9 the default is 0.
* '''animate''': a boolean which indicate if the healing animations must be played. (default no)
* '''moves''': (integer, default 0) The maximum current movement points the units will be "healed". Can't set below 0 or above max_moves. If "full", sets moves to max_moves.
* '''restore_attacks''': (boolean, default no) Whether the units' attacks_left should be reset to their max_attacks (usually 1).
* '''restore_statuses''': (boolean, default yes) Whether standard statuses should be reset to "no". This affects poisoned, slowed, petrified and unhealable. Before 1.9 this is always "no".

=== [harm_unit] ===
Harms every unit matching the filter, for the specific damage amount.
* '''[filter]''': [[StandardUnitFilter]] all matching units will be harmed (required).
* '''[filter_second]''': [[StandardUnitFilter]] if present, the first matching unit will attack all the units matching the filter above.
* '''amount''': the amount of damage that will be done (required).
* '''alignment''': (default neutral) applies an alignment to the damage, this means that if alignment=chaotic, the damage will be increased at night and reduced at day.
* '''damage_type''': if present, amount will be altered by unit resistance to the damage type specified.
* '''kill''': (default yes) if yes, when a harmed unit goes to or below 0 HP, it is killed; if no its HP are set to 1.
* '''fire_event''': (default no) if yes, when a unit is killed by harming, the corresponding events are fired. If yes, also the corresponding advance and post advance events are fired.
* '''animate''': (default no) if yes, scrolls to each unit before harming it and plays its defense (or attack, if it's the harmer) and death animations. Special values supported, other than the usual yes and no, are "attacker", that means only the harmer will be animated, and "defender", that means only the harmed units will be animated. If the supplied value is yes, attacker or defender also advancement animations are played.
* '''[primary_attack], [secondary_attack]''': these set the weapon against which the harmed units will defend, and that the harming unit will use to attack, respectively (notice this is the opposite of '''[filter]''' and '''[filter_second]''' above). This allows for playing specific defense and attack animations. Both tags are expected to contain a [[FilterWML#Filtering_Weapons|Standard Weapon Filter]].
* '''delay''': if animate=yes, sets the delay (in milliseconds, default 500) between each unit harming.
* '''variable''': if present, the damage caused to the unit, altered by resistances, will be stored in a WML array with the given name, under the "harm_amount" key.
* '''poisoned, slowed, petrified, unhealable''': (default no) if yes, every harmed unit that doesn't already have such status will have it set.
* '''experience''': if yes, and there is a harmer, experience will be attributed like in regular combat.
* '''resistance_multiplier''': the harmed unit's resistance is multiplied by the supplied value; this means that a value lower than 1 increases it, and a value greater than 1 decreases it. Default value is 1, that means no modification.

=== [time_area] ===
How a day should progress in a given area. Everywhere not specified in a [time_area] tag is affected by the [time] tags in the [scenario] tag.
* [[StandardLocationFilter]]: the locations to affect. ''note: only for [event][time_area]s - at scenario toplevel [time_area] does not support [[StandardLocationFilter]], only location ranges''
* [[TimeWML]]: the new schedule.
* '''id''': an unique identifier assigned to a time_area. Optional, unless you want to remove the time_area later. Can be a comma-separated list when removing time_areas, see below.
* '''remove''': (boolean) yes/no value. Indicates whether the specified time_area should be removed. Requires an identifier. If no identifier is used, however, all time_areas are removed.
* '''current_time''': The time slot number (starting with zero) active at the creation of the area.

''Example:'' (caves in parts of a map)
[time_area]
x=1-2,4-5
y=1-2,1-2
{UNDERGROUND}
[/time_area]

=== [remove_time_area] ===

{{DevFeature1.13|2}}

This is a syntactic shortcut for [time_area] remove=.
* '''id''': Comma-separated list of time area ids to remove.

=== [end_turn] ===
End the current side's turn. The current event is finished before the turn is ended. Also, if the current event (where the tag appears) has been fired by another event, that event (and the complete stack of other possible parent events) is ended before [end_turn] comes into affect. Also, events following the event stack that fired [end_turn] are not omitted (e.g. [end_turn] is used by a side turn event and a turn refresh event does something afterwards).

=== [replace_map] ===

Replaces the entire map.
* '''map''': Content of a wesnoth map file. example:
map="{campaigns/Heir_To_The_Throne/maps/01_The_Elves_Besieged.map}"
* '''expand''': if 'yes', allows the map size to increase. The expansion direction is currently always bottom-right.
* '''shrink''': if 'yes', allows the map size to decrease. If the map size is reduced, any units that would no longer be on the map due to its coordinates no longer existing will be put into the recall list.
Note: When a hex changes from a village terrain to a non-village terrain, and a team owned that village it loses that village. When a hex changes from a non-village terrain to a village terrain and there is a unit on that hex it does not automatically capture the village. The reason for not capturing villages it that there are too many choices to make; should a unit lose its movement points, should capture events be fired. It is easier to do this as wanted by the author in WML.

=== [replace_schedule] ===
Replace the time of day schedule of the entire scenario.
* [[TimeWML]]: the new schedule.
* '''current_time''': The time slot number (starting with zero) active at schedule replacement.

=== [tunnel] ===

Create a tunnel between some locations, later usable by units to move from source hex to target hex (using the movement cost of unit on the target terrain). ([http://forums.wesnoth.org/viewtopic.php?f=21&t=14749&p=405667&hilit=tunnel#p405667 source])

* '''id''' identifier for the tunnel, to allow removing (optional).
* '''remove''': (boolean) yes/no value. If yes, removes all defined tunnels with the same ID (then only id= is necessary). (default: no)
* '''bidirectional''': (boolean) if yes, creates also a tunnel in the other direction. (default: yes)
* '''always_visible''': (boolean) if yes, the possible movement of enemies under fog can be seen. (default: no)
* '''[source]''': [[StandardLocationFilter]] the source hex(es) (required).
* '''[target]''': [[StandardLocationFilter]] the target hex(es) (required).
* '''[filter]''': [[StandardUnitFilter]] the units which can use the tunnel (required). Leave empty for "all units".

(Note: The tunnel tag can also be used inside the [[AbilitiesWML|[teleport]]] ability, without remove= and id=).

=== [do_command] ===

{{DevFeature1.13|0}}

Executes a command, specified using the same syntax as a [command] tag in [[ReplayWML]]. Not all [command]'s are valid: only these are accepted

* [attack]
* [move]
* [recruit]
* [recall]
* [disband]
* [fire_event]
* [lua_ai]

The tags corresponding to player actions generally use the same codepath as if a player had ordered it.

One purpose of this tag is to allow scripting of noninteractive scenarios -- without a tag like this, this might require elaborate mechanisms to coerce ais in order to test these code paths.

This command should always be replay safe.

=== [put_to_recall_list] ===

{{DevFeature1.13|0}}

Puts a unit to the recall list of its side.
* '''[[StandardUnitFilter]]''': the unit(s) to get put to the recall list.
* '''heal''': (default=no) Whether the unit should be refreshed, similar to the unit moving to the recall list at the end of a scenario.

== Useful Macros ==
There are some predefined macros that you find useful for direct actions. You can find a complete list along with a detailed explanation of how they work [http://www.wesnoth.org/macro-reference.xhtml here].
* '''{MOVE_UNIT}''': Moves a unit to another location in the map and the player sees the movement (unlike [teleport])
* '''{FULL_HEAL}''': Brings a unit to full HP
* '''{LOYAL_UNIT}''': Create a loyal unit
* '''{MODIFY_TERRAIN_MASK}''': Modify an area of terrain

== See Also ==

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

[[Category: WML Reference]]
[[Category: ActionsWML]]

SideWML

2015-04-19T16:52:27Z

Trewe: /* the [side] tag */

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

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

The following keys are recognized:

* '''side''': a number. The leader of this side is placed on the tile represented by this number (see [[BuildingMaps]]). When defining sides, they must be defined in order since the side number is checked against the number of sides seen so far. Currently, the Multiplayer server rejects entering a scenario with more than 9 sides, even if those extra sides are AI sides.

* '''controller''': how moves for this side should be inputted.
** '''ai''': the Wesnoth AI makes this side's moves. This is the default setting.
** '''human''': a player controls this side's moves.
** '''null''': the side doesn't get a turn to move and doesn't have a leader generated from the contents of the [side] tag. (It still can get units from [unit] tags in the [side] tag.) Events that would usually occur on the side's turn will not take place. This includes healing (ability, villages and rest) and ''side turn'' events.
** '''a number''': gives this side's control to a side with '''side''' matching the number (multiplayer only).

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

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

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

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

* '''hidden''': if 'yes', side is not shown in status table.

* '''fog''': if 'yes', this side cannot see any tiles it is not within vision of, except at the start. Please note that the AI currently ignores the fog.

* '''fog_data''': describes the area which this team has de-fogged, using the same format as shroud_data. (This is not particularly useful when defining a side, though, as the game will recalculate fog as turns begin and end.) It is used in saved games.

* '''[fog_override]''' With keys x= and y=, this records the hexes that have been cleared (multiturn) with {{tag|DirectActionsWML|lift_fog}}.

* '''shroud''': if 'yes', this side cannot see any tiles it has not moved within sight of. Please note that the AI currently ignores the shroud. NOTE: with shroud=no, this team *ignores* shroud, so it is not possible to modify it using place_shroud and remove_shroud tags. If you want to do so, use "shroud=yes" and place_shroud/remove_shroud tags.

* '''shroud_data''': describes the area which this team has de-shrouded. An example:
|
|00011111000
:This would leave the first column on the map unaltered and would change the second column for 11 tiles. A '0' means: shrouded, '1' means unshrouded. You can either call an external file using {@filename} (see [[PreprocessorRef]]) or place the data in quotes. For making an external file see [[BuildingScenariosShroudData]].

* '''persistent''': whether the side exists in any other scenarios. If ''yes'', then ''save_id'' (see below) is used to identify the side in other scenarios. Defaults to ''yes'' for sides with a human controller, and ''no'' for ai controlled sides.

* '''save_id''': defaults to the leader's ''id'' if available, 'Unknown' otherwise. The ID of the side with respect to the previous and next scenarios. Used to carry over the side's recall list (including the side's leader), recruitment list, and starting gold from scenario to scenario. Also used for the side's displayed name in the victory gold-calculation dialog.

* '''team_name''': a non translatable string representing the team's description. Sides with the same team_name are allied. Default ''side''. ''team_name'' is now a comma-separated list of teams that the side is on.

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

* '''current_player''': a translatable string representing the player's or leader's name. Defaults to the leader's id; if the side's leader is a human player in multiplayer, the default is the player's username.

* '''color''': May be either a numeric color index or a color name (e.g. 'blue', 'purple', 'orange', etc.). The numeric form is deprecated. The default list of numbers and corresponding colors can be found in data/core/team_colors.cfg.

* '''flag''': a custom flag animation to use instead of the default one to mark captured villages. An automatic side-coloring is applied.
** Example animation that has three frames and loops every 750ms: ''flag=misc/myflag-1.png:250,misc/myflag-2.png:250,misc/myflag-3.png:250''

* '''flag_icon''': a custom flag icon to indicate the side playing in the statusbar (a size of 24x16 is recommended). An automatic side-coloring is applied.

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

* '''village_support''': the number of unit levels this side is able to support (does not pay upkeep on) per village it controls. Default specified in ''village_support'', '''[game_config]''' ([[GameConfigWML]]).

* '''recall_cost''': the amount of gold it costs to recall a unit. Default specified in ''recall_cost'', '''[game_config]''' ([[GameConfigWML]]).

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

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

* '''scroll_to_leader''': optional. If 'no', scroll to the leader is not performed on the start of each turn. (default: yes)

* '''suppress_end_turn_confirmation''': If "yes", then the player will not be asked to confirm ending their turn even if they have not done anything. This is provided for some (probably few) user-made scenarios in which players often skip their turns. (default: no)

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

* '''[village]''' describes a village the side begins in control of.
** ''x'', ''y'' the location of the village. If the pair of coordinates is not a village or is duplicated in another [village] tag, behaviour is undefined. Recent game engine or wmllint should warn about these.

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

* '''[leader]''' same as [unit] except that canrecruit will default to yes and current position to the side starting location if not specified.

* '''defeat_condition''' Specifies when a side is considered ''defeated'' this is checked ''for all sides'', after every player action and at the beginning of every turn.
** '''no_leader_left''': (default) The side is considered defeated if it has no units with canrecruit=yes
** '''no_units_left''': The side is defeated as soon as it has no units left.
** '''never''': The side is never considered defeated.
** '''always''': The side is always considered defeated.

: For the meaning and significance of ''defeated'', see [[ScenarioWML#Scenario_End_Conditions]]

The following keys are multiplayer only:

* '''allow_player''': if false then this side will not be allowed to be modified and will be hidden during game creation. False also prevents this side from being included in shuffle sides. Defaults to yes.

* '''disallow_observers''': prevents observers from seeing this side turn. (default: no)

* '''disallow_shuffle''': {{DevFeature1.13|0}} do not shuffle this side if the "shuffle sides" option is used. (Usually all playable sides are shuffled.) (default: no)

* '''chose_random''': {{DevFeature1.13|0}} indicates if a side chose a random faction during creation

* '''controller_lock''': if true then this side's controller ("Player/Type") modification is limited. It is bound to the '''controller''' attribute in [[SideWML]].

* '''team_lock''': if true then this side's team is not allowed to be modified.

* '''color_lock''': if true then this side's color is not allowed to be modified.

* '''gold_lock''': if true then this side's gold is not allowed to be modified.

* '''income_lock''': if true then this side's income is not allowed to be modified.

* '''faction_lock''': if true then this side's faction is not allowed to be modified.

* '''leader_lock''': if true then this side's leader (type or gender) is not allowed to be modified.

* '''faction''': if valid faction id is provided then this side's faction will default to it.

* '''faction_from_recruit''': if true then this side will be locked to the faction that matches the recruits better.

N.B. the ''lock'' attributes use [[ScenarioWML]] '''force_lock_settings''' as their default value. I.e. if no value to ''lock'' was set, it will take '''force_lock_settings''' value.

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

[[Category: WML Reference]]

TranslatorShellscript

2014-11-17T21:48:57Z

Trewe: /* poEdits Wrath */ keep it simple

Feel free to post improvements as well. In which languages it does not work at all? What kind of shell script are needed as well?

== First of all ==
Prior to use the shell scripts, the po-File needs to be opened and saved with poEdit. The reason is, that then the texts are saved in separated lines without interfering /n's. As result, a normal entry consists of 4 lines, where one line contains the "characters text" and a prior line the "characters name". Without saving the file with poEdit, the number of text-lines would be undefined.

Or using msgcat (part of GNU gettext), save the file with the ''--no-wrap'' switch,
msgcat --no-wrap file1.po -o file2.po

== poEdits Wrath ==
Anyhow, those changes introduced by poEdit should be undone prior sending the new po-File to your language maintainer. Especially, it must be undone prior to "diff" the new version against the old one. This may be done by executing the following:
msgcat file.po -o file.po

Now, if you
diff -u SVN.file.po file.po > file.po.diff

Your "diff" will only contain your changes and will look much nicer - your language maintainer will like you even more :).
(see [[GettextForTranslators#FAQ]])

== Trailing Spaces ==

At the end of each translated "string", spaces should be avoided. Checking might be done using
::sed -n '/ "$/{N;s/\n$//p}' de.po
in a shell. (Checks whether there is a trailing space and the next line is empty.)

== Extracting a target language script ==

For proof-reading of a campaign it might be much easier to print it out in a more "scriptlike" format (<charactername>: <text>) (target language only), e.g. to read it in a bus, a train or in a car. Thanks to the programmer(s) that included the "speaker" in the comments of the po-files (Ivanovic?)! Those are definitely helpful and make this approach possible.

::>cat ./de.po | grep -v "msgid \"" | grep -v "#: data" | sed "s/\[message\]: speaker//g" | sed "s/#. =//g" | sed "s/msgstr/:/g" |grep -v ": \"\"" | sed ':;s/\n:/:/;N;T' | sed ':;s/\n\n/\n/;N;T'| sed "s/#. \[scenario\]/\n#. \[scenario\]/g" > target-language-script.txt

An even nicer extraction method without saving via poedit is the following :
::> sed -n 's/#\. $\[scenario\]: id=.\+$$/\n\n\1/p;s/#\. $\[part\]$$/\n\1/p;t msgid;s/#\. \[message\]: speaker=$.\+$$/\1/;t speaker;b;:speaker;H;n;s/#\. \[message\]: speaker=$.\+$$/, \1/;t speaker;x;s/$/:\t/;s/\n//g;x;t msgid;:msgid;s/msgid $".*"$/\1/;t nextmsgid;n;b msgid;:nextmsgid;H;n;/^".*"$/b nextmsgid;x;s/"\n"//g;s/\n//;;s/".*"//;x;s/msgstr $".*"$/\1/;:nextmsgstr;H;n;/^".*"$/b nextmsgstr;x;s/"\n"//g;s/\n//;s/$//;p' ./de.po > target-language-script.txt

(derived from the SED-command below- thanks to Soliton)

I load this text file into a editor to print it in two columns with the name of the "speaker" intended (like in script book).

== Extracting an English script ==

For proof-reading of a campaign it might be much easier to print it out in a more "scriptlike" format (<charactername>: <text>) (english only), e.g. to read it in a bus.
This one is even more preliminary than the one before. It still contains some target language parts.

::>cat de.po | grep -v "msgstr \"" | grep -v "#: data" | sed "s/\[message\]: speaker//g" | sed "s/#. =//g" | sed "s/msgid/:/g" |grep -v ": \"\"" | sed ':;s/\n:/:/;N;T' | sed ':;s/\n\n/\n/;N;T'| sed "s/#. \[scenario\]/\n#. \[scenario\]/g" > english.txt

== Extracting a script with original and translated strings ==

Similar as above. A sed script to extract dialog and story parts in the form:

:[scenario]: id=<id>
:<original title>
:<translated title>

:[part]
:<original story part>
:<translated story part>

:<speaker>: <original dialog>
:<speaker>: <translated dialog>

::one-line version:
::sed -n 's/#\. $\[scenario\]: id=.\+$$/\n\n\1/p;s/#\. $\[part\]$$/\n\1/p;t msgid;s/#\. \[message\]: speaker=$.\+$$/\1/;t speaker;b;:speaker;H;n;s/#\. \[message\]: speaker=$.\+$$/, \1/;t speaker;x;s/$/:\t/;s/\n//g;x;t msgid;:msgid;s/msgid $".*"$/\1/;t nextmsgid;n;b msgid;:nextmsgid;H;n;/^".*"$/b nextmsgid;x;s/"\n"//g;s/\n//;p;s/".*"//;x;s/msgstr $".*"$/\1/;:nextmsgstr;H;n;/^".*"$/b nextmsgstr;x;s/"\n"//g;s/\n//;s/$/\n/;p' de.po

It works on unmodified po files as well. (no re-saving in poedit necessary)

== Extracting a list of characters ==

Be aware, that you should be in the right directory. It contains *.cfg files for each campaign-scenario.

::cd <wesnoth-installpath>/data/campaigns/Northern_Rebirth/scenarios
::sed -n '/\[unit\]/,/\[\/unit\]/ba;/\[side\]/,/\[\/side\]/ba;b;:a s/^ *id *= *"\?$[^"]*$"\?/\1/p' *.cfg | sort | uniq -c | sort -nr > ~/NRcharacterlist.txt
(Looks for id= keys in [side] and [unit] tags and extracts the value then sorts them by number of occurrences.)

You can leave off the "-c | sort -nr" part if you don't care about the number of occurrences.

== Translating without knowing English? ==
(This was copied from the Wesnoth translation forum, a thread and an brilliant idea from [[User:Viliam]] http://www.wesnoth.org/forum/viewtopic.php?f=7&t=8817)

Have you found someone willing to translate Wesnoth to a language X (or willing to help you translating to your language), but then you found that the person does not speak English? This is no longer a problem!

My solution is a Perl script that will enrich your PO file with translations to other language(s), inserted as comments to the English phrases. When you work with "poEdit" application and click on the phrase, you will see translations in other language(s) in the comment window; so you can translate the phrase without a good knowledge of English, or you can have an advantage of using translation to language similar to your one.

You can immediately use the compiled MO files in game, because the PO file remains an "English to language X" translation. Only comments are changed, nothing else.

Examples:

I have a Slovak translation "sk.po", and would like to use a Czech translation as help:

multi_po.pl sk.po --add cs.po CS > sk_multi.po

In file "sk_multi.po" there is for every phrase added corresponding Czech translation from "cs.po" file, labeled as "CS". (My original comments in "sk.po" file are there, too.)

Before sending to translation maintainers, I remove unnecessary comments:

multi_po.pl sk_multi.po --remove > sk.po

The Czech translations are removed. (My original comments remained.)

It is possible to add more languages to one PO file. To use newer version of translation, you must remove the translations, and add them again. Your comments will remain (unless you use "{ ... }" as substring in them).

If someone finds this helpful, please report to me any bugs found. (That is... be careful and backup your PO files. This is a program written today, not much tested yet.)

http://www.wesnoth.org/forum/download/file.php?id=5872

== Style scripts following the typographic style guide ==
Here, I show possibilities using an UNIX-environment (Windows-user - check "cygwin" or similar for getting something like this). I like to use pipes ("|"), as you may easily put those commandos one after another as you need it for your purpose.

Those scripts only work on po-files re-saved with po-Edit, thus guaranteeing "single-line strings". The "single-line string" is important, as it is a simple way to separate the original from the translated string. Otherwise you will introduce changes in the original strings as well and subsequent patching your translation to the game might fail.

=== No double spaces ===
You should get rid of double (multiple) spaces in your translation strings:
cat de.po | sed '/msgstr/s/ \+/ /g' > de.po1

=== Ellipsis instead of three dots ===
Use only if this applies to your language - English does not yet implement it.
cat de.po | sed '/msgstr/s/\.\.\./…/g' > de.po1

Check all lines for "irregular leftovers" of multiple dots (as a line like "........" would leave)
cat de.po1 | grep 'msgstr' | grep '…\.'
gives you a list of those.

=== Dashes ===
This is kind of tricky as the sophisticated use of different dashes explained in [[Typography_Style_Guide#Dashes]] might not be used in all translations.

The following command line introduces the "long" em-dash in all cases that "involves spaces and minuses". This might be correct in most cases.
cat de.po | sed '/msgstr/s/ - / — /g;/msgstr/s/ -/ —/g;/msgstr/s/- /— /g' > de.po1

Again, check the changed lines on occurrences of "real minuses" or "concatenated words"
cat de.po1 | grep 'msgstr' | grep '—'
and reverse the "wrong dashes" back to "minus" using po-Edit.

=== Apostrophes ===
This command line exchanges all occurrences of the keyboard »'« with the curly one »’«. This might not be applicable for all languages depending on its use.
cat de.po | sed "/msgstr/s/'/’/g" > de.po1

=== Use of » or « for Quotes ===
If your language team decided on using » and « as quotation marks (instead of " or ' or similar) you may type >> and << in your po-file and the command line below changes it into the nice ones:
cat de.po | sed '/msgstr/s/>>/»/g;/msgstr/s/<</«/g' > de.po1

=== Fusing commands ===

Use the followoing style:
cat de.po | sedcommand1 | sedcommand2 | sedcommand3 > de.po1

e.g. changing apostrophes and quotes and ellipsis in one step and producing a new file called "de.po1":
cat de.po | sed "/msgstr/s/'/’/g" | sed '/msgstr/s/>>/»/g;/msgstr/s/<</«/g' | sed '/msgstr/s/\.\.\./…/g' > de.po1

Reminder: use msgattrib (see above) for reformatting the po-file prior using the "diff command".

== Comments ==

Disclaimer: This scripts are far away from "flawless". Anyhow, try it, like it, use it; dislike it, improve it :).

And, yes, I know, its programming (the ones I did) is pathetic :). And, yes, more knowledge about WML would definitely improve it. Or a higher frustration threshold... :). Or the accuracy, a real programmer would have. Hence, improvements might be a very good idea - If anybody has suggestions, feel free to contact me or just post it here. Or even realize them on a higher level - why not writing a script to transform it in TEX - per aspera ad astra :).

[[Category:Translations]]
[[Category:Tools]]

TranslatorShellscript

2014-11-17T21:47:33Z

Trewe: /* First of all */ No poedit needed

Feel free to post improvements as well. In which languages it does not work at all? What kind of shell script are needed as well?

== First of all ==
Prior to use the shell scripts, the po-File needs to be opened and saved with poEdit. The reason is, that then the texts are saved in separated lines without interfering /n's. As result, a normal entry consists of 4 lines, where one line contains the "characters text" and a prior line the "characters name". Without saving the file with poEdit, the number of text-lines would be undefined.

Or using msgcat (part of GNU gettext), save the file with the ''--no-wrap'' switch,
msgcat --no-wrap file1.po -o file2.po

== poEdits Wrath ==
Anyhow, those changes introduced by poEdit should be undone prior sending the new po-File to your language maintainer. Especially, it must be undone prior to "diff" the new version against the old one. This may be done by executing the following:
msgattrib file.po > file.po1
mv file.po1 file.po

Now, if you
diff -u SVN.file.po file.po > file.po.diff

Your "diff" will only contain your changes and will look much nicer - your language maintainer will like you even more :).
(see [[GettextForTranslators#FAQ]])

== Trailing Spaces ==

At the end of each translated "string", spaces should be avoided. Checking might be done using
::sed -n '/ "$/{N;s/\n$//p}' de.po
in a shell. (Checks whether there is a trailing space and the next line is empty.)

== Extracting a target language script ==

For proof-reading of a campaign it might be much easier to print it out in a more "scriptlike" format (<charactername>: <text>) (target language only), e.g. to read it in a bus, a train or in a car. Thanks to the programmer(s) that included the "speaker" in the comments of the po-files (Ivanovic?)! Those are definitely helpful and make this approach possible.

::>cat ./de.po | grep -v "msgid \"" | grep -v "#: data" | sed "s/\[message\]: speaker//g" | sed "s/#. =//g" | sed "s/msgstr/:/g" |grep -v ": \"\"" | sed ':;s/\n:/:/;N;T' | sed ':;s/\n\n/\n/;N;T'| sed "s/#. \[scenario\]/\n#. \[scenario\]/g" > target-language-script.txt

An even nicer extraction method without saving via poedit is the following :
::> sed -n 's/#\. $\[scenario\]: id=.\+$$/\n\n\1/p;s/#\. $\[part\]$$/\n\1/p;t msgid;s/#\. \[message\]: speaker=$.\+$$/\1/;t speaker;b;:speaker;H;n;s/#\. \[message\]: speaker=$.\+$$/, \1/;t speaker;x;s/$/:\t/;s/\n//g;x;t msgid;:msgid;s/msgid $".*"$/\1/;t nextmsgid;n;b msgid;:nextmsgid;H;n;/^".*"$/b nextmsgid;x;s/"\n"//g;s/\n//;;s/".*"//;x;s/msgstr $".*"$/\1/;:nextmsgstr;H;n;/^".*"$/b nextmsgstr;x;s/"\n"//g;s/\n//;s/$//;p' ./de.po > target-language-script.txt

(derived from the SED-command below- thanks to Soliton)

I load this text file into a editor to print it in two columns with the name of the "speaker" intended (like in script book).

== Extracting an English script ==

For proof-reading of a campaign it might be much easier to print it out in a more "scriptlike" format (<charactername>: <text>) (english only), e.g. to read it in a bus.
This one is even more preliminary than the one before. It still contains some target language parts.

::>cat de.po | grep -v "msgstr \"" | grep -v "#: data" | sed "s/\[message\]: speaker//g" | sed "s/#. =//g" | sed "s/msgid/:/g" |grep -v ": \"\"" | sed ':;s/\n:/:/;N;T' | sed ':;s/\n\n/\n/;N;T'| sed "s/#. \[scenario\]/\n#. \[scenario\]/g" > english.txt

== Extracting a script with original and translated strings ==

Similar as above. A sed script to extract dialog and story parts in the form:

:[scenario]: id=<id>
:<original title>
:<translated title>

:[part]
:<original story part>
:<translated story part>

:<speaker>: <original dialog>
:<speaker>: <translated dialog>

::one-line version:
::sed -n 's/#\. $\[scenario\]: id=.\+$$/\n\n\1/p;s/#\. $\[part\]$$/\n\1/p;t msgid;s/#\. \[message\]: speaker=$.\+$$/\1/;t speaker;b;:speaker;H;n;s/#\. \[message\]: speaker=$.\+$$/, \1/;t speaker;x;s/$/:\t/;s/\n//g;x;t msgid;:msgid;s/msgid $".*"$/\1/;t nextmsgid;n;b msgid;:nextmsgid;H;n;/^".*"$/b nextmsgid;x;s/"\n"//g;s/\n//;p;s/".*"//;x;s/msgstr $".*"$/\1/;:nextmsgstr;H;n;/^".*"$/b nextmsgstr;x;s/"\n"//g;s/\n//;s/$/\n/;p' de.po

It works on unmodified po files as well. (no re-saving in poedit necessary)

== Extracting a list of characters ==

Be aware, that you should be in the right directory. It contains *.cfg files for each campaign-scenario.

::cd <wesnoth-installpath>/data/campaigns/Northern_Rebirth/scenarios
::sed -n '/\[unit\]/,/\[\/unit\]/ba;/\[side\]/,/\[\/side\]/ba;b;:a s/^ *id *= *"\?$[^"]*$"\?/\1/p' *.cfg | sort | uniq -c | sort -nr > ~/NRcharacterlist.txt
(Looks for id= keys in [side] and [unit] tags and extracts the value then sorts them by number of occurrences.)

You can leave off the "-c | sort -nr" part if you don't care about the number of occurrences.

== Translating without knowing English? ==
(This was copied from the Wesnoth translation forum, a thread and an brilliant idea from [[User:Viliam]] http://www.wesnoth.org/forum/viewtopic.php?f=7&t=8817)

Have you found someone willing to translate Wesnoth to a language X (or willing to help you translating to your language), but then you found that the person does not speak English? This is no longer a problem!

My solution is a Perl script that will enrich your PO file with translations to other language(s), inserted as comments to the English phrases. When you work with "poEdit" application and click on the phrase, you will see translations in other language(s) in the comment window; so you can translate the phrase without a good knowledge of English, or you can have an advantage of using translation to language similar to your one.

You can immediately use the compiled MO files in game, because the PO file remains an "English to language X" translation. Only comments are changed, nothing else.

Examples:

I have a Slovak translation "sk.po", and would like to use a Czech translation as help:

multi_po.pl sk.po --add cs.po CS > sk_multi.po

In file "sk_multi.po" there is for every phrase added corresponding Czech translation from "cs.po" file, labeled as "CS". (My original comments in "sk.po" file are there, too.)

Before sending to translation maintainers, I remove unnecessary comments:

multi_po.pl sk_multi.po --remove > sk.po

The Czech translations are removed. (My original comments remained.)

It is possible to add more languages to one PO file. To use newer version of translation, you must remove the translations, and add them again. Your comments will remain (unless you use "{ ... }" as substring in them).

If someone finds this helpful, please report to me any bugs found. (That is... be careful and backup your PO files. This is a program written today, not much tested yet.)

http://www.wesnoth.org/forum/download/file.php?id=5872

== Style scripts following the typographic style guide ==
Here, I show possibilities using an UNIX-environment (Windows-user - check "cygwin" or similar for getting something like this). I like to use pipes ("|"), as you may easily put those commandos one after another as you need it for your purpose.

Those scripts only work on po-files re-saved with po-Edit, thus guaranteeing "single-line strings". The "single-line string" is important, as it is a simple way to separate the original from the translated string. Otherwise you will introduce changes in the original strings as well and subsequent patching your translation to the game might fail.

=== No double spaces ===
You should get rid of double (multiple) spaces in your translation strings:
cat de.po | sed '/msgstr/s/ \+/ /g' > de.po1

=== Ellipsis instead of three dots ===
Use only if this applies to your language - English does not yet implement it.
cat de.po | sed '/msgstr/s/\.\.\./…/g' > de.po1

Check all lines for "irregular leftovers" of multiple dots (as a line like "........" would leave)
cat de.po1 | grep 'msgstr' | grep '…\.'
gives you a list of those.

=== Dashes ===
This is kind of tricky as the sophisticated use of different dashes explained in [[Typography_Style_Guide#Dashes]] might not be used in all translations.

The following command line introduces the "long" em-dash in all cases that "involves spaces and minuses". This might be correct in most cases.
cat de.po | sed '/msgstr/s/ - / — /g;/msgstr/s/ -/ —/g;/msgstr/s/- /— /g' > de.po1

Again, check the changed lines on occurrences of "real minuses" or "concatenated words"
cat de.po1 | grep 'msgstr' | grep '—'
and reverse the "wrong dashes" back to "minus" using po-Edit.

=== Apostrophes ===
This command line exchanges all occurrences of the keyboard »'« with the curly one »’«. This might not be applicable for all languages depending on its use.
cat de.po | sed "/msgstr/s/'/’/g" > de.po1

=== Use of » or « for Quotes ===
If your language team decided on using » and « as quotation marks (instead of " or ' or similar) you may type >> and << in your po-file and the command line below changes it into the nice ones:
cat de.po | sed '/msgstr/s/>>/»/g;/msgstr/s/<</«/g' > de.po1

=== Fusing commands ===

Use the followoing style:
cat de.po | sedcommand1 | sedcommand2 | sedcommand3 > de.po1

e.g. changing apostrophes and quotes and ellipsis in one step and producing a new file called "de.po1":
cat de.po | sed "/msgstr/s/'/’/g" | sed '/msgstr/s/>>/»/g;/msgstr/s/<</«/g' | sed '/msgstr/s/\.\.\./…/g' > de.po1

Reminder: use msgattrib (see above) for reformatting the po-file prior using the "diff command".

== Comments ==

Disclaimer: This scripts are far away from "flawless". Anyhow, try it, like it, use it; dislike it, improve it :).

And, yes, I know, its programming (the ones I did) is pathetic :). And, yes, more knowledge about WML would definitely improve it. Or a higher frustration threshold... :). Or the accuracy, a real programmer would have. Hence, improvements might be a very good idea - If anybody has suggestions, feel free to contact me or just post it here. Or even realize them on a higher level - why not writing a script to transform it in TEX - per aspera ad astra :).

[[Category:Translations]]
[[Category:Tools]]

Micro AIs

2014-11-17T20:50:39Z

Trewe: /* Zone guardian (ai_type=zone_guardian) */

Micro AIs allow Wesnoth campaign and scenario authors to add new AI functionality without the need for any AI programming. A Micro AI is activated and configured (or deleted) via the [micro_ai] tag, requiring only a few lines of WML code. Note that this is a new functionality and theat '''[http://forums.wesnoth.org/viewtopic.php?f=10&t=39456 we are very much looking for feedback]''' on bugs, new feature requests for the existing AIs or ideas for new Micro AIs.

Micro AIs are available in mainline Wesnoth '''starting from Version 1.11.2'''.

'''''This page only contains instructions for <u>Wesnoth 1.11.7 and later</u> any more.''''' See [[Micro_AIs#A_Few_General_Words_about_Micro_AIs|below]] for details.

== A Few General Words about Micro AIs ==

* '''''This page only contains instructions for <u>Wesnoth 1.11.7 and later</u> any more'''''
** The Micro AIs have gone through so many changes since their introduction in Wesnoth 1.11.2 that this page was becoming too cluttered with all the version history.
** If you are using an earlier Wesnoth version, check out this wiki page's history. Information about versions 1.11.2 - 1.11.6 was removed on 15 November 2013.
** If you are adapting Micro AI code from a version earlier than 1.11.7, in particular '''code containing the now removed RCA_STAGE macro''', the first step is to remove the entire [ai] tag from the [side] definition, as [[Micro_AIs#Setting_up_a_Micro_AI|only the [micro_ai] tag is required]] now with no need for an engine definition in the [side] tag.

* Micro AIs are meant to bring new specialized behavior to Wesnoth that cannot be achieved, at least not easily, by adjusting default AI parameters (such as those described at [[AiWML]]) or with WML code.

* The '''default AI aspects are, for the most part, not taken into account by the Micro AIs'''. For example, unless noted otherwise, specifying a value for 'aggression' does not change the MAI behavior, and locations specified in an '[avoid]' tag generally can be entered by units controlled by an MAI. This is a feature of the Micro AIs, not a bug. If you feel that a certain default AI aspect should also apply to a Micro AI, please let us know in the [http://forums.wesnoth.org/viewtopic.php?f=10&t=39456 Micro AIs Feedback thread].

* Most Micro AIs in their default setting apply to all units of a side, although many of them provide parameters for filtering the units that should be affected by the new behavior. If the Micro AI is applied only to part of the units of a side, the other units follow the default Wesnoth AI behavior.

=== Micro AI Test and Demo Scenarios ===

All Micro AIs described here can be checked out in a number of test and demo scenarios. Test scenarios can be accessed from the command line by typing
path/wesnoth-executable -t micro_ai_test
This starts up a "switchboard scenario" in which you can select the Micro AI demonstration scenario you want to check out. Here, ''path/wesnoth-executable'' needs to be replaced by whatever the path and filename of the Wesnoth executable is on your system.

== Setting up a Micro AI ==

Setting up a Micro AI requires only one simple step:
==== 1. Activating and configuring (or deleting) a Micro AI ====

Micro AIs are activated, deleted and configured using the [micro_ai] tag. This tag needs to be placed in [[ActionWML]], that is, in an event, a menu option or the like. As an example, the following code activates the healer_support Micro AI in its default configuration for Side 2 from the beginning of the scenario:
[event]
name=prestart

# Configure the healer support micro AI
[micro_ai]
side=2
ai_type=healer_support
action=add
[/micro_ai]
[/event]
'''Keys required for all Micro AIs:'''
All [micro_ai] tags must contain the following three required keys:
* '''side''': The side for which the Micro AI is to be added, changed or deleted. This has to be an individual side number, lists of sides are not supported.
* '''ai_type''': The type of Micro AI to be added, changed or deleted. See the following sections for allowed values.
* '''action''' (string): The action to take concerning the Micro AI. The following values are allowed:
** ''add'': Add a Micro AI to a side.
** ''change'': Change the configuration of an existing Micro AI. Note that this does not only change the specific parameters provided in the tag, but it replaces the entire existing Micro AI by a new version with the new (and only the new) configuration. It is therefore equivalent to using first the ''delete'' and then the ''add'' action.
** ''delete'': Delete an existing Micro AI from a side.

'''Keys required under certain circumstances:'''
* '''ca_id''': (string) If several MAIs of the same type are used for the same side and one or several of these are to be changed or deleted during a scenario, this key needs to be included so that the [micro_ai] tag knows which of them needs to be changed/deleted. Notes:
** The id(s)/name(s) actually assigned to the CA(s) of the MAI by the engine might be different from the parameter passed here. It is, however, sufficient to use this ca_id with the [micro_ai] tag add/delete/change actions to identify the MAI uniquely. (In other words: you don't have to worry about this if you always use the [micro_ai] tag, but might have to figure out the actual name(s) of the CA(s) if you want to delete or change them manually.)
* Other keys may also be required depending on the Micro AI. In additional, a number of optional keys may be available to configure the AI behavior. See the sections on the individual Micro AIs for details.

'''Required keys for deleting a Micro AI:'''

Only a subset of the keys required for setting up a Micro AI are needed when deleting it. '''side''', '''ai_type''' and '''action'''=delete always need to be provided. '''ca_id''' needs to be given if it was provided when setting up the Micro AI.

'''Notes:'''
* The ''add'' and ''change'' actions ignore all keys that do not apply to the respective Micro AI type. The ''delete'' action ignores all keys other than the required keys listed above.

* Some of the Micro AIs use and/or modify default AI components (candidate actions or aspects) when they are added, or reset these components to their default values when they are deleted. Thus, if you have modified the AI yourself using the default CAs or aspects, some of these modifications might be affected, or might be interfering with the Micro AI. The sections below indicate whether a Micro AI modifies any default AI components.

===Combining Different Micro AI Types for the Same Side===

No extra steps need to be taken when combining different Micro AIs on the same side. Simply set up the [micro_ai] tags for all AIs you want to use.

'''Notes:'''
* While it is ''technically'' possible to combine any number of Micro AIs, this does not mean that all Micro AIs work together in practice. Some are not compatible because they control units in contradictory ways.
* Not all combinations that ''should'' work have been tested yet. If you find a combination that you believe should work but doesn't, [http://forums.wesnoth.org/viewtopic.php?f=10&t=39456 please let us know] and we will see if that can be fixed.
* The candidate action score almost certainly has to be set (using the ca_score= key) for one or several of the MAIs if several of them are used on the same side.

== Animals Micro AIs ==
=== General Comments on the Animal Micro AIs ===

The Animals Micro AIs are meant to simulate the behaviors of certain types of animals. They are, however, set up so that they can be used with arbitrary unit types and might be applicable in quite diverse situations. The AIs nevertheless remain named after the animals for which they were written originally, so that they are (to some extent) descriptive of their behavior.

Brief descriptions of the AI behaviors are given in the following subsections. To get a better feeling for their behavior, check out the "Animals", "Swarm", "Wolves" and "Dragon" scenarios from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]. Note that some of the animal AIs are designed for animal types that do not exist in mainline. In the test scenario, other animal types are therefore substituted for them.

=== Animals AI: Wolves (ai_type=wolves) ===

The Wolves Micro AI organizes all "wolf" units (predators) of the side to hunt in a single pack. They actively chase after the closest prey and try to corner it (not always super successfully), but are easily distracted by other enemy units coming into attack range, to the point where the pack might split up. The wolves can, however, be told to attack only prey units as well as to try to avoid other types of units (such as larger predators). When no prey is left, the wolves wander randomly.

This AI works best for a small number of predators (2 - 5) and sparse prey. Also, the predators should be put on the map in a pack, that is, reasonably close to each other. For a demonstration of the Wolves AI behavior, check out the "Animals" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Note that another wolves AI exists, called [[Micro_AIs#Animals_AI:_Multi-pack_Wolves_.28ai_type.3Dwolves_multipacks.29|Multipack Wolves]], which distributes the wolves of a side into several packs, rather than all of them into one single pack as it is done here.

Enable the Wolves Micro AI by using
ai_type=wolves
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

* '''[filter]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting the predator units. The filter automatically includes the side= key set to the AI side.
* '''[filter_second]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting the prey units. The filter automatically includes a [[StandardSideFilter|Standard Side Filter]] set to all enemies of the AI side.

'''Optional keys:'''

* '''attack_only_prey'''=no: In the default configuration, the wolves attack all enemy units in attack range. If this key is set to 'yes', they only attack prey units.
* '''avoid_type''': Comma-separated list of unit types (on enemy sides) which the wolves try to avoid. They try to stay out of these units' way as much as possible when moving around (except when they are moving in to attack another enemy unit) and never attack them.
* '''ca_score'''=90000: (non-negative integer) The evaluation score of the candidate actions controlling this Micro AI. By default, it is set to 90,000, which is lower than the default combat CA, but higher than most other default CAs which move units. It can be changed by setting this parameter but in most cases this will not make sense. Note that the Wolves AI consists of 2 CAs with scores ranging from <tt>ca_score-1</tt> to <tt>ca_score</tt>.

'''Note:''' Depending on the parameters chosen, the Wolves Micro AI might modify the [[AiWML#Filtering_Combat_with_the_.27attacks.27_Aspect|attacks aspect]].

Here's an example of a wolves [micro_ai] tag usage from the "Animals" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=6
ai_type=wolves
action=add

[filter]
type=Wolf
[/filter]
[filter_second]
type=Vampire Bat
[/filter_second]
avoid_type=Yeti,Giant Spider,Ghast,Footpad
[/micro_ai]

=== Animals AI: Multi-pack Wolves (ai_type=wolves_multipacks) ===

The Multi-pack Wolves Micro AI is different from the [[Micro_AIs#Animals_AI:_Wolves_.28ai_type.3Dwolves.29|Wolves Micro AI]] in that there can be an arbitrary number of wolf packs, with the pack size being a free parameter. At the beginning of the scenario, close wolves are grouped into packs in a semi-methodical way. If the wolves are put on the map in distinct groups of close wolves of the correct number, they will be joined into packs matching these groups. If, on the other hand, they are spread out all over the map, the method of assigning them to packs is semi-random.

Wolves of the same pack begin by joining each other on the map. After that, they stay together until only one wolf is left, which then tries to join up with an incomplete pack or with other single wolves. Individual wolves entering the map during the scenario behave in that way as well.

A second difference to the other Wolves AI is that wolves do not actively hunt here. For the most part they just wander (often long distance). However, the pack ferociously (and without regard for its own health) attacks any enemy units that come into range, as long as that does not mean separating the pack by more than a few hexes. Staying together, or joining with a new wolf assigned to the pack, is the only thing that takes priority over satisfying the wolves' thirst for blood.

For a demonstration of the Multi-pack Wolves AI behavior, check out the "Wolves" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Multi-pack Wolves Micro AI by using
ai_type=wolves_multipacks
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

There are no required keys

'''Optional keys:'''

* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate actions controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs. Note that the Multi-pack Wolves AI consists of 2 CAs with scores ranging from <tt>ca_score-1</tt> to <tt>ca_score</tt>.
* '''pack_size'''=3: (integer) The size of the packs.
* '''show_pack_number'''=no: If set to "yes", the wolves' pack numbers will be shown below them. Note that this means that the pack number of a wolf killed in an attack will remain as a label on the map.
* '''type'''=Wolf: Comma-separated list of the unit types which the AI controls. The default value is "Wolf".

Here's an example of a wolves_multipacks [micro_ai] tag usage from the "Wolves" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=wolves_multipacks
action=add

show_pack_number=yes
pack_size=4
[/micro_ai]

=== Animals AI: Big Animals (ai_type=big_animals) ===

The Big Animals Micro AI is a simulation of large predators that wander and hunt alone, such as Bears, Giant Spiders or Yetis. For the most part, these just wander on the terrain that's been defined for them, but they attack enemy units if those happen to come into range. The AI can be set up so that the Big Animals stay out of the way of other units (such as other large predators), in which case they only attack those if cornered.

For a demonstration of the Big Animals AI behavior, check out the "Animals" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Big Animals Micro AI by using
ai_type=big_animals
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

* '''[filter]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting the animals to which this AI is applied. The filter automatically includes the side= key set to the AI side.

'''Optional keys:'''

* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs.
* '''[filter_location]''': The big animals often go for long distance (multi-turn) journeys. This tag is a [[StandardLocationFilter|Standard Location Filter]] describing the terrain from which the next goal is chosen. The default is all terrain on the map.
* '''[filter_location_wander]''': The terrain on which the big animals will end their moves. This is a [[StandardLocationFilter|Standard Location Filter]]. The default is all terrain on the map.
* '''[avoid_unit]''': A [[StandardUnitFilter|Standard Unit Filter]] describing all enemy units that the big animals will avoid. The filter automatically includes a [[StandardSideFilter|Standard Side Filter]] set to all enemies of the AI side.

Here's an example of big_animals [micro_ai] tag usage from the "Animals" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=3
ai_type=big_animals
action=add

[filter]
type=Ghast
[/filter]
[avoid_unit]
type=Yeti,Giant Spider,Ghast,Footpad
[/avoid_unit]
[filter_location]
x,y=1-40,1-18
[/filter_location]
[/micro_ai]

=== Animals AI: Forest Animals (ai_type=forest_animals) ===

The Forest Animals Micro AI simulates a number of different animal behaviors that one might find in a forest, namely animals behaving like deer, rabbits and families of tuskers. In the following, we will refer to those animals by these types, even though the actual unit types can be selected freely. They behave as follows:
* Each deer wanders randomly on (selectable) terrain, except when enemies get in its (the deer's) maximum movement range, in which case it flees to the farthest point it can reach.
* Tuskers exhibit the same behavior as deer, except when an enemy is next to one of the tusklets. This enemy is attacked unconditionally by the tuskers trying to protect their young.
* Tusklets blindly follow the closest adult tusker, except when there is no tusker left, in which case they behave the same as deer.
* Rabbits also wander randomly, but in addition disappear into their holes (if any are within reach) when enemies are close. They reappear out of their holes at the beginning of the turn, if it is safe.

For a demonstration of the Forest Animals AI behavior, check out the "Animals" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Forest Animals Micro AI by using
ai_type=forest_animals
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

There are no required keys

'''Optional keys:'''

* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate actions controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs. Note that the Forest Animals AI consists of 4 CAs with scores ranging from <tt>ca_score-3</tt> to <tt>ca_score</tt>.
* '''rabbit_type, tusker_type, tusklet_type, deer_type''': Comma-separated lists of the unit types behaving as the respective animals. If any of these parameters are not set, those types of animal behavior are skipped by the AI.
* '''[filter_location]''': A [[StandardLocationFilter|Standard Location Filter]] describing the terrain on which the forest animals wander when they are not threatened by enemies.
* '''rabbit_number'''=6: (integer) The number of rabbits for the AI to have on the map simultaneously. The AI puts the missing number of rabbits onto the map at the beginning of the AI's turn (when the rabbits come out of their holes).
* '''rabbit_enemy_distance'''=3: (number) Rabbits won't spawn in holes that aren't more than this distance away from all enemies.
* '''rabbit_hole_img''': Rabbit holes are marked by items on the map. If this parameter is set, it must be the file name of the item image. If it is not set, all items on the map are treated as rabbit holes.

Here's an example of forest_animals [micro_ai] tag usage from the "Animals" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=forest_animals
action=add

deer_type=Vampire Bat
rabbit_type=Giant Rat
tusker_type=Ogre
tusklet_type=Young Ogre
[filter_location]
terrain=*^F*
[/filter_location]
[/micro_ai]

=== Animals AI: Herd and Herders (ai_type=herding) ===

The Herding Micro AI sets up an area on the map where a number of herder units (such as sheep dog) control and protect a herd (such as sheep). For convenience, we simply refer to them as sheep dogs and sheep in the following, even though arbitrary unit types can be selected for either.

Sheep dogs try to keep their sheep safe. This involves keeping them inside the herding area, positioning themselves in between the sheep and approaching enemies, and attacking the enemies if those get too close. If no active herding or protecting move is needed, the dogs go to a random location on the perimeter of the herding area.

Sheep wander aimlessly except when a sheep dog is next to them, in which case they run away from the dog. The dogs exploit this by positioning themselves on the outside of the sheep, if possible. Sheep also run away from approaching enemies.

For a demonstration of the Herding AI behavior, check out the "Animals" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Herding Micro AI by using
ai_type=herding
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

* '''[filter]''': A [[StandardUnitFilter|Standard Unit Filter]] describing the herder units (e.g. dogs). The filter automatically includes the side= key set to the AI side.
* '''[filter_second]''': A [[StandardUnitFilter|Standard Unit Filter]] describing the herd units (e.g. sheep). The filter automatically includes the side= key set to the AI side.
* '''[filter_location]''': A [[StandardLocationFilter|Standard Location Filter]] describing the terrain forming the perimeter of the herding area. In other words, this is the path the herders (dogs) use to patrol around the outside of the herding area. This must be a set of coordinates ''completely enclosing'' the herding area. Here's an example of setting up a rectangular perimeter:
[filter_location]
x=10-20,10-20,10, ,20
y=11, 21, 11-21,11-21
[/filter_location]
Another possibility is by defining the path by certain terrain on the map (as it is done in the "Animals" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]), in which case the filter can simply look like this:
[filter_location]
terrain=Rb
[/filter_location]
* '''herd_x,herd_y''': The coordinate of one hex (''any'' one hex) inside the herding area. This is needed to define which part of the map is on the ''inside'' of the herding area perimeter defined by [herding_perimeter], and which is the ''outside''.

'''Optional keys:'''
* '''attention_distance'''=8: (integer) If an enemy is within this distance of a herd unit, but not as close as ''attack_distance'', the herders try to position themselves in between the enemy and the herd unit.
* '''attack_distance'''=4: (integer) If an enemy is within this distance of a herd animal, the herders attack this enemy.
* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate actions controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs. Note that the Herding AI consists of 6 CAs with scores ranging from <tt>ca_score-5</tt> to <tt>ca_score</tt>.

Here's an example of a Herding [micro_ai] tag usage from the "Animals" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=7
ai_type=herding
action=add

[filter]
type=Footpad
[/filter]
[filter_second]
type=Troll Whelp
[/filter_second]
herd_x,herd_y=32,28
[filter_location]
terrain=Rb
[/filter_location]
[/micro_ai]

=== Animals AI: Hunter (ai_type=hunter) ===

The Hunter Micro AI leads a unit (or units) through hunt-and-rest cycles. The units wander in a prescribed area of the map, their hunting ground, until an enemy unit comes within range. Note that the units do not actively chase down enemies, but wander randomly through the hunting ground until an enemy is encountered.

If enemies are within range of a hunter unit, the hunter attacks the weakest of them. If a kill is made, it then retreats to its rest location, where it stays for a certain number of turns and until fully healed (whatever happens later).

A few more details:
* If the hunter's way home is entirely blocked on the return (so that there is no possible path), the normal RCA AI takes over its behavior.
* However, if the way is blocked by an enemy unit occupying the rest hex, that enemy will be attacked unconditionally.
* A kill only makes the hunter go home when it is the attacker, not as defender.

For a demonstration of the Hunter AI behavior, check out the "Dragon" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Hunter Micro AI by using
ai_type=hunter
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

* '''id''' or '''[filter]''': The ID of a unit or a [[StandardUnitFilter|Standard Unit Filter]] selecting the units controlled by this Micro AI.
** One or the other is required
** If both are given, [filter] takes priority over id=
** The AI contains an implicit filter for units on the AI side. Thus, if all AI units are to be selected, an empty [filter] tag can be used.
** If several units match the filter, the order in which they are controlled is not guaranteed. If the order matters, set up several MAIs using the id= key and different values for ca_score=.
* '''home_x,home_y''': The coordinates of the hex to which the hunter returns and rests at after a kill.

'''Optional keys:'''

* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs.
* '''[filter_location]''': A [[StandardLocationFilter|Standard Location Filter]] describing the unit's hunting ground. If this tag is not provided, the hunter uses all of the map.
* '''rest_turns'''=3: (integer) The number of turns the AI stays at home_x,home_y after a kill. It will not leave its home until this number of turns have passed ''and'' it is fully healed.
* '''show_messages'''=no: (boolean) If set to yes, the hunter announces whenever its behavior changes to the next phase. Note that this is meant as debug output for the scenario author. The messages are not translated and are not included in replays (and are only visible to the host in an MP game).

Here's an example of a hunter [micro_ai] tag usage from the "Dragon" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=1
ai_type=hunter
action=add

id=Rowck
[filter_location]
x,y=5-30,1-15
[/filter_location]
home_x,home_y=3,15
rest_turns=2

show_messages=yes
[/micro_ai]

=== Animals AI: Swarm (ai_type=swarm) ===

The Swarm Micro AI uses some very simply algorithms to simulate animal swarm behavior. Without adjacent enemies, they simply do a random move, trying to stay together and at a certain distance from enemies. However, if an enemy unit is close to any bat, the swarm scatters. This is particular fun to watch when one places an enemy unit in the middle of the swarm. After being scattered, the swarm members slowly rejoin, but not in a very organized way. Sub-swarms or individual bats might roam around for quite some time before they find their way back. It is also possible that individual bats (or small groups) split off from the larger swarm at times.

For a demonstration of the Swarm AI behavior, check out the "Swarm" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Swarm Micro AI by using
ai_type=swarm
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

There are no required keys

'''Optional keys:'''

* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate actions controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs. Note that the Swarm AI consists of 2 CAs with scores ranging from <tt>ca_score-1</tt> to <tt>ca_score</tt>.
* '''enemy_distance'''=5: (int) The minimum distance kept between units of the swarm and enemies when the swarm moves as a whole.
* '''scatter_distance'''=3: (int) Enemies within "scatter_distance" hexes of any swarm unit cause the swarm to scatter, by each unit trying to maximize its individual distance from the enemy.
* '''vision_distance'''=12: (int) Only units within this distance follow the overall swarm motion (either away from an enemy or of the swarm as a whole). The smaller this value is set, the less likely the swarm is to stay together or rejoin. This parameter is meant to simulate how far an individual member of the swarm can see, meaning that the swarm is "out of sight" (and the unit will not be able to follow it) if it is more than this distance away.

Here's an example of a Swarm [micro_ai] tag usage from the "Swarm" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=swarm
action=add
[/micro_ai]

== Bottleneck Defense Micro AI (ai_type=bottleneck_defense) ==

The Bottleneck Defense Micro AI lets you define a location on the map where the AI can take a defensive stance behind a narrow passage (bottleneck). Units on the front line are backed up by healers and/or units with the leadership ability. Injured units are moved to the back and replaced by uninjured (or less injured) units. The units on the front line only attack when it is safe (no retaliation) or when there is a high chance that they will make a kill or level up. Using this Micro AI only makes sense if there is no way for the enemy sides to move around the bottleneck and attack the AI's units from behind.

For a demonstration, check out the "Bottleneck" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Bottleneck Defense Micro AI by using
ai_type=bottleneck_defense
in the [micro_ai] tag.

===Bottleneck Defense specific keys for the [micro_ai] tag:===

'''Required keys:'''

The Bottleneck Defense AI requires two sets of coordinates that define where it should be taking up its defensive stance, and from which side the enemy attacks at that location.

* '''x,y''': Comma separated lists of the hexes on the front line, where strong units are placed. All hexes on which the AI makes contact with (can be attacked by) the enemy need to be included here. Units are placed on them in the order in which they are listed here.
* '''enemy_x,enemy_y''': Comma separated list of the hexes from which the enemy can attack the AI front line units. This is needed for the AI to know on which side of the front line support units (healers etc.) need to be placed. In many cases, it is sufficient to provide only one of the enemy front line hexes, but there are geometries for which that does not work. It is therefore safer to list all enemy front line hexes here.

'''Optional keys:'''

By default, the AI places healers and units with the leadership ability both on the front line itself (if they are the strongest units available) and on hexes adjacent to and behind the line. If different placement is desired, these locations can be overridden with the following keys.

* '''active_side_leader'''=no: (boolean) If set to 'yes', the side leader participates in the bottleneck defense action after the side's gold has been spent. If set to 'no' (default), the leader follows default AI behavior (sitting on the keep and recruiting, for the most part).
* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate actions controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs. Note that the Bottleneck Defense AI consists of 2 CAs with scores ranging from <tt>ca_score-1</tt> to <tt>ca_score</tt>.
* '''healer_x,healer_y''': Comma separated list of hexes where healers are placed. This can be used to keep healers from the front line (or to take up only certain positions on the front line), and/or to override the default healing positions behind the line. Healers are placed on them in the order in which the hexes are listed, with the exception that hexes on the line always take priority over hexes behind the line.
* '''leadership_x,leadership_y''': Same as ''healer_x,healer_y'', but for units with the leadership ability.

As an example, in the "Bottleneck" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]], there are three front line hexes, two of which are on hill terrain, while the third is a road with a lower defense rating. The healer and side leader are supposed to participate in combat because they are strong units, but only from the hill hexes to keep them safer. This is accomplished by using the following keys settings (check out the scenario to see which hex is which):
[micro_ai]
side=1
ai_type=bottleneck_defense
action=add

x=14,14,14
y= 7, 9, 8
enemy_x=13,13
enemy_y= 8, 9

healer_x=14,14,15,15
healer_y= 7, 9, 8, 9
leadership_x=14,14,15,15
leadership_y= 7, 9, 9 ,8
active_side_leader=yes
[/micro_ai]

== Fast Micro AI (ai_type=fast_ai) ==

{{DevFeature1.13|0}}

This AI is meant as a fall-back AI for scenarios where there are so many units that attacks and moves done by the default AI are slow with long delays before each move. It replaces the default combat and move-to-targets candidate actions (CAs). It should be obvious that in order to achieve the faster speed, compromises concerning the quality of the moves have to be made.

'''Combat candidate action:'''
* Attackers are considered individually one at a time. The best attack found for a unit is executed without checking whether a better attack by another unit might be possible.
* The default order in which attackers are considered is by decreasing hitpoints, starting with the strongest unit (in terms of HP). This can be modified with the optional keys below.
* By default, if weaker units block attack hexes for a stronger unit, they do not move out of the way (this is the same as for the default AI). If a hex becomes available after an attack (e.g. due to a weaker unit dying in the attack), all attacks that were possible ''before'' this happened are finished first. Only after that are attacks by the stronger unit reconsidered.
* If include_occupied_attack_hexes=yes is set, weaker units move out of the way for stronger units if possible. This can, however slow down the AI depending on the situation on the map. Use with caution.

'''Move-to-targets, villages and retreat candidate actions:'''
* The move-to-targets, villages and retreat candidate actions of the default AI are removed. Move-to-targets and villages are taken over by the Fast Micro AI, whereas retreat is simply not done.
* This CA moves units toward goals after attacks are done. Goals are unowned (if the AI side has a leader only) and enemy-owned villages and enemy leaders.
* For each goal, units are pre-sorted in order of the fewest moves needed to cover the ''distance'' toward the goal (that is, as if move cost on each hex toward the goal were 1). Units are then considered sequentially and if a unit can get there "efficiently", its move is executed without considering other units.
** A move is considered efficient if the move cost to get to the hex is not more than 'move_cost_factor' larger than the distance to the hex. 'move_cost_factor' is an optional key that defaults to 2. It can be set to values of 1.1 or larger (see below).
** If the move for the current unit is not found to be efficient, the AI considers the next unit instead. If no unit can do an efficient move toward the goal, the best (fastest) of the inefficient moves is selected instead.

* Village goals:
** Village goals are considered before enemy leader goals so that the AI preferentially chooses scouts (or otherwise fast units) for them.
** The number of units sent toward villages depends on the value of the default AI aspect village_value. It is set to village_value/4 times the number of units the AI has left to move. Thus, by default (village_value=1.0) the AI sends a quarter of its units toward villages, and the rest toward enemy leaders. This means that the meaningful range of values for village_value is 0..4.
** Only one unit is moved toward each village. This consideration also overrides the number of units to move toward villages defined by village_value, topping it at the number of unowned/enemy-owned villages on the map.
** Setting village_value=0 disables moving units toward villages altogether. That is, not only are no units chosen, but the village targeting phase of the AI is entirely disabled with no evaluation time used for it. Note that, unlike with the default AI, this also means that no villages within range of an AI unit are grabbed.
** The order in which villages are chosen as goals is some combination of them being close to the AI side's leader and being spread out over the map.

* Enemy leader goals:
** The order of enemy leaders goals is set according to their distance from the AI leader with the closest enemy leader being targeted first (if the AI has a leader, otherwise their order is random). One unit is sent toward each enemy leader in this order, after which the AI starts with the first enemy leader again. This is repeated until all units have moved.

* Guardians (units with ai_special=guardian set) are ignored by the fast move-to-targets CA.

'''Tips for speeding up/modifying the Fast Micro AI in specific scenarios:'''

A number of optional keys and default AI aspects can be used to modify the behavior of the Fast Micro AI. The MAI is set up so that it is a reasonable compromise between speed and quality of the moves in most situations. However, this might not be ideal for all scenarios here are some things that can be done to speed up the AI (or to get better behavior in some situations by doing the opposite):
* Use large values for the default AI aspect aggression. The largest delays before attacks happen (in some circumstances) when the Fast MAI has to consider lots of units with attacks left but decides not to attack with them. See below for a description of how aggression is used by the fast AI.
* Use large values of move_cost_factor (see above for description of what this does). If you want to emphasize units that can move across terrain easily (e.g. bats) to be chosen for village grabbing, you might want to use low values of move_cost_factor, but this might slow down the AI. The default value should work reasonably well in most standard situations, but modifying the value might work better on specific maps.
* Don't use dungeon_mode=yes unless absolutely necessary, even in most dungeon crawls. Test the AI without this setting first and only use it if it is the only way to solve the problem. Often, a minor tweak to the map will have the same effect, without the speed penalty.
* Use include_occupied_attack_hexes=yes with caution. It might (or might not) slow down the attack CA significantly, depending on the scenario.
* Set village_value=0, which makes the AI not consider villages as goals. This has not been found to make a large difference on the maps tested so far, but it might have an effect on maps with a very large number of villages.

'''Required keys:'''

There are no required keys.

'''Optional keys:'''

* '''dungeon_mode'''=no: (boolean) As much as possible, the Fast Micro AI works with distances between hexes rather than path finding. This works pretty well on open maps and even most dungeon crawls (and similar scenarios), but it might result in some units getting temporarily (and in rare cases permanently) stuck on maps with convoluted labyrinths. If that is the case, setting dungeon_mode=yes triggers more path finding that avoids such situations (but as a result is somewhat slower).
* '''include_occupied_attack_hexes'''=no: (boolean) If set to 'yes', the AI moves weaker units out of the way for a stronger attacker. This might lead to better attacks but is slower, so don't use if speed is essential.
* '''move_cost_factor'''=2: (number >= 1.1) The factor by which the move cost to a goal hex may be larger than the distance to the goal hex for a move to be considered "efficient". See description above. 1.1 is used if this is set to values smaller than 1.1. Smaller values might lead to better behavior, while larger values might speed up the AI.
* '''weak_units_first'''=no: (boolean) If set to 'yes', inverts the order in which units are considered by the combat CA. Attacks are then done in order of increasing hitpoints of the attackers.
* '''skip_combat_ca'''=no: (boolean) If set to 'yes', the fast combat CA is not used. The default AI's CA remains in place in this case.
* '''skip_move_ca'''=no: (boolean) If set to 'yes', the fast move-to-targets CA is not used. The default AI's retreat, villages and move-to-targets CAs remains in place in this case.

'''Standard RCA AI aspects respected by this Micro AI:'''
*'''aggression''': The [[AiWML#The_.5Bai.5D_Tag:_Defining_Aspects|default RCA AI aspect]] used to set how aggressive the AI should attack. It works in roughly the same way as the default AI aspect:
** The value of (1 - aggression) determines how much the AI values its own units compared to the enemy's units. Thus, aggression=0 means that attacks are only done if the AI expects to deal (roughly) the same amount of damage as it will receive. aggression=1 means that expected damage to the AI's units is not considered, only the expected damage to enemy units matters.
** Damage is calculated as a combination of hitpoints and chance to die, in "gold equivalent units".
** Unlike the default AI, aggression is set to 1 for values larger than 1. Allowed values are thus anything from -infinity to +infinity, although only -infinity to +1.0 make sense.
*'''village_value=1''': (number ranging from 0 to 4) The [[AiWML#The_.5Bai.5D_Tag:_Defining_Aspects|default RCA AI aspect]] used to define how much villages should be targeted by the move-to-targets CA. In the Fast MAI, this defines which fraction of the AI units are moved toward village goals (see above for details). If set to 0, villages are ignored as goals.

'''Notes:'''
* The CA evaluation scores of this AI are hard-coded to the same values as those of the respective [[AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29|default candidate actions]]. ca_score is therefore not a valid optional key.
* The fast Micro AI modifies (removes) the default combat, move-to-targets, villages and retreat candidate actions.

== Generalized Goto Micro AI (ai_type=goto) ==

The Goto Micro AI provides a highly configurable method of sending a unit (or units) to a location or set of locations. The units to be moved are defined using a [[StandardUnitFilter|Standard Unit Filter]] (SUF) [alternatively, all side units are used if the SUF is not provided), while the goto locations are given in a [[StandardLocationFilter|Standard Location Filter]] (SLF).

By default, each unit matching the SUF will move toward the closest goal (in terms of turns needed to get there) matching the SLF via the fastest route given the current situation on the map (locations of enemy units etc.), but this behavior can be influenced by the optional keys listed below. Note that this means that a unit's goal might change from one turn to the next depending on the situation on the map.

The behavior of the unit(s) once they reach their goal location(s) is configurable as well. By default, they will stay there until the Goto Micro AI is deleted or changed.

For demonstrations of several Goto Micro AI usages, check out the "Goto" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Goto Micro AI by using
ai_type=goto
in the [micro_ai] tag.

===Goto specific keys for the [micro_ai] tag:===

'''Required keys:'''

* '''[filter_location]''': A [[StandardLocationFilter|Standard Location Filter]] describing the possible goal locations for the move.

'''Optional keys:'''

* '''avoid_enemies''': (number>0) By default, units controlled by the Goto Micro AI will not take enemy units into account for route finding, other than the enemies' ZoCs. By contrast, if this key is set, they will try to avoid traversing hexes on which they can be attacked by enemies. The larger the value of ''avoid_enemies'', the more the units will try to stay out of the enemies' way. Notes:
** Units are willing to take a path that is 'avoid_enemies' movement points longer for each enemy unit that can be avoided by doing so for each hex along the path. As an example, if avoid_enemies=1 and the shortest path crosses 2 hexes that can be reached by 3 enemies each, the unit is willing to take a path that is up to 6 hexes longer instead. If avoid_enemies=10 in the same situation, the unit will take a path up to 60 hexes longer.
** Hexes adjacent to enemy units are always strongly avoided, independent of the value of avoid_enemies.
** avoid_enemies is ignored if 'use_straight_line=true' is set.
* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs.
* '''[filter]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting the units to be moved. Defaults to all units of the side if not defined. The filter automatically includes the side= key set to the AI side.
* '''ignore_enemy_at_goal'''=no and '''ignore_units'''=no: (boolean) In the default configuration, the Goto MAI does not move units if the path to all goal hexes is blocked by enemies. It is therefore possible to disable the Goto MAI by putting enemy units on all the goal hexes. That can be changed if either of these two keys is set to 'yes'.
** 'ignore_enemy_at_goal=yes' makes the AI choose its goals while disregarding any enemy units at the goal hexes. Even so, a stiff rating penalty is applied to goal hexes occupied by enemies, thus that unoccupied goal hexes are chosen unless all possible goals are occupied by enemies. Note that this setting ''only'' ignores enemy units at the goal hexes themselves. It is still possible to disable the AI by putting enemies all around the goals.
** 'ignore_units=yes' let's the AI ignore ''all'' enemy units when deciding which goal hex(es) to move toward.
** In both cases, enemies are only ignored for deciding which unit to move toward which goal hex. For the actual move itself, all enemies and their ZoCs are considered as usual.
** Both options only take effect if neither avoid_enemies nor use_straight_line is set to 'yes', as neither of these consider enemies as blockers.
* '''release_unit_at_goal'''=no: (boolean) By default, a unit that reaches a goal location will stay there until the Goto Micro AI is deleted or changed (or until the conditions specified in the [goto_goals] SLF change). If this parameter is set, a unit that has reached its goal will not be controlled by this Micro AI any more starting from the next turn.
* '''release_all_units_at_goal'''=no: (boolean) Same as ''release_unit_at_goal'', but this will deactivate the Goto Micro AI for all units once the first unit reaches a goal.
* '''unique_goals'''=no: (boolean) If set to 'yes', each unit will be sent to a different goal location. Note that the best goals are recalculated each turn, so a unit might choose a different goal this turn from what it was heading for during the previous turn if the situation on the map has changed. Also note that if there are more units than goal locations, the left over units will not be handled by the Goto MAI but follow default behavior instead.
* '''use_straight_line'''=no: (boolean) By default, units choose the route by which they will get to their goal locations in the smallest number of turns. If this parameter is set to 'yes', a straight line route (or something pretty close to it at least) will be chosen instead, irrespective of whether this leads into a dead end, whether it is blocked by enemies, etc.

'''Notes:'''
* Depending on the parameters used, the Goto Micro AI might require a lot of path finding to be done. Thus, while it is possible to set up this AI to move many units to many different locations, a usage like that might require quite a long calculation time.

===Goto Micro AI example usages:===

Here are several examples of goto [micro_ai] tag usages from the "Goto" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
* Send a unit toward a castle (similar to the RCA AI's Goto Candidate Action, but avoiding dead ends and areas ZoCed by enemies)
[micro_ai]
side=2
ai_type=goto
action=add
ca_id=messenger1

[filter]
id=messenger1
[/filter]
[filter_location]
x,y=6-7,2-4
terrain=C*
[/filter_location]
ca_score=210001
[/micro_ai]
* Send all units of the side toward the southern border of the map
[micro_ai]
side=8
ai_type=goto
action=add

[filter_location]
y=33
[/filter_location]
avoid_enemies=1
[/micro_ai]
* Send units to the four corners of the map (with each unit going to a different corner).
[micro_ai]
side=7
ai_type=goto
action=add

[filter_location]
x=1,1,44,44
y=1,33,1,33
[/filter_location]
unique_goals=yes
[/micro_ai]
* Set up a guardian unit that doesn't move while no enemy unit is within 8 hexes (ironically, the Goto Micro AI can be used to keep units in place, although using one of the Guardian Micro AIs might often be a better idea)
[micro_ai]
side=3
ai_type=goto
action=add

[filter]
id=guard1
[/filter]
[filter_location]
[filter]
id=guard1
[/filter]
[not]
[filter]
side=1
[/filter]
radius=8
[/not]
[/filter_location]
[/micro_ai]

== Guardian Micro AIs ==
=== General Comments on the Guardian Micro AIs ===

The Guardian Micro AIs can be used to set up different kind of guardian behaviors for a unit or a set of units. Four different types of guardians are available and are described below.

For a demonstration of several different guardian behaviors, check out the "Guardians" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

=== Return Guardian (ai_type=return_guardian)===

A 'return guardian' is a variation of the standard Wesnoth guardian. It has an assigned guard position (GP) to which it returns after attacks on approaching enemies:
* If at GP with no enemy in reach, do nothing.
* If at GP with an enemy in reach, attack (note that the attack is done by default AI, which might result in the guardian not attacking if the enemy is deemed too strong).
* If not at GP, return there, no matter whether an enemy is in reach or not.
* If enemies are blocking the way back to GP, do your best to move around them.
* If the guardian ends up next to an enemy on the way back, attack that enemy after the move.

Enable the Return Guardian Micro AI by using
ai_type=return_guardian
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

* '''id''' or '''[filter]''': The ID of a unit or a [[StandardUnitFilter|Standard Unit Filter]] selecting the units controlled by this Micro AI.
** One or the other is required
** If both are given, [filter] takes priority over id=
** The AI contains an implicit filter for units on the AI side. Thus, if all AI units are to be selected, an empty [filter] tag can be used.
** If several units match the filter, the order in which they are controlled is not guaranteed. If the order matters, set up several MAIs using the id= key and different values for ca_score=.
* '''return_x,return_y''': The coordinate of the hex the unit returns to after each attack

'''Optional keys:'''

* '''ca_score'''=10010: (non-negative integer) The evaluation score of the candidate actions controlling this Micro AI. This AI consist of 2 CAs, one with score <tt>ca_score</tt> the other with <tt>ca_score-20</tt>. The default value is set so that the first CA gets executed right before the default combat CA, and the other right after. It usually will not make sense to change this value, but it is possible to do so for custom applications.

Here's an example of a return guardian [micro_ai] tag usage from the "Guardians" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=return_guardian
action=add

id=return1
return_x,return_y=20,2
[/micro_ai]

===Stationed Guardian (ai_type=stationed_guardian) ===

A 'stationed guardian' is another variation of the standard Wesnoth guardian with a somewhat more complex behavior than that of the 'return guardian'. Two positions are defined for it, a 'station' and a 'guarded location', as well as a distance. The behavior is as follows:
* If no enemy is within 'distance' of the guard's current position, do nothing. This is independent of the guardian being at its station or not.
* Otherwise: If an enemy is within 'distance' of the guard, but not also within the same distance of the guarded location and the station (all of this simultaneously), move the guard in the direction of the station.
* Otherwise:
** Pick the enemy unit that is closest to the guarded location.
** If we can reach it, pick the adjacent hex with the highest defense rating and attack from there.
** If not in reach, move toward this unit.

Enable the Stationed Guardian Micro AI by using
ai_type=stationed_guardian
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

* '''id''' or '''[filter]''': The ID of a unit or a [[StandardUnitFilter|Standard Unit Filter]] selecting the units controlled by this Micro AI.
** One or the other is required
** If both are given, [filter] takes priority over id=
** The AI contains an implicit filter for units on the AI side. Thus, if all AI units are to be selected, an empty [filter] tag can be used.
** If several units match the filter, the order in which they are controlled is not guaranteed. If the order matters, set up several MAIs using the id= key and different values for ca_score=.
* '''distance''': The distance parameter as explained above
* '''station_x,station_y''': The x and y position of the hex that serves as the guardians station.
* '''guard_x, guard_y''': The x and y position of the guarded location. {{DevFeature1.13|0}} These are now optional keys, defaulting to station_x,station_y if not provided.

'''Optional keys:'''

* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs.

Here's an example of a stationed guardian [micro_ai] tag usage from the "Guardians" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=stationed_guardian
action=add

id=stationed1
distance=4
station_x,station_y=2,14
guard_x,guard_y=3,13
[/micro_ai]

=== Coward (ai_type=coward) ===

Cowards are units that, like guardians, sit around doing nothing until an enemy comes into range. Unlike guardians, however, they run away once enemies approach. Applications might be wild animals, unarmed civilians getting in the way of a battle, etc. The coward macro can be called with two optional locations, 'seek' and 'avoid':
* If neither is given, the coward retreats to the position farthest away from the approaching enemies.
* If 'seek' is given, it preferentially goes toward that location (but getting away from enemies takes priority).
* If 'avoid' is given, it in addition tries to avoid that location (with both maximizing distance from enemies and going toward 'seek' taking priority).
* Both 'seek' and 'avoid' may consist of only one coordinate ('x' or 'y'), in which case not a single hex, but a line of hexes is sought or avoided.

Enable the Coward Micro AI by using
ai_type=coward
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

* '''id''' or '''[filter]''': The ID of a unit or a [[StandardUnitFilter|Standard Unit Filter]] selecting the units controlled by this Micro AI.
** One or the other is required
** If both are given, [filter] takes priority over id=
** The AI contains an implicit filter for units on the AI side. Thus, if all AI units are to be selected, an empty [filter] tag can be used.
** If several units match the filter, the order in which they are controlled is not guaranteed. If the order matters, set up several MAIs using the id= key and different values for ca_score=.
* '''distance''': The distance within which an enemy must be to "scare" the unit

'''Optional keys:'''

* '''attack_if_trapped'''='no': {{DevFeature1.13|0}} With the default settings, a coward never attacks. If this key is set to 'yes', the coward attacks the weakest (lowest hitpoints) enemy next to which it ends up after moving (such as a cornered animal would do, blindly lashing out without regards for its own safety).
* '''avoid_x, avoid_y''': The x and y coordinate of the hex to avoid
* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs.
* '''[filter_second]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting the units from which the cowards flee. If not set, this defaults to all enemy units. Note, however, that no "enemy of AI side" condition is added if [filter_second] is specified, meaning that it can include allied and/or enemy units as desired (and even units on the same side as the coward). {{DevFeature1.11|8}}
* '''seek_x, seek_y''': The x and y coordinate of the hex to seek

Here's an example of a coward [micro_ai] tag usage from the "Guardians" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=coward
action=add

id=coward3
distance=5
seek_x,seek_y=24,5
avoid_x,avoid_y=24,15
[/micro_ai]

=== Zone guardian (ai_type=zone_guardian) ===

A zone guardian is a unit that, as the name says, guards a zone. It moves randomly inside this zone until an enemy enters it (or a separately defined enemy zone, see below). Applications might be the defense of a castle, a nesting area or for protecting an unit. The zone macro can be called with an optional SLF, [filter_location_enemy]:
* If not specified, the zone guard attacks any enemy coming inside its guard zone.
* If [filter_location_enemy] is given, it attacks any enemy entering this zone and once there are no more enemies, it goes back to patrol in its basic zone.

Enable the Zone Guardian Micro AI by using
ai_type=zone_guardian
in the [micro_ai] tag together with the following keys:

'''Required keys:'''

* '''id''' or '''[filter]''': The ID of a unit or a [[StandardUnitFilter|Standard Unit Filter]] selecting the units controlled by this Micro AI.
** One or the other is required
** If both are given, [filter] takes priority over id=
** The AI contains an implicit filter for units on the AI side. Thus, if all AI units are to be selected, an empty [filter] tag can be used.
** If several units match the filter, the order in which they are controlled is not guaranteed. If the order matters, set up several MAIs using the id= key and different values for ca_score=.
* '''[filter_location]''': A [[StandardLocationFilter|Standard Location Filter]] designating the zone to guard.

'''Optional keys:'''
* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs.
* '''[filter_location_enemy]''': A [[StandardLocationFilter|Standard Location Filter]] designating the zone where enemies have to be attacked. If not given, it defaults to [filter_location].
* '''station_x,station_y''': By default, the zone guardian moves randomly within the zone if there is no enemy to attack. However, if station_x/y is given, it moves to this position instead during turns when it does not have an enemy to attack. This position does not need to be inside the zone defined above. Note: obviously it does not make sense to define [filter_location], [filter_location_enemy] and station_x/y all at the same time. Only [filter_location] and either one of the latter two (or none of them) should be provided for any zone guardian.

Here's an example of a zone guardian [micro_ai] tag usage from the "Guardians" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=zone_guardian
action=add

id=zone3
[filter_location]
x,y=22-31,4-11 # This is intentionally chosen to extend past the lake
terrain=W*
[/filter_location]
station_x,station_y=32,8
[/micro_ai]

== Hang Out Micro AI (ai_type=hang_out) ==

The Hang Out Micro AI instructs units of the AI side to "hang out" around a certain location, or locations, until a condition for mobilizing the side is met. If none of the optional keys are given, the AI controls all units of the side to hang around the leader while moving off castle tiles to make room for recruiting.

The AI works by moving each unit to its best hex first using the minimum amount of movement points required for this move. Once all AI units are in position, movement points are set to zero for all of them simultaneously such that they cannot be used by other AI candidate actions. This is done because the mobilizing condition might be met as result of one of the moves of the Hang Out AI, after which we want units to be able to continue with other AI actions.

For a demonstration, check out the "Hang Out and Messenger" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Hang Out Micro AI by using
ai_type=hang_out
in the [micro_ai] tag.

===Hang Out specific keys for the [micro_ai] tag:===

'''Required keys:'''

There are no required keys. In its default configuration, the Hang Out MAI controls all units of a side, keeping them as close to the side leader(s) as possible while moving off castle tiles to make room for recruiting. For this purpose, the candidate action score defaults to 170,000, which is just below the score of the default recruiting CA.

'''Optional keys:'''

* '''[avoid]''': A [[StandardLocationFilter|Standard Location Filter]] for the terrain which the AI units should avoid. If it is not given, the existence of the default (RCA) AI's [avoid] tag is checked (and used if it exists). If neither of these two exists, this parameter is set to default to all castle terrain (<tt>terrain=C*,C*^*,*^C*</tt>) so that units move off the castle to make room for recruiting. Note that this does not include keep terrain, otherwise the leader would be moved off the keep as well.
* '''ca_score'''=170000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 170,000, which means that it is executed after the default recruitment CA, but before most of the other default CAs.
* '''[filter]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting the units of the AI side participating in the Hang Out action (<tt>side=</tt> is always set and does not need to be provided). It defaults to all units of the side. The filter automatically includes the side= key set to the AI side.
* '''[filter_location]''': A [[StandardLocationFilter|Standard Location Filter]] describing the locations ''near'' which the AI units should hang out. This does not mean that the units only move onto terrain specified here, but that they minimize the distance to such terrain. It defaults to the position of the side leader(s).
* '''mobilize_condition''': ([[ConditionalActionsWML#Condition_Tags|WML Condition Tag]]) Once the condition set up here has been met, the Hang Out MAI is disabled and the side goes over to other AI activity. The Hang Out MAI remains disabled after this, even if the condition is not met any more later in the scenario.
* '''mobilize_on_gold_less_than''': (number) Since side gold cannot be checked in a WML condition tag without storing it in a variable first, this key is provided separately. It disables the Hang Out Micro AI once the side gold goes below the value specified here for the first time.

'''Standard RCA AI aspects respected by this Micro AI:'''
*'''[avoid]''': The standard RCA AI aspect used to define locations that should be avoided by the AI. See above (under 'optional keys') for details.

'''Notes:'''

* The Hang Out AI still takes effect if no locations to hang out at are found or if all map locations are to be avoided. In that case, it simply keeps all units at their current locations.

This is an example of a Hang Out Micro AI configuration from the "Hang Out and Messenger" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=1
ai_type=hang_out
action=add

[avoid]
terrain=C*,H*,M*,A*,S*,*^F*
[/avoid]
[mobilize_condition]
[have_unit]
side=1
count=7-99
[/have_unit]
[/mobilize_condition]
[/micro_ai]

== Healer Support Micro AI (ai_type=healer_support) ==

The Healer Support Micro AI configures the healers of a side to stay behind the battle lines and heal injured and/or threatened units rather than participate in combat under all circumstances. You can set different levels of aggressiveness for the healers.

'''Notes'''
* By default, ''all'' healers of the AI side are controlled by this AI. This includes in particular also the side leader, if the leader is a healer. If you do not want the leader to be included (and possibly be moved away from the keep etc.) use the [filter] tag with canrecruit=no (see below).
* It is not always better to use this Micro AI than the default AI, as it takes healers (which can be strong units) away from the pool of units to choose for attacks.

For a demonstration, check out the "Healers" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Healer Support Micro AI by using
ai_type=healer_support
in the [micro_ai] tag.

===Healer Support specific keys for the [micro_ai] tag:===

'''Required keys:'''

There are no required keys.

'''Optional keys:'''

* '''[filter]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting the healer units. If set, only units on the AI side passing this filter ''and'' having the healing ability are considered by this Micro AI.
*'''[filter_second]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting units to receive healing. If set, only units on the AI side passing this filter ''and'' the other healee selection criteria will be selected for healing by this Micro AI.
* '''aggression'''=1.0: (float) Sets the aggressiveness of the AI. This parameter is set up as a float to accommodate future functionality, but it currently acts as a boolean: if set to zero, the AI will never let its healers participate in combat, for all other values it allows them to attack after all other units have attacked and if the healers cannot find any more units to support. The former behavior might be appropriate in scenarios with only one or few valuable healers, while the latter might work better in scenarios with many healers.
* '''injured_units_only'''=no: (boolean) If set to 'yes', the AI will only move healers next to units that are already injured and skip units that currently have full hitpoints, but might get injured during the next enemy turn.
* '''max_threats'''=9999: (integer) The maximum allowable number of enemies that can attack a hex in order for it to be considered for a healer. As an example, setting 'max_threats=0' means that the AI only moves healers to locations that are entirely safe from the enemy (assuming that none of the units currently on the map dies). Note that the value of this key is checked against the number of enemies that can make it to the hex, not the number of adjacent hexes from which the healer could be attacked.

'''Standard RCA AI aspects respected by this Micro AI:'''
*'''[avoid]''': The standard RCA AI aspect used to define locations that should be avoided by the AI.

'''Notes:'''
* The Healer Support Micro AI modifies the [[AiWML#Filtering_Combat_with_the_.27attacks.27_Aspect|attacks aspect]].
* The CA evaluation scores of this AI are hard-coded. It does not work otherwise.

This is an example of a Healer Support Micro AI configuration from the "Healers" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=healer_support
action=add

aggression=0
[/micro_ai]

== Lurkers Micro AI (ai_type=lurkers) ==

The Lurker Micro AI controls some or all units of a side in "lurker mode". A lurker is a unit that is capable of moving across most terrains, but that only stops on and attacks from specific terrain. It might also have the ability to hide on this terrain (which is the reason why it is called a lurker).

Lurkers move individually without strategy and always attack the weakest enemy within their reach. If no enemy is in reach, the lurker does a random move instead - or it just sits and waits (lurks).

For a demonstration of different types of lurker behavior, check out the "Lurkers" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Lurkers Micro AI by using
ai_type=lurkers
in the [micro_ai] tag

===Lurkers specific keys for the [micro_ai] tag:===

'''Required keys:'''
* '''[filter]''': Specifies which units of the side are controlled by the Lurker Micro AI. This is a [[StandardUnitFilter|Standard Unit Filter]]. The filter automatically includes the side= key set to the AI side.
* '''[filter_location]''': Specifies the terrain from which the lurkers attack. This is a [[StandardLocationFilter|Standard Location Filter]].

'''Optional keys:'''
* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs.
* '''[filter_location_wander]''': Specifies the terrain on which lurkers end their moves if there is no enemy in reach. This is a [[StandardLocationFilter|Standard Location Filter]]. If [filter_location_wander] is not given, it defaults to [filter_location].
* '''stationary'''=no: (boolean) If set to yes, a lurker never moves if there is no enemy within attack range.

Here's an example of [micro_ai] tag usage from the "Lurkers" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=4
ai_type=lurkers
action=add

[filter]
type=Naga Fighter
[/filter]
[filter_location]
terrain=W*,S*
[/filter_location]
[filter_location_wander]
terrain=W*
[/filter_location_wander]
[/micro_ai]

== Messenger Escort Micro AI (ai_type=messenger_escort) ==

The Messenger Escort Micro AI lets you define a set of waypoints through which it tries to move one or several of its units, the messenger(s). The other units escort the messenger, trying to protect it and attacking enemies that are in its way. Note that a messenger might not strictly hit intermediate waypoints, but that getting close is good enough, especially if a waypoint is occupied by an enemy unit. It does, however, always try to get to the last waypoint.

'''Notes on the use of several messengers:''' {{DevFeature1.13|0}}
* This Micro AI can control several messengers at the same time, which can but do not have to move in a group. They can be put on the map altogether in one location, or be spread out on the map or across different turns.
* The farther a messenger has moved through the chain of waypoints, the higher a priority it is for the AI, meaning that farther advanced (on the map) messengers are moved first, and that the escort units try to clear the way and stay with those messengers more so than with those further back on the map. This order can be inverted using the invert_order= key.
* If several messengers are on the map, escort units might move from one to the other, the AI making a judgement call where they are needed most. Closeness to a messenger is generally the most important criterion, but not the only one.
* If a messenger dies, the escort units previously staying with it now join one of the other messengers if there are any left (otherwise they follow default AI behavior).
* If you want certain escort units to stay always with the same messenger, use several messenger [micro_ai] tags with different [filter]/[filter_second] combinations.

For a demonstration, check out the "Messenger" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Messenger Escort Micro AI by using
ai_type=messenger_escort
in the [micro_ai] tag.

===Messenger Escort specific keys for the [micro_ai] tag:===

'''Required keys:'''

* '''id''' or '''[filter]''': {{DevFeature1.13|0}} (Previous to 1.13.0, only id= was allowed.) The id of a unit or a [[StandardUnitFilter|Standard Unit Filter]] selecting the units controlled by this Micro AI.
** One or the other is required
** If both are given, [filter] takes priority over id=
** The AI contains an implicit filter for units on the AI side. Thus, if all AI units are to be selected, an empty [filter] tag can be used.
* '''waypoint_x,waypoint_y''': Comma-separated list of waypoint coordinates through which the messenger will go in the given order to reach its goal, given by the last coordinate. If you want the messenger to go directly to the goal, simply enter a single x,y coordinate here. Note that the messenger does not have to hit each waypoint exactly (except for the final one), getting close to them is good enough.

'''Optional keys:'''

* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate actions controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs. Note that the Messenger Escort AI consists of 3 CAs with scores ranging from <tt>ca_score-2</tt> to <tt>ca_score</tt>.
* '''enemy_death_chance'''=0.67 and '''messenger_death_chance'''=0.0: (both floats; ranging from 0 to 1) If the messenger is adjacent to an enemy at the end of the move, it will only attack the enemy if the chance of death of the enemy is >= enemy_death_chance and if the messenger's chance of death is <= messenger_death_chance (or if it is an attack at a range for which the enemy does not have a weapon).
* '''[filter_second]''': {{DevFeature1.13|0}} A [[StandardUnitFilter|Standard Unit Filter]] selecting the escort units. If not set, this defaults to all enemy units. The filter automatically includes the side= key set to the AI side.
* '''invert_order'''=no: {{DevFeature1.13|0}} If set to 'yes', the order of priority with which messenger units are considered is inverted, starting with the messenger unit that is the least advanced on the map (see description above). In most cases, selecting this option results in worse performance of the AI, so use it with caution. (And obviously it has no effect at all if there is only one messenger controlled by the AI.)

Here's an example of [micro_ai] tag usage from the "Messenger Escort" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=messenger_escort
action=add

id=messenger
waypoint_x=31,24,27,28
waypoint_y=20,14,7,1
[/micro_ai]

== Patrol Micro AI (ai_type=patrol) ==

The defines a number of waypoints for a unit (or units) to follow. Options can be set whether the route should be followed in a loop, as an out-and back, only once, whether units encountered along the way should be attacked, etc.

No matter what options are chosen, getting to the next waypoint always takes priority over attacking for a patroller. The AI thus prefers to move the patrol unit around enemies rather than straight for them. Also, if a waypoint is occupied by a unit the AI is not instructed to attack, it will (eventually) abandon that waypoint once it gets close enough and move on to the next one.

For a demonstration of several different patrol behaviors, check out the "Patrols" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Patrol Micro AI it by using
ai_type=patrol
in the [micro_ai] tag.

===Patrol specific keys for the [micro_ai] tag:===

'''Required keys:'''

* '''id''' or '''[filter]''': The ID of a unit or a [[StandardUnitFilter|Standard Unit Filter]] selecting the units controlled by this Micro AI.
** One or the other is required
** If both are given, [filter] takes priority over id=
** The AI contains an implicit filter for units on the AI side. Thus, if all AI units are to be selected, an empty [filter] tag can be used.
** If several units match the filter, the order in which they are controlled is not guaranteed. If the order matters, set up several MAIs using the id= key and different values for ca_score=.
* '''waypoint_x,waypoint_y''': Comma-separated lists of the waypoint coordinates through which the patrol travels (in order).

'''Optional keys:'''

* '''attack''': By default (if this key is not set), the patrol unit attacks any unit it ends up next to after a move. Alternatively, this parameter can be set to a comma-separated list of unit ids. If that is done, the patrol only attacks these units when it ends up next to them and ignores any other unit. This can in turn be used to have the patroller not attack at all, by setting ''attack='' to a non-existing id.
* '''ca_score'''=300000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 300,000, which is higher than any of the [http://wiki.wesnoth.org/AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29 RCA AI candidate actions]. By setting it, for example, to 170,000, we can have it be executed after the default recruitment CA, but before most of the other default CAs.
* '''one_time_only'''=no: (boolean) If set to 'yes', the unit goes through the patrol route only once and then hangs out at the last waypoint. It also always attacks any enemy unit on the last waypoint, independent of what ''attack='' is set to.
* '''out_and_back'''=no: (boolean) By default, a patrol unit returns to the first waypoint after reaching the last, doing the patrol route as a loop. If this parameter is set to 'yes', the unit instead reverses its course and perpetually does out and backs of the route.

Here's an example of [micro_ai] tag usage from the "Patrols" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=2
ai_type=patrol
action=add

id=Konrad
waypoint_x=9,24,25
waypoint_y=21,23,15
one_time_only=yes
attack=Gertburt
[/micro_ai]

== Protect Unit Micro AI (ai_type=protect_unit) ==

The Protect Unit Micro AI tries to move one or several units to a given location while keeping them safe from enem attacks. It does so by keeping the protected units away from enemy units and close to friendly units. Other units on the AI side are controlled by the default Wesnoth AI.

For a demonstration, check out the "Protect Unit" and "The Elves Besieged" scenarios from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Protect Unit Micro AI by using
ai_type=protect_unit
in the [micro_ai] tag.

===Protect Unit specific keys for the [micro_ai] tag:===

'''Required keys:'''

* '''[unit]''': A separate [unit] tag is required for each protected unit(s). Each tag has required keys id=, goal_x=, goal_y= for each unit, as shown in the example below.

'''Optional keys:'''

* '''disable_move_leader_to_keep'''=no: (boolean) If set to 'yes', side leaders protected by this AI do not try to return to their keep. This is necessary for this Micro AI to work with units that are side leaders and that are supposed to move to an off-keep location.

'''Notes:'''
*The Protect Unit Micro AI modifies the [[AiWML#Filtering_Combat_with_the_.27attacks.27_Aspect|attacks aspect]]. Depending on the parameters, it might also modify the [[AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29|move leader to keep candidate action]].
* The CA evaluation scores of this AI are hard-coded. It does not work otherwise.

Here's an example of [micro_ai] tag usage from the "HttT: The Elves Besieged" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=1
ai_type=protect_unit
action=add

[unit]
id=Delfador
goal_x,goal_y=1,2
[/unit]
[unit]
id=Konrad
goal_x,goal_y=1,1
[/unit]

disable_move_leader_to_keep=true
[/micro_ai]

== Recruiting Micro AI==
=== General Comments on the Recruiting Micro AIs ===

The Recruiting Micro AI replaces the default recruitment AI by alternative recruiting patterns. Currently there are two recruiting algorithms you can choose from, random recruiting and the rush recruiting used in the new (as of Version 1.11.1) Experimental AI (see below).

For a demonstration of a different recruiting pattern, check out the "Recruiting" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]. You can also explore the unit choices by watching the Experimental AI in a multiplayer game.

'''Note:''' Obviously, the Recruitment Micro AI modifies the [[AiWML#Evaluating_AI_Moves_--_Candidate_Actions_.28CAs.29|recruitment candidate action]].

=== Random Recruitment AI (ai_type=recruit_random) ===

This AI randomly selects a unit type from the recruitment list of the side. The probability of choosing each type and the behavior in low-gold situations can be influenced with optional parameters.

Enable the Random Recruiting Micro AI by using
ai_type=recruit_random
in the [micro_ai] tag.

'''Required keys:'''

There are no required keys.

'''Optional keys:'''

* '''ca_score'''=180000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 180,000. This is identical to the default Recruiting CA which it replaces.
* '''[probability]''': This tag sets the probability of selecting the given unit type. It has two required sub-keys:
** '''type''': comma-separated list of unit types to which this probability is to be applied
** '''probability''': (non-negative float) The probability with which these unit types is to be selected. All unit types for which no [probability] tag is defined receive a default probability of 1.0, thus values should be chosen relative to that. As an example, in the code below swordsmen and peasants are given a probability of 8, while no other units have assigned probabilities. Thus, each of these two unit types is 8 times more likely to be selected than any other individual unit type.
* '''skip_low_gold_recruit'''=no: (boolean) By default, the random recruitment AI chooses a unit to recruit only from those types for which it has sufficient gold. If this parameter is set to 'yes', it will instead choose from all available unit types and end recruiting for the turn if there is not enough gold to recruit it this turn (even if other, affordable unit types exist).

Here's an example of a random recruiting [micro_ai] tag usage from the "Recruiting" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=1
ai_type=recruit_random
action=add

[probability]
type=Swordsman,Peasant
probability=8
[/probability]

skip_low_gold_recruiting=yes
[/micro_ai]

=== Rush Recruitment AI (ai_type=recruit_rushers) ===

This AI replaces the default recruiting with the rush recruiting used in the new (as of Version 1.11.1) Experimental AI.

Enable the Rush Recruiting Micro AI by using
ai_type=recruit_rushers
in the [micro_ai] tag.

'''Required keys:'''

There are no required keys.

'''Optional keys:'''

* '''ca_score'''=180000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 180,000. This is identical to the default Recruiting CA which it replaces.
* '''randomness'''=0.1: (number) A random number is applied to the rusher recruit engine's score to prevent the recruitment pattern from being too predictable. 0 causes no randomness to be applied, while larger numbers increase the random effect. A value of 1-2 generates results in which the random effect is approximately equal to the scored effect. Extremely high values are essentially entirely random.

Here's an example of a rush recruiting [micro_ai] tag usage from the "Recruiting" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]:
[micro_ai]
side=1
ai_type=recruit_rushers
action=add
[/micro_ai]

== Simple Attack Micro AI (ai_type=simple_attack) ==

The Simple Attack Micro AI is meant as an addition to the default combat candidate action for when one wants to force the AI to do attacks that it would otherwise not do (for example on units that are 1 XP from leveling) or to execute certain attacks before all others (for example, attack with all "expendable" units first). It is not set up to be a replacement for the default attacks. Some notes:

* The algorithm is different from and simpler than that of the default combat CA. For example, no attack combinations are considered, only individual attacks. As a result, the [[AiWML#The_.5Bai.5D_Tag:_Defining_Aspects|default aspects]] (aggression, caution, [avoid], ...) are not taken into account. Also, if lots of units are involved, evaluation of this Micro AI is potentially quite a bit slower than of the default attacks.

* If an attack matching the Standard Unit Filters described below is found, this attack will always be executed, no matter how bad the odds are. Thus, this Micro AI can be used to force the AI to do attacks it would otherwise avoid.

* Other than selecting the attacker/defender units, this AI is currently not configurable. Let us know if you would like to see certain options to be added. (No guarantees that we will add them, but we will definitely consider them.)

For a demonstration, check out the "Simple Attack" scenario from the [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

Enable the Simple Attack Micro AI by using
ai_type=simple_attack
in the [micro_ai] tag.

===Simple Attack specific keys for the [micro_ai] tag:===

'''Required keys:'''

There are no required keys. It is, however, in general not desirable to use this AI without at least one of the optional Standard Unit Filters below, as this AI is not meant as a replacement of the default combat candidate action.

'''Optional keys:'''

* '''ca_score'''=110000: (non-negative integer) The evaluation score of the candidate action controlling this Micro AI. By default, it is set to 110,000, which means that it is executed right before the default combat candidate action.
* '''[filter]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting the units of the AI side participating in the Simple Attack action. It defaults to all units of the side. The filter automatically includes the side= key set to the AI side.
* '''[filter_second]''': A [[StandardUnitFilter|Standard Unit Filter]] selecting the units the AI should attack. It defaults to all enemy units. The filter automatically includes a [[StandardSideFilter|Standard Side Filter]] set to all enemies of the AI side.
* '''weapon'''=-1: (integer) The number of the weapon that should be used for this attack. Weapon numbers start at 1 (not 0). -1 stands for "best weapon" (by whatever criterion the AI chooses to use). '''Available from Wesnoth 1.11.8'''

Below are 2 examples of Simple Attack Micro AI configurations from the "Simple Attack" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]]. The first one shows how to force the AI to attack with all Soulless and Walking Corpse units first:
[micro_ai]
side=2
ai_type=simple_attack
action=add

ca_score=110000
[filter]
type=Soulless,Walking Corpse
[/filter]
[/micro_ai]
The second executes attacks by Soulless on all enemy units that are 1 XP from leveling (something the RCA AI would generally not do). Note that the Lua code bit is simply there in order to code the "1 XP from advancing" condition. It is not needed for most other SUFs, as can be seen in the previous example.
[lua]
code=<<
function close_to_advancing(unit)
if (unit.experience >= unit.max_experience-1) then
return true
else
return false
end
end
>>
[/lua]

[micro_ai]
side=2
ai_type=simple_attack
action=add

ca_score=110001
[filter]
type=Soulless # No Walking Corpses; L0 units don't advance enemy
[/filter]
[filter_second]
lua_function = "close_to_advancing"
[/filter_second]
[/micro_ai]
Several Simple Attack Micro AIs can be combined for the same AI side. The two examples above are both used (note the different values for ca_score) in the "Simple Attack" [[Micro_AIs#Micro_AI_Test_and_Demo_Scenarios|test scenario]].

== Using Development (1.13) Version Micro AIs in your Stable (1.12) Version Add-on ==

The Micro AIs will be in a stable release for the first time in Wesnoth 1.12. It is therefore likely that quite a few (good) feature requests will be made as more UMC authors start using them. However, new features cannot be added to the stable 1.12 series and will be implemented in Wesnoth 1.13 instead. Fortunately, since the Micro AIs are entirely written in Lua, a 1.13 Micro AI can be added to a 1.12 add-on with relative ease. This section describes the steps necessary to accomplish that.

==== 1. Download the latest development release and locate the Micro AIs directory in it ====

The Micro AI directory in each Wesnoth distribution is <tt>data/ai/micro_ais</tt>. Check out [http://wiki.wesnoth.org/Editingwesnoth#The_game_data_directory this link] if you do not know where that is on your system.

As an alternative to downloading the entire development release, you can also download only the files in which you are interested from the [https://github.com/wesnoth/wesnoth/ Wesnoth repository site].

==== 2. Copy the relevant files into your add-on ====

* In your add-on's folder, create a directory <tt>ai</tt>
* Copy file <tt>data/ai/micro_ais/micro_ai_wml_tag.lua</tt> from the development release into the new <tt>ai</tt> folder in your add-on
* In <tt>data/ai/micro_ais</tt> is a subfolder called <tt>cas</tt> containing all the AI candidate action (CA) files. Copy the files for the Micro AI you want to use from there into the <tt>ai</tt> folder of your add-on. The number of relevant files depends on the Micro AI. For example, the Patrol Micro AI only uses a single file (<tt>ca_patrol.lua</tt>), while there are four for the Messenger Escort Micro AI (<tt>ca_messenger_attack.lua</tt>, <tt>ca_messenger_escort_move.lua</tt>, <tt>ca_messenger_f_next_waypoint.lua</tt> and <tt>ca_messenger_move.lua</tt>).

==== 3. Set up a local Micro AI tag ====

Open file <tt>micro_ai_wml_tag.lua</tt> (the one in your add-on, not the original) and find these two lines:
function wesnoth.wml_actions.micro_ai(cfg)
local CA_path = ''''ai/micro_ais/cas/''''
Modify them to (the pars to change are shown in bold)
function wesnoth.wml_actions.micro_ai'''_MC'''(cfg)
local CA_path = ''''~add-ons/My_Campaign/ai/''''
<tt>_MC</tt> here stands for 'My Campaign'. You can really use anything you want here, as long as you use it consistently throughout the next steps. Also, you need to change the second line (with the CA_path variable) to contain the correct path to the directory into which you just put the AI candidate action (CA) files in your add-on.

You also need to add the following to your <tt>_main.cfg</tt> file
[lua]
code = << wesnoth.dofile("~add-ons/My_Campaign/ai/micro_ai_wml_tag.lua") >>
[/lua]
replacing, again, <tt>My_Campaign</tt> with the correct path to your add-on.

These two steps set up a WML tag <tt>[micro_ai_MC]</tt> which you can use in exactly the same way as the mainline <tt>[micro_ai]</tt> tag, just that it contains the functionality of the new files you just copied into the <tt>ai</tt> folder of your add-on. However, it might not quite work correctly yet as the paths in some of the files still might have to be adjusted.

==== 4. Adjust paths in the files ====

All of the candidate action files load other libraries (files) at the beginning. For example, this is the beginning of <tt>ca_messenger_attack.lua</tt>
local H = wesnoth.require "lua/helper.lua"
local AH = wesnoth.require "ai/lua/ai_helper.lua"

local messenger_next_waypoint = wesnoth.require "ai/micro_ais/cas/ca_messenger_f_next_waypoint.lua"

The most difficult part of setting up the Micro AI in your add-on is figuring out which of these files need to be imported and linked in your add-on directory. Anything that belongs to the same Micro AI definitely needs to be changed. Thus, the last line needs to be changed to
local messenger_next_waypoint = wesnoth.require "~add-ons/My_Campaign/ai/ca_messenger_f_next_waypoint.lua"

For all other files included by the CA file (that is <tt>lua/helper.lua</tt> and <tt>ai/lua/ai_helper.lua</tt> in the example above), it depends on whether they have been changed between the version of Wesnoth 1.12 you are using and the development version from which you are copying the Micro AI; and more importantly, whether the part of them which the Micro AI uses has been changed. In principle, you could import and change all files that are linked from the <tt>ca_*.lua</tt> files, but that would result in a lot of unnecessary code duplication and should be avoided. It's better to compare the files (do a 'diff') between the stable and the development version and decide based on that. If in doubt, just [http://forums.wesnoth.org/viewtopic.php?f=10&t=39456 ask] and we will tell you.

As an example, let's assume that file <tt>ai_helper.lua</tt> has been changed. In that case, it needs to be copied from <tt>data/ai/lua/ai_helper.lua</tt> in the development version (note that the paths shown in the example above do not include the leading <tt>data/</tt>) and copied into your add-on's <tt>ai</tt> directory. And finally, as a last step, the line including the file inside <tt>ca_messenger_attack.lua</tt> needs to be changed to point to the newly created local copy:
local AH = wesnoth.require "~add-ons/My_Campaign/ai/ai_helper.lua"
Repeat this step for all the <tt>ca_*.lua</tt> files.

Well, that's all. You can now use the <tt>[micro_ai_MC]</tt> tag for the Micro AI you just imported, and continue to use the default <tt>[micro_ai]</tt> tag for all others. It does take a bit of work, but it (hopefully) is much easier than writing your own AI from scratch. If you have any problems with this, please don't hesitate to [http://forums.wesnoth.org/viewtopic.php?f=10&t=39456 ask us for help].

[[Category:AI]]

EraWML

2014-11-17T20:47:55Z

Trewe: /* The [era] top level tag */ an rather obscure (and useless) feature

{{WML Tags}}
== The [era] top level tag ==

This tag describes one era. An era is a set of teams to play in multiplayer.

In the multiplayer game creation screen, an era is chosen by the host by the 'Era' option button.

The following key/tags are recognized for '''[era]'''
* '''id''': ID of the era - must be unique. No gameplay effect
* '''name''': displayed name of the era.
* '''description''': {{DevFeature1.11}} a short description of the era.
* <span id="require_era">'''require_era'''</span>: whether clients are required to have this era installed beforehand to be allowed join a game using this era. Possible values 'yes' (the default) and 'no'.
* '''allow_scenario''': {{DevFeature1.11}} a list of scenario ids. Only the scenarios with matching ids will be allowed to be played with this era.
* '''disallow_scenario''': {{DevFeature1.11}} a list of scenario ids. Only the scenarios with matching ids will not be allowed to be played with this era. Cannot be used in parallel with allow_scenario.
* '''ignore_incompatible_scenario''': {{DevFeature1.11}} a list of scenario ids. The scenarios with matching ids will be considered compatible with this era regardless their dependencies.
* '''allow_modification''': {{DevFeature1.11}} same as allow_scenario, but for modifications.
* '''disallow_modification''': {{DevFeature1.11}} same as disallow_scenario, but for modifications. Cannot be used in parallel with allow_modification.
* '''ignore_incompatible_modification''': {{DevFeature1.11}} same as ignore_incompatible_scenario, but for modifications.
* '''force_modification''': {{DevFeature1.11}} a list of modification ids. The specified modifications must be enabled to play this era.
* '''[multiplayer_side]''': a faction in the era. This tag contains many of the same keys as a [side] tag (A description of the [side] tag can be found in [[SideWML]]). When a multiplayer game is played, then the [side] tag for the scenario is merged with the keys(currently, not tags) of the [multiplayer_side] tag of the faction which the side chose.
** '''id''': faction ID - must be unique to your era. No gameplay effect
** '''name''': a description that Wesnoth displays as the option selecting that faction; see [[DescriptionWML]]. Any image in this description will ''not'' use the team color.
** '''image''': an image to display in the option. This image will use the team color.
** '''flag_rgb''': often set by [http://www.wesnoth.org/macro-reference.xhtml#MAGENTA_IS_THE_TEAM_COLOR MAGENTA_IS_THE_TEAM_COLOR]
** '''leader''': a list of unit types. Must be present. When this faction is chosen, the side can choose any of these unit types to be the side's leader (i.e. "Choose your Leader"). They will also have the option of having one of these types being chosen randomly.
** '''random_leader''': if this list of types is present, it would use this list to instead to choose a random leader. If not it would use '''leader'''
** '''random_faction''': default 'no'. If 'yes', then when this faction is chosen, another non random faction will be randomly chosen instead. The leader will also be chosen randomly.
** '''choices''': Empty by default. If non-empty and the faction has '''random_faction=yes''', it is the list of the IDs of the non random factions that will be choosen randomly. If empty, any faction can be chosen.
** '''except''': Empty by default. If the faction has random_faction=yes, it is the list of the IDs of the non random factions that will not be choosen randomly.
** '''type''': the unit type of the default leader for the side. This must be present. 'random' is a valid value here and will cause a random leader choice by default.
** '''recruit''': a comma-separated list of unit types this faction can recruit.
** '''extra_recruit''': a comma-separated list of unit types appended to the leader recruitlist (see [[SingleUnitWML]]).
** '''terrain_liked''': an unseparated list of terrains (see [[TerrainCodesWML]]). On random maps, these terrains will determine which keep the side is assigned, attempting to put it near the listed terrains.
* '''[event]''': any [event]s written inside the [era] tag will get included into scenarios that are played using this era. See [[EventWML]].
* '''[options]''': {{DevFeature1.11}} custom options. See [[OptionWML]] for details.
* '''[ai]''': See [[AiWML]] for details.

== See Also ==

* [[ReferenceWML]]
* [[SideWML]]

[[Category: WML Reference]]

MapGeneratorWML

2014-11-17T20:25:23Z

Trewe: /* [generator] */ fix markup

Map Generator WML is used to create scenarios which are randomly generated. Of course, any scenario may reconfigure itself during a start / prestart event as much as it likes, using randomness, but the Map Generator WML has the following advantages:

* Wesnoth has several built-in map generators which can be configured with options, and these are much better developed than any existing pure WML options.
* Map generation occurs before the scenario is even loaded, something which is not possible for WML events. In an mp game, the map generator code will run only on the host, side-stepping any synchronization issues, and keeping your scenario code as simple as possible.
* For scenarios with "allow_new_game=yes" and which use map generators, the generator may be reconfigured in the mp create screen (assuming that someone has coded a dialog for it). The user can also select to regenerate the map and get instant feedback from the minimap display.

== Scenario vs map generation ==

Every map generator can be used in either '''scenario_generation''' mode or '''map_generation''' mode. In map_generation mode, the generator is only used to replace the map_data of your scenario. In scenario_generation mode, the entire [scenario] tag is replaced.

To select a map generator and mode, in your [scenario] tag you must place '''one of'''
* '''scenario_generation=algorithm'''
* '''map_generation=algorithm'''
where '''algorithm''' is the generator algorithm you want to use. Note that not every algorithm is designed to be use with both of these options.

You must additionally place a [generator] tag in your scenario, which contains the options to the map generator.

== [generator] ==

The exact things that should be placed in [generator] depend on what algorithm you pick. There are three kinds of generators, '''default''', '''cave''', '''lua''' {{DevFeature1.13|0}}, and '''yamg''' {{DevFeature1.13|0}}.

For which key to use and what value, see the section for the generator you want to use.

===The lua generator===
The lua generator type specifies a custom map generator, which you provide via lua scripts.

The following keys are recognized for '''[generator]''' when the lua generator is used:
* '''create_map''' : A lua routine which returns a string containing the new map_data. The entire contents of the '''[generator]''' are passed to the script in a lua table (see [[LuaWML]]), via the argument '''...''' (see http://www.lua.org/pil/5.2.html).
* '''create_scenario''' : The same, but returning a '''[scenario]''' tag for the new scenario, as a lua table.

Any other keys are used only by the lua script.

The following keys of the output [scenario] are specifically watched by the mp create screen:
* '''id'''
* '''name'''
* '''description'''
* '''error_message'''

====Available Lua API====
The usual in-game API, in the table '''wesnoth''', is not available to lua scripts. However the usual standard lua libs are available, and a random number generator object is available from the Rng table. This is an instance of the Mersenne Twister 19937 random number generator from the C++11 standard.

* '''rng = Rng:create()''' : creates a new rng object
* '''rng:seed()''' : seed an rng, expects a string in hexadecimal format
* '''rng:draw()''' : draw a 32-bit random integer from the rng

===The Default Generator===
The default generator can be used to generate map data for any scenario. The data in this section is inferred from “data/multiplayer/scenarios/Random_Scenario.cfg”, usage in add-on content, and inspection of mapgen.cpp

'''Excerpt from mapgenerator comments:'''

* Basically we generate alot of hills, each hill being centered at a certain point, with a certain radius - being a half sphere. Hills are combined additively to form a bumpy surface. The size of each hill varies randomly from 1-hill_size. We generate 'iterations' hills in total. The range of heights is normalized to 0-1000. 'island_size' controls whether or not the map should tend toward an island shape, and if so, how large the island should be. Hills with centers that are more than 'island_size' away from the center of the map will be inverted (i.e. be valleys). 'island_size' as 0 indicates no island.

To use the default '''[generator]''' your '''[scenario]''' tag must contain one of the following keys:
* '''scenario_generation=default'''
* '''map_generation=default'''
If ‘scenario_generation’ is used, the engine will expect for your entire '''[scenario]''' sub tags to be inside a '''[scenario]''' tag inside '''[generator]'''. Tags outside of this will be ignored. There may be value in this, but at this writing, it’s not clear.
‘map_generation=default’ is simpler and more commonly used. It is also necessary to use this key so that you can regenerate a map in MP game creation.
In its use only generator data is in the '''[generator]''' tag, all other '''[scenario]''' data is placed outside of it. The exception is if you are making an initial MP scenario available in MP game creation, for this a '''[scenario]''' tag must appear inside of '''[generator]''', containing the '''[scenario]''' subtags you want to use. See “data/multiplayer/scenarios/Random_Scenario.cfg” for an example.

The following key/tags are recognized for '''[generator]''' when the default generator is used:
* '''[scenario]''': See [[ScenarioWML]]
* '''name'''
** '''default'''
* '''map_width''','''map_height''': size of the map to generate
* '''iterations''': the number of times an attempt is being made to generate a hill
* '''hill_size''': hills will have a random size between 1 and ''hill_size''
* '''max_lakes''': the number of times an attempt is being made to generate a lake
* '''min_lake_height''': lakes are the starting point of rivers and need to start above a certain height
* '''lake_size''': the size of a lake still randomly generated
* '''river_frequency''': determine how much a river can run uphill and thus generate more rivers

* '''villages''': villages per 1,000 hexes
* '''players''': Number of starting locations for the map.
* '''castle_size''': Number of castle tiles (including the keep), per player.
* '''temperature_iterations''': Same as iterations, but for the temperature map.
* '''temperature_size''': Same as hill_size, but for the temperature map. (Temperature map is generated the same way as a hill map, but is hard coded with a island_size of 0.)
* '''roads''': number of roads the generator will attempt to make
* '''road_windiness''': Use 1 for the road to be made using the cheapest path (based on [road_cost] tags), higher values introduce randomness to make the road wind a bit.
* '''island_size''': Use 1-5 for coastal maps and 6-10 for island maps. Bigger values may crash map generation process. Bigger numbers makes more water (and less land)
* '''default_flatland''': If not specified, is Grassland. If your height tags don't go down to 0, the default_flatland will be used (possibly in other cases as well).
* '''[height]''': list of common terrain types that come in at different heights, from highest to lowest. Good WML will have the range of 1000-0 covered.
** '''height''': the terrain specified below will appear at this height and up.
** '''terrain''': 1 terrain code
* '''[convert]''': used to make terrain conversions. For example, water becomes ice at low temperatures, grass snow, etc. If the terrain is between the min_x and max_x it will be converted. If min_x is not defined it will default to a large negative number. If max_x is not defined it will default to a large positive number
** '''min_height'''
** '''max_height'''
** '''min_temperature'''
** '''max_temperature'''
** '''from''': a comma separated terrains to convert from
** '''to''': The terrain to convert these terrains to
* '''[road_cost]'''
** '''terrain''' 1 terrain code
** '''cost''': how expensive it is the create a road on this terrain, this influences the odds of this terrain getting a road
** '''convert_to_bridge''': a comma separated list of terrains; N/S, then NE/SW, then NW/SE.
** '''convert_to''': 1 terrain code (note using both ''convert_to_bridge'' and ''convert_to'' might result in unwanted results)
* '''[village]''': The conversion of terrains to villages
** '''terrain''': 1 terrain code which will be converted to a village
** '''convert_to''': 1 terrain code for the village
** '''adjacent_liked''': a comma separated terrain list. This list increases the rating for a certain location, every tile around the location will be tested against this list and for every match the rating of the location is increased. The same terrain twice in the list will double the rating increase for that location.
** '''rating''': chance of appearing
* '''[castle]''': the conversion of castles
** '''valid_terrain''': a comma-separated terrain list with terrains which are allowed to be converted to a castle.
** '''min_distance''': all castles generated must be this number of hexes apart from each other
* '''[naming]''': The names used to label landscape features (forests, lakes, etc.). This controls, for example, the "Fox" part of "Foxwood". If this tag is empty, those labels should be suppressed. (Due to a bug, they are not suppressed prior to 1.11.1.) The predefined macro VILLAGE_NAMES is one option for the contents of this tag. If that macro is not used, this tag takes one key.
** '''male_names'''
* '''[village_naming]''': The names used to label villages. This controls, for example, the "Fox" part of "Foxham". If this tag is empty, those labels should be suppressed. (Due to a bug, they are not suppressed prior to 1.11.1.) The predefined macro VILLAGE_NAMES is one option for the contents of this tag. If that macro is not used, this tag takes one key.
** '''male_names'''

===The Cave Generator===
The cave generator does not appear to have been written for multiplayer scenario game creation like the default generator was. It is used in '''campaigns\Sceptre_of_Fire\scenarios\4_Gathering_Materials.cfg''' & '''campaigns\Heir_To_The_Throne\scenarios\ 17_Scepter_of_Fire.cfg '''. The data here is inferred from those scenarios and an inspection of cavegen.cpp

To use the cave '''[generator]''' your '''[scenario]''' tag must contain one of the following keys:
* '''scenario_generation=cave'''
* '''map_generation=cave'''
Here it is recommend you use ‘scenario_generation’ as there are examples to follow, though it may be possible to use’ map_generation’.

The following key/tags are recognized for '''[generator]''' when the cave generator is used:
* '''[settings]''': behaves as if '''[scenario]''', See [[ScenarioWML]]
* '''map_width''','''map_height''': size of the map to generate
* '''village_density''': influences number of villages
* '''flipx_chance''': Chance to flip x coordinates, that meens the map is mirrored at the vertical axis in its midth.
* '''flipy_chance''': Chance to flip y coordinates, that meens the map is mirrored at the horizontal axis in its midth.
* '''[chamber]''': for underground maps
** '''id''': a name used to identify where the passages lead. See the [passage] tag, below.
** '''x''','''y''': approximate location of the center hex of the chamber. Unfortunately it isn't always exact. Can be a single number (x=5) or a range (x=10-20)
** '''size''': circular radius of the chamber, including the center hex
** '''jagged''': a good value is probably between 0-50 (not sure exactly)
** '''chance''': chance for the chamber to be generated, between 0 and 100, 100 if key not present
** '''[items]''': See [[ScenarioWML]]. This can contain tags normally found under [scenario] like [side], [item], and [event]. Moveto events definitely work here (using the same_location_as_previous key instead of a location filter). Other events can be placed in the [settings] tag, above. Locations of items will be generated randomly. The attribute '''same_location_as_previous=yes''' means that the filter for a moveto event (see [[EventWML]]) is the same as the location of the previous item.
** '''[passage]''': defines a pathway between chambers
*** '''destination''': the id key of the destination chamber
*** '''windiness''': a good value is probably between 1-10
*** '''laziness''':
*** '''width''': number of hexes
*** '''jagged''': a good value is probably between 1-10
*** '''chance''': chance for the passage to be generated, between 0 and 100, 100 if key not present

=== YAMG generator ===

*** Please document me! ***

== Infrastructure ==

* The default generator settings are loaded from a scenario file under data/multiplayer/scenarios.
* mapgen_dialog overwrites these values if necessary.
* The create_map / create_scenario function is called by one of the following
** multiplayer_create_engine.cpp:394
** context_manager.cpp:648
** map_create.cpp:56
* A map buffer is written to res["map_data"]
* the config res is passed to the calling function.

== See Also ==

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

[[Category: WML Reference]]

PortugueseContinentalTranslation

2014-10-29T15:20:56Z

Trewe: /* Calão do jogo */

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar ativamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Ativos====

* trewe (maintainer) [mailto:sjrs456ATyahooDOTfr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.isATgmailDOTcom]
* Carlos Sousa
* Luís Passos
* lokakuu
* alfalb (tradutor/revisor de prova) [mailto:alfredoDOTsilvaATskyDOTcom]
* Manuela Silva [mailto:manuelaPONTOsilvaAROBAskyPONTOcom]

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou através do IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente, pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada por e-mail ou na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controlo [http://git-scm.com/ Git] e os ficheiros atuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans Github].

Após terem obtido o(s) ficheiro(s) *.po(s) estes podem ser abertos com o editor preferido para começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal], são bons exemplos de programas de código aberto e plataforma múltipla que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o ''patch'' para o responsável pelo projeto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objetivos dos cenários e dos comandos gerais são sempre dirigidos ao utilizador com o sujeito subententido.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A exceção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Discurso direto===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (exceções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjetivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialeto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| transferir
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| noturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projeto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Soberano
|-
| Spearman
| Milícia/Hoste/Lançador
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (nunca! como xamã)
|-
| merman
| ondim (Camões, Teófilo Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjetivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor/Dom
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|-
| BW (Before Wesnoth)
| AW (Antes do Reino de Wesnoth)
|-
| AW (After Wesnoth)
| CW ([segundo a] Cronologia de Wesnoth / nas crónicas de Wesnoth)
|-
| Lich
| Liche
|-
| Cepter of Fire
| Ceptro do Fogo (intencionalmente pre-AO)
|-
|}

==Estado da tradução==

=== Lista de Traduções ===

A lista seguinte, pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?version=master&package=&lang=pt Estatísticas da tradução]

[[WesnothTranslations]]

== Hiperligações Diversas ==

[[Category:Translations]]

PortugueseContinentalTranslation

2014-10-28T20:28:53Z

Trewe: /* Estilos e vocabulário */

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar ativamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Ativos====

* trewe (maintainer) [mailto:sjrs456ATyahooDOTfr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.isATgmailDOTcom]
* Carlos Sousa
* Luís Passos
* lokakuu
* alfalb (tradutor/revisor de prova) [mailto:alfredoDOTsilvaATskyDOTcom]
* Manuela Silva [mailto:manuelaPONTOsilvaAROBAskyPONTOcom]

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou através do IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente, pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada por e-mail ou na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controlo [http://git-scm.com/ Git] e os ficheiros atuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans Github].

Após terem obtido o(s) ficheiro(s) *.po(s) estes podem ser abertos com o editor preferido para começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal], são bons exemplos de programas de código aberto e plataforma múltipla que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o ''patch'' para o responsável pelo projeto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objetivos dos cenários e dos comandos gerais são sempre dirigidos ao utilizador com o sujeito subententido.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A exceção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Discurso direto===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (exceções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjetivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialeto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| transferir
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| noturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projeto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Soberano
|-
| Spearman
| Milícia/Hoste/Lançador
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (nunca! como xamã)
|-
| merman
| ondim (Camões, Teófilo Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjetivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor/Dom
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|-
| BW (Before Wesnoth)
| AW (Antes do Reino de Wesnoth)
|-
| AW (After Wesnoth)
| CW ([segundo a] Cronologia de Wesnoth / nas crónicas de Wesnoth)
|-
| Lich
| Liche
|-
|}

==Estado da tradução==

=== Lista de Traduções ===

A lista seguinte, pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?version=master&package=&lang=pt Estatísticas da tradução]

[[WesnothTranslations]]

== Hiperligações Diversas ==

[[Category:Translations]]

PortugueseContinentalTranslation

2014-10-28T20:26:37Z

Trewe: /* Calão do jogo */

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar ativamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Ativos====

* trewe (maintainer) [mailto:sjrs456ATyahooDOTfr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.isATgmailDOTcom]
* Carlos Sousa
* Luís Passos
* lokakuu
* alfalb (tradutor/revisor de prova) [mailto:alfredoDOTsilvaATskyDOTcom]
* Manuela Silva [mailto:manuelaPONTOsilvaAROBAskyPONTOcom]

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou através do IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente, pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada por e-mail ou na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controlo [http://git-scm.com/ Git] e os ficheiros atuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans Github].

Após terem obtido o(s) ficheiro(s) *.po(s) estes podem ser abertos com o editor preferido para começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal], são bons exemplos de programas de código aberto e plataforma múltipla que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o ''patch'' para o responsável pelo projeto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objetivos dos cenários e dos comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A exceção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Discurso direto===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (exceções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjetivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialeto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| transferir
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| noturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projeto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Soberano
|-
| Spearman
| Milícia/Hoste/Lançador
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (nunca! como xamã)
|-
| merman
| ondim (Camões, Teófilo Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjetivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor/Dom
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|-
| BW (Before Wesnoth)
| AW (Antes do Reino de Wesnoth)
|-
| AW (After Wesnoth)
| CW ([segundo a] Cronologia de Wesnoth / nas crónicas de Wesnoth)
|-
| Lich
| Liche
|-
|}

==Estado da tradução==

=== Lista de Traduções ===

A lista seguinte, pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?version=master&package=&lang=pt Estatísticas da tradução]

[[WesnothTranslations]]

== Hiperligações Diversas ==

[[Category:Translations]]

PortugueseContinentalTranslation

2014-10-28T20:23:42Z

Trewe: /* Equipa da tradução */ translators

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar ativamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Ativos====

* trewe (maintainer) [mailto:sjrs456ATyahooDOTfr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.isATgmailDOTcom]
* Carlos Sousa
* Luís Passos
* lokakuu
* alfalb (tradutor/revisor de prova) [mailto:alfredoDOTsilvaATskyDOTcom]
* Manuela Silva [mailto:manuelaPONTOsilvaAROBAskyPONTOcom]

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou através do IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente, pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada por e-mail ou na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controlo [http://git-scm.com/ Git] e os ficheiros atuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans Github].

Após terem obtido o(s) ficheiro(s) *.po(s) estes podem ser abertos com o editor preferido para começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal], são bons exemplos de programas de código aberto e plataforma múltipla que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o ''patch'' para o responsável pelo projeto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objetivos dos cenários e dos comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A exceção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Discurso direto===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (exceções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjetivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialeto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| transferir
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| noturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projeto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Soberano
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teófilo Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjetivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|-
| BW (Before Wesnoth)
| AW (Antes do Reino de Wesnoth)
|-
| AW (After Wesnoth)
| CW ([segundo a] Cronologia de Wesnoth / nas crónicas de Wesnoth)
|}

==Estado da tradução==

=== Lista de Traduções ===

A lista seguinte, pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?version=master&package=&lang=pt Estatísticas da tradução]

[[WesnothTranslations]]

== Hiperligações Diversas ==

[[Category:Translations]]

Wml optimisation

2014-10-12T14:07:49Z

Trewe: /* The basics */

==The basics==
The first thing you need to know: '''If you have no problems with performance, then don't bother'''.
Any optimisation is supposed to help you in following situations:
* The game freezes for several seconds after each user action
* Your scenario loading time is longer than several minutes
* Your add-on codebase is larger than 5 megabytes

===What you should know next===
*[[PreprocessorRef#Preprocessor_directives|Macros]]
*[[EventWML]]
*[[EventWML#Custom_events|Custom events]]
*[[ConditionalActionsWML#.5Bwhile.5D|While loops]]

===How do I optimise my code?===

So, you've written your campaign, scenario or era and it works. Congratulations, but your work is far from over! If your campaign or scenario is big enough, you'll often notice that it runs very slowly, and you need to do something about it. Or maybe you have a powerful computer and you'd like to make sure that other, weaker machines won't have troubles with running your content. Or perhaps, you just want to learn how to write code that not only works, but is also efficient.

The first thing to know, since apparently it's not stressed enough, macros '''do not''' improve performance! Macros only make your code more readable and easier to maintain. Try to refrain from using big macros, and more importantly, avoid using macros inside macros (inside macros, inside macros... yes, I've seen it happen, and yes I've tried doing it myself when I was new to wml). Under the covers, WML macros are replaced by the code they represent, and if there are macros inside macros (especially big ones), lines of code multiply horribly fast.

What's a better way to write code that appears often? ''Custom events''' and ''while loops''! By defining a '''custom event''', and firing it when needed, you'll save a lot of code lines, make your code nicer to read and much more efficient. Same goes for the '''while loop''': instead of copy/pasting your code, try to use a loop, whenever you can. Let's take a look at this example problem: whenever side 1 unit enters a village, you want to place 5 walking corpses around this village. Let's say there are 6 villages in question with coordinates (1,1), (2,2), (3,3), (4,4), (5,5), (6,6).

====Inefficient example====

#NOTE: remember, this should work alright, but it is not efficient! Imagine if you have much more villages in mind, or you want to spawn more zombies

#define SPAWN_ZOMBIES X Y SIDE
[unit]
side={SIDE}
type=Walking Corpse
x,y={X},{Y}
placement=map_passable
[unit]
[unit]
side={SIDE}
type=Walking Corpse
x,y={X},{Y}
placement=map_passable
[unit]
[unit]
side={SIDE}
type=Walking Corpse
x,y={X},{Y}
placement=map_passable
[unit]
[unit]
side={SIDE}
type=Walking Corpse
x,y={X},{Y}
placement=map_passable
[unit]
[unit]
side={SIDE}
type=Walking Corpse
x,y={X},{Y}
placement=map_passable
[unit]
#enddef

[event]
name=moveto
[filter]
side=1
x,y=1,1
[or]
x,y=2,2
[/or]
[or]
x,y=3,3
[/or]
[or]
x,y=4,4
[/or]
[or]
x,y=5,5
[/or]
[or]
x,y=6,6
[/or]
[/filter]

{SPAWN_ZOMBIES $unit.x $unit.y 2}
[/event]

Looks pretty innocent, right? But imagine that there are more villages. Or better yet, imagine you want to increase the amount of zombies, you'll have to copy/paste even more, and it's easy to make a mistake while doing it.

====More efficient example====

#first, let's define our custom event:
[event]
name=spawn_zombies
first_time_only=no
#it's easy to forget, but you have to set first_time_only in custom events too
{VARIABLE i 0}
[while]
[variable]
name=i
less_than_equal_to=5
#repeating the loop 5 times for 5 zombies, note how easy it is now to change the amount of zombies you want to spawn!
[/variable]
[do]
[unit]
side=2
type=Walking Corpse
x,y=$unit.x,$unit.y
#unit variable is passed to this event from the parent event.
placement=map_passable
[unit]
{VARIABLE_OP i add 1}
[/do]
[/while]
{CLEAR_VARIABLE i}
[/event]

[event]
name=moveto
[filter]
side=1
x,y=1,1
[or]
x,y=2,2
[/or]
[or]
x,y=3,3
[/or]
[or]
x,y=4,4
[/or]
[or]
x,y=5,5
[/or]
[or]
x,y=6,6
[/or]
[/filter]

[fire_event]
name=spawn_zombies
[/fire_event]
[/event]

===Fired events vs macros===

But if ''fire events'' are so cool and efficient, what is the advantage of using ''macros''? Good question. As you can see, custom events have one issue: ''it's harder to set dynamic variables in fired events''. When defining macros, you specify arguments and those arguments are declared ''whenever we're using that macro'' and can be changed in any way you, and more importantly, someone else wants. Remember, that you might want to start a bigger project and invite someone to help you with the code. '''Macros are obvious and transparent in usage''' - when reading a macro definition you always know what is the changing variable and what is a constant. In custom events, it is not so obvious.

Let's take a look at one of the default macros included with wesnoth:

#define ABILITY_REGENERATES
# Canned definition of the Regenerate ability to be included in an [abilities]
# clause.
[regenerate]
value=8
id=regenerates
name= _ "regenerates"
female_name= _ "female^regenerates"
description= _ "Regenerates:
The unit will heal itself 8 HP per turn. If it is poisoned, it will remove the poison instead of healing."
affect_self=yes
poison=cured
[/regenerate]
#enddef

This is a good macro, because replacing it by a custom event would be complicated and messy and it wouldn't save a lot of code, anyway. Another example is

#define GENERIC_UNIT SIDE TYPE X Y
# Creates a generic unit of TYPE belonging to SIDE at X,Y, which has a
# random name, gender and traits (just like a recruited unit).
[unit]
side={SIDE}
type={TYPE}
x={X}
y={Y}
generate_name=yes
random_traits=yes
random_gender=yes
upkeep=full
[/unit]
#enddef

This time, making a custom event would be fairly easy, but it would be much less transparent in usage. The code {GENERIC_UNIT 1 Spearman 12 3} is self-explanatory, simple and versatile.

==Do not treat macroses as functions==
Main advantage of macroses is that they allow you to reuse your code with less effort. But you need to take into account how ''exactly'' they are used by Wesnoth. Look at the example

#define CREATE_REINFORCMENT SIDE
{VARIABLE temp_side {SIDE}}
[variable]
name = temp_side
value = 1
[/variable]
[if]
{VARIABLE_CONDITIONAL temp_side equals 1}
[then]
{GENERIC_UNIT 1 "Walking Corpse" 12 3}
[/then]
[/if]
[if]
{VARIABLE_CONDITIONAL temp_side equals 2}
[then]
{GENERIC_UNIT 2 "Spearman" 3 16}
[/then]
[/if]
{CLEAR_VARIABLE temp_side}
#enddef
[event]
name=turn 10
{CREATE_REINFORCMENT 1}
{CREATE_REINFORCMENT 2}
[/event]

In this example I wanted to create additional units for each side at turn 10. Side 1 is undeads and side 2 is loyalists. Everything looks good, but there is a mistake. When Wesnoth loads scenario, all macroses are substituted with their meaning. This example becomes:

[event]
name="turn 10"
[set_variable]
name="temp_side"
value=1
[/set_variable]
[if]
[variable]
equals=1
name="temp_side"
[/variable]
[then]
[unit]
generate_name=yes
random_gender=yes
random_traits=yes
side=1
type="Walking Corpse"
upkeep="full"
x=12
y=3
[/unit]
[/then]
[/if]
[if]
[variable]
equals=2
name="temp_side"
[/variable]
[then]
# PART 1 BEGINS
[unit]
generate_name=yes
random_gender=yes
random_traits=yes
side=2
type="Spearman"
upkeep="full"
x=3
y=16
[/unit]
# PART 1 ENDS
[/then]
[/if]
[clear_variable]
name="temp_side"
[/clear_variable]
[set_variable]
name="temp_side"
value=2
[/set_variable]
[if]
[variable]
equals=1
name="temp_side"
[/variable]
[then]
# PART 2 BEGINS
[unit]
generate_name=yes
random_gender=yes
random_traits=yes
side=1
type="Walking Corpse"
upkeep="full"
x=12
y=3
[/unit]
# PART 2 ENDS
[/then]
[/if]
[if]
[variable]
equals=2
name="temp_side"
[/variable]
[then]
[unit]
generate_name=yes
random_gender=yes
random_traits=yes
side=2
type="Spearman"
upkeep="full"
x=3
y=16
[/unit]
[/then]
[/if]
[clear_variable]
name="temp_side"
[/clear_variable]
[/event]

Obviously part 1 and part 2 will never happen. It makes conditional check useless while you code becomes more complex. This is very common mistake even in advanced scenarios and add-ons. To avoid this problem, you need to follow the rule: '''Do not make conditional actions based on values of arguments'''. If you need to do this, then you need to think over situation again. In our example it might be:

[event]
name=turn 10
{GENERIC_UNIT 1 "Walking Corpse" 12 3}
{GENERIC_UNIT 2 "Spearman" 3 16}
[/event]

==Analogies to "real" programming==

Now that you know how to use macros and custom events to optimise your code, let's take a moment to think how you could use your knowledge outside Wesnoth. You've probably heard about c++, python, lua or any other programming language. Just like them, WML has some common features but under slightly different names. For example, instead of making custom ''events'', you're making custom ''functions'' and ''procedures'' that can be used further in your code in a very similar way. That's why understanding optimisation is so important - it'll help you understand real programming problems, and develop good habits!

==Further reading==

*[http://wiki.wesnoth.org/Advanced_Optimisations_and_Hacks More complex optimisations] - read this only if you believe you know everything!
*[http://www.wesnoth.org/macro-reference.xhtml Macro reference]
*[[LuaWML]]
*[[ConventionsWML]]

[[Category:WML_Tips]]

ShroudDataWML

2014-04-24T14:43:53Z

Trewe: /* Making 'shroud_data' */ Don't call it "M$" and added note about fog

= Making 'shroud_data' =

As pointed out in [[SideWML]] you can add the key shroud_data to a [side] tag to describe what parts of the map should be shrouded for a side and what parts not. This comes in handy when you need to unshroud a large part of the map from the start of the game. When you would use the [remove_shroud] tag for that purpose (eg in the prestart event) you would have to a list of x,y coordinates and this can become somewhat lengthy, and it's difficult to find out what coordinates need to be set.

This tutorial is going to make a file containing the data that will unshroud those parts of the map you'd like to see unshrouded.
All you need is:
* the wesnoth map editor
* your favorite text editor (with a search & replace function)
* a spreadsheet like Microsoft Excel or Libreoffice Calc

== Making your map ==
First of all you will need a map. This can be made in the wesnoth map editor (see [[BuildingMaps]] for more information)
Once you've got that, make a copy. If you like to, you can renaim this copy to eg MapName_Shroud to indicate this file will contain the shroud data.

== Selecting what tiles will be unshrouded + flipping the map ==
(Open MapName_Shroud again in the editor if you closed it)
You can now select the tiles in the editor you want to be unshrouded. Hold shift and click left to (un)select a single tile and hold shift+alt and click left to select adjecent terrain tiles of the same type.
Now fill your selection with one terrain type, and then select all the other tiles and fill it with another type.

Once that's done, you can save again and quit the editor.

Import the file in your spreadsheet (in Openoffice.org: Insert->Sheet From File) and select the comma as seperator. You should see an example of what it will look like, if each lettercombination has it's own cell, then things are good.
Select all of the cells and press ctrl+x (Edit->Cut). Then select the top left most cell on the sheet and right click in it. Select 'Paste special'. A dialog window appears. There should be a checkbox name 'transpose', check it.
Now you've switched the rows and columns in the map. Select all of your cells again and press ctrl+c (Edit->Copy).
Open your favorite text editor and press ctrl+v in a new file. Save this file over your MapName_Shroud file.

== Rewriting the data of the map ==
(Open MapName_Shroud in your text editor if you closed it)
Now you'll see a (text) table containing the map data. You should see only two letter combinations are present, one for the shrouded part and one without. Use search and replace to search for the 'unshroud' letter combination (include leading and trailing spaces) and replace it with a '1' (without quotes). Then do the same for the 'shroud' combination and replace it with a '0'.
Make sure nothing separates the zeros from the ones.
Once All that is done you only need to add a pipe in front of each line in this file. The result should look something like this:

|000000000000000000
|000000000000000000
|000000000000000000
|000001111111000000
|000001111111000000
|000001111111000000
|000001111111000000
|000001111111000000

Save the file and reference it in you scenario .cfg-file like this (make sure the quotes are present, if not this will break the file):

[side]
...
shroud_data="{@url/MapName_Shroud}"
...
[/side]

Happy Unshrouding!

=== Footnote ===
{{DevFeature1.11}} The same holds true for setting fog in scenarios (though of limited use), just replace ''shroud_data'' with ''fog_data'' in the side definition.

[[Category:Create]]

PortugueseContinentalTranslation

2014-02-21T13:10:20Z

Trewe: /* Lista de Traduções */ fix broken link

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar ativamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Ativos====

* trewe (maintainer) [mailto:sjrs456ATyahooDOTfr]
* alfalb (tradutor/revisor de prova) [mailto:alfredoDOTsilvaATskyDOTcom]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.isATgmailDOTcom]
* Carlos Sousa
* Luís Passos
* lokakuu

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou através do IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente, pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada por e-mail ou na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controlo [http://git-scm.com/ Git] e os ficheiros atuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans Github].

Após terem obtido o(s) ficheiro(s) *.po(s) estes podem ser abertos com o editor preferido para começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal], são bons exemplos de programas de código aberto e plataforma múltipla que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o ''patch'' para o responsável pelo projeto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objetivos dos cenários e dos comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A exceção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Discurso direto===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (exceções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjetivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialeto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| transferir
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| noturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projeto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Soberano
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teófilo Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjetivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|-
| BW (Before Wesnoth)
| AW (Antes do Reino de Wesnoth)
|-
| AW (After Wesnoth)
| CW ([segundo a] Cronologia de Wesnoth / nas crónicas de Wesnoth)
|}

==Estado da tradução==

=== Lista de Traduções ===

A lista seguinte, pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?version=master&package=&lang=pt Estatísticas da tradução]

[[WesnothTranslations]]

== Hiperligações Diversas ==

[[Category:Translations]]

PortugueseContinentalTranslation

2014-01-26T20:26:43Z

Trewe: /* Equipa da tradução */

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

* trewe (maintainer) [mailto:sjrs456ATyahooDOTfr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.isATgmailDOTcom]
* Carlos Sousa
* Luís Passos
* lokakuu

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controllo [http://git-scm.com/ Git] e os ficheiros actuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans Github].

Após terem obtido o(s) ficheiro(s) *.po(s) estes podem ser abridos com o editor preferido para começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o patch para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teofólio Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|-
| BW (Before Wesnoth)
| AW (Antes do Reino de Wesnoth)
|-
| AW (After Wesnoth)
| CW ([segundo a] Cronologia de Wesnoth / nas crónicas de Wesnoth)
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

[[Category:Translations]]

WesnothTranslations

2014-01-26T20:25:18Z

Trewe: /* Translations */ anti-spam and reordered alfabethicaly

== 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]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: 楊綮銘 (Taiwan) - [mailto:steven2880ATgmailDOTcom]
* [[CroatianTranslation|Croatian]] - maintainer: Ivica Đurenec (charlieh65) - [mailto:ivicaDOTdurenecATgmailDOTcom]
* [[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]
* [[EnglishGBTranslation|English (GB)]] - maintainer: 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: Jarkko Patteri (Jarkko) - [mailto:jarkkopatteriATgmailDOTcom], Samu Voutilainen (Smar) - [mailto:samu.voutilainenATgmailDOTcom]
* [[FrenchTranslation|French]] - maintainer: Guillaume Pascal (Haldric) - Please use the 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: Farkas János - [mailto:mailDOTjanosDOTfarkasATgmailDOTcom]
* [[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: Antonio Rosella - [mailto:arosellaATyahooDOTcom]
* [[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: Espreon - [mailto:Majora700ATgmaillDOTcom]
* [[PolishTranslation|Polish]] - maintainer: position vacant
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Diego Inácio Goergen - [mailto:thegoergenATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese (European)]] - maintainer: trewe [mailto:sjrs456ATyahooDOTfr]
* [[RACVTranslation|RACV]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[RomanianTranslation|Romanian]] - maintainer: Alexandru Szasz [mailto:alexxedATgmailDOTcom]
* [[RussianTranslation|Russian]] - maintainer: Victor Sergienko [mailto:singalenATgmailDOTcom]
* [[Scottish_Gaelic_Translation|Scottish Gaelic]] - maintainer: GunChleoc- [mailto:fiosAIGforamnagaidhligDOTnet]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[SlovakTranslation#Preklad|Slovak]] - maintainer: Aceman
* [[SlovenianTranslation|Slovenian]] - maintainer: Klemen Košir (nNa) - [mailto:klemen913ATgmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: no one (contact Espreon for information [mailto:Majora700ATgmailDOTcom])
* [[SwedishTranslation|Swedish]] - maintainer: Niklas Bolmdahl (dacovale) - [mailto:wesnothATniklasDOTbolmdahlDOTcom]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[UkrainianTranslation|Ukrainian]] - maintainer: robson - [mailto:arobsonATyandexDOTru]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Huynh Yen Loc (hhyloc) - [mailto:nightgaunt13ATgmailDOTcom]

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

InterfaceActionsWML

2014-01-26T20:21:08Z

Trewe: /* [inspect] */ corrected obsolete info

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

Part of [[ActionWML]], interface actions are actions that do not have a direct 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.

== [inspect] ==
This user interface instantly displays the gamestate inspector dialog at the current scenario state (the same one that can be brought up with [[CommandMode|the ''':inspect''' command]]), which can be used to inspect the values of WML variables, AI configuration, recall lists, and more.

* '''name''': optional attribute to specify the name of this gamestate inspector dialog. It is just a label to help differentiate between different invocations of gamestate inspector dialog.

== [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]:
* [[StandardUnitFilter]]: The unit whose profile and name are displayed. Do not use a [filter] tag. If no unit matching this filter is found, the message is not displayed (The unit has probably been killed).<br>'''[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. You may specify as the value of the speaker attribute a unit id or any of the following special values:
** '''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 ''' " ''')
* '''[show_if]''': if present then this message will only be displayed if the conditional statement in this tag is passed (see [[ConditionalActionsWML#Condition_Tags|ConditionalActionsWML]])
* '''side_for''': (default: all sides) comma-separated list of sides for who message is shown. (Note: Don't use this if the message has options, as such message can only be shown to the current player.)
* '''image''': (default: profile image of speaker) the image to display next to the message. Append ~RIGHT() if you want the image to appear on the right side.
* '''caption''': (default: name of speaker) the caption to display beside the image. Name to be displayed. Note: use a translation mark to avoid wmllint errors.
* '''scroll''': Boolean specifying whether the game view should scroll to the speaking unit. Defaults to ''yes''.
* '''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.
* '''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]''': No '''[option]''' elements have to be used. 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 [[ConditionalActionsWML#Condition_Tags|ConditionalActionsWML]])
** '''[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_length''': the maximum number of characters that may be typed into the field
** '''text''': text that is written into the field in the beginning
* Check [[EventWML#Multiplayer_safety]] to find out in which events you can safely use '''[option]''' and '''[text_input]''' without causing OOS.

=== Formatting ===
In 1.8, [http://developer.gnome.org/pango/unstable/PangoMarkupFormat.html Pango markup formatting codes] have been adopted for '''[message]'''. These can also be used in unit names (user_description), objectives, and such. Note that you'll probably want to use a single quote ' instead of a double quote " as double quotes cannot be escaped, otherwise the string will appear fragmented and you may also encounter errors. Running wmllint on your campaign will up-convert it, warning you about unusual cases you must fix by hand.

For example, if you wanted to write "You are victorious!" in large, italic, gold letters, you might write it this way:

<nowiki><span color='#BCB088' size='large' font-style='italic'>You are victorious!</span></nowiki>

These are the codes taken from the Pango markup formatting guide:

*'''font''', '''font_desc''': A font description string, such as "Sans Italic 12".
*'''font_family''', '''face''': A font family name.
*'''font_size''', '''size''': Font size in 1024ths of a point, or one of the absolute sizes 'xx-small', 'x-small', 'small', 'medium', 'large', 'x-large', 'xx-large', or one of the relative sizes 'smaller' or 'larger'.
*'''font_style''', '''style''': One of 'normal', 'oblique', 'italic'.
*'''font_weight''', '''weight''': One of 'ultralight', 'light', 'normal', 'bold', 'ultrabold', 'heavy', or a numeric weight.
*'''font_variant''', '''variant''': One of 'normal' or 'smallcaps'.
*'''font_stretch''', '''stretch''': One of 'ultracondensed', 'extracondensed', 'condensed', 'semicondensed', 'normal', 'semiexpanded', 'expanded', 'extraexpanded', 'ultraexpanded'.
*'''foreground''', '''fgcolor''', '''color''': An RGB color specification such as '#00FF00' or a color name such as 'red'.
*'''background, bgcolor''': An RGB color specification such as '#00FF00' or a color name such as 'red'.
*'''underline''': One of 'none', 'single', 'double', 'low', 'error'.
*'''underline_color''': The color of underlines; an RGB color specification such as '#00FF00' or a color name such as 'red'.
*'''rise''': Vertical displacement, in 10000ths of an em. Can be negative for subscript, positive for superscript.
*'''strikethrough''': 'true' or 'false' whether to strike through the text.
*'''strikethrough_color''': The color of strikethrough lines; an RGB color specification such as '#00FF00' or a color name such as 'red'
*'''fallback''': 'true' or 'false' whether to enable fallback. If disabled, then characters will only be used from the closest matching font on the system. No fallback will be done to other fonts on the system that might contain the characters in the text. Fallback is enabled by default. Most applications should not disable fallback.
*'''letter_spacing''': Inter-letter spacing in 1024ths of a point.
*'''gravity''': One of 'south', 'east', 'north', 'west', 'auto'.
*'''gravity_hint''': One of 'natural', 'strong', 'line'.

In 1.6, Wesnoth uses older text formatting options
* 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.

Attributes of '''[objectives]''':
* '''side''': Default '0'. The side to set the objectives for. A value of 0 sets objectives for all sides. note: There are side-specific objectives and default objectives, which are used in case a side doesn't have specific ones. Specifying 0 sets the default ones.
* '''[[StandardSideFilter]]''' {{DevFeature1.11}} tags and keys: Sets the objectives of all matching sides to these passed specifications (the rest of this [objectives] tag). If no sides (such as when passing side=0) or all sides match, sets the default objectives, and the side specific ones for the matching sides otherwise.
* '''bullet''': Default '• '. Replaces the default bullet, with whatever is passed, for all objectives, gold carryover notes, and notes defined with [note].
* '''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.
* '''gold_carryover_string''': Default ' _ "Gold carryover:"', this text precedes the gold carryover information.
* '''notes_string''': Default ' _ "Notes:"', this text precedes the notes.
* '''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.
** '''bullet''': Default '• ' or whatever is set in the parent [objectives] block. Replaces the default bullet, with whatever is provided, for the objective defined by the [objective] block.
** '''red''': Default '0' for winning objectives, '255' for losing objectives. Overrides the default red coloring of the entire objective, including the bullet.
** '''green''': Default '255' for winning objectives, '0' for losing objectives. Overrides the default green coloring of the entire objective, including the bullet.
** '''blue''': Default '0'. Overrides the default blue coloring of the entire objective, including the bullet.
** '''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'')
** '''show_turn_counter''': If set to yes, displays the number of turns remaining in the scenario. Default is no.
** '''[show_if]''': A condition that disables the objective if it doesn't hold. Conditional objectives are refreshed at '''[show_objectives]''' time only.
* '''[gold_carryover]''': describes how the gold carryover works in this scenario. This is intended to be a more convenient way of displaying carryover information than using the note= key in [objectives].
** '''bullet''': Default '• ' or whatever is set in the parent [objectives] block. Replaces the default bullet with whatever is provided.
** '''red''': Default '255'. Overrides the default red coloring of the entire objective, including the bullet.
** '''green''': Default '255'. Overrides the default green coloring of the entire objective, including the bullet.
** '''blue''': Default '192'. Overrides the default blue coloring of the entire objective, including the bullet.
** '''bonus''' (boolean): whether an early finish bonus is granted. If omitted, early finish bonus is not mentioned.
** '''carryover_percentage''': the amount of carryover gold. If omitted, the amount is not mentioned.
* '''[note]''': describes a note, usually used for hints or additional information. This is an easier way of adding several notes than concatenating them together into a single string to use with the ''note='' key.
** '''bullet''': Default '• ' or whatever is set in the parent [objectives] block. Replaces the default bullet with whatever is provided for the note defined by the [note] block.
** '''red''': Default '255'. Overrides the default red coloring of the entire note, including the bullet.
** '''green''': Default '255'. Overrides the default green coloring of the entire note, including the bullet.
** '''blue''': Default '255'. Overrides the default blue coloring of the entire note, including the bullet.
** '''description''': the text of the note.
** {{DevFeature1.11}} '''[show_if]''': The note will not be shown if the specified condition isn't met. Conditional notes are refreshed at '''[show_objectives]''' time only.

== [set_menu_item] ==
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.
The user can also assign hotkeys to these WML commands unless specified otherwise. When the hotkey is pressed the event fill be fired/filtered at the current mouse position.

'''Note:''' Due to limitations in portable devices where there are no scroll bars for context menus, there is a hard-coded limit of 7 custom WML menu items. If you really need to have more than 7 menu items, try combining some of them in a submenu.

* '''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.
* '''use_hotkey''' {{DevFeature1.11}}: if ''no'' (default ''yes''), then the user cannot assign hotkeys to this menu item. If ''only'', the menu item is only accessible via hotkeys, not via right-click context; you can use this in combination with [default_hotkey] if you want custom hotkeys in your campaign/mp.
* '''[show_if]''': If present, the menu item will only be available if the conditional statement (see [[ConditionalActionsWML#Condition_Tags|ConditionalActionsWML]]) 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.
* '''[default_hotkey]''' {{DevFeature1.11}}: contains a hotkey WML to specify what hotkey to assign to this, '''if the user has no hotkey assigned to this yet'''. (Unlike the rest of a menu item definition, modifying this tag has no effect on the game; it is only effective when initially defining a menu item.) Hotkey WML matches the format in the preferences file and contains the following keys:
** '''key''': a string that contains the key to assign to this.
** '''alt''', '''shift''', '''cmd'''(apple only), '''ctrl''': boolean values.
* '''[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.
** '''delayed_variable_substitution ''' {{DevFeature1.11}} (boolean yes|no, default: yes): If no, forces a variable substitution run onto the wml included in this [command] block. Use this, if you want variables which are to substitute to get the values they have at execution time of the event where this set_menu_item appears. Other than that, they get the values they have at invocation time of the menu item.

== [clear_menu_item] ==
{{DevFeature1.11}}

Removes a menu item from the scenario.
Normally menu items are, including all their defining wml, automatically carried over between scenarios. This tag prevents this. (The behavior is comparable to set_variable/clear_variable).
* '''id''': (string): id of the menu item to clear. Can be a comma-separated list.

== 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. <tt>''('''Hint:''' There are a number of predefined items that are used in various campaigns that you can make use of. You can find [http://www.wesnoth.org/macro-reference.xhtml#file:items.cfg a list of them] if you look into the items.cfg file in the wesnoth install directory (under /data/core/macros).)''</tt>
* '''x''', '''y''': the location to place the item. (only for [event][item]: full [[StandardLocationFilter|SLF]] support)
* '''image''': the image (in ''images/'' as .png) to place on the hex. This image is aligned with the top-left of the hex (which is 72 pixels wide and 72 pixels tall). It is drawn underneath units. ''('''Hint:''' If using an image smaller than 72x72, then it might be useful to [[ImagePathFunctionWML#Blit_Function|BLIT]] the image onto <tt>misc/blank-hex.png</tt> (a blank 72x72 image).)''
* '''halo''': an image to place centered on the hex. It is drawn on top of units. Use this instead of ''image'' if the image is bigger than the hex or if you want to animate an image.
''Example (where the integer after the colon is the duration of each frame or square bracket expansion as per AnimationWML is used): halo=scenery/fire1.png:100,scenery/fire2.png:100,scenery/fire3.png:100,scenery/fire4.png:100,scenery/fire5.png:100,scenery/fire6.png:100,scenery/fire7.png:100,scenery/fire8.png:100''
or equivalently (requires Wesnoth 1.11.2+):
''halo=scenery/fire[1~8].png:100''
* '''team_name''': name of the team for which the item is to be displayed (hidden for others). For multiple teams just put all the names in one string, for example separated by commas.
* '''visible_in_fog''': whether the item should be visible through fog or not. Default yes.
* '''redraw''': {{DevFeature1.11}}(boolean yes|no, default: yes): If no, disables implicit calls to [[InterfaceActionsWML#.5Bredraw.5D|[redraw]]] when placing the items.

=== [remove_item] ===
Removes any graphical items on a given hex.
* [[StandardLocationFilter]]: the hexes to remove items off
* '''image''' if specified, only removes the given image item (This image name must include any [[ImagePathFunctionWML|image path functions]] appended to the original image name.)

=== [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-separated list of x locations to move along
* '''y''': a comma-separated list of y locations to move along (x and y values are matched pairs)
* '''side''': the side of the fake unit, used for team-coloring the fake unit
* '''gender''': the gender of the fake unit. Example: gender=female
* '''variation''': the variation of the fake unit. Example: variation=undead
* '''image_mods''': [[ImagePathFunctionWML|image path functions]] sequence to be applied on the fake unit.
* {{DevFeature1.11}} '''force_scrolling''': Whether to scroll the map or not even when [[#.5Block_view.5D|[lock_view]]] is in effect or ''Follow Unit Actions'' is disabled in ''Advanced Preferences''. Defaults to ''yes'' starting with version '''1.11.6'''; the attribute did not exist in previous versions and this action behaved as if ''no'' was passed instead.

=== [move_units_fake] ===
moves multiple images of units along paths on the map. These units are moved in lockstep.
* '''[fake_unit]''': A fake unit to move
** '''type''': the type of unit whose image to use
** '''x''': a comma-separated list of x locations to move along
** '''y''': a comma-separated list of y locations to move along (x and y values are matched pairs)
** '''side''': the side of the fake unit, used for team-coloring the fake unit
** '''skip_steps''': the number of steps to skip before this unit starts moving
=== [hide_unit] ===
Temporarily prevents the engine from displaying the given unit. The unit does not become invisible, as it would be with the '''[hides]''' ability; it is still the same plain unit, but without an image. Useful in conjunction with '''[move_unit_fake]''': to move a leader unit into position on-screen. Until 1.8 each '''[hide_unit]''' tag only hides one unit.
* [[StandardUnitFilter]]: All matching units will be hidden

=== [unhide_unit] ===
Stops the currently hidden units from being hidden.
* [[StandardUnitFilter]]: Only the matching units will be unhidden

=== [lock_view] ===
{{DevFeature1.11}} Locks gamemap view scrolling for human players, so they cannot scroll the gamemap view until it is unlocked. WML or Lua actions such as '''[scroll_to]''' will continue to work normally, as they ignore this restriction; the locked/unlocked state is preserved when saving the current game.

This feature is generally intended to be used in cutscenes to prevent the player scrolling away from scripted actions.

=== [unlock_view] ===
{{DevFeature1.11}} Unlocks gamemap view scrolling for human players.

=== [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
* {{DevFeature1.11}} '''side''': the side or sides for which this should happen. By default, the [scroll] happens for everyone.
* {{DevFeature1.11}} '''[filter_side]''': a [[StandardSideFilter]] to select the sides for which this should happen. By default, the [scroll] happens for everyone.

=== [scroll_to] ===
Scroll to a given hex
* '''x''', '''y''': the hex to scroll to
* {{DevFeature1.11}} [[StandardLocationFilter]], do not use a [filter_location] sub-tag. If more than one location matches the filter, only the first matching location will be used.
* '''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.
* {{DevFeature1.11}} '''immediate''': whether to instantly warp to the target hex regardless of the scroll speed setting in Preferences (defaults to ''false'').
* {{DevFeature1.11}} '''side''': the side or sides for which this should happen. By default, the [scroll_to] happens for everyone.
* {{DevFeature1.11}} '''[filter_side]''': a [[StandardSideFilter]] to select the sides for which this should happen. By default, the [scroll_to] happens for everyone.

=== [scroll_to_unit] ===
Scroll to a given unit
* [[StandardUnitFilter]]
* '''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.
* {{DevFeature1.11}} '''immediate''': whether to instantly warp to the target hex regardless of the scroll speed setting in Preferences (defaults to ''false'').
* {{DevFeature1.11}} '''for_side''': the side or sides for which this should happen. By default, the [scroll_to_unit] happens for everyone.
* {{DevFeature1.11}} '''[for_side]''': a [[StandardSideFilter]] to select the sides for which this should happen. By default, the [scroll_to_unit] happens for everyone.

=== [select_unit] ===
Selects a given unit.
* [[StandardUnitFilter]]: The first unit found will be selected.
* '''fire_event''': whether a ''select'' event should be triggered or not (def. ''no''). (Note that select events aren't multiplayer save.)
* '''highlight''': whether the unit's current hex should be highlighted (def. ''yes'').

=== [sound]===
Plays a sound
* '''name''': the filename of the sound to play (in ''sounds/'' as .wav or .ogg)
* '''repeat''': repeats the sound for a specified additional number of times (default=0)
=== [sound_source] ===
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
* '''check_shrouded''': possible values "true" and "false" - if true the source will not play if its locations are shrouded
* '''x,y''': similar to x,y as found in a [[StandardLocationFilter]], these are the locations associated with the sound source
* '''fade_range''' (default = 3): distance in hexes that determines a "circular" area around the one specified by '''full_range''' where sound volume fades out linearly
* '''full_range''' (default = 14): distance in hexes that determines a "circular" area where source plays with full volume, relative to screen center
* '''loop''': number of times a sound sample should be looped if it stays visible. -1 means infinite (~65000)

=== [remove_sound_source] ===
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
===[volume]===
Changes the game volume to a percent of the preferences volume for the game being played. Values can go from 0 to 100:
* '''music''': Changes the music volume.
* '''sound''': Changes the sound volume.
=== [color_adjust]===
Tints the color of the screen.
* '''red''', '''green''', '''blue''': values from -255 to 255, the amount to tint by for each color
=== [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).
* '''clear_shroud''' (boolean yes|no, default no): If yes, clears fog and shroud around existing units. 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).
* '''[[StandardSideFilter]]''': the sides for which to recalculate fog and shroud.
* '''side''': If used (forces clear_shroud=yes), clears fog and shroud for that side.

=== [unit_overlay] ===
Sets an image that will be drawn over a particular unit, and follow it around
* [[StandardUnitFilter]]: All matching units will get the overlay (do not use [filter])
* '''image''': the image to place on the unit

=== [remove_unit_overlay] ===
removes a particular overlayed image from a unit
* [[StandardUnitFilter]]: The overlay will get removed from all matching units (do not use [filter])
* '''image''': the image to remove from the unit

=== [animate_unit] ===
Uses an animation of a unit to animate it on screen (if the unit has the corresponding animation).
* '''flag''': The key to find the custom animation in the unit description (see the '''[extra_anim]''' description in [[AnimationWML]]). Standard animations can be triggered with the following keywords: ''leading recruited standing idling levelout levelin healing healed poisoned movement defend attack death victory pre_teleport post_teleport''
* '''[filter]''' with a [[StandardUnitFilter]] as argument, 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. Takes a weapon filter as argument, see [[FilterWML]].
* '''[secondary_attack]''': Similar to '''[primary_attack]'''. May be needed to trigger a defense animation correctly, if there are more than one animations available for the defending unit.
* '''hits''': yes/no/hit/miss/kill: which according variation of a attack/defense animation shall be chosen (required)
* '''text''': a text to hover during the animation
* '''red''': red value for the text color (0-255)
* '''green''': green value for the text color
* '''blue''': blue value for the text color
* '''with_bars''': yes/no: whether to display the status bars during the animation (e.g. the hitpoint bar)
* '''[animate]''': a sub block with the same syntax as '''[animate_unit]''' except that the '''[filter]''' block is mandatory to find the unit. This block will find and animate another unit simultaneously.
* '''[facing]''': a [[StandardLocationFilter]] specifying what direction the unit should be facing when animated

=== [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.
* '''color''': color of the label. The format is r,g,b; r, g and b are numbers between 0 and 255.
* '''visible_in_fog''': whether the label should be visible through fog or not. Default yes.
* '''visible_in_shroud''': whether the label should be visible through shroud or not. Default no.
* '''immutable''': whether this label is protected from being removed or changed by players. Default yes.
=== [floating_text]===
Floats text (similar to the damage and healing numbers) on the given locations.
* [[StandardLocationFilter]]: the text will be floated on all matching locations simultaneously.
* '''text''': the text to display.

The default text color is <span style="color: #6b8cff;">'''#6b8cff'''</span>. To change the color, use [[#Formatting|Pango markup]]. For example:

<pre>
# Float some golden yellow text at 20,20.
[floating_text]
x,y=20,20
text="<span color='#cccc33'>" + _ "Your text here" + "</span>"
[/floating_text]
</pre>

=== [deprecated_message] ===
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.
=== [wml_message] ===
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. The log domain for it is '''wml''', and the '''debug/dbg''' log level is available for use with the '''logger''' attribute. Depending on the current log level ('''error''' by default), which may be changed with the in-game :log command, or the --log-<level>=wml command line switch, the messages are echoed to the in-game chat.
* '''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.

Note: As of 1.9.4/1.9.5 (r48805) the following "loggers" should work: If in [wml_message]: err/error, warn/wrn/warning, debug/dbg; using the :log command: Only the long forms error, warning, info and debug (this part gathered by trying rather than source inspecting). The long forms are most likely also the only ones working when starting wesnoth with --log-<level>=wml.
For log level warning or error (as during normal play), only wml_messages with logger error or warning display (for both). With logger info or debug, additionally wml_messages with logger info or debug display (for both).

=== [open_help] ===
Opens the in-game help.
* '''topic''': the id of the topic to open
=== [show_objectives] ===
refreshes the objectives defined by [objectives] and its [show_if] tags, and displays them. (It is also called whenever the user explicitly asks for the objectives; this matters only if the tag was overridden by a [[LuaWML#register_wml_action|Lua]] script.)
* '''side''': the side to show the objectives. If not set, all sides are used.
* '''[[StandardSideFilter]]''' {{DevFeature1.11}} tags and keys: Tag affects the matching sides instead of just all or the one given by the integer value of the side= key.

=== [chat] ===
Displays a message in the chat area.
* '''speaker''': (default="WML") A string for the name of the sender of the message.
* '''message''': The message that should be displayed.
* '''[[StandardSideFilter]]''' tags and keys as argument; if the same client controls multiple sides that match, then the message will only be displayed once.

== Useful Macros ==
There are some predefined macros that you find useful for interface actions. You can find a complete list along with a detailed explanation of how they work [http://www.wesnoth.org/macro-reference.xhtml here].
* '''{HIGHLIGHT_UNIT}''' Highlight a unit on the map. Use this to show important units
* '''{HIGHLIGHT_IMAGE}''' Places and highlights an image on the map. Use this to show important items or locations
* '''{SET_IMAGE}''' Places an image on the map which has no other function.
* '''{QUAKE <soundfile>}''' Creates a tremor-like screenshake and plays <soundfile>. For example, '''{QUAKE (rumble.ogg)}'''.
* '''{FLASH_WHITE}''' Flash the screen white momentarily. You can also replace WHITE with RED, BLUE or GREEN for a different colour.

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

[[Category: WML Reference]]
[[Category: ActionsWML]]

PortugueseContinentalTranslation

2013-11-27T18:34:25Z

Trewe: /* Calão do jogo */ dates in game

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

* trewe (maintainer) [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.is@gmail.com]
* Carlos Sousa
* Luís Passos
* lokakuu

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controllo [http://git-scm.com/ Git] e os ficheiros actuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans Github].

Após terem obtido o(s) ficheiro(s) *.po(s) estes podem ser abridos com o editor preferido para começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o patch para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teofólio Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|-
| BW (Before Wesnoth)
| AW (Antes do Reino de Wesnoth)
|-
| AW (After Wesnoth)
| CW ([segundo a] Cronologia de Wesnoth / nas crónicas de Wesnoth)
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

[[Category:Translations]]

PortugueseContinentalTranslation

2013-10-16T18:55:17Z

Trewe: /* Processo da Equipa de Português */ shortened section

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

* trewe (maintainer) [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.is@gmail.com]
* Carlos Sousa
* Luís Passos
* lokakuu

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controllo [http://git-scm.com/ Git] e os ficheiros actuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans Github].

Após terem obtido o(s) ficheiro(s) *.po(s) estes podem ser abridos com o editor preferido para começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o patch para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teofólio Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

[[Category:Translations]]

PortugueseContinentalTranslation

2013-10-16T18:51:09Z

Trewe: /* Estilos e vocabulário */ removed obsolete sections

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

* trewe (maintainer) [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.is@gmail.com]
* Carlos Sousa
* Luís Passos
* lokakuu

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controllo [http://git-scm.com/ Git] e os ficheiros actuais da tradução podem ser obtidos no repositório da github.

Em sistemas *nix:

Descarregar os ficheiros:
git clone git://github.com/trewe/wesn-pt-trans.git && cd wesn-pt-trans

ver o que pode ser editado:
git branch -a

Criar um branch local para editar:
git checkout -b my_branch <STARTING POINT>
:(onde <STARING POINT> é o nome da branch/tag da qual quiserem começar)

Abrir o(s) ficheiro(s) *.po(s) com o editor preferido e começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Aplicar o trabalho feito:
git commit -a -m 'updated translation'

Criar um patch:
git format-patch <PARENT> --stdout > my_translation.patch
:(parent é a branch da qual fizeram o fork)

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o patch para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teofólio Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

[[Category:Translations]]

PortugueseContinentalTranslation

2013-09-29T19:45:03Z

Trewe: /* Estado desconhecido */ added misterious user (appears in the repo history)

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

* trewe (maintainer) [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.is@gmail.com]
* Carlos Sousa
* Luís Passos
* lokakuu

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controllo [http://git-scm.com/ Git] e os ficheiros actuais da tradução podem ser obtidos no repositório da github.

Em sistemas *nix:

Descarregar os ficheiros:
git clone git://github.com/trewe/wesn-pt-trans.git && cd wesn-pt-trans

ver o que pode ser editado:
git branch -a

Criar um branch local para editar:
git checkout -b my_branch <STARTING POINT>
:(onde <STARING POINT> é o nome da branch/tag da qual quiserem começar)

Abrir o(s) ficheiro(s) *.po(s) com o editor preferido e começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Aplicar o trabalho feito:
git commit -a -m 'updated translation'

Criar um patch:
git format-patch <PARENT> --stdout > my_translation.patch
:(parent é a branch da qual fizeram o fork)

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o patch para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Que norma ortográfica?===

Todo o trabalho corrente é baseado na norma de 1911.

A livre escolha de cada tradutor. Apesar de ser verdade que agora existe um «acordo ortográfico» (em vigor no Brasil deste 2004 e em Portugal 2009); é utópico pensar que a língua utilizada nos países lusófonos mude de alguma forma. Haverá sempre diferenças nos diferentes dialectos até porque <b>não</b> existe uma coisa como «português padrão».

Para se ter uma ideia, o acordo muda cerca de 4% do vocabulário do português europeu e pouco menos de 3% do brasileiro.

===O uso do «você»===

Nunca. O utilizador é referido na segunda pessoa do singular. (Sempre no presente do indicativo e com o pronome omitido)

E nos diálogos a preferência vai para a 2ª pessoa (singular como plural).

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teofólio Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

[[Category:Translations]]

DirectActionsWML

2013-06-23T12:41:57Z

Trewe: /* [recall] */ special case: multiple leaders scenario

{{WML Tags}}
== Direct actions ==

Direct actions are actions that have a direct effect on gameplay. They can be used inside of [[EventWML|events]].

The following tags are actions:

=== [endlevel] ===
Ends the scenario.
* '''result''': before the scenario is over, all events with ''name=result'' are triggered. If ''result=victory'', the player progresses to the next level (i.e., the next scenario in single player); if ''result=defeat'', the game returns to the main menu.

When the result is "victory" the following keys can be used:
* '''bonus''': whether the player should get bonus gold (maximum possible gold that could have been earned by waiting the level out). The default is bonus=yes.
* '''carryover_report''': whether the player should receive a summary of the scenario outcome, the default is carryover_report=yes.
* '''save''': whether a start-of-scenario save should be created for the next scenario, the default is save=yes. Do not confuse this with saving of replays for the current scenario.
* '''replay_save''': whether a replay save for the current scenario is allowed, the default is replay_save=yes. If yes, the player's settings in preferences will be used to determine if a replay is saved. If no, will override and not save a replay.
* '''linger_mode''': If ...=yes, the screen is greyed out and there's the possibility to save before advancing to the next scenario, the default is linger_mode=yes.
* '''reveal_map''': (Multiplayer only) (Default is 'yes') If 'no', shroud doesn't disappear when game ended.
* '''next_scenario''': (default specified in '''[scenario]''' tag) the ID of the next scenario that should be played. All units that side 1 controls at this point become available for recall in ''next_scenario''.
* '''carryover_percentage''': by default 80% of the gold is carried over to the next scenario, with this key the amount can be changed.
* '''carryover_add''': if true the gold will be added to the starting gold the next scenario, if false the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is false.
* '''music''': (default specified in '''[scenario]''' or '''[game_config]''' tags) a comma-separated list of music tracks from which one will be chosen and played once after any events related to the end of level result are executed; by default, victory_music is used on victory, and defeat_music on defeat.
* '''end_credits''': {{DevFeature1.11}} Whether to display the credits screen at the end of a single-player campaign. Defaults to ''yes''. Note that this has cumulative effects over the campaign - it persists even if the endlevel does not trigger the end of the campaign. See also [[CampaignWML]].
* '''end_text''': (translatable) Text that is shown centered in a black screen at the end of a campaign. Defaults to "The End". Note that this has cumulative effects over the campaign - it persists even if the endlevel does not trigger the end of the campaign. See also [[CampaignWML]].
* '''end_text_duration''': Delay, in milliseconds, before displaying the game credits at the end of a campaign. In other words, for how much time '''end_text''' is displayed on screen. Defaults to 3500. Note that this has cumulative effects over the campaign - it persists even if the endlevel does not trigger the end of the campaign. See also [[CampaignWML]].

=== [unit] ===
Places a unit on the map. For syntax see [[SingleUnitWML]].
* {{Short Note:Predefined Macro|GENERIC_UNIT}}
* '''to_variable''': spawn directly into a variable instead of on the map.

=== [recall] ===
Recalls a unit taking into account any [http://wiki.wesnoth.org/SingleUnitWML filter_recall] of the leader. The unit is recalled free of charge, and is placed near its leader, e.g., if multiple leaders are present, near the first found which would be able to normally recall it.

If neither a valid map location is provided nor a leader on the map would be able to recall it, the tag is ignored.

* [[StandardUnitFilter]]: the first matching unit will be recalled. If no units match this tag is ignored. Do not use a [filter] tag. If a comma separated list is given, every unit currently considered for recall is checked against all the types (not each single one of the types against all units).
* '''x,y''': the unit is placed here instead of next to the leader.
* '''show''': yes/no, default yes: whether the unit is animated (faded in) or instantly displayed
* '''fire_event''': boolean yes|no (default no); whether any according prerecall or recall events shall be fired.
* '''check_passability''': (boolean yes|no, default yes): If yes, checks for terrain passability when placing the unit (a nearby passable hex is chosen).

=== [teleport] ===
Teleports a unit on map. {{Short Note:Predefined Macro|TELEPORT_UNIT}}
* '''[filter]''': [[StandardUnitFilter]] the first unit matching this filter will be teleported.
* '''x,y''': the position to teleport to.
* '''clear_shroud''': should shroud be cleared on arrival
* '''animate''': should a teleport animation be played (if the unit doesn't have a teleport animation, it will fade out/fade in)
* '''check_passability''': (boolean yes|no, default yes): normally, units will not be teleported into terrain that is impassable for them. Setting this attribute to "no" permits it.

(Note: There is also a ability named teleport, see [[AbilitiesWML]].)

=== [terrain_mask] ===
Changes the terrain on the map. See [[TerrainMaskWML]].

=== [terrain] ===
Changes the terrain on the map.
* '''terrain''': the character of the terrain to use. See [[TerrainCodesWML]] to see what letter a type of terrain uses.
* [[StandardLocationFilter]]. This [[StandardLocationFilter]]'s terrain= key is used for the new terrain, filtering by terrain can be done with a nested [[StandardLocationFilter]]: [and]terrain=terrain_string_to_be_filtered_for.
* '''layer''': (overlay|base|both, default=both) only change the specified layer.
* '''replace_if_failed''': (default=no) When replacing just one layer failed, try to replace the whole terrain. If '''terrain''' is an overlay only terrain, use the default_base as base layer. If the terrain has no default base, do nothing.
Note: When a hex changes from a village terrain to a non-village terrain, and a team owned that village it loses that village. When a hex changes from a non-village terrain to a village terrain and there is a unit on that hex it does not automatically capture the village. The reason for not capturing villages it that there are too many choices to make; should a unit loose its movement points, should capture events be fired. It is easier to do this as wanted by the author in WML.

=== [gold] ===
Gives sides gold.
* '''amount''': the amount of gold to give.
* '''side''': (default=1) the number of the side to give the gold to. Can be a comma-separated list of sides. note: Default side=1 for empty side= is deprecated.
* [[StandardSideFilter]] {{DevFeature1.11}} tags and keys; default for empty side= is all sides, as usual in a SSF.
* '''[filter_side]''' with a [[StandardSideFilter]] as argument {{DevFeature1.11}}: [gold][filter_side] is deprecated, use the new inline SSF.

=== [unstore_unit] ===
Creates a unit from a game variable, and activates it on the playing field. This must be a specific variable describing a unit, and may not be an array -- to unstore an entire array, iterate over it. The variable is not cleared. See also [[InternalActionsWML#.5Bstore_unit.5D|[store_unit]]], [[ConditionalActionsWML#.5Bwhile.5D|[while]]] and [[InternalActionsWML#.5Bclear_variable.5D|[clear_variable]]].
* '''variable''': the name of the variable.
* '''find_vacant''': whether the unit should be placed on the nearest vacant tile to its specified location. If this is set to 'no'(default), then any unit on the same tile as the unit being unstored will be destroyed.
* '''check_passability''': (boolean yes|no, default yes): If yes, checks for terrain passability when placing the unit. This key has no effect if find_vacant=no (no check performed then). Before 1.9 this key is always "no".
* '''text''': (translatable) floating text to display above the unit, such as a damage amount
* '''red''', '''green''', '''blue''': (default=0,0,0) the color to display the text in. Values vary from 0-255. You may find it convenient to use the {COLOR_HARM} or {COLOR_HEAL} macro instead. (Use {COLOR_HARM} or {COLOR_HEAL} instead of the whole red,green,blue= line.)
* '''advance''': (default=true) if true the unit is advanced if it has enough XP. When modifying XP make sure to do it from inside a [[EventWML#Multiplayer_safety|synchronized event]] or it may lead to OOS errors especially when several advancement paths exist. Note that advance and post advance events are called, so infinite loops can happen.
* '''fire_event''': (boolean yes|no, default no) Whether any advance/post advance events shall be fired if an advancement takes place, no effect otherwise.
* '''animate''': {{DevFeature1.11}} (boolean yes|no, default yes) Whether "levelout" and "levelin" (or fade to white and back) animations shall be played if an advancement takes place, no effect otherwise.
* '''x''' ,'''y''': override unit location, "x,y=recall,recall" will put the unit on the unit's side's recall list.
Units can be unstored with negative (or zero) hit points. This can be useful if modifying a unit in its last_breath event (as the unit's death is already the next step), but tends to look wrong in other cases. In particular, it is possible to have units with negative hit points in play. Such units are aberrations, subject to unusual behavior as the game compensates for them. (For example, such units are currently automatically hit–and killed–in combat.) The details of the unusual behavior are subject to change between stable releases without warning.

=== [allow_recruit] ===
Allows a side to recruit units it couldn't previously recruit.
* '''type''': the types of units that the side can now recruit.
* '''side''': (default=1) the number of the side that is being allowed to recruit the units. This can be a comma-separated list note: Default side=1 for empty side= is deprecated.
* [[StandardSideFilter]] {{DevFeature1.11}} tags and keys; default for empty side= is all sides, as usual in a SSF.

=== [allow_extra_recruit] ===
Allows a leader to recruit units it couldn't previously recruit.
These types add to the types the leader can recruit because of [side]recruit=.
* '''extra_recruit''': the types of units that the unit can now recruit.
* '''[[StandardUnitFilter]]''': All units matching this filter are modified. Does not match on recall list units.

=== [disallow_recruit] ===
Prevents a side from recruiting units it could previously recruit.
* '''type''': the types of units that the side can no longer recruit.
* '''side''': (default=1) the number of the side that may no longer recruit the units. This can be a comma-separated list note: Default side=1 for empty side= is deprecated.
* [[StandardSideFilter]] {{DevFeature1.11}} tags and keys; default for empty side= is all sides, as usual in a SSF.

=== [disallow_extra_recruit] ===
Prevents a leader from recruiting units it could previously recruit.
* '''extra_recruit''': the types of units that the side can no longer recruit.
* '''[[StandardUnitFilter]]''': All units matching this filter are modified. Does not match on recall list units.

=== [set_recruit] ===
Sets the units a side can recruit.
* '''recruit''': the types of units that the side can now recruit.
* '''side''': (default=1) the number of the side that is having its recruitment set. This can be a comma-separated list. note: Default side=1 for empty side= is deprecated.
* [[StandardSideFilter]] {{DevFeature1.11}} tags and keys; default for empty side= is all sides, as usual in a SSF.

=== [set_extra_recruit] ===
Sets the units a leader can recruit.
* '''extra_recruit''': the types of units that the leader can now recruit.
* '''[[StandardUnitFilter]]''': All units matching this filter are modified. Does not match on recall list units.

=== [modify_side] ===
Modifies some details of a given side in the middle of a scenario. '''The following listed properties are the only properties that [modify_side] can affect!'''
* '''side''': (default=1) the number of the side that is to be changed. note: Default side=1 for empty side= is deprecated.
* '''[filter_side]''' with a [[StandardSideFilter]] as argument
* '''income''': the income given at the begining of each turn.
* '''recruit''': a list of unit types, replacing the side's current recruitment list.
* '''team_name''': the team in which the side plays the scenario.
* '''user_team_name''': a translatable string representing the team's description. This has no effect on alliances. Defaults to ''team_name''.
* '''gold''': the amount of gold the side owns.
* '''village_gold''': the income setting per village for the side.
* '''controller''': the identifier string of the side's controller. Uses the same syntax of the ''controller'' key in the [[SideWML|[side]]] tag.
* '''fog''': a boolean string (yes/no) describing the status of Fog for the side.
* '''shroud''': a boolean string describing the status of Shroud for the side.
* '''hidden''': a boolean string specifying whether side is shown in status table.
* '''color''': {{DevFeature1.11}} a team color range specification, name (e.g. "red", "blue"), or number (e.g. "1", "2") for this side. The default color range names, numbers, and definitions can be found in data/core/team_colors.cfg.
* '''[ai]''': replaces a side's AI parameters with the new specified ones. Uses the same syntax described in [[AiWML]]. Note that [modify_side][ai] works for all simple AI parameters and some, but not all of the more complex ones. If in doubt, use [http://wiki.wesnoth.org/AiWML#Adding_and_Deleting_Aspects_with_the_.5Bmodify_ai.5D_Tag [modify_ai]] instead, which always works.
* '''switch_ai''': replaces a side ai with a new AI from specified file(ignoring those AI parameters above). Path to file follows the usual WML convention.
* '''reset_maps''': {{DevFeature1.11}} If set to "yes", then the shroud is spread to all hexes, covering the parts of the map that had already been explored by the side, including hexes currently seen. (Seen hexes will be cleared at the end of most events; they can also be manually cleared with {{tag|InterfaceActionsWML|redraw}}.) This is only effective if shroud is on, but this is evaluated after shroud= (and before shroud_data=).
* '''reset_view''': {{DevFeature1.11}} If set to "yes", then the fog of war is spread to all hexes, covering the parts of the map that had already been seen this turn by the side, including hexes currently seen, excluding hexes affected by multi-turn {{tag|DirectActionsWML|lift_fog}}. (Seen hexes will be cleared at the end of most events; they can also be manually cleared with {{tag|InterfaceActionsWML|redraw}}.) This is only effective if fog is on, but this is evaluated after fog=.
* '''share_maps''': change the share_maps side attribute. Be sure to use shroud=yes for that side and have it as an ally
* '''share_view''': change the share_view side attribute. Be sure to use fog=yes for that side and have it as an ally
* '''shroud_data''': changes to the side's shroud, using the same format as when defining the [side].
* '''suppress_end_turn_confirmation''': {{DevFeature1.11}} Boolean value controlling whether or not a player is asked for confirmation when skipping a turn.

=== [modify_turns] ===
Modifies the turn limit in the middle of a scenario.
* '''value''': the new turn limit.
* '''add''': if used instead of ''value'', specifies the number of turns to add to the current limit (can be negative).
* '''current''': changes the current turn number after applying turn limit modifications, if any. It is not possible to change the turn number to exceed the turn limit (1 <= current turns <= max turns).

=== [allow_end_turn] ===
Allows human players to end their turn through the user interface if they were previously affected by the '''[disallow_end_turn]''' action. This action doesn't take any arguments.

=== [disallow_end_turn] ===
Disallows human players to end their turn through the user interface. This action doesn't take any arguments.

'''Note:''' on Wesnoth versions prior to 1.10.6, there are two bugs affecting this WML action. First, its effect was lost when reloading from a saved game ([https://gna.org/bugs/?20350 bug #20350]); second, its effect persisted when advancing scenarios in a campaign ([https://gna.org/bugs/?20351 bug #20351]).

A known workaround for both issues would be to use [[PreprocessorRef#.23ifver_and_.23ifnver|#ifver]]-based preprocessor macros to include additional code for Wesnoth 1.10.5 and earlier taking advantage of unique ''preload'', ''victory'', and ''defeat'' [[EventWML|event handlers]], such as the following:

#ifver WESNOTH_VERSION > 1.10.5

#define DISALLOW_END_TURN
[disallow_end_turn][/disallow_end_turn]
#enddef

#define ALLOW_END_TURN
[allow_end_turn][/allow_end_turn]
#enddef

#else

#define DISALLOW_END_TURN
[disallow_end_turn][/disallow_end_turn]

[event]
id=bug_20350_workaround
name=preload

[disallow_end_turn][/disallow_end_turn]
[/event]

[event]
id=bug_20351_workaround
name=victory,defeat

[allow_end_turn][/allow_end_turn]
[/event]
#enddef

#define ALLOW_END_TURN
[allow_end_turn][/allow_end_turn]

[event]
id=bug_20350_workaround
remove=yes
[/event]

[event]
id=bug_20351_workaround
remove=yes
[/event]
#enddef

#endif

=== [capture_village] ===
Changes the ownership of a village.
* [[StandardLocationFilter]]: all village locations matching the filter are affected.
* '''side''': the side that takes control of the village. This side needs to have a leader (canrecruit=yes). If the side key is not given, the village will become neutral (unless [filter_side] is present, in which case that side fiter decides, see below).
* '''[filter_side]''' with [[StandardSideFilter]] tags and keys as arguments; if both this tag and inline side= are present it's an error. Otherwise, the first matching side gets ownership (or the village becomes neutral if none match).
* '''fire_event''' (boolean yes|no, default: no): Whether any capture events shall be fired.

=== [kill] ===
Removes all units (including units in a recall list) that match the filter from the game.
* [[StandardUnitFilter]]: Selection criterion; do not use a [filter] tag.
* '''animate''': if 'yes', displays the unit dying (fading away).
* '''fire_event''': if 'yes', triggers any appropriate 'die' events (See [[EventWML]]). Note that events are only fired for killed units that have been on the map (as opposed to recall list).
* '''[secondary_unit]''' with a [[StandardUnitFilter]] as argument. Do not use a [filter] tag. Has an effect only if fire_event=yes. The first on-map unit matching the filter becomes second_unit in any fired die and last breath events. If an on-map unit matches and if there are several units killed with a single [kill] tag, second_unit is this same unit for all of them. If no on-map unit matches or [secondary_unit] isn't present, the variable second_unit in each of the die and last breath events is always the same as the variable unit (the dying unit).

=== [move_unit] ===
works like the MOVE_UNIT macro.
* [[StandardUnitFilter]] as argument; do not use a [filter] tag. All units matching the filter are moved. If the target location is occupied, the nearest free location is chosen.
* '''to_x''' (unsigned integer): The units are moved to this x coordinate. Can be a comma-separated list, in which case the unit follows this given path during the move.
* '''to_y''' (unsigned integer): The units are moved to this y coordinate. Can be a comma-separated list.
* '''fire_event''' (optional, boolean yes|no, default no): Whether any according moveto events shall be fired. The target location ($x1, $y1 in the event) may not be the same location that the unit was tried to be moved to, if the original target location is occupied or impassable.
* '''check_passability''' (boolean yes|no, default yes): Whether the terrain the unit is moved to should be checked for suiting the unit. (If it does not, a nearby suitable hex is chosen.)

=== [modify_ai] ===
Changes AI objects (aspects, goals, candidate actions or stages) for a specified side. See [[AiWML#Adding_and_Deleting_Aspects_with_the_.5Bmodify_ai.5D_Tag|AiWML]] for full description.

* '''action''' (string): Takes values 'add', 'change', 'delete' or 'try_delete' to do just that for the AI object.
* '''path''' (string): Describes which AI object is to be modified.
* '''[facet]''', '''[goal]''', '''[candidate_action]''' or '''[stage]''': Details about the AI object to be modified.
* [[StandardSideFilter]] {{DevFeature1.11}} tags and keys; default for empty side= is all sides, as usual in a SSF.
* '''[filter_side]''' with a [[StandardSideFilter]] as argument {{DevFeature1.11}}: [modify_ai][filter_side] is deprecated, use the new inline SSF.

=== [modify_unit] ===
works similar to the MODIFY_UNIT macro.
* '''[filter]''' with a [[StandardUnitFilter]] as argument. All units matching this filter are modified. Matches on recall list units too.
* Accepts generally the syntax inside of wml unit variables created by [store_unit] which can be viewed in a savefile or by using the :inspect command. Can add traits with immediate effect. Cannot remove things. Subtags with the same name must be written in the correct order to match them with the tag they are supposed to modify.
example usage (see also the test scenario):
[modify_unit]
[filter]
x,y=38,6
[/filter]
hitpoints=10
{TRAIT_HEALTHY}
[/modify_unit]

The unit which is currently modified is accessible via $this_unit, e.g. hitpoints = "$($this_unit.hitpoints / 2)" to set the hitpoints of all units to half of their particular maxima. This this_unit variable is independent from the this_unit variable available in the SUF used to determine which units to modify (first all matching units are gathered, and then all those are modified).

note: The syntax allowed is somehow vague. Just try things and possibly correct/add/modify this documentation. (a [http://forums.wesnoth.org/viewtopic.php?f=21&t=31676& forum thread] discusses some related issues).

=== [transform_unit] ===
Transforms every unit matching the filter to the given unit type. Keeps intact hit points, experience and status. If the unit is transformed to a non-living type (undead or mechanical), it will be also unpoisoned.
{{DevFeature1.11}} Hit points will be changed if necessary to respect the transformed unit's maximum hit points.
* [[StandardUnitFilter]]: do not use a [filter] tag.
* '''transform_to''': the unit type in which all the units matching the filter will be transformed. If missing, the units will follow their normal advancement.

=== [petrify] ===

* [[StandardUnitFilter]] as an argument. Do not use a [filter] tag. All units matching this filter are petrified. Recall list units are included.

=== [unpetrify] ===
* [[StandardUnitFilter]] as an argument. Do not use a [filter] tag. All units matching this filter are unpetrified. Recall list units are included.

=== [object] ===
Gives some unit an object which modifies their stats in some way.
* '''id''': (Optional) when the object is picked up, a flag is set for ''id''. The object cannot be picked up if a flag for ''id'' has been set. This means that any object with an id can only be used once, even if first_time_only=no is set for the event. This restriction is per level. In a campaign objects with the same id can be assigned once per level.
* '''delayed_variable_substitution''' (boolean yes|no, default no): If set to "yes", the wml block contained in this [object] is not variable-substituted at execution time of the event where this [object] is within. You need this to work around a bug when adding ABILITY_TELEPORT via an [object] or when using [object][effect][filter]with a $this_unit (see http://gna.org/bugs/index.php?18893).
* '''[effect]''': one or more effect elements may be listed. See [[EffectWML]] for a description of [effect].
* '''duration''':
**if 'level', effects only last until the end of the level (note : 'level' is the scenario, so this doesn't mean it last until the unit levels-up). {{DevFeature1.11}} 'level' has been renamed to 'scenario'.
**if 'forever' or not set, effects never wear off.
** {{DevFeature1.11}} if 'turn', effects only last until the start of the unit's next turn (when the unit refreshes movement and attacks). (Like other start-of-turn behavior, objects with a duration of "turn" won't expire before turn 2.)
* '''[filter]''' with a [[StandardUnitFilter]] as argument. The first unit found that matches the filter will be given the object. Only on-map units are considered. If no unit matches or no [filter] is supplied, it is tried to apply the object to the unit at the $x1,$y1 location of the event where this [object] is in. The case of no unit being at that spot is handled in the same way as no unit matching a given filter ([else] commands executed, cannot_use_message displayed)
* '''[then]''': a subtag that lets you execute actions if the filter conditions are met. The most common action that should be inside here is a '''[remove_item]''' tag, but you could probably put any tags that otherwise work in a [then] tag.
* '''[else]''': a subtag that lets you execute actions if the filter conditions are *not* met.
* '''silent''': whether or not messages should be suppressed. Default is "no".
* '''image''': the displayed image of the object.
* '''name''': (translatable) displayed as a caption of the image.

* '''description''': (translatable) displayed as a message of the image.
* '''cannot_use_message''': (translatable) displayed instead of '''description''' if no unit passes the filter test.

=== [remove_shroud] ===
Removes some shroud from the map for a certain side (only relevant for sides that have shroud=yes).
* '''side''': (default=1) the side for which to remove shroud. This can be a comma-separated list of sides. note: Default side=1 for empty side= is deprecated.
* '''[filter_side]''' with a [[StandardSideFilter]] as argument
* [[StandardLocationFilter]]: the range of tiles for which shroud should be removed

=== [place_shroud] ===
Places some shroud on the map for a certain side (only relevant for sides that have shroud=yes).
* '''side''': (default=1) the side for which to place shroud. This can be a comma-separated list. note: Default side=1 for empty side= is deprecated.
* '''[filter_side]''' with a [[StandardSideFilter]] as argument
* [[StandardLocationFilter]]: the range of tiles on which shroud should be placed

=== [lift_fog] ===
{{DevFeature1.11}}Lifts the fog of war from parts of the map for a certain side (only relevant for sides that have fog=yes), allowing a player to witness what occurs there even if that player has no units within vision range.
* '''[filter_side]''' with a [[StandardSideFilter]] indicating which sides should be affected.
* [[StandardLocationFilter]]: the tiles from which fog should be lifted.
* '''multiturn''': ''yes/no, default:no''. The default (not multiturn) causes fog to be removed in the same way that normal vision works; the cleared tiles will remain cleared until fog is recalculated (which normally happens when a side ends its turn). When multiturn is set to "yes", the cleared tiles remain clear until {{tag||reset_fog}} cancels the clearing. This allows tiles to remain clear for multiple turns, or to be refogged before the end of the current turn (without also refogging all tiles). Multiturn lifted fog is not shared with allies (even when share_view=yes).

=== [reset_fog] ===
{{DevFeature1.11}}The primary use of this tag is to remove multiturn lifted fog (created by {{tag||lift_fog}}), which causes the fog to reset to what it would have been had WML not interfered. (That is, hexes that a side's units could not see at any point this turn will be re-fogged, while seen hexes remain defogged.)
* '''[filter_side]''' with a [[StandardSideFilter]] indicating which sides should be affected.
* [[StandardLocationFilter]]: the fog reset will be restricted to these tiles.
* '''reset_view''': ''yes/no, default: no'' If set to "yes", then in addition to removing multiturn fog, the side's current view is canceled (independent of the SLF). This means that all hexes will become fogged for the side unless multiturn fog exists outside the tiles selected by the SLF. Normally, one would want the currently seen hexes to become clear of fog; this is done automatically at the end of many events, and it can be done manually with {{tag|InterfaceActionsWML|redraw}}.
Omitting both the SSF and the SLF would cancel all earlier uses of [lift_fog].
Additionally setting reset_view="yes" would cause the side's entire map to be fogged (unless an ally keeps hexes clear by sharing its view).

=== [allow_undo] ===

Normally when an event with a handler fires, the player's undo stack is cleared, preventing all actions performed so far from being undone. Including this tag in the event handler prevents the stack from being cleared for this reason, allowing the player to undo actions. (However, the stack might still be cleared for other reasons, such as fog being cleared or combat occurring.) In the common cases, this means '''[allow_undo]''' allows the current action to be undone even though an event was handled. There is a less common case, though — specifically when handling a menu item, where there is no current action — and in this case, '''[allow_undo]''' means merely that earlier actions can still be undone.
* {{DevFeature1.11}} Using this tag in a menu item has an additional side effect in 1.11. Starting with version 1.11.1, executing a WML menu item normally counts as doing something as far as the "you have not started your turn yet" dialog is concerned. However, a menu item whose handler includes '''[allow_undo]''' will not count.

This tag does nothing during recruit and recall actions, as the game incorrectly ignores whether or not an event fired during those times. {{DevFeature1.11}} This has been fixed in the latest development release.

The types of actions that can be undone are movement, recruitment, recalling, and dismissing a unit from the recall list. If an action is undone, only the position (or existence) of the involved unit will be restored; any altered variables or changes to the game will remain changed after the action is undone. It is up to the scenario designer to avoid abusing this command.
* Technically, if '''[allow_undo]''' is inside an '''[event]''' with ''first_time_only=yes'' (the default setting), and the user undoes the event, then the state of the game has changed in this way: the event will not fire a second time, even though the user undid the action the first time.

=== [heal_unit] ===
Heal a unit. The variable '''$heal_amount''' will be set to the exact number of points healed (i.e can be lesser than the parameter '''amount''' if the unit is fully healed). $heal_amount contains only the number of hitpoints the first unit that was found got healed.
* '''[filter]''': [[StandardUnitFilter]] All matching on-map units are healed. If no filter is supplied, it is tried to take the unit at $x1, $y1.
* '''[filter_second]''': [[StandardUnitFilter]] all the units matching the filter ''and'' having the ''heals'' ability will have their animation played (if ''animate'' is set to true) for each of the units healed.
* '''amount''': (integer, default full) the maximum points the unit(s) will be healed. Can't set below 1 or above max_hitpoints. If "full", sets hitpoints to max_hitpoints. Before 1.9 the default is 0.
* '''animate''': a boolean which indicate if the healing animations must be played. (default no)
* '''moves''': (integer, default 0) The maximum current movement points the units will be "healed". Can't set below 0 or above max_moves. If "full", sets moves to max_moves.
* '''restore_attacks''': (boolean, default no) Whether the units' attacks_left should be reset to their max_attacks (usually 1).
* '''restore_statuses''': (boolean, default yes) Whether standard statuses should be reset to "no". This affects poisoned, slowed, petrified and unhealable. Before 1.9 this is always "no".

=== [harm_unit] ===
Harms every unit matching the filter, for the specific damage amount.
* '''[filter]''': [[StandardUnitFilter]] all matching units will be harmed (required).
* '''[filter_second]''': [[StandardUnitFilter]] if present, the first matching unit will attack all the units matching the filter above.
* '''amount''': the amount of damage that will be done (required).
* '''alignment''': (default neutral) applies an alignment to the damage, this means that if alignment=chaotic, the damage will be increased at night and reduced at day.
* '''damage_type''': if present, amount will be altered by unit resistance to the damage type specified.
* '''kill''': (default yes) if yes, when a harmed unit goes to or below 0 HP, it is killed; if no its HP are set to 1.
* '''fire_event''': (default no) if yes, when a unit is killed by harming, the corresponding events are fired. {{DevFeature1.11}} If yes, also the corresponding advance and post advance events are fired.
* '''animate''': (default no) if yes, scrolls to each unit before harming it and plays its defense (or attack, if it's the harmer) and death animations. Special values supported, other than the usual yes and no, are "attacker", that means only the harmer will be animated, and "defender", that means only the harmed units will be animated. {{DevFeature1.11}} If the supplied value is yes, attacker or defender also advancement animations are played.
* '''[primary_attack], [secondary_attack]''': these set the weapon against which the harmed units will defend, and that the harming unit will use to attack, respectively (notice this is the opposite of '''[filter]''' and '''[filter_second]''' above). This allows for playing specific defense and attack animations. Both tags are expected to contain a [[FilterWML#Filtering_Weapons|Standard Weapon Filter]].
* '''delay''': if animate=yes, sets the delay (in milliseconds, default 500) between each unit harming.
* '''variable''': if present, the damage caused to the unit, altered by resistances, will be stored in a WML array with the given name, under the "harm_amount" key.
* '''poisoned, slowed, petrified, unhealable''': (default no) if yes, every harmed unit that doesn't already have such status will have it set.
* '''experience''': if yes, and there is a harmer, experience will be attributed like in regular combat.
* '''resistance_multiplier''': {{DevFeature1.11}} the harmed unit's resistance is multiplied by the supplied value; this means that a value lower than 1 increases it, and a value greater than 1 decreases it. Default value is 1, that means no modification.

=== [time_area] ===
How a day should progress in a given area. Everywhere not specified in a [time_area] tag is affected by the [time] tags in the [scenario] tag.
* [[StandardLocationFilter]]: the locations to affect. ''note: only for [event][time_area]s - at scenario toplevel [time_area] does not support [[StandardLocationFilter]], only location ranges''
* [[TimeWML]]: the new schedule.
* '''id''': an unique identifier assigned to a time_area. Optional, unless you want to remove the time_area later. Can be a comma-separated list when removing time_areas, see below.
* '''remove''': (boolean) yes/no value. Indicates whether the specified time_area should be removed. Requires an identifier. If no identifier is used, however, all time_areas are removed.

''Example:'' (caves in parts of a map)
[time_area]
x=1-2,4-5
y=1-2,1-2
{UNDERGROUND}
[/time_area]

=== [end_turn] ===
End the current side's turn. The current event is finished before the turn is ended. Also, if the current event (where the tag appears) has been fired by another event, that event (and the complete stack of other possible parent events) is ended before [end_turn] comes into affect. Also, events following the event stack that fired [end_turn] are not omitted (e.g. [end_turn] is used by a side turn event and a turn refresh event does something afterwards).

=== [replace_map] ===

Replaces the entire map.
* '''map''': Content of a wesnoth map file. example:
map="{campaigns/Heir_To_The_Throne/maps/01_The_Elves_Besieged.map}"
* '''expand''': if 'yes', allows the map size to increase. The expansion direction is currently always bottom-right.
* '''shrink''': if 'yes', allows the map size to decrease. If the map size is reduced, any units that would no longer be on the map due to its coordinates no longer existing will be put into the recall list.
Note: When a hex changes from a village terrain to a non-village terrain, and a team owned that village it loses that village. When a hex changes from a non-village terrain to a village terrain and there is a unit on that hex it does not automatically capture the village. The reason for not capturing villages it that there are too many choices to make; should a unit loose its movement points, should capture events be fired. It is easier to do this as wanted by the author in WML.

=== [replace_schedule] ===
Replace the time of day schedule of the entire scenario.
* [[TimeWML]]: the new schedule.

=== [tunnel] ===

Create a tunnel between some locations, later usable by units to move from source hex to target hex (using the movement cost of unit on the target terrain). ([http://forums.wesnoth.org/viewtopic.php?f=21&t=14749&p=405667&hilit=tunnel#p405667 source])

* '''id''' identifier for the tunnel, to allow removing (optional).
* '''remove''': (boolean) yes/no value. If yes, removes all defined tunnels with the same ID (then only id= is necessary). (default: no)
* '''bidirectional''': (boolean) if yes, creates also a tunnel in the other direction. (default: yes)
* '''always_visible''': (boolean) if yes, the possible movement of enemies under fog can be seen. (default: no)
* '''[source]''': [[StandardLocationFilter]] the source hex(es) (required).
* '''[target]''': [[StandardLocationFilter]] the target hex(es) (required).
* '''[filter]''': [[StandardUnitFilter]] the units which can use the tunnel (required). Leave empty for "all units".

(Note: The tunnel tag can also be used inside the [[AbilitiesWML|[teleport]]] ability, without remove= and id=).

== Useful Macros ==
There are some predefined macros that you find useful for direct actions. You can find a complete list along with a detailed explanation of how they work [http://www.wesnoth.org/macro-reference.xhtml here].
* '''{MOVE_UNIT}''': Moves a unit to another location in the map and the player sees the movement (unlike [teleport])
* '''{FULL_HEAL}''': Brings a unit to full HP
* '''{LOYAL_UNIT}''': Create a loyal unit
* '''{MODIFY_TERRAIN_MASK}''': Modify an area of terrain

== See Also ==

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

[[Category: WML Reference]]
[[Category: ActionsWML]]

PortugueseContinentalTranslation

2013-04-17T13:08:29Z

Trewe: /* Bem-Vindo */

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

* trewe (maintainer) [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.is@gmail.com]
* Carlos Sousa
* Luís Passos

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução portuguesa faz uso do sistema de controllo [http://git-scm.com/ Git] e os ficheiros actuais da tradução podem ser obtidos no repositório da github.

Em sistemas *nix:

Descarregar os ficheiros:
git clone git://github.com/trewe/wesn-pt-trans.git && cd wesn-pt-trans

ver o que pode ser editado:
git branch -a

Criar um branch local para editar:
git checkout -b my_branch <STARTING POINT>
:(onde <STARING POINT> é o nome da branch/tag da qual quiserem começar)

Abrir o(s) ficheiro(s) *.po(s) com o editor preferido e começar a traduzir, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Aplicar o trabalho feito:
git commit -a -m 'updated translation'

Criar um patch:
git format-patch <PARENT> --stdout > my_translation.patch
:(parent é a branch da qual fizeram o fork)

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o patch para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Que norma ortográfica?===

Todo o trabalho corrente é baseado na norma de 1911.

A livre escolha de cada tradutor. Apesar de ser verdade que agora existe um «acordo ortográfico» (em vigor no Brasil deste 2004 e em Portugal 2009); é utópico pensar que a língua utilizada nos países lusófonos mude de alguma forma. Haverá sempre diferenças nos diferentes dialectos até porque <b>não</b> existe uma coisa como «português padrão».

Para se ter uma ideia, o acordo muda cerca de 4% do vocabulário do português europeu e pouco menos de 3% do brasileiro.

===O uso do «você»===

Nunca. O utilizador é referido na segunda pessoa do singular. (Sempre no presente do indicativo e com o pronome omitido)

E nos diálogos a preferência vai para a 2ª pessoa (singular como plural).

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teofólio Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

[[Category:Translations]]

PortugueseContinentalTranslation

2013-03-16T10:27:09Z

Trewe: /* Bem-Vindo */ release announcenment

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

É com prazer que a equipa anuncia que a tradução portuguesa está completa a partir da versão 1.10.6 !

Porém:

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

* trewe (maintainer) [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.is@gmail.com]
* Carlos Sousa
* Luís Passos

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

Os ficheiros actuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans github].

Após terem sido obtidos os ficheiros será necessário usar um programa de edição de ficheiros *.po, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o(s) ficheiro(s) traduzido(s) para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Que norma ortográfica?===

Todo o trabalho corrente é baseado na norma de 1911.

A livre escolha de cada tradutor. Apesar de ser verdade que agora existe um «acordo ortográfico» (em vigor no Brasil deste 2004 e em Portugal 2009); é utópico pensar que a língua utilizada nos países lusófonos mude de alguma forma. Haverá sempre diferenças nos diferentes dialectos até porque <b>não</b> existe uma coisa como «português padrão».

Para se ter uma ideia, o acordo muda cerca de 4% do vocabulário do português europeu e pouco menos de 3% do brasileiro.

===O uso do «você»===

Nunca. O utilizador é referido na segunda pessoa do singular. (Sempre no presente do indicativo e com o pronome omitido)

E nos diálogos a preferência vai para a 2ª pessoa (singular como plural).

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teofólio Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

Página do projecto: <a definir>

Página de detalhes no sourceforge: http://sourceforge.net/projects/wesn-pt-trans

Endereço do repositório: https://wesn-pt-trans.svn.sourceforge.net/svnroot/wesn-pt-trans

Mailing Lists:
* wesn-pt-trans-commits <at.here> lists.sourceforge.net - registo de commits, lista para onde são enviados automaticamente as mensagens de commit.
* wesn-pt-trans-users <at.here> lists.sourceforge.net - lista geral, pode ser usada para qualquer tipo de contacto, pergunta ou comentário.

[[Category:Translations]]

WesnothTranslations

2013-03-16T10:18:52Z

Trewe: /* Translations */ pt_PT

== 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]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: 楊綮銘 (Taiwan) - [mailto:steven2880ATgmailDOTcom]
* [[CroatianTranslation|Croatian]] - maintainer: Ivica Đurenec (charlieh65) - [mailto:ivicaDOTdurenecATgmailDOTcom]
* [[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]
* [[EnglishGBTranslation|English (GB)]] - maintainer: Steven Panek (Espreon) - [mailto:Majora700@gmail.com]
* [[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: Jarkko Patteri (Jarkko) - [mailto:jarkkopatteriATgmailDOTcom], Samu Voutilainen (Smar) - [mailto:samu.voutilainenATgmailDOTcom]
* [[FrenchTranslation|French]] - maintainer: Guillaume Pascal (Haldric) - Please use the 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: Antonio Rosella - [mailto:arosellaATyahooDOTcom]
* [[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:Majora700@gmaill.com]
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Diego Inácio Goergen - [mailto:thegoergenATgmailDOTcom]
* [[PortugueseContinentalTranslation|European Portuguese]] - maintainer: trewe [mailto:sjrs456@yahoo.fr]
* [[RomanianTranslation|Romanian]] - maintainer: Alexandru Szasz [mailto:alexxedATgmailDOTcom]
* [[RussianTranslation|Russian]] - maintainer: Victor Sergienko [mailto:singalenATgmailDOTcom]
* [[Scottish_Gaelic_Translation|Scottish Gaelic]] - maintainer: GunChleoc- [mailto:fiosAIGforamnagaidhligDOTnet]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[SlovakTranslation#Preklad|Slovak]] - maintainer: Aceman
* [[SlovenianTranslation|Slovenian]] - maintainer: Klemen Košir (nNa) - [mailto:klemen913ATgmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Steven Panek (Espreon) - [mailto:Majora700@gmail.com]); comaintainer: Víctor Martínez Estrada (Darkmage) - [mailto:quianaaelonin@gmail.com])
* [[SwedishTranslation|Swedish]] - maintainer: Niklas Bolmdahl (dacovale) - [mailto:wesnothATniklasDOTbolmdahlDOTcom]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[UkrainianTranslation|Ukrainian]] - maintainer: robson - [mailto:arobsonATyandexDOTru]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Huynh Yen Loc (hhyloc) - [mailto:nightgaunt13ATgmailDOTcom]

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

WesnothTranslations

2013-03-10T10:37:07Z

Trewe: Undo revision 48736 by Marsianen (Talk)

== Переводы ==

Веснот переводится в настоящее время на языки представленные ниже. Инструкции о том, как внести находятся здесь:
[[WesnothПереводыЧтоКЧему]].
* [[AfrikaansTranslation|Afrikaans]] - координатор: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - координатор: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - координатор: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - координатор: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - координатор: CloudiDust - [mailto:cloudidustATgmailDOTcom]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - координатор: 楊綮銘 (Taiwan) - [mailto:steven2880ATgmailDOTcom]
* [[CroatianTranslation|Croatian]] - координатор: Ivica Đurenec (charlieh65) - [mailto:ivicaDOTdurenecATgmailDOTcom]
* [[CzechTranslation|Czech]] - координатор: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - координатор: Alexander van Gessel (AI/AI0867) - [mailto:AI0867_AT_gmail.com]
* [[EnglishGBTranslation|English (GB)]] - координатор: Steven Panek (Espreon) - [mailto:Majora700@gmail.com]
* [[EnglishShawTranslation|English (Shaw)]] - координатор: Arc Riley - [mailto:ArcRileyATubuntu.com]
* [[Esperanto_translation|Esperanto]] - координатор: Manuel Ortega - [mailto:manuelATelarteDOTcoop]
* [[EstonianTranslation|Estonian]] - координатор: Kaido Kikkas (UncleOwl) - [mailto:kaidoDOTkikkasATkakupesaDOTnet]
* [[FilipinoTranslation|Filipino]] - координатор: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - координатор: Jarkko Patteri (Jarkko) - [mailto:jarkkopatteriATgmailDOTcom], Samu Voutilainen (Smar) - [mailto:samu.voutilainenATgmailDOTcom]
* [[FrenchTranslation|French]] - координатор: Guillaume Pascal (Haldric) - Please use the translation team mailing list [mailto:wesnothATmlDOTfreeDOTfr]
* [[FriulianTranslation|Friulian]] - координатор: Michele Calligaris (MayBug) - [mailto:michele.calligaris-CAIUT-gmail.com]
* [[GalicianTranslation|Galician]] - координатор: Adrián Chaves Fernández (Gallaecio) - [mailto:adriyetichavesATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - координатор: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - координатор: Konstantinos Egarhos [mailto:konsnoslATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - координатор: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - координатор: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Udvari Gábor [mailto:gaborDOTudvariATgmailDOTcom]
* [[IcelandicTranslation|Icelandic]] - координатор: Gabríel A. Pétursson [mailto:gabrielpATsimnetDOTis]
* [[IndonesianTranslation|Indonesian]] - координатор: Yuristyawan Pambudi Wicaksana [mailto:yuris_wicaksana@yahoo.com]
* [[IrishTranslation|Irish]] - координатор: Carson "Mountain_King" [mailto:tree_ringsATrocketmailDOTcom]
* [[ItalianTranslation|Italian]] - координатор: Antonio Rosella - [mailto:arosellaATyahooDOTcom]
* [[JapaneseTranslation|Japanese]] - координатор: IWAI, Masaharu (iwaim) - [mailto:iwaim.subATgmailDOTcom], Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - координатор: mistzone - [mailto:drier22ATgmailDOTcom]
* [[LatinTranslation|Latin]] - координатор: Michael Babich ([[User:Aethaeryn|Aethaeryn]])
* [[LatvianTranslation|Latvian]] - координатор: Reinis Danne - [mailto:rei4danATgmailDOTcom]
* [[LithuanianTranslation|Lithuanian]] - координатор: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MarathiTranslation|Marathi]] - координатор: Sujit R Jadhav - [mailto:sujitrjadhavATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - координатор: Dimitar Ilccov (Mythological)
* [[NorwegianTranslation|Norwegian]] - координатор: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - координатор: Nobody, currently
* [[OldEnglishTranslation|Old English]] - координатор: Steven Panek (Espreon) - [mailto:Majora700@gmaill.com]
* [[PolishTranslation|Polish]] - координатор: none
* [[PortugueseTranslation|Portuguese Brazilian]] - координатор: Diego Inácio Goergen - [mailto:thegoergenATgmailDOTcom]
* [[PortugueseContinentalTranslation|European Portuguese]] - координатор: Sérgio Lopes [mailto:knitter.is@gmail.com] co-maintainer trewe [mailto:sjrs456@yahoo.fr]
* [[RomanianTranslation|Romanian]] - координатор: Alexandru Szasz [mailto:alexxedATgmailDOTcom]
* [[RussianTranslation|Русский]] - координатор: Victor Sergienko [mailto:singalenATgmailDOTcom]
* [[Scottish_Gaelic_Translation|Scottish Gaelic]] - координатор: GunChleoc- [mailto:fiosAIGforamnagaidhligDOTnet]
* [[SerbianTranslation|Serbian]] - координатор: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[SlovakTranslation#Preklad|Slovak]] - координатор: Aceman
* [[SlovenianTranslation|Slovenian]] - координатор: Klemen Košir (nNa) - [mailto:klemen913ATgmailDOTcom]
* [[SpanishTranslation|Spanish]] - координатор: Steven Panek (Espreon) - [mailto:Majora700@gmail.com]); comaintainer: Víctor Martínez Estrada (Darkmage) - [mailto:quianaaelonin@gmail.com])
* [[SwedishTranslation|Swedish]] - координатор: Niklas Bolmdahl (dacovale) - [mailto:wesnothATniklasDOTbolmdahlDOTcom]
* [[TurkishTranslation|Turkish]] - координатор: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[UkrainianTranslation|Ukrainian]] - координатор: robson - [mailto:arobsonATyandexDOTru]
* [[Wesnoth-in-Valencian|Valencian]] - координатор: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - координатор: Huynh Yen Loc (hhyloc) - [mailto:nightgaunt13ATgmailDOTcom]

== Список Рассылки ==

Теперь имеется рассылки, посвященный вопросам перевода. Это, в основном, предназначен для информирования перевод сопровождающих о важных изменениях, чтобы объявить строки замерзает и других специальных вещей.Каждый волен, чтобы подписаться на этот список. Вы можете найти этот список, имеющих право Wesnoth -i18n at список всех Parking списки рассылки:

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

Архив за этот список можно найти [http://mail.gna.org/public/wesnoth-i18n/ сдесь].
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.

== См. также ==

* [[WesnothTranslationsHowTo]]
* [[ImageLocalization]]
* [[GetText]]
* [http://gettext.wesnoth.org Статистика Переводов (стабильный)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Статистика Переводов (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]
* [[CharactersStorys| Character descriptions for Translators (Spoiler Warning)]]
* [[TextdomainStatus]]

[[Категория:Переводы|*]]

PortugueseContinentalTranslation

2013-02-27T18:06:35Z

Trewe: /* Estilos e vocabulário */

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

* trewe (maintainer) [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.is@gmail.com]
* Carlos Sousa
* Luís Passos

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

Os ficheiros actuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans github].

Após terem sido obtidos os ficheiros será necessário usar um programa de edição de ficheiros *.po, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o(s) ficheiro(s) traduzido(s) para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para manter o espírito do jogo.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Que norma ortográfica?===

Todo o trabalho corrente é baseado na norma de 1911.

A livre escolha de cada tradutor. Apesar de ser verdade que agora existe um «acordo ortográfico» (em vigor no Brasil deste 2004 e em Portugal 2009); é utópico pensar que a língua utilizada nos países lusófonos mude de alguma forma. Haverá sempre diferenças nos diferentes dialectos até porque <b>não</b> existe uma coisa como «português padrão».

Para se ter uma ideia, o acordo muda cerca de 4% do vocabulário do português europeu e pouco menos de 3% do brasileiro.

===O uso do «você»===

Nunca. O utilizador é referido na segunda pessoa do singular. (Sempre no presente do indicativo e com o pronome omitido)

E nos diálogos a preferência vai para a 2ª pessoa (singular como plural).

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| ondim (Camões, Teofólio Braga)
|-
| mermaid
| ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

Página do projecto: <a definir>

Página de detalhes no sourceforge: http://sourceforge.net/projects/wesn-pt-trans

Endereço do repositório: https://wesn-pt-trans.svn.sourceforge.net/svnroot/wesn-pt-trans

Mailing Lists:
* wesn-pt-trans-commits <at.here> lists.sourceforge.net - registo de commits, lista para onde são enviados automaticamente as mensagens de commit.
* wesn-pt-trans-users <at.here> lists.sourceforge.net - lista geral, pode ser usada para qualquer tipo de contacto, pergunta ou comentário.

[[Category:Translations]]

PortugueseContinentalTranslation

2013-02-27T17:59:50Z

Trewe: /* Equipa da tradução */

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

* trewe (maintainer) [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

* knitter aka Sérgio Lopes [mailto:knitter.is@gmail.com]
* Carlos Sousa
* Luís Passos

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

Os ficheiros actuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans github].

Após terem sido obtidos os ficheiros será necessário usar um programa de edição de ficheiros *.po, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o(s) ficheiro(s) traduzido(s) para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para
manter o espírito do jogo.

O inglês usa capitalização extensiva neste jogo porém em português só palavras em destaque deverão estar.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Que norma ortográfica?===

A livre escolha de cada tradutor. Apesar de ser verdade que agora existe um «acordo ortográfico» (em vigor no Brasil deste 2004 e em Portugal 2009); é utópico pensar que a língua utilizada nos países lusófonos mude de alguma forma. Haverá sempre diferenças nos diferentes dialectos até porque <b>não</b> existe uma coisa como «português padrão».

Para se ter uma ideia, o acordo muda cerca de 4% do vocabulário do português europeu e pouco menos de 3% do brasileiro.

===O uso do «você»===

Nunca. O utilizador é referido na segunda pessoa do singular. (Sempre no presente do indicativo e com o pronome omitido)

E nos diálogos a preferência vai para a 2ª pessoa (singular como plural).

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar/Submeter
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar/processar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| tritão/ondim
|-
| mermaid
| sereia/ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

Página do projecto: <a definir>

Página de detalhes no sourceforge: http://sourceforge.net/projects/wesn-pt-trans

Endereço do repositório: https://wesn-pt-trans.svn.sourceforge.net/svnroot/wesn-pt-trans

Mailing Lists:
* wesn-pt-trans-commits <at.here> lists.sourceforge.net - registo de commits, lista para onde são enviados automaticamente as mensagens de commit.
* wesn-pt-trans-users <at.here> lists.sourceforge.net - lista geral, pode ser usada para qualquer tipo de contacto, pergunta ou comentário.

[[Category:Translations]]

Template:WML Tags

2013-01-25T22:13:27Z

Trewe:

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

|-
|''A:''
[[AbilitiesWML|abilities]],
[[CampaignWML#Campaign credits|about]],
[[Lua_AI_Howto#Behavior_.28Sticky.29_Candidate_Actions|add_ai_behavior]],
[[AbilitiesWML#Common_keys_and_tags_for_every_ability|adjacent_description]],
[[SingleUnitWML|advance]],
[[AdvancedPreferenceWML|advanced_preference]],
[[UnitTypeWML|advancefrom]],
[[UnitTypeWML#After_max_level_advancement_.28AMLA.29|advancement]],
[[StatisticalScenarioWML#The_.5Bteam.5D_tag|advances]],
[[AbilitiesWML#Common_keys_and_tags_for_every_ability|affect_adjacent]],
[[AiWML#The_.5Bai.5D_Tag:_Defining_Aspects|ai]],
[[StandardSideFilter|allied_with]],
[[DirectActionsWML#.5Ballow_end_turn.5D|allow_end_turn]],
[[DirectActionsWML#.5Ballow_extra_recruit.5D|allow_extra_recruit]],
[[DirectActionsWML#.5Ballow_recruit.5D|allow_recruit]],
[[DirectActionsWML#.5Ballow_undo.5D|allow_undo]],
[[ConditionalActionsWML#Meta-Condition_Tags|and]],
[[InterfaceActionsWML#.5Banimate_unit.5D|animate]],
[[InterfaceActionsWML#.5Banimate_unit.5D|animate_unit]],
[[AnimationWML|animation]],
[[VariablesWML#Array|array]],
[[AiWML#A_Bit_More_on_Simple_vs._Composite_Aspects|aspect]],
[[UnitTypeWML#Attacks|attack]],
[[AnimationWML|attack_anim]],
[[StatisticalScenarioWML#The_.5Bteam.5D_tag|attacks]],
[[AiWML#The_.5Bai.5D_Tag:_Defining_Aspects|avoid]];
|-
|''B:''
[[UnitTypeWML#Other_tags|base_unit]],
[[AbilitiesWML|berserk]],
[[BinaryPathWML|binary_path]],
[[EditorWML#The_.5Bbrush.5D_tag|brush]];
|-
|''C:''
[[CampaignWML#The_.5Bcampaign.5D_tag|campaign]],
[[Formula_AI_Howto#Setting_up_the_RCA_main_loop_Stage_and_Candidate_Actions|candidate_action]],
[[DirectActionsWML#.5Bcapture_village.5D|capture_village]],
[[ConditionalActionsWML#.5Bswitch.5D|case]],
[[MapGeneratorWML#The_Default_Generator|castle]],
[[MapGeneratorWML#The_Cave_Generator|chamber]],
[[AbilitiesWML#The_.5Bspecials.5D_tag|chance_to_hit]],
[[InterfaceActionsWML#.5Bchat.5D|chat]],
[[ReplayWML|choose]],
[[PersistenceWML|clear_global_variable]],
[[InterfaceActionsWML#.5Bclear_menu_item.5D|clear_menu_item]],
[[InternalActionsWML#.5Bclear_variable.5D|clear_variable]],
[[InterfaceActionsWML#.5Bcolor_adjust.5D|color_adjust]],
command ([[ConditionalActionsWML#.5Bcommand.5D|action]], [[ReplayWML|replay]]),
[[MapGeneratorWML#The_Default_Generator|convert]],
[[AiWML#The_.5Bgoal.5D_Tag|criteria]];
|-
|''D:''
[[AbilitiesWML#The_.5Bspecials.5D_tag|damage]],
[[AnimationWML#death|death]],
[[StatisticalScenarioWML#The_.5Bteam.5D_tag|deaths]],
[[AnimationWML#default|default]],
[[AnimationWML#defend|defend]],
[[StatisticalScenarioWML#The_.5Bteam.5D_tag|defends]],
[[UnitsWML#.5Bmovetype.5D|defense]],
[[InterfaceActionsWML#.5Bdelay.5D|delay]],
[[InterfaceActionsWML#.5Bdeprecated_message.5D|deprecated_message]],
[[ReplayWML|destination]],
[[DirectActionsWML#.5Bdisallow_end_turn.5D|disallow_end_turn]],
[[DirectActionsWML#.5Bdisallow_extra_recruit.5D|disallow_extra_recruit]],
[[DirectActionsWML#.5Bdisallow_recruit.5D|disallow_recruit]],
[[ConditionalActionsWML#.5Bwhile.5D|do]],
[[AbilitiesWML#The_.5Bspecials.5D_tag|drains]],
[[AnimationWML#draw_weapon_anim|draw_weapon_anim]];
|-
|''E:''
[[EditorWML#The_.5Beditor_group.5D_tag|editor_group]],
[[EditorWML#The_.5Beditor_music.5D_tag|editor_music]],
[[EditorWML#The_.5Beditor_times.5D_tag|editor_times]],
[[EditorWML#The_.5Beditor_tool_hint.5D_tag|editor_tool_hint]],
[[EffectWML|effect]],
else ([[ConditionalActionsWML#.5Bif.5D|action]], [[AnimationWML#.5Bif.5D_and_.5Belse.5D|animation]]),
[[DirectActionsWML#.5Bendlevel.5D|endlevel]],
end_turn ([[DirectActionsWML#.5Bend_turn.5D|action]], [[ReplayWML|replay]]),
[[StandardSideFilter|enemy_of]],
[[Customizing_AI_in_Wesnoth_1.8#AI_engines_.28_via_.5Bengine.5D_tags_.29|engine]],
[[CampaignWML#Campaign_credits|entry]],
[[EraWML|era]],
[[EventWML|event]],
[[ThemeWML#.5Bstatus.5D|expenses]],
[[AnimationWML#Simplified_animation_blocks|extra_anim]];
|-
|''F:''
[[AiWML#A_Bit_More_on_Simple_vs._Composite_Aspects|facet]],
[[InterfaceActionsWML#.5Banimate_unit.5D|facing]],
[[InterfaceActionsWML#.5Bmove_units_fake.5D|fake_unit]],
[[UnitTypeWML#Other_tags|female]],
[[FilterWML|filter]],
[[StandardUnitFilter|filter_adjacent]],
[[StandardLocationFilter|filter_adjacent_location]],
[[FilterWML#Filtering_Weapons|filter_attack]],
[[AbilitiesWML#Common_keys_and_tags_for_every_weapon_special|filter_attacker]],
[[AbilitiesWML#Common_keys_and_tags_for_every_ability|filter_base_value]],
[[EventWML#.5Bfilter_condition.5D|filter_condition]],
[[AbilitiesWML#Common_keys_and_tags_for_every_weapon_special|filter_defender]],
[[AiWML#Filtering_Combat_with_the_.27attacks.27_Aspect|filter_enemy]],
[[StandardLocationFilter|filter_location]],
[[AbilitiesWML#Common_keys_and_tags_for_every_weapon_special|filter_opponent]],
[[AiWML#Filtering_Combat_with_the_.27attacks.27_Aspect|filter_own]],
[[StandardLocationFilter|filter_owner]],
[[StandardLocationFilter|filter_radius]],
[[SingleUnitWML|filter_recall]],
[[StandardUnitFilter|filter_second]],
[[FilterWML#Filtering_Weapons|filter_second_attack]],
[[AbilitiesWML|filter_self]],
[[StandardSideFilter|filter_side]],
[[FilterWML#Filtering_Vision|filter_vision]],
[[AbilitiesWML#Common_keys_and_tags_for_every_weapon_special|filter_weapon]],
[[StandardUnitFilter|filter_wml]],
[[InternalActionsWML#.5Bfind_path.5D|find_path]],
[[InternalActionsWML#.5Bfire_event.5D|fire_event]],
[[AbilitiesWML#The_.5Bspecials.5D_tag|firststrike]],
[[InterfaceActionsWML#.5Bfloating_text.5D|floating_text]],
[[AnimationWML#Frames|frame]];
|-
|''G:''
[[GameConfigWML|game_config]],
[[MapGeneratorWML|generator]],
[[PersistenceWML|get_global_variable]],
[[AiWML#The_.5Bgoal.5D_Tag|goal]],
gold ([[DirectActionsWML#.5Bgold.5D|action]], [[ThemeWML|theme]]),
[[InterfaceActionsWML#.5Bobjectives.5D|gold_carryover]];
|-
|''H:''
[[DirectActionsWML#.5Bharm_unit.5D|harm_unit]],
[[StandardSideFilter|has_unit]],
[[ConditionalActionsWML#Condition_Tags|have_location]],
[[ConditionalActionsWML#Condition_Tags|have_unit]],
[[AbilitiesWML#The_.5Bspecials.5D_tag|heal_on_hit]],
[[DirectActionsWML#.5Bheal_unit.5D|heal_unit]],
[[AnimationWML#healed|healed_anim]],
[[AnimationWML#healing|healing_anim]],
[[AbilitiesWML|heals]],
[[MapGeneratorWML|height]],
[[UnitsWML#.5Bhide_help.5D|hide_help]],
[[InterfaceActionsWML#.5Bhide_unit.5D|hide_unit]],
[[AbilitiesWML|hides]];
|-
|''I:''
[[AnimationWML#idling|idle_anim]],
if ([[ConditionalActionsWML#.5Bif.5D|action]], [[AnimationWML#.5Bif.5D_and_.5Belse.5D|animation]]),
[[AbilitiesWML|illuminates]],
[[TerrainGraphicsWML|image]],
[[ThemeWML#.5Bstatus.5D|income]],
[[ReplayWML|init_side]],
[[InternalActionsWML#.5Binsert_tag.5D|insert_tag]],
[[InterfaceActionsWML#.5Binspect.5D|inspect]],
[[InterfaceActionsWML#.5Bitem.5D|item]],
[[MapGeneratorWML#The_Cave_Generator|items]];
|-
|''J:''
[[InternalActionsWML#.5Bset_variables.5D|join]];
|-
|''K:''
[[DirectActionsWML#.5Bkill.5D|kill]],
[[StatisticalScenarioWML|killed]];
|-
|''L:''
label ([[InterfaceActionsWML#.5Blabel.5D|map]], [[ThemeWML|theme]]),
[[LanguageWML|language]],
[[AiWML#The_.5Bai.5D_Tag:_Defining_Aspects|leader_goal]],
[[AbilitiesWML|leadership]],
[[AnimationWML#leading|leading_anim]],
[[AnimationWML#levelin|levelin_anim]],
[[AnimationWML#levelout|levelout_anim]],
[[DirectActionsWML#.5Blift_fog.5D|lift_fog]],
[[AiWML#Limiting_Recruiting_with_the_.27recruitment.27_Aspect|limit]],
[[InternalActionsWML#.5Bset_variables.5D|literal]],
[[LocaleWML|locale]],
[[InterfaceActionsWML#.5Block_view.5D|lock_view]],
[[LuaWML|lua]];
|-
|''M:''
[[ThemeWML#.5Bmain_map.5D|main_map]],
[[ThemeWML#.5Bmain_map_border.5D|main_map_border]],
[[UnitTypeWML#Other_tags|male]],
[[ThemeWML#.5Bmenu.5D|menu]],
[[SavefileWML|menu_item]],
[[InterfaceActionsWML#.5Bmessage.5D|message]],
[[Micro AIs|micro_ai]],
[[ThemeWML#.5Bmini_map.5D|mini_map]],
[[AnimationWML#The_content_of_a_frame|missile_frame]],
[[ModificationWML|modification]],
[[SingleUnitWML|modifications]],
[[DirectActionsWML#.5Bmodify_ai.5D|modify_ai]],
[[DirectActionsWML#.5Bmodify_side.5D|modify_side]],
[[DirectActionsWML#.5Bmodify_turns.5D|modify_turns]],
[[DirectActionsWML#.5Bmodify_unit.5D|modify_unit]],
[[ReplayWML|move]],
[[DirectActionsWML#.5Bmove_unit.5D|move_unit]],
[[InterfaceActionsWML#.5Bmove_unit_fake.5D|move_unit_fake]],
[[InterfaceActionsWML#.5Bmove_units_fake.5D|move_units_fake]],
[[AnimationWML#movement|movement_anim]],
[[UnitsWML#.5Bmovetype.5D|movement costs]],
[[UnitsWML#.5Bmovetype.5D|movetype]],
[[ScenarioWML|multiplayer]],
[[EraWML|multiplayer_side]],
[[MusicListWML#.5Bmusic.5D|music]];
|-
|''N:''
[[MapGeneratorWML|naming]],
[[ConditionalActionsWML#Meta-Condition_Tags|not]],
[[InterfaceActionsWML#.5Bobjectives.5D|note]],
[[ThemeWML#.5Bstatus.5D|num_units]];
|-
|''O:''
[[DirectActionsWML#.5Bobject.5D|object]],
[[InterfaceActionsWML#.5Bobjectives.5D|objective]],
[[InterfaceActionsWML#.5Bobjectives.5D|objectives]],
[[ThemeWML#.5Bstatus.5D|observers]],
[[InterfaceActionsWML#.5Bopen_help.5D|open_help]],
[[InterfaceActionsWML#.5Bmessage.5D|option]],
[[OptionWML|options]],
[[ConditionalActionsWML#Meta-Condition_Tags|or]];
|-
|''P:''
[[ThemeWML#.5Bpanel.5D|panel]],
[[IntroWML|part]],
[[AbilitiesWML#The_.5Bspecials.5D_tag|petrifies]],
[[DirectActionsWML#.5Bpetrify.5D|petrify]],
[[DirectActionsWML#.5Bplace_shroud.5D|place_shroud]],
[[AbilitiesWML#The_.5Bspecials.5D_tag|plague]],
[[AbilitiesWML#The_.5Bspecials.5D_tag|poison]],
[[UnitTypeWML#Other_tags|portrait]],
[[ThemeWML#.5Bstatus.5D|position]],
[[AnimationWML#post_movement|post_movement_anim]],
[[AnimationWML#pre_movement|pre_movement_anim]],
[[FilterWML#Filtering_Weapons|primary_attack]],
[[StandardUnitFilter|primary_unit]],
[[InterfaceActionsWML#.5Bprint.5D|print]],
[[AiWML#Deprecated_AI_Targeting_Aspects|protect_location]],
[[AiWML#Deprecated_AI_Targeting_Aspects|protect_unit]];
|-
|''R:''
[[UnitsWML#.5Brace.5D|race]],
[[ReplayWML|random]],
recall ([[DirectActionsWML#.5Brecall.5D|action]], [[ReplayWML|replay]]),
[[StatisticalScenarioWML|recalls]],
[[ReplayWML|recruit]],
[[AnimationWML#recruited|recruit_anim]],
[[AnimationWML#recruiting|recruiting_anim]],
[[StatisticalScenarioWML|recruits]],
[[InterfaceActionsWML#.5Bredraw.5D|redraw]],
[[AbilitiesWML|regenerate]],
[[InterfaceActionsWML#.5Bremove_item.5D|remove_item]],
[[DirectActionsWML#.5Bremove_shroud.5D|remove_shroud]],
[[InterfaceActionsWML#.5Bremove_sound_source.5D|remove_sound_source]],
[[InterfaceActionsWML#.5Bremove_unit_overlay.5D|remove_unit_overlay]],
[[DirectActionsWML#.5Breplace_map.5D|replace_map]],
[[DirectActionsWML#.5Breplace_schedule.5D|replace_schedule]],
[[ReplayWML|replay]],
[[SavefileWML|replay_start]],
[[DirectActionsWML#.5Breset_fog.5D|reset_fog]],
resistance ([[AbilitiesWML|ability]], [[UnitsWML#.5Bmovetype.5D|unit]]),
[[ThemeWML|resolution]],
[[ReplayWML|results]],
[[MapGeneratorWML|road_cost]],
[[InternalActionsWML#.5Brole.5D|role]],
[[TerrainMaskWML|rule]];
|-
|''S:''
[[SavefileWML|save]],
[[ScenarioWML|scenario]],
[[InterfaceActionsWML#.5Bscroll.5D|scroll]],
[[InterfaceActionsWML#.5Bscroll_to.5D|scroll_to]],
[[InterfaceActionsWML#.5Bscroll_to_unit.5D|scroll_to_unit]],
[[FilterWML#Filtering_Weapons|secondary_attack]],
[[StandardUnitFilter|secondary_unit]],
[[HelpWML|section]],
[[InterfaceActionsWML#.5Bselect_unit.5D|select_unit]],
[[ReplayWML|sequence]],
[[DirectActionsWML#.5Bset_extra_recruit.5D|set_extra_recruit]],
[[PersistenceWML|set_global_variable]],
[[InterfaceActionsWML#.5Bset_menu_item.5D|set_menu_item]],
[[DirectActionsWML#.5Bset_recruit.5D|set_recruit]],
[[EffectWML|set_specials]],
[[InternalActionsWML#.5Bset_variable.5D|set_variable]],
[[InternalActionsWML#.5Bset_variables.5D|set_variables]],
[[MapGeneratorWML#The_Cave_Generator|settings]],
[[AnimationWML#sheath_weapon|sheath_weapon_anim]],
show_if ([[InterfaceActionsWML#.5Bmessage.5D|message]], [[InterfaceActionsWML#.5Bset_menu_item.5D|set_menu_item]]),
[[InterfaceActionsWML#.5Bshow_objectives.5D|show_objectives]],
[[SideWML|side]],
[[ThemeWML|side_playing]],
[[AbilitiesWML|skirmisher]],
[[AbilitiesWML#The_.5Bspecials.5D_tag|slow]],
[[SavefileWML|snapshot]],
[[InterfaceActionsWML#.5Bsound.5D|sound]],
[[InterfaceActionsWML#.5Bsound_source.5D|sound_source]],
source ([[ReplayWML|replay]], [[DirectActionsWML#.5Btunnel.5D|teleport]]),
[[AbilitiesWML#The_.5Bspecials.5D_tag|specials]],
[[InternalActionsWML#.5Bset_variables.5D|split]],
[[Customizing_AI_in_Wesnoth_1.8#Working_with_main_loop_of_the_RCA_AI|stage]],
[[AnimationWML#standing|standing_anim]],
[[StatisticalScenarioWML#The_.5Bstatistics.5D_tag|statistics]],
status ([[SingleUnitWML|single unit]], [[ThemeWML|theme]]),
[[InternalActionsWML#.5Bstore_gold.5D|store_gold]],
[[InternalActionsWML#.5Bstore_items.5D|store_items]],
[[InternalActionsWML#.5Bstore_locations.5D|store_locations]],
[[InternalActionsWML#.5Bstore_map_dimensions.5D|store_map_dimensions]],
[[InternalActionsWML#.5Bstore_reachable_locations.5D|store_reachable_locations]],
[[InternalActionsWML#.5Bstore_side.5D|store_side]],
[[InternalActionsWML#.5Bstore_starting_location.5D|store_starting_location]],
[[InternalActionsWML#.5Bstore_time_of_day.5D|store_time_of_day]],
[[InternalActionsWML#.5Bstore_turns.5D|store_turns]],
[[InternalActionsWML#.5Bstore_unit.5D|store_unit]],
[[InternalActionsWML#.5Bstore_unit_type.5D|store_unit_type]],
[[InternalActionsWML#.5Bstore_unit_type_ids.5D|store_unit_type_ids]],
[[InternalActionsWML#.5Bstore_villages.5D|store_villages]],
[[IntroWML|story]],
[[AbilitiesWML#The_.5Bspecials.5D_tag|swarm]],
[[ConditionalActionsWML#.5Bswitch.5D|switch]];
|-
|''T:''
[[DirectActionsWML#.5Btunnel.5D|target]],
[[StatisticalScenarioWML#The_.5Bteam.5D_tag|team]],
teleport ([[AbilitiesWML|ability]], [[DirectActionsWML#.5Bteleport.5D|action]]),
[[AnimationWML#pre_teleport|teleport_anim]],
[[DirectActionsWML#.5Bterrain.5D|terrain]],
[[TerrainGraphicsWML|terrain_graphics]],
[[TerrainMaskWML|terrain_mask]],
[[TerrainWML|terrain_type]],
[[ScenarioWML#Test_scenario|test]],
[[InterfaceActionsWML#.5Bmessage.5D|text_input]],
[[WesCamp#The_textdomain_declaration|textdomain]],
[[ThemeWML|theme]],
[[ConditionalActionsWML#.5Bif.5D|then]],
[[TerrainGraphicsWML|tile]],
[[TimeWML|time]],
[[DirectActionsWML#.5Btime_area.5D|time_area]],
[[ThemeWML#.5Bstatus.5D|time_of_day]],
[[HelpWML|topic]],
[[HelpWML|toplevel]],
[[UnitsWML#.5Btrait.5D|trait]],
[[DirectActionsWML#.5Btransform_unit.5D|transform_unit]],
[[InternalActionsWML#.5Bfind_path.5D|traveler]],
[[DirectActionsWML#.5Btunnel.5D|tunnel]],
[[ThemeWML#.5Bstatus.5D|turn]],
[[ScenarioWML|tutorial]];
|-
|''U:''
[[InterfaceActionsWML#.5Bunhide_unit.5D|unhide_unit]],
[[SingleUnitWML|unit]],
[[ThemeWML#.5Bstatus.5D|unit_abilities]],
[[ThemeWML#.5Bstatus.5D|unit_alignment]],
[[ThemeWML#.5Bstatus.5D|unit_description]],
[[ThemeWML#.5Bstatus.5D|unit_hp]],
[[ThemeWML#.5Bstatus.5D|unit_image]],
[[ThemeWML#.5Bstatus.5D|unit_level]],
[[ThemeWML#.5Bstatus.5D|unit_moves]],
[[InterfaceActionsWML#.5Bunit_overlay.5D|unit_overlay]],
[[ThemeWML#.5Bstatus.5D|unit_profile]],
[[ThemeWML#.5Bstatus.5D|unit_status]],
[[ThemeWML#.5Bstatus.5D|unit_traits]],
[[UnitTypeWML|unit_type]],
[[ThemeWML#.5Bstatus.5D|unit_weapons]],
[[InternalActionsWML|unit_worth]],
[[ThemeWML#.5Bstatus.5D|unit_xp]],
[[UnitsWML|units]],
[[InterfaceActionsWML#.5Bunlock_view.5D|unlock_view]],
[[DirectActionsWML#.5Bunpetrify.5D|unpetrify]],
[[DirectActionsWML#.5Bunstore_unit.5D|unstore_unit]],
[[ThemeWML#.5Bstatus.5D|upkeep]];
|-
| ''V:''
[[InternalActionsWML#.5Bset_variables.5D|value]],
[[ConditionalActionsWML#Condition_Tags|variable]],
[[VariablesWML#The_.5Bvariables.5D_tag|variables]],
[[UnitTypeWML#Other_tags|variation]],
[[AnimationWML#victory|victory_anim]],
[[SideWML|village]],
[[MapGeneratorWML|village_naming]],
[[ThemeWML#.5Bstatus.5D|villages]],
[[InterfaceActionsWML#.5Bvolume.5D|volume]];
|-
| ''W:''
[[ConditionalActionsWML#.5Bwhile.5D|while]],
[[InterfaceActionsWML#.5Bwml_message.5D|wml_message]];
|}

<includeonly>[[Category:WML Reference]]</includeonly>

<noinclude>A box with all the WML tags, each one linking to the page and section they are described in. This box should be included in each of the WML reference pages.</noinclude>

InternalActionsWML

2013-01-25T22:10:04Z

Trewe: added [unit_worth]

{{WML Tags}}

Part of [[ActionWML]], Internal actions are actions that WML uses internally that do not directly affect game play (or, at least, are not readily apparent to the player). For example, storing a variable is an internal action.

== Variable Actions ==

These actions are focused, in one way or another, on [[VariablesWML|variables]]. Creating them, modifying them, capturing game data to them, you name it, these actions are all about the variables.

=== [set_variable] ===

The '''[set_variable]''' tag is used to create and manipulate WML variables. The [http://www.wesnoth.org/macro-reference.xhtml#VARIABLE VARIABLE] macro is a quick syntactic shortcut for simple variable creation and the [http://www.wesnoth.org/macro-reference.xhtml#VARIABLE_OP VARIABLE_OP] macro is a quick syntactic shortcut for performing simple mathematical operations on variables.

* '''name''': the name of the variable to manipulate

* '''value''': set the variable to the given value (can be numeric or string).Use literal for no substitution. (see [[VariablesWML]])

* '''literal''': set the variable to the given value (can be numeric or string). This does not interpret any dollars signs.

* '''to_variable''': set the variable to the value of the given variable, e.g. 'to_variable=temp' would be equivalent to 'value=$temp'.

* '''add''': add the given amount to the variable.

* '''sub''': subtract the given amount from the variable.

* '''multiply''': multiply the variable by the given number. The result is a float.<br />To negate a number, multiply by -1. If you negate 0, the result is a floating-point negative zero -0. To display -0 as 0, use a second tag with add=0; it will flip -0 to 0 but not affect other numbers.

* '''divide''': divide the variable by the given number. The result is a float. Wesnoth 1.9 and later no longer uses integer division. Use a second tag with round=floor if you relied on this.

* '''modulo''': returns the remainder of a division.

* '''rand''': the variable will be randomly set.<br>You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'.<br>You may provide a range of numbers (integers), e.g. 'random=3..5'.<br>You may combine these, e.g. 'random=100,1..9', in which case there would be 1/10th chance of getting 100, just like for each of 1 to 9. See [[BuildingMultiplayerExamples]] for more info on the MP case.

* '''time=stamp''': 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.

* '''string_length''': Retrieves the length in characters of the string passed as this attribute's value; such string is parsed and variable substitution applied automatically (see [[VariablesWML]] for details).

* '''[join]''' joins an array of strings to create a textual list
** '''variable''': name of the array
** '''key''': the key of each array element(array[$i].foo) in which the strings are stored
** '''separator''': separator to connect the elements
** '''remove_empty''': whether to ignore empty elements

* '''ipart''': Assigns the integer part (the part to the left of the comma) of the referenced variable.

* '''fpart''': Assigns the decimal part (the part to the right of the comma) of the referenced variable.

* '''round''': Rounds the variable to the specified number of digits of precision. Negative precision works as expected (rounding 19517 to -2 = 19500). Special values:
**'''round=ceil''': Rounds upward to the nearest integer.
**'''round=floor''': Rounds down to the nearest integer.

=== [set_variables] ===

Manipulates a WML array or container

* '''name''': the name of the array or container to manipulate

* '''mode''': one of the following values:
** ''replace'': will clean the array '''name''' and replace it with given data
** ''append'': will append given data to the current array
** ''merge'': will merge in the given data into '''name'''
** ''insert'': will insert the given data at the index specified in the '''name''' attribute, such as name=my_array[1]. The default index is zero, which will insert to the front of the array. '''Note:''' if an invalid index is used, empty containers will be created before the insertion is performed. In other words, do not attempt to insert at an index greater than (or equal to) the array's current length. This limitation may be removed in future versions.

* '''to_variable''': data will be set to the given array

* '''[value]''': the WML inside the [value] tags will be stored in data, variables will be interpolated directly, use $| in order to escape the $ sign, you can store arrays of WML by supplying multiple [value] tags. ([[#Using_.5Bset_variables.5D_to_Create_Arrays_of_WML|See Example]])

* '''[literal]''': same as '''[value]''', but variables will not be substituted, '''[literal]''' and '''[value]''' can not be used in the same [set_variables] tag, i.e. you can not create arrays by piling a mix of '''[value]''' and '''[literal]''' tags

*'''[split]''' splits a textual list into an array which will then be set to data
** '''list''': textual list to split
** '''key''': the key of each array element(array[$i].foo) in which the strings are stored
** '''separator''': separator to separate the elements
** '''remove_empty''': whether to ignore empty elements

=== Capturing Game Data ===

These actions capture different bits of game data and store them to variables so they can be examined and/or manipulated.

==== [store_gold] ====

Stores a side's gold into a variable.

* '''[[StandardSideFilter]]''': The first matching side's gold will be stored in the variable "variable".
* '''variable''': (default='gold') the name of the variable to store the gold 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) and 'owner_side' (villages only). The array will include any unreachable border hexes, if applicable.

* [[StandardLocationFilter]]: a location or location range which specifies the locations to store. By default, all locations on the map are stored.

* '''variable''': the name of the variable (array) into which to store the locations.

==== [store_reachable_locations] ====

Stores locations reachable by the given units. Can store either the movement, attack or vision ranges.

* '''[filter]''': a [[StandardUnitFilter]]. The locations reachable by any of the matching units will be stored.
* '''[filter_location]''': (optional) a [[StandardLocationFilter]]. Only locations which also match this filter will be stored.
* '''range''': possible values ''movement'' (default), ''attack'', ''vision''. If ''movement'', stores the locations within the movement range of the unit, taking Zone of Control into account. If ''attack'', stores the attack range (movement range + 1 hex). If ''vision'', stores the vision range (movement range ignoring Zone of Control + 1 hex).
* '''moves''': possible values ''current'' (default), ''max''. Specifies whether to use the current or maximum movement points when calculating the range.
* '''viewing_side''': (optional) the side whose vision to use when calculating the reach. This only has meaning in the presence of fog, shroud, or units with the ambush ability. If left out, then fog, shroud and ambushers are ignored and the real reach of the units is stored.
* '''variable''': the name of the variable (array) into which to store the locations.

==== [store_map_dimensions] ====

Stores the map dimensions in a variable.

* '''variable''': the name of the variable where the values will be saved into. If it is skipped, a variable 'map_size' is used, and its contents overridden, if they existed already. The result is a container variable, with members ''width'' and ''height''.

==== [store_side] ====

Stores information about a certain side in a variable.

'''Keys:'''
* '''[[StandardSideFilter]]''': All matching sides are stored. (An array is created if several sides match - access it with side[2].team_name and so on.)
* '''variable''': the name of the variable to store the information in (default: "side")

'''Result'''

Variable will contain following members:
* '''color''': It indicates team color. Can be one of the following:
{| border = 1
| ''color''
| red
| blue
| green
| purple
| black
| brown
| orange
| white
| teal
|-
| ''value''
| 1
| 2
| 3
| 4
| 5
| 6
| 7
| 8
| 9
|}
* '''colour''': Same as above.
* '''controller''': Indicates type of player that control this side. ''In networked multiplayer, the controller attribute is ambiguous. Be very careful or you have OOS errors.''
** '''human''': Human player
** '''human_ai''': If human player was replaced by AI player by "droid" command.
** '''null''': If players assigns "Empty" to "Player/Type" in game lobby
** '''ai''': If players assigns "Computer Player" to "Player/Type" in game lobby
* '''fog''': Indicates whether this side is affected by fog of war.
* '''gold''': The amount of gold the side have.
* '''hidden''': (boolean) If 'yes', side is not shown in status table.
* '''income''': Base income for this side (without villages).
* '''name''': Name of player.
* '''recruit''': A comma-separated list of unit types that can be recruited by this side.
* '''shroud''': Whether this side is affected by shroud.
* '''side''': The $side_number of the side belonging to this container
* '''team_name''': String representing the team's description.
* '''user_team_name''': Translated string representing the team's description.
* '''village_gold''': The amount of gold given to this side per village it controls per turn.

==== [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', 'terrain' and 'owner_side' (villages only)

* [[StandardSideFilter]]: The starting locations of all matching sides will be stored. If multiple sides are matched, a WML array will be created.
* '''variable''': (default='location'): the name of the variable to store the location in

==== [store_time_of_day] ====

Stores time of day information from the current scenario into a WML variable container.

* '''x, y''': Location to store the time for. [[DirectActionsWML#.5Btime_area.5D|Time areas]] matter; illumination does not. If this is omitted, the global (location-independent) time is stored.

* '''variable''': (default='time_of_day') name of the container on which to store the information. The container will be filled with the same attributes found on [[TimeWML]].

* '''turn''': (defaults to the current turn number) changes the turn number for which time of day information should be retrieved.

Prior to 1.11.1, the variable was treated as an array, and the container with the time of day information was appended to the end. The upshot of which is that in 1.10, you probably want to [[#.5Bclear_variable.5D|clear]] the <code>time_of_day</code> variable before storing information in it.

==== [store_turns] ====

Stores the turn limit (the maximum number of turns). If there is no limit, this stores ''-1''.

* '''variable''': (default='turns') the name of the variable in which to store the turn limit.

==== [store_unit] ====

Stores details about units into a [[VariablesWML#Container|container]] variable. When a unit is stored, all keys and tags in the unit definition may be manipulated, including some others, with [[InternalActionsWML#.5Bset_variable.5D|[set_variable]]]. A sample list of these tags and keys can be found [[InternalActionsWMLUnitTags|here]]. 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 (or just examine the '''[unit]''' tag(s) in any save file).

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 [[DirectActionsWML#.5Bunstore_unit.5D|[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 [[DirectActionsWML#.5Bunstore_unit.5D|[unstore_unit]]] and [http://www.wesnoth.org/macro-reference.xhtml#FOREACH FOREACH].''

* '''[filter]''' with a [[StandardUnitFilter]] as argument. All units matching this filter will be stored. If there are multiple units, they will be stored into an array of variables. The units will be stored in order of their internal ''underlying_id'' attribute, which is usually in creation order (but you normally should not depend on the order).

* '''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 not be cleared, and units which match the filter will overwrite existing elements at the start of the array, leaving any additional elements intact if the original array contained more elements than there are units matching the filter. If mode is set to ''append'', the variable will not be cleared, and units which match the filter will be added to the array after the existing elements.

* '''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.

==== [store_unit_type] ====

* '''type''': (required) the defined ID of the unit type, for example "Goblin Knight". Do not use a translation mark or it will not work correctly for different languages. A comma-separated list of IDs may also be used to store an array of unit types.

* '''variable''': the name of the variable into which to store the unit type information (default "unit_type")

==== [store_unit_type_ids] ====

* '''variable''': the name of the variable into which to store a comma-separated list of all unit type IDs

==== [store_villages] ====

Stores a series of locations of villages that pass certain criteria into an array. Each member of the result array will have members 'x' and 'y' (the position) and 'terrain' (the terrain type) and 'owner_side'. note: The only advantage/difference this tag has, in comparison to using [store_locations]terrain=*^V*, is that the amount of hexes which are considered for a possible match is previously restricted to those with villages.

* '''variable''': the name of the variable (array) into which to store the locations (default: "location")
* '''[[StandardLocationFilter]]''' tags and keys as arguments

==== [store_items] ====

Stores current items in the scenario into an array. Each entry has at least members x and y and can have all of the other keys listed in the documentation of [[InterfaceActionsWML#.5Bitem.5D|[item]]] (depending on what was set during creating the item).

*'''variable''': name of the wml variable array to use (default "items")
*'''[[StandardLocationFilter]]''' keys as arguments: only items on locations matching this [[StandardLocationFilter]] will be stored

==== [find_path] ====

A WML interface to the pathfinder. Calculates the path between a unit and a location and returns the result in a WML variable, that contains also an array for every step of the path.

*'''[traveler]''': [[StandardUnitFilter]], only the first matching unit will be used for calculation
*'''[destination]''': [[StandardLocationFilter]], only the first matching nearest hex will be used
*'''variable''': the variable name where the result will be stored, if no value is supplied 'path' will be used as default name. Each step will be stored in a [step] array inside that variable.
*'''allow_multiple_turns''': default no, if yes also moves that require more than one turn will be calculated.
*'''check_visibility''': default no, if yes the path will not be computed if some hexes are not visible due to shroud.
*'''check_teleport''': default yes, if no teleport won't be taken in account while computing path.
*'''check_zoc''': default yes, if no unit ZOCs won't be considered while calculating the path.
This is the structure of the variable returned by [find_path]:
[path]
length = the total length of the path
if the path is calculated to an impassable hex, or the move requires multiple turns
and allow_multiple_turns is no, its value will be 0.
hexes = in 1.11, this will replace the length key above
from_x, from_y = location of the unit
to_x, to_y = destination
movement_cost = total movement cost required by unit to reach that hex
required_turns = total turns required by unit to reach that hex
[step]
x, y = location of the step
terrain = terrain of the step
movement_cost = movement cost required by unit to reach that hex
required_turns = turns required by unit to reach that hex
[/step]
[/path]
To read the total length of the path on 1.10, use ''path.step.length''.<br>
{{DevFeature1.11}} ''length'' is replaced by ''hexes'' in the output array.

==== [unit_worth] ====
Takes only an inline [[StandardUnitFilter]] (only the first matching unit will be used for calculation) and outputs the following variables:
*''cost'', the current unit cost;
*''next_cost'', the cost of the most expensive advancement;
*''health'', the health of the unit in percentage;
*''experience'', current experience in percentage;
*''unit_worth'', how much the unit is worth.

Mainly used for internal AI checks, but one could in theory just do anything with it.

[event]
name=moveto
[unit_worth]
x,y=$x1,$y1
[/unit_worth]
[message]
id=$unit.id
message=_"I cost $cost gold, with $health|% of my hitpoints and $experience|% on the way to cost $next_cost|.
I am estimated to be worth $unit_worth"
[/message]
[clear_variable]
name=cost,next_cost,health,experience,unit_worth
[/clear_variable]
[/event]

=== [clear_variable] ===

This will delete the given variable. This tag can delete a scalar or an entire array; it can also delete one container at an array index. The macro [http://www.wesnoth.org/macro-reference.xhtml#CLEAR_VARIABLE CLEAR_VARIABLE] is a shortcut for this tag.

This action is good to use to clean up the set of variables; for example, a well-behaved scenario will delete any variables that should not be kept for the next scenario before the end of the scenario. One can also clear tags and variables of stored units; for example, one can remove [trait]s and [object]s.

* '''name''': the name of the variable to clear. This can also be a comma-separated list of multiple variable names.
** If a name ends with an array index, then it deletes that one container, and shifts the indexes of all subsequent containers. For example, <code>{CLEAR_VARIABLE my_awesome_array[2]}</code> deletes <code>my_awesome_array[2]</code>, but then moves <code>my_awesome_array[3]</code> to <code>my_awesome_array[2]</code>, moves <code>my_awesome_array[4]</code> to <code>my_awesome_array[3]</code>, and so on until the end of the array.
** Note that <code>{CLEAR_VARIABLE my_awesome_array}</code> deletes the entire array, but <code>{CLEAR_VARIABLE my_awesome_array[0]}</code> deletes only the first container.

== Other Internal Actions ==

Believe it or not, there are some internal actions that are not focused primarily on variables. They are all grouped here.

=== [fire_event] ===

Trigger a WML event

* '''name''': the name of event to trigger

* '''[primary_unit]''': ''(Optional)'' Primary unit for the event. Will never match on a recall list unit. The first unit matching the filter will be chosen.
**[[StandardUnitFilter]] as argument. Do not use a [filter] tag.

* '''[secondary_unit]''': ''(Optional)'' Same as '''[primary_unit]''' except for the secondary unit.
**[[StandardUnitFilter]] as argument. Do not use a [filter] tag.

* '''[primary_attack]''': Information passed to the primary attack filter and $weapon variable on the new event.

* '''[secondary_attack]''': Information passed to the second attack filter and $second_weapon variable on the new event.

=== [insert_tag] ===

Inserts a variable as WML. In other words, the value of the passed [[VariablesWML#Container|container variable]] will be injected into the game as if they had been written out in WML form. ([[#.5Binsert_tag.5D_Example|See Example]]).

Tag insertion is a special case in that it can be used in places where other ActionWML cannot be used. The basic rule is that anywhere that $variable syntax works, tag insertion will also work. In practice this means pretty much everywhere except directly within top-level scenario tags.

*'''name''': The ["name"] to be given to the tag. This must be a tag which would be valid at the place where [insert_tag] is used, for anything to happen. (For example, if used as ActionWML, it should be a [[ActionWML]] tag name, and it may be a recognized subtag such as "option" when used within a [message]).

*'''variable''': Name of the container variable which will have its value inserted into the tag.

=== [role] ===

Tries to find a unit to assign a role to.<br>This is useful if you want to choose a non-major character to say some things during the game. Once a role is assigned, you can use '''role=''' in a unit filter to identify the unit with that role (See [[FilterWML]]).<br>However, there is no guarantee that roles will ever be assigned. You can use '''[have_unit]''' (see [[ConditionalActionsWML#Condition_Tags|Condition Tags]]) to see whether a role was assigned. This tag uses a [[StandardUnitFilter]] (without [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 [[StandardUnitFilter]] 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.

* [[StandardUnitFilter]], do not use a [filter] sub-tag. SUF's role= and type= keys are not used: if you want to use them, use a nested SUF wrapped inside a [and] tag.

== Examples ==

=== Using [set_variables] to Create Arrays of WML ===

[set_variables]
name=arr
mode=replace
[value]
foo=bar
[/value]
[value]
foo=more
[/value]
[/set_variables]
{DEBUG_MSG $arr[0].foo}
{DEBUG_MSG $arr[1].foo}

This will produce two output messages, first one saying '''bar''' and next one saying '''more'''.

=== [insert_tag] Example ===

[event]
name=moveto

[set_variable]
name=temp.speaker
value=Konrad
[/set_variable]

[set_variable]
name=temp.message
value= _ "Yo Kalenz!"
[/set_variable]

[insert_tag]
name=message
variable=temp
[/insert_tag]
[/event]

This is effectively identical to:

[event]
name=moveto

[message]
speaker=Konrad
message= _ "Yo Kalenz!"
[/message]
[/event]

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

[[Category: WML Reference]]
[[Category: ActionsWML]]

WSNPP

2013-01-20T21:52:00Z

Trewe:

== Wesnoth Strategy for New or Professional Players ==

Hello all and welcome to '''Wesnoth Strategy for New or Professional Players'''. We are the WSNPP and our aim is to provide Wesnoth players both new and old with guides to improve their gameplay to become one of the top players in Wesnoth.

Also feel free to check out our Blog: "http://wsnpp.blogspot.com/"

Moving along, we plan on sharing my ideas, thoughts, theories, etc through weekly guides for everyone. There will be at least 1 guide for PWP and NWP per week

There will be two types of guides that we will be making:

* NWP - New Wesnoth Player guides
* PWP - Professional/Intermediate Wesnoth Player guides

NOTE: With PWP guides we will assume you know most of the Wesnoth game mechanics.

This will occur weekly and it will either be a NWP or PWP guide or both (depending on the time we have). Each guide will tackle different tactics, situations and the what to do and what not's and more. we will try to use diagrams or images to help you understand the explanation more and in some cases we might do videos in the future (This is still being discuessed).

At any time feel free to add comment on my guides or add ideas and theories of your own. That said, we hope you all find our guides useful. The team is also opened to any suggestions on improving WSNPP, whether it's graphics related, design or something else

Follow our blog for weekly updates.

=== NWP Guides ===

* '''Edition #1:''' [[Terrain you Pain]]
* '''Edition #2:''' [[ZOC]]
* '''Edition #3:''' [[Going Backwards]]
* '''Edition #4:''' [[Basic Build Orders]]
* '''Edition #5:''' [[Our love for villages]]
* '''Edition #6:''' [[Resistances]]
* '''Edition #7:''' [[Terrain Defence]]
* '''Edition #8:''' [[Traits]]
* '''Edition #9:''' [[NWP: Weapon abilities]]
* '''Edition #10:''' [[NWP: "Special forces. On my mark!"]]
* '''Edition #11:''' [[NWP: The Wesnoth GUI]] (Video)

=== PWP Guides ===

* '''Edition #1:''' [[The Do's and Dont's of 2v2 Battles]]
* '''Edition #2:''' [[Auxiliary Build Orders]]
* '''Edition #3:''' [[Dynamic strategies; 1 plan failed, 100 more to go]]
* '''Edition #4:''' [[What use are bats]]
* '''Edition #5:''' [[The power of 2]]
* '''Edition #6:''' [[Flank the Flank]]
* '''Edition #7:''' [[PWP: Unit composition]]
* '''Edition #8:''' [[PWP: The power of FOG]]
* '''Edition #9:''' [[PWP: Banking, "No tax, no fees, no interest"]]
* '''Edition #10:''' [[PWP: 1hp = full hp... say what!?!]]

=== The Team ===

* '''WSNPP Director: - Sarom'''
* '''Guide Author: - Sarom'''
* '''Art Director: - Zaine'''
* '''FunChillWesnoth Podcasts - So, it seems that around 20 of the voters turn out to be non-wesnoth players... I believe. SO for those who voted sincerely I will occasionally create vids of wesnoth fun ;) Other vids will be for designed for NWP and PWP.'''

[[Category:Tactics]]

PWP: The power of 2

2013-01-20T21:51:08Z

Trewe:

'''WSNPP: PWP – Edition #5''' “The power of 2”

Hello all and welcome once again to another PWP guide. In this edition, we’ll be going back to team battles, the power of 2! We’re going to follow up on guide 2 about the do’s and don’ts of 2v2 and take it to the next level.

Think to yourself, how many 2v2’s have you played (with a random team player you don’t know) and lost. Now ask yourself why? Is it because your teammate isn’t experienced enough? Is he/she playing for the first time? Is your teammate reluctant to co-operate to plans? Is it because you both aren’t co-operating each other? OR is it because of you? Well, it could be all of these or any of them OR it could be none of these questions that fit the reason as to why you failed.

Take this for example: You and a friend are experienced players, you both co-operate and communicate well with each other and you just know all your stuff about Wesnoth. However you still lose the game and you wonder why. Well the answer is, you just did not integrate your strategies with each other. A slight mistake between the synchronisation between two or more players will definitely defeat. How, you might wonder?

(To simplify things say we have 4 players P1,P2,P3,P4. P1 and P2 vs P3 and P4)
Well to put it simply, you did not combine your forces. Each player, should, start off evenly out however what happens when P1 pushes on the left side of the map and P2 pushes on the right side of the map? Well most of the time you’d win since you can surround, trap and kill the enemy leaders. It’s a good tactic but what happens when the enemy team (P3,P4) both pushes on the left side of the map. That one army is now going against two armies (P1 vs P3 and P4).

Several things can occur but the most likely case scenario is that players 3 and 4 would win with little or no casualties. Now hang on a sec not all is lost, player 2 still has his army and is advancing with no confrontation on the right side of the map. The leaders are undefended and vulnerable to player’s 2 attacks. You might celebrate, you might feel wonderful and you might win but the chances of that are slim. Why? Well P2 is trying to kill two leaders with just one army (P1 can’t do much at this stage) and P3 & P4 are attacking two leaders with an army the size of two. Seeing the picture here? Whilst P2 attacks the leaders of P3 and P4 with one army, P3 and P4 are attacking P1 and P2’s leaders. P3 and P4 are going to kill the leader faster than P2 kills theirs. Yes both players can recruit more men for defence but the most likely end result is that P1 and P2 loses.

What I am trying to express here is the importance of combining forces and moving as one large force. Strategy won’t be helpful if the enemy kills off one whole army and the last surviving army has to defend and attack two players. Not to mention the combined army may or may not have level 2’s or have units that are about to level. The same goes for 3v3’s or 4v4’s or 3v1’s etc. No matter what mind blowing strategy you have, if your friend loses his army to a giant rolling ball of death spikes, your team will most likely lose (fortunately as a TBS game relying on luck, you might win anyway) and the chances that you win are very slim.

Notice how I’m prioritising this over strategy? After all this is a strategy game so why isn’t strategy the number 1 requirement? I’m not disregarding strategy as useless and pointless. Knowing tactics can also mean between life and death but it is more useful in a 1v1 (or FFA’s) game rather than a team battle.

Generally you’ll find that in most of the favoured maps, players don’t start off really close to each other. The ideal solution is to set up a rendezvous point to combine your armies before moving out. Other cases, you share the same keep and other times you are away from each other but the map is quite small. (Isar’s Cross is an example).

Going back to ‘Luck’, almost all the time luck will always screw absolutely anything up. Who knows, your combined army might lose to an army the size of one. Bad luck, nothing you can do about it really there. Or your enemy might kill your leaders faster than your combined army does. Once again bad luck. That doesn’t mean that you should stop combining your forces. Most of the time you will win, whether you’re lucky or not so lucky (if you’re really unlucky then just try again some other time).

Unit composition (or unit combinations FYI) can also make a huge difference. Say both players decide to join forces... good 1 star for both teams. One team has troll whelps and the other team just has horsemen. Well... the most likely outcome is this: after turn 5 the troll whelps starts to engage one enemy leader whilst the horsemen kill off one leader and start engaging the other. What’s the issue here? You lacked speed but fear not, you did nothing wrong. The only reason why the orc players lost is because they got rushed with horsemen and that’s that. Those loyalist players chose a good unit composition, no players did anything wrong they just made the wrong choice of units and that happens in many wesnoth games. The only thing you could do is scout out ahead first but we’ll leave that to another guide.

Hope this one helps your 2v2’s!

'''Previous edition - #4''' [[What use are bats]]

'''Next edition - #6''' [[Flank the flank]]

'''Main menu''' – [[WSNPP]]

[[Category:Tactics]]

What use are bats?!?

2013-01-20T21:50:36Z

Trewe:

'''WSNPP: PWP – Edition #4: What use are bats?!?'''

There was once a bat called pat,

He ate a feline called cat,

He ate all day,

And failed to pay,

And became the Vampire bat.

Like the poem? As it implies, bats are useful and annoying at the same time. SO how useful are bats? Well believe it or not, they can change the tides of many battles in your favour or the enemies depending on how you use them.

Most people don’t use them and I understand why too. They cost 13gp and they’re a level 0 unit that can be killed in one shot with a Heavy infantry during dawn or dusk (not counting traits). However if you’re an undead player don’t neglect the usefulness of a bat or a few bats.

Let’s take a look at ‘bat’ in general, I won’t go to specific details such as defences and resistance but we should all know the basic and common thoughts of bats which is the fact that bats are fast but weak starting off. Upon reaching level 1 (Blood Bats) they’re still pretty bad compared to a spearman or skeleton soldier. However once they reach level 2 (Vampire Bats), they are fairly deadly.

A level 0 bat can be very useful when used correctly. In, the rare cases, where you fight a player who uses bats the most likely strategy that the player will utilised would be village capturing. This is a valid and the most useful tactic however we can go further and level bats. *In some rare cases bats are used as cannon fodder (or bait): not the best tactic but it does work sometimes.*

Level 1 bats or blood bats are basically stronger versions of bats. They have an increase in hp and damage. Same goes for vampire bats (level 2). If you do level your bats you’ll find how efficient they can be. Thanks to their drain and high defences they are good for recon, hit and run or picking of retreating 1 hp units. If utilised correctly you can trap your enemy from behind and the front using the bat’s speed and ZoC. And if you don’t wish to do that, you can always be a pain in the neck and take their villages.

All of these strategies with bats can tip of the balance between victory and defeat. I won’t explain how since you guys could predict the outcome of the tactic. Yes luck can also change the tide of battle but that’s for another edition. ;)

So ultimately bats are balanced, they’re useful and ridiculously annoying to fight against, especially in the hands of an expert. So if you’re undead next time, practise using them. Small things can make a big difference.

'''Next Edition – Edition #5:''' [[The power of 2]]

'''Previous Edition – Edition #3:''' [[Dynamic strategies; 1 plan failed, 100 more to go]]

'''Main Menu:''' [[WSNPP]]

[[Category:Tactics]]

SlovakDictionary

2013-01-20T21:45:59Z

Trewe:

{{SlovakMenu}}

Táto stránka obsahuje často používané slová a názvy. Prekladateľom odporúčame dodržiavať tieto dohodnuté názvy kvôli konzistentnosti prekladov. K niektorým prekladom je uvedené vysvetlenie. Privítame doplnenie tohto spoločného slovníka. Ak máte návrh na vylepšenie niektorého názvu, prekonzultujte ho najprv s koordinátorom prekladu. Prípadné zmeny názvov je totiž potrebné vykonať jednotne naprieč všetkými prekladanými súbormi.

== Rasy ==

=== Človek (Human) ===

==== Hrdinovia ====

* Mladík (Youth)
- Vojak (Fighter)
+ Veliteľ (Commander)
# Šľachtic (Lord)

* Starší mág (Elder Mage)

* Princezná (Princess)
- Bojovná princezná (Battle Princess)

* Temná kráľovná (Dark Queen)

* Mladý šľachtic (Noble Youth)
- Šľachtic bojovník (Noble Fighter)
+ Šľachtic veliteľ (Noble Commander)
# Šľachtic (Noble Lord)

* Zbojnícka princezná (Outlaw Princess)
- Zbojnícka kráľovná (Outlaw Queen)

* Bojovný kráľ (Warrior King)

* Vojak jazdy (Mounted Fighter)
- Bojovník jazdy (Mounted Warrior)
+ Pán jazdy (Horse Lord)

==== Základné jednotky ====

* Čatár (Sergeant)
- Poručík (Lieutenant)
+ Generál (General)
# Vrchný veliteľ (Grand Marshal)

* Jazdec kavalérie (Cavalryman)
- Dragún (Dragoon)
+ Elitný jazdec (Cavalier)

* Jazdec (Horseman)
- Rytier (Knight)
+ Paladín (Paladin)
+ Starší rytier (Grand Knight)
- Útočník (Lancer)

* Šermiar (Fencer)
- Duelista (Duelist)
+ Majster zbraní (Master at Arms)

* Burič (Ruffian)
- Poskok (Footpad)
+ Štvanec (Outlaw)
# Utečenec (Fugitive)
- Hrdlorez (Thug)
+ Bandita (Bandit)
# Zbojník (Highwayman)

* Ťažký pešiak (Heavy Infantryman)
- Špeciálny pešiak (Shock Trooper)
+ Miesiželezo (Iron Mauler)

* Mág (Mage)
- Biely mág (White Mage)
+ Mág svetla (Mage of Light)
- Červený mág (Red Mage)
+ Archmág (Arch Mage)
# Veľký mág (Great Mage)
+ Strieborný mág (Silver Mage)

* Sedliak (Peasant)
- Oštepník (Spearman)
+ Bojovník (Swordsman)
# Kráľovský gardista (Royal Guard)
+ Kopijník (Pikeman)
# Halapartník (Halbardier)
+ Oštepár (Javelineer)
- Lukostrelec (Bowman)
+ Strelec z dlhého luku (Longbowman)
# Majster lukostrelec (Master Bowman)

* Horal (Woodsman)
- Pytliak (Poacher)
+ Stopár (Trapper)
# Lovec (Huntsman)
# Zálesák (Ranger)

* Zlodej (Thief)
- Lupič (Rogue)
+ Zabijak (Assassin)

==== Zriedkavé jednotky ====

* Mladík/Dievčina (Peasant Youth)
- Stráca/Strákyňa (Watchman)
+ Pohraničiar/Pohraničiarka (Borderer)

* Dedinčan (Villager)
- Dedinský starší (Village Elder)
+ Dedinský starešina (Senior Village Elder)

* Poľovník (Peasant Hunter)
- Pasciar (Peasant Trapper)
+ Tulák (Peasant Huntsman)

* Túlavý mág (Rogue Mage)
- Tieňový mág (Shadow Mage)
+ Pán tieňov (Shadow Lord)

=== Elf (Elf) ===

==== Hrdinovia ====

- Elfský šľachtic (Elvish Lord)
+ Elfský veľmož (Elvish High Lord)

* Elfská šľachtičná (Elvish Lady)

==== Základné jednotky ====

* Elfský lukostrelec (Elvish Archer)
- Elfský hraničiar (Elvish Ranger)
+ Elfský pomstiteľ (Elvish Avenger)
- Elfský ostrostrelec (Elvish Marksman)
+ Elf ostreľovač (Elvish Sharpshooter)

* Elfský vojak (Elvish Fighter)
- Elfský kapitán (Elvish Captain)
+ Elfský maršal (Elvish Marshal)
- Elfský hrdina (Elvish Hero)
+ Elfský šampión (Elvish Champion)

* Elfský zved (Elvish Scout)
- Elfský jazdec (Elvish Rider)
+ Elfský prieskumník (Elvish Outrider)

* Elfská šamanka (Elvish Shaman)
- Elfská druidka (Elvish Druid)
+ Elfská víla (Elvish Shyde)
- Elfská čarodejnica (Elvish Sorceress)
+ Elfská zaklínačka (Elvish Enchantress)
# Elfská sylfa (Elvish Sylph)

=== Goblin (Goblin) ===

* Goblin kopijník (Goblin Spearman)
- Goblin napichovač (Goblin Impaler)
- Goblin provokatér (Goblin Rouser)

=== Gryf (Gryphon) ===

* Jazdec na gryfovi (Gryphon Rider)
- Pán gryfov (Gryphon Master)

=== Hadí človek (Naga) ===

* Hadí vojak (Naga Fighter)
- Hadí bojovník (Naga Warrior)
+ Hadí majster (Naga Myrmidon)

=== Jašter (Drake) ===

Anglické "Drake" sa prekladá ako "jašter", pretože to nie je drak ("Dragon"), ale menší príbuzný druh.

* Jašter opekač (Drake Burner)
- Ohnivý jašter (Fire Drake)
+ Pekelný jašter (Inferno Drake)
- Žiarivý jašter (Drake Flare)
+ Plamenný jašter (Drake Flameheart)

* Jašter úderník (Drake Clasher)
- Jašter mlátič (Drake Thrasher)
+ Jašter dozorca (Drake Enforcer)
o Jašter vyjednávač (Drake Arbiter)
+ Jašter strážca (Drake Warden)

* Jašter vojak (Drake Fighter)
- Jašter bojovník (Drake Warrior)
+ Jašter šermiar (Drake Blademaster)

* Plachtiaci jašter (Drake Glider)
- Lietajúci jašter (Sky Drake)
+ Búrkový jašter (Hurricane Drake)

* Jašter "dych pekla" (Armageddon Drake)

=== Lesný muž (Wose) ===

* Lesný muž (Wose)
- Starý lesný muž (Elder Wose)
+ Prastarý lesný muž (Ancient Wose)

=== Morský človek (Merman) ===

* Morská novicka (Mermaid Initiate)
- Morská kňažka (Mermaid Priestess)
+ Morská veštkyňa (Mermaid Diviner)
- Morská zaklínačka (Mermaid Enchantress)
+ Siréna (Mermaid Siren)

* Morský vojak (Merman Fighter)
- Morský bojovník (Merman Warrior)
+ Triton (Merman Triton)
+ Morský ťažký pešiak (Merman Hoplite)

* Morský lovec (Merman Hunter)
- Morský kopijník (Merman Spearman)
+ Morský oštepník (Merman Javelineer)
- Morský vrhač sietí (Merman Netcaster)
+ Morský zamotávač (Merman Entangler)

=== Nemŕtvy (Undead) ===

==== Základné jednotky ====

* Temný učeň (Dark Adept)
- Temný čarodejník (Dark Sorcerer)
+ Černokňažník (Necromancer)
+ Kostej (Lich)

* Duch (Ghost)
- Mátoha (Wraith)
+ Prízrak (Spectre)
- Tieň (Shadow)
+ Nočný des (Nightgaunt)

* Ghúl (Ghoul)
- Mrchožrút (Necrophage)

* Kostlivec (Skeleton)
- Umrlec (Revenant)
+ Kostlivý hrdina (Draug)
- Kostlivý šermiar (Deathblade)

* Kostlivec lukostrelec (Skeleton Archer)
- Kostlivec ostreľovač (Bone Shooter)
+ Prekliaty luk (Banebow)

* Chodiaca mŕtvola (Walking Corpse)
- Bezduchý (Soulless)

==== Zriedkavé jednotky ====

* Učeň (Initiate)
- Pán smrti (Deathmaster)
+ Starší kostej (Demilich)
# Prakostej (Dread Lich)

* Prastarý kostej (Ancient Lich)

* Čokobon (Chocobone)

* Temný duch (Dark Spirit)

* Drak kostlivec (Skeletal Dragon)

* Panoš smrti (Death Squire)
- Rytier smrti (Death Knight)

* Kostlivý jazdec (Skeleton Rider)
- Kostlivý rytier (Bone Knight)

=== Netopier (Bat) ===

* Pani upírov (Vampire Lady)

* Netopier upír (Vampire Bat)
- Krvavý netopier (Blood Bat)

=== Ohyzd (Ogre) ===

* Mladý ohyzd (Young Ogre)
- Ohyzd (Ogre)

=== Ork (Orc) ===

==== Základné jednotky ====

* Ork veliteľ (Orcish Leader)
- Ork vládca (Orcish Ruler)
+ Ork náčelník (Orcish Sovereign)

* Ork lukostrelec (Orcish Archer)
- Ork kušostrelec (Orcish Crossbowman)
+ Ork ostreľovač (Orcish Slurbow)

* Ork vrah (Orcish Assassin)
o Ork zabijak (Orcish Slayer)

* Ork pešiak (Orcish Grunt)
- Ork bojovník (Orcish Warrior)
+ Ork vojvoda (Orcish Warlord)

==== Zriedkavé jednotky ====

* Morský ork (Sea Orc)

* Ork mladý šaman (Novice Orcish Shaman)
- Ork šaman (Orcish Shaman)
+ Ork starý šaman (Old Orcish Shaman)

Názov ork skloňujeme nasledovne (v poradí podľa pádov):
*ork
*orka
*orkovi
*orka
*orkovi
*orkom

*orkovia
*orkov
*orkom
*orkov
*orkoch
*orkmi / orkami

Prídavné mená:
*orkský (otrasné, ale ak dobre vidím zatiaľ nikto v prekladoch nepoužil "orčí")
*orkského
*orkskému
*orkského
*orkskom
*orkským

=== Saur (Saurian) ===

* Saur prieskumník (Saurian Skirmisher)
- Saur zákerák (Saurian Ambusher)
+ Saur prepadávač (Saurian Flanker)

* Saur šaman (Saurian Augur)
o Saur veštec (Saurian Oracle)
o Saur liečiteľ (Saurian Soothsayer)

=== Trol (Troll) ===

* Trol hrdina (Troll Hero)
- Veľký troll (Great Troll)

* Trol mláďa (Troll Whelp)
- Trol (Troll)
+ Trol bojovník (Troll Warrior)
- Trol vrhač (Troll Rocklobber)

* Trol šaman (Troll Shaman)

=== Trpaslík (Dwarf) ===

* Trpaslík vojak (Dwarvish Fighter)
- Trpaslík obrnenec (Dwarvish Steelclad)
+ Trpaslík šľachtic (Dwarvish Lord)

* Trpaslík strážca (Dwarvish Guardsman)
- Trpaslík obranca (Dwarvish Stalwart)
+ Trpaslík ochranca (Dwarvish Sentinel)

* Trpaslík hromobijca (Dwarvish Thunderer)
- Trpaslík hromový strážca (Dwarvish Thunderguard)
+ Trpaslík dračí strážca (Dwarvish Dragonguard)

* Trpaslík zurvalec (Dwarvish Ulfserker)
- Trpaslík zúrivec (Dwarvish Berserker)

* Trpaslík učenec (Dwarvish Runemaster)

=== Vlk (Wolf) ===

* Vlčí jazdec (Wolf Rider)
- Goblin rytier (Goblin Knight)
+ Vlčí pán (Direwolf Rider)
- Goblin rabovač (Goblin Pillager)

=== Potvory (Monsters) ===

* Blatovec (Mudcrawler)
- Veľký blatovec (Giant Mudcrawler)

* Chápadlo z hlbín (Tentacle of the Deep)

* Morský had (Sea Serpent)

* Obrí škorpión (Giant Scorpion)

* Obrí pavúk (Giant Spider)

* Ohnivý drak (Fire Dragon)

* Sépia (Cuttle Fish)

* Yeti (Yeti)

* Chiméra (Cockatrice)

=== Ostatné ===

* Brána (Gate)
* Strážna veža (Watch Tower)
* Galeóna (Galleon)
* Obchodná loď (Transport Galleon)
* Pirátska loď (Pirate Galleon)
* Ohnivá guľa (Fireball)

== Frakcie (Fractions) ==

* Náhodná (Random)

* Aliancia Knalgy (Knalgan Alliance)
* Jašteri (Drakes)
* Lojalisti (Loyalists)
* Nemŕtvi (Undead)
* Rebeli (Rebels)
* Severania (Northerners)

* Aliancia svetla (Alliance of Light)
* Aliancia temnoty (Aliance of Darkness)

== Vlastnosti (Traits) ==

* nebojácny (fearless)
* inteligentný (intelligent)
* odolný (resilient)
* silný (strong)
* rýchly (quick)
* obratný (dextrous)
* životaschopný (healthy)
* hlúpy (dim)
* weak (slabý)
* verný (loyal)
* nemŕtvy (undead)
* mechanický (mechanical)
* divoký (feral)
* elementálny (elemental) [napadá niekoho lepší preklad? "živelný" tiež nie je úplne ono]
* starý (aged)

* poriadok (lawful)
* neutrál (neutral)
* chaos (chaotic)
* na rozhraní (liminal) [napadá niekoho lepší preklad?]

== Schopnosti (Abilities) ==

* kŕmenie (feeding)
* lieči (cures)
* neoblomný (steadfast)
* nočné zakrádanie (nightstalk)
* osvetľuje (illuminates)
* ponorenie (submerge)
* prepad (ambush)
* priebojný (skirmisher)
* regeneruje (regenerates)
* teleport (teleport)
* utajenie (concealment)
* uzdravuje (heals)
* velenie (leadership)

== Špeciálne zbrane (Weapon specials) ==

* húf (swarm)
* choroba (plague)
* jed (poison)
* magický (magical)
* presný (marksman)
* prvý úder (firststrike)
* spomaľuje (slow)
* výpad (charge)
* vysaje (drains)
* zákerný (backstab)
* zúrivý (berserk)

* skamenenie (pertify)

== Útok (Attack) ==

* sečný (blade)
* bodný (pierce)
* tupý (impact)
* oheň (fire)
* mráz (cold)
* mystický (arcane)

* úder (strike)
* zranenie (damage)

== Terén (Terrain) ==

* odkrývanie mapy (shroud) (= zatiaľ neobjavený terén)
* hmla (fog [of war])

=== Neprekonateľný (impassable) ===

* stena jaskyne (cave wall)
* neprekonateľné hory (impassable mountains)

=== Neschodný (unwalkable) ===

* kaňon (canyon)
* trhlina (chasm)
* priepasť (abyss)
* láva (lava)

=== Podzemný (underground) ===

* jaskyňa (cave)
* osvetlená jaskyňa (illuminated cave)
* skalnatá jaskyňa (rockbound cave)

=== Vodný (water) ===

* hlboká voda (deep water)
* plytká voda (shallow water)
* riečny brod (river ford)
* pobrežný útes (coastal reef)

=== Stavby ===

* pevnosť (keep)
* hrad (castle)
* tábor (encampment)

* dedina (village)
* dedina v púšti (desert village)
* dedina v tropickom lese (tropical forrest village)
* zasnežená dedina (snow village)
* ponorená dedina (submerged village)

* trpasličí hrad (dwarven castle)
* ruina, zatopená ruina, ruina v močiari (ruin, sunken ruin, swamp ruin)

* most (bridge)
* veterný mlyn (windmill)

=== Ostatný ===

* močiar (swamp)
* piesok, púšť (sand, desert)
* sneh, ľad (snow, ice)

* rovina, cesta, prach, savana (flat/grassland, road, dirt, savanna)
* les, tropický les, zasnežený les, oáza (forrest, tropical forrest, snow forrest, oasis)
* listnatý les, zmiešaný les (deciduos forrest, mixed forrest)
* kopce, púštne kopce, zasnežené kopce (hills, desert hills, snow hills)

* hory, púštne hory (mountains, desert mountains)
* hubový porast (mushroom grove)

== Denná doba (time of day) ==

* svitanie (dawn)
* ráno (morning)
* popoludnie (afternoon)
* súmrak (dusk)
* prvá hliadka (first watch)
* druhá hliadka (second watch)

* podzemie (underground)

== Všeobecné slová ==

* scéna (scenario)
* denná doba (time of day)
* výprava (campaign), niekedy aj príbeh
* zlato, zlatky (gold)
* úroveň [jednotky] (level)
* životy (HP, hitpoints)
* skúsenosti (XP, experience [points])
* R.W. (YW) [= roku Wesnothu, letopočet]

== Všeobecné poznámky ==

V prekladoch je nutné dávať pozor na gramatické odlišnosti angličtiny a slovenčiny. Napríklad radové číslovky majú v slovenčine na konci bodku. Takže "Garard II" -> "Garard II." alebo "YW" -> "R.W.", pretože ide o skratku z "Rok Wesnothu".

Taktiež je možné niektoré krkolomné mená hrdinov poslovenčiť (napr. "Asheviere" -> "Aševiera"). Ale nie je to nutnosť, záleží od pocitu prekladateľa.

Z tohto pohľadu by sa napríklad "th" v názvoch malo poslovenčiť na "t". Avšak potom by vznikol "Wesnoth" -> "Wesnot", čo by zase bolo veľmi zvláštne, keďže je to samotný názov a značka hry.

[[Category:Translations]]

NotSpellingMistakes

2013-01-20T21:40:22Z

Trewe:

This page exists to collect some notes for non-native speakers of English, who have a tendency to read certain archaic dialect words and usages as incorrect.

== Not Broken, Don't Fix It ==

For the plural of "dwarf" we use Tolkien's form "dwarves", not "dwarfs". This is probably expected by native speakers, as it has become general in English since the early 1970s.

In ''An Orcish Incursion'' and elsewhere, "march" is ''not'' a typo for "marsh"; also, in ''Liberty'', "marchlander" is not a typo for "marshlander". "The marches" is archaic English for the border country of a kingdom. The word was originally Norse "mark" and is related to the ordinary English word "mark"; it also appears as an element in the place name "the Estmark Hills" which is "the hills of the eastern border".

In ''Son Of The Black Eye'', the phrasing "the River Bork" is correct. Modern English usage would favor "the Bork River", but "the River Bork" is historically common and still used in fantasy literature.

In ''Son Of The Black Eye'', "whupping" is a Southern American rural dialect word - a rather rough and rude one - that means "a severe beating", either as verb or noun. It is an appropriate word for Orcs to use.

In ''Liberty'' and ''Two Brothers'' we make an exception to the normal rule of using American spellings in preference to British in the base text. Thus, "Grey Woods" rather than "Gray woods". We do this because to anyone who notices the difference, "Grey" will probably sound slightly archaic.

In ''Sceptre of Fire'' we make another exception: "scepter" is spelled British fashion, for the same reason.

In ''Northern Rebirth'' and elsewhere, do not mistakenly change the verb 'preying' to 'praying'. They mean different things.

In ''Northern Rebirth'' and elsewhere, "to espy" is an early-modern-English variant of the verb "to spy" inserted as a deliberate archaism. The form "espied" occurs as well. (compare "espionage")

In ''Heir To The Throne'', the word "thutter" is not a misspelling of "thunder". It is a rare and specialized word describing a fast series of striking or slapping sounds, found mainly in SF novels and possibly invented by the writer Poul Anderson. In modern English one might speak, for example, of the thutter of helicopter blades.

In the Dwarvish unit descriptions and elsewhere, the correct plural of "staff" is not "staffs" but "staves". Thus "one Dragonguard's staff" but "the staves of the Dragonguards". Compare "hoof" vs. "hooves" and "dwarf" vs. "dwarves".

Remember that we capitalize the name of a race when (and only when) referring to the entire race. Thus: "the lore of the Elves", but "a band of elves".

==Usages to Avoid==

* '''alot''' – 'a lot' should be two words, unless you intended to write 'allot', meaning 'allocate'.

* '''alright''' – Technically, 'alright' ''is'' correct; it's a back formation, derived in the same way as 'already', and it can be traced back for decades. But it looks very modern. As we usually want a more archaic tone for Wesnoth, please use '''all right''' as two words instead. Consider using "Very well."

* '''anymore''' – No, this ''is'' wrong. '''any more''' should be two words.

* '<b>being through with</b>' – Constructs such as 'I am through dealing with these people' are also modern. Use sparingly.

* '<b>Great.</b>' – Not necessarily wrong, but very modern, especially when used ironically.

* '''guys''' – Very modern usage. Please avoid.

* '''malus''' – The opposite of bonus. Unfortunately, while it's a convenient coinage this word is not yet widely accepted. It appears in the Urban Dictionary, but no other online authorities list it yet. A better opposite for 'bonus' is ''penalty''.

* '''nevermind''' – Two words, please.

* '''OK, okay''' – Modern; avoid.

* '<b>Princess</b>' – Addressing a princess as 'Princess' is an egregious, tin-eared piece of George Lucas-level modern phrasing. It's not even correct in the real world. Correct Earth etiquette is to call her 'Your Royal Highness' when you first meet her, thereafter, 'Ma'am' (pronounced 'mam'). Search for 'Correct terms of address' if you have characters in your campaign for whom you need to get it right, or check this (and other) etiquette link(s) on Wikipedia: [http://en.wikipedia.org/wiki/Forms_of_address_in_the_United_Kingdom]. Any character born a noble ''will'' know this stuff, and will automatically get it right; to them, it's ingrained habit. Other characters might not, unless they're higher-level, better-educated, or have been briefed on what to do. But in formal encounters, such as meeting a (potential) enemy noble for the first time, characters will often at least try to be polite. Of course, Wesnoth etiquette is not necessarily the same as Earth etiquette. We haven't defined the rules for Wesnoth etiquette yet, and the Wikipedia article linked above is far more detailed than we'll ever need. Nevertheless, when we eventually do define our etiquette rules, they will be mostly Earth-like, and not George Lucas-like. Also look up the rules on lèse majesté (although those rules do only apply to sovereigns, not mere princesses), and bear in mind that any poor ignoramus who did address a princess as "Princess" would probably be taken away and flogged. This applies to other noble titles as well, to a greater or lesser degree. At least use phrases such as 'milady', 'my lord' and so on.

* '<b>Right.</b>' – Not necessarily wrong, and preferable to 'Great.', but still very modern, especially when used ironically. Try 'Aye', or 'Yes', or 'Yea' instead.

* '<b>technically</b>' – Modern; use sparingly.

* '<b>Uh, Um, Er,</b>' – When they appear, these noises tend to be used in a modern way. You'll find 'O' and 'Oh' and 'Ah' and 'Ho' and 'Ha' in Shakespeare, but not 'Uh'. Instead of starting a sentence with 'Uh,' try to find a more archaic way of phrasing it.

* '<b>'Yeah.</b>' – Modern phrasing.

===Fantasy, archaic and other terms clarified===

* '''alternate/alternative'''

''Alternate'' means 'one, then the other, then the first, and so on', ''alternative'' means ''an''other. 90% of the time, people incorrectly use 'alternate' when they should be using 'alternative'. If it's a choice of two, you should use '''alternative'''.

* '''behold'''

''Behold'' means 'see'. This means you can't behold sounds, or smells.

* '''besieged/beset'''

You can only be ''besieged'' if you're on some sort of defensible structure, but you don't have to be outmatched.

You can be ''beset'' in the middle of a flat featureless plain, but only if you're outmatched or close to it.

* '''breech/breach'''

A ''breach'' is a break. Breach can also be a verb.

"Once more unto the breach, dear friends!", as King Henry V once said.

A ''breech'' is part of a gun. Breech can't be a verb.

* '''breeches'''

''Breeches'' also means a type of trousers or pants that usually extend to the knee. Hence also 'knee breeches'. May sometimes be known as 'breeks'.

* '''Hear hear'''

Never 'Here here'. 'Hear hear' is short for 'Hear him, hear him', and originated in the English parliament in the 18th century.

* '''horde/hoard'''

A ''horde'' of barbarians.

A ''hoard'' of treasure. Hoard can also be a verb.

*'''prey/pray'''

Predators ''prey'' on their ''prey''. (verb and noun)

Priests ''pray'' prayers. (verb and noun)

The insects are known as ''praying mantises''.

* '''ravish/ravage'''

''Ravish'' has sexual connotations which ''ravage'' does not.

You can ravish a fair maiden, and an old crone could have ravaged features.

You can ravage the land. You can't ravish the land, however.

* '''rise up'''

'Rise up' usually means 'rebel', and it is a rather inelegant term for 'advance'.

* '''wield'''

''Wield'' is a verb referring to carrying or using a weapon. A phrase such as 'he wields his father's enchanted sword and boots' implies the existence of a new martial art of some kind. Presumably you tie the laces together and use the boots as a sort of bola...

== UTF-8==

The mainline campaigns are being switched to UTF-8. We are adopting the use of the following glyphs:

en dash: – U+2013 (8211)
em dash: — U+2014 (8212)
horizontal bar: ― U+2015 (8213) aka quotation bar
minus sign: − U+2212 (8722)
apostrophe: ’ U+2019 (8217) same character as the right single quote
left single quote: ‘ U+2018 (8216)
right single quote: ’ U+2019 (8217) same character as the apostrophe
left double quote: “ U+201C (8220)
right double quote: ” U+201D (8221)

This replaces the current uses of - ' and -- in dialogue, most of which have already been cleared out. If you see characters such as "'''... the landâ€™s very heart...'''" instead of "'''... the land’s very heart...'''" (the exact triplet shown may vary depending on your operating system), your system/editor/viewer/whatever is not displaying UTF-8 characters correctly.

We are also adopting the use of Pango-style markup, allowing us to mark up text with colours, bold, italics and large or small text.

[[Category:Writing]]

MP Tutorial

2013-01-20T21:24:03Z

Trewe:

{| style="float:right;"
|
__TOC__
|}
If you want to play Multiplayer games and are unsure of how, or seek more information on the workings of Wesnoth multiplayer, this is the place for you. Welcome to our MP tutorial.
<BR/><BR/><BR/>
This tutorial was designed for version 1.4 of Battle for Wesnoth, but most information here is still accurate.
<BR/><BR/>
Don't be daunted by the length of this page. It's not a required read, meant mostly as a bulletproof description on how to do everything on multiplayer and you can skim through it pretty quickly.

=== Multiplayer menu ===

<div class="thumb tright"><div>
[http://img140.imageshack.us/img140/1740/menu1zw9.png http://img140.imageshack.us/img140/1740/menu1zw9.th.png]
<div class="thumbcaption">Battle for Wesnoth main menu</div></div>
</div>

The first thing you need to do if you want to play a multiplayer game is to choose which kind of game you want to play.

* Click the multiplayer button in the general menu of wesnoth.

A new window will pop-up, asking you what kind of multiplayer game you want to play :

<div class="thumb tright"><div>
[http://img142.imageshack.us/img142/1139/menu2lu0.png http://img142.imageshack.us/img142/1139/menu2lu0.th.png]
<div class="thumbcaption">Pop-up window</div></div>
</div>

* Put your username on the top.

Your username is how you will appear on the servers and during games. The next time you will click on the multiplayer button on the main screen, this username will be automatically set, but you will be able to change it anytime you come back to this pop-up window. It is advised that you keep the same username (in 1.5, you are reserved your forum name), as players are often recognized by their names, and so you will build a reputation if you use the same name each time you play.

* Choose the kind of game you want to play.

Under your username, you now have three choices:
* Join official server : Allows you to join the official Battle for Wesnoth server, where most of the multiplayer games are played.
* Connect to host/server : Allows you to connect to a different server, useful when the official server is down for example...
* Local game : Allows you to play a multiplayer game on a sole computer, this is Battle for Wesnoth "Hot-Seat" mode.

Double click on the selected option or press the OK button to start playing. A click on the cancel button will bring you back to the main menu.

==== Welcome to the official server ====

When you connect to the server, a welcome message appears in the chat area at the bottom. It contains some useful directions and occasionally some current information.<br>
Perhaps the most important part of it is the link to the official server's [[MP_CodeOfConduct|Code of Conduct]]. All players who stay on the server are supposed to have read it, but of course we can't force anyone. : )

=== The lobby ===
The multiplayer '''lobby''' is a game screen with interactive list of games, of players and a [[MP_Tutorial#Talking_to_players|simple chat interface]].
<br><br>
<div class="thumb tright"><div>
[http://img76.imageshack.us/img76/628/lobby3ar3.png http://img76.imageshack.us/img76/628/lobby3ar3.th.png]
<div class="thumbcaption">Official server</div></div>
</div>The lobby looks like the image on the right. (without the green lines of course)<br><br>

It is divided into four areas, each further described below:

* 1: [[MP_Tutorial#Menu|Menu]].
* 2: [[MP_Tutorial#Game_legend|Games]].
* 3: [[MP_Tutorial#Players|Players]].
* 4: [[MP_Tutorial#Talking_to_players|Chat Area]].

==== Menu ====

The server menu allows you to join, observe or create a game.

* To join a game, click on a game and then click on the "Join Game" button. We will see which games you can join and which you can not join in the Game legend section.
* To observe a game, click on the game you want to observe, then click the "Observe Game" button. If you want to go straight to the current turn of the game, check the "Quick Replays" box, if this box is unchecked, you will be able to see all the moves of each player during all the turns of the game.
* To create a game, click the "Create Game" button. We will go back to this in the "Create a game" section.
* "Preferences" allows you to change Battle for Wesnoth configuration, sound, video... this button brings you to the same menu that the "Preferences" button on the title page of Battle for Wesnoth.
* The "Quit" button brings you back to the title menu.

==== Game legend ====

Games appear in the lobby in different colors :

* <span style="background-color:black; color:#FFFFFF;"> '''White''' </span> are games that already have started. You can only observe those games.
* <span style="background-color:black; color:#FF2C13;"> '''Red''' </span> are games that have started and that you can't observe.
* <span style="background-color:black; color:#00FF00;">''' Green '''</span> are games you can join or observe and which haven't started yet.
* <span style="background-color:black; color:#EFEF00;">''' Yellow '''</span> are reloaded games, only people with the same name as the original players can join.

Here is an example of a "green" game, it's to say a game you are able to play :
http://img155.imageshack.us/img155/2041/gamefk7.png

* On the left appears a thumbnail of the map.
* On the top, in green, appears the name of the game : in this example "remfarkas jateka" (remfarkas's game)
* On the top right corner appears the number of players needed for the game to start, or "vacant slot". In our example you can learn that the game is designed for four players and that three players are already waiting for the game to start.

Next comes a white line where you can see a description of what is needed to play :
* First comes the "era" (Default in this example). '''"Default" means that everyone can join''' the game to play. In some other cases, you will need a specific era to play.
* Just right to the era appears the size of the map, in remfarkas's game, 20x20 tiles (which means this is a small map).
* Then comes the number of players the map is designed for (4p in the same example).
* And last is the name of the map : "Isar's Cross".

The last line shows some icons :

* The eye : http://img154.imageshack.us/img154/2681/eye1gs1.png means that you can observe this game. When you can't observe a game, this eye is scratched in red.
* The gold pile : http://img83.imageshack.us/img83/9238/goldpileak2.png tells you the number of gold you get each turn per village (in this example two gold per village per turn).
* The experience needed to level up a unit is described near this icon : http://img504.imageshack.us/img504/9579/xperienceqh7.png (70% is the required experience using map settings most of the time).
* This icon: http://img147.imageshack.us/img147/1123/fogmk5.png shows if there will be fog of war or no fog during the game.
* At last can in some cases be seen "Use Map Settings" this tells you that the game is set with the original configuration developers gave to their map.

Here are some other examples, with different configurations:

http://img293.imageshack.us/img293/6357/game2bc3.png

"jeu de Prince" (prince's game) needed that you had the "era_magic" to play, anyway it's a "white game" so you can't join.

'''''Eras can be downloaded on the main screen of Battle for Wesnoth, in the "Add-ons" menu.'''''

Also, please be sure to have the appropriate era before joining a game, if you do not have it and that the game starts, you will crash while other players will be less likely to play with you again.

On the top-right corner you can see that the game has already started and is currently at turn 1.
The game can be observed (once more, you need the appropriate era).
Players get 5 gold per village per turn, units need 30% of experience to level up and there is no fog of war.

Some other games are reserved, most of the times the word "reserved" appears in the name of the game. Ladder games are reserved for ladder players only for example.
http://img187.imageshack.us/img187/74/laddergamepg6.png

This game also uses a timer. Players will have 270 seconds per turn, a 200 seconds reserve and a 20 seconds action bonus (they will get 20 seconds more each time they do an action).

'''In any case, please read the name of the game before joining''', a lot of informations is written here by the game hosts.

==== Players ====

You may have noticed that players on the right panel can appear in different colors :
* Players <span style="background-color:black; color:#BBBFFF;"> in blue </span> are those in the currently selected game (as players or as observers).
* Players <span style="background-color:black; color:#FF2C13;"> '''in red''' </span> are players currently involved in a game.
* Players <span style="background-color:black; color:#FFFFFF;"> in white </span> are on the lobby, they are not playing and may be available for a game.

Your name appears first, then appear the names of your friends.

Names are sorted alphabetically (once with major caps and then with minor caps) for each color type.

==== Talking to players ====

You might need to talk to other players, for example to set up a game. It's not always easy to find players so you may have to ask who is interested for what kind of games... Or maybe you just want to ask something.

<div align="center">You have two ways to talk on the official server :</div>

* Using the chat box. Just type your message then press "return/enter". Your message will be visible for everyone on the lobby.
* Send a 'private message' also know as 'whisper' to a player -- it will only be visible for the player you send it to...
:'''*''' Double click on a player name on the right panel, a window will pop-up, then type your message and press Enter.
:'''*''' When combined with [[MP_Tutorial#Tips|tab-completion]], the faster way to whisper is by typing in the following command and pressing Enter:<BR>
:::: "/m username message", changing "username" the the desired nickname. To see more useful commands check the following page: [[MP_CodeOfConduct#Useful_commands|Useful_commands]]

==== Hosts ====
Any player who creates a game is that game's host.<br>
He/she is in charge of solving any in-game issues or disputes between players, possibly with the aid of the host-only [[MP_CodeOfConduct#command_type_2|commands]].

=== Time To Play ===

==== Joining a game ====

To join a game, double click on a green game or click a game and then press the "Join Game" button.
You will then be asked to choose a faction and a leader, you can also choose to play with a random faction and leader.

If you decide to change faction/hero, you can ask the host to change it for you while the game hasn't started yet.

==== Creating a game ====

<div class="thumb tright"><div>
[http://img505.imageshack.us/img505/9342/creategamekd1.png http://img505.imageshack.us/img505/9342/creategamekd1.th.png]
<div class="thumbcaption">Creating a game</div></div>
</div>
When pressing the create game button, you should see something like this :

This window will allow you to configure the game you want to play. Different options are available.

* On the top of the screen, put the desired name for your game. Battle for Wesnoth will automatically name your game "username's game" (in the language you use Battle for Wesnoth), but you can change this name just clicking in the text field.
* Under the name of your game, you have to choose the map on which you want to play. 2p maps are designed for two players, 3p for three players etc... A thumbnail of the map will appear on the left.
* Under the picture of your map, you have two buttons, "Default" is the current era for the map, you can change it by clicking, a list will show you the available eras.
* You can set a password by clicking the "Set Password..." button. When trying to join your game, people will be asked for this password. Useful for reserved games.

The right of the screen contains more gameplay options:

* The first horizontal scroll bar allows you to choose a determined number of turns before the game stops. At maximum the game will not have turn limit.
* The second scroll bar will determine the number of gold a player gains each turn by holding a village.
* The third scroll bar determines the experience required for any unit to level up.

''''' You may not be able to change some of the configurations if the box "Use map settings" is set.'''''

Then come check boxes :

* Use map settings, when checked, the game will be played with the developers configuration.
* Observers, allows observers to watch your game when checked.
* Time limit, when checked determines a time limit for each turn, you can set this time limit with the little scroll bars, where (in seconds) :
*** "Init. Limit" is the initial amount of time a player have.
*** "Turn Bonus" is the amount of time a player gets each turn.
*** "Reservoir" is a granted number of seconds each turn to complete the turn bonus.
*** "Action Bonus" is a granted number of seconds for each unit who have done an action this turn.

The right options can only be checked/unchecked when you don't use the map settings:

* Fog of war : if unchecked both player can see the whole map when playing. If checked, each player will only be able to see as far as his/her units can move next turn + one hexagon.
* Shroud of war : this is a kind of fog of war, but darker ;).
* Random start time : instead of starting at sunrise, game will start at a random time of the day.

When you have set all the desired options, press OK, if you don't want to continue further, press cancel and you'll get back to the lobby.

Once you have pressed OK, choose your faction and your hero and wait for other players.
You're also able to toggle position between players by clicking a player name. (The player whom name comes first will play first)

=== Other servers/ Local games ===

You now know all to play on any [[MultiplayerServers|other server]] or to play a local game, those work exactly the same way as described above.

=== Tips ===
These assorted bits of advice could make your stay on the server more comfortable.

==== Registering a nickname ====
registering a nick has a number of advantages:
* it makes it harder for someone to impersonate you, and people will immediately know it's you
* you can kick an old instance of your connection by reconnecting (remove the 'ghost')

&emsp;you can register a nickname by going [http://forum.wesnoth.org/ucp.php?mode=register here]<br>
<br>
'''Tab-completion'''<br>
Instead of typing a person's whole name, you can have the remainder of it filled-in by pressing the Tab key.<br>
<br>
To catch a person's attention, send them a PM or type out their whole nick as it's written. <br>
<span style="font-size:85%">(NOTE: sending PM's to people who don't know you might offend them)</span>

=== Final Word ===

Hope this tutorial has helped you, good luck, have fun ;).

=== See Also ===

* [[MP_CodeOfConduct|Wesnoth Code of Conduct]]
* [[GettingStarted|Getting Started]]
* [[CommandMode|Useful Commands]]
Maybe also some :
* [[BasicStrategy|Basic Strategy]] or
* [[AdvancedTactics|Advanced Tactics]]

[[Category:Playing_Wesnoth]]

Invasion of Eliador

2013-01-20T21:12:22Z

Trewe:

= Invasion of Eliador =

A peaceful island is about to be invaded by unknadd-ons foes travelling towards the eastern shore. It is up to a family of outlaws to warn the island's inhabitants before it's too late.

== Summarize ==

You start the campaign at Eliador, the north country of the green Isle never truly explored as read in ''The Rise of Wesnoth''.

At first there will be three different paths that can be chosen, ''Mt. Sinon'', ''Bay of Heldurin'' and ''Woods of Glorienda''. Play the the three in any order you want.

While playing more branches will be unlocked. After the three initial the suggested order is the following:

#Caves of Anwar
#Zilead's Treasure
#Bay of Heldurin (again)
#Beach of Balas
#Coast of Kelroth
#Swamp of Illien
#Plains of Varad

After defeating all puzzles, the map will lead to the final confrontation against the Invaders of Eliador.

== Scenarios [SPOILER ALARM] ==

;Mt. Sinon
:Save as many horses you can (9-10 on easy 6-7 on hard) from the spreading lava, by moving one of your heroes next to them and moving to an hill. But remember to save a place for the kids (which cannot climb mountains) on an hill too. At the end move Ardella to safety e.g. a mountain.

;Bay of Heldurin
:Talk only

;Woods of Glorienda
:capture more villages than your opponent. Each village which you have visited more than the enemy will join the cause of Eliador.

;Caves of Anwar
:Explore the dark and dangerous caves of Anwar and recruit their habitants. '''Tip:''' Ignore Ardella and move (and fight) with the kids.

;Zilead's Treasure
:Ardella has to find, open and bring back to the entrance a treasure chest. For that she should go directly to it ignoring any threads. Lure the monsters with your kids to start a fight amongst themselves.

;Beach of Balas
:While Ardella, the Monsters and any elves from Glorienda will battle and kill all fencers on the beach, move the kids into water and mount sea serpents too rescue the human prisoners.

;Coast of Kelroth
:A task for your bored horseman. Hunt down all invaders while the kids '''''should''''' mount a gryphon and search the sea for survivors.

;Swamps of Illien
:You have to play a game of [http://en.wikipedia.org/wiki/Reversi Reversi] against the crazy wizard called Othello. Move Ardella to a row/column to place an unit on the board, wait for Othello doing the same on his turn and continue reverting his moves until the board is full or (very rare) neither leader can do a move. All ''normal'' Reversi rules apply (Othello variant). Some [http://www.samsoft.org.uk/reversi/strategy.htm Strategy].

;Plains of Varad
:A Wizard duel. The scenario will continue until one of the wizard dies. '''Hint:''' Keep your thieves save and backstab whenever you can.

----

When you return to the main map, you will have at least 60 soldiers: enough to fight and win the battle. And if you keep the heroes alive they will even bring reinforcements.

The witch will arrive later and you win by killing her. Don't be scared about her defenses (70% everywhere), they are proportional to her health, meaning that the more wounded the witch will be, less defense she will have. Mages, monsters and horseman are pretty much able to deal with her.

== Tips ==

* the kids aren't that bad in combat - use them!
* level up Ardella, her inspire is worth it
* maximize experience, there isn't that much to grab
* the kids are the main heroes - use them!

== Version ==

Campaign written by Genosuke and taken over by trewe too lift it to Wesnoth 1.6 and later. Current version is 1.0.4 founded on the official server.

[[Category:Campaigns]]

Elensefar

2013-01-20T20:58:13Z

Trewe:

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.

[[Category:World_of_Wesnoth]]

Campaign/Invasion of Arendia

2013-01-20T20:52:37Z

Trewe:

== Invasion of Arendia ==

This is the Invasion of Arendia campaign wiki, basically it's purpose is to allow other users to easily modify the campaign, and submit the results to me (Ranger M), and also so that people can download new scnearios as I make them, and edit them where they can improve them. You can edit any scenario you wish and fix typing or WML errors or even contribute to the dialogues in order to make them more immersive.
There is a story page which outlines my purpose for the storyline one or two scenarios ahead, and has a general map of the whole thing.

;Spoiler Warning
Be aware that this is a complete spoiler. If you wish to contribute adequately you'll have no choice but to see the storyline.

Here's what you can edit right now
=== Scenarios ===
*1. [[Campaign/Invasion_of_Arendia/01_Reths_Beginning | Reth's Beginning]]
*2. [[Campaign/Invasion_of_Arendia/02_Reths_Training | Reth's Training]]
*3. [[Campaign/Invasion_of_Arendia/03_Border_Disturbance | Border Disturbance]]
*4. [[Campaign/Invasion_of_Arendia/04_Midnight_Raiding | Midnight Raiding]]
*5. [[Campaign/Invasion_of_Arendia/05_Threats | Threats]]
*6. [[Campaign/Invasion_of_Arendia/06_Black_Hand_Attack | Black Hand Attack]]
*7. [[Campaign/Invasion_of_Arendia/07_The_Enemy_Of_My_Enemy | The Enemy of my Enemy]]
*8. [[Campaign/Invasion_of_Arendia/08_Turlins_Fall | Turlin's Fall]]
*9. [[Campaign/Invasion_of_Arendia/09_Fleeing_East | Fleeing East]]
*10. [[Campaign/Invasion_of_Arendia/10_Sneaking_Around | Sneaking Around]]
*11. [[Campaign/Invasion_of_Arendia/11_Thrashan | Thrashan]]
*12. [[Campaign/Invasion_of_Arendia/12_Freeing_Nagas | Freeing Nagas]]
*13. [[Campaign/Invasion_of_Arendia/13_Naga_Temple | Naga Temple]]
*14. [[Campaign/Invasion_of_Arendia/14_Saving_Thrashan | Saving Thrashan]]
*15. [[Campaign/Invasion_of_Arendia/15_Through_Water_and_Stone | Through Water and Stone]]

[[Category:Campaigns - Invasion of Arendia]][[Category:Campaigns - Invasion of Arendia - Development]][[Category:Campaigns_-_by_Title]]

Guide to UMC Content

2013-01-20T18:46:18Z

Trewe: /* The Three Elves */

''This is a guide to the current (1.10.x/1.11.x) UMC campaigns for players. It aims to provide all the information not only about the story, but also about completion, difficulty and playing style of the campaign. See http://forums.wesnoth.org/viewtopic.php?f=8&t=37476 for further information, for currently non-available UMC-content please refer to http://forums.wesnoth.org/viewtopic.php?f=8&t=36733. Please edit, it is a wiki.''

=== Blueprint ===

'''Status:'''
* Broken = Does not work at all
* Incomplete = Partially written, no progress
* WIP = Partially written, progress
* Complete = Completely written, but buggy as well as potential balance issues.
* Finished = Completely written, minimal to no bugs, slight balance issues possible.

'''Length:'''

'''Author:'''

'''Maintainer:''' if not maintained by the author anymore.

'''Description:'''

'''Version: '''

'''Requirements:'''

'''Difficulty:'''

Please note: Often campaigns introducing new mechanics are listed as expert level on the add-on server, here difficulty means the raw difficulty after the mechanics are understood.

* Unbalanced = If you can't beat the hard mode, it isn't necessarily unbalanced, but if the difficulty changes erraticly from one scenario to the next and only people using the debug mode have seen the final, then it is.
* Easy
* Normal
* Hard

'''Style:'''

Please note: Many campaigns will feature more than one style. Please list the most significant ones.

* Skirmish = small to medium sized armies, your standard Wesnoth gameplay
* Dungeon = long and narrow tunnels (not every underground scenario is a dungeon, a dungeon isn't necessarily underground)
* RPG = role playing game elements such as talking with non-player-characters, item collection, dependency on a party of very few adventurers without or limited recruits
* Survival = being exposed to changing, spawning enemies while remaining on the same map
* Large Battle = Eastern Flank in Northern Rebirth, Civil War in Son of the Black-Eye
* Simulation = campaigns feat. terrain modification, alternative resources
* Boss battle = a recurring feature of Invasion of the Unknown

'''Faction/Era:'''

* Era for the whole campaign and more specifically the faction or unit composition you field.

'''Custom units:'''

* Link to the unit tree for cases that don't feel sufficiently described by Faction / Era entry.

'''Forum:'''

* Links to the feedback and development threads at forums.wesnoth.org

== Battle for Wesnoth 1.10.x - stable ==

''Campaigns available in the 1.10.x stable version.''

=== Aldur The Great ===

''This is a story about Aldur the Great.''

'''Author:''' pintercsabi

'''Status:''' Complete, but unbalanced

'''Length:''' 5 playable scenarios

'''Difficulty:''' Unbalanced

'''Style:''' Skirmish

'''Faction/Era:''' Default

'''Version:''' 1.2.2

'''Forum:''' -

'''Note:''' (Adamant14) Short unbalanced campaign, maybe abandoned. You fight with Peasants, Ruffians and Woodsman against Orcs

=== Alfhelm the Wise ===

''This is the tale of Alfhelm, called by some the Wise, son of Alfric Conqueror. This is the tale of his victories over his enemies, and his rise to power in the clans of Marauderdom. This is the tale of his journey south and his destruction of the Lavinian Empire. And this is the tale of his demise in the dark forests far to the east of his homeland.''

'''Author:''' turin

'''Maintainer:''' UnwiseOwl

'''Status:''' Complete

'''Length:''' 15 gameplay scenarios

'''Difficulty:''' Moderate

'''Style:''' Skirmish

'''Faction/Era:''' Imperial Era, Marauders.

'''Version:''' 0.6.0

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=17144

[Maintainers Note: Though this campaign is complete and playable the whole way through, the code is four years old and pretty buggy. If you notice any errors while playing, please let me know and I'll incorporate the fixes into my next revision as soon as possible.]

=== Antar, Son of Rheor ===

''This is the story about a young Lord and his first mission; sent by his father the young Lord Antar has to relieve his neighbours; he has to convince the Elves and Dwarves to ally him; he has to fight against hordes of Orcs and Endless Undead; and finally he has to defeat Mal Kazur, the mastermind who is behind all the evil.''

'''Author:''' Adamant14

'''Status:''' WIP

'''Length:''' 9 playable scenarios / 1 cutscene

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Loyalists and Elves (feat. fencer as main hero + various allies)

'''Version:''' 0.9.9

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36075

=== A Story of the Northlands ===

''A story of life and death in a remote village of the Northlands. Your village has been overrun by an orcish raid. You fight for its freedom while you wait for help to arrive.''

'''Author:''' zepko

'''Status:''' Complete

'''Length:''' 10 playable scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default + additions: you play with a custom faction of outlaws and with a custom party of loyalist knights.

'''[http://units.wesnoth.org/1.10/A_Story_of_the_Northlands/en_US/A_Story_of_the_Northlands.html Custom Units]'''

'''Version:''' 0.2.0

=== A Vision Blinded ===

''Defend the northern forest against what appeared like a routine orcish raid, and unravel the greater conspiracies that lie below its waves.''

'''Author:''' LemonTea

'''Maintainer:''' AxalaraFlame

'''Status:''' Complete

'''Length:''' 13 playable scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Elves (+ Trolls, Outlaws)

'''[http://units.wesnoth.org/1.10/A_Vision_Blinded/en_US/A_Vision_Blinded.html Custom units]'''

'''Version:''' 0.6.6

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=23463&hilit=a+vision+blinded

=== Besieged Druids ===

''A elvish school for druids comes under attack by goblins. It seems more than just a routine raid; is there something more sinister behind this attack? - In Beseiged Druids, you control Eärendil, the surviving teacher at the school, and the many and varied initiates. Not all of these are ordinary students; many have been experimenting with other forms of magic, while others are simply overachievers in some area of study. Unfortunately, they are not especially good at combat, at least initially. Together with a very small contingent of surviving guards, it is up to these students to save the island of Aleron from disaster.''

'''Author:''' Celtic Minstrel

'''Status:''' Complete

'''Length:''' 9 scenarios

'''Difficulty:''' Unbalanced

'''Style:''' Skirmish

'''Faction/Era:''' Default, Elves

'''[http://units.wesnoth.org/1.10/DruidSiege/en_US/celmin-druid-siege.html Custom units]'''

'''Version:''' 1

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=37342

=== Cities of the Frontier ===

''Settle a new town in the wilds north of the Great River.''

''This campaign makes several changes to the standard Wesnoth game mechanics, and focuses on city-building and gold management.''

'''Author:''' esci

'''Status:''' Complete

'''Length:''' Not fixed, approximately 6-10 seasons of 36 turns each

'''Difficulty:''' Normal

'''Style:''' Simulation, Survival

'''Faction/Era:''' Default, Loyalist

'''[http://units.wesnoth.org/1.10/Cities_of_the_Frontier/en_US/Cities_of_the_Frontier.html Custom units]'''

'''Version:''' 0.5.1

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36004

=== Considerate Dead ===

''As the wind goes on and on, people discover necromancer aren't always bad. Made by tribes45 - No scenarios are done, 4 playable out of ??.''

'''Author:''' tribes45 aka tribes55

'''Status:''' Incomplete, unbalanced, abandoned

'''Length:''' 5 scenarios

'''Difficulty:''' Unbalanced

'''Style:''' Skirmish

'''Faction/Era:''' Default

'''Version:''' .009

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36522

=== Count Kromire ===

''You are the blood son of a vampire lord, however when the might of the celestial crusades comes knocking, and your father is slain, you flee your lands. However you intend to return, to restore the lands of Kromire to the Kromires, to avenge your father, and most importantly, to make sure that no celestial ever dares come into your mountains again.''

'''Author:''' Velensk

'''Maintainer:''' currently none

'''Status:''' Complete

'''Length:''' 9 scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Era of Myths, Vampires

'''Version:''' 1.3.2

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=21560

=== The Dark Hordes ===

'''Status:''' Incomplete/WIP

'''Length:''' 11/?

'''Author:''' Circon

'''Maintainer:''' Various

'''Description:''' Lead fugitive dark sorcerer Gwiti Ha’atel to mastery of the undead hordes.

'''Version: '''

'''Requirements:'''

'''Difficulty:'''

'''Style:''' Skirmish

'''Faction/Era:''' Default undead

'''[http://units.wesnoth.org/1.10/The_Dark_Hordes/en_US/The_Dark_Hordes_1.html Custom Units]'''

'''Walkthrough:''' [[TheDarkHordes]]

'''Forum:''' [[http://forums.wesnoth.org/viewtopic.php?f=8&t=16576&]]

=== The Earth's Gut ===

''The year is 515YW. You are the young dwarven leader Hamel. Your tribe in the caves of Knalga is under pressure from its enemies, and resources are growing scarce. In order to forge the weapons required to resist your enemies, you must set forth and collect what ores and minerals remain.''

'''Author:''' Anonymissimus

'''Maintainer:''' Anonymissimus

'''Status:''' Incomplete

'''Length:''' 21 scenarios

'''Difficulty:''' Normal

'''Style:''' Dungeon

'''Faction/Era:''' Default, dwarves.

'''[http://units.wesnoth.org/1.10/The_Earths_Gut/en_US/the_earths_gut.html Custom units]'''

'''Version:''' 0.2.11

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=26800

'''Note:''' This campaign is a "Dwarvish dungeon crawler" and is intended to be challenging for experienced players on hard whilst suitably easy on easy.

=== Elvish Dynasty RPG ===

''You are the new ruler of an elvish kingdom! Can you lead your people to glory? This campaign is highly randomized so it will be different every time you play!''

''Sequel to Ooze Mini-Campaign''

'''Author:''' spencelack

'''Maintainer:''' Wesbane

'''Status:''' Complete

'''Length:''' 10 years, in each year choice between dialogue and fighting scenario (selected out of a large pool of possible scenarios)

'''Difficulty:''' Normal

'''Style:''' RPG, Skirmish

'''Faction/Era:''' Default, Elves

'''Version:''' 0.9.9b

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=28627

=== The Epic of Vaniyera ===

''The expansionist Lavinian Legion, led by the Imperator himself, has invaded the northern forests of the Sidhe, or Wild Elves. It is up to Leithan the Thunderblade and his advisor Vaniyera to push its armies back where they came from...''

'''Author:''' oreb, turin

'''Maintainer:''' UnwiseOwl

'''Status:''' Complete

'''Length:''' 6 scenarios

'''Difficulty:''' Hard (Don't be fooled by "novice level" in the campaign description, this one is very hard.)

[Maintainers note: Working on this issue, the next release (due at the end of November, hah!) should bring easy difficulty back to the level of a reasonable introduction to the IE, while the hard difficulty will also become slightly easier. With any luck, this will be the last release before version 1.0 of the campaign].

'''Style:''' Skirmish

'''Faction/Era:''' Imperial Era, Sidhe.

'''Version:''' 0.9.0

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=19490

=== Fall of Silvium ===

''You are Caius Regilius, Tribune of the province of Silvia, located in the northmost reaches of the Lavinian Empire at the height of its power. But the Empire has overextended itself, The city of Silvium lies seperated from the rest of the Empire by the mountains of Arendia, and is sandwiched between the Marauders and the Sidhe... war is inevitable, and the province of Silvia will almost certainly fall.''

'''Author:''' turin

'''Maintainer:''' UnwiseOwl

'''Status:''' Complete

'''Length:''' 8 scenarios

'''Difficulty:''' Medium

'''Style:''' Skirmish

'''Faction/Era:''' Imperial Era, Lavinian Legion.

'''Version:''' 0.6

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=31&t=24356

[Note: The final level of this campaign is not supposed to be winnable. It's a final blaze of glory and chance to use all your high-powered units, but to 'win' the campaign, you must lose...the ending is similar to a certain mainline campaign, but predates it.]

=== The Fall of Wesnoth ===

''As the beloved human empire of Wesnoth becomes lazy and arrogant in its peaceful state of happiness, Emperor Dantair demands the creation of another sun in a bid to destroy all evil. Or is it all for a different purpose? A man named Alitar sees it that way, and now he must survive the most evil inhabited lands if he is to stop chaos from rising, and Wesnoth from falling... This is the story of The Fall of Wesnoth.''

'''Author:''' Pewskeepski

'''Status:''' 1st part complete, 2nd WIP.

'''Length:''' 10 playable scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Outlaws

'''[http://units.wesnoth.org/1.10/The_Fall_of_Wesnoth/en_US/The_Fall_of_Wesnoth-1.html Custom units]'''

'''Version:''' 1.0.8

=== Fate of a Princess ===

''Part I: Baldres, a notorious robber baron, flees Wesnoth with his followers and sets off into the northlands to evade the king's justice. The baron's deeds and misdeeds are to change the balance of power between orcs and non-orcs throughout the northlands, and will carry consequences long after his eventual death.''

''Part II: The Greenwood elves face a crisis which demands the return of the queen's estranged half-elven half-sister, Baldres' daughter. Two brave young elves must make a perilous journey to find her and bring her back to her former home. If they fail, the whole northlands will be engulfed in war with the resurgent orcs...''

'''Author:''' SkyOne, mich, simonsmith

'''Status:''' Finished

'''Length:''' 26-29 scenarios (some dialogue-only), 2 parts

'''Difficulty:''' Normal

'''Style:''' Skirmish, Dungeon

'''Faction/Era:''' Default with additions. You play two different, unique cross-faction combinations in each part.

'''[http://units.wesnoth.org/1.10/Fate_of_a_Princess/en_US/Fate_of_a_Princess.html Custom units]'''

'''Version:''' 0.9.17

'''Required Wesnoth version:''' 1.9.12 or later

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=26327

=== Forgotten Kingdom ===

''Help Orlog, a troll chieftan, lead his people to safety in the underground and discover an ancient power long forgotten.''

'''Author:''' Limabean

'''Maintainer:''' Chrysophylax

'''Status:''' Incomplete ( but all scenarios playable and balanced )

'''Length:''' 9 playable scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Goblins, Trolls

'''[http://units.wesnoth.org/1.10/Forgotten_Kingdom/en_US/Forgotten_Kingdom.html Custom units]'''

'''Version:''' 0.1.7

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=23483

'''Note:''' (Adamant14) This campaign includes a custom Troll line. A good campaign, I hope Limabean and/or Chrysophylax will finish it.

=== Forward they Cried ===

''You are the leader of an advanced detachment that has been tasked with capturing a bridgehead while the main army prepares to attack. It should be a simple enough assignment.''

'''Author:''' Glowing Fish

'''Maintainer:''' Lord-Knightmare

'''Status:''' Finished

'''Length:''' 1 scenario ( rather a single scenario than a campaign )

'''Difficulty:''' Hard

'''Style:''' Skirmish

'''Faction/Era:''' Default Loyalists

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=23656&p=350126&hilit=forward+they+cried#p350126

'''Version:''' 1.0.0

'''Note:''' (Adamant14) Only a single scenario, but a great scenario.
(UnwiseOwl) You wouldn't want to stop thinking for a turn, and it's good for the first few turns, but this one leaves me wanting more.

=== The Founding of Borstep ===

''The chieftain of your tribe has become decadent and weak. Take over, and lead your people to a better home--whether it is already occupied or not. The Northlands in year 9W are a barbaric place, but anyone who stands in your way will learn the power of orcs!''

'''Author:''' Beetlenaut

'''Status:''' Complete

'''Length:''' 10 and 1 dialogue only

'''Difficulty:''' Hard

'''Style:''' Skirmish

'''Faction/Era:''' Default, Northerners

'''[http://units.wesnoth.org/1.10/The_Founding_of_Borstep/en_US/The_Founding_of_Borstep.html Custom units]'''

'''Version:''' 1.1.1b

''Note(Kanzil): I find the protagonist hard to sympathise with. Also, most scenarios contain interesting twists. For example, in one, each time you killed a boar it gives you extra health.''

''Note(beetlenaut--author): In most Orcish campaigns the leader is heroic or just wants peace. Krag-Ubor wants plunder and battle like all enemy Orcs in other campaigns. I '''hope''' you don't sympathize too strongly, but I don't think you need to in order to enjoy the game play.''

=== Galuldur's First Journey ===

''While the belligerence of orcs is nothing new, their intensifying attacks on a fledgling colony of elves in Pindir Forest begin to show signs of a deeper malice, forcing Galuldur, the young son of the colony's adventurous founder Galur, to venture out of his forest's friendly trees in search of help. His simple errand quickly turns into a frantic quest to unearth the roots of the mysterious evil threatening his people. As you lead him through unknown lands, Galuldur, forced to match wits with unexpected adversaries at nearly every turn in a desperate attempt to save his world, quickly learns that the world is neither a friendly nor a simple place.''

'''Author:''' mattsc

'''Status:''' Complete

'''Length:''' 8-9 scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Elves

'''[http://units.wesnoth.org/1.10/Galuldur/en_US/Galuldur.html Custom units]'''

'''Version:''' 1.1.1

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=31895

=== Grnk the Mighty ===

''All his life, puny little goblin Grnk the Frail had been dreaming about leaving the orcs and starting a better life. When he finally arrives in the human town of Shmaltupp, he realizes that the world is not as black and white as he had imagined. He also discovers that he is no ordinary goblin. Follow Grnk the Frail on his path to becoming Grnk the Mighty.''

'''Author:''' mattsc

'''Status:''' Part I complete

'''Length:''' 13 scenarios

'''Difficulty:''' Hard

'''Style:''' Skirmish, RPG

'''Faction/Era:''' Default, changing (no standard army building gameplay)

'''[http://units.wesnoth.org/1.10/Grnk/en_US/Grnk.html Custom units]'''

'''Version:''' 1.0.5

'''Required Wesnoth version:''' 1.9.5 or later

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=34970

=== Invasion from the Unknown ===

''Episode I - Seeking the Light: Long after the Fall, the last forest elves are forced to abandon their safe valley, and find themselves resorting to the dark means of necromancy in order to survive the perils and challenges of this new harsh world. May they finally free the Great Continent from its chaos, or perish in the foolish attempt of restoring peace and life to the lands.''

''Episode II - Armageddon: As the shadow of Chaos covers the entire continent, an assorted group of foolish heroes prepares a counter-attack to the Empire, with one unique goal in their minds: defeat the evil Emperor, whoever it is. Lead these courageous living and non-living warriors to victory, and rediscover lost secrets of the history.''

'''Author:''' shadowmaster

'''Maintainer:''' Espreon

'''Status:''' Finished

'''Length:''' 26 scenarios in two episodes

'''Difficulty:''' Normal

'''Style:''' Skirmish, Dungeon, Boss battle

'''Faction/Era:''' Unique. You play Elves and Undead throughout the campaign + in the 2nd part Northerners and Aragwaithi.

'''Version:''' 1.90.6

''Note (taptap): Despite its acknowledged flaws (generic hero, plot holes, deus ex machina moments, gameplay issues in the 2nd part) this is undoubtedly the most iconic campaign in UMC. It single-handedly redefines the elvish history and sketches a cosmology for the ages after the fall. With the Chaos empire and its various allies it introduces an era worth of factions to single-player play. At the same time it features some of the most beautiful maps in Wesnoth and stunning art on par with mainline campaigns.''

=== Invasion of Eliador ===
''A peaceful island is about to be invaded by unknadd-ons foes travelling towards the eastern shore. It is up to a family of outlaws to warn the island's inhabitants before it's too late.''

'''Author:''' Sam M. (Genosuke)

'''Maintainer:''' trewe

'''Version:''' 1.0.4

'''Style:''' RPG, Skirmish, Puzzle

'''Length:''' 10 scenarios + epilogue

'''Difficulty:''' Easy

'''Status:''' Complete

'''Faction:''' Default (outlaws)

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=6556

'''Wiki:''' [[Invasion_of_Eliador]]

=== Langrisser Sample Campaign ===

''The Imperial Knights of the Rayguard Empire have disrupted the peace of the village that was Hein's hometown, seeking only a girl named Liana. Fight to rescue Liana.''

'''Author:''' Morath

'''Status:''' Finished

'''Length:''' 1 playable scenario

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Elves

'''Version:''' 0.1.0.5

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36417&hilit=Langrisser

'''Wikipedia:''' [http://en.wikipedia.org/wiki/Langrisser What is Langrisser]

'''Note:''' (Adamant14) Single scenario, different from usual Wesnoth behaviour.

=== Legend of the Invincibles ===

'''''Part I: Shrouded in Darkness''' (5 chapters, 90 scenarios) - A pair of heroes, after stopping an orcish thread, are outcast into caves, where they have no other choice than to become liches in order to survive. They preserved their human appearance and moral principles, and fight in various skirmishes against evil (although using evil methods sometimes), until the Fall, when they are buried alive under the ashes of the third sun.''

'''''Part II: Into the Light''' (3 chapters, 46 scenarios at the moment) - Long after the Fall, the lich heroes awaken. Searching for more power, they manage to resurrect themselves as living beings, but this time more powerful and cleaned from the evil within them. But the evil from inside them continued to exist, and started a skirmish to conquest the world. Stopping the skirmish caused an even worse disaster...''

'''Author:''' Dugi

'''Status:''' WiP (but Part I might be considered complete)

'''Length:''' 135 (+6 talk-only) scenarios at the moment

'''Difficulty:''' Normal

'''Style:''' mostly Skirmish and Dungeon (all other styles are present as well, but less frequently)

'''Faction/Era:''' Elves, Loyalists, Undead, Dwarves; but they advance past their usual maximum level

'''Version:''' 2.4.0

''Note: The most unique feature of this campaign is its RPG-like unit development system, enemies drop items units can use, leaders are stronger than most usual units and all units get AMLA (after maximum level advancement) after reaching their maximum level (that is also increased by a load of additional level 4 units).''

=== The Library of Kratemaqht ===

''An ancient story from the old continent.''

'''Author:''' Rich Marinaccio (cephalo)

'''Status:''' Complete

'''Length:''' 17 scenarios

'''Difficulty:''' Unbalanced (some scenarios are Easy - some rather Hard)

'''Style:''' Skirmish, RPG

'''Faction/Era:''' Loyalists and custom units.

'''[http://units.wesnoth.org/1.10/Library_Of_Kratemaqht/en_US/The_Library_Of_Kratemaqht.html Custom units]'''

'''Version:''' 1.0.0

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=37798

'''Notes:''' (Adamant14) This campaign has a thought-out story, shows a great love for detail;
It includes a great custom Dragon, some brilliant custom images (fire, burning houses, burning forest) that makes the scenery / maps look very nice.

=== Panther Lord ===

''The Imperialists ambitions of pushing into the Sea States have been repeatedly thwarted and now they turn their attentions elsewhere. You are an outcast Darklander now living as a mercenary in the Sea States and the rumors you hear indicate that they will be coming to your people. Though an outcast you do not wish to see them subjugated. The spirit whose friendship caused you to be an outcast has a plan that might allow you to save them.''

'''Author:''' Velensk

'''Maintainer:''' Lavender

'''Status:''' Finished

'''Length:''' 14 scenarios

'''Difficulty:''' Hard

'''Style:''' Skirmish

'''Faction/Era:''' Era of Four Moons, Darklanders (+ a wide variety of mercenaries)

'''Version:''' 1.0.2

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=34318

=== Return of the Monster ===

''It was time for Amailoss, born from the naga queen's last egg, to leave home. Time for him to grow into a leader in his own right, and eventually become the guardian and leader of another naga city. But along the way, he became friends with an unusual mud-crawler, they met a strange young monster, discovered that a spirit had escaped from an orc prison, and the mystery of that spirit became a grave challenge for Amailoss and the many races in the region....''

''A naga campaign, involving elves, orcs, saurians, turtle-like races, and some monsters.''

'''Author:''' SkyOne

'''Status:''' Complete

'''Length:''' 16 playable, 2 dialog scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish, Dungeon

'''Faction/Era:''' Default with additions. You play a custom naga faction and carapaces (a turtle-like race).

'''[http://units.wesnoth.org/1.10/Return_of_the_Monster/en_US/Return_of_the_Monster.html Custom units]'''

'''Version:''' 0.7.1

'''Required Wesnoth version:''' 1.10.x

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36438

=== Return to Noelren ===

'''Status:''' Complete.

'''Length:''' 26 scenarios + 7 cut scenes

'''Author:''' Pyrophorus

'''Description:''' ''A story in the first Dark Age of Wesnoth. See how various heroes stick together to shun the threat of black magics, restore the secret kingdom of Noelren and install Garard I on the throne of Wesnoth. This campaign features complex scenarios, unusual objectives and units, emphasizing more on story and adventures than hardcore fighting.''

'''Version: ''' 0.7

'''Requirements:''' BfW 1.10 (not tested on 1.11)

'''Difficulty:''' Easy, unbalanced

'''Style:''' Skirmish, RPG, Large Battle, Simulation

'''Faction/Era:''' Default + custom units

'''[http://units.wesnoth.org/1.10/ReturnToNoelren/en_US/ReturnToNoelren.html Custom Units]'''

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=34685#p501026

=== Return to Ruins ===

''The humble farmers of Vertegris are summoned by Erik the General of Weldyn to put an end to an orcish raiding party. If they knew what would befall their former home... They never would have left. This is a relatively short campaign with 8 scenarios, It is still undergoing changes.''

'''Author:''' Ulfsark (Jeff Stevens)

'''Status:''' Complete

'''Length:''' 7 scenarios + 1 dialogue-only

'''Difficulty:''' Easy,Normal,Hard

'''Style:''' Skirmish

'''Faction/Era:''' Default,(Loyalists, Outlaws)

'''Version:''' 0.5.0

'''Required Wesnoth version:''' 1.10.x

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=37790&sid=9059f18497cda1219f42a626544d0ffd&p=540646#p540646

'''Note:''' (Adamant14) You play a short campaign with just a few units. Playable in a few hours, nevertheless it is fun to play.

=== Saving Elensefar ===
''Meneldur, elvish mariner of Elensefar, is driven to sea by the same orcs who attacked the city. He must gather an army willing to fight for him to regain Elensefar, his adopted homeland.''

'''Author:''' Turin

'''Maintainer:''' trewe

'''Status:''' Finished

'''Length:''' 1 year (around 12 scenarios)

'''Difficulty:''' Normal

'''Style:''' Skirmish, RPG, Simulation

'''Version:''' 1.5.2

'''Faction:''' Default Era

'''Forum:''' http://wesnoth.org/forum/viewtopic.php?t=3072&start=0

'''Wiki:''' [[SeafaringCampaign]]

<small>Labeled as Expert, recruit list changes in all scenarios</small>

=== The Roar of the Woses ===

''When the construction of a dam threatens the existence of her home, Kylix is forced on a journey to stop it.''

'''Author:''' Alarantalara

'''Status:''' Finished

'''Length:''' 10-11 scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default with Additions (primarily Saurians, Nagas, Woses)

'''Version:''' 1.2.7

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=29830

'''Note:''' (author) Potentially unbalanced on Hard difficulty due to experiments with non-standard ways to increase difficulty. This issue does not exist on the lower difficulty levels.

=== The Three Elves ===
''Three elves have just begun their adventure in the northern swampland. Will they become heroes or will they be responsible for another undead expansion?''

'''Author:''' Stanislav Hoferek

'''Maintainer:''' trewe

'''Version:''' 0.9

'''Status:''' Complete

'''Difficulty:''' Easy

'''Length:''' 8 scenarios + 2 dialogue

'''Style:''' Skirmish

'''Faction:''' Default (Elves)

'''Forum:''' (does it have one?)

=== Salt Wars ===

''Introductory campaign for the Era of Four Moons.''

''As an officer of one of the Sea States you must defend your organization from aggressive rivals.''

'''Author:''' Velensk

'''Maintainer:''' Lavender

'''Status:''' Complete

'''Length:''' 5 scenarios

'''Difficulty:''' Easy

'''Style:''' Skirmish

'''Faction/Era:''' Era of Four Moons, Sea States

'''Version:''' 0.2.1

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=31498

=== The Sojournings of Grog ===

''Grog (as starred in Under the Burning Suns) goes home.''

'''Author:''' Peter Christopher, Thomas Hockings

'''Maintainer:''' Elvish_Hunter

'''Status:''' Finished

'''Length:''' 18 playable scenarios in 2 parts

'''Difficulty:''' Normal

'''Style:''' Skirmish, Dungeon, Large Battle

'''[http://units.wesnoth.org/1.10/The_Sojournings_of_Grog/en_US/The_Sojournings_of_Grog.html Custom units]'''

'''Faction/Era:''' Default. Most of the time you play trolls and some desert elves accompanying Grog.

'''Version:''' 3.0.1

=== Unlikely Alliance ===

''Play as the members of an alliance between the elves, drakes, and undead after the Fall of Wesnoth.''

'''Author:''' Creativity

'''Status:''' Broken ( Abandoned )

'''Length:''' 2 broken scenarios

'''Difficulty:''' Unbalanced

'''Style:''' -

'''Faction/Era:''' -

'''Version:''' 0.1

'''Forum:''' -

'''Note:''' (Adamant14) Did not work at all. Seems abandoned.

=== Up from Slavery ===

''The Orcei are captives in the imperial city of Lavinium, gladiators performing for the emperor Optus Maximus. All it will take, however, is one orc to lead his people to freedom. The Samnis called Sparxus may be that orc.''

'''Author:''' turin

'''Maintainer:''' UnwiseOwl

'''Status:''' Complete

'''Length:''' 7 scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish, Arena (= No recruit, small group gladiator fights)

'''Faction/Era:''' Imperial Era, Orcei Gladiatores

'''Version:''' 0.6.0

[Maintainer's Note: At some point, I am intending to completely re-work this campaign to be a multi-player campaign, with one side led by Sparxus and one by Gravirivus. If anyone would like to take this on or has ideas for how to accomplish this, let us know. Nevertheless, its playable as a single player campaign now with some nice ideas that could be developed further.]

=== Warmaster ===
''One day the scout of your king brings a mysterious little stone, called Zrai-Stone, back from one of his trips. Soon that stone causes a lot of trouble...''

'''Author:''' Conkinator

'''Maintainer:''' trewe

'''Version:''' 1.3.5

'''Status:''' Finished

'''Length:''' 16 battle + 2 bonus + 1 epilogue scenarios

'''Difficulty:''' Hard

'''Faction:''' Default (loyalists)

'''Style:''' Skirmish, Survival

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=15527

=== Way of Dragon ===

''The story of what might happen if a person against his will transform into a dragon...''

'''Author:''' DrakeDragon

'''Status:''' Complete

'''Length:''' 7 playable scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish/RPG

'''Faction/Era:''' Default Loyalists

'''Version:''' 1.2.0

'''Forum:''' [http://forums.wesnoth.org/viewtopic.php?f=8&t=37876 Wesnoth Forum] [http://uporoom.ru/index.php/topic,179.0.html Russian Forum]

'''Note:''' (Adamant14) Promising short campaign, you play with just a few units.

== Battle for Wesnoth 1.11.x - development ==

''Campaigns available in the 1.11.x development version.''

''Please note: Battle for Wesnoth 1.11.0 features a bug that messes up the selection of difficulty levels.''

=== Antar, Son of Rheor ===

''This is the story about a young Lord and his first mission; sent by his father the young Lord Antar has to relieve his neighbours; he has to convince the Elves and Dwarves to ally him; he has to fight against hordes of Orcs and Endless Undead; and finally he has to defeat Mal Kazur, the mastermind who is behind all the evil.''

'''Author:''' Adamant14

'''Status:''' WIP

'''Length:''' 9 playable scenarios / 1 cutscene

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Loyalists and Elves (feat. fencer as main hero + various allies)

'''Version:''' 0.9.9

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36075

'''Note:''' (Adamant14) The campaign currently did not work with BfW 1.11.0, so please use BfW version 1.11.1!

=== Legend of the Invincibles ===

'''''Part I: Shrouded in Darkness''' (5 chapters, 90 scenarios) - A pair of heroes, after stopping an orcish thread, are outcast into caves, where they have no other choice than to become liches in order to survive. They preserved their human appearance and moral principles, and fight in various skirmishes against evil (although using evil methods sometimes), until the Fall, when they are buried alive under the ashes of the third sun.''

'''''Part II: Into the Light''' (3 chapters, 46 scenarios at the moment) - Long after the Fall, the lich heroes awaken. Searching for more power, they manage to resurrect themselves as living beings, but this time more powerful and cleaned from the evil within them. But the evil from inside them continued to exist, and started a skirmish to conquest the world. Stopping the skirmish caused an even worse disaster...''

'''Author:''' Dugi

'''Status:''' WiP (but Part I might be considered complete)

'''Length:''' 135 (+6 talk-only) scenarios at the moment

'''Difficulty:''' Normal

'''Style:''' mostly Skirmish and Dungeon (all other styles are present as well, but less frequently)

'''Faction/Era:''' Elves, Loyalists, Undead, Dwarves; but they advance past their usual maximum level

'''Version:''' 2.4.0

''Note: The most unique feature of this campaign is its RPG-like unit development system, enemies drop items units can use, leaders are stronger than most usual units and all units get AMLA (after maximum level advancement) after reaching their maximum level (that is also increased by a load of additional level 4 units).''

=== Ruthless ===

''A bard (an aging criminal) is walking in wasteland. Nothing but two hands in his pockets, and nothing but stones around. Suddenly he sees a knight on errand--a dangerous opponent, especially in broad daylight. The two strangers are soon sitting by the campfire, and the bard is telling a story.
(Beginner level, 10+ fights).''

'''Author:''' homunculus

'''Status:''' Finished

'''Length:''' 12 playable scenarios + 5 cutscene scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default (Orcs)

'''Version:''' 1.0.4

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=37874

'''Note:''' (Adamant14) Recommendable campaign, with smart unusual ideas and a good detailed story.
You fight with few units on small but perfect maps. About the difficulty: The author describes his campaign as 'beginner level', but for me the difficulty is rather NORMAL than EASY.

[[Category:Campaigns|*]]

Guide to UMC Content

2013-01-18T13:58:01Z

Trewe:

''This is a guide to the current (1.10.x/1.11.x) UMC campaigns for players. It aims to provide all the information not only about the story, but also about completion, difficulty and playing style of the campaign. See http://forums.wesnoth.org/viewtopic.php?f=8&t=37476 for further information, for currently non-available UMC-content please refer to http://forums.wesnoth.org/viewtopic.php?f=8&t=36733. Please edit, it is a wiki.''

=== Blueprint ===

'''Status:'''
* Broken = Does not work at all
* Incomplete = Partially written, no progress
* WIP = Partially written, progress
* Complete = Completely written, but buggy as well as potential balance issues.
* Finished = Completely written, minimal to no bugs, slight balance issues possible.

'''Length:'''

'''Author:'''

'''Maintainer:''' if not maintained by the author anymore.

'''Description:'''

'''Version: '''

'''Requirements:'''

'''Difficulty:'''

Please note: Often campaigns introducing new mechanics are listed as expert level on the add-on server, here difficulty means the raw difficulty after the mechanics are understood.

* Unbalanced = If you can't beat the hard mode, it isn't necessarily unbalanced, but if the difficulty changes erraticly from one scenario to the next and only people using the debug mode have seen the final, then it is.
* Easy
* Normal
* Hard

'''Style:'''

Please note: Many campaigns will feature more than one style. Please list the most significant ones.

* Skirmish = small to medium sized armies, your standard Wesnoth gameplay
* Dungeon = long and narrow tunnels (not every underground scenario is a dungeon, a dungeon isn't necessarily underground)
* RPG = role playing game elements such as talking with non-player-characters, item collection, dependency on a party of very few adventurers without or limited recruits
* Survival = being exposed to changing, spawning enemies while remaining on the same map
* Large Battle = Eastern Flank in Northern Rebirth, Civil War in Son of the Black-Eye
* Simulation = campaigns feat. terrain modification, alternative resources
* Boss battle = a recurring feature of Invasion of the Unknown

'''Faction/Era:'''

* Era for the whole campaign and more specifically the faction or unit composition you field.

'''Custom units:'''

* Link to the unit tree for cases that don't feel sufficiently described by Faction / Era entry.

'''Forum:'''

* Links to the feedback and development threads at forums.wesnoth.org

== Battle for Wesnoth 1.10.x - stable ==

''Campaigns available in the 1.10.x stable version.''

=== Aldur The Great ===

''This is a story about Aldur the Great.''

'''Author:''' pintercsabi

'''Status:''' Complete, but unbalanced

'''Length:''' 5 playable scenarios

'''Difficulty:''' Unbalanced

'''Style:''' Skirmish

'''Faction/Era:''' Default

'''Version:''' 1.2.2

'''Forum:''' -

'''Note:''' (Adamant14) Short unbalanced campaign, maybe abandoned. You fight with Peasants, Ruffians and Woodsman against Orcs

=== Alfhelm the Wise ===

''This is the tale of Alfhelm, called by some the Wise, son of Alfric Conqueror. This is the tale of his victories over his enemies, and his rise to power in the clans of Marauderdom. This is the tale of his journey south and his destruction of the Lavinian Empire. And this is the tale of his demise in the dark forests far to the east of his homeland.''

'''Author:''' turin

'''Maintainer:''' UnwiseOwl

'''Status:''' Complete

'''Length:''' 15 gameplay scenarios

'''Difficulty:''' Moderate

'''Style:''' Skirmish

'''Faction/Era:''' Imperial Era, Marauders.

'''Version:''' 0.6.0

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=17144

[Maintainers Note: Though this campaign is complete and playable the whole way through, the code is four years old and pretty buggy. If you notice any errors while playing, please let me know and I'll incorporate the fixes into my next revision as soon as possible.]

=== Antar, Son of Rheor ===

''This is the story about a young Lord and his first mission; sent by his father the young Lord Antar has to relieve his neighbours; he has to convince the Elves and Dwarves to ally him; he has to fight against hordes of Orcs and Endless Undead; and finally he has to defeat Mal Kazur, the mastermind who is behind all the evil.''

'''Author:''' Adamant14

'''Status:''' WIP

'''Length:''' 9 playable scenarios / 1 cutscene

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Loyalists and Elves (feat. fencer as main hero + various allies)

'''Version:''' 0.9.7

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36075

=== A Story of the Northlands ===

''A story of life and death in a remote village of the Northlands. Your village has been overrun by an orcish raid. You fight for its freedom while you wait for help to arrive.''

'''Author:''' zepko

'''Status:''' Complete

'''Length:''' 10 playable scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default + additions: you play with a custom faction of outlaws and with a custom party of loyalist knights.

'''[http://units.wesnoth.org/1.10/A_Story_of_the_Northlands/en_US/A_Story_of_the_Northlands.html Custom Units]'''

'''Version:''' 0.2.0

=== A Vision Blinded ===

''Defend the northern forest against what appeared like a routine orcish raid, and unravel the greater conspiracies that lie below its waves.''

'''Author:''' LemonTea

'''Maintainer:''' AxalaraFlame

'''Status:''' Complete

'''Length:''' 13 playable scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Elves (+ Trolls, Outlaws)

'''[http://units.wesnoth.org/1.10/A_Vision_Blinded/en_US/A_Vision_Blinded.html Custom units]'''

'''Version:''' 0.6.6

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=23463&hilit=a+vision+blinded

=== Besieged Druids ===

''A elvish school for druids comes under attack by goblins. It seems more than just a routine raid; is there something more sinister behind this attack? - In Beseiged Druids, you control Eärendil, the surviving teacher at the school, and the many and varied initiates. Not all of these are ordinary students; many have been experimenting with other forms of magic, while others are simply overachievers in some area of study. Unfortunately, they are not especially good at combat, at least initially. Together with a very small contingent of surviving guards, it is up to these students to save the island of Aleron from disaster.''

'''Author:''' Celtic Minstrel

'''Status:''' Complete

'''Length:''' 9 scenarios

'''Difficulty:''' Unbalanced

'''Style:''' Skirmish

'''Faction/Era:''' Default, Elves

'''[http://units.wesnoth.org/1.10/DruidSiege/en_US/celmin-druid-siege.html Custom units]'''

'''Version:''' 1

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=37342

=== Cities of the Frontier ===

''Settle a new town in the wilds north of the Great River.''

''This campaign makes several changes to the standard Wesnoth game mechanics, and focuses on city-building and gold management.''

'''Author:''' esci

'''Status:''' Complete

'''Length:''' Not fixed, approximately 6-10 seasons of 36 turns each

'''Difficulty:''' Normal

'''Style:''' Simulation, Survival

'''Faction/Era:''' Default, Loyalist

'''[http://units.wesnoth.org/1.10/Cities_of_the_Frontier/en_US/Cities_of_the_Frontier.html Custom units]'''

'''Version:''' 0.5.1

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36004

=== Considerate Dead ===

''As the wind goes on and on, people discover necromancer aren't always bad. Made by tribes45 - No scenarios are done, 4 playable out of ??.''

'''Author:''' tribes45 aka tribes55

'''Status:''' Incomplete, unbalanced, abandoned

'''Length:''' 5 scenarios

'''Difficulty:''' Unbalanced

'''Style:''' Skirmish

'''Faction/Era:''' Default

'''Version:''' .009

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36522

=== Count Kromire ===

''You are the blood son of a vampire lord, however when the might of the celestial crusades comes knocking, and your father is slain, you flee your lands. However you intend to return, to restore the lands of Kromire to the Kromires, to avenge your father, and most importantly, to make sure that no celestial ever dares come into your mountains again.''

'''Author:''' Velensk

'''Maintainer:''' currently none

'''Status:''' Complete

'''Length:''' 9 scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Era of Myths, Vampires

'''Version:''' 1.3.2

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=21560

=== The Dark Hordes ===

'''Status:''' Incomplete/WIP

'''Length:''' 11/?

'''Author:''' Circon

'''Maintainer:''' Various

'''Description:''' Lead fugitive dark sorcerer Gwiti Ha’atel to mastery of the undead hordes.

'''Version: '''

'''Requirements:'''

'''Difficulty:'''

'''Style:''' Skirmish

'''Faction/Era:''' Default undead

'''[http://units.wesnoth.org/1.10/The_Dark_Hordes/en_US/The_Dark_Hordes_1.html Custom Units]'''

'''Walkthrough:''' [[TheDarkHordes]]

'''Forum:''' [[http://forums.wesnoth.org/viewtopic.php?f=8&t=16576&]]

=== The Earth's Gut ===

''The year is 515YW. You are the young dwarven leader Hamel. Your tribe in the caves of Knalga is under pressure from its enemies, and resources are growing scarce. In order to forge the weapons required to resist your enemies, you must set forth and collect what ores and minerals remain.''

'''Author:''' Anonymissimus

'''Maintainer:''' Anonymissimus

'''Status:''' Incomplete

'''Length:''' 21 scenarios

'''Difficulty:''' Normal

'''Style:''' Dungeon

'''Faction/Era:''' Default, dwarves.

'''[http://units.wesnoth.org/1.10/The_Earths_Gut/en_US/the_earths_gut.html Custom units]'''

'''Version:''' 0.2.11

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=26800

'''Note:''' This campaign is a "Dwarvish dungeon crawler" and is intended to be challenging for experienced players on hard whilst suitably easy on easy.

=== Elvish Dynasty RPG ===

''You are the new ruler of an elvish kingdom! Can you lead your people to glory? This campaign is highly randomized so it will be different every time you play!''

''Sequel to Ooze Mini-Campaign''

'''Author:''' spencelack

'''Maintainer:''' Wesbane

'''Status:''' Complete

'''Length:''' 10 years, in each year choice between dialogue and fighting scenario (selected out of a large pool of possible scenarios)

'''Difficulty:''' Normal

'''Style:''' RPG, Skirmish

'''Faction/Era:''' Default, Elves

'''Version:''' 0.9.9b

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=28627

=== The Epic of Vaniyera ===

''The expansionist Lavinian Legion, led by the Imperator himself, has invaded the northern forests of the Sidhe, or Wild Elves. It is up to Leithan the Thunderblade and his advisor Vaniyera to push its armies back where they came from...''

'''Author:''' oreb, turin

'''Maintainer:''' UnwiseOwl

'''Status:''' Complete

'''Length:''' 6 scenarios

'''Difficulty:''' Hard (Don't be fooled by "novice level" in the campaign description, this one is very hard.)

[Maintainers note: Working on this issue, the next release (due at the end of November, hah!) should bring easy difficulty back to the level of a reasonable introduction to the IE, while the hard difficulty will also become slightly easier. With any luck, this will be the last release before version 1.0 of the campaign].

'''Style:''' Skirmish

'''Faction/Era:''' Imperial Era, Sidhe.

'''Version:''' 0.9.0

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=19490

=== Fall of Silvium ===

''You are Caius Regilius, Tribune of the province of Silvia, located in the northmost reaches of the Lavinian Empire at the height of its power. But the Empire has overextended itself, The city of Silvium lies seperated from the rest of the Empire by the mountains of Arendia, and is sandwiched between the Marauders and the Sidhe... war is inevitable, and the province of Silvia will almost certainly fall.''

'''Author:''' turin

'''Maintainer:''' UnwiseOwl

'''Status:''' Complete

'''Length:''' 8 scenarios

'''Difficulty:''' Medium

'''Style:''' Skirmish

'''Faction/Era:''' Imperial Era, Lavinian Legion.

'''Version:''' 0.6

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=31&t=24356

[Note: The final level of this campaign is not supposed to be winnable. It's a final blaze of glory and chance to use all your high-powered units, but to 'win' the campaign, you must lose...the ending is similar to a certain mainline campaign, but predates it.]

=== The Fall of Wesnoth ===

''As the beloved human empire of Wesnoth becomes lazy and arrogant in its peaceful state of happiness, Emperor Dantair demands the creation of another sun in a bid to destroy all evil. Or is it all for a different purpose? A man named Alitar sees it that way, and now he must survive the most evil inhabited lands if he is to stop chaos from rising, and Wesnoth from falling... This is the story of The Fall of Wesnoth.''

'''Author:''' Pewskeepski

'''Status:''' 1st part complete, 2nd WIP.

'''Length:''' 10 playable scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Outlaws

'''[http://units.wesnoth.org/1.10/The_Fall_of_Wesnoth/en_US/The_Fall_of_Wesnoth-1.html Custom units]'''

'''Version:''' 1.0.8

=== Fate of a Princess ===

''Part I: Baldres, a notorious robber baron, flees Wesnoth with his followers and sets off into the northlands to evade the king's justice. The baron's deeds and misdeeds are to change the balance of power between orcs and non-orcs throughout the northlands, and will carry consequences long after his eventual death.''

''Part II: The Greenwood elves face a crisis which demands the return of the queen's estranged half-elven half-sister, Baldres' daughter. Two brave young elves must make a perilous journey to find her and bring her back to her former home. If they fail, the whole northlands will be engulfed in war with the resurgent orcs...''

'''Author:''' SkyOne, mich, simonsmith

'''Status:''' Finished

'''Length:''' 26-29 scenarios (some dialogue-only), 2 parts

'''Difficulty:''' Normal

'''Style:''' Skirmish, Dungeon

'''Faction/Era:''' Default with additions. You play two different, unique cross-faction combinations in each part.

'''[http://units.wesnoth.org/1.10/Fate_of_a_Princess/en_US/Fate_of_a_Princess.html Custom units]'''

'''Version:''' 0.9.17

'''Required Wesnoth version:''' 1.9.12 or later

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=26327

=== Forgotten Kingdom ===

''Help Orlog, a troll chieftan, lead his people to safety in the underground and discover an ancient power long forgotten.''

'''Author:''' Limabean

'''Maintainer:''' Chrysophylax

'''Status:''' Incomplete ( but all scenarios playable and balanced )

'''Length:''' 9 playable scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Goblins, Trolls

'''[http://units.wesnoth.org/1.10/Forgotten_Kingdom/en_US/Forgotten_Kingdom.html Custom units]'''

'''Version:''' 0.1.7

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=23483

'''Note:''' (Adamant14) This campaign includes a custom Troll line. A good campaign, I hope Limabean and/or Chrysophylax will finish it.

=== Forward they Cried ===

''You are the leader of an advanced detachment that has been tasked with capturing a bridgehead while the main army prepares to attack. It should be a simple enough assignment.''

'''Author:''' Glowing Fish

'''Maintainer:''' Lord-Knightmare

'''Status:''' Finished

'''Length:''' 1 scenario ( rather a single scenario than a campaign )

'''Difficulty:''' Hard

'''Style:''' Skirmish

'''Faction/Era:''' Default Loyalists

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=23656&p=350126&hilit=forward+they+cried#p350126

'''Version:''' 1.0.0

'''Note:''' (Adamant14) Only a single scenario, but a great scenario.
(UnwiseOwl) You wouldn't want to stop thinking for a turn, and it's good for the first few turns, but this one leaves me wanting more.

=== The Founding of Borstep ===

''The chieftain of your tribe has become decadent and weak. Take over, and lead your people to a better home--whether it is already occupied or not. The Northlands in year 9W are a barbaric place, but anyone who stands in your way will learn the power of orcs!''

'''Author:''' Beetlenaut

'''Status:''' Complete

'''Length:''' 10 and 1 dialogue only

'''Difficulty:''' Hard

'''Style:''' Skirmish

'''Faction/Era:''' Default, Northerners

'''[http://units.wesnoth.org/1.10/The_Founding_of_Borstep/en_US/The_Founding_of_Borstep.html Custom units]'''

'''Version:''' 1.1.1b

''Note(Kanzil): I find the protagonist hard to sympathise with. Also, most scenarios contain interesting twists. For example, in one, each time you killed a boar it gives you extra health.''

''Note(beetlenaut--author): In most Orcish campaigns the leader is heroic or just wants peace. Krag-Ubor wants plunder and battle like all enemy Orcs in other campaigns. I '''hope''' you don't sympathize too strongly, but I don't think you need to in order to enjoy the game play.''

=== Galuldur's First Journey ===

''While the belligerence of orcs is nothing new, their intensifying attacks on a fledgling colony of elves in Pindir Forest begin to show signs of a deeper malice, forcing Galuldur, the young son of the colony's adventurous founder Galur, to venture out of his forest's friendly trees in search of help. His simple errand quickly turns into a frantic quest to unearth the roots of the mysterious evil threatening his people. As you lead him through unknown lands, Galuldur, forced to match wits with unexpected adversaries at nearly every turn in a desperate attempt to save his world, quickly learns that the world is neither a friendly nor a simple place.''

'''Author:''' mattsc

'''Status:''' Complete

'''Length:''' 8-9 scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Elves

'''[http://units.wesnoth.org/1.10/Galuldur/en_US/Galuldur.html Custom units]'''

'''Version:''' 1.1.1

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=31895

=== Grnk the Mighty ===

''All his life, puny little goblin Grnk the Frail had been dreaming about leaving the orcs and starting a better life. When he finally arrives in the human town of Shmaltupp, he realizes that the world is not as black and white as he had imagined. He also discovers that he is no ordinary goblin. Follow Grnk the Frail on his path to becoming Grnk the Mighty.''

'''Author:''' mattsc

'''Status:''' Part I complete

'''Length:''' 13 scenarios

'''Difficulty:''' Hard

'''Style:''' Skirmish, RPG

'''Faction/Era:''' Default, changing (no standard army building gameplay)

'''[http://units.wesnoth.org/1.10/Grnk/en_US/Grnk.html Custom units]'''

'''Version:''' 1.0.5

'''Required Wesnoth version:''' 1.9.5 or later

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=34970

=== Invasion from the Unknown ===

''Episode I - Seeking the Light: Long after the Fall, the last forest elves are forced to abandon their safe valley, and find themselves resorting to the dark means of necromancy in order to survive the perils and challenges of this new harsh world. May they finally free the Great Continent from its chaos, or perish in the foolish attempt of restoring peace and life to the lands.''

''Episode II - Armageddon: As the shadow of Chaos covers the entire continent, an assorted group of foolish heroes prepares a counter-attack to the Empire, with one unique goal in their minds: defeat the evil Emperor, whoever it is. Lead these courageous living and non-living warriors to victory, and rediscover lost secrets of the history.''

'''Author:''' shadowmaster

'''Maintainer:''' Espreon

'''Status:''' Finished

'''Length:''' 26 scenarios in two episodes

'''Difficulty:''' Normal

'''Style:''' Skirmish, Dungeon, Boss battle

'''Faction/Era:''' Unique. You play Elves and Undead throughout the campaign + in the 2nd part Northerners and Aragwaithi.

'''Version:''' 1.90.6

''Note (taptap): Despite its acknowledged flaws (generic hero, plot holes, deus ex machina moments, gameplay issues in the 2nd part) this is undoubtedly the most iconic campaign in UMC. It single-handedly redefines the elvish history and sketches a cosmology for the ages after the fall. With the Chaos empire and its various allies it introduces an era worth of factions to single-player play. At the same time it features some of the most beautiful maps in Wesnoth and stunning art on par with mainline campaigns.''

=== Invasion of Eliador ===
''A peaceful island is about to be invaded by unknadd-ons foes travelling towards the eastern shore. It is up to a family of outlaws to warn the island's inhabitants before it's too late.''

'''Author:''' Sam M. (Genosuke)

'''Maintainer:''' trewe

'''Version:''' 1.0.4

'''Style:''' RPG, Skirmish, Puzzle

'''Length:''' 10 scenarios + epilogue

'''Difficulty:''' Easy

'''Status:''' Complete

'''Faction:''' Default (outlaws)

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=6556

'''Wiki:''' [[Invasion_of_Eliador]]

=== Langrisser Sample Campaign ===

''The Imperial Knights of the Rayguard Empire have disrupted the peace of the village that was Hein's hometown, seeking only a girl named Liana. Fight to rescue Liana.''

'''Author:''' Morath

'''Status:''' Finished

'''Length:''' 1 playable scenario

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Elves

'''Version:''' 0.1.0.5

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36417&hilit=Langrisser

'''Wikipedia:''' [http://en.wikipedia.org/wiki/Langrisser What is Langrisser]

'''Note:''' (Adamant14) Single scenario, different from usual Wesnoth behaviour.

=== Legend of the Invincibles ===

'''''Part I: Shrouded in Darkness''' (5 chapters, 90 scenarios) - A pair of heroes, after stopping an orcish thread, are outcast into caves, where they have no other choice than to become liches in order to survive. They preserved their human appearance and moral principles, and fight in various skirmishes against evil (although using evil methods sometimes), until the Fall, when they are buried alive under the ashes of the third sun.''

'''''Part II: Into the Light''' (3 chapters, 46 scenarios at the moment) - Long after the Fall, the lich heroes awaken. Searching for more power, they manage to resurrect themselves as living beings, but this time more powerful and cleaned from the evil within them. But the evil from inside them continued to exist, and started a skirmish to conquest the world. Stopping the skirmish caused an even worse disaster...''

'''Author:''' Dugi

'''Status:''' WiP (but Part I might be considered complete)

'''Length:''' 135 (+6 talk-only) scenarios at the moment

'''Difficulty:''' Normal

'''Style:''' mostly Skirmish and Dungeon (all other styles are present as well, but less frequently)

'''Faction/Era:''' Elves, Loyalists, Undead, Dwarves; but they advance past their usual maximum level

'''Version:''' 2.4.0

''Note: The most unique feature of this campaign is its RPG-like unit development system, enemies drop items units can use, leaders are stronger than most usual units and all units get AMLA (after maximum level advancement) after reaching their maximum level (that is also increased by a load of additional level 4 units).''

=== The Library of Kratemaqht ===

''An ancient story from the old continent.''

'''Author:''' Rich Marinaccio (cephalo)

'''Status:''' Complete

'''Length:''' 17 scenarios

'''Difficulty:''' Unbalanced (some scenarios are Easy - some rather Hard)

'''Style:''' Skirmish, RPG

'''Faction/Era:''' Loyalists and custom units.

'''[http://units.wesnoth.org/1.10/Library_Of_Kratemaqht/en_US/The_Library_Of_Kratemaqht.html Custom units]'''

'''Version:''' 1.0.0

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=37798

'''Notes:''' (Adamant14) This campaign has a thought-out story, shows a great love for detail;
It includes a great custom Dragon, some brilliant custom images (fire, burning houses, burning forest) that makes the scenery / maps look very nice.

=== Panther Lord ===

''The Imperialists ambitions of pushing into the Sea States have been repeatedly thwarted and now they turn their attentions elsewhere. You are an outcast Darklander now living as a mercenary in the Sea States and the rumors you hear indicate that they will be coming to your people. Though an outcast you do not wish to see them subjugated. The spirit whose friendship caused you to be an outcast has a plan that might allow you to save them.''

'''Author:''' Velensk

'''Maintainer:''' Lavender

'''Status:''' Finished

'''Length:''' 14 scenarios

'''Difficulty:''' Hard

'''Style:''' Skirmish

'''Faction/Era:''' Era of Four Moons, Darklanders (+ a wide variety of mercenaries)

'''Version:''' 1.0.2

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=34318

=== Return of the Monster ===

''It was time for Amailoss, born from the naga queen's last egg, to leave home. Time for him to grow into a leader in his own right, and eventually become the guardian and leader of another naga city. But along the way, he became friends with an unusual mud-crawler, they met a strange young monster, discovered that a spirit had escaped from an orc prison, and the mystery of that spirit became a grave challenge for Amailoss and the many races in the region....''

''A naga campaign, involving elves, orcs, saurians, turtle-like races, and some monsters.''

'''Author:''' SkyOne

'''Status:''' Complete

'''Length:''' 16 playable, 2 dialog scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish, Dungeon

'''Faction/Era:''' Default with additions. You play a custom naga faction and carapaces (a turtle-like race).

'''[http://units.wesnoth.org/1.10/Return_of_the_Monster/en_US/Return_of_the_Monster.html Custom units]'''

'''Version:''' 0.7.1

'''Required Wesnoth version:''' 1.10.x

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36438

=== Return to Noelren ===

'''Status:''' Complete.

'''Length:''' 26 scenarios + 7 cut scenes

'''Author:''' Pyrophorus

'''Description:''' ''A story in the first Dark Age of Wesnoth. See how various heroes stick together to shun the threat of black magics, restore the secret kingdom of Noelren and install Garard I on the throne of Wesnoth. This campaign features complex scenarios, unusual objectives and units, emphasizing more on story and adventures than hardcore fighting.''

'''Version: ''' 0.7

'''Requirements:''' BfW 1.10 (not tested on 1.11)

'''Difficulty:''' Easy, unbalanced

'''Style:''' Skirmish, RPG, Large Battle, Simulation

'''Faction/Era:''' Default + custom units

'''[http://units.wesnoth.org/1.10/ReturnToNoelren/en_US/ReturnToNoelren.html Custom Units]'''

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=34685#p501026

=== Return to Ruins ===

''The humble farmers of Vertegris are summoned by Erik the General of Weldyn to put an end to an orcish raiding party. If they knew what would befall their former home... They never would have left. This is a relatively short campaign with 8 scenarios, It is still undergoing changes.''

'''Author:''' Ulfsark (Jeff Stevens)

'''Status:''' Complete

'''Length:''' 7 scenarios + 1 dialogue-only

'''Difficulty:''' Easy,Normal,Hard

'''Style:''' Skirmish

'''Faction/Era:''' Default,(Loyalists, Outlaws)

'''Version:''' 0.5.0

'''Required Wesnoth version:''' 1.10.x

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=37790&sid=9059f18497cda1219f42a626544d0ffd&p=540646#p540646

'''Note:''' (Adamant14) You play a short campaign with just a few units. Playable in a few hours, nevertheless it is fun to play.

=== Saving Elensefar ===
''Meneldur, elvish mariner of Elensefar, is driven to sea by the same orcs who attacked the city. He must gather an army willing to fight for him to regain Elensefar, his adopted homeland.''

'''Author:''' Turin

'''Maintainer:''' trewe

'''Status:''' Finished

'''Length:''' 1 year (around 12 scenarios)

'''Difficulty:''' Normal

'''Style:''' Skirmish, RPG, Simulation

'''Version:''' 1.5.2

'''Faction:''' Default Era

'''Forum:''' http://wesnoth.org/forum/viewtopic.php?t=3072&start=0

'''Wiki:''' [[SeafaringCampaign]]

<small>Labeled as Expert, recruit list changes in all scenarios</small>

=== The Roar of the Woses ===

''When the construction of a dam threatens the existence of her home, Kylix is forced on a journey to stop it.''

'''Author:''' Alarantalara

'''Status:''' Finished

'''Length:''' 10-11 scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default with Additions (primarily Saurians, Nagas, Woses)

'''Version:''' 1.2.7

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=29830

'''Note:''' (author) Potentially unbalanced on Hard difficulty due to experiments with non-standard ways to increase difficulty. This issue does not exist on the lower difficulty levels.

=== The Three Elves ===
''Three elves have just begun their adventure in the northern swampland. Will they become heroes or will they be responsible for another undead expansion?''

'''Author:''' Stanislav Hoferek

'''Maintainer:''' trewe

'''Version:''' 0.9

'''Status:''' Complete

'''Difficulty:''' Easy

'''Length:''' 6 scenarios + 2 dialogue

'''Style:''' Skirmish

'''Faction:''' Default (Elves)

'''Forum:''' (does it have one?)

=== Salt Wars ===

''Introductory campaign for the Era of Four Moons.''

''As an officer of one of the Sea States you must defend your organization from aggressive rivals.''

'''Author:''' Velensk

'''Maintainer:''' Lavender

'''Status:''' Complete

'''Length:''' 5 scenarios

'''Difficulty:''' Easy

'''Style:''' Skirmish

'''Faction/Era:''' Era of Four Moons, Sea States

'''Version:''' 0.2.1

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=31498

=== The Sojournings of Grog ===

''Grog (as starred in Under the Burning Suns) goes home.''

'''Author:''' Peter Christopher, Thomas Hockings

'''Maintainer:''' Elvish_Hunter

'''Status:''' Finished

'''Length:''' 18 playable scenarios in 2 parts

'''Difficulty:''' Normal

'''Style:''' Skirmish, Dungeon, Large Battle

'''[http://units.wesnoth.org/1.10/The_Sojournings_of_Grog/en_US/The_Sojournings_of_Grog.html Custom units]'''

'''Faction/Era:''' Default. Most of the time you play trolls and some desert elves accompanying Grog.

'''Version:''' 3.0.1

=== Unlikely Alliance ===

''Play as the members of an alliance between the elves, drakes, and undead after the Fall of Wesnoth.''

'''Author:''' Creativity

'''Status:''' Broken ( Abandoned )

'''Length:''' 2 broken scenarios

'''Difficulty:''' Unbalanced

'''Style:''' -

'''Faction/Era:''' -

'''Version:''' 0.1

'''Forum:''' -

'''Note:''' (Adamant14) Did not work at all. Seems abandoned.

=== Up from Slavery ===

''The Orcei are captives in the imperial city of Lavinium, gladiators performing for the emperor Optus Maximus. All it will take, however, is one orc to lead his people to freedom. The Samnis called Sparxus may be that orc.''

'''Author:''' turin

'''Maintainer:''' UnwiseOwl

'''Status:''' Complete

'''Length:''' 7 scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish, Arena (= No recruit, small group gladiator fights)

'''Faction/Era:''' Imperial Era, Orcei Gladiatores

'''Version:''' 0.6.0

[Maintainer's Note: At some point, I am intending to completely re-work this campaign to be a multi-player campaign, with one side led by Sparxus and one by Gravirivus. If anyone would like to take this on or has ideas for how to accomplish this, let us know. Nevertheless, its playable as a single player campaign now with some nice ideas that could be developed further.]

=== Warmaster ===
''One day the scout of your king brings a mysterious little stone, called Zrai-Stone, back from one of his trips. Soon that stone causes a lot of trouble...''

'''Author:''' Conkinator

'''Maintainer:''' trewe

'''Version:''' 1.3.5

'''Status:''' Finished

'''Length:''' 16 battle + 2 bonus + 1 epilogue scenarios

'''Difficulty:''' Hard

'''Faction:''' Default (loyalists)

'''Style:''' Skirmish, Survival

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=15527

=== Way of Dragon ===

''The story of what might happen if a person against his will transform into a dragon...''

'''Author:''' DrakeDragon

'''Status:''' Complete

'''Length:''' 7 playable scenarios + 1 dialogue-only

'''Difficulty:''' Normal

'''Style:''' Skirmish/RPG

'''Faction/Era:''' Default Loyalists

'''Version:''' 1.2.0

'''Forum:''' [http://forums.wesnoth.org/viewtopic.php?f=8&t=37876 Wesnoth Forum] [http://uporoom.ru/index.php/topic,179.0.html Russian Forum]

'''Note:''' (Adamant14) Promising short campaign, you play with just a few units.

== Battle for Wesnoth 1.11.x - development ==

''Campaigns available in the 1.11.x development version.''

''Please note: Battle for Wesnoth 1.11.0 features a bug that messes up the selection of difficulty levels.''

=== Antar, Son of Rheor ===

''This is the story about a young Lord and his first mission; sent by his father the young Lord Antar has to relieve his neighbours; he has to convince the Elves and Dwarves to ally him; he has to fight against hordes of Orcs and Endless Undead; and finally he has to defeat Mal Kazur, the mastermind who is behind all the evil.''

'''Author:''' Adamant14

'''Status:''' WIP

'''Length:''' 9 playable scenarios / 1 cutscene

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default, Loyalists and Elves (feat. fencer as main hero + various allies)

'''Version:''' 0.9.7

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=36075

'''Note:''' (Adamant14) The campaign currently did not work with BfW 1.11.0, so please use BfW version 1.11.1!

=== Legend of the Invincibles ===

'''''Part I: Shrouded in Darkness''' (5 chapters, 90 scenarios) - A pair of heroes, after stopping an orcish thread, are outcast into caves, where they have no other choice than to become liches in order to survive. They preserved their human appearance and moral principles, and fight in various skirmishes against evil (although using evil methods sometimes), until the Fall, when they are buried alive under the ashes of the third sun.''

'''''Part II: Into the Light''' (3 chapters, 46 scenarios at the moment) - Long after the Fall, the lich heroes awaken. Searching for more power, they manage to resurrect themselves as living beings, but this time more powerful and cleaned from the evil within them. But the evil from inside them continued to exist, and started a skirmish to conquest the world. Stopping the skirmish caused an even worse disaster...''

'''Author:''' Dugi

'''Status:''' WiP (but Part I might be considered complete)

'''Length:''' 135 (+6 talk-only) scenarios at the moment

'''Difficulty:''' Normal

'''Style:''' mostly Skirmish and Dungeon (all other styles are present as well, but less frequently)

'''Faction/Era:''' Elves, Loyalists, Undead, Dwarves; but they advance past their usual maximum level

'''Version:''' 2.4.0

''Note: The most unique feature of this campaign is its RPG-like unit development system, enemies drop items units can use, leaders are stronger than most usual units and all units get AMLA (after maximum level advancement) after reaching their maximum level (that is also increased by a load of additional level 4 units).''

=== Ruthless ===

''A bard (an aging criminal) is walking in wasteland. Nothing but two hands in his pockets, and nothing but stones around. Suddenly he sees a knight on errand--a dangerous opponent, especially in broad daylight. The two strangers are soon sitting by the campfire, and the bard is telling a story.
(Beginner level, 10+ fights).''

'''Author:''' homunculus

'''Status:''' Finished

'''Length:''' 12 playable scenarios + 5 cutscene scenarios

'''Difficulty:''' Normal

'''Style:''' Skirmish

'''Faction/Era:''' Default (Orcs)

'''Version:''' 1.0.4

'''Forum:''' http://forums.wesnoth.org/viewtopic.php?f=8&t=37874

'''Note:''' (Adamant14) Recommendable campaign, with smart unusual ideas and a good detailed story.
You fight with few units on small but perfect maps. About the difficulty: The author describes his campaign as 'beginner level', but for me the difficulty is rather NORMAL than EASY.

[[Category:Campaigns|*]]

PortugueseContinentalTranslation

2013-01-13T12:22:08Z

Trewe: update repository name

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

*trewe [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

*Sérgio Lopes (maintainer) [mailto:knitter.is@gmail.com]
*Carlos Sousa
*Luís Passos

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

Os ficheiros actuais da tradução podem ser obtidos no repositório da [https://github.com/trewe/wesn-pt-trans github].

Após terem sido obtidos os ficheiros será necessário usar um programa de edição de ficheiros *.po, [http://www.poedit.net PoEdit] ou [http://translate.sourceforge.net/wiki/virtaal/index Virtaal] são bons exemplos de programas open-source e multiplataforma que poderão usar.

Quando iniciarem a tradução dum ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o(s) ficheiro(s) traduzido(s) para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para
manter o espírito do jogo.

O inglês usa capitalização extensiva neste jogo porém em português só palavras em destaque deverão estar.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Que norma ortográfica?===

A livre escolha de cada tradutor. Apesar de ser verdade que agora existe um «acordo ortográfico» (em vigor no Brasil deste 2004 e em Portugal 2009); é utópico pensar que a língua utilizada nos países lusófonos mude de alguma forma. Haverá sempre diferenças nos diferentes dialectos até porque <b>não</b> existe uma coisa como «português padrão».

Para se ter uma ideia, o acordo muda cerca de 4% do vocabulário do português europeu e pouco menos de 3% do brasileiro.

===O uso do «você»===

Nunca. O utilizador é referido na segunda pessoa do singular. (Sempre no presente do indicativo e com o pronome omitido)

E nos diálogos a preferência vai para a 2ª pessoa (singular como plural).

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar/Submeter
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar/processar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| tritão/ondim
|-
| mermaid
| sereia/ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

Página do projecto: <a definir>

Página de detalhes no sourceforge: http://sourceforge.net/projects/wesn-pt-trans

Endereço do repositório: https://wesn-pt-trans.svn.sourceforge.net/svnroot/wesn-pt-trans

Mailing Lists:
* wesn-pt-trans-commits <at.here> lists.sourceforge.net - registo de commits, lista para onde são enviados automaticamente as mensagens de commit.
* wesn-pt-trans-users <at.here> lists.sourceforge.net - lista geral, pode ser usada para qualquer tipo de contacto, pergunta ou comentário.

[[Category:Translations]]

PortugueseContinentalTranslation

2013-01-13T12:11:10Z

Trewe: /* Contactos */

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

*trewe [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

*Sérgio Lopes (maintainer) [mailto:knitter.is@gmail.com]
*Carlos Sousa
*Luís Passos

=== Contactos ===
Para contactar a equipa de tradução basta enviarem um e-mail para o endereço acima ou por via IRC no servidor da freenode, canal #wesnoth (generalista) ou #wesnoth-pt.
Alternativamente pode-se utilizar a mailinglist do [http://sourceforge.net/projects/wesn-pt-trans/ sourceforge] (lento).

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução do Wesnoth é feita recorrendo aos serviços que o [http://sourceforge.net Sourceforge] oferece.
Desses serviços o projecto usa [https://sourceforge.net/mail/?group_id=209264 Mailing Lists], [https://sourceforge.net/svn/?group_id=209264 Repositório de Subversion] e sistema de [https://sourceforge.net/tracker/?group_id=209264 Bug Reports].
É assim necessário ter acesso a um cliente [http://subversion.tigris.org Subversion], aceder ao repositório do projecto de tradução e obter os ficheiros a traduzir.

Após terem sido obtidos os ficheiros será necessário usar um programa de edição de ficheiros *.po, http://www.poedit.net é um bom exemplo de um programa open source e multiplataforma que poderão usar.

Quando iniciarem a tradução de um ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o(s) ficheiro(s) traduzido(s) para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para
manter o espírito do jogo.

O inglês usa capitalização extensiva neste jogo porém em português só palavras em destaque deverão estar.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Que norma ortográfica?===

A livre escolha de cada tradutor. Apesar de ser verdade que agora existe um «acordo ortográfico» (em vigor no Brasil deste 2004 e em Portugal 2009); é utópico pensar que a língua utilizada nos países lusófonos mude de alguma forma. Haverá sempre diferenças nos diferentes dialectos até porque <b>não</b> existe uma coisa como «português padrão».

Para se ter uma ideia, o acordo muda cerca de 4% do vocabulário do português europeu e pouco menos de 3% do brasileiro.

===O uso do «você»===

Nunca. O utilizador é referido na segunda pessoa do singular. (Sempre no presente do indicativo e com o pronome omitido)

E nos diálogos a preferência vai para a 2ª pessoa (singular como plural).

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar/Submeter
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar/processar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| tritão/ondim
|-
| mermaid
| sereia/ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

Página do projecto: <a definir>

Página de detalhes no sourceforge: http://sourceforge.net/projects/wesn-pt-trans

Endereço do repositório: https://wesn-pt-trans.svn.sourceforge.net/svnroot/wesn-pt-trans

Mailing Lists:
* wesn-pt-trans-commits <at.here> lists.sourceforge.net - registo de commits, lista para onde são enviados automaticamente as mensagens de commit.
* wesn-pt-trans-users <at.here> lists.sourceforge.net - lista geral, pode ser usada para qualquer tipo de contacto, pergunta ou comentário.

[[Category:Translations]]

Invasion of Eliador

2013-01-09T21:55:13Z

Trewe:

Saving Elensefar

2013-01-09T20:09:44Z

Trewe:

== Saving Elensefar ==

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

:another campaign by turin

=== Description ===

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

=== Features ===

This campaign has a semilinear plot design hopping from one island to another. 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.

Your eventual objective is to go to an island in 5 months (30 turns) where Black the Red disclaims existing an army to get aid in saving Elensefar, until them you cannot return to Elensefar.

=== Length ===

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

It is expected that around a third of the islands will be visited and battled 2-5 enemy ships, depending of difficulty and route taken.

=== Tips ===

Keep your recall list small, no leader needs more than a dozen of units, since all require upkeep (even when idling on the recall list). Always have an eye on the gold resources looting any single coin you can and spending wisely those you have, if you run out of gold the campaign is lost.

Check the available recruits with every leader, in this campaign they change their recruits more often than their underwear.

=== Version ===

Current version as is 1.5.2 (released 9-12-12) downloadable from the official stable campaign server.

The campaign is scenario-complete. Plotwise, it was finished as of version 0.7.6 (3-10-05). In version 1.5.0 an experimental branch was introduced with new features like multiple leaders and innovative upkeep.

If anyone has balancing suggestions, typo fixes, or bug reports, post them in the ([http://wesnoth.org/forum/viewtopic.php?t=3072&start=0 forum thread] ) or send a PM or e-mail to the maintainer (trewe [mailto:sjrs456@yahoo.fr]).

== See Also ==

* [[UserCampaigns]]

[[Category:Campaigns]]

WesnothTranslations

2012-12-23T15:02:05Z

Trewe: /* 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]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: 楊綮銘 (Taiwan) - [mailto:steven2880ATgmailDOTcom]
* [[CroatianTranslation|Croatian]] - maintainer: Ivica Đurenec (charlieh65) - [mailto:ivicaDOTdurenecATgmailDOTcom]
* [[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]
* [[EnglishGBTranslation|English (GB)]] - maintainer: Steven Panek (Espreon) - [mailto:Majora700@gmail.com]
* [[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: Jarkko Patteri (Jarkko) - [mailto:jarkkopatteriATgmailDOTcom], Samu Voutilainen (Smar) - [mailto:samu.voutilainenATgmailDOTcom]
* [[FrenchTranslation|French]] - maintainer: Guillaume Pascal (Haldric) - Please use the 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: Antonio Rosella - [mailto:arosellaATyahooDOTcom]
* [[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:Majora700@gmaill.com]
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Diego Inácio Goergen - [mailto:thegoergenATgmailDOTcom]
* [[PortugueseContinentalTranslation|European Portuguese]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com] co-maintainer trewe [mailto:sjrs456@yahoo.fr]
* [[RomanianTranslation|Romanian]] - maintainer: Alexandru Szasz [mailto:alexxedATgmailDOTcom]
* [[RussianTranslation|Russian]] - maintainer: Victor Sergienko [mailto:singalenATgmailDOTcom]
* [[Scottish_Gaelic_Translation|Scottish Gaelic]] - maintainer: GunChleoc- [mailto:fiosAIGforamnagaidhligDOTnet]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[SlovakTranslation#Preklad|Slovak]] - maintainer: Aceman
* [[SlovenianTranslation|Slovenian]] - maintainer: Klemen Košir (nNa) - [mailto:klemen913ATgmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Steven Panek (Espreon) - [mailto:Majora700@gmail.com]); comaintainer: Víctor Martínez Estrada (Darkmage) - [mailto:quianaaelonin@gmail.com])
* [[SwedishTranslation|Swedish]] - maintainer: Niklas Bolmdahl (dacovale) - [mailto:wesnothATniklasDOTbolmdahlDOTcom]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[UkrainianTranslation|Ukrainian]] - maintainer: robson - [mailto:arobsonATyandexDOTru]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Huynh Yen Loc (hhyloc) - [mailto:nightgaunt13ATgmailDOTcom]

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

PortugueseContinentalTranslation

2012-12-23T14:58:44Z

Trewe: major overhaul of the portuguese page

=Bem-Vindo=

Bem-vindo à página de apresentação da tradução para português europeu do jogo "A Batalha por Wesnoth".

O esforço da tradução pretende oferecer aos utilizadores de "Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

Todos podem ajudar neste processo, seja oferecendo o seu tempo a trabalhar activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

===Equipa da tradução===

====Activos====

*trewe [mailto:sjrs@yahoo.fr]

====Estado desconhecido====

*Sérgio Lopes (maintainer) [mailto:knitter.is@gmail.com]
*Carlos Sousa
*Luís Passos

=== Contactos ===
A equipa de tradução pode ser contactada através do seu espaço no SourceForge, [http://sourceforge.net/projects/wesn-pt-trans/ wesn-pt-trans]. Nele podem encontrar a lista de discussão bem como um ponto de acesso aos ficheiros a traduzir.

== Regras para os Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução do Wesnoth é feita recorrendo aos serviços que o [http://sourceforge.net Sourceforge] oferece.
Desses serviços o projecto usa [https://sourceforge.net/mail/?group_id=209264 Mailing Lists], [https://sourceforge.net/svn/?group_id=209264 Repositório de Subversion] e sistema de [https://sourceforge.net/tracker/?group_id=209264 Bug Reports].
É assim necessário ter acesso a um cliente [http://subversion.tigris.org Subversion], aceder ao repositório do projecto de tradução e obter os ficheiros a traduzir.

Após terem sido obtidos os ficheiros será necessário usar um programa de edição de ficheiros *.po, http://www.poedit.net é um bom exemplo de um programa open source e multiplataforma que poderão usar.

Quando iniciarem a tradução de um ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o(s) ficheiro(s) traduzido(s) para o responsável pelo projecto, (trewe à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

==Estilos e vocabulário==

Como o jogo decorre num ambiente medieval será boa ideia utilizar um vocabulário e estilo pendente, especialmente na prosa para
manter o espírito do jogo.

O inglês usa capitalização extensiva neste jogo porém em português só palavras em destaque deverão estar.

Os objectivos dos cenários e comandos gerais são sempre dirigidos ao utilizador.

Nomes próprios normalmente mantêm-se, ou então são aportuguesados. A excepção vai para aqueles que têm significado (sub)entendido.

A tradução das unidades em todas as línguas pode ser encontrada na [http://units.wesnoth.org/trunk/mainline/pt_PT/mainline.html Lista das Unidades].

===Que norma ortográfica?===

A livre escolha de cada tradutor. Apesar de ser verdade que agora existe um «acordo ortográfico» (em vigor no Brasil deste 2004 e em Portugal 2009); é utópico pensar que a língua utilizada nos países lusófonos mude de alguma forma. Haverá sempre diferenças nos diferentes dialectos até porque <b>não</b> existe uma coisa como «português padrão».

Para se ter uma ideia, o acordo muda cerca de 4% do vocabulário do português europeu e pouco menos de 3% do brasileiro.

===O uso do «você»===

Nunca. O utilizador é referido na segunda pessoa do singular. (Sempre no presente do indicativo e com o pronome omitido)

E nos diálogos a preferência vai para a 2ª pessoa (singular como plural).

===Discurso directo===

Elfos - hipercorrectos e até algo «poético».

Orcs - Normal mas com forte tendência pro-drop e utilização dos tempos compostos.

Gnomos - Como os Orcs mas mais submissos.

Trogloditas e Ogres - Sempre no infinitivo e na terceira pessoa (excepções confirmam a regra), evitam a passiva.

Silvanos (Wose) - Forte adjectivação.

Dragos - Metafóricos e «understatements»

Répteis e Nagas - ênfase nos 'erres' e 'zês'.

Anões - dialecto transmontano :)

Humanos - Nada de especial (depende da posição social)

Morto-Vivos - Nada de especial (como em vida), talvez algo submissos; os magos são humanos.

Monstros - Normal ou dependendo do contexto.

===Calão do jogo===

Segue-se uma lista breve de termos frequentemente usados no jogo, para manter a consistência, não tem intenção ser completo nem canónico.

{|
|-
| Screen
| Ecrã
|-
| chance
| hipótese
|-
| OK
| Confirmar/Submeter
|-
| Undo
| Anular
|-
| multiplayer
| jogo em rede
|-
| download
| carregar
|-
| load
| retomar/processar
|-
| game
| partida
|-
| game (the engine)
| jogo (o programa)
|-
| user
| utilizador
|-
| password
| palavra-passe
|-
| host
| anfitrião
|-
| whiteboard
| modo de planificação
|-
| hex
| hexágono
|-
| add-on
| Extra/Suplemento
|-
| mod
| modificação
|-
| AMLA (After Max Level Advancement)
| AANM (Avanço Após Nível Máximo)
|-
| melee
| curto [alcance]
|-
| ranged
| longo [alcance]
|-
|lawful
| diurno
|-
| chaotic
| nocturno
|-
| neutral
| neutro
|-
| liminal
| liminar
|-
| blade
| cortante
|-
| pierce
| perfurante
|-
| impact
| impacto
|-
| fire
| fogo
|-
| cold
| gelado
|-
| arcane
| arcano
|-
| movement
| [pontos de] movimentos
|-
| defense
| defesa
|-
| hitpoints/HP
| pontos de vida/PV
|-
| experience points/XP
| pontos de experiência/XP
|-
| trait
| característica
|-
| dextrous
| hábil
|-
| dim
| asno
|-
| level
| nível
|-
| ability
| habilidade
|-
| skirmisher
| escaramuçador
|-
| ambush
| emboscada
|-
| heal
| sarar
|-
| weapon special
| efeito da arma
|-
| marksman
| precisão
|-
| feeding
| canibalismo
|-
| faction
| facção
|-
| Rebels
| Rebeldes
|-
| Loyalists
| Leais
|-
| Northerners
| Nortistas
|-
| Drakes
| Dragos
|-
| Undead
| Morto-Vivos
|-
| Knalgan Alliance
| Aliança de Gnalga
|-
| Gameplay
| Regras do Jogo
|-
| Campaign Design
| Projecto da campanha
|-
| Maintainer
| Manutenção da campanha
|-
| Artwork
|trabalho artístico
|-
| fighter
| soldado
|-
| warrior
| guerreiro
|-
| lord
| Lorde/Senhor/Mestre
|-
| Spearman
| Milícia/Hoste/Lançador (hoste e lançador são palavras medievais)
|-
| Horseman/Cavalry/Knight/Dragoon/Lancer
| Escuteiro/Cavalaria/Cavaleiro/Bridão/Ginete/Draconiano/Lanceiro
|-
| Shaman
| Bruxo(a) (¡nunca! como xamã)
|-
| merman
| tritão/ondim
|-
| mermaid
| sereia/ondina
|-
| Wose
| Silvano
|-
| Goblin
| Gnomo
|-
| Troll
| Troglodita
|-
| Naga
| Naga
|-
| Drake
| Drago
|-
| Saurian
| Réptil
|-
| elf
| elfo (substantivo)
|-
| elvish
| elfo (adjectivo)
|-
| Dark Elf
| Duende
|-
| Dark <...> (unit name)
| Obscuro/Trevas/Maligno (unidades)
|-
| orcish/dwarvish/drakish
| orc/anão/anã/drago (adjectivo)
|-
| Novice Level
| Nível Principiante
|-
| Intermediate Level
| Nível Intermediário
|-
| Expert Level
| Nível Veterano
|-
| Defeat all enemy leaders
| Derrota todos os líderes adversários
|-
| sir
| senhor
|-
| enemy
| adversário
|-
| healer
| curandeiro
|-
| village
| aldeia
|-
| gold
| peças de ouro
|}

==Estado da tradução==

=== Lista de Traduções ===

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[http://www.wesnoth.org/gettext/index.lang.php?lang=pt&version=trunk Estatísticas da tradução]

[[WesnothTranslations]]

== Links Diversos ==

Página do projecto: <a definir>

Página de detalhes no sourceforge: http://sourceforge.net/projects/wesn-pt-trans

Endereço do repositório: https://wesn-pt-trans.svn.sourceforge.net/svnroot/wesn-pt-trans

Mailing Lists:
* wesn-pt-trans-commits <at.here> lists.sourceforge.net - registo de commits, lista para onde são enviados automaticamente as mensagens de commit.
* wesn-pt-trans-users <at.here> lists.sourceforge.net - lista geral, pode ser usada para qualquer tipo de contacto, pergunta ou comentário.

[[Category:Translations]]

PortugueseContinentalTranslation

2012-12-22T22:51:54Z

Trewe: /* Lista de Traduções */

== Introdução ==
Bemvindo à página de apresentação da tradução para português de Portugal do jogo "Battle for Wesnoth"

O esforço de tradução pretende oferecer aos utilizadores de "Battle for Wesnoth" a possibilidade de jogarem o jogo na sua língua nativa e numa versão localizada ao seu país. Desta forma pretende-se que a experiência de jogo seja melhor e que mais pessoas possam usufruir deste jogo.

A todos os que tiverem oportunidade pedimos ajuda neste processo, seja oferecendo o seu tempo trabalhando activamente na tradução, seja através de sugestões, dicas e indicações de pequenos erros ou falhas existentes.

== Equipa de Tradução ==

=== Elementos ===
Actualmente a equipa de tradução é composta por:

* Sérgio Lopes (maintainer)

* trewe (co-maintainer)

Inactivos:

* Carlos Sousa

* Luís Passos

=== Contactos ===
A equipa de tradução pode ser contactada através do seu espaço no SourceForge, [http://sourceforge.net/projects/wesn-pt-trans/ wesn-pt-trans]. Nele podem encontrar a lista de discussão bem como um ponto de acesso aos ficheiros a traduzir.

== Regras para Tradutores ==
As seguintes regras pretendem introduzir futuros colaboradores no processo de tradução. São um ponto de partida a verificar, no entanto, qualquer dúvida pode ser colocada quer por e-mail quer na lista de discussão.

=== Processo Geral ===

[[WesnothTranslationsHowTo]]

=== Processo da Equipa de Português ===

A tradução do Wesnoth é feita recorrendo aos serviços que o [http://sourceforge.net Sourceforge] oferece.
Desses serviços o projecto usa [https://sourceforge.net/mail/?group_id=209264 Mailing Lists], [https://sourceforge.net/svn/?group_id=209264 Repositório de Subversion] e sistema de [https://sourceforge.net/tracker/?group_id=209264 Bug Reports].
É assim necessário ter acesso a um cliente [http://subversion.tigris.org Subversion], aceder ao repositório do projecto de tradução e obter os ficheiros a traduzir.

Após terem sido obtidos os ficheiros será necessário usar um programa de edição de ficheiros *.po, http://www.poedit.net é um bom exemplo de um programa open source e multiplataforma que poderão usar.

Quando iniciarem a tradução de um ficheiro, embora não seja necessário, é aconselhável que notifiquem um dos membros aqui listados. Quando terminarem uma tradução basta que enviem o(s) ficheiro(s) traduzido(s) para o responsável pelo projecto, ([mailto:knitter.is@gmail.com Sérgio Lopes] à data de escrita deste texto) para que os ficheiros sejam incluídos no repositório.

O livre acesso ao repositório será fornecido após pedido e avaliação do trabalho feito.

== Links importantes ==

Página do projecto: <a definir>

Página de detalhes no sourceforge: http://sourceforge.net/projects/wesn-pt-trans

Endereço do repositório: https://wesn-pt-trans.svn.sourceforge.net/svnroot/wesn-pt-trans

Mailing Lists:
* wesn-pt-trans-commits <at.here> lists.sourceforge.net - registo de commits, lista para onde são enviados automaticamente as mensagens de commit.
* wesn-pt-trans-users <at.here> lists.sourceforge.net - lista geral, pode ser usada para qualquer tipo de contacto, pergunta ou comentário.

== Lista de Traduções ==

A seguinte lista pretende mostrar todas as traduções existentes ou futuras do jogo.

[[WesnothTranslations]]

[[Units]]

[[Category:Translations]]