The Battle for Wesnoth Wiki - User contributions [en]

DeadlyUnitsFromLotI

2022-07-03T16:00:58Z

Mathemagician: /* Devastating Demilich of Doom */

== Legend of the Invincibles - Deadly units (2019 versions) ==

Add your suggestions here!!!

(WDF) Entirely Different Game Plan As this Unit Doesn't Kill Itself But Makes everything else Stupid. Duke/Elvish Warlord With Basically any support items/Amla's Can Make an Average Unit Into A Boss Shredder by giving it over 100% Attack Increase, Penetration,Defense Buffs, Marksman And Whatever else You could think of with the right Items. Not really a specific unit But moreso An Overall Type of unit. 2 Big Tips, 1: You can Get a Duke(Who can get one higher level of leadership I believe) relatively early By levelling Mario in Part 1 And The General On Efraim's Side in Part 2 and 2: If you want to InstaKill Bosses, Use these guys to Buff Battleragers. Whatever the Ragers Are Looking at won't be a boss for Long.

== Legend of the Invincibles - Deadly units (2015 to 2019 changes) ==
=== Assassin of Everything ===
The reduction is suck is the primary reason this unit is no longer so dominant. Getting more than suck 2 is pretty tough in 2019. Conviction also formerly reduced all resistances and now it only reduces elemental ones (see Frail tide for physical).

== Legend of the Invincibles - Deadly units (2015 versions) ==
I ([[User:Ashes]]) created this wiki page to share tips and tricks for Legend of the Invincibles, and mainly to share deadly units. This campaign has a gameply so different from the standard BfW game that the usual tricks are no more relevant. The start of the campaign is good to help the beginner, but some other things can only be learned later, when playing.

== Boss killers ==
Sometimes, there is a villain with hundreds of hitpoints. One possibility is to carefully organise a long fight that will kill the villain. But in practice it is more efficient to have a boss killer that will kill it in one turn.

=== Berserker draining dwarf ===
My ([[User:Ashes]]) favourite boss killer.
A Dwarvish Battlerager with a Soul Eclipse axe. Unless the enemy resists drain, or the enemy is very difficult to hit, this dwarf is deadly.

I also equipped my Dwarvish Battlerager with a Mithral Armour of Wrath (wrath is very useful for berserkers) and some additional but less important items (a Deadborn cloak to suck 2 health and to have 5% chance to strike a devastating blow; boots of Lightning agility and Lucky Farmer's Amulet to reduce chances of getting hit, gauntlets of Fiery Blood to be able to choose between fire damage and blade damage, ...)

Why is he better:
Full fledged berserk means a huge number of attacks - either he dies or the target dies.

=== Destroyer (Part II equipment) ===
My ([[User:dabber]]) primary solo boss killer.
Destroyer with Jawbreaker as his weapon, because that provides Mayhem (target damage drops after each hit). Need AMLAs for Battle Frenzy and its upgrades to give him 30 attacks. Jawbreaker provides only suck 2, but a little bit more suck from other items combined with his natural physical resistances mean he does fine.

Other major upgrades:
* Mystic Armour of the Untouchable (suck and dodge)
* Orb of Wrath (wrath)
* Fencer's Study
* AMLAs to increase physical resistance

Why is he great:
* Impact resistance is generally lower than other resistances.
* Mayhem reduces damage coming back, and means even if the target lives, it isn't so dangerous anymore.

I'm running a Demon Lord hunting group through The Last Crusade (end of chapter 9), with two Celestial Messengers (Legacy of Kings), a Duke, a Swordmaster (for Doom and Trickery via Stormrend) and this guy. With buffs, this guy can immediately kill many Demon Lords.

=== Evil Healer (Lich King) ===
by Delicius169

Lich King is quite a weak unit, his only advantage is that if you use Tome of liches, he can become unit with the biggest amount of weapons (mage-white mage- paladin- lich- lich king= mace, spear, sword, essence of magic, axe, staff)

* 35-6 meele, blade
* 22-4 ice wave
* 16-4 shadow wave
* 30-4 doom, meele, blade

resistance: 58/61/16/60/90/45

Items:
* Books: Book of courage, Magical swordplay, How to be an overlord (hasnt finished reading yet)
* Blackened cloak, intoxicator (boots), Mask of insanity, Mystic armour of Carparitia, dark gloves of destruction, Demon core (amulet), sparkling ring
* Weapons: 2x Dominion (Mace, Essence of magic), Deathwhirl (sword), Staff of Crelanu, Corpsegrinder (spear, gives Eviscreation), Morrigans Slasher (axe, gives murderlust)

He is the one, who stands in front line, he is the most usefull healer I have. He can kill almost every unit in one round (thanks to mask of insanity), he cant be affected by temptation, he weakens strong leaders with doom attack.

Of course, he could be stronger, I was too lazy to try more unit to get Legacy of kings/ sorrow/ dark dragon, so I got just legacy of Titans. Also I dint get the Mace with Hate speech skill.

== Lone warriors ==
Some units are quite good when sent alone behing the enemy lines.

=== Juggernaut of doom ===
An Elvish Juggernaut, doing 57-9 melee (blade, slow, disintegrate) and 36-9 ranged (pierce, marksman, slow) or 26-6 ranged (arcane, slow, drain, focused -- useful to drain hitpoints when regenerating is not enough).

Equipped with Doombringer sword, and Stormforce bow, and protected by a Prayer armour, a Gloomy Cloak, a Gloomy Amulet, a Gloomy Ring, Mighty Gauntlets, Elusive Boots and the Dark Helm of Destruction.

A full Dark Dragon Legacy, four AMLA for bow, two AMLA for sword, five AMLA to reduce chance to be hit by 10% and a few AMLA to increase physical resistances.

=== Icy Dragon Rider of Wrath ===
A Dragon Rider mainly doing 75-4 wrath (5) melee (ice, charge, slow, horrid, backstab) or 26-6 ranged (ice, slow, cone) and defensively 39-4 melee with drain and slow.

Equipped with a Holy Sword and a Return to the Tribe spear, and protected by a Horrid Ice Armour, a Ring of Iced Veins, Slow Boots, Draingloves, a Mask of Famine, a Leechward amulet and a Cloak of the Assassin Leader.

A full Ice Dragon Legacy, a full Raging/Wrathful Combat Techniques, five AMLA to command the dragon to bite better (and to eat in the process), five AMLA to have a tougher dragon.

=== Assassin of Everything ===
dabber's deadliest lone unit.
Elvish Assassin. Legacy of Sorrow, Dark set 
Melee 33-8 blade, struggle, slows, poison, suck 5 
Ranged 33-11, blade, focused, mind raid, struggle, slows, poison, suck 7 
Resistances 37,37,18,30,25,40

No unit in my army, including Efraim and Lethalia, has anywhere near the experience of this lady. I let her solo several levels of Inferno for fun.

Critical Equipment: 
Dark Sword, Dark Helm, Dark Gloves, Unprecious Ring, Intoxicator boots 

Other Current Equipment: 
Mystic Armour of the Untouchable, Bow of Plagiarism, Gloomy Cloak, Amulet of Reason, Fencer's Study

Why is she great: 
* Conviction means she does serious damage to any target.
* Focussed on ranged attacks ensures they hit, and therefore suck.
* High suck with many attacks, plus despair, slow, and struggle means she avoids or heals most any damage.
* If she ever gets hurt, she can use Distant Attack to heal.

=== Deadly Champion ===

Favorite of arobinson, the Champion's power is in the opponent missing, not in the offensive power of the unit. The idea is to make the Champion very hard to hit and then use Anger to increase the number of attacks. The more attacks the opponent has the better in this case. Because of the Champion's chance to be hit ratio, a few equipment items means that it almost cannot be hit. The unit is not all that good for spell defense, so it is not quite a loner, but it is very powerful on offense against any opponent.

There are many options for armor and weapons, but basically you want to try to (1) maximize the number of attacks and (2) decrease the chance to hit.

Recommended Equipment: 
* Crafted "Anger" sword or "Marrowrend" (*2 attacks offense and defense, this is key)
* Helmet
** Helmet of Paladins (for the illumination)
** Mask of Insanity (not necessary, but good for really hard units)
** Rherraent's Helm
* Gloves
** Quick Gauntlets (+1 attack)
** Draingloves
** Dark Gloves of Destruction
* Book of Courage (if not using the Helmet of Paladins)
* Dazzling Ring
* Amulets
** The gloomy Amulet
** Lucky Farmer's Amulet
** Amulet of the Last Guide
* Armor
** Mystic Armour of the Untouchable
** Dark Sarcasm
** Redshirt Armour
* Crossbow
** Crafted Gloombringer crossbow
** Crafted Malice crossbow
** Crafted Deathblade Inheritance crossbow
* Boots
** Elusive Boots
** Slow Boots of Certainty
* Cloak of the Assassin leader
* Other crafted
** Lightning Agility
** Deflector of Light

Advancements: 
Focus on the sword (number of attacks), then "better at defending" (up to -15% chance to be hit) and then the "better resistances when defending" advancements to improve the unit's defense against magical attacks while defending.

=== Devastating Demilich of Doom ===

With maxed out resistances, good healing and tons of penetration, this unit can sometimes kill healthy units even while slowed, and is nearly impossible to kill.

* Weapons
** Soul Hunter (nostalgia)
** Misanthropia (nostalgia)
** Another Misanthropia (nostalgia)
** A third Misanthropia (otherworldly essence)
** The Killer of Great Magi (staff)
* Armor
** Crapsack World (amulet)
** Fiery Blood (gauntlets)
** Wisdom of the Ages (helm)
** The Godless (armor)
** Search for Wisdom (boots)
** Exterminator's Ring
** Tracking the Lost Knowledge (cloak)
* Tomes
** Book of Herbal Tinctures and Malignancies

That gives you 21-8 melee with drain and 31-6 ranged with magical, slows, spell suck 3 and 70% cold penetration, and all resistances except impact maxed out. Regen +13, murderlust and absorb 1 really seals the deal. If you want to fish for legacies, Legacy of the Frozen North, Legacy of Sorrow and Legacy of the Free are all fine choices.

There's a bit of leeway with gear here too. Lucky Farmer's Amulet is fine with the rest of the list, and The Touch of God might be an improvement over Tracking the Lost Knowledge. Fire Dragon Legacy and Wrathful Combat Techniques or Guide to Lycanthropy is also worth considering, to make this a boss killer and a lone warrior.

How do you get 3 nostalgia weapons? Use the Tome of Liches on one of these, and let the unit get killed once it has the necromancy ability:

* Exterminator (dagger, knife, polearm)
* Elvish Sharpshooter/Outrider (sword) -> Elvish Gryphon Rider (metal claws, bow)
* Mage of Light (mace) -> Prophet (sword, spear)

DeadlyUnitsFromLotI

2022-07-03T15:59:55Z

Mathemagician: /* Devastating Demilich of Doom */

== Legend of the Invincibles - Deadly units (2019 versions) ==

Add your suggestions here!!!

(WDF) Entirely Different Game Plan As this Unit Doesn't Kill Itself But Makes everything else Stupid. Duke/Elvish Warlord With Basically any support items/Amla's Can Make an Average Unit Into A Boss Shredder by giving it over 100% Attack Increase, Penetration,Defense Buffs, Marksman And Whatever else You could think of with the right Items. Not really a specific unit But moreso An Overall Type of unit. 2 Big Tips, 1: You can Get a Duke(Who can get one higher level of leadership I believe) relatively early By levelling Mario in Part 1 And The General On Efraim's Side in Part 2 and 2: If you want to InstaKill Bosses, Use these guys to Buff Battleragers. Whatever the Ragers Are Looking at won't be a boss for Long.

== Legend of the Invincibles - Deadly units (2015 to 2019 changes) ==
=== Assassin of Everything ===
The reduction is suck is the primary reason this unit is no longer so dominant. Getting more than suck 2 is pretty tough in 2019. Conviction also formerly reduced all resistances and now it only reduces elemental ones (see Frail tide for physical).

== Legend of the Invincibles - Deadly units (2015 versions) ==
I ([[User:Ashes]]) created this wiki page to share tips and tricks for Legend of the Invincibles, and mainly to share deadly units. This campaign has a gameply so different from the standard BfW game that the usual tricks are no more relevant. The start of the campaign is good to help the beginner, but some other things can only be learned later, when playing.

== Boss killers ==
Sometimes, there is a villain with hundreds of hitpoints. One possibility is to carefully organise a long fight that will kill the villain. But in practice it is more efficient to have a boss killer that will kill it in one turn.

=== Berserker draining dwarf ===
My ([[User:Ashes]]) favourite boss killer.
A Dwarvish Battlerager with a Soul Eclipse axe. Unless the enemy resists drain, or the enemy is very difficult to hit, this dwarf is deadly.

I also equipped my Dwarvish Battlerager with a Mithral Armour of Wrath (wrath is very useful for berserkers) and some additional but less important items (a Deadborn cloak to suck 2 health and to have 5% chance to strike a devastating blow; boots of Lightning agility and Lucky Farmer's Amulet to reduce chances of getting hit, gauntlets of Fiery Blood to be able to choose between fire damage and blade damage, ...)

Why is he better:
Full fledged berserk means a huge number of attacks - either he dies or the target dies.

=== Destroyer (Part II equipment) ===
My ([[User:dabber]]) primary solo boss killer.
Destroyer with Jawbreaker as his weapon, because that provides Mayhem (target damage drops after each hit). Need AMLAs for Battle Frenzy and its upgrades to give him 30 attacks. Jawbreaker provides only suck 2, but a little bit more suck from other items combined with his natural physical resistances mean he does fine.

Other major upgrades:
* Mystic Armour of the Untouchable (suck and dodge)
* Orb of Wrath (wrath)
* Fencer's Study
* AMLAs to increase physical resistance

Why is he great:
* Impact resistance is generally lower than other resistances.
* Mayhem reduces damage coming back, and means even if the target lives, it isn't so dangerous anymore.

I'm running a Demon Lord hunting group through The Last Crusade (end of chapter 9), with two Celestial Messengers (Legacy of Kings), a Duke, a Swordmaster (for Doom and Trickery via Stormrend) and this guy. With buffs, this guy can immediately kill many Demon Lords.

=== Evil Healer (Lich King) ===
by Delicius169

Lich King is quite a weak unit, his only advantage is that if you use Tome of liches, he can become unit with the biggest amount of weapons (mage-white mage- paladin- lich- lich king= mace, spear, sword, essence of magic, axe, staff)

* 35-6 meele, blade
* 22-4 ice wave
* 16-4 shadow wave
* 30-4 doom, meele, blade

resistance: 58/61/16/60/90/45

Items:
* Books: Book of courage, Magical swordplay, How to be an overlord (hasnt finished reading yet)
* Blackened cloak, intoxicator (boots), Mask of insanity, Mystic armour of Carparitia, dark gloves of destruction, Demon core (amulet), sparkling ring
* Weapons: 2x Dominion (Mace, Essence of magic), Deathwhirl (sword), Staff of Crelanu, Corpsegrinder (spear, gives Eviscreation), Morrigans Slasher (axe, gives murderlust)

He is the one, who stands in front line, he is the most usefull healer I have. He can kill almost every unit in one round (thanks to mask of insanity), he cant be affected by temptation, he weakens strong leaders with doom attack.

Of course, he could be stronger, I was too lazy to try more unit to get Legacy of kings/ sorrow/ dark dragon, so I got just legacy of Titans. Also I dint get the Mace with Hate speech skill.

== Lone warriors ==
Some units are quite good when sent alone behing the enemy lines.

=== Juggernaut of doom ===
An Elvish Juggernaut, doing 57-9 melee (blade, slow, disintegrate) and 36-9 ranged (pierce, marksman, slow) or 26-6 ranged (arcane, slow, drain, focused -- useful to drain hitpoints when regenerating is not enough).

Equipped with Doombringer sword, and Stormforce bow, and protected by a Prayer armour, a Gloomy Cloak, a Gloomy Amulet, a Gloomy Ring, Mighty Gauntlets, Elusive Boots and the Dark Helm of Destruction.

A full Dark Dragon Legacy, four AMLA for bow, two AMLA for sword, five AMLA to reduce chance to be hit by 10% and a few AMLA to increase physical resistances.

=== Icy Dragon Rider of Wrath ===
A Dragon Rider mainly doing 75-4 wrath (5) melee (ice, charge, slow, horrid, backstab) or 26-6 ranged (ice, slow, cone) and defensively 39-4 melee with drain and slow.

Equipped with a Holy Sword and a Return to the Tribe spear, and protected by a Horrid Ice Armour, a Ring of Iced Veins, Slow Boots, Draingloves, a Mask of Famine, a Leechward amulet and a Cloak of the Assassin Leader.

A full Ice Dragon Legacy, a full Raging/Wrathful Combat Techniques, five AMLA to command the dragon to bite better (and to eat in the process), five AMLA to have a tougher dragon.

=== Assassin of Everything ===
dabber's deadliest lone unit.
Elvish Assassin. Legacy of Sorrow, Dark set 
Melee 33-8 blade, struggle, slows, poison, suck 5 
Ranged 33-11, blade, focused, mind raid, struggle, slows, poison, suck 7 
Resistances 37,37,18,30,25,40

No unit in my army, including Efraim and Lethalia, has anywhere near the experience of this lady. I let her solo several levels of Inferno for fun.

Critical Equipment: 
Dark Sword, Dark Helm, Dark Gloves, Unprecious Ring, Intoxicator boots 

Other Current Equipment: 
Mystic Armour of the Untouchable, Bow of Plagiarism, Gloomy Cloak, Amulet of Reason, Fencer's Study

Why is she great: 
* Conviction means she does serious damage to any target.
* Focussed on ranged attacks ensures they hit, and therefore suck.
* High suck with many attacks, plus despair, slow, and struggle means she avoids or heals most any damage.
* If she ever gets hurt, she can use Distant Attack to heal.

=== Deadly Champion ===

Favorite of arobinson, the Champion's power is in the opponent missing, not in the offensive power of the unit. The idea is to make the Champion very hard to hit and then use Anger to increase the number of attacks. The more attacks the opponent has the better in this case. Because of the Champion's chance to be hit ratio, a few equipment items means that it almost cannot be hit. The unit is not all that good for spell defense, so it is not quite a loner, but it is very powerful on offense against any opponent.

There are many options for armor and weapons, but basically you want to try to (1) maximize the number of attacks and (2) decrease the chance to hit.

Recommended Equipment: 
* Crafted "Anger" sword or "Marrowrend" (*2 attacks offense and defense, this is key)
* Helmet
** Helmet of Paladins (for the illumination)
** Mask of Insanity (not necessary, but good for really hard units)
** Rherraent's Helm
* Gloves
** Quick Gauntlets (+1 attack)
** Draingloves
** Dark Gloves of Destruction
* Book of Courage (if not using the Helmet of Paladins)
* Dazzling Ring
* Amulets
** The gloomy Amulet
** Lucky Farmer's Amulet
** Amulet of the Last Guide
* Armor
** Mystic Armour of the Untouchable
** Dark Sarcasm
** Redshirt Armour
* Crossbow
** Crafted Gloombringer crossbow
** Crafted Malice crossbow
** Crafted Deathblade Inheritance crossbow
* Boots
** Elusive Boots
** Slow Boots of Certainty
* Cloak of the Assassin leader
* Other crafted
** Lightning Agility
** Deflector of Light

Advancements: 
Focus on the sword (number of attacks), then "better at defending" (up to -15% chance to be hit) and then the "better resistances when defending" advancements to improve the unit's defense against magical attacks while defending.

=== Devastating Demilich of Doom ===

With maxed out resistances, good healing and tons of penetration, this unit can sometimes kill healthy units even while slowed, and is nearly impossible to kill.

* Weapons
** Soul Hunter (nostalgia)
** Misanthropia (nostalgia)
** Another Misanthropia (nostalgia)
** A third Misanthropia (otherworldly essence)
** The Killer of Great Magi (staff)
* Armor
** Crapsack World (amulet)
** Fiery Blood (gauntlets)
** Wisdom of the Ages (helm)
** The Godless (armor)
** Search for Wisdom (boots)
** Exterminator's Ring
** Tracking the Lost Knowledge (cloak)
* Tomes
** Book of Herbal Tinctures and Malignancies

That gives you 21-8 melee with drain and 31-6 ranged with slows, spell suck 3 and 70% cold penetration, and all resistances except impact maxed out. Regen +13, murderlust and absorb 1 really seals the deal. If you want to fish for legacies, Legacy of the Frozen North, Legacy of Sorrow and Legacy of the Free are all fine choices.

There's a bit of leeway with gear here too. Lucky Farmer's Amulet is fine with the rest of the list, and The Touch of God might be an improvement over Tracking the Lost Knowledge. Fire Dragon Legacy and Wrathful Combat Techniques or Guide to Lycanthropy is also worth considering, to make this a boss killer and a lone warrior.

How do you get 3 nostalgia weapons? Use the Tome of Liches on one of these, and let the unit get killed once it has the necromancy ability:

* Exterminator (dagger, knife, polearm)
* Elvish Sharpshooter/Outrider (sword) -> Elvish Gryphon Rider (metal claws, bow)
* Mage of Light (mace) -> Prophet (sword, spear)

DeadlyUnitsFromLotI

2022-07-03T15:32:34Z

Mathemagician: /* Devastating Demilich of Doom */

== Legend of the Invincibles - Deadly units (2019 versions) ==

Add your suggestions here!!!

(WDF) Entirely Different Game Plan As this Unit Doesn't Kill Itself But Makes everything else Stupid. Duke/Elvish Warlord With Basically any support items/Amla's Can Make an Average Unit Into A Boss Shredder by giving it over 100% Attack Increase, Penetration,Defense Buffs, Marksman And Whatever else You could think of with the right Items. Not really a specific unit But moreso An Overall Type of unit. 2 Big Tips, 1: You can Get a Duke(Who can get one higher level of leadership I believe) relatively early By levelling Mario in Part 1 And The General On Efraim's Side in Part 2 and 2: If you want to InstaKill Bosses, Use these guys to Buff Battleragers. Whatever the Ragers Are Looking at won't be a boss for Long.

== Legend of the Invincibles - Deadly units (2015 to 2019 changes) ==
=== Assassin of Everything ===
The reduction is suck is the primary reason this unit is no longer so dominant. Getting more than suck 2 is pretty tough in 2019. Conviction also formerly reduced all resistances and now it only reduces elemental ones (see Frail tide for physical).

== Legend of the Invincibles - Deadly units (2015 versions) ==
I ([[User:Ashes]]) created this wiki page to share tips and tricks for Legend of the Invincibles, and mainly to share deadly units. This campaign has a gameply so different from the standard BfW game that the usual tricks are no more relevant. The start of the campaign is good to help the beginner, but some other things can only be learned later, when playing.

== Boss killers ==
Sometimes, there is a villain with hundreds of hitpoints. One possibility is to carefully organise a long fight that will kill the villain. But in practice it is more efficient to have a boss killer that will kill it in one turn.

=== Berserker draining dwarf ===
My ([[User:Ashes]]) favourite boss killer.
A Dwarvish Battlerager with a Soul Eclipse axe. Unless the enemy resists drain, or the enemy is very difficult to hit, this dwarf is deadly.

I also equipped my Dwarvish Battlerager with a Mithral Armour of Wrath (wrath is very useful for berserkers) and some additional but less important items (a Deadborn cloak to suck 2 health and to have 5% chance to strike a devastating blow; boots of Lightning agility and Lucky Farmer's Amulet to reduce chances of getting hit, gauntlets of Fiery Blood to be able to choose between fire damage and blade damage, ...)

Why is he better:
Full fledged berserk means a huge number of attacks - either he dies or the target dies.

=== Destroyer (Part II equipment) ===
My ([[User:dabber]]) primary solo boss killer.
Destroyer with Jawbreaker as his weapon, because that provides Mayhem (target damage drops after each hit). Need AMLAs for Battle Frenzy and its upgrades to give him 30 attacks. Jawbreaker provides only suck 2, but a little bit more suck from other items combined with his natural physical resistances mean he does fine.

Other major upgrades:
* Mystic Armour of the Untouchable (suck and dodge)
* Orb of Wrath (wrath)
* Fencer's Study
* AMLAs to increase physical resistance

Why is he great:
* Impact resistance is generally lower than other resistances.
* Mayhem reduces damage coming back, and means even if the target lives, it isn't so dangerous anymore.

I'm running a Demon Lord hunting group through The Last Crusade (end of chapter 9), with two Celestial Messengers (Legacy of Kings), a Duke, a Swordmaster (for Doom and Trickery via Stormrend) and this guy. With buffs, this guy can immediately kill many Demon Lords.

=== Evil Healer (Lich King) ===
by Delicius169

Lich King is quite a weak unit, his only advantage is that if you use Tome of liches, he can become unit with the biggest amount of weapons (mage-white mage- paladin- lich- lich king= mace, spear, sword, essence of magic, axe, staff)

* 35-6 meele, blade
* 22-4 ice wave
* 16-4 shadow wave
* 30-4 doom, meele, blade

resistance: 58/61/16/60/90/45

Items:
* Books: Book of courage, Magical swordplay, How to be an overlord (hasnt finished reading yet)
* Blackened cloak, intoxicator (boots), Mask of insanity, Mystic armour of Carparitia, dark gloves of destruction, Demon core (amulet), sparkling ring
* Weapons: 2x Dominion (Mace, Essence of magic), Deathwhirl (sword), Staff of Crelanu, Corpsegrinder (spear, gives Eviscreation), Morrigans Slasher (axe, gives murderlust)

He is the one, who stands in front line, he is the most usefull healer I have. He can kill almost every unit in one round (thanks to mask of insanity), he cant be affected by temptation, he weakens strong leaders with doom attack.

Of course, he could be stronger, I was too lazy to try more unit to get Legacy of kings/ sorrow/ dark dragon, so I got just legacy of Titans. Also I dint get the Mace with Hate speech skill.

== Lone warriors ==
Some units are quite good when sent alone behing the enemy lines.

=== Juggernaut of doom ===
An Elvish Juggernaut, doing 57-9 melee (blade, slow, disintegrate) and 36-9 ranged (pierce, marksman, slow) or 26-6 ranged (arcane, slow, drain, focused -- useful to drain hitpoints when regenerating is not enough).

Equipped with Doombringer sword, and Stormforce bow, and protected by a Prayer armour, a Gloomy Cloak, a Gloomy Amulet, a Gloomy Ring, Mighty Gauntlets, Elusive Boots and the Dark Helm of Destruction.

A full Dark Dragon Legacy, four AMLA for bow, two AMLA for sword, five AMLA to reduce chance to be hit by 10% and a few AMLA to increase physical resistances.

=== Icy Dragon Rider of Wrath ===
A Dragon Rider mainly doing 75-4 wrath (5) melee (ice, charge, slow, horrid, backstab) or 26-6 ranged (ice, slow, cone) and defensively 39-4 melee with drain and slow.

Equipped with a Holy Sword and a Return to the Tribe spear, and protected by a Horrid Ice Armour, a Ring of Iced Veins, Slow Boots, Draingloves, a Mask of Famine, a Leechward amulet and a Cloak of the Assassin Leader.

A full Ice Dragon Legacy, a full Raging/Wrathful Combat Techniques, five AMLA to command the dragon to bite better (and to eat in the process), five AMLA to have a tougher dragon.

=== Assassin of Everything ===
dabber's deadliest lone unit.
Elvish Assassin. Legacy of Sorrow, Dark set 
Melee 33-8 blade, struggle, slows, poison, suck 5 
Ranged 33-11, blade, focused, mind raid, struggle, slows, poison, suck 7 
Resistances 37,37,18,30,25,40

No unit in my army, including Efraim and Lethalia, has anywhere near the experience of this lady. I let her solo several levels of Inferno for fun.

Critical Equipment: 
Dark Sword, Dark Helm, Dark Gloves, Unprecious Ring, Intoxicator boots 

Other Current Equipment: 
Mystic Armour of the Untouchable, Bow of Plagiarism, Gloomy Cloak, Amulet of Reason, Fencer's Study

Why is she great: 
* Conviction means she does serious damage to any target.
* Focussed on ranged attacks ensures they hit, and therefore suck.
* High suck with many attacks, plus despair, slow, and struggle means she avoids or heals most any damage.
* If she ever gets hurt, she can use Distant Attack to heal.

=== Deadly Champion ===

Favorite of arobinson, the Champion's power is in the opponent missing, not in the offensive power of the unit. The idea is to make the Champion very hard to hit and then use Anger to increase the number of attacks. The more attacks the opponent has the better in this case. Because of the Champion's chance to be hit ratio, a few equipment items means that it almost cannot be hit. The unit is not all that good for spell defense, so it is not quite a loner, but it is very powerful on offense against any opponent.

There are many options for armor and weapons, but basically you want to try to (1) maximize the number of attacks and (2) decrease the chance to hit.

Recommended Equipment: 
* Crafted "Anger" sword or "Marrowrend" (*2 attacks offense and defense, this is key)
* Helmet
** Helmet of Paladins (for the illumination)
** Mask of Insanity (not necessary, but good for really hard units)
** Rherraent's Helm
* Gloves
** Quick Gauntlets (+1 attack)
** Draingloves
** Dark Gloves of Destruction
* Book of Courage (if not using the Helmet of Paladins)
* Dazzling Ring
* Amulets
** The gloomy Amulet
** Lucky Farmer's Amulet
** Amulet of the Last Guide
* Armor
** Mystic Armour of the Untouchable
** Dark Sarcasm
** Redshirt Armour
* Crossbow
** Crafted Gloombringer crossbow
** Crafted Malice crossbow
** Crafted Deathblade Inheritance crossbow
* Boots
** Elusive Boots
** Slow Boots of Certainty
* Cloak of the Assassin leader
* Other crafted
** Lightning Agility
** Deflector of Light

Advancements: 
Focus on the sword (number of attacks), then "better at defending" (up to -15% chance to be hit) and then the "better resistances when defending" advancements to improve the unit's defense against magical attacks while defending.

=== Devastating Demilich of Doom ===

With maxed out resistances, good healing and tons of penetration, this unit can sometimes kill healthy units even while slowed, and is nearly impossible to kill.

* Weapons
** Soul Hunter (nostalgia)
** Misanthropia (nostalgia)
** Another Misanthropia (nostalgia)
** A third Misanthropia (otherworldly essence)
** The Killer of Great Magi (staff)
* Armor
** Crapsack World (amulet)
** Fiery Blood (gauntlets)
** Wisdom of the Ages (helm)
** The Godless (armor)
** Search for Wisdom (boots)
** Exterminator's Ring
** Tracking the Lost Knowledge (cloak)
* Tomes
** Book of Herbal Tinctures and Malignancies

That gives you 21-8 melee with drain and 31-6 ranged with slows, spell suck 3 and 70% cold penetration, and all resistances except impact maxed out. Regen +13 and absorb 1 really seals the deal. If you want to fish for legacies, Legacy of the Frozen North, Legacy of Sorrow and Legacy of the Free are all fine choices.

There's a bit of leeway with gear here too. Lucky Farmer's Amulet is fine with the rest of the list, and The Touch of God might be an improvement over Tracking the Lost Knowledge. Fire Dragon Legacy and Wrathful Combat Techniques or Guide to Lycanthropy is also worth considering, to make this a boss killer and a lone warrior.

How do you get 3 nostalgia weapons? Use the Tome of Liches on one of these, and let the unit get killed once it has the necromancy ability:

* Exterminator (dagger, knife, polearm)
* Elvish Sharpshooter/Outrider (sword) -> Elvish Gryphon Rider (metal claws, bow)
* Mage of Light (mace) -> Prophet (sword, spear)

DeadlyUnitsFromLotI

2022-07-03T15:28:36Z

Mathemagician: /* Lone warriors */

== Legend of the Invincibles - Deadly units (2019 versions) ==

Add your suggestions here!!!

(WDF) Entirely Different Game Plan As this Unit Doesn't Kill Itself But Makes everything else Stupid. Duke/Elvish Warlord With Basically any support items/Amla's Can Make an Average Unit Into A Boss Shredder by giving it over 100% Attack Increase, Penetration,Defense Buffs, Marksman And Whatever else You could think of with the right Items. Not really a specific unit But moreso An Overall Type of unit. 2 Big Tips, 1: You can Get a Duke(Who can get one higher level of leadership I believe) relatively early By levelling Mario in Part 1 And The General On Efraim's Side in Part 2 and 2: If you want to InstaKill Bosses, Use these guys to Buff Battleragers. Whatever the Ragers Are Looking at won't be a boss for Long.

== Legend of the Invincibles - Deadly units (2015 to 2019 changes) ==
=== Assassin of Everything ===
The reduction is suck is the primary reason this unit is no longer so dominant. Getting more than suck 2 is pretty tough in 2019. Conviction also formerly reduced all resistances and now it only reduces elemental ones (see Frail tide for physical).

== Legend of the Invincibles - Deadly units (2015 versions) ==
I ([[User:Ashes]]) created this wiki page to share tips and tricks for Legend of the Invincibles, and mainly to share deadly units. This campaign has a gameply so different from the standard BfW game that the usual tricks are no more relevant. The start of the campaign is good to help the beginner, but some other things can only be learned later, when playing.

== Boss killers ==
Sometimes, there is a villain with hundreds of hitpoints. One possibility is to carefully organise a long fight that will kill the villain. But in practice it is more efficient to have a boss killer that will kill it in one turn.

=== Berserker draining dwarf ===
My ([[User:Ashes]]) favourite boss killer.
A Dwarvish Battlerager with a Soul Eclipse axe. Unless the enemy resists drain, or the enemy is very difficult to hit, this dwarf is deadly.

I also equipped my Dwarvish Battlerager with a Mithral Armour of Wrath (wrath is very useful for berserkers) and some additional but less important items (a Deadborn cloak to suck 2 health and to have 5% chance to strike a devastating blow; boots of Lightning agility and Lucky Farmer's Amulet to reduce chances of getting hit, gauntlets of Fiery Blood to be able to choose between fire damage and blade damage, ...)

Why is he better:
Full fledged berserk means a huge number of attacks - either he dies or the target dies.

=== Destroyer (Part II equipment) ===
My ([[User:dabber]]) primary solo boss killer.
Destroyer with Jawbreaker as his weapon, because that provides Mayhem (target damage drops after each hit). Need AMLAs for Battle Frenzy and its upgrades to give him 30 attacks. Jawbreaker provides only suck 2, but a little bit more suck from other items combined with his natural physical resistances mean he does fine.

Other major upgrades:
* Mystic Armour of the Untouchable (suck and dodge)
* Orb of Wrath (wrath)
* Fencer's Study
* AMLAs to increase physical resistance

Why is he great:
* Impact resistance is generally lower than other resistances.
* Mayhem reduces damage coming back, and means even if the target lives, it isn't so dangerous anymore.

I'm running a Demon Lord hunting group through The Last Crusade (end of chapter 9), with two Celestial Messengers (Legacy of Kings), a Duke, a Swordmaster (for Doom and Trickery via Stormrend) and this guy. With buffs, this guy can immediately kill many Demon Lords.

=== Evil Healer (Lich King) ===
by Delicius169

Lich King is quite a weak unit, his only advantage is that if you use Tome of liches, he can become unit with the biggest amount of weapons (mage-white mage- paladin- lich- lich king= mace, spear, sword, essence of magic, axe, staff)

* 35-6 meele, blade
* 22-4 ice wave
* 16-4 shadow wave
* 30-4 doom, meele, blade

resistance: 58/61/16/60/90/45

Items:
* Books: Book of courage, Magical swordplay, How to be an overlord (hasnt finished reading yet)
* Blackened cloak, intoxicator (boots), Mask of insanity, Mystic armour of Carparitia, dark gloves of destruction, Demon core (amulet), sparkling ring
* Weapons: 2x Dominion (Mace, Essence of magic), Deathwhirl (sword), Staff of Crelanu, Corpsegrinder (spear, gives Eviscreation), Morrigans Slasher (axe, gives murderlust)

He is the one, who stands in front line, he is the most usefull healer I have. He can kill almost every unit in one round (thanks to mask of insanity), he cant be affected by temptation, he weakens strong leaders with doom attack.

Of course, he could be stronger, I was too lazy to try more unit to get Legacy of kings/ sorrow/ dark dragon, so I got just legacy of Titans. Also I dint get the Mace with Hate speech skill.

== Lone warriors ==
Some units are quite good when sent alone behing the enemy lines.

=== Juggernaut of doom ===
An Elvish Juggernaut, doing 57-9 melee (blade, slow, disintegrate) and 36-9 ranged (pierce, marksman, slow) or 26-6 ranged (arcane, slow, drain, focused -- useful to drain hitpoints when regenerating is not enough).

Equipped with Doombringer sword, and Stormforce bow, and protected by a Prayer armour, a Gloomy Cloak, a Gloomy Amulet, a Gloomy Ring, Mighty Gauntlets, Elusive Boots and the Dark Helm of Destruction.

A full Dark Dragon Legacy, four AMLA for bow, two AMLA for sword, five AMLA to reduce chance to be hit by 10% and a few AMLA to increase physical resistances.

=== Icy Dragon Rider of Wrath ===
A Dragon Rider mainly doing 75-4 wrath (5) melee (ice, charge, slow, horrid, backstab) or 26-6 ranged (ice, slow, cone) and defensively 39-4 melee with drain and slow.

Equipped with a Holy Sword and a Return to the Tribe spear, and protected by a Horrid Ice Armour, a Ring of Iced Veins, Slow Boots, Draingloves, a Mask of Famine, a Leechward amulet and a Cloak of the Assassin Leader.

A full Ice Dragon Legacy, a full Raging/Wrathful Combat Techniques, five AMLA to command the dragon to bite better (and to eat in the process), five AMLA to have a tougher dragon.

=== Assassin of Everything ===
dabber's deadliest lone unit.
Elvish Assassin. Legacy of Sorrow, Dark set 
Melee 33-8 blade, struggle, slows, poison, suck 5 
Ranged 33-11, blade, focused, mind raid, struggle, slows, poison, suck 7 
Resistances 37,37,18,30,25,40

No unit in my army, including Efraim and Lethalia, has anywhere near the experience of this lady. I let her solo several levels of Inferno for fun.

Critical Equipment: 
Dark Sword, Dark Helm, Dark Gloves, Unprecious Ring, Intoxicator boots 

Other Current Equipment: 
Mystic Armour of the Untouchable, Bow of Plagiarism, Gloomy Cloak, Amulet of Reason, Fencer's Study

Why is she great: 
* Conviction means she does serious damage to any target.
* Focussed on ranged attacks ensures they hit, and therefore suck.
* High suck with many attacks, plus despair, slow, and struggle means she avoids or heals most any damage.
* If she ever gets hurt, she can use Distant Attack to heal.

=== Deadly Champion ===

Favorite of arobinson, the Champion's power is in the opponent missing, not in the offensive power of the unit. The idea is to make the Champion very hard to hit and then use Anger to increase the number of attacks. The more attacks the opponent has the better in this case. Because of the Champion's chance to be hit ratio, a few equipment items means that it almost cannot be hit. The unit is not all that good for spell defense, so it is not quite a loner, but it is very powerful on offense against any opponent.

There are many options for armor and weapons, but basically you want to try to (1) maximize the number of attacks and (2) decrease the chance to hit.

Recommended Equipment: 
* Crafted "Anger" sword or "Marrowrend" (*2 attacks offense and defense, this is key)
* Helmet
** Helmet of Paladins (for the illumination)
** Mask of Insanity (not necessary, but good for really hard units)
** Rherraent's Helm
* Gloves
** Quick Gauntlets (+1 attack)
** Draingloves
** Dark Gloves of Destruction
* Book of Courage (if not using the Helmet of Paladins)
* Dazzling Ring
* Amulets
** The gloomy Amulet
** Lucky Farmer's Amulet
** Amulet of the Last Guide
* Armor
** Mystic Armour of the Untouchable
** Dark Sarcasm
** Redshirt Armour
* Crossbow
** Crafted Gloombringer crossbow
** Crafted Malice crossbow
** Crafted Deathblade Inheritance crossbow
* Boots
** Elusive Boots
** Slow Boots of Certainty
* Cloak of the Assassin leader
* Other crafted
** Lightning Agility
** Deflector of Light

Advancements: 
Focus on the sword (number of attacks), then "better at defending" (up to -15% chance to be hit) and then the "better resistances when defending" advancements to improve the unit's defense against magical attacks while defending.

=== Devastating Demilich of Doom ===

With maxed out resistances, good healing and tons of penetration, this unit can sometimes kill healthy units even while slowed, and is nearly impossible to kill.

* Weapons
** Soul Hunter (nostalgia)
** Misanthropia (nostalgia)
** Another Misanthropia (nostalgia)
** A third Misanthropia (otherworldly essence)
** The Killer of Great Magi (staff)
* Armor
** Crapsack World (amulet)
** Fiery Blood (gauntlets)
** Wisdom of the Ages (helm)
** The Godless (armor)
** Search for Wisdom (boots)
** Exterminator's Ring
** Tracking the Lost Knowledge (cloak)
* Tomes
** Book of Herbal Tinctures and Malignancies

That gives you 21-8 melee with drain and 31-6 ranged with slows, spell suck 3 and 70% cold penetration, and all resistances except impact maxed out. Regen +13 and absorb 1 really seals the deal. If you want to fish for legacies, Legacy of the Frozen North, Legacy of Sorrow and Legacy of the Free are all fine choices.

There's a bit of leeway with gear here too. Lucky Farmer's Amulet is fine with the rest of the list, and The Touch of God might be an improvement over Tracking the Lost Knowledge. Fire Dragon Legacy and Wrathful Combat Techniques or Guide to Lycanthropy is also worth considering, to make this a boss killer and a lone warrior.

IGNFileFormat

2019-12-21T12:35:35Z

Mathemagician: /* _server.ign does NOT implicitly include the defaults */

__NOTOC__
When you upload an add-on, some files and directories are ignored and not uploaded.

If you would prefer to have more control over which files and directories should be ignored, you should provide a _server.ign file containing a list of filter patterns. Each file or directory matching any entry of the _server.ign file will not be included when uploaded to the add-ons server.

== Where do I put the file, and what goes in it? ==

The file should be placed within the root level of your add-on (data/add-ons/addon_name/_server.ign).

A specific format is required:

* {{DevFeature1.13|0}}: Blank lines and lines beginning with '<code># </code>' (space required) are ignored.
* Each line should contain exactly one pattern.
* <code>*</code> and <code>?</code> wildcards are supported (<code>?</code> stands for any single character, <code>*</code> stands for any number of any characters).
* {{DevFeature1.13|12}}: <code>+</code> wildcards are also supported: it stands for one or more characters.
* Patterns with a trailing forward slash '<code>/</code>' will match directories; the rest only match files.

==== Default values ====

If there is no custom _server.ign file present, a default filter will be used instead, which is as follows:

.+
.+/
__MACOSX/
#*#
*~
*-bak
*.swp
*.pbl
*.ign
_info.cfg
*.exe
*.bat
*.cmd
*.com
*.scr
*.sh
*.js
*.vbs
*.o
*.ini {{DevFeature1.13|12}}
Thumbs.db
*.wesnoth
*.project

If you create a custom _server.ign, you should add these entries to it.

== See Also ==

* [[PblWML]]

[[Category:Create]]

InterfaceActionsWML

2019-12-19T22:51:22Z

Mathemagician: /* Formatting */

{{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). [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''': {{DevFeature1.13|6}} 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 ''' " ''')
* '''male_message''', '''female_message''': {{DevFeature1.13|2}} (translatable) Used instead of ''message'' if the unit's gender matches. Never used if there is no unit (ie ''speaker=narrator''). {{DevFeature1.13|6}} This matches the primary unit, not the secondary unit.
* '''wait_description''': {{DevFeature1.13|2}} the description of this message displayed when other players in a mp game wait for one player doing input in a [message] (with [option]s or [text_input]).
* '''[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. This will not work with messages that take user input ([option]/[text_input]), which can only ever be shown to the current player. {{DevFeature1.13|0}} side_for= is now also accepted for messages with user input, it specifies on which side the message is shown (defaults to the currently playing side). For messages with input it does not accept a comma seperated list only a single number.
* '''image''': (default: profile image of speaker) the image to display to the left of the message text. Append ~RIGHT() if you want the image to appear on the right side.
** {{DevFeature1.13|0}} none: display no image
* '''mirror''': {{DevFeature1.13|5}}whether to mirror the image specified by the '''image''' attribute.
* '''second_image''': {{DevFeature1.13|6}}same as the '''image''' attribute, but the image is displayed on the right of the message text.
* '''second_mirror''': {{DevFeature1.13|6}}same as '''mirror''', but for the '''second_image''' attribute.
* '''image_pos''': {{DevFeature1.13|5}} whether to show the image on the left or right; supercedes the use of ~RIGHT() described above
* '''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''.
* '''highlight''': {{DevFeature1.13|5}} Boolean specifying whether to highlight the speaker. Defaults to ''yes''.
* '''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.
* '''voice''': {{DevFeature1.13|?}} a sound to be played as the message is displayed. This can also be a comma-separated list, from which one will be randomly chosen. This is intended for voiceovers for the message.
* '''[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. ''Note: Messages with options will not be shown at all in prestart events''
** '''message''': (translatable) the text displayed for the option. {{DevFeature1.15|1}} This is now a synonym for '''description='''.
** '''image''', '''label''', '''description''', '''default''': See [[DescriptionWML#WML_Format|DescriptionWML]].
** '''value''': {{DevFeature1.13|?}} Gives the option a value to be stored in a variable.
** '''[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.
* '''variable''': {{DevFeature1.13|?}} If present, either the index or the value of the chosen option will be stored in the specified variable. Option indexing starts from 1. If option has '''[show_if]''' condition evaluated as false, then it is hidden and excluded from the indexing.
* '''[text_input]''': there can be only one [text_input] tag. this adds a text input field to the message. ''Note: Messages with text_input will not be shown at all in prestart events''
** '''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 ===
'''[message]''' and other tags such as unit names (user_description), objectives, and floating text can make use of [https://developer.gnome.org/pango/stable/pango-Markup.html Pango markup formatting codes].

Remember to use single quotes (') instead of double quotes (") within the formatting string, as double quotes cannot be escaped, and the string will appear fragmented and possibly cause errors. Escaping markup is described in https://github.com/wesnoth/wesnoth/blob/master/src/font/pango/escape.hpp#L35-L39.

For example, if you wanted to write "You are victorious!" in large, italic, gold letters, you might write it this way:

<nowiki>You are victorious!</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'.

The following pango attributes are also available directly as attributes of the '''[message]''' tag:
{{DevFeature1.13|4}}

*'''font'''
*'''font_family'''
*'''font_size'''
*'''font_style'''
*'''font_weight'''
*'''font_variant'''
*'''font_stretch'''
*'''color'''
*'''bgcolor'''
*'''underline'''
*'''underline_color'''
*'''rise'''
*'''strikethrough'''
*'''strikethrough_color'''
*'''fallback'''
*'''letter_spacing'''
*'''gravity'''
*'''gravity_hint'''

== [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]]''' 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. Can be set to "" too.
* '''defeat_string''': Default ' _ "Defeat:"', this text precedes the defeat objectives. Can be set to "" too.
* '''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.
* '''delayed_variable_substitution''': {{DevFeature1.13|8}} If set to yes, any variables or [insert_tag] are not substituted right away. Instead, they are substituted whenever the objectives are actually viewed.

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.
** '''caption''': a text which will be displayed above the ''description''. This can be used to display a subcategory of objectives below ''victory_string'' or ''defeat_string''.
** '''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, or when manually opening the scenario objectives.
* '''[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.
** '''[show_if]''': {{DevFeature1.13|11}} Gold carryover will not be shown if the specified condition isn't met. Conditional gold carryover is refreshed at '''[show_objectives]''' time only.
* '''[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.
** '''[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 menu items can be set and modified during any event, for example during "start" or "prestart" events. The user can also assign hotkeys to these WML commands unless specified otherwise. When the hotkey is pressed the event will 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. {{DevFeature1.13|0}} This limitation is being removed in a [http://forums.wesnoth.org/viewtopic.php?p=572554#p572554 future version] of Wesnoth.

* '''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. {{DevFeature1.13|6}} ''needs_select=yes'' is deprecated, consider using manual variable syncing with [sync_variable].
* '''synced''' {{DevFeature1.13|1}}: if ''no'' (default ''yes'') the command handler will only be run on the client that invoked the menu item; this means that changing the gamestate in a command handler of a menu item with ''synced=no'' will cause OOS
* '''use_hotkey''': 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]''': 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.
** '''repeat_on_hold''' {{DevFeature1.13|12}}: if ''yes'' (default ''no''), holding the hotkey will repeat the action continuously, unless it blocks input with something like '''[message]'''. Due to a bug, versions older than 1.13.12 always repeat the action, with no way to disable it.
* '''[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 ''' (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] ==

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:

=== [change_theme] ===

{{DevFeature1.13|8}}

Change the current interface theme.

* '''theme''': The ID of the new theme. Use <code>theme=</code> (empty key) to switch back to the theme that the player has selected in Preferences. On 1.14.2 and later it is also possible to omit the key entirely to achieve the same effect (on previous versions this will crash the Lua engine).

=== [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 [[ImagePathFunctions#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 (https://github.com/wesnoth/wesnoth/issues/1219).
* '''name''' an id that can be used to remove the item.
''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. {{DevFeature1.15|0}} In 1.14 the '''[side]team_name''' attribute was expected to be a substring of this '''team_name'''. In 1.15 both are expected to be comma-separated lists of names and the item is visible if the lists intersect. ([[https://github.com/wesnoth/wesnoth/pull/3533|#3533]])
* '''visible_in_fog''': whether the item should be visible through fog or not. Default yes.
* '''redraw''': (boolean yes|no, default: yes): If no, disables implicit calls to [[InterfaceActionsWML#.5Bredraw.5D|[redraw]]] when placing the items.
* '''[filter_team]''': {{DevFeature1.15|0}} A [[StandardSideFilter]]. Set '''team_name''' to the union of all '''[side]team_name''' attributes of all sides that match the SSF. ([[https://github.com/wesnoth/wesnoth/pull/3533|#3533]])
* {{DevFeature1.15|0}} If both '''team_name''' and '''[filter_team]''' are set, '''team_name''' is ignored.

=== [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 [[ImagePathFunctions|image path functions]] appended to the original image name.)
* '''name''': removes an item with a previously defined 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. {{DevFeature1.13|x}} Use of red, green, blue is now deprecated; use color=0,0,0 instead.

=== [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''': [[ImagePathFunctions|image path functions]] sequence to be applied on the fake unit.
* '''force_scroll''': 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.
* '''force_scroll''': {{DevFeature1.15|0}} Has the same meaning as in [move_unit_fake] but a different default.
* '''[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] ===
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.

{{DevFeature1.13|8}} This now also blocks the player from zooming the gamemap view. WML or Lua zoom will continue to work normally.

=== [unlock_view] ===
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
* '''side''': the side or sides for which this should happen. By default, the [scroll] happens for everyone.
* '''[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
* [[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 ''yes'' (don't scroll to fog) and ''no'' (scroll even to fog), with ''no'' as the default.
* '''immediate''': whether to instantly warp to the target hex regardless of the scroll speed setting in Preferences (defaults to ''no'').
* '''highlight''': {{DevFeature1.13|5}} Whether to highlight the hex being scrolled to (defaults to ''no'').
* '''side''': the side or sides for which this should happen. By default, the [scroll_to] happens for everyone.
* '''[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 ''yes'' (don't scroll to fog) and ''no'' (scroll even to fog), with ''no'' as the default.
* '''immediate''': whether to instantly warp to the target hex regardless of the scroll speed setting in Preferences (defaults to ''no'').
* '''highlight''': {{DevFeature1.13|5}} Whether to highlight the hex the unit is on (defaults to ''no'').
* '''for_side''': the side or sides for which this should happen. By default, the [scroll_to_unit] happens for everyone.
* '''[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). This can be a comma-separated list, from which one sound will be chosen randomly.
* '''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 ''yes'' and ''no'' - ''yes'' means the source will not play if its locations are fogged
* '''check_shrouded''': possible values ''yes'' and ''no'' - ''yes'' means 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)

=== [story] ===
{{DevFeature1.13|8}}

Shows the story screen.
* '''title''': Default title used if a part does not specify one — unlike the intro storyscreen, the scenario name is not used as a default title.
* '''[part]''': As [[IntroWML]].

=== [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
* '''accelerate ''' (boolean yes|no, default no): {{DevFeature1.13|0}} whether the delay is affected by acceleration. When [delay] is used to make an animation, this should be set to yes so that your animation matches the ones generated by the game.

=== [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
Using remove_object is also possible, see https://github.com/wesnoth/wesnoth/commit/26c2f941f2bcdd89528481e114c0375ad2a46271

=== [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
* '''male_text''', '''female_text''': {{DevFeature1.13|2}} (translatable) gender-specific versions of the above
* '''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. {{DevFeature1.13|1}} (only for [event][label]: full [[StandardLocationFilter|SLF]] support)
* '''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.
* '''category''': the Show/Hide Labels dialog allows showing/hiding all labels of a given category by toggling a checkbox.
* '''tooltip''': A tooltip visible when mouseovering the hex the label is on
* '''side''': the number of the side that placed the label. Can be 0 for labels placed by WML.

=== [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 '''#6b8cff'''. 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="" + _ "Your text here" + ""
[/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.
* '''level''': {{DevFeature1.13|10}} The deprecation level, a number from 1 to 3.
* '''what''': {{DevFeature1.13|10}} The name of the thing being deprecated. Use this instead of '''message''' if possible; a stock message will be generated from it. Use '''message''' only if more information is required; it will be appended to the stock message. This should not be translatable
* '''version''': {{DevFeature1.13|10}} For deprecation levels 2 and 3, this indicates the version in which the feature could be removed. It does ''not'' indicate the version in which it became deprecated.

The meanings of the deprecation levels are as follows:

# Deprecated, but will only be removed if absolutely necessary. The '''version''' key is ignored.
# It will be removed no earlier than a specified version.
# It will be removed in the next stable version
# It has already been removed, leaving just a stub to inform users of how to update their code.

Note that as of 1.13.11, deprecation messages show only in the log, not in the chat message area. The '''message''' can be translatable, but does not need to be.

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

=== [test_condition] ===

{{DevFeature1.13|2}}

Evaluates the contained conditional tags. If they evaluate to the expected value, it prints out a message to the console explaining which part of the condition caused this result in a way similar to [wml_message]. This can be used if your conditional test is failing and you're not sure why.

* '''result''': Whether you expect the conditions to fail or succeed. If no (the default), a message will be printed if the conditional tags fail. If yes, a message will instead be printed if the conditional tags pass.
* '''logger''': Same as for [wml_message]. Defaults to "warning".

=== [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]]''' 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, not visible for observers. Alternative unconditionally visible for everyone: [[LuaWML:Display#wesnoth.message]]. {{DevFeature1.13|9}} can be visible for observers.
* '''speaker''': (default="WML") A string for the name of the sender of the message.
* '''message''': The message that should be displayed.
* '''observable''' (boolean yes|no, default yes): {{DevFeature1.13|9}} Whether the message is displayed for observers.
* '''[[StandardSideFilter]]''' tags and keys as argument; if the same client controls multiple sides that match, then the message will only be displayed once.

=== [zoom] ===

{{DevFeature1.13|8}}

Changes the zoom level of the map.

* '''factor''': The new zoom factor
* '''relative''': If yes, zoom relative to current zoom level. Otherwise, set the absolute zoom level. Default no.

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

Wesnoth AI

2019-12-19T01:33:39Z

Mathemagician: /* Available AI Tools */

==Introduction to the Wesnoth AIs==

Wesnoth provides an artificial intelligence (AI) which is active by default for all computer-controlled sides, as well as several optional AIs. These AIs are highly configurable and can be included and/or customized by scenario and map creators using simple WML code. For AI developers, it is also possible to replace parts or all of the default AI with custom code.

This page provides a brief summary of the available AIs and of the methods, tools and resources available for using and modifying them. Links are provided to detailed documentation on each of the topics. For reference, we also provide a brief timeline describing some of the main development milestones of the Wesnoth AIs.

== Available AIs ==

This section briefly lists the different AIs available in Wesnoth. Click on the links provided here and in the resources section below for detailed descriptions of the AIs and for instructions for using and customizing them.

=== AIs Available to Scenario and Map Designers ===

Wesnoth comes with several built-in AIs from which scenario and map designers can choose:

* '''[[RCA_AI|Default (RCA) AI]]''': If no special instructions are given, this AI is used automatically for all computer-controlled sides with no setup needed. It can be customized in many different ways.
* The '''[[Experimental AI]]''' adds additional features to the RCA AI. {{DevFeature1.15|3}} Most of the actions of the Experimental AI have been merged into the default AI. The Experimental AI is therefore currently only available in debug mode in the MP computer player selection menu, as it is almost the same as the default AI. This may change in the future if new features are added.
* '''[[Micro AIs]]''' add specialized behavior to Wesnoth that cannot be achieved with the default AI. There is a large number of available Micro AIs and they can be set up using just a few lines of simple WML code.
* '''[[Creating Custom AIs|Custom AIs]]''': In addition to these AIs, Wesnoth provides a large variety of options for writing your own AI code.

=== AIs Available in the Multiplayer Setup Menu ===

Several AIs are available to be chosen for computer players in the multiplayer setup menu:

* '''[[RCA_AI|Default AI (RCA)]]''': This is the same AI as listed above.
* '''[[Experimental_AI]]''': Again, the same AI as described above.
* Debug Mode '''Dev AIs''': If Wesnoth is in debug mode, several additional AIs are available in the menu. For the most part, these are not meant as complete stand-alone AIs, or as AIs that are significantly different from the default AI, but rather as examples that can be used for development purposes. {{DevFeature1.13|5}} The list of AIs has been cleaned up. Only working and (somewhat) meaningful AIs remain.
* '''[[Creating Custom AIs|Custom AIs]]''': Just as it is possible to include custom AIs in the scenario code, they can also be provided for selection from the MP setup menu. These can be written either for specific scenarios/maps or so that they are available for all maps.

== Available AI Tools ==

The default AI is written in C++ and therefore difficult to modify directly. However, it is a [[Wesnoth_AI_Framework#Wesnoth_AI_Framework:_A_Composite_AI|composite AI]] assembled from individual components which can be customized and modified in both WML and [[LuaWML|Lua]]. Documentation on the available AI tools can be found at:

* [[AiWML]]: Customizing the default AI using WML
* [[Modifying AI Components]]: More complex customization tasks and mid-scenario changes
* [[Wesnoth AI Framework]]: Description of Wesnoth's composite AI configuration
* [[Creating Custom AIs]]: Instructions for writing your own AI components
* [[LuaAI|Lua AI]]: Recommended method for writing custom AIs

'''Notes:'''
* Wesnoth has its own internal language called 'Formula' which can also be used for AI development. It is, however, not maintained any more and has by now been surpassed by Lua in ease of use in most cases. We therefore do not recommend using it any more, but links to the legacy documentation are still provided in the resources section below.
* A Python API for AI development also existed for a while. It was removed for security reasons.

== List of Wesnoth AI Resources ==

===AI Resources for Scenario and Map Creators===

* [[RCA AI]]: Description of Wesnoth's default AI, with the following additional documentation:
** [[AiWML]]: Customizing the default AI using WML
** [[AI Recruitment]]: Customizing the recruitment of the default AI
** [[Modifying AI Components]]: Instructions for some of the more complex customization tasks
* [[Experimental AI]]: Experimental augmented version of the default AI with additional features
* [[Micro AIs]]: Additional specialized AI behavior that cannot be achieved with the default AI

===Resources for AI Coders===

* [[Wesnoth AI Framework]]: General principles of the inner workings of the Wesnoth AI mechanism
* [[Creating Custom AIs]]: Instructions for doing just that
* [[LuaAI|Lua AI]]: Recommended method for writing custom AIs

==== Legacy Resources for AI Coders====

* [[Lua AI Legacy Methods Howto]]: Old methods for writing custom AIs using Lua AI
* [[FormulaAI|Formula AI]]: Another language for writing custom AIs

===Miscellaneous Other Resources===

The following resources are not generally needed for understanding, using and modifying Wesnoth AIs, but they might nevertheless contain some useful bits of information for the interested reader.

* [[AI Arena]]
* [[Machine Learning Recruiter]]
* [[WhyWritingAWesnothAIIsHard|Why Writing A Wesnoth AI Is Hard]]
* [[WritingYourOwnAI|Writing Your Own AI]]

Finally, the link to the AI Category at the bottom of this page includes links to all the remaining AI-related pages.

==A Very Brief History of Wesnoth AIs==

While the general principle of the Wesnoth AI has been relatively stable throughout its development, the AI implementation has seen dramatic changes. That said, basic scenario creator tasks such as [[AiWML|modifying AI parameters in WML]] are usually not changed much in order to keep backward compatibility. On the other hand, the steps needed to write, for example, [[Creating_Custom_AIs#Creating_Custom_Candidate_Actions|custom candidate actions]] and bind them into the existing AI framework have definitely evolved significantly from Wesnoth 1.8 to 1.10 to 1.12.

It is not possible to capture all these changes on the Wesnoth AI wiki pages due to the complexity of the topic. They generally only refer to the latest stable release series and the current development release series. If, for some reason, you need to do AI work with an earlier version of Wesnoth, we still provide some of the legacy documentation, but you might also have to check out the history of the wiki pages. Another way to go about it is by checking out examples of how things are done in mainline or add-ons of the respective release series. In general, however, we ''strongly'' recommend using the latest Wesnoth versions, as modifying AI behavior has become ''a lot'' simpler than it used to be.

For reference, here is a list of some of the major milestones of the AI development:

* Up to '''Wesnoth 1.6''':
** The default AI of Wesnoth is, in fact, called ''Default AI'', with <code>id=default_ai</code> in the configuration.
* '''Wesnoth 1.1/1.2''':
** A Python API for AI development is introduced. This was later removed for security reasons.
* '''Wesnoth 1.5/1.6''':
** [[FormulaAI|Formula AI]] is introduced.
* '''Wesnoth 1.7/1.8''':
** [[Wesnoth_AI_Framework|Composite AI framework]] is introduced, with the default AI functionality ported to this framework in the form of the [[RCA AI]].
** The [[RCA AI]] becomes the default.
** [[LuaAI|Lua AI]] is introduced.
* '''Wesnoth 1.11/1.12''':
** Introduction of the [[Micro AIs]]
** External Lua candidate actions become fully usable. They are now the recommended method for [[Creating_Custom_AIs|creating custom AIs]]
* '''Wesnoth 1.15/1.16''':
** Merging of most of the previous [[Experimental_AI]] candidate actions into the [[RCA AI]]

[[Category:AI]]

MultiplayerContent

2009-01-16T23:54:43Z

Mathemagician: Merged two sections, changed header levels

'''Multiplayer campaigns are working again in versions 1.3.5+''', they are broken in both stable and development versions of Wesnoth prior to 1.x.5. Check the [http://www.wesnoth.org/forum/viewtopic.php?t=11349 forums] for more information.

= Building multiplayer campaigns =

Both the stable and development versions of wesnoth have basic support for campaigns that can be played in multiplayer mode, with your friends, or even with an AI. There will still be some things that don't work as expected as multiplayer campaigns are an area for exploration. While you can and should test your work in hotseat mode, there are a number of things that might behave differently under real network conditions (mostly affecting scenario and side parameters). Keep this in mind and make sure to test your campaign over the net, too.
This page only documents the differences between writing multiplayer campaigns and single player campaigns, so you might want to read up on [[BuildingCampaigns]] and [[BuildingMultiplayer]] first.

== The campaign file ==

Multiplayer campaigns do not use the [campaign] tag. As a result of this, multiplayer campaigns only support one difficulty level, though you could support more with enough WML, if you're feeling ambitious. The "campaign file" should look something like this:

#ifdef MULTIPLAYER
{@campaigns/My_Campaign/scenarios}

#Only needed if you have custom units
[+units]
{@campaigns/My_Campaign/units}
[/units]
#endif

Anything that you would normally put in the campaign tag now goes into the first scenario, if it's supported there. The order of scenarios is determined by next_scenario tags, just like in single player.

== Scenarios ==

A scenario in a multiplayer campaign is almost identical to a scenario in a single player campaign. You only need to change the following:

* The [scenario] tag should be replaced with a [multiplayer] tag.
* The '''next_scenario''' key points to the id of the next scenario.
* Every scenario after the first should have '''allow_new_game=no''' inside the [multiplayer] tag. This will prevent it from showing up in the map selection menu.
* Each human-controlled side needs to have a '''controller=human''' key defined in their [side] tag to work in network mode.
* Each human-controlled side also needs to have a '''save_id''' defined inside their [side] tag. Each side's save_id should be unique, and it should be the same in every scenario. Without this, your recall lists and leaders will not carry over from one scenario to the next.
* Each human-controlled side has to have a leader '''type=''' definition in every scenario except the first one . It doesn't matter which type you choose cause the type set here gets replaced by the actual leader in the recall list.
* Each AI-controlled side should have '''allow_player=no''' in their [side] tag.
* The [story] tag will only display for the first player (or maybe it's the host player). You'll have to use [message] tags in the start event if you want everyone to read the story.
* If you have a file containing macros, it must be referenced by every scenario, since there is no proper campaign file to include it from.

== The first scenario ==

The first scenario might need some extra work, because the settings from the multiplayer dialog will override the settings in the scenario. However, most of the multiplayer settings can be overridden in the prestart event.

Use a macro like this to force a side to have a particular type of leader.
#define MP_SIDE SIDENO TYPE DESC
[store_unit]
variable=oldunit
kill=yes
[filter]
side={SIDENO}
[/filter]
[/store_unit]

[unit]
type={TYPE}
description={DESC}
unrenameable=yes
side={SIDENO}
x,y=$oldunit.x,$oldunit.y
canrecruit=yes
[/unit]

[clear_variable]
name=oldunit
[/clear_variable]
#enddef

Other useful tags include [set_recruit], [modify_side], [modify_turns] and [remove_shroud]. There is currently no way to remove fog. You might also want to use ''experience_modifier=100'' in the [multiplayer] tag.

== See Also ==

* [http://www.wesnoth.org/forum/viewtopic.php?t=11349 Multiplayer Campaigns HOWTO forum post]
* [[BuildingScenarios]]
* [[BuildingMultiplayer]]

[[Category:Create]]

BuildingCampaignsTheCampaignFile

2009-01-15T03:19:02Z

Mathemagician: Typo fix

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

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

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

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

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

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

[campaign]

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

The next group of lines uniquely identifies the campaign:

name= _ "A Simple Campaign"
abbrev=ASC
define=CAMPAIGN_SIMPLE_CAMPAIGN

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

''name'' is the name of your campaign that the user will see. It must be in quotation marks and be preceded by an underscore to facilitate translation.
''abbrev'' defines a campaign abbreviation that will be used as a prefix for the names of save files from that campaign (in 1.3.12 and later). ''define'' creates a key that lets the game know when a user has selected to play a scenario from your campaign. More on it in a bit. If you are missing the ''name'' or ''define'' keys of these your campaign will not work correctly; ''abbrev'' is optional but recommended.

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

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

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

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

''difficulties'' creates three definitions for three different difficulty levels. For more information on difficulty levels and balancing see [[http://catb.org/~esr/wesnoth/campaign-design-howto.html Campaign Design HOWTO]].

first_scenario=the_first_scenario

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

[/campaign]

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

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

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

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

#ifdef CAMPAIGN_SIMPLE_CAMPAIGN

{@campaigns/simple_campaign/scenarios}

#endif

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

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

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

== See Also ==

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

[[Category:Create]]

MultiplayerContent

2009-01-15T02:12:34Z

Mathemagician: Fixed out of date info.

'''Multiplayer campaigns are working again in versions 1.3.5+''', they are broken in both stable and development versions of Wesnoth prior to 1.x.5. Check the [http://www.wesnoth.org/forum/viewtopic.php?t=11349 forums] for more information.

== Building multiplayer campaigns ==

Both the stable and development versions of wesnoth have basic support for campaigns that can be played in multiplayer mode, with your friends, or even with an AI. There will still be some things that don't work as expected as multiplayer campaigns are an area for exploration. While you can and should test your work in hotseat mode, there are a number of things that might behave differently under real network conditions (mostly affecting scenario and side parameters). Keep this in mind and make sure to test your campaign over the net, too.
This page only documents the differences between writing multiplayer campaigns and single player campaigns, so you might want to read up on [[BuildingCampaigns]] and [[BuildingMultiplayer]] first.

=== The campaign file ===

Multiplayer campaigns do not use the [campaign] tag. As a result of this, multiplayer campaigns only support one difficulty level, though you could support more with enough WML, if you're feeling ambitious. The "campaign file" should look something like this:

#ifdef MULTIPLAYER
{@campaigns/My_Campaign/scenarios}
#endif

Anything that you would normally put in the campaign tag now goes into the first scenario, if it's supported there. The order of scenarios is determined by next_scenario tags, just like in single player.

=== Scenarios ===

A scenario in a multiplayer campaign is almost identical to a scenario in a single player campaign. You only need to change the following:

* The [scenario] tag should be replaced with a [multiplayer] tag.
* The '''next_scenario''' key points to the id of the next scenario.
* Every scenario after the first should have '''allow_new_game=no''' inside the [multiplayer] tag. This will prevent it from showing up in the map selection menu.
* Each human-controlled side needs to have a '''controller=human''' key defined in their [side] tag to work in network mode.
* Each human-controlled side also needs to have a '''save_id''' defined inside their [side] tag. Each side's save_id should be unique, and it should be the same in every scenario. Without this, your recall lists and leaders will not carry over from one scenario to the next.
* Each human-controlled side has to have a leader '''type=''' definition in every scenario except the first one . It doesn't matter which type you choose cause the type set here gets replaced by the actual leader in the recall list.
* Each AI-controlled side should have '''allow_player=no''' in their [side] tag.
* The [story] tag will only display for the first player (or maybe it's the host player). You'll have to use [message] tags in the start event if you want everyone to read the story.
* If you have a file containing macros, it must be referenced by every scenario, since there is no proper campaign file to include it from.

=== The first scenario ===

The first scenario might need some extra work, because the settings from the multiplayer dialog will override the settings in the scenario. However, most of the multiplayer settings can be overridden in the prestart event.

Use a macro like this to force a side to have a particular type of leader.
#define MP_SIDE SIDENO TYPE DESC
[store_unit]
variable=oldunit
kill=yes
[filter]
side={SIDENO}
[/filter]
[/store_unit]

[unit]
type={TYPE}
description={DESC}
unrenameable=yes
side={SIDENO}
x,y=$oldunit.x,$oldunit.y
canrecruit=yes
[/unit]

[clear_variable]
name=oldunit
[/clear_variable]
#enddef

Other useful tags include [set_recruit], [modify_side], [modify_turns] and [remove_shroud]. There is currently no way to remove fog. You might also want to use ''experience_modifier=100'' in the [multiplayer] tag.

=== Custom units ===

If you have any custom units, you can include them from the campaign file. It will look something like this:

#ifdef MULTIPLAYER
{@campaigns/My_Campaign/scenarios}

[+units]
{@campaigns/My_Campaign/units}
[/units]
#endif

== See Also ==

* [http://www.wesnoth.org/forum/viewtopic.php?t=11349 Multiplayer Campaigns HOWTO forum post]
* [[BuildingScenarios]]
* [[BuildingMultiplayer]]

[[Category:Create]]