#textdomain wesnoth-help [help] [toplevel] sections=introduction,gameplay,units,abilities_section,traits_section,weapon_specials,eras_section,terrains_section,schedule,addons,editor,commands,encyclopedia topics=license [/toplevel] [section] id=schedule title= _ "Time of Day Schedule" generator=time_of_days sort_topics=generated [/section] [section] id=introduction title= _ "Introduction" topics=..introduction,about_game [/section] [section] id=gameplay title= _ "Gameplay" topics=..gameplay,victory_and_defeat,recruit_and_recall,income_and_upkeep,hitpoints,advancement,movement,vision,shroud_and_fog,combat,damage_types_and_resistance,orbs,crowns,time_of_day,healing,saveload,whylost,wrap_up [/section] [section] id=traits_section title= _ "Traits" topics=..traits_section generator=traits sort_topics=generated [/section] [section] id=units title= _ "Units" sections_generator=races sort_topics=yes sort_sections=yes topics=..units,.unknown_unit [/section] [section] id=abilities_section title= _ "Abilities" topics=..abilities_section generator=abilities sort_topics=generated [/section] [section] id=weapon_specials title= _ "Weapon Specials" topics=..weapon_specials generator=weapon_specials sort_topics=generated [/section] [section] id=eras_section title= _ "Eras" sections_generator=eras sort_topics=yes topics=..eras_section [/section] [section] id=terrains_section title= _ "Terrains" sections_generator=terrains topics=..terrains_section sort_topics=generated [/section] [section] id=addons title= _ "Add-ons" topics=..addons,using_addons,installing_addons,removing_addons [/section] [section] id=commands title= _ "Commands" topics=..commands,general_commands,mp_commands,debug_commands [/section] {core/editor/help.cfg} {core/encyclopedia} # wmllint: markcheck off [topic] id=..introduction title= _ "Introduction" text="src=misc/logo-bg.png~BLIT(misc/logo.png) align=middle" + _ "
text='Battle for Wesnoth' is a turn-based fantasy strategy game somewhat unusual among modern strategy games. While other games strive for complexity, text='Battle for Wesnoth' strives for simplicity of both rules and gameplay. This does not make the game simple, however — from these simple rules arises a wealth of strategy, making the game easy to learn but a challenge to master. The following pages outline all you need to know to play Wesnoth. As you play, new information is added to the various categories as you come across new aspects of the game. For more detailed information on special situations and exceptions, follow the included links." [/topic] # wmllint: markcheck on [topic] id=about_game title= _ "About the Game" text= _ "The game takes place on a hex-based game field, where your units battle against those controlled by the computer, friends who each take turns on the same computer (hotseat play), other players on the same network, or players worldwide in multiplayer mode. Each of these battles is called a text='scenario', which can be strung together to make text='campaigns'. Besides the campaigns that ship with the game, Wesnoth supports user-made content, and the add-on server boasts hundreds of custom maps, campaigns, eras, factions, and resources. The game also features a human-readable markup called Wesnoth Markup Language (WML) to easily allow users to create their own content, as well as a fully-featured Map and Scenario Editor for designing your own battlefields. The text='Battle for Wesnoth' project was begun in 2003, and has been worked on by a multitude of volunteers ever since." [/topic] [topic] id=..units title= _ "Units" text= _ "This section will list all the units you discover as you explore the world of Wesnoth. When you see a new unit during a campaign or multiplayer scenario it will be added to its race’s subsection; you can then view its page any time you wish. A unit’s page will provide a general description, its statistics, attacks, resistances, and movement and defense values. " generator="contents:generated" [/topic] [topic] id=..eras_section title= _ "Eras" text= _ "A faction is a collection of units and leaders. Factions are assigned to sides in multiplayer games. " + _ "An era is a collection of factions, intended to be played against one another. Besides the mainline eras that come with the game, many user-made factions are available from add-ons. " generator="contents:generated" [/topic] [topic] id=..abilities_section title= _ "Abilities" text= _ "Certain units have abilities that either directly affect other units or have an impact on how the unit interacts with other units. These abilities will be listed under this section as you encounter them. Each page will provide a description of what the ability does and which (currently discovered) units have it. " generator="contents:generated" [/topic] [topic] id=..weapon_specials title= _ "Weapon Specials" text= _ "Some weapons have special features that increase the effectiveness of attacking with them. When you see a new weapon special during a campaign or multiplayer scenario it will be added to this list; you can then view its page any time you wish. Each page will provide a description of what the weapon special does and which (currently discovered) units have it. " generator="contents:generated" [/topic] # wmllint: markcheck off [topic] id=.unknown_unit title= _ "Unknown Unit" text="" + _ " This unit is unknown for the moment. You must discover it in the game to be allowed to see its description." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=..gameplay title= _ "Gameplay" text= _ "Wesnoth is comprised of a series of battles, called text='scenarios', that pit your troops against the troops of one or more adversaries. Multiple scenarios that follow on from each other, telling a story, make up text='campaigns'. In a campaign, you often need to play more carefully, preserving your best troops for use again in later scenarios. The interactive text='Tutorial' introduces the basics of Wesnoth gameplay in the context of a scenario. Most material covered in the tutorial is explained more in-depth in these pages, so you can always refer back here if you forget something. After you master the basics, try out a beginner campaign, such as text='Heir to the Throne' or text='The South Guard'. A full list of installed campaigns can be found via the text='Campaign' option on the main menu. As Wesnoth can be quite challenging, you may wish to start on easy before progressing to higher difficulties. Campaigns are grouped by text='level' and text='difficulty'. For example, text='Heir to the Throne' is ‘Novice’ level, and is playable at three difficulties: ‘Beginner’, ‘Normal’, and ‘Challenging’. The level of a campaign indicates what degree of proficiency in the game mechanics (such as dst='movement' text='zones of control' and dst='time_of_day' text='time of day') is assumed. The difficulty indicates how challenging the scenarios will be to a veteran player: at higher difficulties, the obstacles to victory will be higher and overcoming them will require more skillful play. For example, at higher difficulties the enemy may have higher incomes, higher-level units, more castle hexes, and so on." + " src=help/tooltip.png align=right float=yes" + _ "While playing, keep in mind that you can mouse-over many items in the game, such as the information displayed in the status pane, to see a brief description explaining each item. This is especially useful when you encounter new elements, such as dst='..abilities_section' text='abilities', for the first time." + _ "
text='Fundamentals of Gameplay'
" generator="contents:gameplay" [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=victory_and_defeat title= _ "Victory and Defeat" text= _ "Pay careful attention to the text='Objectives' pop-up box at the beginning of each scenario. In most scenarios, you will achieve victory by killing all enemy leaders ; likewise, the death of your own leader generally results in defeat. However, some scenarios may have other victory objectives, such as getting your leader to a designated point, rescuing an ally, solving a puzzle, or holding out against a siege until a certain number of turns have elapsed." + _ " When you win a scenario, the map grays over and the text='End Turn' button changes to text='End Scenario'. You can now do things like changing your save options or (if you are in a multiplayer game) chatting with other players before pressing that button to advance." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=recruit_and_recall title= _ "Recruiting and Recalling" text="src=help/recruit.png align=right float=yes" + _ "Each side begins with one leader in their keep. At the start of any battle, and at times during it, you will need to recruit dst='..units' text='units' into your army. To recruit, you must have your leader (for instance, Konrad in the text='Heir to the Throne' campaign) on the keep hex of a dst='..terrain_castle' text='castle'. Then you may recruit by either choosing text='Recruit' from the menu or right-clicking on a hex and selecting text='Recruit'. This brings up the recruit menu, which lists units available for recruitment, along with their gold cost. Click on a unit to see its statistics, then press the text='Recruit' button to recruit it." + _ " If you right-clicked on a castle hex and selected recruit, the new unit will appear in that hex. Otherwise, it will appear in a free hex near the keep. You may only recruit as many units as you have free hexes in your castle, and you cannot spend more gold than you actually have on recruiting." + _ " Recruited units come with two random dst='..traits_section' text='traits' which modify their statistics." + _ " In later scenarios, you may also Recall survivors from earlier battles. Recalling costs a standard 20 gold and presents you with a list of all surviving units from previous scenarios." + _ " Units not only cost gold to Recruit or Recall, they also require money to support. See dst='income_and_upkeep' text='income and upkeep' for more information." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=income_and_upkeep title= _ "Income and Upkeep" text= _ "In Wesnoth, it is not enough simply to recruit units and fight. You must watch your gold as well, especially in campaigns, where you can carry extra gold over from one scenario to the next. There are two aspects to this; text='income' and text='upkeep'." + _ " Income is simple. You have a base income of 2 gold per turn. For every village you control, you gain one additional gold each turn. Thus, if you have ten villages, you would normally gain 12 gold each turn. Your upkeep costs are subtracted from this income, as detailed below." + " src=help/income-upkeep1.png align=middle box=no
" + _ " Upkeep is also fairly simple. Each unit requires an amount of Upkeep equal to its level. You can support as many levels worth of units as you have villages, without paying any upkeep. However, for each level of unit beyond the number of villages you have, you must pay one gold per turn. For example, if you have twelve level one units and ten villages, you would have to pay two gold each turn in upkeep." + _ " Upkeep costs are subtracted from your income, so in the case of twelve levels of units and ten villages, your resultant Income would be 10 gold per turn." + " src=help/income-upkeep2.png align=middle box=no
" + _ " In general, the base income, the amount of gold you get per village per turn, and the number of unit levels each village can support are configurable, but in campaigns they are almost always the values described above. The text='Scenario Settings' tab of the text='Status Table' dialog shows the values for the current scenario." + _ " There are two important exceptions to upkeep: units with the loyal trait and leaders never incur upkeep. Units you begin the scenario with (such as Delfador), or units who join you during a scenario (such as the horseman in the second scenario of text='Heir to the Throne') will usually have the text='loyal' trait. The unit you are playing (such as Konrad) will almost always be a leader." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=hitpoints title= _ "Hitpoints and Experience" text= "src=help/hpxp.png align=right float=yes" + _ "Each unit has a certain number of text='hitpoints' (HP). If the hitpoints of a unit drop below 1, the unit dies. Each unit also has a certain number of text='experience points' (XP). A freshly recruited unit starts with no experience points, and gains experience by fighting enemies." + " " + _ "The hitpoints and experience points are both indicated in the status pane using two numbers (the current value and the maximum value the unit can have)." + " src=help/hp-bars.png align=right float=yes" + _ "The hitpoints are also indicated by an energy bar next to each unit, which is green, yellow or red. A unit with at least 1 experience point has a blue experience bar, which turns white as the unit is about to dst='advancement' text='advance'." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=advancement title= _ "Advancement" text= _ "If both units survive a combat, they gain a number of experience points equal to the level of the unit they’re fighting. If a unit kills another in combat, however, it gains much more experience — 4 for a level 0 unit, 8 for level 1, 16 for level 2, 24 for level 3, and so forth." + _ " Units have a certain amount of experience required to advance (this is 20% less for units with the Intelligent trait). Once they achieve this amount, they immediately advance to the next level, healing fully in the process. In some cases, you will be given a choice of advancement options." + _ " While most units have three levels, not all do. Occasional units (such as dst='unit_Mage' text='magi') may have four. Once a unit has reached its maximum level, it may have an text='After Maximum Level Advancement' (AMLA) available to it. The AMLA will modify the unit each time the unit reaches the experience goal, but the unit will remain the same level. The typical AMLA effect is for the unit to raise the maximum HP by 3 and full-heal it. The first AMLA will normally be reached with 150 XP gained (120 XP for intelligent units). However, gaining an AMLA becomes progressively harder for each AMLA the unit receives, and so it is usually more useful to try to advance your lower level units." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=movement title= _ "Movement" text="src=help/moving1.png align=right float=yes" + "src=help/moving2.png align=right float=yes" + _ "Movement in text='Battle for Wesnoth' is simple. Click on the unit you wish to move to select it, then click on the hex you wish to move it to. When a unit is selected, everywhere it can move this turn will be highlighted, and all other hexes on the map are made dull. Mousing over a highlighted hex shows the defense rating the unit would have if you moved it to that hex. Mousing over a dull hex will also show the number of turns required to reach it, and clicking will cause the unit to move towards it by the fastest route over this and subsequent turns. If you don’t use up all of a unit’s movement when you first move a unit, you may move it again. This is useful when having two units switch places. Attacking with a unit will use up its movement. Ending a move in a village you don’t already own will also use up a unit’s movement, but will still allow it to attack." + _ " Each unit has a certain number of movement points which are used up when moving into a new hex, depending on the Terrain of that particular hex. For instance, grassland nearly always costs 1 movement point to enter. Exactly how many movement points are spent entering a hex depends on the unit type — in forest, elvish units only spend 1 movement point, most human and orc units spend 2, while horsemen spend 3. You can learn how many movement points a unit requires to enter a certain terrain type by right-clicking on it, selecting text='Unit Description', and then looking at text='Terrain Modifiers'." + _ " Another thing to keep in mind while moving is text='zones of control'. Each unit — except for level 0 units — generates a zone of control in the hexes immediately surrounding it, and any enemy unit entering those hexes immediately ends its movement. Learning how to use zones of control to your advantage is an important part of Wesnoth, as only dst='ability_skirmisherskirmisher' text='skirmishers' can ignore zones of control." + _ " To see where the enemy can move to during their next turn, press Ctrl-v or Cmd-v. Ctrl-b or Cmd-b shows where the enemy could move, if your units were not on the map to block their progress." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=vision title= _ "Vision" text=_ "Vision determines how far a unit can see on the map. Normally, a unit’s vision range is calculated as its movement range plus one hex. Certain units with unique vision capabilities deviate from this rule and have vision cost independent of movement range." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=shroud_and_fog title= _ "Shroud and Fog of War" text= _ "In some scenarios, parts of the map will be hidden from you. There are two mechanisms that can be used separately or together. The text='shroud' hides both the terrain and any units at a location. However, once it is cleared, you can always see that location. The text='fog of war' only hides units and ownership of villages (other than by you or your allies). The fog of war is cleared temporarily when you have units nearby, but returns when they leave. Both the shroud and the fog of war are cleared by units. Each unit clears locations adjacent to those within one turn’s move (ignoring zones of control and enemy units). Normally you can undo a unit’s movement, as long as an event with a randomized result has not occurred, such as combat or recruitment (as most units receive random traits when recruited). Exploring hidden terrain by clearing shroud or fog will also prevent undos to a previous state. You may wish to activate text='Delay Shroud Updates' in the actions menu. This will prevent units from clearing shroud or fog until the next randomized event or a manual update via text='Update Shroud Now' (or the end of your turn) and thereby preserve your ability to undo movement." + " " + _ "
text='Multiplayer and undo'
" + " " + _ "In multiplayer games, moves that have been sent to the network can’t be undone; the game delays sending data to try to preserve your undo ability. When discussing with teammates, remember that the other players are usually looking at a snapshot from the time of the last combat or fog-revealing move. Chat messages and map labels are sent immediately, however they don’t cause the undoable moves to be sent." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=saveload title= _ "Save-loading" text= _ "Random numbers are part of Wesnoth, attacks can fail and units can die due to bad luck — this is an expected part of the game. Going back to a previous turn to try a different strategy is a part of learning the game, but we recommend against reloading merely to try the same strategy again while hoping for better luck." + " " + _ "One of the challenges of the game is to work out how to protect your heroes. Small risks quickly build up: if you have five important units, and they each have just a 1% chance of death each turn, you can text='expect' one of them to die about every 20 turns. So, you’ll rarely make it through a scenario without having it happen." + " " + # po: exceptions to the "rarely any penalty" include plague, and campaign-specific events in UtBS (the cost of new recruits rises during the campaign, which is accelerated by losses during the campaign). _ "Small risks build up for your non-hero units too. While the story and dialogue usually aim to give you some emotional bond with your troops, the game mechanics reward remembering that it’s just a game — there is rarely any penalty for letting these units die, other than being unable to recall them in future scenarios. Your battle plan should distribute the risks based on which troops you want to recall later." + " " + _ "The difficulty levels are balanced assuming that the player won’t save-load. In the mainline campaigns, harder difficulties generally have more enemies and thus more experience points available; this leads to them being balanced assuming that the player will be able to train enough troops to cope with losing some level two or level three units." + " " + _ "That said, it’s a game; the best way to play it is whichever way gives you the most enjoyment." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=whylost title= _ "Learning from Losses" text= _ "text='Why did I lose that scenario?' One of the most difficult parts of Wesnoth is understanding why a scenario was lost." + _ " When you first start playing, you will probably lose some scenarios. That is normal, and is part of learning the game. When that happens, try to learn from your mistakes: watch the replay, try to understand what you did wrong, then dst='saveload' text='restart the scenario' and try again." + _ " Some common reasons for losing a scenario are:" + _ " • Playing a campaign at too high a dst='..gameplay' text='difficulty level'. Try restarting the scenario at an easier difficulty." + _ " • Playing a poor strategy: for example, recruiting the wrong types of units, fighting at the wrong dst='time_of_day' text='time of day', not taking advantage of terrain features or units’ special abilities, and so on." + _ " • Missing clues. Often there will be hints in the campaign’s story and dialog about what to expect from a difficult scenario and how to prepare for it. If you have a loyal mage on your side, take the time to listen to its advice; it may save your life." + _ " • Barely scraping a victory in a previous scenario. Campaigns generally assume that you will have some text='carryover gold' and some experienced units on your text='recall list.' (These concepts are explained in the tutorial.) If you win a scenario but lose most of your experienced units and much of your gold, the following scenario may be very difficult to beat, even for a more experienced player. If you find yourself in this situation, you may try to go back a scenario or two and win them more convincingly, or change to an easier difficulty. (However, remember that text='some' losses are expected, particularly at higher difficulties.)" + _ " • Poor gold management. At higher difficulties, managing gold — capturing villages to increase the income, and using low-level units and fresh recruits to reduce the spending — becomes important. If you use many high-level units, you might win a scenario easily but have not enough gold carryover for the next scenario. (This would be an example of “barely scraping a victory”.)" + _ "
text='Unlikely reasons'
" + _ " In addition to the common reasons, listed above, there are a few other reasons which are unlikely, though not impossible. They are:" + _ " • You may have played a strategy that the campaign developer did not anticipate, and ended up with a set of high-level units not suitable for the next scenario." + _ " • You may have found a scenario that can only be won on the second or third time through, whether by requiring above-average luck or by expecting the players to have foreknowledge — to know what surprises are coming up before they happen. (It is under discussion whether foreknowledge is expected at the highest difficulties. Requiring above-average luck, however, would qualify as a bug.)" + _ " • Unusually-bad luck. Whether an attack hits or misses is random, so it could happen that the enemy was very lucky and had many hits, while you were very unlucky and had many misses. However, this is a very rare occurrence, virtually unheard of in all but the shortest, smallest scenarios. In fact, losses are more commonly caused by playing a text='bad' strategy despite having text='above-average' luck, than by playing a text='good' strategy but having text='below-average' luck. Moreover, merely having “below-average” luck does not excuse a loss; having below-average luck is perfectly normal, and scenarios are designed to be winnable even with below-average luck. It is only exceedingly bad luck, over multiple turns, that we mean here." + _ " Be wary of attributing a loss to any of these reasons. If you are not a veteran player, it is far more likely that your loss was caused by one of the text='common' errors, listed above, and is not indicative of a bug in the campaign. However, if you still think you found a bug, then by all means, report it!" + _ " The “Damage Calculations” dialog shows some statistics that can help determine whether a match was very lucky or very unlucky. However, reading the statistics is no substitute to watching the replay and looking for strategic mistakes, or small bits of luck at critical points in the engagement." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=combat title= _ "Combat" text= "src=help/combat1.png align=right float=yes" + _ "Combat in text='Battle for Wesnoth' always takes place between units in adjacent hexes. Click on your unit, and click on the enemy you want to attack: your unit will move towards the enemy unit, and when they are next to each other, combat will begin. The attacker and defender alternate strikes until each has used their allotted number of strikes. The attacker chooses one of its weapons to attack with, and the defender retaliates with one of its attacks of the same type. There are two types of attacks: text='melee', which usually involves weapons such as swords, axes or fangs; and text='ranged', which usually involves weapons such as bows, spears and fireballs." + _ "
text='Order and Number of Strikes'
" + _ " The attacker gets the first strike, then the defender retaliates. Each strike either hits, doing a given amount of damage, or misses, doing no damage at all. Strikes alternate until each unit has used up all of its strikes. The number of strikes a unit has varies; for instance, an elvish fighter with a 5×4 attack may strike 4 times, each successful strike dealing 5 damage, while an orcish grunt with a 9×2 attack can only strike twice (but at 9 damage for each hit)." + _ "
text='Chance to Hit'
" + _ " Every unit has a chance of being hit, based on the text='terrain' it is in. This is shown in the status pane, and may also be found by right-clicking a unit, selecting text='Unit Description', and then looking at text='Terrain Modifiers'. For instance, many elves have a defense rating of 70% in forest, so a unit attacking them has only a 30% chance of hitting. Conversely, the elf’s chance of hitting the attacker in return depends on what terrain the attacker is in." + _ " There are two exceptions to this rule: dst='weaponspecial_magical' text='magical attacks' and dst='weaponspecial_marksman' text='marksmen'. Magical attacks always have a 70% chance to hit, regardless of terrain, and, when used offensively, marksmen always have at least a 60% chance to hit, regardless of terrain." + _ "
text=Damage
" + _ " Each strike which hits causes a base amount of damage depending on the attack type. For instance, an elvish fighter with a 5×4 attack does 5 base damage. This is usually modified by two things: dst='damage_types_and_resistance' text='resistance' and dst='time_of_day' text='time of day'. To see how base damage is modified by the circumstances, select text='Damage Calculations' in the attack selection menu." + _ " A few units have special dst='..abilities_section' text='abilities' which affect damage dealt in combat. The most common of these is dst='weaponspecial_charge' text='charge', which doubles the damage dealt by both attacker and defender when the unit with charge attacks." [/topic] # wmllint: markcheck on [topic] id=damage_types_and_resistance title= _ "Damage Types and Resistance" text= _ "In Wesnoth, there are three types of damage usually associated with physical attacks: text='blade, pierce, and impact damage'. Additionally, there are three further types of damage usually associated with magical attacks: text='fire, cold, and arcane attacks'. Different units may have resistances which alter the damage which they take from certain damage types." + _ " Resistances work very simply: if a unit has 40% resistance against a damage type, then it will suffer 40% less damage when hit with that damage type. It is also possible for a unit to be vulnerable against some damage types. If a unit has −100% resistance against a damage type, it will suffer 100% more damage when hit by that type." + _ " For example, skeletons are highly resistant to blade and pierce damage, but are vulnerable to impact and fire damage, and extremely vulnerable to arcane damage." + _ " If a strike is determined to hit, it will always do at least 1 point of damage. This applies even if the defender has 100% resistance to the damage type." [/topic] # wmllint: markcheck off [topic] id=orbs title= _ "Orbs and ellipses" text= _ "There are colored indicators above the energy bars of some units, consisting of a colored orb (and sometimes a dst='crowns' text='crown')." + " " + "src=help/orb-green.png align=here" + "src=help/orb-yellow.png align=here" + "src=help/orb-red.png align=here" + "src=help/orb-disengaged.png align=here" + "src=help/orb-blue.png align=here" + "src=help/orb-none.png align=here" + " " + #po: The help page has a set of images above this paragraph, in the same order as the bullet points _ "The orbs show whether the unit can move or attack. The statuses and their standard colors are: • text='Green' if it has neither moved nor attacked this turn. • text='Yellow' if it has moved (or attacked), and can still attack. It might still be able to move further too. • text='Red' if it can neither move further nor attack again this turn. • Red is also used after the ‘end unit turn’ command, and, • when a unit is in the middle of a multi-turn move (has been told to move further than it can in the current turn). • text='Red and yellow' if it has moved (or attacked), can still move further, but it can no longer attack. • This can happen due to campaign-specific events or abilities, for example the text='disengage' ability in the campaign text='Under the Burning Suns'. • text='Blue' for allied units, except during that ally’s own turn. • During the ally’s own turn, their units will be shown with the colors showing whether the units can still move and attack; however their moves, and the corresponding orb changes, are delayed as explained in dst='shroud_and_fog' text='Shroud and Fog of War'. • Enemy units normally don’t have orbs, however these can be enabled in the advanced preference “Customize orb colors”." + " " + _ "
text='Ellipses'
" + " " + _"A team-colored shape is drawn on the ground under each unit. This is called the “ellipse”, although some units’ ellipses are not elliptical." + " " + "src='help/empty-square.png~BLIT(misc/ellipse-top.png)~BLIT(misc/ellipse-bottom.png)~BLIT(units/human-loyalists/spearman.png~TC(1, magenta))'" + "src='help/empty-square.png~BLIT(misc/ellipse-leader-top.png)~BLIT(misc/ellipse-leader-bottom.png)~BLIT(units/human-loyalists/lieutenant.png~TC(1, magenta))'" + "src='help/empty-square.png~BLIT(misc/ellipse-hero-top.png)~BLIT(misc/ellipse-hero-bottom.png)~BLIT(units/human-loyalists/lieutenant.png~TC(1, magenta))'" + "src='help/empty-square.png~BLIT(misc/ellipse-nozoc-top.png)~BLIT(misc/ellipse-nozoc-bottom.png)~BLIT(units/human-peasants/peasant.png~TC(1, magenta))'" + "src='help/empty-square.png~BLIT(misc/ellipse-leader-nozoc-top.png)~BLIT(misc/ellipse-leader-nozoc-bottom.png)~BLIT(units/human-peasants/peasant.png~TC(1, magenta))'" + " " + #po: The help page has a set of images above this paragraph, in the same order as the bullet points _ "• Most units have a circular ellipse. • Units that can recruit have a seven-pointed star. • dst='crowns' text='Hero units' have a smaller variant of the seven-pointed star, these units can’t recruit. • Units without a dst='movement' text='zone of control' have a broken outline version of the shape. • Some campaigns start with a level zero leader. Able to recruit but lacking a ZoC, these units have a broken outline version of the seven-pointed star." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=crowns title= _ "Crowns and loyal markers" text=_ "Some units have an additional marker superimposed on their dst='orbs' text='orb', and a corresponding shape to their dst='orbs' text='ellipses':" + " " + "src='help/empty-square.png~CROP(0,0,72,36)~BLIT(misc/leader-crown.png~CROP(4,0,36,18)~XBRZ(2))'" + "src='help/empty-square.png~CROP(0,0,72,36)~BLIT(misc/hero-icon.png~CROP(4,0,36,18)~XBRZ(2))'" + "src='help/empty-square.png~CROP(0,0,72,36)~BLIT(misc/leader-expendable.png~CROP(4,0,36,18)~XBRZ(2))'" + "src='help/empty-square.png~CROP(0,0,72,36)~BLIT(misc/loyal-icon.png~CROP(4,0,36,18)~XBRZ(2))'
" + "src='help/empty-square.png~BLIT(misc/ellipse-leader-top.png)~BLIT(misc/ellipse-leader-bottom.png)~BLIT(units/orcs/leader.png~TC(1, magenta))~BLIT(misc/leader-crown.png)'" + "src='help/empty-square.png~BLIT(misc/ellipse-hero-top.png)~BLIT(misc/ellipse-hero-bottom.png)~BLIT(units/dunefolk/herbalist/alchemist.png~TC(1, magenta))~BLIT(misc/hero-icon.png)'" + "src='help/empty-square.png~BLIT(misc/ellipse-leader-top.png)~BLIT(misc/ellipse-leader-bottom.png)~BLIT(units/human-magi/white-mage.png~TC(1, magenta))~BLIT(misc/leader-expendable.png)'" + "src='help/empty-square.png~BLIT(misc/ellipse-top.png)~BLIT(misc/ellipse-bottom.png)~BLIT(units/human-loyalists/spearman.png~TC(1, magenta))~BLIT(misc/loyal-icon.png)'" + " " + #po: The help page has a set of images above this paragraph, in the same order as the first set of bullet points, showing what the "loyal icon" is and the difference between "silver" and "blueish-silver". _ "• Leaders are shown with a text='gold crown'. • Heroes have a text='blueish-silver crown'. • Expendable leaders are shown with a text='silver crown'. • dst='traits_loyal' text='Loyal units' have the text='loyal icon'. Of these categories, only leaders are built into the basic game rules. The others are found in campaigns, and are characters that form part of the narration. The exact rules for them are set by their campaign, which might deviate from these standard expectations about them: • The death of any hero leads to immediate defeat. • The death of an expendable leader doesn’t lead to immediate defeat, even though they can recruit. • All of these units have the main advantage of the loyal trait, that they cost no upkeep. • Losing any of these units causes a disadvantage for the remainder of the campaign, assuming it doesn’t end immediately. • These units will never occur as random recruits." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=time_of_day title= _ "Time of Day" text= _ "The time of day affects the damage of certain units as follows: • LAWFUL units get +25% damage in daytime, and −25% damage at night. • CHAOTIC units get +25% damage at night, and −25% in daytime. • NEUTRAL units are unaffected by the time of day. • LIMINAL units get +25% damage during twilight." + _ " The current time of day can be observed under the minimap in the status pane. For the usual day/night cycle, morning and afternoon count as day, first and second watch count as night:" + " Dawnsrc=misc/time-schedules/default/schedule-dawn.png Morningsrc=misc/time-schedules/default/schedule-morning.png Afternoonsrc=misc/time-schedules/default/schedule-afternoon.png Dusksrc=misc/time-schedules/default/schedule-dusk.png First Watchsrc=misc/time-schedules/default/schedule-firstwatch.png Second Watchsrc=misc/time-schedules/default/schedule-secondwatch.png
" + " " + _" Keep in mind that some scenarios take place underground, where it is perpetually night!" + "" + _" Some underground locations are illuminated. They are perpetually intermediate between day and night." + "" + _" Some role-playing scenarios take place indoors — these regions are similarly intermediate." + "" + _" Finally, units with the dst='ability_illuminationilluminates' text='illuminates' ability and terrain features such as dst='terrain_lava' text='lava' change the time of day bonus around them." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=healing title= _ "Healing" text= _ "In combat, your units will inevitably take damage. There are several ways to heal your units. However, with the exception of resting, these do not stack; only one can occur per turn." + _ " • text='Resting': A unit which neither moves, attacks, nor is attacked will heal 2 HP in its next turn." + _ " • text='Villages': A unit which starts a turn in a village or dst='terrain_oasis' text='oasis' will heal 8HP. If the unit is poisoned, the poison will be cured instead." + _ " • dst='ability_regeneratesregenerates' text='Regeneration': Certain units (such as trolls) will automatically heal 8HP every turn. If the unit is poisoned, the poison will be cured instead." + _ " • text='Healing units': Units with the dst='ability_healingheals +4' text='Heals' ability will heal each allied adjacent unit, usually dst='ability_healingheals +4' text='4HP' or dst='ability_healingheals +8' text='8HP' per turn, or prevent Poison from causing that unit damage." + _ " • text='Curing units': Units with the dst='ability_curingcures' text='cures' ability will cure Poison in all allied adjacent units (in preference to healing, if it has that ability as well)." + _ " • text='Advancement': When a unit dst='advancement' text='advances', it will heal fully. This can happen as soon as your unit gains enough experience, whether it is your turn or not." + _ " Resting can be combined with other forms of healing, but villages, regeneration, healing and curing cannot combine with each other: the best option will be used. Finally, units heal fully between scenarios." + _ " text='Advanced'" + _ " Unlike other forms of healing, the heals ability will not take effect on the healed unit’s turn, but on the healer’s turn. This means that while a unit surrounded by several healers on the same side will only receive healing from one healer per turn, a unit surrounded by healers from several allied sides will be healed once on each of said allied sides’ turns." [/topic] # wmllint: markcheck on [topic] id=wrap_up title= _ "Wrap Up" text= _ "This concludes the fundamentals of Wesnoth. You might want to read up on basic strategy, or familiarize yourself with dst='..traits_section' text='traits' and dst='..abilities_section' text='abilities', but you now know everything you need to know to play the text='Heir to the Throne' campaign. Have fun, and good luck!" [/topic] [topic] id=license title= _ "License" #ifndef SCHEMA_VALIDATION text="{COPYING.txt}" #endif [/topic] # wmllint: markcheck off [topic] id=..traits_section title= _ "Traits" generator="contents:generated" text= _ "Traits are modifications that change a unit’s attributes slightly. They are usually randomly assigned to a unit when it is recruited. The traits available to a unit are largely determined by its text='race'." + _ " Most units have two traits. However, goblins have only one trait, undead units are always assigned the single trait text='undead' and in some cases text='fearless', and woses do not receive any traits. " + _ " The traits that are available to most non‐undead units are dst='traits_intelligent' text='intelligent', dst='traits_quick' text='quick', dst='traits_resilient' text='resilient', and dst='traits_strong' text='strong'." + _ " Elves may also receive dst='traits_dextrous' text='dextrous', and dwarves may receive dst='traits_healthy' text='healthy'. Trolls and certain humans may receive dst='traits_fearless' text='fearless'. Other traits which may be assigned include dst='traits_loyal' text='loyal', dst='traits_feral' text='feral' and dst='traits_undead' text='undead'. " [/topic] [topic] id=..terrains_section title= _ "Terrains" text= _ "Game maps feature a variety of terrains that affect both unit movement and a unit’s defensive capability in combat." + _ " Terrains come in two types: basic and mixed." + _ "
Basic Terrain Types
" + _ " Basic terrain types include Flat, Hills, Mountains, Sands, Water and Swamps. There are many more besides these — a list of the terrain types you have discovered can be found at the end of this page. " + "" + "" + "" + "" + "" + "
" + _ "Every unit has a defense rating and a movement cost for each of the basic terrain types, and these values are listed in the unit’s help page. Basic terrain types may have unique properties like illumination effects as well." + _ "
Mixed Terrain Types
" + _ " Mixed terrain types share the properties of multiple basic terrain types — units generally receive the best defense and worst movement of the underlying basic types when they move onto a mixed type. For example, this is the case with forested hills, sand hills, and cave hills. " + "" + "" + "
" + _ "One notable exception is bridge terrains, such as bridges over shallow water, fords, and bridges over chasms. Fords are easily passable to both merfolk and humans — all units moving on a ford enjoy the best defense and best movement out of flat and shallow water, rather than the worse movement of the two. Similarly, bridges over chasms are passable to nonfliers (unsurprisingly). " + "" + "" + "" + _ "
Land-based villages generally give the best defense and movement as well. These villages are mixed terrains, based on the village terrain type, together with hill, swamp, and cave, respectively. " + "" + "" + "
" + _ "Finally, water villages are generally inhospitable to land units, and do not give defense or movement benefits associated with the village terrain type. Instead, they count only as water tiles. " + "
" + _ "You can see what basic types a mixed terrain is comprised of by mousing over its hex and checking the terrain type icons displayed in the upper right (under the default theme)." + _ " You can see what type of behavior the mixed terrain gives by mousing over its hex and viewing the terrain description by either pressing the hotkey, or right clicking and selecting from the context menu." + _ "
Defense Caps
" + _ " Some units have defense caps for a particular basic terrain type. These units suffer a penalty on mixed terrains with that type — their defense cannot exceed the cap." + _ " For example, the Loyalist Cavalryman has a defense rating of 30% on forests, and a defense cap for forests. Thus, on forested hills, he has a defense rating of 30% rather than 40%, because the mixed rating cannot exceed the cap." + _ " If a unit has a defense cap for some terrain, it is always the same as its defense rating on that terrain (it cannot be larger)." + _ "
Basic Terrain Types
" generator="contents:generated" [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=..addons title= _ "Add-ons" text = _ "The degree of customization offered by the Wesnoth engine allows players to create their own game content, including new scenarios, campaigns, and much more beyond what is offered in the official content bundled with the game. " generator="contents:addons" [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=using_addons title= _ "Using Add-ons" text= _ "The game supports different types of add-on content, which are not all available in every gameplay mode." + _ "
text='Campaigns and Scenarios'
" + _ " Single-player campaigns are collections of scenarios that fit together to tell a story. Both stand-alone scenarios—if intended to be played as such—and regular campaigns are available from the text='Campaigns' menu at the title screen." + _ "
text='Multiplayer Campaigns, Scenarios, and Map Packs'
" + _ " text='Multiplayer' games can be played in fully customized, scripted scenarios or even specially designed campaigns. There are also packs providing sets of individual multiplayer scenarios." + _ "
text='Multiplayer Eras and Factions'
" + _ " For gameplay purposes, various races of creatures in the world cooperate with each other in factions. Factions are grouped in balanced sets with a common theme; for example, the main factions of Wesnoth can be found in the included Default Era. In text='Multiplayer' mode, you can choose an era when creating a new game, and players can pick from the available factions for that era when setting up their sides and teams." + _ " You can see what eras you have loaded in the text='eras' dst='..eras_section' of the help." + _ "
text='Modifications'
" + _ " Modifications are optional scenario- and era-independent scripts that can alter the default ruleset in various ways. You can choose and configure modifications when creating a new game." + _ "
text='Cores'
" + _ " Cores enable total conversion of The Battle for Wesnoth. A core can replace all the content in Wesnoth: when a different core is loaded, the regular units, terrains and the like do not exist. Cores allow a significantly different game experience: for example, a World War II campaign, or even a different game altogether, as long as it can be represented as a hexagonal map with ’units’ in some way." + _ "
text='Creator Resources'
" + _ " Content authors can use resource packs available on the add-ons server to enrich their own content with existing assets such as images, music, and code. These are not generally intended for direct use in-game; however, other playable add-ons may depend on them and suggest or require their installation during download." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=installing_addons title= _ "Installing Add-ons" text = _ "User-made add-ons can be obtained and updated through the text='Add-ons' option in the main menu. After connecting to the add-ons server (by default text='add-ons.wesnoth.org'), you will be presented with a list of add-ons available on the server for downloading. The installation status for each add-on is shown below each entry. For add-ons that are text='upgradable' or text='outdated' on the server, their installed and published versions will be shown in the text='Version' column. To search for add-ons by keywords, type any relevant terms in any order in the search box, separated by spaces. You can also sort the add-on list by clicking the column headers. It is also possible to choose to only display add-ons of specific categories by clicking on the text='Type' dropdown. To install an add-on, select it from the list and click the text='+' icon, or simply double-click on the add-on’s title. If the window is too small to show them inline, the text='Add-on Details' button provides you with additional details about the add-on, such as its full description, installation status, and available translations." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=removing_addons title= _ "Removing Add-ons" text = _ "To remove add-ons, choose text='Remove Add-ons' in the add-ons server connection dialog. You will be presented with options to remove any number of add-ons you currently have installed. It is not possible to remove add-ons for which there is publishing information (text='.pbl' files) attached, in order to prevent its accidental loss. If necessary, you must manually delete the information files or the add-ons themselves using a file manager provided by your platform." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=..commands title= _ "Commands" generator="contents:commands" [/topic] [topic] id=general_commands title= _ "General Commands" text= _ "These commands can either be issued via the command line by prefixing them with ‘:’ (as shown here) or via the chat by prefixing them with ‘/’ (press ‘m’ first to open the chat line). " + "
text=':benchmark'
" + _ " Similar to the ‘fps’ command, but also forces everything to redraw instead of only things that have changed. " + "
text=':clear'
" + _ " Clear chat messages. " + "
text=':debug'
" + _ " Switch debug mode on (does not work in multiplayer). See dst='debug_commands' text='debug mode commands'. Debug mode is turned off by quitting the game or :nodebug. " + "
text=':droid [] [on|off|full]'
" + _ " Switch a side between human and AI control. The second parameter can be ‘off’ to bring the side under human control, ‘on’ to watch the AI make its moves, or ‘full’ to make the AI’s turn behave similarly to another player‘s turn. If no second parameter is supplied, it toggles between ‘on’ and ‘off’. Defaults to toggling the currently active side if no parameters are supplied. " + "
text=':controller '
" + _ " Display the controller status of a side. " + "
text=':fps'
" + _ " Toggle the display of the current frames per second. Also writes these values to a file in the userdata directory. " + "
text=':log '
" + _ " Switch a log domain to a different log level. " + "
text=':refresh'
" + _ " Redraws the screen and reloads any image files that have been changed. " + "
text=':theme'
" + _ " Bring up theme selection menu. " + "
text=':q or :q!'
" + _ " Quit the scenario (without prompting). " + "
text=':w'
" + _ " Save the game (without prompting). " + "
text=':wq'
" + _ " Save the game and quit the scenario (without prompting)." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=mp_commands title= _ "Multiplayer Commands" text= _ "These commands can either be issued via the command line by prefixing them with ‘:’ (as shown here) or via the chat by prefixing them with ‘/’ (press ‘m’ first to open the chat line). " + "
text=':ban '
" + _ " Ban a user in a multiplayer game by the IP address used by that username and kick him. Can be used on users not in the game but on the server. (Of course they won’t be kicked then.) " + "
text=':control '
" + _ " Change the controller for side (write here the number of the side) to username (write here the nickname of the player or observer). You can check what side belongs to which player in the text='Scenario Settings' dialog (Press the text='More' button in the text='Status Table' (alt+s by default) to get there.). The host can change control of any side. " + "
text=':give_control'
" + _ " Launch a dialog to assist the host in changing the human controllers of sides. " + "
text=':idle '
" + _ " Toggle the idle state for a side. The host may make a side idle after a network disconnection. " + "
text=':kick '
" + _ " Kick a user in multiplayer. They will be able to rejoin the game. If you just want to change control of their side(s) use the :control command instead. " + "
text=':m or :msg or :whisper '
" + _ " Send a private message to a user. When in a game, it is not possible to send private messages to players who are currently controlling a side in the same game. " + "
text=':mute []'
" + _ " Mute a specific observer. If no username is supplied the muted usernames are displayed. " + "
text=':muteall'
" + _ " Toggle muting/silencing of all observers on/off. " + "
text=':unban '
" + _ " Unban a user in a multiplayer game by the IP address used by that username. Can be used on users not in the game but on the server. " + "
text=':unmute []'
" + _ " Unmute a specific observer. If no username is supplied the list of muted observers is cleared." [/topic] # wmllint: markcheck on # wmllint: markcheck off [topic] id=debug_commands title= _ "Debug Mode Commands" text= _ "These commands can either be issued via the command line by prefixing them with ‘:’ (as shown here) or via the chat by prefixing them with ‘/’ (press ‘m’ first to open the chat line). " + "
text=':choose_level or :cl'
" + _ " Brings up a menu for choosing a scenario to immediately advance to in a campaign. " + "
text=':create '
" + _ " Create a unit of the specified type on the selected hex. " + "
text=':fog/shroud'
" + _ " Toggle fog/shroud for the current side. " + "
text=':gold '
" + _ " Adds the specified amount to the current side’s gold. " + "
text=':n'
" + _ " Immediately advances to the next scenario in a campaign. " + "
text=':set_var '
" + _ " Manually set a gamestate variable to value. " + "
text=':show_var '
" + _ " Show a gamestate variable. " + "
text=':throw/fire '
" + _ " Manually fire the specified event. " + "
text=':unit '
" + _ " Modifies the specified property of the selected unit. Example: :unit hitpoints=100 " + "
text=':unit '
" + _ " Makes the selected unit level up N times. Example: :unit advances=2" [/topic] # wmllint: markcheck on [/help]