https://wiki.wesnoth.org/api.php?action=feedcontributions&feedformat=atom&user=Placid 2026-05-12T08:55:27Z User contributions MediaWiki 1.31.16 https://wiki.wesnoth.org/index.php?title=Template:Compiling_Wesnoth&diff=33737 2010-02-14T02:56:00Z

<p>Placid: make compiling menu consistent with wml menu formatting</p> <hr /> <div>{| class=&quot;gallery&quot; style=&quot;width:175px;float: right;border: 1px solid #B48648; color:#B48648; font-size: 8pt;margin-left;10px;&quot;<br /> |-<br /> |<br /> &lt;span style=&quot;float: right;&quot;&gt;&lt;small class=&quot;editlink noprint plainlinksneverexpand&quot;&gt;[{{SERVER}}{{localurl:Template:Compiling Wesnoth|action=edit}} edit ]&lt;/small&gt;&lt;/span&gt;<br /> '''Compiling Wesnoth'''<br /> |-<br /> |Platforms<br /> * [[CompilingWesnoth|Linux or Unix]]<br /> * [[WesnothOnLinuxPDAs|Linux PDA]]<br /> * [[CompilingWesnothOnMacOSX|Mac OS X]]<br /> * [[CompilingWesnothOnWindows|MS Windows]]<br /> * [[CompilingWesnothOnSuSE|SuSE]]<br /> * [[CompilingWesnoth/CrossCompiling|cross-compiling]]<br /> |-<br /> |Tools<br /> * [[UsingAutotools|Autotools]]<br /> * [[Dev-Cpp|Dev-C++]]<br /> * [[Jam]]<br /> * [[WesnothSVN|Subversion (SVN)]]<br /> * [[SCons]]<br /> |}</div>

Placid https://wiki.wesnoth.org/index.php?title=User_talk:Placid&diff=26017 2008-06-24T07:15:35Z

<p>Placid: Removing all content from page</p> <hr /> <div></div>

Placid https://wiki.wesnoth.org/index.php?title=User_talk:Placid&diff=26009 2008-06-24T06:34:04Z

<p>Placid: /* Headline text */</p> <hr /> <div>[[Media:Example.ogg]][[Image:Example.jpg]]</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8631 2006-03-28T04:42:02Z

<p>Placid: </p> <hr /> <div>{|width=&quot;80%&quot; width=&quot;{{{width}}}&quot; align=&quot;center&quot; align=&quot;{{{align}}}&quot; cellspacing=&quot;0&quot; cellpadding=&quot;8&quot; style=&quot;border: 2px solid #B48648; font-size: 90%; padding:5px; background-color: #f9f9f9;&quot;<br /> |-<br /> |align=&quot;left&quot;|''{{{quote}}}''<br /> |-<br /> |align=&quot;right&quot;|&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=80%<br /> |align=center<br /> |quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=William Shakespeare, ''Julius Caesar'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8632 2006-03-28T04:41:45Z

<p>Placid: </p> <hr /> <div>{|width=&quot;80%&quot; width=&quot;{{{width}}}&quot; align=&quot;center&quot; align=&quot;{{{align}}}&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;border: 2px solid #B48648; font-size: 90%; padding:15px; background-color: #f9f9f9;&quot;<br /> |-<br /> |align=&quot;left&quot;|''{{{quote}}}''<br /> |-<br /> |align=&quot;right&quot;|&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=80%<br /> |align=center<br /> |quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=William Shakespeare, ''Julius Caesar'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8630 2006-03-28T04:41:42Z

<p>Placid: </p> <hr /> <div>{|width=&quot;80%&quot; width=&quot;{{{width}}}&quot; align=&quot;center&quot; align=&quot;{{{align}}}&quot; cellspacing=&quot;0&quot; cellpadding=&quot;8&quot; style=&quot;border: 2px solid #B48648; font-size: 90%; margin:5px; background-color: #f9f9f9;&quot;<br /> |-<br /> |align=&quot;left&quot;|''{{{quote}}}''<br /> |-<br /> |align=&quot;right&quot;|&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=80%<br /> |align=center<br /> |quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=William Shakespeare, ''Julius Caesar'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8629 2006-03-28T04:40:48Z

<p>Placid: </p> <hr /> <div>{|width=&quot;80%&quot; width=&quot;{{{width}}}&quot; align=&quot;center&quot; align=&quot;{{{align}}}&quot; cellspacing=&quot;0&quot; cellpadding=&quot;8&quot; style=&quot;border: 2px solid #B48648; font-size: 90%; background-color: #f9f9f9;&quot;<br /> |-<br /> |align=&quot;left&quot;|''{{{quote}}}''<br /> |-<br /> |align=&quot;right&quot;|&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=80%<br /> |align=center<br /> |quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=William Shakespeare, ''Julius Caesar'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8628 2006-03-28T04:37:45Z

<p>Placid: </p> <hr /> <div>{|width=&quot;80%&quot; width=&quot;{{{width}}}&quot; align=&quot;center&quot; align=&quot;{{{align}}}&quot; cellspacing=&quot;4&quot; cellpadding=&quot;4&quot; style=&quot;border: 2px solid #B48648; font-size: 90%; padding: 3px; margin: 1em; background-color: #f9f9f9;&quot;<br /> |-<br /> |align=&quot;left&quot;|''{{{quote}}}''<br /> |-<br /> |align=&quot;right&quot;|&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=80%<br /> |align=center<br /> |quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=William Shakespeare, ''Julius Caesar'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8627 2006-03-28T04:35:44Z

<p>Placid: </p> <hr /> <div>{|width=&quot;80%&quot; width=&quot;{{{width}}}&quot; align=&quot;center&quot; cellspacing=&quot;4&quot; cellpadding=&quot;4&quot; style=&quot;border: 2px solid #B48648; font-size: 90%; padding: 3px; margin: 1em; background-color: #f9f9f9;&quot;<br /> |-<br /> |align=&quot;left&quot;|''{{{quote}}}''<br /> |-<br /> |align=&quot;right&quot;|&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> width=80%<br /> |quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Quotation templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=AdvancedTactics&diff=8626 2006-03-28T04:32:52Z

<p>Placid: TOC right</p> <hr /> <div>{|align=&quot;right&quot;<br /> |-<br /> |__TOC__<br /> |}<br /> This page assumes that the reader has read [[GettingStarted]] and is familiar with the [[WesnothManual]].<br /> It assumes you have played enough games to be familiar with the system,<br /> and know how to push units around, and are now looking for insight in how to<br /> outthink the AI or a human opponent.<br /> Some tactics are only useful in specific circumstances and would be foolish at other times.<br /> Pick and choose those that fit your particular style.<br /> Do you overwhelm your opponent with sheer numbers, or a few well-chosen<br /> high-level units? Do you prefer to &quot;roleplay&quot; one race?<br /> Do you want to play many scenarios, or replay one over and over until you achieve the perfect game?<br /> <br /> <br /> === Strategy ===<br /> ==== Fight unfair ====<br /> From Sun Tsu to &quot;Shock and Awe&quot;, military writers have stressed that<br /> one must not enter into a conflict unless substantially stronger<br /> than your enemy. In Wesnoth, this means<br /> * more units<br /> * better (stronger, higher level) units, and<br /> * superior healing ability in your second line.<br /> <br /> Napoleon was especially skilled at maneuvering his forces so as to gain an<br /> advantage even when outnumbered. By attacking his enemy in the center, he broke<br /> their lines and divided the enemy forces in two. Then, a small detachment<br /> fortified their position and held off one flank, while Napoleon's main<br /> force attacked the now outnumbered other half. After reducing the<br /> first half, the main force would rejoin the flank-holders and destroy the<br /> remaining half. (This strategy is known as &quot;defeat in detail&quot;.)<br /> <br /> To implement this in Wesnoth, leave a few units with many hit points<br /> in favorable terrain on one flank, while the majority of your force<br /> attacks on a different front.<br /> For example, two red and one white mage, or three paladins.<br /> By combining healers and the healing effect of villages,<br /> a small force can hold off superior numbers for a very long time.<br /> <br /> ==== Feints ====<br /> You can misdirect the AI (and a surprising number of human opponents)<br /> by sending a few units towards an objective like an enemy leader, village,<br /> or bridge. They will overreact and position their units badly.<br /> Similarly, you can send fast units behind the enemy lines to capture villages.<br /> Do not attempt to hold them; instead move onto the next while the enemy diverts<br /> front line troops or reinforcements.<br /> Flying units are particularly adept at this since they ignore terrain.<br /> Sometimes a feint can turn into your main offensive as well,<br /> if the enemy calls a bluff and ignores your feinting units.<br /> <br /> ==== Bounding (or leap frog) ====<br /> Every strategist throughout history warns to &quot;keep a reserve&quot;.<br /> In Wesnoth, this means that you must not attack with all your units.<br /> Instead, hold back units to exploit holes caused by your initial attacks.<br /> Or, you might need to move a fresh unit with many hit points to the<br /> front line so they can 'take a beating' and hold your lines.<br /> <br /> In modern times, the &quot;reserve&quot; concept has been expanded as follows.<br /> Divide your main force into two groups, and attack with the first<br /> while holding the second back. When the first group is chewed up,<br /> withdraw it to healers or villages, while you attack with the second group.<br /> This approach allows you to distribute experience more evenly among your units,<br /> particularly useful in a longer campaign.<br /> However, if you need the higher-level units, selecting which units deliver a fatal blow levels units faster.<br /> This way, you are less likely to lose units with higher exp,<br /> resulting in more units succeeding in leveling up.<br /> <br /> Do not use high level units, and definitely not your commander,<br /> to guard the healers or villages, as the enemy might focus on them instead,<br /> and attack the wounded seeking aid.<br /> <br /> Sometimes, if it is a favorable time of day, you can quickly achieve victory<br /> with an all-out assault. If the enemy is clearly weaker then you, or the conditions are right, this can be an effective<br /> strategy. Most of the time, however, commanders are advised to use other, more elegant strategies.<br /> <br /> ==== Small and strong ====<br /> Develop a small core group of high level units. Recall a strike force<br /> for one or two turns, then move off in a tight pack.<br /> Most should be level 2, with a few level 3 units to hold the flanks or<br /> commit in the 2-3 most decisive rounds.<br /> With this strategy, you'll need fewer villages to provide income,<br /> and thus be less distracted with acquiring them.<br /> <br /> Remember to recruit level 1 units to absorb the enemy's first attacks,<br /> as well as for feints and holding unimportant villages.<br /> Allow those that survive to finish off dying enemy units to replace<br /> any of your core group that make the final sacrifice.<br /> In other words, since some of your leveled units are expected to die,<br /> you need to level up new units to replace them.<br /> <br /> ==== Hit Point Conservation ====<br /> Hit points are a unit's only non-renewable resource.<br /> Choose the attack which causes your unit the least damage,<br /> not deals out the most to the enemy.<br /> For example, assume you are attacking a unit that does 6-3 close combat,<br /> and has no range attack.<br /> Your unit has a 4-4 close combat and a 3-3 range attack.<br /> Consider the tactical situation carefully.<br /> Do you need to kill the unit this turn?<br /> Is it on a village or next to a healer?<br /> Do not automatically accept the computer's recommendation<br /> (it is simply the attack likely to do the most<br /> damage, regardless of how much you take!).<br /> <br /> Remember, when a unit levels up, it regenerates its full HP allowance.<br /> <br /> Finally, attacking an enemy leader, especially in a castle,<br /> is an expensive proposition, even if you use magical attacks.<br /> Expect to lose units while wearing down its hit points.<br /> <br /> <br /> === Weapon specialties ===<br /> ==== Backstab ====<br /> {{Quote|<br /> |quote=&quot;Thieves are deft of foot, and elusive, making them difficult to hit. Being skilled at backstabbing, thieves do double damage when attacking an enemy that has an ally of the thief on its opposite side. Being of chaotic disposition, thieves fight better at night than during the day.&quot;<br /> |source=Thief description<br /> |}}<br /> <br /> Assassins, Nightgaunts, Rogues, Shadows and Thieves can backstab.<br /> A Thief costs 12 gold and has base attack of 4-3. But with a backstab,<br /> it does an impressive 8-3, the equivalent of most Level 2 units.<br /> Backstabbing at night with a Strong Thief does 12-3.<br /> After 24 Experience Points, they level up to a Rogue doing 6-3 base...<br /> <br /> You don't have to ''attack'' with another unit to get the backstab<br /> bonus -- there just needs to be a unit on the opposite side of the enemy.<br /> The ally can even move after the backstab, if it didn't use up its moves<br /> by moving into the enemy's Zone of Control this turn.<br /> Thieves work well in pairs against weak or unsupported units.<br /> They can surround a unit and attack it turn after turn.<br /> <br /> It's often effective to use units with backstab in pairs, so that each <br /> provides the bonus to the other. This is especially effective with <br /> Shadows, due to their good movement rate. Keep one or two such pairs <br /> around your flanks to ambush lone scouts and village-stealers.<br /> <br /> ==== Slow ====<br /> Shamans, being slow, weak, and of limited firepower, need to be<br /> used carefully, but don't dismiss their offensive ability.<br /> Many enemy units such as Trolls (not to mention Troll Warriors!), Orcish Grunts,<br /> and Horsemen have two powerful attacks.<br /> You can cripple them for a round by Slowing them, effectively halving their attacks.<br /> <br /> Of course this tactic is even more useful for your higher-level units:<br /> Druids, Shydes, and Goblin Pillagers.<br /> <br /> ==== Healing and Curing ====<br /> Move your healers in pairs so that you retain the<br /> freedom to use them in combat when appropriate without having to retire<br /> to a village afterward.<br /> Remember the difference between healing and curing, put your better healers<br /> where they will be more needed.<br /> <br /> Don't forget that with a Curing unit nearby, you needn't fear poison.<br /> An assassin's darts are only a serious threat if they can poison an unsupported unit.<br /> Your Druid or White Mage will cure the poison before it has time to work,<br /> (However, they cannot remove damage from a unit on the same turn they cure<br /> poison from that unit). and they can cure poison from ''every'' adjacent unit -<br /> irrespective of damage they have to heal.<br /> <br /> ==== Poison ====<br /> <br /> When using poisonous units (Ghouls, Orcish Assassins, Assassins), your goal should be to distribute their poison attack among as many units as possible, rather than concentrating on a single enemy. Units that are already poisoned should be a low priority for your other units' attacks as well, unless they can score a kill.<br /> <br /> Don't underestimate the usage of poison against regenerating units, or any unit in a village next to a curer. While the healing will remove the poison, it does so in lieu of healing hit points. Repeated poisonings can prevent these (often tough or hard-to-hit) units from recovering while your other units whittle them down.<br /> <br /> ==== Swarm ====<br /> <br /> When a unit's attack is listed as &quot;swarm&quot;, the number of attacks per round is based on its current fraction of maximum health. That is to say, if a unit with swarm is at 3/4 health, it will only do 3/4 of its maximum attacks. This does not effect the damage of each attack.<br /> <br /> If you are the owner of such a unit then keeping it in good health should be your top priority. If you are facing a swarmer, the best idea is to poison it and then avoid it as they are usually high level monsters. As of 1.1.1 using &quot;slow&quot; on these units is very effective as it halves their movement speed, making avoiding them while the poison works easier. Once they are at low health, move in for the kill.<br /> <br /> (From the manual - Henkutsu_tama)<br /> <br /> === Recruiting ===<br /> <br /> Remember that your commander may recruit units when standing on ''any'' Keep tile,<br /> not only the one you start on. If you have two enemies, where one is some<br /> distance beyond the other (like in 'The Siege of Elensefar'), you recruit enough<br /> units to take out the first enemy Commander (and posssibly hold off the second<br /> enemy's front troops), then you move onto the slain Commander's Keep, and<br /> recruit the units you need to take out the remaining opposition.<br /> This saves you money in the long run, and keeps your Commander closer<br /> to the action so he may level up sooner.<br /> <br /> If there are several enemies with significant difference in their strength<br /> of arms, first concentrate on the weakest, or else the one with the<br /> highest income potential.<br /> Move your Commander along with your troops, and after you have wiped<br /> this enemy out, use their Castle as your new base.<br /> This has the added benefit of protecting your Commander, often a target<br /> of enemy troops, so you don't need to recruit units only for protecting him,<br /> while your main force is engaged somewhere else.<br /> In the end, this will save you lots of gold.<br /> Such tactics are essential on maps with many opponents,<br /> for example against the AI on multiplayer map 'Dwarven Doors'.<br /> <br /> ==== Plan placement of units ====<br /> Place recruited and recalled units manually.<br /> Choose the best castle tile for a unit to be placed by clicking on the<br /> tile before recruiting or recalling.<br /> This way you can often capture villages a turn earlier,<br /> or move units to critical map squares before your opponent.<br /> <br /> For maps with narrow passages leading out of the castle<br /> (like Bay of Pearls or some of the random underground maps in<br /> Heir to the Throne), recruit or recall pairs of slow and fast units.<br /> Both units in such a pair will then be able to use their maximum<br /> movement without impeding each other. So recruit an Elvish Fighter<br /> together with a Horseman, or even an Elvish Fighter with an Elvish Archer.<br /> <br /> ==== Unit Choice ====<br /> * Some units, such as Orcish Grunts or Horseman, have no ranged attack. Take advantage of this by using units that are skilled in both melee and ranged, such as Elvish Rangers, so that when you attack you will never be hurt, but yet will not be at a disadvantage when you are attacked. The same goes for units with no melee attack, such at Dark Adepts.<br /> * When a battle is raging, use fast-moving units (your scouts) to distract the enemy by sneaking past enemy troops and conquering enemy villages, cutting off their gold supply or sometimes forcing them to split up their armies.<br /> * If a battle occurs at a river or some other narrow pass, it can be beneficial to use skirmishing units such as Duelists to easily cross the river and surround your opponent or use airborne units like Gryphons to use the river squares without being at a great disadvantage.<br /> * If you need to cross a large body of shallow water, mountains, cave floor, or other difficult terrain, use units whose moves are divisible by their movement on such terrain so moves don't go to waste. For example, if a unit takes three moves to get through one water tile, make sure it has three, six, or nine movement. Recalling 'quick' units can help ensure you've chosen the right ones. If you recall a unit with five movement points, they will only be able to move one hex per turn in terrain that requires three movement points, while a similar unit with six movement points can move two hexes per turn.<br /> * Units such as Elvish Fighters that are cheap to produce in mass and that have both decent melee and ranged attacks can often be good for holding your front lines, since they will cause harm to their opponents no matter what they are. A front line of horsemen, on the other hand, is not good for holding a position, for they are costly, fall quickly to enemy archers, and probably will never be able to strike back.<br /> <br /> === Know the Battlefield ===<br /> <br /> ==== Reconnaissance - Know the Map ====<br /> While attack is influenced by the time of day, defense is affected<br /> by terrain. First find all the castles and note the different kinds<br /> of terrain immediately surrounding them. If you're playing under<br /> Shroud, send out two or three scouts to locate the castles.<br /> This is also often worth it on Fog of War, because you learn<br /> what faction your enemy is (if you don't know already) and<br /> how defended their castle is. Expect to recruit more when they die.<br /> The knowledge they provide is worth more than their cost.<br /> <br /> ==== Survey - Know the Terrain ====<br /> Take an overall look at the size of each terrain type and note which<br /> are the most important.<br /> This affects what units to select and their overall effectiveness.<br /> Then examine whether the main terrain is evenly<br /> distributed, scattered, or in a few large areas.<br /> Note what terrain you want to avoid and why.<br /> Mountains and deep water are bad for all but a few unit types.<br /> These act as walls which the opponents can use to trap you:<br /> of course, you can do likewise to your opponents. If you have<br /> saved some of your starting gold, you can also decide which units will<br /> be better for reinforcements based off a more common terrain.<br /> <br /> ==== Transport - Know the Pathways ====<br /> Try to link advantageous terrain areas together in your mind<br /> from where your units are (your castle at start of play)<br /> to opposing ''and'' friendly castles. Use villages scattered between<br /> you and the target to influence the route to take, especially if you<br /> can't recruit any healing units.<br /> Decide which terrain is most favourable for your units and<br /> less favourable for the enemy.<br /> If you goal is to reach an object or hex, then do the same for that.<br /> <br /> If one route proves difficult, switch to another. Get to know<br /> which routes work best for different units and locate meeting<br /> places to regroup units.<br /> Try to keep the opponents guessing what you're going to do next.<br /> By using several adjacent routes to a target, the opponents<br /> will have a tougher time stopping your advance.<br /> In some cases it is easier to send a main group directly towards<br /> the target and use fast units to circle around behind.<br /> <br /> ==== Features - Know the Traps ====<br /> Note carefully where favourable terrain on either side of<br /> unfavourable reach their closest point. These are defense positions<br /> for you to ambush approaching opponents (with or without a thief) and<br /> provide protection for friendly units. Sometimes the terrain forms<br /> passages for units to pass through quickly. Check whether it takes<br /> fewer turns to move around slow terrain than through it.<br /> In slow terrain, it is tougher to encircle units and immobilise them,<br /> so drive them toward better suited terrain (using ZoC, see elsewhere)<br /> and encircle there.<br /> <br /> <br /> ==== Distance - Watch the Time ====<br /> Use caution when setting up your front line and advancing immediately, as often the time of day will be exactly in it's least advantageous point right when you meet your enemies. If you wait a few turns just passing the time by capturing nearby villages and meet the enemy at First Watch/Dawn, respectively, you can cut down the majority of the enemie's army before they can do anything about it. Also, if you find yourself in a evenly matched or losing position during your worst part of the day it can be ideal to fall back to villages or simply hold tight without attacking the enemy, as you want the battle to progress as slowly as possible during theis part of the day. (Note: If you have units that can attack at no risk [mages to trolls, for example] don't waste their actions, keep on fighting no matter what.)<br /> <br /> === Zone of Control (ZoC) ===<br /> <br /> The Zone Of Control allows you to build artificial barriers at will.<br /> With it, you can reduce the likelyhood that a weaker, injured unit will<br /> be killed, by reducing the number or kind of enemies that can reach it.<br /> It is hard to measure who has Movement Control because it depends<br /> on where the units are positioned more than how many there are.<br /> Although this is a tactical device, it is more strategically<br /> significant than tactical because Zone of Control applies before<br /> and after encounters, rather than during. Establishing and maintaining<br /> good Zones of Control gives you better mobility and control over most other<br /> aspects of the game, even against stronger units less well positioned.<br /> <br /> Your units influence space beyond the hex they're standing on.<br /> The total area of influence includes the hexes adjacent to the units<br /> and ''this'' is the Zone Of Control. When strong opposing units<br /> approach your weaker ones, pay particular attention to the ZoC<br /> and terrain types. Combine the ZoC of your units to form a solid barrier.<br /> Your goal is to rearrange your units such that the opponent's attack<br /> occurs where your units are well positioned defensively and at the worst<br /> time of day for opposing units.<br /> Check that none of your units can be attacked by more than two enemy units<br /> ''and'' that no enemy unit can pass between them.<br /> In this case, you spread your units out, extending your ZoC and forcing<br /> the enemy to select one or more targets.<br /> <br /> In most cases, the opponent will target one unit. You should<br /> ensure that each of your units is within the ZoC of at least two others.<br /> So when the enemy hits one unit, you can close in (encircle, encircle...)<br /> until reinforcements arrive. It is often as important to hold a ZoC<br /> as it is a village or passage.<br /> <br /> While ZoC isn't very important against slow moving units, it is<br /> very effective against fast ones, such as horsemen, bats, ghosts,<br /> and wolf riders. The approach to handling these is assign two or<br /> three of your fastest units, target one long range opposing unit<br /> and spread yours out defensively between its target (usually villages)<br /> and itself in a semi-circle or line. Move these units toward the enemy<br /> so that it has increasingly less space to move. When it is within your ZoC,<br /> encircle and kill. Move on to the next long range unit and repeat.<br /> <br /> After the first round (when everyone has recruited), all the units are<br /> grouped, so try to create a ZoC against all of the long range units<br /> as quickly as you can. In this way you can prevent them from<br /> spreading out, while you systematically encircle and kill each one.<br /> Since the opponent won't have occupied enough villages, there is a<br /> good chance all you'll have left are short range units to deal with.<br /> <br /> Under FoW and Shroud, it is impossible to know what the opponent has<br /> recruited, but it is good practice to check your ZoC around your villages<br /> so you are not surprised by a sudden invasion. Early on, long range<br /> units are used to occupy villages, so the sooner you engage them,<br /> the less villages they can possess. Creating a ZoC quickly around<br /> unoccupied villages allows you to possess them at your leisure and keep them.<br /> <br /> Another use in ZoC is deciding when and where battles will be fought.<br /> If the opponent moves into your ZoC, but positioned near unfavourable<br /> attack terrain, you have several choices. Either attack anyway,<br /> which is mostly bad, wait for the opponent to attack on its next turn,<br /> which gives it the choice of target, or move your units out of its ZoC<br /> to favourable terrain. You can check how far forward the units can move<br /> and place guard units to maintain your ZoC and centralise the others<br /> behind and protecting the guards. This forces the opponent to commit<br /> and gives you time to prepare a tactical counter-attack. Keep your<br /> guards guarding! If the ZoC crumbles your units will be overwhelmed.<br /> <br /> The ZoC is effective when wounded units need to pass through hostile areas.<br /> Rather than closing in, form a large circle around the wounded presenting<br /> a much wider perimeter.<br /> This makes it harder for opposing units to attack all yours and allows you<br /> to keep healthy units within the ZoC and leap-frog when needed.<br /> <br /> On approaching an opponent's castle, ZoC can be critical to your success.<br /> In some scenarios events are triggered when you occupy hexes directly next<br /> to a castle hex. Make sure the approaching units keep their distance from the<br /> castle, but within their ZoC. When assembled, move directly on to the castle.<br /> <br /> For skirmishing units who ignore ZoC, you have little choice but build a solid<br /> wall of units. Alternatively, you may make a ZoC to block the typical units and<br /> prepare a welcoming party for the skirmishers.<br /> <br /> In a campaign scenario, where the objective is to move a unit to a certain point<br /> on the map (often specified by a signpost) you can use more unimportant units<br /> and ZoC by placing them a space or two away from your leader and a space apart<br /> from each other, since in battle units can quite suddenly die, and you don't want<br /> that one to be your leader.<br /> <br /> ==== Encirclement ====<br /> The encircling tactic by two units is very powerful, particularly against long range units. By placing two units on either side, you limit the opposing unit to 1 hex move in any direction. When the unit sidesteps in the following turn, you can re-encircle.<br /> This means you can hold the unit until reinforcements arrive and then adopt a<br /> leap-frog approach against very strong units.<br /> <br /> === Retreating ===<br /> <br /> Sometimes the battle doesn't go your way. Either you battle to the last unit, or<br /> retreat. The purpose of retreating is to regroup your units more effectively and<br /> give them time to heal. Retreating can be organised with a reverse leap-frog<br /> approach, where you give ground, encouraging the opponent to push forward.<br /> Now your healers are in front and moving toward better terrain<br /> where you can make a final stand.<br /> <br /> Being prepared for, and knowing when to retreat, is also important.<br /> Too often a player tries to retreat, but has no reinforcements to halt the retreat.<br /> Try to leave a &quot;safe zone&quot; on a flank, protected by ZoC, where you can pull back.<br /> <br /> The real problem with retreating is putting distance between your units and the<br /> opponents. If they can move faster than yours, you may have to setup a ZoC to<br /> last long enough for you to get your slow units to safety. Invisibility units<br /> are the best because they cannot be seen and will take the opponent valuable<br /> turns to find them. Once the group is safe, they can slip away unnoticed.<br /> Sometimes sending out a unit or two as a kamikaze works to slow them down -<br /> if the exp they gain matters less to them than saving more of your units does to you.<br /> <br /> &lt;noinclude&gt;=== See Also ===<br /> <br /> * [[GettingStarted]]<br /> * [[WesnothManual]]<br /> * [[PlayingOrcs]]<br /> * [[PlayingUndead]]<br /> * [[BestForumStrategies]]<br /> * [[CampaignStrategies]]<br /> * [[Advanced Tactics (Russian)]]<br /> * [[Advanced Tactics (French)]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8625 2006-03-28T04:31:22Z

<p>Placid: </p> <hr /> <div>{|width=&quot;80%&quot; width=&quot;{{{width}}}&quot; align=&quot;center&quot; cellspacing=&quot;4&quot; cellpadding=&quot;4&quot; style=&quot;border: 4px solid #aaa; font-size: 90%; padding: 4px; margin: 1em; background-color: #f9f9f9;&quot;<br /> |-<br /> |align=&quot;left&quot;|''{{{quote}}}''<br /> |-<br /> |align=&quot;right&quot;|&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> width=80%<br /> |quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Quotation templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=AdvancedTactics&diff=8623 2006-03-28T04:21:37Z

<p>Placid: /* Backstab */</p> <hr /> <div>This page assumes that the reader has read [[GettingStarted]] and is familiar with the [[WesnothManual]].<br /> It assumes you have played enough games to be familiar with the system,<br /> and know how to push units around, and are now looking for insight in how to<br /> outthink the AI or a human opponent.<br /> Some tactics are only useful in specific circumstances and would be foolish at other times.<br /> Pick and choose those that fit your particular style.<br /> Do you overwhelm your opponent with sheer numbers, or a few well-chosen<br /> high-level units? Do you prefer to &quot;roleplay&quot; one race?<br /> Do you want to play many scenarios, or replay one over and over until you achieve the perfect game?<br /> <br /> <br /> === Strategy ===<br /> ==== Fight unfair ====<br /> From Sun Tsu to &quot;Shock and Awe&quot;, military writers have stressed that<br /> one must not enter into a conflict unless substantially stronger<br /> than your enemy. In Wesnoth, this means<br /> * more units<br /> * better (stronger, higher level) units, and<br /> * superior healing ability in your second line.<br /> <br /> Napoleon was especially skilled at maneuvering his forces so as to gain an<br /> advantage even when outnumbered. By attacking his enemy in the center, he broke<br /> their lines and divided the enemy forces in two. Then, a small detachment<br /> fortified their position and held off one flank, while Napoleon's main<br /> force attacked the now outnumbered other half. After reducing the<br /> first half, the main force would rejoin the flank-holders and destroy the<br /> remaining half. (This strategy is known as &quot;defeat in detail&quot;.)<br /> <br /> To implement this in Wesnoth, leave a few units with many hit points<br /> in favorable terrain on one flank, while the majority of your force<br /> attacks on a different front.<br /> For example, two red and one white mage, or three paladins.<br /> By combining healers and the healing effect of villages,<br /> a small force can hold off superior numbers for a very long time.<br /> <br /> ==== Feints ====<br /> You can misdirect the AI (and a surprising number of human opponents)<br /> by sending a few units towards an objective like an enemy leader, village,<br /> or bridge. They will overreact and position their units badly.<br /> Similarly, you can send fast units behind the enemy lines to capture villages.<br /> Do not attempt to hold them; instead move onto the next while the enemy diverts<br /> front line troops or reinforcements.<br /> Flying units are particularly adept at this since they ignore terrain.<br /> Sometimes a feint can turn into your main offensive as well,<br /> if the enemy calls a bluff and ignores your feinting units.<br /> <br /> ==== Bounding (or leap frog) ====<br /> Every strategist throughout history warns to &quot;keep a reserve&quot;.<br /> In Wesnoth, this means that you must not attack with all your units.<br /> Instead, hold back units to exploit holes caused by your initial attacks.<br /> Or, you might need to move a fresh unit with many hit points to the<br /> front line so they can 'take a beating' and hold your lines.<br /> <br /> In modern times, the &quot;reserve&quot; concept has been expanded as follows.<br /> Divide your main force into two groups, and attack with the first<br /> while holding the second back. When the first group is chewed up,<br /> withdraw it to healers or villages, while you attack with the second group.<br /> This approach allows you to distribute experience more evenly among your units,<br /> particularly useful in a longer campaign.<br /> However, if you need the higher-level units, selecting which units deliver a fatal blow levels units faster.<br /> This way, you are less likely to lose units with higher exp,<br /> resulting in more units succeeding in leveling up.<br /> <br /> Do not use high level units, and definitely not your commander,<br /> to guard the healers or villages, as the enemy might focus on them instead,<br /> and attack the wounded seeking aid.<br /> <br /> Sometimes, if it is a favorable time of day, you can quickly achieve victory<br /> with an all-out assault. If the enemy is clearly weaker then you, or the conditions are right, this can be an effective<br /> strategy. Most of the time, however, commanders are advised to use other, more elegant strategies.<br /> <br /> ==== Small and strong ====<br /> Develop a small core group of high level units. Recall a strike force<br /> for one or two turns, then move off in a tight pack.<br /> Most should be level 2, with a few level 3 units to hold the flanks or<br /> commit in the 2-3 most decisive rounds.<br /> With this strategy, you'll need fewer villages to provide income,<br /> and thus be less distracted with acquiring them.<br /> <br /> Remember to recruit level 1 units to absorb the enemy's first attacks,<br /> as well as for feints and holding unimportant villages.<br /> Allow those that survive to finish off dying enemy units to replace<br /> any of your core group that make the final sacrifice.<br /> In other words, since some of your leveled units are expected to die,<br /> you need to level up new units to replace them.<br /> <br /> ==== Hit Point Conservation ====<br /> Hit points are a unit's only non-renewable resource.<br /> Choose the attack which causes your unit the least damage,<br /> not deals out the most to the enemy.<br /> For example, assume you are attacking a unit that does 6-3 close combat,<br /> and has no range attack.<br /> Your unit has a 4-4 close combat and a 3-3 range attack.<br /> Consider the tactical situation carefully.<br /> Do you need to kill the unit this turn?<br /> Is it on a village or next to a healer?<br /> Do not automatically accept the computer's recommendation<br /> (it is simply the attack likely to do the most<br /> damage, regardless of how much you take!).<br /> <br /> Remember, when a unit levels up, it regenerates its full HP allowance.<br /> <br /> Finally, attacking an enemy leader, especially in a castle,<br /> is an expensive proposition, even if you use magical attacks.<br /> Expect to lose units while wearing down its hit points.<br /> <br /> <br /> === Weapon specialties ===<br /> ==== Backstab ====<br /> {{Quote|<br /> |quote=&quot;Thieves are deft of foot, and elusive, making them difficult to hit. Being skilled at backstabbing, thieves do double damage when attacking an enemy that has an ally of the thief on its opposite side. Being of chaotic disposition, thieves fight better at night than during the day.&quot;<br /> |source=Thief description<br /> |}}<br /> <br /> Assassins, Nightgaunts, Rogues, Shadows and Thieves can backstab.<br /> A Thief costs 12 gold and has base attack of 4-3. But with a backstab,<br /> it does an impressive 8-3, the equivalent of most Level 2 units.<br /> Backstabbing at night with a Strong Thief does 12-3.<br /> After 24 Experience Points, they level up to a Rogue doing 6-3 base...<br /> <br /> You don't have to ''attack'' with another unit to get the backstab<br /> bonus -- there just needs to be a unit on the opposite side of the enemy.<br /> The ally can even move after the backstab, if it didn't use up its moves<br /> by moving into the enemy's Zone of Control this turn.<br /> Thieves work well in pairs against weak or unsupported units.<br /> They can surround a unit and attack it turn after turn.<br /> <br /> It's often effective to use units with backstab in pairs, so that each <br /> provides the bonus to the other. This is especially effective with <br /> Shadows, due to their good movement rate. Keep one or two such pairs <br /> around your flanks to ambush lone scouts and village-stealers.<br /> <br /> ==== Slow ====<br /> Shamans, being slow, weak, and of limited firepower, need to be<br /> used carefully, but don't dismiss their offensive ability.<br /> Many enemy units such as Trolls (not to mention Troll Warriors!), Orcish Grunts,<br /> and Horsemen have two powerful attacks.<br /> You can cripple them for a round by Slowing them, effectively halving their attacks.<br /> <br /> Of course this tactic is even more useful for your higher-level units:<br /> Druids, Shydes, and Goblin Pillagers.<br /> <br /> ==== Healing and Curing ====<br /> Move your healers in pairs so that you retain the<br /> freedom to use them in combat when appropriate without having to retire<br /> to a village afterward.<br /> Remember the difference between healing and curing, put your better healers<br /> where they will be more needed.<br /> <br /> Don't forget that with a Curing unit nearby, you needn't fear poison.<br /> An assassin's darts are only a serious threat if they can poison an unsupported unit.<br /> Your Druid or White Mage will cure the poison before it has time to work,<br /> (However, they cannot remove damage from a unit on the same turn they cure<br /> poison from that unit). and they can cure poison from ''every'' adjacent unit -<br /> irrespective of damage they have to heal.<br /> <br /> ==== Poison ====<br /> <br /> When using poisonous units (Ghouls, Orcish Assassins, Assassins), your goal should be to distribute their poison attack among as many units as possible, rather than concentrating on a single enemy. Units that are already poisoned should be a low priority for your other units' attacks as well, unless they can score a kill.<br /> <br /> Don't underestimate the usage of poison against regenerating units, or any unit in a village next to a curer. While the healing will remove the poison, it does so in lieu of healing hit points. Repeated poisonings can prevent these (often tough or hard-to-hit) units from recovering while your other units whittle them down.<br /> <br /> ==== Swarm ====<br /> <br /> When a unit's attack is listed as &quot;swarm&quot;, the number of attacks per round is based on its current fraction of maximum health. That is to say, if a unit with swarm is at 3/4 health, it will only do 3/4 of its maximum attacks. This does not effect the damage of each attack.<br /> <br /> If you are the owner of such a unit then keeping it in good health should be your top priority. If you are facing a swarmer, the best idea is to poison it and then avoid it as they are usually high level monsters. As of 1.1.1 using &quot;slow&quot; on these units is very effective as it halves their movement speed, making avoiding them while the poison works easier. Once they are at low health, move in for the kill.<br /> <br /> (From the manual - Henkutsu_tama)<br /> <br /> === Recruiting ===<br /> <br /> Remember that your commander may recruit units when standing on ''any'' Keep tile,<br /> not only the one you start on. If you have two enemies, where one is some<br /> distance beyond the other (like in 'The Siege of Elensefar'), you recruit enough<br /> units to take out the first enemy Commander (and posssibly hold off the second<br /> enemy's front troops), then you move onto the slain Commander's Keep, and<br /> recruit the units you need to take out the remaining opposition.<br /> This saves you money in the long run, and keeps your Commander closer<br /> to the action so he may level up sooner.<br /> <br /> If there are several enemies with significant difference in their strength<br /> of arms, first concentrate on the weakest, or else the one with the<br /> highest income potential.<br /> Move your Commander along with your troops, and after you have wiped<br /> this enemy out, use their Castle as your new base.<br /> This has the added benefit of protecting your Commander, often a target<br /> of enemy troops, so you don't need to recruit units only for protecting him,<br /> while your main force is engaged somewhere else.<br /> In the end, this will save you lots of gold.<br /> Such tactics are essential on maps with many opponents,<br /> for example against the AI on multiplayer map 'Dwarven Doors'.<br /> <br /> ==== Plan placement of units ====<br /> Place recruited and recalled units manually.<br /> Choose the best castle tile for a unit to be placed by clicking on the<br /> tile before recruiting or recalling.<br /> This way you can often capture villages a turn earlier,<br /> or move units to critical map squares before your opponent.<br /> <br /> For maps with narrow passages leading out of the castle<br /> (like Bay of Pearls or some of the random underground maps in<br /> Heir to the Throne), recruit or recall pairs of slow and fast units.<br /> Both units in such a pair will then be able to use their maximum<br /> movement without impeding each other. So recruit an Elvish Fighter<br /> together with a Horseman, or even an Elvish Fighter with an Elvish Archer.<br /> <br /> ==== Unit Choice ====<br /> * Some units, such as Orcish Grunts or Horseman, have no ranged attack. Take advantage of this by using units that are skilled in both melee and ranged, such as Elvish Rangers, so that when you attack you will never be hurt, but yet will not be at a disadvantage when you are attacked. The same goes for units with no melee attack, such at Dark Adepts.<br /> * When a battle is raging, use fast-moving units (your scouts) to distract the enemy by sneaking past enemy troops and conquering enemy villages, cutting off their gold supply or sometimes forcing them to split up their armies.<br /> * If a battle occurs at a river or some other narrow pass, it can be beneficial to use skirmishing units such as Duelists to easily cross the river and surround your opponent or use airborne units like Gryphons to use the river squares without being at a great disadvantage.<br /> * If you need to cross a large body of shallow water, mountains, cave floor, or other difficult terrain, use units whose moves are divisible by their movement on such terrain so moves don't go to waste. For example, if a unit takes three moves to get through one water tile, make sure it has three, six, or nine movement. Recalling 'quick' units can help ensure you've chosen the right ones. If you recall a unit with five movement points, they will only be able to move one hex per turn in terrain that requires three movement points, while a similar unit with six movement points can move two hexes per turn.<br /> * Units such as Elvish Fighters that are cheap to produce in mass and that have both decent melee and ranged attacks can often be good for holding your front lines, since they will cause harm to their opponents no matter what they are. A front line of horsemen, on the other hand, is not good for holding a position, for they are costly, fall quickly to enemy archers, and probably will never be able to strike back.<br /> <br /> === Know the Battlefield ===<br /> <br /> ==== Reconnaissance - Know the Map ====<br /> While attack is influenced by the time of day, defense is affected<br /> by terrain. First find all the castles and note the different kinds<br /> of terrain immediately surrounding them. If you're playing under<br /> Shroud, send out two or three scouts to locate the castles.<br /> This is also often worth it on Fog of War, because you learn<br /> what faction your enemy is (if you don't know already) and<br /> how defended their castle is. Expect to recruit more when they die.<br /> The knowledge they provide is worth more than their cost.<br /> <br /> ==== Survey - Know the Terrain ====<br /> Take an overall look at the size of each terrain type and note which<br /> are the most important.<br /> This affects what units to select and their overall effectiveness.<br /> Then examine whether the main terrain is evenly<br /> distributed, scattered, or in a few large areas.<br /> Note what terrain you want to avoid and why.<br /> Mountains and deep water are bad for all but a few unit types.<br /> These act as walls which the opponents can use to trap you:<br /> of course, you can do likewise to your opponents. If you have<br /> saved some of your starting gold, you can also decide which units will<br /> be better for reinforcements based off a more common terrain.<br /> <br /> ==== Transport - Know the Pathways ====<br /> Try to link advantageous terrain areas together in your mind<br /> from where your units are (your castle at start of play)<br /> to opposing ''and'' friendly castles. Use villages scattered between<br /> you and the target to influence the route to take, especially if you<br /> can't recruit any healing units.<br /> Decide which terrain is most favourable for your units and<br /> less favourable for the enemy.<br /> If you goal is to reach an object or hex, then do the same for that.<br /> <br /> If one route proves difficult, switch to another. Get to know<br /> which routes work best for different units and locate meeting<br /> places to regroup units.<br /> Try to keep the opponents guessing what you're going to do next.<br /> By using several adjacent routes to a target, the opponents<br /> will have a tougher time stopping your advance.<br /> In some cases it is easier to send a main group directly towards<br /> the target and use fast units to circle around behind.<br /> <br /> ==== Features - Know the Traps ====<br /> Note carefully where favourable terrain on either side of<br /> unfavourable reach their closest point. These are defense positions<br /> for you to ambush approaching opponents (with or without a thief) and<br /> provide protection for friendly units. Sometimes the terrain forms<br /> passages for units to pass through quickly. Check whether it takes<br /> fewer turns to move around slow terrain than through it.<br /> In slow terrain, it is tougher to encircle units and immobilise them,<br /> so drive them toward better suited terrain (using ZoC, see elsewhere)<br /> and encircle there.<br /> <br /> <br /> ==== Distance - Watch the Time ====<br /> Use caution when setting up your front line and advancing immediately, as often the time of day will be exactly in it's least advantageous point right when you meet your enemies. If you wait a few turns just passing the time by capturing nearby villages and meet the enemy at First Watch/Dawn, respectively, you can cut down the majority of the enemie's army before they can do anything about it. Also, if you find yourself in a evenly matched or losing position during your worst part of the day it can be ideal to fall back to villages or simply hold tight without attacking the enemy, as you want the battle to progress as slowly as possible during theis part of the day. (Note: If you have units that can attack at no risk [mages to trolls, for example] don't waste their actions, keep on fighting no matter what.)<br /> <br /> === Zone of Control (ZoC) ===<br /> <br /> The Zone Of Control allows you to build artificial barriers at will.<br /> With it, you can reduce the likelyhood that a weaker, injured unit will<br /> be killed, by reducing the number or kind of enemies that can reach it.<br /> It is hard to measure who has Movement Control because it depends<br /> on where the units are positioned more than how many there are.<br /> Although this is a tactical device, it is more strategically<br /> significant than tactical because Zone of Control applies before<br /> and after encounters, rather than during. Establishing and maintaining<br /> good Zones of Control gives you better mobility and control over most other<br /> aspects of the game, even against stronger units less well positioned.<br /> <br /> Your units influence space beyond the hex they're standing on.<br /> The total area of influence includes the hexes adjacent to the units<br /> and ''this'' is the Zone Of Control. When strong opposing units<br /> approach your weaker ones, pay particular attention to the ZoC<br /> and terrain types. Combine the ZoC of your units to form a solid barrier.<br /> Your goal is to rearrange your units such that the opponent's attack<br /> occurs where your units are well positioned defensively and at the worst<br /> time of day for opposing units.<br /> Check that none of your units can be attacked by more than two enemy units<br /> ''and'' that no enemy unit can pass between them.<br /> In this case, you spread your units out, extending your ZoC and forcing<br /> the enemy to select one or more targets.<br /> <br /> In most cases, the opponent will target one unit. You should<br /> ensure that each of your units is within the ZoC of at least two others.<br /> So when the enemy hits one unit, you can close in (encircle, encircle...)<br /> until reinforcements arrive. It is often as important to hold a ZoC<br /> as it is a village or passage.<br /> <br /> While ZoC isn't very important against slow moving units, it is<br /> very effective against fast ones, such as horsemen, bats, ghosts,<br /> and wolf riders. The approach to handling these is assign two or<br /> three of your fastest units, target one long range opposing unit<br /> and spread yours out defensively between its target (usually villages)<br /> and itself in a semi-circle or line. Move these units toward the enemy<br /> so that it has increasingly less space to move. When it is within your ZoC,<br /> encircle and kill. Move on to the next long range unit and repeat.<br /> <br /> After the first round (when everyone has recruited), all the units are<br /> grouped, so try to create a ZoC against all of the long range units<br /> as quickly as you can. In this way you can prevent them from<br /> spreading out, while you systematically encircle and kill each one.<br /> Since the opponent won't have occupied enough villages, there is a<br /> good chance all you'll have left are short range units to deal with.<br /> <br /> Under FoW and Shroud, it is impossible to know what the opponent has<br /> recruited, but it is good practice to check your ZoC around your villages<br /> so you are not surprised by a sudden invasion. Early on, long range<br /> units are used to occupy villages, so the sooner you engage them,<br /> the less villages they can possess. Creating a ZoC quickly around<br /> unoccupied villages allows you to possess them at your leisure and keep them.<br /> <br /> Another use in ZoC is deciding when and where battles will be fought.<br /> If the opponent moves into your ZoC, but positioned near unfavourable<br /> attack terrain, you have several choices. Either attack anyway,<br /> which is mostly bad, wait for the opponent to attack on its next turn,<br /> which gives it the choice of target, or move your units out of its ZoC<br /> to favourable terrain. You can check how far forward the units can move<br /> and place guard units to maintain your ZoC and centralise the others<br /> behind and protecting the guards. This forces the opponent to commit<br /> and gives you time to prepare a tactical counter-attack. Keep your<br /> guards guarding! If the ZoC crumbles your units will be overwhelmed.<br /> <br /> The ZoC is effective when wounded units need to pass through hostile areas.<br /> Rather than closing in, form a large circle around the wounded presenting<br /> a much wider perimeter.<br /> This makes it harder for opposing units to attack all yours and allows you<br /> to keep healthy units within the ZoC and leap-frog when needed.<br /> <br /> On approaching an opponent's castle, ZoC can be critical to your success.<br /> In some scenarios events are triggered when you occupy hexes directly next<br /> to a castle hex. Make sure the approaching units keep their distance from the<br /> castle, but within their ZoC. When assembled, move directly on to the castle.<br /> <br /> For skirmishing units who ignore ZoC, you have little choice but build a solid<br /> wall of units. Alternatively, you may make a ZoC to block the typical units and<br /> prepare a welcoming party for the skirmishers.<br /> <br /> In a campaign scenario, where the objective is to move a unit to a certain point<br /> on the map (often specified by a signpost) you can use more unimportant units<br /> and ZoC by placing them a space or two away from your leader and a space apart<br /> from each other, since in battle units can quite suddenly die, and you don't want<br /> that one to be your leader.<br /> <br /> ==== Encirclement ====<br /> The encircling tactic by two units is very powerful, particularly against long range units. By placing two units on either side, you limit the opposing unit to 1 hex move in any direction. When the unit sidesteps in the following turn, you can re-encircle.<br /> This means you can hold the unit until reinforcements arrive and then adopt a<br /> leap-frog approach against very strong units.<br /> <br /> === Retreating ===<br /> <br /> Sometimes the battle doesn't go your way. Either you battle to the last unit, or<br /> retreat. The purpose of retreating is to regroup your units more effectively and<br /> give them time to heal. Retreating can be organised with a reverse leap-frog<br /> approach, where you give ground, encouraging the opponent to push forward.<br /> Now your healers are in front and moving toward better terrain<br /> where you can make a final stand.<br /> <br /> Being prepared for, and knowing when to retreat, is also important.<br /> Too often a player tries to retreat, but has no reinforcements to halt the retreat.<br /> Try to leave a &quot;safe zone&quot; on a flank, protected by ZoC, where you can pull back.<br /> <br /> The real problem with retreating is putting distance between your units and the<br /> opponents. If they can move faster than yours, you may have to setup a ZoC to<br /> last long enough for you to get your slow units to safety. Invisibility units<br /> are the best because they cannot be seen and will take the opponent valuable<br /> turns to find them. Once the group is safe, they can slip away unnoticed.<br /> Sometimes sending out a unit or two as a kamikaze works to slow them down -<br /> if the exp they gain matters less to them than saving more of your units does to you.<br /> <br /> &lt;noinclude&gt;=== See Also ===<br /> <br /> * [[GettingStarted]]<br /> * [[WesnothManual]]<br /> * [[PlayingOrcs]]<br /> * [[PlayingUndead]]<br /> * [[BestForumStrategies]]<br /> * [[CampaignStrategies]]<br /> * [[Advanced Tactics (Russian)]]<br /> * [[Advanced Tactics (French)]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=AdvancedTactics&diff=8622 2006-03-28T04:21:17Z

<p>Placid: /* Backstab */ quote</p> <hr /> <div>This page assumes that the reader has read [[GettingStarted]] and is familiar with the [[WesnothManual]].<br /> It assumes you have played enough games to be familiar with the system,<br /> and know how to push units around, and are now looking for insight in how to<br /> outthink the AI or a human opponent.<br /> Some tactics are only useful in specific circumstances and would be foolish at other times.<br /> Pick and choose those that fit your particular style.<br /> Do you overwhelm your opponent with sheer numbers, or a few well-chosen<br /> high-level units? Do you prefer to &quot;roleplay&quot; one race?<br /> Do you want to play many scenarios, or replay one over and over until you achieve the perfect game?<br /> <br /> <br /> === Strategy ===<br /> ==== Fight unfair ====<br /> From Sun Tsu to &quot;Shock and Awe&quot;, military writers have stressed that<br /> one must not enter into a conflict unless substantially stronger<br /> than your enemy. In Wesnoth, this means<br /> * more units<br /> * better (stronger, higher level) units, and<br /> * superior healing ability in your second line.<br /> <br /> Napoleon was especially skilled at maneuvering his forces so as to gain an<br /> advantage even when outnumbered. By attacking his enemy in the center, he broke<br /> their lines and divided the enemy forces in two. Then, a small detachment<br /> fortified their position and held off one flank, while Napoleon's main<br /> force attacked the now outnumbered other half. After reducing the<br /> first half, the main force would rejoin the flank-holders and destroy the<br /> remaining half. (This strategy is known as &quot;defeat in detail&quot;.)<br /> <br /> To implement this in Wesnoth, leave a few units with many hit points<br /> in favorable terrain on one flank, while the majority of your force<br /> attacks on a different front.<br /> For example, two red and one white mage, or three paladins.<br /> By combining healers and the healing effect of villages,<br /> a small force can hold off superior numbers for a very long time.<br /> <br /> ==== Feints ====<br /> You can misdirect the AI (and a surprising number of human opponents)<br /> by sending a few units towards an objective like an enemy leader, village,<br /> or bridge. They will overreact and position their units badly.<br /> Similarly, you can send fast units behind the enemy lines to capture villages.<br /> Do not attempt to hold them; instead move onto the next while the enemy diverts<br /> front line troops or reinforcements.<br /> Flying units are particularly adept at this since they ignore terrain.<br /> Sometimes a feint can turn into your main offensive as well,<br /> if the enemy calls a bluff and ignores your feinting units.<br /> <br /> ==== Bounding (or leap frog) ====<br /> Every strategist throughout history warns to &quot;keep a reserve&quot;.<br /> In Wesnoth, this means that you must not attack with all your units.<br /> Instead, hold back units to exploit holes caused by your initial attacks.<br /> Or, you might need to move a fresh unit with many hit points to the<br /> front line so they can 'take a beating' and hold your lines.<br /> <br /> In modern times, the &quot;reserve&quot; concept has been expanded as follows.<br /> Divide your main force into two groups, and attack with the first<br /> while holding the second back. When the first group is chewed up,<br /> withdraw it to healers or villages, while you attack with the second group.<br /> This approach allows you to distribute experience more evenly among your units,<br /> particularly useful in a longer campaign.<br /> However, if you need the higher-level units, selecting which units deliver a fatal blow levels units faster.<br /> This way, you are less likely to lose units with higher exp,<br /> resulting in more units succeeding in leveling up.<br /> <br /> Do not use high level units, and definitely not your commander,<br /> to guard the healers or villages, as the enemy might focus on them instead,<br /> and attack the wounded seeking aid.<br /> <br /> Sometimes, if it is a favorable time of day, you can quickly achieve victory<br /> with an all-out assault. If the enemy is clearly weaker then you, or the conditions are right, this can be an effective<br /> strategy. Most of the time, however, commanders are advised to use other, more elegant strategies.<br /> <br /> ==== Small and strong ====<br /> Develop a small core group of high level units. Recall a strike force<br /> for one or two turns, then move off in a tight pack.<br /> Most should be level 2, with a few level 3 units to hold the flanks or<br /> commit in the 2-3 most decisive rounds.<br /> With this strategy, you'll need fewer villages to provide income,<br /> and thus be less distracted with acquiring them.<br /> <br /> Remember to recruit level 1 units to absorb the enemy's first attacks,<br /> as well as for feints and holding unimportant villages.<br /> Allow those that survive to finish off dying enemy units to replace<br /> any of your core group that make the final sacrifice.<br /> In other words, since some of your leveled units are expected to die,<br /> you need to level up new units to replace them.<br /> <br /> ==== Hit Point Conservation ====<br /> Hit points are a unit's only non-renewable resource.<br /> Choose the attack which causes your unit the least damage,<br /> not deals out the most to the enemy.<br /> For example, assume you are attacking a unit that does 6-3 close combat,<br /> and has no range attack.<br /> Your unit has a 4-4 close combat and a 3-3 range attack.<br /> Consider the tactical situation carefully.<br /> Do you need to kill the unit this turn?<br /> Is it on a village or next to a healer?<br /> Do not automatically accept the computer's recommendation<br /> (it is simply the attack likely to do the most<br /> damage, regardless of how much you take!).<br /> <br /> Remember, when a unit levels up, it regenerates its full HP allowance.<br /> <br /> Finally, attacking an enemy leader, especially in a castle,<br /> is an expensive proposition, even if you use magical attacks.<br /> Expect to lose units while wearing down its hit points.<br /> <br /> <br /> === Weapon specialties ===<br /> ==== Backstab ====<br /> {{Quote|<br /> |align=center<br /> |quote=&quot;Thieves are deft of foot, and elusive, making them difficult to hit. Being skilled at backstabbing, thieves do double damage when attacking an enemy that has an ally of the thief on its opposite side. Being of chaotic disposition, thieves fight better at night than during the day.&quot;<br /> |source=Thief description<br /> |}}<br /> <br /> Assassins, Nightgaunts, Rogues, Shadows and Thieves can backstab.<br /> A Thief costs 12 gold and has base attack of 4-3. But with a backstab,<br /> it does an impressive 8-3, the equivalent of most Level 2 units.<br /> Backstabbing at night with a Strong Thief does 12-3.<br /> After 24 Experience Points, they level up to a Rogue doing 6-3 base...<br /> <br /> You don't have to ''attack'' with another unit to get the backstab<br /> bonus -- there just needs to be a unit on the opposite side of the enemy.<br /> The ally can even move after the backstab, if it didn't use up its moves<br /> by moving into the enemy's Zone of Control this turn.<br /> Thieves work well in pairs against weak or unsupported units.<br /> They can surround a unit and attack it turn after turn.<br /> <br /> It's often effective to use units with backstab in pairs, so that each <br /> provides the bonus to the other. This is especially effective with <br /> Shadows, due to their good movement rate. Keep one or two such pairs <br /> around your flanks to ambush lone scouts and village-stealers.<br /> <br /> ==== Slow ====<br /> Shamans, being slow, weak, and of limited firepower, need to be<br /> used carefully, but don't dismiss their offensive ability.<br /> Many enemy units such as Trolls (not to mention Troll Warriors!), Orcish Grunts,<br /> and Horsemen have two powerful attacks.<br /> You can cripple them for a round by Slowing them, effectively halving their attacks.<br /> <br /> Of course this tactic is even more useful for your higher-level units:<br /> Druids, Shydes, and Goblin Pillagers.<br /> <br /> ==== Healing and Curing ====<br /> Move your healers in pairs so that you retain the<br /> freedom to use them in combat when appropriate without having to retire<br /> to a village afterward.<br /> Remember the difference between healing and curing, put your better healers<br /> where they will be more needed.<br /> <br /> Don't forget that with a Curing unit nearby, you needn't fear poison.<br /> An assassin's darts are only a serious threat if they can poison an unsupported unit.<br /> Your Druid or White Mage will cure the poison before it has time to work,<br /> (However, they cannot remove damage from a unit on the same turn they cure<br /> poison from that unit). and they can cure poison from ''every'' adjacent unit -<br /> irrespective of damage they have to heal.<br /> <br /> ==== Poison ====<br /> <br /> When using poisonous units (Ghouls, Orcish Assassins, Assassins), your goal should be to distribute their poison attack among as many units as possible, rather than concentrating on a single enemy. Units that are already poisoned should be a low priority for your other units' attacks as well, unless they can score a kill.<br /> <br /> Don't underestimate the usage of poison against regenerating units, or any unit in a village next to a curer. While the healing will remove the poison, it does so in lieu of healing hit points. Repeated poisonings can prevent these (often tough or hard-to-hit) units from recovering while your other units whittle them down.<br /> <br /> ==== Swarm ====<br /> <br /> When a unit's attack is listed as &quot;swarm&quot;, the number of attacks per round is based on its current fraction of maximum health. That is to say, if a unit with swarm is at 3/4 health, it will only do 3/4 of its maximum attacks. This does not effect the damage of each attack.<br /> <br /> If you are the owner of such a unit then keeping it in good health should be your top priority. If you are facing a swarmer, the best idea is to poison it and then avoid it as they are usually high level monsters. As of 1.1.1 using &quot;slow&quot; on these units is very effective as it halves their movement speed, making avoiding them while the poison works easier. Once they are at low health, move in for the kill.<br /> <br /> (From the manual - Henkutsu_tama)<br /> <br /> === Recruiting ===<br /> <br /> Remember that your commander may recruit units when standing on ''any'' Keep tile,<br /> not only the one you start on. If you have two enemies, where one is some<br /> distance beyond the other (like in 'The Siege of Elensefar'), you recruit enough<br /> units to take out the first enemy Commander (and posssibly hold off the second<br /> enemy's front troops), then you move onto the slain Commander's Keep, and<br /> recruit the units you need to take out the remaining opposition.<br /> This saves you money in the long run, and keeps your Commander closer<br /> to the action so he may level up sooner.<br /> <br /> If there are several enemies with significant difference in their strength<br /> of arms, first concentrate on the weakest, or else the one with the<br /> highest income potential.<br /> Move your Commander along with your troops, and after you have wiped<br /> this enemy out, use their Castle as your new base.<br /> This has the added benefit of protecting your Commander, often a target<br /> of enemy troops, so you don't need to recruit units only for protecting him,<br /> while your main force is engaged somewhere else.<br /> In the end, this will save you lots of gold.<br /> Such tactics are essential on maps with many opponents,<br /> for example against the AI on multiplayer map 'Dwarven Doors'.<br /> <br /> ==== Plan placement of units ====<br /> Place recruited and recalled units manually.<br /> Choose the best castle tile for a unit to be placed by clicking on the<br /> tile before recruiting or recalling.<br /> This way you can often capture villages a turn earlier,<br /> or move units to critical map squares before your opponent.<br /> <br /> For maps with narrow passages leading out of the castle<br /> (like Bay of Pearls or some of the random underground maps in<br /> Heir to the Throne), recruit or recall pairs of slow and fast units.<br /> Both units in such a pair will then be able to use their maximum<br /> movement without impeding each other. So recruit an Elvish Fighter<br /> together with a Horseman, or even an Elvish Fighter with an Elvish Archer.<br /> <br /> ==== Unit Choice ====<br /> * Some units, such as Orcish Grunts or Horseman, have no ranged attack. Take advantage of this by using units that are skilled in both melee and ranged, such as Elvish Rangers, so that when you attack you will never be hurt, but yet will not be at a disadvantage when you are attacked. The same goes for units with no melee attack, such at Dark Adepts.<br /> * When a battle is raging, use fast-moving units (your scouts) to distract the enemy by sneaking past enemy troops and conquering enemy villages, cutting off their gold supply or sometimes forcing them to split up their armies.<br /> * If a battle occurs at a river or some other narrow pass, it can be beneficial to use skirmishing units such as Duelists to easily cross the river and surround your opponent or use airborne units like Gryphons to use the river squares without being at a great disadvantage.<br /> * If you need to cross a large body of shallow water, mountains, cave floor, or other difficult terrain, use units whose moves are divisible by their movement on such terrain so moves don't go to waste. For example, if a unit takes three moves to get through one water tile, make sure it has three, six, or nine movement. Recalling 'quick' units can help ensure you've chosen the right ones. If you recall a unit with five movement points, they will only be able to move one hex per turn in terrain that requires three movement points, while a similar unit with six movement points can move two hexes per turn.<br /> * Units such as Elvish Fighters that are cheap to produce in mass and that have both decent melee and ranged attacks can often be good for holding your front lines, since they will cause harm to their opponents no matter what they are. A front line of horsemen, on the other hand, is not good for holding a position, for they are costly, fall quickly to enemy archers, and probably will never be able to strike back.<br /> <br /> === Know the Battlefield ===<br /> <br /> ==== Reconnaissance - Know the Map ====<br /> While attack is influenced by the time of day, defense is affected<br /> by terrain. First find all the castles and note the different kinds<br /> of terrain immediately surrounding them. If you're playing under<br /> Shroud, send out two or three scouts to locate the castles.<br /> This is also often worth it on Fog of War, because you learn<br /> what faction your enemy is (if you don't know already) and<br /> how defended their castle is. Expect to recruit more when they die.<br /> The knowledge they provide is worth more than their cost.<br /> <br /> ==== Survey - Know the Terrain ====<br /> Take an overall look at the size of each terrain type and note which<br /> are the most important.<br /> This affects what units to select and their overall effectiveness.<br /> Then examine whether the main terrain is evenly<br /> distributed, scattered, or in a few large areas.<br /> Note what terrain you want to avoid and why.<br /> Mountains and deep water are bad for all but a few unit types.<br /> These act as walls which the opponents can use to trap you:<br /> of course, you can do likewise to your opponents. If you have<br /> saved some of your starting gold, you can also decide which units will<br /> be better for reinforcements based off a more common terrain.<br /> <br /> ==== Transport - Know the Pathways ====<br /> Try to link advantageous terrain areas together in your mind<br /> from where your units are (your castle at start of play)<br /> to opposing ''and'' friendly castles. Use villages scattered between<br /> you and the target to influence the route to take, especially if you<br /> can't recruit any healing units.<br /> Decide which terrain is most favourable for your units and<br /> less favourable for the enemy.<br /> If you goal is to reach an object or hex, then do the same for that.<br /> <br /> If one route proves difficult, switch to another. Get to know<br /> which routes work best for different units and locate meeting<br /> places to regroup units.<br /> Try to keep the opponents guessing what you're going to do next.<br /> By using several adjacent routes to a target, the opponents<br /> will have a tougher time stopping your advance.<br /> In some cases it is easier to send a main group directly towards<br /> the target and use fast units to circle around behind.<br /> <br /> ==== Features - Know the Traps ====<br /> Note carefully where favourable terrain on either side of<br /> unfavourable reach their closest point. These are defense positions<br /> for you to ambush approaching opponents (with or without a thief) and<br /> provide protection for friendly units. Sometimes the terrain forms<br /> passages for units to pass through quickly. Check whether it takes<br /> fewer turns to move around slow terrain than through it.<br /> In slow terrain, it is tougher to encircle units and immobilise them,<br /> so drive them toward better suited terrain (using ZoC, see elsewhere)<br /> and encircle there.<br /> <br /> <br /> ==== Distance - Watch the Time ====<br /> Use caution when setting up your front line and advancing immediately, as often the time of day will be exactly in it's least advantageous point right when you meet your enemies. If you wait a few turns just passing the time by capturing nearby villages and meet the enemy at First Watch/Dawn, respectively, you can cut down the majority of the enemie's army before they can do anything about it. Also, if you find yourself in a evenly matched or losing position during your worst part of the day it can be ideal to fall back to villages or simply hold tight without attacking the enemy, as you want the battle to progress as slowly as possible during theis part of the day. (Note: If you have units that can attack at no risk [mages to trolls, for example] don't waste their actions, keep on fighting no matter what.)<br /> <br /> === Zone of Control (ZoC) ===<br /> <br /> The Zone Of Control allows you to build artificial barriers at will.<br /> With it, you can reduce the likelyhood that a weaker, injured unit will<br /> be killed, by reducing the number or kind of enemies that can reach it.<br /> It is hard to measure who has Movement Control because it depends<br /> on where the units are positioned more than how many there are.<br /> Although this is a tactical device, it is more strategically<br /> significant than tactical because Zone of Control applies before<br /> and after encounters, rather than during. Establishing and maintaining<br /> good Zones of Control gives you better mobility and control over most other<br /> aspects of the game, even against stronger units less well positioned.<br /> <br /> Your units influence space beyond the hex they're standing on.<br /> The total area of influence includes the hexes adjacent to the units<br /> and ''this'' is the Zone Of Control. When strong opposing units<br /> approach your weaker ones, pay particular attention to the ZoC<br /> and terrain types. Combine the ZoC of your units to form a solid barrier.<br /> Your goal is to rearrange your units such that the opponent's attack<br /> occurs where your units are well positioned defensively and at the worst<br /> time of day for opposing units.<br /> Check that none of your units can be attacked by more than two enemy units<br /> ''and'' that no enemy unit can pass between them.<br /> In this case, you spread your units out, extending your ZoC and forcing<br /> the enemy to select one or more targets.<br /> <br /> In most cases, the opponent will target one unit. You should<br /> ensure that each of your units is within the ZoC of at least two others.<br /> So when the enemy hits one unit, you can close in (encircle, encircle...)<br /> until reinforcements arrive. It is often as important to hold a ZoC<br /> as it is a village or passage.<br /> <br /> While ZoC isn't very important against slow moving units, it is<br /> very effective against fast ones, such as horsemen, bats, ghosts,<br /> and wolf riders. The approach to handling these is assign two or<br /> three of your fastest units, target one long range opposing unit<br /> and spread yours out defensively between its target (usually villages)<br /> and itself in a semi-circle or line. Move these units toward the enemy<br /> so that it has increasingly less space to move. When it is within your ZoC,<br /> encircle and kill. Move on to the next long range unit and repeat.<br /> <br /> After the first round (when everyone has recruited), all the units are<br /> grouped, so try to create a ZoC against all of the long range units<br /> as quickly as you can. In this way you can prevent them from<br /> spreading out, while you systematically encircle and kill each one.<br /> Since the opponent won't have occupied enough villages, there is a<br /> good chance all you'll have left are short range units to deal with.<br /> <br /> Under FoW and Shroud, it is impossible to know what the opponent has<br /> recruited, but it is good practice to check your ZoC around your villages<br /> so you are not surprised by a sudden invasion. Early on, long range<br /> units are used to occupy villages, so the sooner you engage them,<br /> the less villages they can possess. Creating a ZoC quickly around<br /> unoccupied villages allows you to possess them at your leisure and keep them.<br /> <br /> Another use in ZoC is deciding when and where battles will be fought.<br /> If the opponent moves into your ZoC, but positioned near unfavourable<br /> attack terrain, you have several choices. Either attack anyway,<br /> which is mostly bad, wait for the opponent to attack on its next turn,<br /> which gives it the choice of target, or move your units out of its ZoC<br /> to favourable terrain. You can check how far forward the units can move<br /> and place guard units to maintain your ZoC and centralise the others<br /> behind and protecting the guards. This forces the opponent to commit<br /> and gives you time to prepare a tactical counter-attack. Keep your<br /> guards guarding! If the ZoC crumbles your units will be overwhelmed.<br /> <br /> The ZoC is effective when wounded units need to pass through hostile areas.<br /> Rather than closing in, form a large circle around the wounded presenting<br /> a much wider perimeter.<br /> This makes it harder for opposing units to attack all yours and allows you<br /> to keep healthy units within the ZoC and leap-frog when needed.<br /> <br /> On approaching an opponent's castle, ZoC can be critical to your success.<br /> In some scenarios events are triggered when you occupy hexes directly next<br /> to a castle hex. Make sure the approaching units keep their distance from the<br /> castle, but within their ZoC. When assembled, move directly on to the castle.<br /> <br /> For skirmishing units who ignore ZoC, you have little choice but build a solid<br /> wall of units. Alternatively, you may make a ZoC to block the typical units and<br /> prepare a welcoming party for the skirmishers.<br /> <br /> In a campaign scenario, where the objective is to move a unit to a certain point<br /> on the map (often specified by a signpost) you can use more unimportant units<br /> and ZoC by placing them a space or two away from your leader and a space apart<br /> from each other, since in battle units can quite suddenly die, and you don't want<br /> that one to be your leader.<br /> <br /> ==== Encirclement ====<br /> The encircling tactic by two units is very powerful, particularly against long range units. By placing two units on either side, you limit the opposing unit to 1 hex move in any direction. When the unit sidesteps in the following turn, you can re-encircle.<br /> This means you can hold the unit until reinforcements arrive and then adopt a<br /> leap-frog approach against very strong units.<br /> <br /> === Retreating ===<br /> <br /> Sometimes the battle doesn't go your way. Either you battle to the last unit, or<br /> retreat. The purpose of retreating is to regroup your units more effectively and<br /> give them time to heal. Retreating can be organised with a reverse leap-frog<br /> approach, where you give ground, encouraging the opponent to push forward.<br /> Now your healers are in front and moving toward better terrain<br /> where you can make a final stand.<br /> <br /> Being prepared for, and knowing when to retreat, is also important.<br /> Too often a player tries to retreat, but has no reinforcements to halt the retreat.<br /> Try to leave a &quot;safe zone&quot; on a flank, protected by ZoC, where you can pull back.<br /> <br /> The real problem with retreating is putting distance between your units and the<br /> opponents. If they can move faster than yours, you may have to setup a ZoC to<br /> last long enough for you to get your slow units to safety. Invisibility units<br /> are the best because they cannot be seen and will take the opponent valuable<br /> turns to find them. Once the group is safe, they can slip away unnoticed.<br /> Sometimes sending out a unit or two as a kamikaze works to slow them down -<br /> if the exp they gain matters less to them than saving more of your units does to you.<br /> <br /> &lt;noinclude&gt;=== See Also ===<br /> <br /> * [[GettingStarted]]<br /> * [[WesnothManual]]<br /> * [[PlayingOrcs]]<br /> * [[PlayingUndead]]<br /> * [[BestForumStrategies]]<br /> * [[CampaignStrategies]]<br /> * [[Advanced Tactics (Russian)]]<br /> * [[Advanced Tactics (French)]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8621 2006-03-28T04:20:44Z

<p>Placid: </p> <hr /> <div>{|width=&quot;80%&quot; align=&quot;center&quot; cellspacing=&quot;4&quot; cellpadding=&quot;4&quot; style=&quot;border: 4px solid #aaa; font-size: 90%; padding: 4px; margin: 1em; background-color: #f9f9f9;&quot;<br /> |-<br /> |align=&quot;left&quot;|''{{{quote}}}''<br /> |-<br /> |align=&quot;right&quot;|&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Quotation templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8620 2006-03-28T04:18:22Z

<p>Placid: </p> <hr /> <div>{|width=&quot;{{{width}}}&quot; align=&quot;{{{align}}}&quot; cellspacing=&quot;4&quot; cellpadding=&quot;4&quot; style=&quot;border: 4px solid #aaa; font-size: 90%; padding: 4px; margin: 1em; background-color: #f9f9f9;&quot;<br /> |-<br /> ||''{{{quote}}}''&lt;br&gt;&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> width=<br /> |align=<br /> |quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Quotation templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:Quote&diff=8619 2006-03-28T04:15:55Z

<p>Placid: create</p> <hr /> <div>{|width=&quot;{{{width}}}&quot; align=&quot;{{{align}}}&quot; cellspacing=&quot;4&quot; cellpadding=&quot;4&quot; style=&quot;border: 4px solid #aaa; font-size: 90%; padding: 4px; margin: 1em; background-color: #f9f9f9;&quot;<br /> |-<br /> |align=&quot;center&quot;|''{{{quote}}}''&lt;br&gt;&amp;mdash;{{{source}}}<br /> |}&lt;noinclude&gt;<br /> ----<br /> == Instructions ==<br /> The '''quote box''' template allows you to easily put a quote (and its source) inside a box. This is useful in articles where you are short on images and want to add some sort of graphic, or you just want to set off an important or interesting quote away from the main text.<br /> <br /> As a stylistic device, the quoted text is ''italicized'' in the box by default, so you don't need to put quote marks (&quot; &quot;) around the quoted text; the italics do the work of quote marks in this context. (Should you want to defeat any part of the default italics in the quote, put two apostrophes on each side of the quoted text you do not want italicized, &lt;nowiki&gt;''like this''&lt;/nowiki&gt;.)<br /> <br /> You can pick how wide you want the box (as px or a percentage), and how to align it (center, right, left). The parameters are:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> width=<br /> |align=<br /> |quote=<br /> |source=<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> For example, entering the following:<br /> <br /> &lt;pre&gt;<br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> &lt;/pre&gt;<br /> <br /> <br /> Produces this:<br /> <br /> {{Quote_box|<br /> width=45%<br /> |align=right<br /> |quote=Cry &quot;Havoc,&quot; and let slip the dogs of war.<br /> |source=[[William Shakespeare]], ''[[Julius Caesar (play)|Julius Caesar]]'', Act III, Scene I.<br /> |}}<br /> <br /> [[Category:Quotation templates|{{PAGENAME}}]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=AdvancedTactics&diff=8618 2006-03-28T04:08:14Z

<p>Placid: /* Backstab */ quote</p> <hr /> <div>This page assumes that the reader has read [[GettingStarted]] and is familiar with the [[WesnothManual]].<br /> It assumes you have played enough games to be familiar with the system,<br /> and know how to push units around, and are now looking for insight in how to<br /> outthink the AI or a human opponent.<br /> Some tactics are only useful in specific circumstances and would be foolish at other times.<br /> Pick and choose those that fit your particular style.<br /> Do you overwhelm your opponent with sheer numbers, or a few well-chosen<br /> high-level units? Do you prefer to &quot;roleplay&quot; one race?<br /> Do you want to play many scenarios, or replay one over and over until you achieve the perfect game?<br /> <br /> <br /> === Strategy ===<br /> ==== Fight unfair ====<br /> From Sun Tsu to &quot;Shock and Awe&quot;, military writers have stressed that<br /> one must not enter into a conflict unless substantially stronger<br /> than your enemy. In Wesnoth, this means<br /> * more units<br /> * better (stronger, higher level) units, and<br /> * superior healing ability in your second line.<br /> <br /> Napoleon was especially skilled at maneuvering his forces so as to gain an<br /> advantage even when outnumbered. By attacking his enemy in the center, he broke<br /> their lines and divided the enemy forces in two. Then, a small detachment<br /> fortified their position and held off one flank, while Napoleon's main<br /> force attacked the now outnumbered other half. After reducing the<br /> first half, the main force would rejoin the flank-holders and destroy the<br /> remaining half. (This strategy is known as &quot;defeat in detail&quot;.)<br /> <br /> To implement this in Wesnoth, leave a few units with many hit points<br /> in favorable terrain on one flank, while the majority of your force<br /> attacks on a different front.<br /> For example, two red and one white mage, or three paladins.<br /> By combining healers and the healing effect of villages,<br /> a small force can hold off superior numbers for a very long time.<br /> <br /> ==== Feints ====<br /> You can misdirect the AI (and a surprising number of human opponents)<br /> by sending a few units towards an objective like an enemy leader, village,<br /> or bridge. They will overreact and position their units badly.<br /> Similarly, you can send fast units behind the enemy lines to capture villages.<br /> Do not attempt to hold them; instead move onto the next while the enemy diverts<br /> front line troops or reinforcements.<br /> Flying units are particularly adept at this since they ignore terrain.<br /> Sometimes a feint can turn into your main offensive as well,<br /> if the enemy calls a bluff and ignores your feinting units.<br /> <br /> ==== Bounding (or leap frog) ====<br /> Every strategist throughout history warns to &quot;keep a reserve&quot;.<br /> In Wesnoth, this means that you must not attack with all your units.<br /> Instead, hold back units to exploit holes caused by your initial attacks.<br /> Or, you might need to move a fresh unit with many hit points to the<br /> front line so they can 'take a beating' and hold your lines.<br /> <br /> In modern times, the &quot;reserve&quot; concept has been expanded as follows.<br /> Divide your main force into two groups, and attack with the first<br /> while holding the second back. When the first group is chewed up,<br /> withdraw it to healers or villages, while you attack with the second group.<br /> This approach allows you to distribute experience more evenly among your units,<br /> particularly useful in a longer campaign.<br /> However, if you need the higher-level units, selecting which units deliver a fatal blow levels units faster.<br /> This way, you are less likely to lose units with higher exp,<br /> resulting in more units succeeding in leveling up.<br /> <br /> Do not use high level units, and definitely not your commander,<br /> to guard the healers or villages, as the enemy might focus on them instead,<br /> and attack the wounded seeking aid.<br /> <br /> Sometimes, if it is a favorable time of day, you can quickly achieve victory<br /> with an all-out assault. If the enemy is clearly weaker then you, or the conditions are right, this can be an effective<br /> strategy. Most of the time, however, commanders are advised to use other, more elegant strategies.<br /> <br /> ==== Small and strong ====<br /> Develop a small core group of high level units. Recall a strike force<br /> for one or two turns, then move off in a tight pack.<br /> Most should be level 2, with a few level 3 units to hold the flanks or<br /> commit in the 2-3 most decisive rounds.<br /> With this strategy, you'll need fewer villages to provide income,<br /> and thus be less distracted with acquiring them.<br /> <br /> Remember to recruit level 1 units to absorb the enemy's first attacks,<br /> as well as for feints and holding unimportant villages.<br /> Allow those that survive to finish off dying enemy units to replace<br /> any of your core group that make the final sacrifice.<br /> In other words, since some of your leveled units are expected to die,<br /> you need to level up new units to replace them.<br /> <br /> ==== Hit Point Conservation ====<br /> Hit points are a unit's only non-renewable resource.<br /> Choose the attack which causes your unit the least damage,<br /> not deals out the most to the enemy.<br /> For example, assume you are attacking a unit that does 6-3 close combat,<br /> and has no range attack.<br /> Your unit has a 4-4 close combat and a 3-3 range attack.<br /> Consider the tactical situation carefully.<br /> Do you need to kill the unit this turn?<br /> Is it on a village or next to a healer?<br /> Do not automatically accept the computer's recommendation<br /> (it is simply the attack likely to do the most<br /> damage, regardless of how much you take!).<br /> <br /> Remember, when a unit levels up, it regenerates its full HP allowance.<br /> <br /> Finally, attacking an enemy leader, especially in a castle,<br /> is an expensive proposition, even if you use magical attacks.<br /> Expect to lose units while wearing down its hit points.<br /> <br /> <br /> === Weapon specialties ===<br /> ==== Backstab ====<br /> :''&quot;Thieves are deft of foot, and elusive, making them difficult to hit. Being skilled at backstabbing, thieves do double damage when attacking an enemy that has an ally of the thief on its opposite side. Being of chaotic disposition, thieves fight better at night than during the day.&quot;'' --Thief_description<br /> <br /> Assassins, Nightgaunts, Rogues, Shadows and Thieves can backstab.<br /> A Thief costs 12 gold and has base attack of 4-3. But with a backstab,<br /> it does an impressive 8-3, the equivalent of most Level 2 units.<br /> Backstabbing at night with a Strong Thief does 12-3.<br /> After 24 Experience Points, they level up to a Rogue doing 6-3 base...<br /> <br /> You don't have to ''attack'' with another unit to get the backstab<br /> bonus -- there just needs to be a unit on the opposite side of the enemy.<br /> The ally can even move after the backstab, if it didn't use up its moves<br /> by moving into the enemy's Zone of Control this turn.<br /> Thieves work well in pairs against weak or unsupported units.<br /> They can surround a unit and attack it turn after turn.<br /> <br /> It's often effective to use units with backstab in pairs, so that each <br /> provides the bonus to the other. This is especially effective with <br /> Shadows, due to their good movement rate. Keep one or two such pairs <br /> around your flanks to ambush lone scouts and village-stealers.<br /> <br /> ==== Slow ====<br /> Shamans, being slow, weak, and of limited firepower, need to be<br /> used carefully, but don't dismiss their offensive ability.<br /> Many enemy units such as Trolls (not to mention Troll Warriors!), Orcish Grunts,<br /> and Horsemen have two powerful attacks.<br /> You can cripple them for a round by Slowing them, effectively halving their attacks.<br /> <br /> Of course this tactic is even more useful for your higher-level units:<br /> Druids, Shydes, and Goblin Pillagers.<br /> <br /> ==== Healing and Curing ====<br /> Move your healers in pairs so that you retain the<br /> freedom to use them in combat when appropriate without having to retire<br /> to a village afterward.<br /> Remember the difference between healing and curing, put your better healers<br /> where they will be more needed.<br /> <br /> Don't forget that with a Curing unit nearby, you needn't fear poison.<br /> An assassin's darts are only a serious threat if they can poison an unsupported unit.<br /> Your Druid or White Mage will cure the poison before it has time to work,<br /> (However, they cannot remove damage from a unit on the same turn they cure<br /> poison from that unit). and they can cure poison from ''every'' adjacent unit -<br /> irrespective of damage they have to heal.<br /> <br /> ==== Poison ====<br /> <br /> When using poisonous units (Ghouls, Orcish Assassins, Assassins), your goal should be to distribute their poison attack among as many units as possible, rather than concentrating on a single enemy. Units that are already poisoned should be a low priority for your other units' attacks as well, unless they can score a kill.<br /> <br /> Don't underestimate the usage of poison against regenerating units, or any unit in a village next to a curer. While the healing will remove the poison, it does so in lieu of healing hit points. Repeated poisonings can prevent these (often tough or hard-to-hit) units from recovering while your other units whittle them down.<br /> <br /> ==== Swarm ====<br /> <br /> When a unit's attack is listed as &quot;swarm&quot;, the number of attacks per round is based on its current fraction of maximum health. That is to say, if a unit with swarm is at 3/4 health, it will only do 3/4 of its maximum attacks. This does not effect the damage of each attack.<br /> <br /> If you are the owner of such a unit then keeping it in good health should be your top priority. If you are facing a swarmer, the best idea is to poison it and then avoid it as they are usually high level monsters. As of 1.1.1 using &quot;slow&quot; on these units is very effective as it halves their movement speed, making avoiding them while the poison works easier. Once they are at low health, move in for the kill.<br /> <br /> (From the manual - Henkutsu_tama)<br /> <br /> === Recruiting ===<br /> <br /> Remember that your commander may recruit units when standing on ''any'' Keep tile,<br /> not only the one you start on. If you have two enemies, where one is some<br /> distance beyond the other (like in 'The Siege of Elensefar'), you recruit enough<br /> units to take out the first enemy Commander (and posssibly hold off the second<br /> enemy's front troops), then you move onto the slain Commander's Keep, and<br /> recruit the units you need to take out the remaining opposition.<br /> This saves you money in the long run, and keeps your Commander closer<br /> to the action so he may level up sooner.<br /> <br /> If there are several enemies with significant difference in their strength<br /> of arms, first concentrate on the weakest, or else the one with the<br /> highest income potential.<br /> Move your Commander along with your troops, and after you have wiped<br /> this enemy out, use their Castle as your new base.<br /> This has the added benefit of protecting your Commander, often a target<br /> of enemy troops, so you don't need to recruit units only for protecting him,<br /> while your main force is engaged somewhere else.<br /> In the end, this will save you lots of gold.<br /> Such tactics are essential on maps with many opponents,<br /> for example against the AI on multiplayer map 'Dwarven Doors'.<br /> <br /> ==== Plan placement of units ====<br /> Place recruited and recalled units manually.<br /> Choose the best castle tile for a unit to be placed by clicking on the<br /> tile before recruiting or recalling.<br /> This way you can often capture villages a turn earlier,<br /> or move units to critical map squares before your opponent.<br /> <br /> For maps with narrow passages leading out of the castle<br /> (like Bay of Pearls or some of the random underground maps in<br /> Heir to the Throne), recruit or recall pairs of slow and fast units.<br /> Both units in such a pair will then be able to use their maximum<br /> movement without impeding each other. So recruit an Elvish Fighter<br /> together with a Horseman, or even an Elvish Fighter with an Elvish Archer.<br /> <br /> ==== Unit Choice ====<br /> * Some units, such as Orcish Grunts or Horseman, have no ranged attack. Take advantage of this by using units that are skilled in both melee and ranged, such as Elvish Rangers, so that when you attack you will never be hurt, but yet will not be at a disadvantage when you are attacked. The same goes for units with no melee attack, such at Dark Adepts.<br /> * When a battle is raging, use fast-moving units (your scouts) to distract the enemy by sneaking past enemy troops and conquering enemy villages, cutting off their gold supply or sometimes forcing them to split up their armies.<br /> * If a battle occurs at a river or some other narrow pass, it can be beneficial to use skirmishing units such as Duelists to easily cross the river and surround your opponent or use airborne units like Gryphons to use the river squares without being at a great disadvantage.<br /> * If you need to cross a large body of shallow water, mountains, cave floor, or other difficult terrain, use units whose moves are divisible by their movement on such terrain so moves don't go to waste. For example, if a unit takes three moves to get through one water tile, make sure it has three, six, or nine movement. Recalling 'quick' units can help ensure you've chosen the right ones. If you recall a unit with five movement points, they will only be able to move one hex per turn in terrain that requires three movement points, while a similar unit with six movement points can move two hexes per turn.<br /> * Units such as Elvish Fighters that are cheap to produce in mass and that have both decent melee and ranged attacks can often be good for holding your front lines, since they will cause harm to their opponents no matter what they are. A front line of horsemen, on the other hand, is not good for holding a position, for they are costly, fall quickly to enemy archers, and probably will never be able to strike back.<br /> <br /> === Know the Battlefield ===<br /> <br /> ==== Reconnaissance - Know the Map ====<br /> While attack is influenced by the time of day, defense is affected<br /> by terrain. First find all the castles and note the different kinds<br /> of terrain immediately surrounding them. If you're playing under<br /> Shroud, send out two or three scouts to locate the castles.<br /> This is also often worth it on Fog of War, because you learn<br /> what faction your enemy is (if you don't know already) and<br /> how defended their castle is. Expect to recruit more when they die.<br /> The knowledge they provide is worth more than their cost.<br /> <br /> ==== Survey - Know the Terrain ====<br /> Take an overall look at the size of each terrain type and note which<br /> are the most important.<br /> This affects what units to select and their overall effectiveness.<br /> Then examine whether the main terrain is evenly<br /> distributed, scattered, or in a few large areas.<br /> Note what terrain you want to avoid and why.<br /> Mountains and deep water are bad for all but a few unit types.<br /> These act as walls which the opponents can use to trap you:<br /> of course, you can do likewise to your opponents. If you have<br /> saved some of your starting gold, you can also decide which units will<br /> be better for reinforcements based off a more common terrain.<br /> <br /> ==== Transport - Know the Pathways ====<br /> Try to link advantageous terrain areas together in your mind<br /> from where your units are (your castle at start of play)<br /> to opposing ''and'' friendly castles. Use villages scattered between<br /> you and the target to influence the route to take, especially if you<br /> can't recruit any healing units.<br /> Decide which terrain is most favourable for your units and<br /> less favourable for the enemy.<br /> If you goal is to reach an object or hex, then do the same for that.<br /> <br /> If one route proves difficult, switch to another. Get to know<br /> which routes work best for different units and locate meeting<br /> places to regroup units.<br /> Try to keep the opponents guessing what you're going to do next.<br /> By using several adjacent routes to a target, the opponents<br /> will have a tougher time stopping your advance.<br /> In some cases it is easier to send a main group directly towards<br /> the target and use fast units to circle around behind.<br /> <br /> ==== Features - Know the Traps ====<br /> Note carefully where favourable terrain on either side of<br /> unfavourable reach their closest point. These are defense positions<br /> for you to ambush approaching opponents (with or without a thief) and<br /> provide protection for friendly units. Sometimes the terrain forms<br /> passages for units to pass through quickly. Check whether it takes<br /> fewer turns to move around slow terrain than through it.<br /> In slow terrain, it is tougher to encircle units and immobilise them,<br /> so drive them toward better suited terrain (using ZoC, see elsewhere)<br /> and encircle there.<br /> <br /> <br /> ==== Distance - Watch the Time ====<br /> Use caution when setting up your front line and advancing immediately, as often the time of day will be exactly in it's least advantageous point right when you meet your enemies. If you wait a few turns just passing the time by capturing nearby villages and meet the enemy at First Watch/Dawn, respectively, you can cut down the majority of the enemie's army before they can do anything about it. Also, if you find yourself in a evenly matched or losing position during your worst part of the day it can be ideal to fall back to villages or simply hold tight without attacking the enemy, as you want the battle to progress as slowly as possible during theis part of the day. (Note: If you have units that can attack at no risk [mages to trolls, for example] don't waste their actions, keep on fighting no matter what.)<br /> <br /> === Zone of Control (ZoC) ===<br /> <br /> The Zone Of Control allows you to build artificial barriers at will.<br /> With it, you can reduce the likelyhood that a weaker, injured unit will<br /> be killed, by reducing the number or kind of enemies that can reach it.<br /> It is hard to measure who has Movement Control because it depends<br /> on where the units are positioned more than how many there are.<br /> Although this is a tactical device, it is more strategically<br /> significant than tactical because Zone of Control applies before<br /> and after encounters, rather than during. Establishing and maintaining<br /> good Zones of Control gives you better mobility and control over most other<br /> aspects of the game, even against stronger units less well positioned.<br /> <br /> Your units influence space beyond the hex they're standing on.<br /> The total area of influence includes the hexes adjacent to the units<br /> and ''this'' is the Zone Of Control. When strong opposing units<br /> approach your weaker ones, pay particular attention to the ZoC<br /> and terrain types. Combine the ZoC of your units to form a solid barrier.<br /> Your goal is to rearrange your units such that the opponent's attack<br /> occurs where your units are well positioned defensively and at the worst<br /> time of day for opposing units.<br /> Check that none of your units can be attacked by more than two enemy units<br /> ''and'' that no enemy unit can pass between them.<br /> In this case, you spread your units out, extending your ZoC and forcing<br /> the enemy to select one or more targets.<br /> <br /> In most cases, the opponent will target one unit. You should<br /> ensure that each of your units is within the ZoC of at least two others.<br /> So when the enemy hits one unit, you can close in (encircle, encircle...)<br /> until reinforcements arrive. It is often as important to hold a ZoC<br /> as it is a village or passage.<br /> <br /> While ZoC isn't very important against slow moving units, it is<br /> very effective against fast ones, such as horsemen, bats, ghosts,<br /> and wolf riders. The approach to handling these is assign two or<br /> three of your fastest units, target one long range opposing unit<br /> and spread yours out defensively between its target (usually villages)<br /> and itself in a semi-circle or line. Move these units toward the enemy<br /> so that it has increasingly less space to move. When it is within your ZoC,<br /> encircle and kill. Move on to the next long range unit and repeat.<br /> <br /> After the first round (when everyone has recruited), all the units are<br /> grouped, so try to create a ZoC against all of the long range units<br /> as quickly as you can. In this way you can prevent them from<br /> spreading out, while you systematically encircle and kill each one.<br /> Since the opponent won't have occupied enough villages, there is a<br /> good chance all you'll have left are short range units to deal with.<br /> <br /> Under FoW and Shroud, it is impossible to know what the opponent has<br /> recruited, but it is good practice to check your ZoC around your villages<br /> so you are not surprised by a sudden invasion. Early on, long range<br /> units are used to occupy villages, so the sooner you engage them,<br /> the less villages they can possess. Creating a ZoC quickly around<br /> unoccupied villages allows you to possess them at your leisure and keep them.<br /> <br /> Another use in ZoC is deciding when and where battles will be fought.<br /> If the opponent moves into your ZoC, but positioned near unfavourable<br /> attack terrain, you have several choices. Either attack anyway,<br /> which is mostly bad, wait for the opponent to attack on its next turn,<br /> which gives it the choice of target, or move your units out of its ZoC<br /> to favourable terrain. You can check how far forward the units can move<br /> and place guard units to maintain your ZoC and centralise the others<br /> behind and protecting the guards. This forces the opponent to commit<br /> and gives you time to prepare a tactical counter-attack. Keep your<br /> guards guarding! If the ZoC crumbles your units will be overwhelmed.<br /> <br /> The ZoC is effective when wounded units need to pass through hostile areas.<br /> Rather than closing in, form a large circle around the wounded presenting<br /> a much wider perimeter.<br /> This makes it harder for opposing units to attack all yours and allows you<br /> to keep healthy units within the ZoC and leap-frog when needed.<br /> <br /> On approaching an opponent's castle, ZoC can be critical to your success.<br /> In some scenarios events are triggered when you occupy hexes directly next<br /> to a castle hex. Make sure the approaching units keep their distance from the<br /> castle, but within their ZoC. When assembled, move directly on to the castle.<br /> <br /> For skirmishing units who ignore ZoC, you have little choice but build a solid<br /> wall of units. Alternatively, you may make a ZoC to block the typical units and<br /> prepare a welcoming party for the skirmishers.<br /> <br /> In a campaign scenario, where the objective is to move a unit to a certain point<br /> on the map (often specified by a signpost) you can use more unimportant units<br /> and ZoC by placing them a space or two away from your leader and a space apart<br /> from each other, since in battle units can quite suddenly die, and you don't want<br /> that one to be your leader.<br /> <br /> ==== Encirclement ====<br /> The encircling tactic by two units is very powerful, particularly against long range units. By placing two units on either side, you limit the opposing unit to 1 hex move in any direction. When the unit sidesteps in the following turn, you can re-encircle.<br /> This means you can hold the unit until reinforcements arrive and then adopt a<br /> leap-frog approach against very strong units.<br /> <br /> === Retreating ===<br /> <br /> Sometimes the battle doesn't go your way. Either you battle to the last unit, or<br /> retreat. The purpose of retreating is to regroup your units more effectively and<br /> give them time to heal. Retreating can be organised with a reverse leap-frog<br /> approach, where you give ground, encouraging the opponent to push forward.<br /> Now your healers are in front and moving toward better terrain<br /> where you can make a final stand.<br /> <br /> Being prepared for, and knowing when to retreat, is also important.<br /> Too often a player tries to retreat, but has no reinforcements to halt the retreat.<br /> Try to leave a &quot;safe zone&quot; on a flank, protected by ZoC, where you can pull back.<br /> <br /> The real problem with retreating is putting distance between your units and the<br /> opponents. If they can move faster than yours, you may have to setup a ZoC to<br /> last long enough for you to get your slow units to safety. Invisibility units<br /> are the best because they cannot be seen and will take the opponent valuable<br /> turns to find them. Once the group is safe, they can slip away unnoticed.<br /> Sometimes sending out a unit or two as a kamikaze works to slow them down -<br /> if the exp they gain matters less to them than saving more of your units does to you.<br /> <br /> &lt;noinclude&gt;=== See Also ===<br /> <br /> * [[GettingStarted]]<br /> * [[WesnothManual]]<br /> * [[PlayingOrcs]]<br /> * [[PlayingUndead]]<br /> * [[BestForumStrategies]]<br /> * [[CampaignStrategies]]<br /> * [[Advanced Tactics (Russian)]]<br /> * [[Advanced Tactics (French)]]<br /> &lt;/noinclude&gt;</div>

Placid https://wiki.wesnoth.org/index.php?title=CampaignTwoBrothers&diff=8617 2006-03-28T03:51:37Z

<p>Placid: /* Translation of Two Brothers */</p> <hr /> <div>== Translation of Two Brothers ==<br /> This is a list of the people currently translating Two Brothers into different languages:<br /> <br /> &lt;table border=&quot;1&quot; style=&quot;width:65%&quot;&gt;<br /> &lt;tr&gt;&lt;th&gt;Language&lt;/th&gt;&lt;th&gt;Translator&lt;/th&gt;&lt;th&gt;Status&lt;/th&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Afrikaans (af)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Brazilian Portuguese (pt_BR)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;British English (en_GB)&lt;/td&gt;&lt;td&gt;[[User:Placid|Placid]]&lt;/td&gt;&lt;td&gt;work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Bulgarian (bg)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Catalan (ca)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Chinese (zh_CN)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Czech (cs)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Danish (da)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Dutch (nl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Estonian (et)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Finnish (fi)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;French (fr)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;German (de)&lt;/td&gt;&lt;td&gt;Ivanovic&lt;/td&gt;&lt;td&gt;completed&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Greek (el_GR)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Hungarian (hu)&lt;/td&gt;&lt;td&gt;[[HungarianTranslation|Műhelyben]]&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Italian (it)&lt;/td&gt;&lt;td&gt;RokStar&lt;/td&gt;&lt;td&gt;completed&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Japanese (ja)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Latin (la)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Norwegian (no)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Polish (pl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Russian (ru)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Serbian (sr)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Slovak (sk)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Slovenian (sl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Spanish (es)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Swedish (sv)&lt;/td&gt;&lt;td&gt;Sanna, Lugo Moll&lt;/td&gt;&lt;td&gt;completed&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Turkish (tr)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> == Status Descriptions ==<br /> * '''unknown'''<br /> <br /> It is not known if someone is actually translating this campaign.<br /> * '''work in progress'''<br /> <br /> Someone is working on it, but it is not done, yet.<br /> * '''correction'''<br /> <br /> Translation is already completed, but it is being corrected at the moment.<br /> * '''completed'''<br /> <br /> It is already completed and updated when there are changes.<br /> * '''completed (not active)'''<br /> <br /> It is already completed and but not updated when there are changes.<br /> <br /> == See Also ==<br /> <br /> * [[WesCamp]]<br /> * [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Two_Brothers&amp;order=trans Translation stats for Two Brothers]</div>

Placid https://wiki.wesnoth.org/index.php?title=CampaignNorthernRebirth&diff=8614 2006-03-27T22:11:19Z

<p>Placid: /* Translation of Northern Rebirth */</p> <hr /> <div>== Translation of Northern Rebirth ==<br /> <br /> This is a list of the people currently translating Northern Rebirth into different languages:<br /> <br /> &lt;table border=&quot;1&quot; style=&quot;width:65%&quot;&gt;<br /> &lt;tr&gt;&lt;th&gt;Language&lt;/th&gt;&lt;th&gt;Translator&lt;/th&gt;&lt;th&gt;Status&lt;/th&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Afrikaans (af)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Brazilian Portuguese (pt_BR)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;British English (en_GB)&lt;/td&gt;&lt;td&gt;[[User:Placid|Placid]]&lt;/td&gt;&lt;td&gt;completed&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Bulgarian (bg)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Catalan (ca)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Chinese (zh_CN)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Czech (cs)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Danish (da)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Dutch (nl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Estonian (et)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Finnish (fi)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;French (fr)&lt;/td&gt;&lt;td&gt;gdou&lt;/td&gt;&lt;td&gt;Work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;German (de)&lt;/td&gt;&lt;td&gt;Belchion&lt;/td&gt;&lt;td&gt;completed (not active)&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Greek (el_GR)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Hungarian (hu)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Italian (it)&lt;/td&gt;&lt;td&gt;Luciano&lt;/td&gt;&lt;td&gt;Work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Japanese (ja)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Latin (la)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Norwegian (no)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Polish (pl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Russian (ru)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Serbian (sr)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Slovak (sk)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Slovenian (sl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Spanish (es)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Swedish (sv)&lt;/td&gt;&lt;td&gt;Unassigned&lt;/td&gt;&lt;td&gt;stalled&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Turkish (tr)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> == Status Descriptions ==<br /> * '''unknown'''<br /> <br /> It is not known if someone is actually translating this campaign.<br /> * '''work in progress'''<br /> <br /> Someone is working on it, but it is not done, yet.<br /> * '''completed'''<br /> <br /> It is already completed and updated when there are changes.<br /> * '''completed (not active)'''<br /> <br /> It is already completed and but not updated when there are changes.<br /> <br /> == See Also ==<br /> <br /> * [[WesCamp]]<br /> * [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Northern_Rebirth&amp;order=trans Translation stats for Northern Rebirth]</div>

Placid https://wiki.wesnoth.org/index.php?title=CampaignBurningSuns&diff=8589 2006-03-27T05:27:44Z

<p>Placid: /* Translation of Under the Burning Suns */</p> <hr /> <div>== Translation of Under the Burning Suns ==<br /> This is a list of the people currently translating Under the Burning Suns into different languages:<br /> <br /> &lt;table border=&quot;1&quot; style=&quot;width:65%&quot;&gt;<br /> &lt;tr&gt;&lt;th&gt;Language&lt;/th&gt;&lt;th&gt;Translator&lt;/th&gt;&lt;th&gt;Status&lt;/th&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Afrikaans (af)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Brazilian Portuguese (pt_BR)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;British English (en_GB)&lt;/td&gt;&lt;td&gt;[[User:Placid|Placid]]&lt;/td&gt;&lt;td&gt;work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Bulgarian (bg)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Catalan (ca)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Chinese (zh_CN)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Czech (cs)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Danish (da)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Dutch (nl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Estonian (et)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Finnish (fi)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;French (fr)&lt;/td&gt;&lt;td&gt;breversa&lt;/td&gt;&lt;td&gt;work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;German (de)&lt;/td&gt;&lt;td&gt;Allefant&lt;/td&gt;&lt;td&gt;completed&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Greek (el_GR)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Hungarian (hu)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Italian (it)&lt;/td&gt;&lt;td&gt;luciano&lt;/td&gt;&lt;td&gt;work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Japanese (ja)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Latin (la)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Norwegian (no)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Polish (pl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;[[CampaignBurningSuns:RussianTranslation|Russian (ru)]]&lt;/td&gt;&lt;td&gt;[[User:Alxrem|Alexey Remizov]]&lt;/td&gt;&lt;td&gt;work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Serbian (sr)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Slovak (sk)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Slovenian (sl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Spanish (es)&lt;/td&gt;&lt;td&gt;Elestel&lt;/td&gt;&lt;td&gt;work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Swedish (sv)&lt;/td&gt;&lt;td&gt;Unassigned&lt;/td&gt;&lt;td&gt;stalled&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Turkish (tr)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> == Status Descriptions ==<br /> * '''unknown'''<br /> <br /> It is not known if someone is actually translating this campaign.<br /> * '''work in progress'''<br /> <br /> Someone is working on it, but it is not done, yet.<br /> * '''correction'''<br /> <br /> Translation is already completed, but it is being corrected at the moment.<br /> * '''completed'''<br /> <br /> It is already completed and updated when there are changes.<br /> * '''completed (not active)'''<br /> <br /> It is already completed and but not updated when there are changes.<br /> <br /> == See Also ==<br /> <br /> * [[WesCamp]]<br /> * [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Under_the_Burning_Suns&amp;order=trans Translation stats for Under the Burning Suns]</div>

Placid https://wiki.wesnoth.org/index.php?title=Play&diff=8466 2006-03-23T22:12:44Z

<p>Placid: rv</p> <hr /> <div><br /> == Getting Battle for Wesnoth ==<br /> * [[Description|About the project]]<br /> * [[Download|Downloads and Source Code Page]]<br /> * [[CompilingWesnoth| Compiling Wesnoth]]<br /> <br /> == Playing Battle for Wesnoth ==<br /> &lt;div class=&quot;thumb tright&quot;&gt;&lt;div&gt;<br /> [http://www.wesnoth.org/images/sshots/wesnoth-1.0-urug.jpg http://www.wesnoth.org/images/sshots/wesnoth-1.0-urug-175.jpg]<br /> &lt;div class=&quot;thumbcaption&quot;&gt;The Elves Besieged&lt;/div&gt;&lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> * [[GettingStarted|Get Started]]<br /> * [[WesnothManual|Game Manual]]<br /> * [[BasicStrategy|Basic Tactics]]<br /> * [[MainlineScenarios|Walkthroughs of Official Campaigns]]<br /> * [[UserScenarios | User-made Add-On Campaigns]]<br /> * [[FAQ]]<br /> <br /> == Advanced Players ==<br /> * [[CommandMode|Debugging and Multiplayer Command Reference]]<br /> * [[AdvancedTactics|Advanced Tactics]]<br /> * [http://wesnoth.slack.it/units.cgi Units Reference]<br /> * [[MultiplayerServers|Multiplayer Servers]]<br /> <br /> == The world of Wesnoth ==<br /> &lt;div class=&quot;thumb tright&quot;&gt;&lt;div&gt;<br /> [http://www.wesnoth.org/images/sshots/wesnoth-map-1.jpg http://www.wesnoth.org/images/sshots/wesnoth-map-1-175.jpg]<br /> &lt;div class=&quot;thumbcaption&quot;&gt; Wesnoth and Surrounding Lands&lt;/div&gt;&lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> * [[WesnothHistory|The history of Wesnoth]]<br /> * [[WesnothGeography|The geography of Wesnoth]]<br /> * [[RaceDescriptions|The races of creatures in Wesnoth]]<br /> * [[WesnothPoetry|Wesnothian poetry]]<br /> <br /> <br /> == Miscellaneous ==<br /> * [[WhatArePlayersSaying|Comments from Wesnoth Players]]<br /> * [[WesnothReviews|Third party Wesnoth reviews]]<br /> * [[Screenshots]]<br /> * [[FAQ#Do_you_want_help_making_this_game.3F_How_can_I_help.3F|Help to improve the game]]<br /> <br /> __NOTOC__<br /> {{Home}}</div>

Placid https://wiki.wesnoth.org/index.php?title=WesnothBinariesLinux&diff=8455 2006-03-23T04:39:37Z

<p>Placid: /* Debian */</p> <hr /> <div>= GNU/Linux =<br /> Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.<br /> <br /> === Arch Linux ===<br /> * For the official pkg from [extra]: &lt;code&gt;pacman -S wesnoth&lt;/code&gt; <br /> * dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.<br /> <br /> === Debian ===<br /> * &lt;code&gt;apt-get install wesnoth&lt;/code&gt; or <br /> * &lt;code&gt;aptitude install wesnoth&lt;/code&gt; <br /> * [http://packages.debian.org/wesnoth Official packages]<br /> * [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]<br /> ===&gt; about this backport, maybe an issue with an unresolvable dependancy, the &quot;ttf-dejavu&quot; package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]<br /> <br /> ====&gt; 8 October: adding<br /> <br /> deb http://ftp.tr.debian.org/debian/ unstable main<br /> deb-src http://ftp.tr.debian.org/debian/ unstable main<br /> <br /> to /etc/apt/sources.list,<br /> <br /> Package: wesnoth<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: wesnoth-data<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: *<br /> Pin: release a=stable<br /> Pin-Priority: 700<br /> <br /> Package: *<br /> Pin: release a=testing<br /> Pin-Priority: 650<br /> <br /> Package: *<br /> Pin: release a=unstable<br /> Pin-Priority: 600<br /> <br /> to /etc/apt/preferences and then installing ttf-dejavu with<br /> <br /> apt-get install -t unstable ttf-dejavu<br /> <br /> worked for me ;-)<br /> <br /> ====Compiling====<br /> If you want to install the latest Development version you may have to compile it yourself. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].<br /> <br /> '''To install the dependencies :'''<br /> &lt;code&gt;aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev&lt;/code&gt;<br /> <br /> Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by<br /> <br /> &lt;code&gt;aptitude install gettext&lt;/code&gt;<br /> <br /> If someone may confirm that ...<br /> <br /> '''To compile it :'''<br /> If you have already installed and older version of wesnoth, uninstall it by :<br /> <br /> &lt;code&gt;aptitude purge wesnoth&lt;/code&gt;<br /> <br /> Note that will remove all your wesnoth configuration.<br /> Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.<br /> Now, it's very easy :<br /> <br /> cd /usr/src<br /> tar -xvzf wesnoth-1.x.x.tar.gz<br /> cd wesnoth-1.x.x<br /> ./configure<br /> make<br /> make install<br /> <br /> You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.<br /> <br /> === Ubuntu ===<br /> <br /> Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the latest stable release. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:<br /> *Upgrade to the Dapper Drake, or<br /> *Use the Breezy-Backports repository,<br /> *Use an unofficial repository, or<br /> *Build from the source per Debian above, or<br /> *Use the generic binary for GNU/Linux found on the [[Download]] page.<br /> <br /> Of these options, the final one is most likely the easiest at this time, while building from source is the most reliable. <br /> <br /> See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.<br /> <br /> Do not attempt to install the debian package and associated dependencies using ''dpkg'' as you will break your environment!<br /> <br /> ====Compiling====<br /> If you choose to build the source you should add the a flag to ''configure'' to ensure your installation puts the data in the same place as the official installation path:<br /> <br /> cd /usr/src<br /> tar -xvzf wesnoth-1.x.x.tar.gz<br /> cd wesnoth-1.x.x<br /> ./configure --datadir=/usr/share/games ...<br /> make<br /> sudo make install<br /> <br /> === Fedora Core ===<br /> Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.<br /> * &lt;code&gt;yum install wesnoth wesnoth-tools wesnoth-server&lt;/code&gt; <br /> * Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/<br /> <br /> === Gentoo ===<br /> * &lt;code&gt;emerge wesnoth&lt;/code&gt;<br /> <br /> === klik ===<br /> * The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no &quot;installation&quot; (the base system remains untouched); its created &quot;AppDir&quot; bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:<br /> ** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to &quot;klik&quot; it, type ''klik://wesnoth'' into your Browser<br /> ** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to &quot;klik&quot; it, type ''klik://wesnoth-latest'' into your Browser<br /> <br /> === Mandrake (cooker) ===<br /> * &lt;code&gt;urpmi wesnoth&lt;/code&gt;<br /> * Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/<br /> * Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/<br /> <br /> === Slackware 10.2 ===<br /> sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy<br /> * '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/<br /> <br /> === [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===<br /> * Wesnoth 1.0 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 &amp; 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):<br /> ** http://www.unixboard.de/suse/10/wesnoth-1.0-1.i386.rpm for [[SuSE]] 10.0<br /> ** http://www.unixboard.de/suse//wesnoth-1.0-1.i386.rpm for [[SuSE]] 9.3<br /> <br /> <br /> * Wesnoth 0.9.4 (by Luciano Montanaro):<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-0.9.4-9ml.i586.rpm (should work on [[SuSE]] 9.1 and 9.2 too)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-editor-0.9.4-9ml.i586.rpm (level editor)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-server-0.9.4-9ml.i586.rpm (game server)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/src/wesnoth-0.9.4-9ml.src.rpm (source rpm)<br /> <br /> * Wesnoth Binaries for [http://www.opensuse.org OpenSUSE] 10.0, [[SuSE]] Linux 9.3 and [[SuSE]] Linux 9.2, x86, ppc and x86_64. (by [[User:MadOssor|Holger Hetterich]] [mailto:ozzyATmetal-district.de] ) <br /> ** http://81.169.140.126/rpm/wesnoth/ <br /> <br /> '''These packages are also usable as a YaST installation source, use the settings from the table below'''<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot;<br /> ! rowspan=2 | SUSE Release<br /> ! rowspan=2 | Protocol <br /> |- <br /> ! SERVER || DIRECTORY/URL <br /> |-<br /> | [[SuSE]] Linux 9.2 x86/x86_64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.2<br /> |-<br /> | [[SuSE]] Linux 9.3 x86/x86-64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.3<br /> |-<br /> | [[SuSE]] Linux 10.0 x86/x86_64/ppc / [http://www.opensuse.org OpenSUSE 10.0] || HTTP || 81.169.140.126 || rpm/wesnoth/10.0<br /> |-<br /> | Current [http://www.opensuse.org OpenSUSE] Development build x86/x86_64/ppc || HTTP || 81.169.140.126 || rpm/wesnoth/OpenSUSE-current<br /> |}<br /> <br /> '''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''<br /> <br /> === Yoper Linux ===<br /> All versions built for Yoper 2.2.0-6, although they should install on 2.1.<br /> Please let kernowyon know via the Yoper forums if you get any problems<br /> Latest 1.0.2 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm<br /> 1.0.1 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm<br /> Earlier version<br /> *http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm<br /> <br /> === Binaries for all distributions ===<br /> * A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: <br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]<br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz] <br /> ** This is NOT a static binary distribution, it resolves dependencies at runtime.<br /> * Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)<br /> <br /> === Other ===<br /> * [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]<br /> <br /> = See Also =<br /> * [[CompilingWesnoth]]<br /> * [[Download]]</div>

Placid https://wiki.wesnoth.org/index.php?title=WesnothBinariesLinux&diff=8454 2006-03-23T04:39:22Z

<p>Placid: /* Debian */</p> <hr /> <div>= GNU/Linux =<br /> Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.<br /> <br /> === Arch Linux ===<br /> * For the official pkg from [extra]: &lt;code&gt;pacman -S wesnoth&lt;/code&gt; <br /> * dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.<br /> <br /> === Debian ===<br /> * &lt;code&gt;apt-get install wesnoth&lt;/code&gt; or <br /> * &lt;code&gt;aptitude install wesnoth&lt;/code&gt; <br /> * [http://packages.debian.org/wesnoth Official packages]<br /> * [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]<br /> ===&gt; about this backport, maybe an issue with an unresolvable dependancy, the &quot;ttf-dejavu&quot; package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]<br /> <br /> ====&gt; 8 October: adding<br /> <br /> deb http://ftp.tr.debian.org/debian/ unstable main<br /> deb-src http://ftp.tr.debian.org/debian/ unstable main<br /> <br /> to /etc/apt/sources.list,<br /> <br /> Package: wesnoth<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: wesnoth-data<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: *<br /> Pin: release a=stable<br /> Pin-Priority: 700<br /> <br /> Package: *<br /> Pin: release a=testing<br /> Pin-Priority: 650<br /> <br /> Package: *<br /> Pin: release a=unstable<br /> Pin-Priority: 600<br /> <br /> to /etc/apt/preferences and then installing ttf-dejavu with<br /> <br /> apt-get install -t unstable ttf-dejavu<br /> <br /> worked for me ;-)<br /> <br /> <br /> ====Compiling====<br /> If you want to install the latest Development version you may have to compile it yourself. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].<br /> <br /> '''To install the dependencies :'''<br /> &lt;code&gt;aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev&lt;/code&gt;<br /> <br /> Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by<br /> <br /> &lt;code&gt;aptitude install gettext&lt;/code&gt;<br /> <br /> If someone may confirm that ...<br /> <br /> '''To compile it :'''<br /> If you have already installed and older version of wesnoth, uninstall it by :<br /> <br /> &lt;code&gt;aptitude purge wesnoth&lt;/code&gt;<br /> <br /> Note that will remove all your wesnoth configuration.<br /> Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.<br /> Now, it's very easy :<br /> <br /> cd /usr/src<br /> tar -xvzf wesnoth-1.x.x.tar.gz<br /> cd wesnoth-1.x.x<br /> ./configure<br /> make<br /> make install<br /> <br /> You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.<br /> <br /> === Ubuntu ===<br /> <br /> Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the latest stable release. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:<br /> *Upgrade to the Dapper Drake, or<br /> *Use the Breezy-Backports repository,<br /> *Use an unofficial repository, or<br /> *Build from the source per Debian above, or<br /> *Use the generic binary for GNU/Linux found on the [[Download]] page.<br /> <br /> Of these options, the final one is most likely the easiest at this time, while building from source is the most reliable. <br /> <br /> See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.<br /> <br /> Do not attempt to install the debian package and associated dependencies using ''dpkg'' as you will break your environment!<br /> <br /> ====Compiling====<br /> If you choose to build the source you should add the a flag to ''configure'' to ensure your installation puts the data in the same place as the official installation path:<br /> <br /> cd /usr/src<br /> tar -xvzf wesnoth-1.x.x.tar.gz<br /> cd wesnoth-1.x.x<br /> ./configure --datadir=/usr/share/games ...<br /> make<br /> sudo make install<br /> <br /> === Fedora Core ===<br /> Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.<br /> * &lt;code&gt;yum install wesnoth wesnoth-tools wesnoth-server&lt;/code&gt; <br /> * Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/<br /> <br /> === Gentoo ===<br /> * &lt;code&gt;emerge wesnoth&lt;/code&gt;<br /> <br /> === klik ===<br /> * The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no &quot;installation&quot; (the base system remains untouched); its created &quot;AppDir&quot; bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:<br /> ** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to &quot;klik&quot; it, type ''klik://wesnoth'' into your Browser<br /> ** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to &quot;klik&quot; it, type ''klik://wesnoth-latest'' into your Browser<br /> <br /> === Mandrake (cooker) ===<br /> * &lt;code&gt;urpmi wesnoth&lt;/code&gt;<br /> * Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/<br /> * Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/<br /> <br /> === Slackware 10.2 ===<br /> sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy<br /> * '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/<br /> <br /> === [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===<br /> * Wesnoth 1.0 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 &amp; 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):<br /> ** http://www.unixboard.de/suse/10/wesnoth-1.0-1.i386.rpm for [[SuSE]] 10.0<br /> ** http://www.unixboard.de/suse//wesnoth-1.0-1.i386.rpm for [[SuSE]] 9.3<br /> <br /> <br /> * Wesnoth 0.9.4 (by Luciano Montanaro):<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-0.9.4-9ml.i586.rpm (should work on [[SuSE]] 9.1 and 9.2 too)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-editor-0.9.4-9ml.i586.rpm (level editor)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-server-0.9.4-9ml.i586.rpm (game server)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/src/wesnoth-0.9.4-9ml.src.rpm (source rpm)<br /> <br /> * Wesnoth Binaries for [http://www.opensuse.org OpenSUSE] 10.0, [[SuSE]] Linux 9.3 and [[SuSE]] Linux 9.2, x86, ppc and x86_64. (by [[User:MadOssor|Holger Hetterich]] [mailto:ozzyATmetal-district.de] ) <br /> ** http://81.169.140.126/rpm/wesnoth/ <br /> <br /> '''These packages are also usable as a YaST installation source, use the settings from the table below'''<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot;<br /> ! rowspan=2 | SUSE Release<br /> ! rowspan=2 | Protocol <br /> |- <br /> ! SERVER || DIRECTORY/URL <br /> |-<br /> | [[SuSE]] Linux 9.2 x86/x86_64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.2<br /> |-<br /> | [[SuSE]] Linux 9.3 x86/x86-64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.3<br /> |-<br /> | [[SuSE]] Linux 10.0 x86/x86_64/ppc / [http://www.opensuse.org OpenSUSE 10.0] || HTTP || 81.169.140.126 || rpm/wesnoth/10.0<br /> |-<br /> | Current [http://www.opensuse.org OpenSUSE] Development build x86/x86_64/ppc || HTTP || 81.169.140.126 || rpm/wesnoth/OpenSUSE-current<br /> |}<br /> <br /> '''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''<br /> <br /> === Yoper Linux ===<br /> All versions built for Yoper 2.2.0-6, although they should install on 2.1.<br /> Please let kernowyon know via the Yoper forums if you get any problems<br /> Latest 1.0.2 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm<br /> 1.0.1 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm<br /> Earlier version<br /> *http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm<br /> <br /> === Binaries for all distributions ===<br /> * A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: <br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]<br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz] <br /> ** This is NOT a static binary distribution, it resolves dependencies at runtime.<br /> * Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)<br /> <br /> === Other ===<br /> * [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]<br /> <br /> = See Also =<br /> * [[CompilingWesnoth]]<br /> * [[Download]]</div>

Placid https://wiki.wesnoth.org/index.php?title=WesnothBinariesLinux&diff=8453 2006-03-23T04:38:01Z

<p>Placid: correct heading level</p> <hr /> <div>= GNU/Linux =<br /> Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.<br /> <br /> === Arch Linux ===<br /> * For the official pkg from [extra]: &lt;code&gt;pacman -S wesnoth&lt;/code&gt; <br /> * dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.<br /> <br /> === Debian ===<br /> * &lt;code&gt;apt-get install wesnoth&lt;/code&gt; or <br /> * &lt;code&gt;aptitude install wesnoth&lt;/code&gt; <br /> * [http://packages.debian.org/wesnoth Official packages]<br /> * [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]<br /> ===&gt; about this backport, maybe an issue with an unresolvable dependancy, the &quot;ttf-dejavu&quot; package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]<br /> <br /> ====&gt; 8 October: adding<br /> <br /> deb http://ftp.tr.debian.org/debian/ unstable main<br /> deb-src http://ftp.tr.debian.org/debian/ unstable main<br /> <br /> to /etc/apt/sources.list,<br /> <br /> Package: wesnoth<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: wesnoth-data<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: *<br /> Pin: release a=stable<br /> Pin-Priority: 700<br /> <br /> Package: *<br /> Pin: release a=testing<br /> Pin-Priority: 650<br /> <br /> Package: *<br /> Pin: release a=unstable<br /> Pin-Priority: 600<br /> <br /> to /etc/apt/preferences and then installing ttf-dejavu with<br /> <br /> apt-get install -t unstable ttf-dejavu<br /> <br /> worked for me ;-)<br /> <br /> <br /> ====&gt; If you want to install the latest Development version you may have to compile it yourself. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].<br /> <br /> '''To install the dependencies :'''<br /> &lt;code&gt;aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev&lt;/code&gt;<br /> <br /> Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by<br /> <br /> &lt;code&gt;aptitude install gettext&lt;/code&gt;<br /> <br /> If someone may confirm that ...<br /> <br /> '''To compile it :'''<br /> If you have already installed and older version of wesnoth, uninstall it by :<br /> <br /> &lt;code&gt;aptitude purge wesnoth&lt;/code&gt;<br /> <br /> Note that will remove all your wesnoth configuration.<br /> Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.<br /> Now, it's very easy :<br /> <br /> cd /usr/src<br /> tar -xvzf wesnoth-1.x.x.tar.gz<br /> cd wesnoth-1.x.x<br /> ./configure<br /> make<br /> make install<br /> <br /> You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.<br /> <br /> === Ubuntu ===<br /> <br /> Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the latest stable release. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:<br /> *Upgrade to the Dapper Drake, or<br /> *Use the Breezy-Backports repository,<br /> *Use an unofficial repository, or<br /> *Build from the source per Debian above, or<br /> *Use the generic binary for GNU/Linux found on the [[Download]] page.<br /> <br /> Of these options, the final one is most likely the easiest at this time, while building from source is the most reliable. <br /> <br /> See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.<br /> <br /> Do not attempt to install the debian package and associated dependencies using ''dpkg'' as you will break your environment!<br /> <br /> ====Compiling====<br /> If you choose to build the source you should add the a flag to ''configure'' to ensure your installation puts the data in the same place as the official installation path:<br /> <br /> cd /usr/src<br /> tar -xvzf wesnoth-1.x.x.tar.gz<br /> cd wesnoth-1.x.x<br /> ./configure --datadir=/usr/share/games ...<br /> make<br /> sudo make install<br /> <br /> === Fedora Core ===<br /> Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.<br /> * &lt;code&gt;yum install wesnoth wesnoth-tools wesnoth-server&lt;/code&gt; <br /> * Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/<br /> <br /> === Gentoo ===<br /> * &lt;code&gt;emerge wesnoth&lt;/code&gt;<br /> <br /> === klik ===<br /> * The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no &quot;installation&quot; (the base system remains untouched); its created &quot;AppDir&quot; bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:<br /> ** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to &quot;klik&quot; it, type ''klik://wesnoth'' into your Browser<br /> ** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to &quot;klik&quot; it, type ''klik://wesnoth-latest'' into your Browser<br /> <br /> === Mandrake (cooker) ===<br /> * &lt;code&gt;urpmi wesnoth&lt;/code&gt;<br /> * Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/<br /> * Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/<br /> <br /> === Slackware 10.2 ===<br /> sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy<br /> * '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/<br /> <br /> === [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===<br /> * Wesnoth 1.0 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 &amp; 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):<br /> ** http://www.unixboard.de/suse/10/wesnoth-1.0-1.i386.rpm for [[SuSE]] 10.0<br /> ** http://www.unixboard.de/suse//wesnoth-1.0-1.i386.rpm for [[SuSE]] 9.3<br /> <br /> <br /> * Wesnoth 0.9.4 (by Luciano Montanaro):<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-0.9.4-9ml.i586.rpm (should work on [[SuSE]] 9.1 and 9.2 too)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-editor-0.9.4-9ml.i586.rpm (level editor)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-server-0.9.4-9ml.i586.rpm (game server)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/src/wesnoth-0.9.4-9ml.src.rpm (source rpm)<br /> <br /> * Wesnoth Binaries for [http://www.opensuse.org OpenSUSE] 10.0, [[SuSE]] Linux 9.3 and [[SuSE]] Linux 9.2, x86, ppc and x86_64. (by [[User:MadOssor|Holger Hetterich]] [mailto:ozzyATmetal-district.de] ) <br /> ** http://81.169.140.126/rpm/wesnoth/ <br /> <br /> '''These packages are also usable as a YaST installation source, use the settings from the table below'''<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot;<br /> ! rowspan=2 | SUSE Release<br /> ! rowspan=2 | Protocol <br /> |- <br /> ! SERVER || DIRECTORY/URL <br /> |-<br /> | [[SuSE]] Linux 9.2 x86/x86_64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.2<br /> |-<br /> | [[SuSE]] Linux 9.3 x86/x86-64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.3<br /> |-<br /> | [[SuSE]] Linux 10.0 x86/x86_64/ppc / [http://www.opensuse.org OpenSUSE 10.0] || HTTP || 81.169.140.126 || rpm/wesnoth/10.0<br /> |-<br /> | Current [http://www.opensuse.org OpenSUSE] Development build x86/x86_64/ppc || HTTP || 81.169.140.126 || rpm/wesnoth/OpenSUSE-current<br /> |}<br /> <br /> '''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''<br /> <br /> === Yoper Linux ===<br /> All versions built for Yoper 2.2.0-6, although they should install on 2.1.<br /> Please let kernowyon know via the Yoper forums if you get any problems<br /> Latest 1.0.2 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm<br /> 1.0.1 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm<br /> Earlier version<br /> *http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm<br /> <br /> === Binaries for all distributions ===<br /> * A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: <br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]<br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz] <br /> ** This is NOT a static binary distribution, it resolves dependencies at runtime.<br /> * Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)<br /> <br /> === Other ===<br /> * [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]<br /> <br /> = See Also =<br /> * [[CompilingWesnoth]]<br /> * [[Download]]</div>

Placid https://wiki.wesnoth.org/index.php?title=WesnothBinariesLinux&diff=8452 2006-03-23T04:24:18Z

<p>Placid: /* Debian */ tidy format</p> <hr /> <div>= GNU/Linux =<br /> Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.<br /> <br /> === Arch Linux ===<br /> * For the official pkg from [extra]: &lt;code&gt;pacman -S wesnoth&lt;/code&gt; <br /> * dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.<br /> <br /> === Debian ===<br /> * &lt;code&gt;apt-get install wesnoth&lt;/code&gt; or <br /> * &lt;code&gt;aptitude install wesnoth&lt;/code&gt; <br /> * [http://packages.debian.org/wesnoth Official packages]<br /> * [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]<br /> ===&gt; about this backport, maybe an issue with an unresolvable dependancy, the &quot;ttf-dejavu&quot; package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]<br /> <br /> ====&gt; 8 October: adding<br /> <br /> deb http://ftp.tr.debian.org/debian/ unstable main<br /> deb-src http://ftp.tr.debian.org/debian/ unstable main<br /> <br /> to /etc/apt/sources.list,<br /> <br /> Package: wesnoth<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: wesnoth-data<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: *<br /> Pin: release a=stable<br /> Pin-Priority: 700<br /> <br /> Package: *<br /> Pin: release a=testing<br /> Pin-Priority: 650<br /> <br /> Package: *<br /> Pin: release a=unstable<br /> Pin-Priority: 600<br /> <br /> to /etc/apt/preferences and then installing ttf-dejavu with<br /> <br /> apt-get install -t unstable ttf-dejavu<br /> <br /> worked for me ;-)<br /> <br /> <br /> ====&gt; If you want to install the latest Development version you may have to compile it yourself. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].<br /> <br /> '''To install the dependencies :'''<br /> &lt;code&gt;aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev&lt;/code&gt;<br /> <br /> Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by<br /> <br /> &lt;code&gt;aptitude install gettext&lt;/code&gt;<br /> <br /> If someone may confirm that ...<br /> <br /> '''To compile it :'''<br /> If you have already installed and older version of wesnoth, uninstall it by :<br /> <br /> &lt;code&gt;aptitude purge wesnoth&lt;/code&gt;<br /> <br /> Note that will remove all your wesnoth configuration.<br /> Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.<br /> Now, it's very easy :<br /> <br /> cd /usr/src<br /> tar -xvzf wesnoth-1.x.x.tar.gz<br /> cd wesnoth-1.x.x<br /> ./configure<br /> make<br /> make install<br /> <br /> You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.<br /> <br /> === Ubuntu ===<br /> <br /> Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the latest stable release. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:<br /> *Upgrade to the Dapper Drake, or<br /> *Use the Breezy-Backports repository,<br /> *Use an unofficial repository, or<br /> *Build from the source per Debian above, or<br /> *Use the generic binary for GNU/Linux found on the [[Download]] page.<br /> <br /> Of these options, the final one is most likely the easiest at this time, while building from source is the most reliable. <br /> <br /> See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.<br /> <br /> Do not attempt to install the debian package and associated dependencies using ''dpkg'' as you will break your environment!<br /> <br /> ==Compiling==<br /> If you choose to build the source you should add the a flag to ''configure'' to ensure your installation puts the data in the same place as the official installation path:<br /> <br /> cd /usr/src<br /> tar -xvzf wesnoth-1.x.x.tar.gz<br /> cd wesnoth-1.x.x<br /> ./configure --datadir=/usr/share/games ...<br /> make<br /> sudo make install<br /> <br /> === Fedora Core ===<br /> Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.<br /> * &lt;code&gt;yum install wesnoth wesnoth-tools wesnoth-server&lt;/code&gt; <br /> * Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/<br /> <br /> === Gentoo ===<br /> * &lt;code&gt;emerge wesnoth&lt;/code&gt;<br /> <br /> === klik ===<br /> * The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no &quot;installation&quot; (the base system remains untouched); its created &quot;AppDir&quot; bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:<br /> ** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to &quot;klik&quot; it, type ''klik://wesnoth'' into your Browser<br /> ** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to &quot;klik&quot; it, type ''klik://wesnoth-latest'' into your Browser<br /> <br /> === Mandrake (cooker) ===<br /> * &lt;code&gt;urpmi wesnoth&lt;/code&gt;<br /> * Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/<br /> * Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/<br /> <br /> === Slackware 10.2 ===<br /> sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy<br /> * '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/<br /> <br /> === [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===<br /> * Wesnoth 1.0 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 &amp; 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):<br /> ** http://www.unixboard.de/suse/10/wesnoth-1.0-1.i386.rpm for [[SuSE]] 10.0<br /> ** http://www.unixboard.de/suse//wesnoth-1.0-1.i386.rpm for [[SuSE]] 9.3<br /> <br /> <br /> * Wesnoth 0.9.4 (by Luciano Montanaro):<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-0.9.4-9ml.i586.rpm (should work on [[SuSE]] 9.1 and 9.2 too)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-editor-0.9.4-9ml.i586.rpm (level editor)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-server-0.9.4-9ml.i586.rpm (game server)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/src/wesnoth-0.9.4-9ml.src.rpm (source rpm)<br /> <br /> * Wesnoth Binaries for [http://www.opensuse.org OpenSUSE] 10.0, [[SuSE]] Linux 9.3 and [[SuSE]] Linux 9.2, x86, ppc and x86_64. (by [[User:MadOssor|Holger Hetterich]] [mailto:ozzyATmetal-district.de] ) <br /> ** http://81.169.140.126/rpm/wesnoth/ <br /> <br /> '''These packages are also usable as a YaST installation source, use the settings from the table below'''<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot;<br /> ! rowspan=2 | SUSE Release<br /> ! rowspan=2 | Protocol <br /> |- <br /> ! SERVER || DIRECTORY/URL <br /> |-<br /> | [[SuSE]] Linux 9.2 x86/x86_64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.2<br /> |-<br /> | [[SuSE]] Linux 9.3 x86/x86-64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.3<br /> |-<br /> | [[SuSE]] Linux 10.0 x86/x86_64/ppc / [http://www.opensuse.org OpenSUSE 10.0] || HTTP || 81.169.140.126 || rpm/wesnoth/10.0<br /> |-<br /> | Current [http://www.opensuse.org OpenSUSE] Development build x86/x86_64/ppc || HTTP || 81.169.140.126 || rpm/wesnoth/OpenSUSE-current<br /> |}<br /> <br /> '''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''<br /> <br /> === Yoper Linux ===<br /> All versions built for Yoper 2.2.0-6, although they should install on 2.1.<br /> Please let kernowyon know via the Yoper forums if you get any problems<br /> Latest 1.0.2 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm<br /> 1.0.1 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm<br /> Earlier version<br /> *http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm<br /> <br /> === Binaries for all distributions ===<br /> * A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: <br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]<br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz] <br /> ** This is NOT a static binary distribution, it resolves dependencies at runtime.<br /> * Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)<br /> <br /> === Other ===<br /> * [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]<br /> <br /> = See Also =<br /> * [[CompilingWesnoth]]<br /> * [[Download]]</div>

Placid https://wiki.wesnoth.org/index.php?title=WesnothBinariesLinux&diff=8451 2006-03-23T04:23:06Z

<p>Placid: /* Ubuntu */ add compiling section. should probably be somewhere else in the medium term</p> <hr /> <div>= GNU/Linux =<br /> Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.<br /> <br /> === Arch Linux ===<br /> * For the official pkg from [extra]: &lt;code&gt;pacman -S wesnoth&lt;/code&gt; <br /> * dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.<br /> <br /> === Debian ===<br /> * &lt;code&gt;apt-get install wesnoth&lt;/code&gt; or <br /> * &lt;code&gt;aptitude install wesnoth&lt;/code&gt; <br /> * [http://packages.debian.org/wesnoth Official packages]<br /> * [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]<br /> ===&gt; about this backport, maybe an issue with an unresolvable dependancy, the &quot;ttf-dejavu&quot; package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]<br /> <br /> ====&gt; 8 October: adding<br /> <br /> deb http://ftp.tr.debian.org/debian/ unstable main<br /> deb-src http://ftp.tr.debian.org/debian/ unstable main<br /> <br /> to /etc/apt/sources.list,<br /> <br /> Package: wesnoth<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: wesnoth-data<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: *<br /> Pin: release a=stable<br /> Pin-Priority: 700<br /> <br /> Package: *<br /> Pin: release a=testing<br /> Pin-Priority: 650<br /> <br /> Package: *<br /> Pin: release a=unstable<br /> Pin-Priority: 600<br /> <br /> to /etc/apt/preferences and then installing ttf-dejavu with<br /> <br /> apt-get install -t unstable ttf-dejavu<br /> <br /> worked for me ;-)<br /> <br /> <br /> ====&gt; If you want to install the latest Development version you may have to compile it yourself. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].<br /> <br /> '''To install the dependencies :'''<br /> &lt;code&gt;aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev&lt;/code&gt;<br /> <br /> Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by<br /> <br /> &lt;code&gt;aptitude install gettext&lt;/code&gt;<br /> <br /> If someone may confirm that ...<br /> <br /> '''To compile it :'''<br /> If you have already installed and older version of wesnoth, uninstall it by :<br /> <br /> &lt;code&gt;aptitude purge wesnoth&lt;/code&gt;<br /> <br /> Note that will remove all your wesnoth configuration.<br /> Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.<br /> Now, it's very easy :<br /> <br /> &lt;code&gt;cd /usr/src&lt;/code&gt;<br /> <br /> &lt;code&gt;tar -xvzf wesnoth-1.1.1.tar.gz&lt;/code&gt;<br /> <br /> &lt;code&gt;cd wesnoth-1.1.1&lt;/code&gt;<br /> <br /> &lt;code&gt;./configure&lt;/code&gt;<br /> <br /> &lt;code&gt;make&lt;/code&gt;<br /> <br /> &lt;code&gt;make install&lt;/code&gt;<br /> <br /> You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.<br /> <br /> === Ubuntu ===<br /> <br /> Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the latest stable release. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:<br /> *Upgrade to the Dapper Drake, or<br /> *Use the Breezy-Backports repository,<br /> *Use an unofficial repository, or<br /> *Build from the source per Debian above, or<br /> *Use the generic binary for GNU/Linux found on the [[Download]] page.<br /> <br /> Of these options, the final one is most likely the easiest at this time, while building from source is the most reliable. <br /> <br /> See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.<br /> <br /> Do not attempt to install the debian package and associated dependencies using ''dpkg'' as you will break your environment!<br /> <br /> ==Compiling==<br /> If you choose to build the source you should add the a flag to ''configure'' to ensure your installation puts the data in the same place as the official installation path:<br /> <br /> cd /usr/src<br /> tar -xvzf wesnoth-1.x.x.tar.gz<br /> cd wesnoth-1.x.x<br /> ./configure --datadir=/usr/share/games ...<br /> make<br /> sudo make install<br /> <br /> === Fedora Core ===<br /> Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.<br /> * &lt;code&gt;yum install wesnoth wesnoth-tools wesnoth-server&lt;/code&gt; <br /> * Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/<br /> <br /> === Gentoo ===<br /> * &lt;code&gt;emerge wesnoth&lt;/code&gt;<br /> <br /> === klik ===<br /> * The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no &quot;installation&quot; (the base system remains untouched); its created &quot;AppDir&quot; bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:<br /> ** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to &quot;klik&quot; it, type ''klik://wesnoth'' into your Browser<br /> ** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to &quot;klik&quot; it, type ''klik://wesnoth-latest'' into your Browser<br /> <br /> === Mandrake (cooker) ===<br /> * &lt;code&gt;urpmi wesnoth&lt;/code&gt;<br /> * Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/<br /> * Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/<br /> <br /> === Slackware 10.2 ===<br /> sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy<br /> * '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/<br /> <br /> === [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===<br /> * Wesnoth 1.0 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 &amp; 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):<br /> ** http://www.unixboard.de/suse/10/wesnoth-1.0-1.i386.rpm for [[SuSE]] 10.0<br /> ** http://www.unixboard.de/suse//wesnoth-1.0-1.i386.rpm for [[SuSE]] 9.3<br /> <br /> <br /> * Wesnoth 0.9.4 (by Luciano Montanaro):<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-0.9.4-9ml.i586.rpm (should work on [[SuSE]] 9.1 and 9.2 too)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-editor-0.9.4-9ml.i586.rpm (level editor)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-server-0.9.4-9ml.i586.rpm (game server)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/src/wesnoth-0.9.4-9ml.src.rpm (source rpm)<br /> <br /> * Wesnoth Binaries for [http://www.opensuse.org OpenSUSE] 10.0, [[SuSE]] Linux 9.3 and [[SuSE]] Linux 9.2, x86, ppc and x86_64. (by [[User:MadOssor|Holger Hetterich]] [mailto:ozzyATmetal-district.de] ) <br /> ** http://81.169.140.126/rpm/wesnoth/ <br /> <br /> '''These packages are also usable as a YaST installation source, use the settings from the table below'''<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot;<br /> ! rowspan=2 | SUSE Release<br /> ! rowspan=2 | Protocol <br /> |- <br /> ! SERVER || DIRECTORY/URL <br /> |-<br /> | [[SuSE]] Linux 9.2 x86/x86_64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.2<br /> |-<br /> | [[SuSE]] Linux 9.3 x86/x86-64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.3<br /> |-<br /> | [[SuSE]] Linux 10.0 x86/x86_64/ppc / [http://www.opensuse.org OpenSUSE 10.0] || HTTP || 81.169.140.126 || rpm/wesnoth/10.0<br /> |-<br /> | Current [http://www.opensuse.org OpenSUSE] Development build x86/x86_64/ppc || HTTP || 81.169.140.126 || rpm/wesnoth/OpenSUSE-current<br /> |}<br /> <br /> '''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''<br /> <br /> === Yoper Linux ===<br /> All versions built for Yoper 2.2.0-6, although they should install on 2.1.<br /> Please let kernowyon know via the Yoper forums if you get any problems<br /> Latest 1.0.2 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm<br /> 1.0.1 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm<br /> Earlier version<br /> *http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm<br /> <br /> === Binaries for all distributions ===<br /> * A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: <br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]<br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz] <br /> ** This is NOT a static binary distribution, it resolves dependencies at runtime.<br /> * Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)<br /> <br /> === Other ===<br /> * [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]<br /> <br /> = See Also =<br /> * [[CompilingWesnoth]]<br /> * [[Download]]</div>

Placid https://wiki.wesnoth.org/index.php?title=WesnothBinariesLinux&diff=8450 2006-03-23T04:20:08Z

<p>Placid: /* Ubuntu */ add some compile notes</p> <hr /> <div>= GNU/Linux =<br /> Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.<br /> <br /> === Arch Linux ===<br /> * For the official pkg from [extra]: &lt;code&gt;pacman -S wesnoth&lt;/code&gt; <br /> * dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.<br /> <br /> === Debian ===<br /> * &lt;code&gt;apt-get install wesnoth&lt;/code&gt; or <br /> * &lt;code&gt;aptitude install wesnoth&lt;/code&gt; <br /> * [http://packages.debian.org/wesnoth Official packages]<br /> * [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]<br /> ===&gt; about this backport, maybe an issue with an unresolvable dependancy, the &quot;ttf-dejavu&quot; package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]<br /> <br /> ====&gt; 8 October: adding<br /> <br /> deb http://ftp.tr.debian.org/debian/ unstable main<br /> deb-src http://ftp.tr.debian.org/debian/ unstable main<br /> <br /> to /etc/apt/sources.list,<br /> <br /> Package: wesnoth<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: wesnoth-data<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: *<br /> Pin: release a=stable<br /> Pin-Priority: 700<br /> <br /> Package: *<br /> Pin: release a=testing<br /> Pin-Priority: 650<br /> <br /> Package: *<br /> Pin: release a=unstable<br /> Pin-Priority: 600<br /> <br /> to /etc/apt/preferences and then installing ttf-dejavu with<br /> <br /> apt-get install -t unstable ttf-dejavu<br /> <br /> worked for me ;-)<br /> <br /> <br /> ====&gt; If you want to install the latest Development version you may have to compile it yourself. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].<br /> <br /> '''To install the dependencies :'''<br /> &lt;code&gt;aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev&lt;/code&gt;<br /> <br /> Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by<br /> <br /> &lt;code&gt;aptitude install gettext&lt;/code&gt;<br /> <br /> If someone may confirm that ...<br /> <br /> '''To compile it :'''<br /> If you have already installed and older version of wesnoth, uninstall it by :<br /> <br /> &lt;code&gt;aptitude purge wesnoth&lt;/code&gt;<br /> <br /> Note that will remove all your wesnoth configuration.<br /> Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.<br /> Now, it's very easy :<br /> <br /> &lt;code&gt;cd /usr/src&lt;/code&gt;<br /> <br /> &lt;code&gt;tar -xvzf wesnoth-1.1.1.tar.gz&lt;/code&gt;<br /> <br /> &lt;code&gt;cd wesnoth-1.1.1&lt;/code&gt;<br /> <br /> &lt;code&gt;./configure&lt;/code&gt;<br /> <br /> &lt;code&gt;make&lt;/code&gt;<br /> <br /> &lt;code&gt;make install&lt;/code&gt;<br /> <br /> You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.<br /> <br /> === Ubuntu ===<br /> <br /> Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the latest stable release. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:<br /> *Upgrade to the Dapper Drake, or<br /> *Use the Breezy-Backports repository,<br /> *Use an unofficial repository, or<br /> *Build from the source per Debian above, or<br /> *Use the generic binary for GNU/Linux found on the [[Download]] page.<br /> <br /> Of these options, the final one is most likely the easiest at this time, while building from source is the most reliable. <br /> <br /> See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.<br /> <br /> Do not attempt to install the debian package and associated dependencies using ''dpkg'' as you will break your environment!<br /> <br /> If you choose to build the source you need to add the following flag to ''configure'' to ensure your installation is consistent with the official installation path:<br /> <br /> ./configure --datadir=/usr/share/games ...<br /> <br /> === Fedora Core ===<br /> Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.<br /> * &lt;code&gt;yum install wesnoth wesnoth-tools wesnoth-server&lt;/code&gt; <br /> * Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/<br /> <br /> === Gentoo ===<br /> * &lt;code&gt;emerge wesnoth&lt;/code&gt;<br /> <br /> === klik ===<br /> * The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no &quot;installation&quot; (the base system remains untouched); its created &quot;AppDir&quot; bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:<br /> ** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to &quot;klik&quot; it, type ''klik://wesnoth'' into your Browser<br /> ** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to &quot;klik&quot; it, type ''klik://wesnoth-latest'' into your Browser<br /> <br /> === Mandrake (cooker) ===<br /> * &lt;code&gt;urpmi wesnoth&lt;/code&gt;<br /> * Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/<br /> * Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/<br /> <br /> === Slackware 10.2 ===<br /> sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy<br /> * '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/<br /> <br /> === [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===<br /> * Wesnoth 1.0 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 &amp; 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):<br /> ** http://www.unixboard.de/suse/10/wesnoth-1.0-1.i386.rpm for [[SuSE]] 10.0<br /> ** http://www.unixboard.de/suse//wesnoth-1.0-1.i386.rpm for [[SuSE]] 9.3<br /> <br /> <br /> * Wesnoth 0.9.4 (by Luciano Montanaro):<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-0.9.4-9ml.i586.rpm (should work on [[SuSE]] 9.1 and 9.2 too)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-editor-0.9.4-9ml.i586.rpm (level editor)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-server-0.9.4-9ml.i586.rpm (game server)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/src/wesnoth-0.9.4-9ml.src.rpm (source rpm)<br /> <br /> * Wesnoth Binaries for [http://www.opensuse.org OpenSUSE] 10.0, [[SuSE]] Linux 9.3 and [[SuSE]] Linux 9.2, x86, ppc and x86_64. (by [[User:MadOssor|Holger Hetterich]] [mailto:ozzyATmetal-district.de] ) <br /> ** http://81.169.140.126/rpm/wesnoth/ <br /> <br /> '''These packages are also usable as a YaST installation source, use the settings from the table below'''<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot;<br /> ! rowspan=2 | SUSE Release<br /> ! rowspan=2 | Protocol <br /> |- <br /> ! SERVER || DIRECTORY/URL <br /> |-<br /> | [[SuSE]] Linux 9.2 x86/x86_64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.2<br /> |-<br /> | [[SuSE]] Linux 9.3 x86/x86-64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.3<br /> |-<br /> | [[SuSE]] Linux 10.0 x86/x86_64/ppc / [http://www.opensuse.org OpenSUSE 10.0] || HTTP || 81.169.140.126 || rpm/wesnoth/10.0<br /> |-<br /> | Current [http://www.opensuse.org OpenSUSE] Development build x86/x86_64/ppc || HTTP || 81.169.140.126 || rpm/wesnoth/OpenSUSE-current<br /> |}<br /> <br /> '''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''<br /> <br /> === Yoper Linux ===<br /> All versions built for Yoper 2.2.0-6, although they should install on 2.1.<br /> Please let kernowyon know via the Yoper forums if you get any problems<br /> Latest 1.0.2 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm<br /> 1.0.1 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm<br /> Earlier version<br /> *http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm<br /> <br /> === Binaries for all distributions ===<br /> * A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: <br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]<br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz] <br /> ** This is NOT a static binary distribution, it resolves dependencies at runtime.<br /> * Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)<br /> <br /> === Other ===<br /> * [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]<br /> <br /> = See Also =<br /> * [[CompilingWesnoth]]<br /> * [[Download]]</div>

Placid https://wiki.wesnoth.org/index.php?title=WesnothBinariesLinux&diff=8449 2006-03-23T04:17:01Z

<p>Placid: /* Ubuntu */</p> <hr /> <div>= GNU/Linux =<br /> Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.<br /> <br /> === Arch Linux ===<br /> * For the official pkg from [extra]: &lt;code&gt;pacman -S wesnoth&lt;/code&gt; <br /> * dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.<br /> <br /> === Debian ===<br /> * &lt;code&gt;apt-get install wesnoth&lt;/code&gt; or <br /> * &lt;code&gt;aptitude install wesnoth&lt;/code&gt; <br /> * [http://packages.debian.org/wesnoth Official packages]<br /> * [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]<br /> ===&gt; about this backport, maybe an issue with an unresolvable dependancy, the &quot;ttf-dejavu&quot; package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]<br /> <br /> ====&gt; 8 October: adding<br /> <br /> deb http://ftp.tr.debian.org/debian/ unstable main<br /> deb-src http://ftp.tr.debian.org/debian/ unstable main<br /> <br /> to /etc/apt/sources.list,<br /> <br /> Package: wesnoth<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: wesnoth-data<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: *<br /> Pin: release a=stable<br /> Pin-Priority: 700<br /> <br /> Package: *<br /> Pin: release a=testing<br /> Pin-Priority: 650<br /> <br /> Package: *<br /> Pin: release a=unstable<br /> Pin-Priority: 600<br /> <br /> to /etc/apt/preferences and then installing ttf-dejavu with<br /> <br /> apt-get install -t unstable ttf-dejavu<br /> <br /> worked for me ;-)<br /> <br /> <br /> ====&gt; If you want to install the latest Development version you may have to compile it yourself. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].<br /> <br /> '''To install the dependencies :'''<br /> &lt;code&gt;aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev&lt;/code&gt;<br /> <br /> Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by<br /> <br /> &lt;code&gt;aptitude install gettext&lt;/code&gt;<br /> <br /> If someone may confirm that ...<br /> <br /> '''To compile it :'''<br /> If you have already installed and older version of wesnoth, uninstall it by :<br /> <br /> &lt;code&gt;aptitude purge wesnoth&lt;/code&gt;<br /> <br /> Note that will remove all your wesnoth configuration.<br /> Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.<br /> Now, it's very easy :<br /> <br /> &lt;code&gt;cd /usr/src&lt;/code&gt;<br /> <br /> &lt;code&gt;tar -xvzf wesnoth-1.1.1.tar.gz&lt;/code&gt;<br /> <br /> &lt;code&gt;cd wesnoth-1.1.1&lt;/code&gt;<br /> <br /> &lt;code&gt;./configure&lt;/code&gt;<br /> <br /> &lt;code&gt;make&lt;/code&gt;<br /> <br /> &lt;code&gt;make install&lt;/code&gt;<br /> <br /> You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.<br /> <br /> === Ubuntu ===<br /> <br /> Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the latest stable release. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:<br /> *Upgrade to the Dapper Drake, or<br /> *Use the Breezy-Backports repository,<br /> *Use an unofficial repository, or<br /> *Build from the source per Debian above, or<br /> *Use the generic binary for GNU/Linux found on the [[Download]] page.<br /> <br /> Of these options, the final one is most likely the safest at this time.<br /> <br /> See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.<br /> <br /> Do not attempt to install the debian package and associated dependencies using ''dpkg'' as you will break your environment!<br /> <br /> === Fedora Core ===<br /> Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.<br /> * &lt;code&gt;yum install wesnoth wesnoth-tools wesnoth-server&lt;/code&gt; <br /> * Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/<br /> <br /> === Gentoo ===<br /> * &lt;code&gt;emerge wesnoth&lt;/code&gt;<br /> <br /> === klik ===<br /> * The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no &quot;installation&quot; (the base system remains untouched); its created &quot;AppDir&quot; bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:<br /> ** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to &quot;klik&quot; it, type ''klik://wesnoth'' into your Browser<br /> ** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to &quot;klik&quot; it, type ''klik://wesnoth-latest'' into your Browser<br /> <br /> === Mandrake (cooker) ===<br /> * &lt;code&gt;urpmi wesnoth&lt;/code&gt;<br /> * Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/<br /> * Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/<br /> <br /> === Slackware 10.2 ===<br /> sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy<br /> * '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/<br /> <br /> === [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===<br /> * Wesnoth 1.0 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 &amp; 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):<br /> ** http://www.unixboard.de/suse/10/wesnoth-1.0-1.i386.rpm for [[SuSE]] 10.0<br /> ** http://www.unixboard.de/suse//wesnoth-1.0-1.i386.rpm for [[SuSE]] 9.3<br /> <br /> <br /> * Wesnoth 0.9.4 (by Luciano Montanaro):<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-0.9.4-9ml.i586.rpm (should work on [[SuSE]] 9.1 and 9.2 too)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-editor-0.9.4-9ml.i586.rpm (level editor)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-server-0.9.4-9ml.i586.rpm (game server)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/src/wesnoth-0.9.4-9ml.src.rpm (source rpm)<br /> <br /> * Wesnoth Binaries for [http://www.opensuse.org OpenSUSE] 10.0, [[SuSE]] Linux 9.3 and [[SuSE]] Linux 9.2, x86, ppc and x86_64. (by [[User:MadOssor|Holger Hetterich]] [mailto:ozzyATmetal-district.de] ) <br /> ** http://81.169.140.126/rpm/wesnoth/ <br /> <br /> '''These packages are also usable as a YaST installation source, use the settings from the table below'''<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot;<br /> ! rowspan=2 | SUSE Release<br /> ! rowspan=2 | Protocol <br /> |- <br /> ! SERVER || DIRECTORY/URL <br /> |-<br /> | [[SuSE]] Linux 9.2 x86/x86_64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.2<br /> |-<br /> | [[SuSE]] Linux 9.3 x86/x86-64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.3<br /> |-<br /> | [[SuSE]] Linux 10.0 x86/x86_64/ppc / [http://www.opensuse.org OpenSUSE 10.0] || HTTP || 81.169.140.126 || rpm/wesnoth/10.0<br /> |-<br /> | Current [http://www.opensuse.org OpenSUSE] Development build x86/x86_64/ppc || HTTP || 81.169.140.126 || rpm/wesnoth/OpenSUSE-current<br /> |}<br /> <br /> '''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''<br /> <br /> === Yoper Linux ===<br /> All versions built for Yoper 2.2.0-6, although they should install on 2.1.<br /> Please let kernowyon know via the Yoper forums if you get any problems<br /> Latest 1.0.2 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm<br /> 1.0.1 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm<br /> Earlier version<br /> *http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm<br /> <br /> === Binaries for all distributions ===<br /> * A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: <br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]<br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz] <br /> ** This is NOT a static binary distribution, it resolves dependencies at runtime.<br /> * Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)<br /> <br /> === Other ===<br /> * [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]<br /> <br /> = See Also =<br /> * [[CompilingWesnoth]]<br /> * [[Download]]</div>

Placid https://wiki.wesnoth.org/index.php?title=WesnothBinariesLinux&diff=8448 2006-03-23T04:13:46Z

<p>Placid: /* Debian */ clarify need for compilation</p> <hr /> <div>= GNU/Linux =<br /> Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.<br /> <br /> === Arch Linux ===<br /> * For the official pkg from [extra]: &lt;code&gt;pacman -S wesnoth&lt;/code&gt; <br /> * dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.<br /> <br /> === Debian ===<br /> * &lt;code&gt;apt-get install wesnoth&lt;/code&gt; or <br /> * &lt;code&gt;aptitude install wesnoth&lt;/code&gt; <br /> * [http://packages.debian.org/wesnoth Official packages]<br /> * [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]<br /> ===&gt; about this backport, maybe an issue with an unresolvable dependancy, the &quot;ttf-dejavu&quot; package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]<br /> <br /> ====&gt; 8 October: adding<br /> <br /> deb http://ftp.tr.debian.org/debian/ unstable main<br /> deb-src http://ftp.tr.debian.org/debian/ unstable main<br /> <br /> to /etc/apt/sources.list,<br /> <br /> Package: wesnoth<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: wesnoth-data<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: *<br /> Pin: release a=stable<br /> Pin-Priority: 700<br /> <br /> Package: *<br /> Pin: release a=testing<br /> Pin-Priority: 650<br /> <br /> Package: *<br /> Pin: release a=unstable<br /> Pin-Priority: 600<br /> <br /> to /etc/apt/preferences and then installing ttf-dejavu with<br /> <br /> apt-get install -t unstable ttf-dejavu<br /> <br /> worked for me ;-)<br /> <br /> <br /> ====&gt; If you want to install the latest Development version you may have to compile it yourself. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].<br /> <br /> '''To install the dependencies :'''<br /> &lt;code&gt;aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev&lt;/code&gt;<br /> <br /> Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by<br /> <br /> &lt;code&gt;aptitude install gettext&lt;/code&gt;<br /> <br /> If someone may confirm that ...<br /> <br /> '''To compile it :'''<br /> If you have already installed and older version of wesnoth, uninstall it by :<br /> <br /> &lt;code&gt;aptitude purge wesnoth&lt;/code&gt;<br /> <br /> Note that will remove all your wesnoth configuration.<br /> Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.<br /> Now, it's very easy :<br /> <br /> &lt;code&gt;cd /usr/src&lt;/code&gt;<br /> <br /> &lt;code&gt;tar -xvzf wesnoth-1.1.1.tar.gz&lt;/code&gt;<br /> <br /> &lt;code&gt;cd wesnoth-1.1.1&lt;/code&gt;<br /> <br /> &lt;code&gt;./configure&lt;/code&gt;<br /> <br /> &lt;code&gt;make&lt;/code&gt;<br /> <br /> &lt;code&gt;make install&lt;/code&gt;<br /> <br /> You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.<br /> <br /> === Ubuntu ===<br /> <br /> Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the current latest version.<br /> <br /> Battle for Wesnoth 1.0-1 is included in Ubuntu Breezy's universe collection. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:<br /> *Upgrade to the Dapper Drake, or<br /> *Use the Breezy-Backports repository, or<br /> *Use an unofficial repository, or<br /> *Build from the source per Debian above, or<br /> *Use the generic binary for GNU/Linux found on the [[Download]] page.<br /> <br /> Of these options, the final one is most likely the safest at this time.<br /> <br /> See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.<br /> <br /> === Fedora Core ===<br /> Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.<br /> * &lt;code&gt;yum install wesnoth wesnoth-tools wesnoth-server&lt;/code&gt; <br /> * Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/<br /> <br /> === Gentoo ===<br /> * &lt;code&gt;emerge wesnoth&lt;/code&gt;<br /> <br /> === klik ===<br /> * The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no &quot;installation&quot; (the base system remains untouched); its created &quot;AppDir&quot; bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:<br /> ** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to &quot;klik&quot; it, type ''klik://wesnoth'' into your Browser<br /> ** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to &quot;klik&quot; it, type ''klik://wesnoth-latest'' into your Browser<br /> <br /> === Mandrake (cooker) ===<br /> * &lt;code&gt;urpmi wesnoth&lt;/code&gt;<br /> * Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/<br /> * Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/<br /> <br /> === Slackware 10.2 ===<br /> sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy<br /> * '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/<br /> <br /> === [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===<br /> * Wesnoth 1.0 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 &amp; 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):<br /> ** http://www.unixboard.de/suse/10/wesnoth-1.0-1.i386.rpm for [[SuSE]] 10.0<br /> ** http://www.unixboard.de/suse//wesnoth-1.0-1.i386.rpm for [[SuSE]] 9.3<br /> <br /> <br /> * Wesnoth 0.9.4 (by Luciano Montanaro):<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-0.9.4-9ml.i586.rpm (should work on [[SuSE]] 9.1 and 9.2 too)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-editor-0.9.4-9ml.i586.rpm (level editor)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-server-0.9.4-9ml.i586.rpm (game server)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/src/wesnoth-0.9.4-9ml.src.rpm (source rpm)<br /> <br /> * Wesnoth Binaries for [http://www.opensuse.org OpenSUSE] 10.0, [[SuSE]] Linux 9.3 and [[SuSE]] Linux 9.2, x86, ppc and x86_64. (by [[User:MadOssor|Holger Hetterich]] [mailto:ozzyATmetal-district.de] ) <br /> ** http://81.169.140.126/rpm/wesnoth/ <br /> <br /> '''These packages are also usable as a YaST installation source, use the settings from the table below'''<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot;<br /> ! rowspan=2 | SUSE Release<br /> ! rowspan=2 | Protocol <br /> |- <br /> ! SERVER || DIRECTORY/URL <br /> |-<br /> | [[SuSE]] Linux 9.2 x86/x86_64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.2<br /> |-<br /> | [[SuSE]] Linux 9.3 x86/x86-64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.3<br /> |-<br /> | [[SuSE]] Linux 10.0 x86/x86_64/ppc / [http://www.opensuse.org OpenSUSE 10.0] || HTTP || 81.169.140.126 || rpm/wesnoth/10.0<br /> |-<br /> | Current [http://www.opensuse.org OpenSUSE] Development build x86/x86_64/ppc || HTTP || 81.169.140.126 || rpm/wesnoth/OpenSUSE-current<br /> |}<br /> <br /> '''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''<br /> <br /> === Yoper Linux ===<br /> All versions built for Yoper 2.2.0-6, although they should install on 2.1.<br /> Please let kernowyon know via the Yoper forums if you get any problems<br /> Latest 1.0.2 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm<br /> 1.0.1 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm<br /> Earlier version<br /> *http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm<br /> <br /> === Binaries for all distributions ===<br /> * A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: <br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]<br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz] <br /> ** This is NOT a static binary distribution, it resolves dependencies at runtime.<br /> * Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)<br /> <br /> === Other ===<br /> * [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]<br /> <br /> = See Also =<br /> * [[CompilingWesnoth]]<br /> * [[Download]]</div>

Placid https://wiki.wesnoth.org/index.php?title=WesnothBinariesLinux&diff=8447 2006-03-23T04:12:17Z

<p>Placid: /* Ubuntu */</p> <hr /> <div>= GNU/Linux =<br /> Not all Distributions are always at the state of the current release. If you want to be sure to have the current version, please get the sources and compile it yourself.<br /> <br /> === Arch Linux ===<br /> * For the official pkg from [extra]: &lt;code&gt;pacman -S wesnoth&lt;/code&gt; <br /> * dibblethewrecker also provides regular SVN snapshots. Please see [[ http://dtw.jiwe.org/content.php?article.9 | here]] for details of how to access the repo. As development of wesnoth continues this repo is likely to follow the unstable branch.<br /> <br /> === Debian ===<br /> * &lt;code&gt;apt-get install wesnoth&lt;/code&gt; or <br /> * &lt;code&gt;aptitude install wesnoth&lt;/code&gt; <br /> * [http://packages.debian.org/wesnoth Official packages]<br /> * [http://debian.wesnoth.org/sarge Wesnoth 1.0 backport for Sarge]<br /> ===&gt; about this backport, maybe an issue with an unresolvable dependancy, the &quot;ttf-dejavu&quot; package which is required but does not belong to sarge main archive. If someone could confirm ? [ 4 october 2005 ]<br /> <br /> ====&gt; 8 October: adding<br /> <br /> deb http://ftp.tr.debian.org/debian/ unstable main<br /> deb-src http://ftp.tr.debian.org/debian/ unstable main<br /> <br /> to /etc/apt/sources.list,<br /> <br /> Package: wesnoth<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: wesnoth-data<br /> Pin: version 1.0-1sarge*<br /> Pin-Priority: 1001<br /> <br /> Package: *<br /> Pin: release a=stable<br /> Pin-Priority: 700<br /> <br /> Package: *<br /> Pin: release a=testing<br /> Pin-Priority: 650<br /> <br /> Package: *<br /> Pin: release a=unstable<br /> Pin-Priority: 600<br /> <br /> to /etc/apt/preferences and then installing ttf-dejavu with<br /> <br /> apt-get install -t unstable ttf-dejavu<br /> <br /> worked for me ;-)<br /> <br /> <br /> ====&gt; If you want to install the Developpement version (1.1.1) you'll have to compile it. See [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth].<br /> <br /> '''To install the dependencies :'''<br /> &lt;code&gt;aptitude install libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libfreetype6-dev&lt;/code&gt;<br /> <br /> Remains one package : libintl which isn't in the Debian packages database, but I think you can install it by<br /> <br /> &lt;code&gt;aptitude install gettext&lt;/code&gt;<br /> <br /> If someone may confirm that ...<br /> <br /> '''To compile it :'''<br /> If you have already installed and older version of wesnoth, uninstall it by :<br /> <br /> &lt;code&gt;aptitude purge wesnoth&lt;/code&gt;<br /> <br /> Note that will remove all your wesnoth configuration.<br /> Then, download the source by wget, or your internet navigator. Save it in the /usr/src directory.<br /> Now, it's very easy :<br /> <br /> &lt;code&gt;cd /usr/src&lt;/code&gt;<br /> <br /> &lt;code&gt;tar -xvzf wesnoth-1.1.1.tar.gz&lt;/code&gt;<br /> <br /> &lt;code&gt;cd wesnoth-1.1.1&lt;/code&gt;<br /> <br /> &lt;code&gt;./configure&lt;/code&gt;<br /> <br /> &lt;code&gt;make&lt;/code&gt;<br /> <br /> &lt;code&gt;make install&lt;/code&gt;<br /> <br /> You may have more information about this part in the [http://www.wesnoth.org/wiki/CompilingWesnoth Compiling Wesnoth] page.<br /> <br /> === Ubuntu ===<br /> <br /> Battle for Wesnoth 1.0.1-1 is included in Ubuntu Dapper's universe collection. This is the current latest version.<br /> <br /> Battle for Wesnoth 1.0-1 is included in Ubuntu Breezy's universe collection. As this is not the latest version, Breezy users will need to do one of the following to obtain the latest version:<br /> *Upgrade to the Dapper Drake, or<br /> *Use the Breezy-Backports repository, or<br /> *Use an unofficial repository, or<br /> *Build from the source per Debian above, or<br /> *Use the generic binary for GNU/Linux found on the [[Download]] page.<br /> <br /> Of these options, the final one is most likely the safest at this time.<br /> <br /> See the [http://help.ubuntu.com/starterguide/C/faqguide-all.html#addinguniverse Ubuntu Starter Guide]'s section on adding the universe repositories.<br /> <br /> === Fedora Core ===<br /> Battle for Wesnoth is included in [http://fedoraproject.org/wiki/Extras/ Fedora Extras], which is enabled in Fedora Core 4 by default.<br /> * &lt;code&gt;yum install wesnoth wesnoth-tools wesnoth-server&lt;/code&gt; <br /> * Wesnoth 1.0rc1: http://download.fedora.redhat.com/pub/fedora/linux/extras/<br /> <br /> === Gentoo ===<br /> * &lt;code&gt;emerge wesnoth&lt;/code&gt;<br /> <br /> === klik ===<br /> * The most easy way to testdrive BfW is provided via [http://klik.atekon.de/ klik]. klik enables clients to create distribution-independent binaries which require no &quot;installation&quot; (the base system remains untouched); its created &quot;AppDir&quot; bundles run even from USB stick or CD RW. klik support is pre-enabled on Knoppix and Kanotix Live CDs. Other distros need to install a small klik client (less than 20 kByte download, less than 20 seconds effort). See the [http://klik.atekon.de/wiki/index.php/User%27s_FAQ klik FAQ] for details. A [http://wesnoth.klik.atekon.de/ BfW-specific klik website] has links to help with the package. Once the klik client is installed, look at this:<br /> ** [http://wesnoth.klik.atekon.de/ Wesnoth-1.0] stable Version: to &quot;klik&quot; it, type ''klik://wesnoth'' into your Browser<br /> ** [http://wesnoth-latest.klik.atekon.de/ Wesnoth-1.1.1] Development-Version: to &quot;klik&quot; it, type ''klik://wesnoth-latest'' into your Browser<br /> <br /> === Mandrake (cooker) ===<br /> * &lt;code&gt;urpmi wesnoth&lt;/code&gt;<br /> * Binary: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/i586/media/contrib/<br /> * Source: ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/cooker/contrib/SRPMS/<br /> <br /> === Slackware 10.2 ===<br /> sorry but the 10.1 isn't out. Don't worry the 10.2 is here \o/ enjoy<br /> * '''Wesnoth 1.0.2''': http://asteroid.celeonet.fr/wesnoth/<br /> <br /> === [[SuSE]] / [http://www.opensuse.org OpenSUSE] ===<br /> * Wesnoth 1.0 ([mailto:sven_AT_unixboard.de build on SuSE 9.3 &amp; 10.0 by Sven Gawlik] hostet on [http://www.unixboard.de Unixboard.de]):<br /> ** http://www.unixboard.de/suse/10/wesnoth-1.0-1.i386.rpm for [[SuSE]] 10.0<br /> ** http://www.unixboard.de/suse//wesnoth-1.0-1.i386.rpm for [[SuSE]] 9.3<br /> <br /> <br /> * Wesnoth 0.9.4 (by Luciano Montanaro):<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-0.9.4-9ml.i586.rpm (should work on [[SuSE]] 9.1 and 9.2 too)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-editor-0.9.4-9ml.i586.rpm (level editor)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/i586/wesnoth-server-0.9.4-9ml.i586.rpm (game server)<br /> ** http://www.cirulla.net/listing/suse-rpm/rpm/9.3/src/wesnoth-0.9.4-9ml.src.rpm (source rpm)<br /> <br /> * Wesnoth Binaries for [http://www.opensuse.org OpenSUSE] 10.0, [[SuSE]] Linux 9.3 and [[SuSE]] Linux 9.2, x86, ppc and x86_64. (by [[User:MadOssor|Holger Hetterich]] [mailto:ozzyATmetal-district.de] ) <br /> ** http://81.169.140.126/rpm/wesnoth/ <br /> <br /> '''These packages are also usable as a YaST installation source, use the settings from the table below'''<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot;<br /> ! rowspan=2 | SUSE Release<br /> ! rowspan=2 | Protocol <br /> |- <br /> ! SERVER || DIRECTORY/URL <br /> |-<br /> | [[SuSE]] Linux 9.2 x86/x86_64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.2<br /> |-<br /> | [[SuSE]] Linux 9.3 x86/x86-64 || HTTP || 81.169.140.126 || rpm/wesnoth/9.3<br /> |-<br /> | [[SuSE]] Linux 10.0 x86/x86_64/ppc / [http://www.opensuse.org OpenSUSE 10.0] || HTTP || 81.169.140.126 || rpm/wesnoth/10.0<br /> |-<br /> | Current [http://www.opensuse.org OpenSUSE] Development build x86/x86_64/ppc || HTTP || 81.169.140.126 || rpm/wesnoth/OpenSUSE-current<br /> |}<br /> <br /> '''The OpenSUSE Development build is Wesnoth for the current OpenSUSE releases (aka 10.1)'''<br /> <br /> === Yoper Linux ===<br /> All versions built for Yoper 2.2.0-6, although they should install on 2.1.<br /> Please let kernowyon know via the Yoper forums if you get any problems<br /> Latest 1.0.2 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0.2-1.i686.rpm<br /> 1.0.1 version<br /> * http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-1.0-1.i686.rpm<br /> Earlier version<br /> *http://yoperstuff.kernowyon.org.uk/rpms/wesnoth-0.9.7-1.i686.rpm<br /> <br /> === Binaries for all distributions ===<br /> * A distribution-independent binary (made with [http://oblisk.codu.org/ OBLISK]) for any somewhat modern GNU/Linux on i386 is available: <br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.1.1-x86-Opkg.tar.gz?download wesnoth-1.1.1-x86-Opkg.tar.gz]<br /> ** [http://prdownloads.sourceforge.net/suparun/wesnoth-1.0.1-x86-Opkg.tar.gz?download wesnoth-1.0.1-x86-Opkg.tar.gz] <br /> ** This is NOT a static binary distribution, it resolves dependencies at runtime.<br /> * Wesnoth 0.8.8 static binary (by Yann): http://prdownloads.sourceforge.net/wesnoth/wesnoth-i386-static?download (needs the [http://prdownloads.sourceforge.net/wesnoth/wesnoth-0.8.tar.gz?download source tarball] for the data - run it with the path to the unpacked data as argument)<br /> <br /> === Other ===<br /> * [http://rpmfind.net/linux/rpm2html/search.php?query=wesnoth Search RPMs]<br /> <br /> = See Also =<br /> * [[CompilingWesnoth]]<br /> * [[Download]]</div>

Placid https://wiki.wesnoth.org/index.php?title=CampaignNorthernRebirth&diff=8392 2006-03-22T11:48:46Z

<p>Placid: /* Translation of Northern Rebirth */</p> <hr /> <div>== Translation of Northern Rebirth ==<br /> <br /> This is a list of the people currently translating Northern Rebirth into different languages:<br /> <br /> &lt;table border=&quot;1&quot; style=&quot;width:65%&quot;&gt;<br /> &lt;tr&gt;&lt;th&gt;Language&lt;/th&gt;&lt;th&gt;Translator&lt;/th&gt;&lt;th&gt;Status&lt;/th&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Afrikaans (af)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Brazilian Portuguese (pt_BR)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;British English (en_GB)&lt;/td&gt;&lt;td&gt;Placid&lt;/td&gt;&lt;td&gt;Work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Bulgarian (bg)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Catalan (ca)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Chinese (zh_CN)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Czech (cs)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Danish (da)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Dutch (nl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Estonian (et)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Finnish (fi)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;French (fr)&lt;/td&gt;&lt;td&gt;gdou&lt;/td&gt;&lt;td&gt;Work in progress&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;German (de)&lt;/td&gt;&lt;td&gt;Belchion&lt;/td&gt;&lt;td&gt;completed (not active)&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Greek (el_GR)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Hungarian (hu)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Italian (it)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Japanese (ja)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Latin (la)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Norwegian (no)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Polish (pl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Russian (ru)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Serbian (sr)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Slovak (sk)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Slovenian (sl)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Spanish (es)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Swedish (sv)&lt;/td&gt;&lt;td&gt;Unassigned&lt;/td&gt;&lt;td&gt;stalled&lt;/td&gt;&lt;/tr&gt;<br /> &lt;tr&gt;&lt;td&gt;Turkish (tr)&lt;/td&gt;&lt;td&gt;?&lt;/td&gt;&lt;td&gt;unknown&lt;/td&gt;&lt;/tr&gt;<br /> &lt;/table&gt;<br /> <br /> == Status Descriptions ==<br /> * '''unknown'''<br /> <br /> It is not known if someone is actually translating this campaign.<br /> * '''work in progress'''<br /> <br /> Someone is working on it, but it is not done, yet.<br /> * '''completed'''<br /> <br /> It is already completed and updated when there are changes.<br /> * '''completed (not active)'''<br /> <br /> It is already completed and but not updated when there are changes.<br /> <br /> == See Also ==<br /> <br /> * [[WesCamp]]<br /> * [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Northern_Rebirth&amp;order=trans Translation stats for Northern Rebirth]</div>

Placid https://wiki.wesnoth.org/index.php?title=Template:WML_Tags&diff=8385 2006-03-22T02:07:38Z

<p>Placid: tighten layout</p> <hr /> <div>{| class=&quot;gallery&quot; style=&quot;width:175px;float: right;border: 1px solid #B48648; color:#B48648; font-size: 7pt;margin-left;10px;&quot;<br /> |-<br /> |<br /> &lt;span style=&quot;float: right;&quot;&gt;&lt;small class=&quot;editlink noprint plainlinksneverexpand&quot;&gt;[{{SERVER}}{{localurl:Template:WML Tags|action=edit}} edit ]&lt;/small&gt;&lt;/span&gt;<br /> '''WML Tags'''<br /> <br /> |-<br /> |''A:'' <br /> [[CampaignWML#The_.5Babout.5D_tag|about]],[[StatisticalScenarioWML|advances]],<br /> [[UnitWML|advancefrom]],<br /> [[AiWML|ai]],<br /> [[DirectActionsWML|allow_recruit]],<br /> [[VariablesWML|array]],<br /> [[AttackWML|attack]],<br /> [[StatisticalScenarioWML|attacks]],<br /> [[AiWML|avoid]];<br /> |-<br /> |''B:'' <br /> [[CampaignWML#The_.5Bbinary_path.5D_tag|binary_path]],[[HelpWML|bold]];<br /> |-<br /> |''C:'' <br /> [[CampaignWML#The_.5Bcampaign.5D_tag|campaign]], [[DirectActionsWML|capture_village]], [[ReplayWML|choose]],<br /> [[InternalActionsWML|clear_variable]],<br /> [[InterfaceActionsWML|colour_adjust]],<br /> [[ReplayWML|command]];<br /> |-<br /> |''D:'' <br /> [[StatisticalScenarioWML|deaths]],[[UnitWML|defend]],[[StatisticalScenarioWML|defends]],<br /> [[UnitWML|defense]],<br /> [[InterfaceActionsWML|delay]],<br /> [[ReplayWML|destination]],<br /> [[DirectActionsWML|disallow_recruit]],<br /> [[InternalActionsWML|do]];<br /> |-<br /> |''E:'' <br /> [[UnitsWML|effect]],[[InternalActionsWML|else]],[[ReplayWML|end_turn]],<br /> [[DirectActionsWML|endlevel]],<br /> [[EraWML|era]],<br /> [[EventWML|event]],<br /> [[ThemeWML|expenses]];<br /> |-<br /> |''F:'' <br /> [[FilterWML|filter]], [[FilterWML|filter_second]], [[HelpWML|format]], [[AttackWML|frame]];<br /> |-<br /> |''G:'' <br /> [[GameConfigWML|game_config]], [[ScenarioWML|generator]], [[ThemeWML|gold]];<br /> |-<br /> |''H:'' <br /> [[InternalActionsWML|have_unit]], [[HelpWML|header]], [[InterfaceActionsWML|hide_unit]];<br /> |-<br /> |''I:'' <br /> [[InternalActionsWML|if]], [[TimeWML|illuminated_time]], [[TerrainGraphicsWML|image]],<br /> [[HelpWML|img]], [[ThemeWML|income]], [[HelpWML|italic]], [[InterfaceActionsWML|item]];<br /> |-<br /> |''J:''<br /> [[HelpWML|jump]];<br /> |-<br /> |''K:'' <br /> [[DirectActionsWML|kill]], [[StatisticalScenarioWML|killed]];<br /> |-<br /> |''L:'' <br /> [[ThemeWML|label]], [[LanguageWML|language]], [[AiWML|leader_goal]];<br /> |-<br /> |''M:'' <br /> [[ThemeWML|main_map]],[[ThemeWML|menu]], [[InterfaceActionsWML|message]], [[ThemeWML|mini_map]],<br /> [[AttackWML|missile_frame]], [[SingleUnitWML|modifications]], [[DirectActionsWML|modify_side]],<br /> [[ReplayWML|move]], [[InterfaceActionsWML|move_unit_fake]], [[UnitWML|movement costs]],<br /> [[UnitsWML|movetype]], [[ScenarioWML|multiplayer]], [[EraWML|multiplayer_side]], [[InterfaceActionsWML|music]];<br /> |-<br /> |''N:'' <br /> [[FilterWML|not]], [[ThemeWML|num_units]];<br /> |-<br /> |''O:'' <br /> [[DirectActionsWML|object]], [[InterfaceActionsWML|objectives]], [[InterfaceActionsWML|objective]],<br /> [[ThemeWML|observers]], [[InterfaceActionsWML|option]], [[InternalActionsWML|or]];<br /> |-<br /> |''P:'' <br /> [[ThemeWML|panel]], [[IntroWML|part]], [[DirectActionsWML|place_shroud]], [[ThemeWML|position]],<br /> [[InterfaceActionsWML|print]], [[AiWML|protect_location]], [[AiWML|protect_unit]];<br /> |-<br /> |''R:'' <br /> [[UnitsWML|race]], [[ReplayWML|random]], [[ReplayWML|recall]], [[StatisticalScenarioWML|recalls]],<br /> [[ReplayWML|recruit]], [[StatisticalScenarioWML|recruits]], [[InterfaceActionsWML|redraw]],<br /> [[HelpWML|ref]], [[DirectActionsWML|remove_shroud]], [[InterfaceActionsWML|remove_unit_overlay]],<br /> [[InterfaceActionsWML|removeitem]], [[SavefileWML|replay]], [[SavefileWML|replay_start]],<br /> [[UnitWML|resistance]], [[ThemeWML|resolution]], [[ReplayWML|results]], [[InternalActionsWML|role]];<br /> |-<br /> |''S:'' <br /> [[SavefileWML|save]], [[ScenarioWML|scenario]],[[InterfaceActionsWML|scroll]], [[InterfaceActionsWML|scroll_to]],<br /> [[InterfaceActionsWML|scroll_to_unit]], [[HelpWML|section]], [[DirectActionsWML|set_recruit]],<br /> [[InternalActionsWML|set_variable]], [[SideWML|side]], [[ThemeWML|side_playing]], [[SavefileWML|snapshot]],<br /> [[InterfaceActionsWML|sound]], [[ReplayWML|source]], [[StatisticalScenarioWML|statistics]],<br /> [[ThemeWML|status]], [[DirectActionsWML|stone]], [[InternalActionsWML|store_gold]], [[InternalActionsWML|store_locations]],<br /> [[InternalActionsWML|store_starting_location]], [[InternalActionsWML|store_unit]], [[IntroWML|story]];<br /> |-<br /> |''T:'' <br /> [[AiWML|target]], [[StatisticalScenarioWML|team]], [[DirectActionsWML|teleport]], [[UnitWML|teleport_anim]],<br /> [[TerrainWML|terrain]], [[TerrainGraphicsWML|terrain_graphics]], [[ScenarioWML#Test_scenario|test]],<br /> [[CampaignWML#The_.5Btextdomain.5D_tag|textdomain]], [[ThemeWML|theme]], [[InternalActionsWML|then]],<br /> [[TerrainGraphicsWML|tile]], [[TimeWML|time]], [[ScenarioWML|time_area]], [[ThemeWML|time_of_day]],<br /> [[HelpWML|topic]], [[HelpWML|toplevel]], [[SingleUnitWML|trait]], [[ThemeWML|turn]], [[ScenarioWML|tutorial]];<br /> |-<br /> |''U:'' <br /> [[InterfaceActionsWML|unhide_unit]], unit&amp;nbsp;([[UnitWML|define]], [[DirectActionsWML|create]]),<br /> [[ThemeWML|unit_abilities]], [[ThemeWML|unit_alignment]], [[ThemeWML|unit_description]],<br /> [[ThemeWML|unit_hp]], [[ThemeWML|unit_image]], [[ThemeWML|unit_level]], [[ThemeWML|unit_moves]],<br /> [[InterfaceActionsWML|unit_overlay]], [[ThemeWML|unit_profile]], [[ThemeWML|unit_status]],<br /> [[ThemeWML|unit_traits]], [[ThemeWML|unit_type]], [[ThemeWML|unit_weapons]], [[ThemeWML|unit_xp]],<br /> [[UnitsWML|units]], [[DirectActionsWML|unstone]], [[DirectActionsWML|unstore_unit]], [[ThemeWML|upkeep]];<br /> |-<br /> | ''V:'' <br /> [[InternalActionsWML|variable]], [[VariablesWML|variables]], [[SideWML|village]], [[ThemeWML|villages]];<br /> |-<br /> | ''W:'' <br /> [[InternalActionsWML|while]]<br /> |}</div>

Placid https://wiki.wesnoth.org/index.php?title=Geography_of_Wesnoth&diff=8379 2006-03-22T01:31:35Z

<p>Placid: /* Wesnoth */ sp</p> <hr /> <div>== Wesnoth and Surrounding Lands ==<br /> <br /> Here's a link to a [http://www.wesnoth.org/misc/httt-hi-res.jpg '''big''' (2.3 MB)] black and white version of the map.<br /> <br /> http://svn.gna.org/viewcvs/*checkout*/wesnoth/trunk/images/maps/wesnoth.png<br /> <br /> * International land features:<br /> ** The Ocean: Nameless and unlabeled, it lies to the west of the continent and all rivers flow eventually to it<br /> ** The Bay of Pearls: The Elensefar Peninsula in the North and the Isle of Anduin in the southwest separate this from the Great Sea<br /> ** The Great River: Most rivers in the land eventually flow to it. The islands in its delta are home to the citizens of Elensefar<br /> ** The Barren Swamp: Basically lifeless and hard to traverse, it formed a natural boundary between the Elvish and Human lands<br /> <br /> === Wesnoth ===<br /> The Kingdom of Wesnoth lies in the center of the land. Most of the campaigns revolve around it. Its borders are the Great River to the north, the Lower Hills in the east and south, the Green Swamp to the southwest, and the Ocean<br /> to the west.<br /> * Notable cities:<br /> ** Weldyn: The capital of Wesnoth<br /> ** Aldril: City lying on the Bay of Pearls<br /> ** Blackwater Port: City lying south of the Bay of Pearls<br /> ** Carcyn: City on the Wesnoth-Elensefar border, shared with Elensefar<br /> ** Dan'Tonk: Wesnoth's largest city located in the center of the country, just west of Weldyn<br /> ** Miluz: The easternmost border outpost<br /> ** Soradoc: The northernmost border outpost<br /> ** Fort Tahn: The southernmost border outpost<br /> ** Tath: A wilderness city north of Dan'Tonk that serves the military patrols traveling to Abez<br /> * Notable land features:<br /> ** Gryphon Mountain: Home of the fabled Gryphons<br /> ** Ford of Abez: Shallow part of the Great River, it is usually controlled by Wesnothian forces<br /> ** Weldyn River: It branches from the Great River and goes south<br /> ** Great Central Plain: Area bounded by Weldyn, Dan'Tonk, and Fort Tahn, this plain is Wesnoth's bread basket and home to most of its population<br /> ** Dulatus Hills: These rolling hills bordering the Great Central Plain provide much of Wesnoth's livestock and agriculture<br /> ** Brown Hills: Wasteland surrounding Gryphon Mountain that is not well-populated and occasionally very dangerous<br /> ** Glyn's Forest: Sometimes known as the Royal Forest, named for one of Haldric II's sons<br /> ** Gray Woods: Large forest in the heart of the wilds of Wesnoth, located between Carcyn and Aldril and generally considered to be haunted<br /> ** Green Swamp: Large swamp in the heart of the wilds of Wesnoth, south of Aldril. It receives drainage from the Brown Hills and feeds into the Great River.<br /> <br /> === Southwest Elven Lands ===<br /> The Wood Elves are separate from those of the north, and have a frigid relationship with them and most other countries. Its borders are the Green Swamp to the northeast, the desert (not shown) to the south, and the Ocean to the west.<br /> * Notable cities<br /> ** none known<br /> * Notable land features:<br /> ** Aethen Forest: The largest southern forest, it extends far to the southwest - much farther than is charted - and is home to elves<br /> ** Weldyn River: By this point it is very large and provides good trade<br /> <br /> === Elensefar ===<br /> Elensefar is at times a province of Wesnoth, at times an independent country, and at times in a loosely defined treaty with Wesnoth. Its borders are the Great River to the north, a loosely defined line with Wesnoth to the<br /> east, the Bay of Pearls to the south, and the ocean to the west.<br /> * Notable cities:<br /> ** Elensefar: The capital, located on an island in the Great River delta<br /> ** Carcyn: City on the Wesnoth-Elensefar border, shared with Wesnoth<br /> * Notable land features:<br /> ** Great River: It is very wide at this point, and only ships can cross it<br /> <br /> === Northlands ===<br /> <br /> There is no government of the Northlands. Various groups of orcs, dwarves, barbarian men and even elves populate the region. The northern and eastern borders are not defined, the southern border is the Great River, and the western border is the Ocean.<br /> * Notable cities:<br /> ** Glamdrol: An Orcish tribal capital<br /> ** Romyr: Another Orcish tribal capital<br /> ** North Elven Capital: Of unknown location deep in the Northeast Forest<br /> ** Wesmere: The location of the Ka'lian - the Elvish Council<br /> ** Caverns of Knalga: Various dwarven cities exist under here<br /> ** Dallben and Delwyn: Human villages originally built by settlers who crossed the Great River during Wesnoth's Golden Age expansion. Now abandoned. The forested area northeast of Elensefar, where these villages were located, was named the Annuvin province by men but was known by the elves as Wesmere.<br /> * Notable land features:<br /> ** Northern Mountains: A virtually unpassable barrier<br /> ** Devon Lake: A mountain lake whose river carves the only pathway through the Northern Mountains<br /> ** River Glaaq: The river than comes out of Devon Lake<br /> ** Northern Forest: A gigantic forest whose eastern boundary only the elves know<br /> ** Great River: The origin of this river is somewhere in the east of the northern lands<br /> ** Suquets Forest: A forest on the Great River near Elensefar, in early times called Wesmere<br /> <br /> == Far North ==<br /> <br /> http://savannah.nongnu.org/cgi-bin/viewcvs/*checkout*/wesnoth/wesnoth/images/campaigns/Son_Of_The_Black_Eye/maps/sotbe.png<br /> <br /> Cold, harsh, and inaccessible, the Far North is the ancestral home of the Orcish Clannate. It lies north of the Northern Mountains, which the Orcs call the Haggid-Dargor and claim (without merit) as their own. To the east lie the Unaligned Tribes of the Wild Steppe, who fell out of the control of the Clannate, instead roaming with wild human barbarians and clashing with the High Elves of the North Plains (known as North Elves in human lands). The High Elves themselves reside further east, where it is rumored they rule a vast kingdom.<br /> <br /> * Notable cities:<br /> ** Barag Gor, a city home to the Orcish Council<br /> ** Bitok<br /> ** Borstep<br /> ** Castelfrang<br /> ** Farzi<br /> ** Festog<br /> ** Grisbi<br /> ** Lmarig<br /> ** Melmog<br /> ** Prestim<br /> ** Tirigaz<br /> * Notable land features:<br /> ** Swamp of Desolation<br /> ** Mountains of Dorth<br /> ** Mountains of Haag<br /> ** Green Forest<br /> ** Silent Forest<br /> ** Forest of Thelien<br /> ** River Oumph<br /> ** River Bork<br /> ** Wild Steppe<br /> <br /> == The Green Isle ==<br /> <br /> http://savannah.nongnu.org/cgi-bin/viewcvs/*checkout*/wesnoth/wesnoth/images/campaigns/The_Rise_of_Wesnoth/maps/the_green_isle.png<br /> <br /> === Wesfolk Land ===<br /> This is where the Wesfolk live, with their Lich overlords. The boundary between it and the Islefolk land is the hilly area running south-west to north-east. The Wesfolk land is in the north-west. Little is known about what happened to the island after Haldric left.<br /> * Notable cities:<br /> ** Jevyan: The capital of the Wesfolk, where Jevyan reigned; presumably where the gates to orcland were opened<br /> * Notable land features<br /> ** None. (its not a very detailed map, is it? :) )<br /> <br /> === Islefolk Land ===<br /> This is where the Islefolk (Haldric's folk) live. The boundary is the same as that of the Wesfolk; the islefolk land is to the southeast.<br /> * Notable cities:<br /> ** Blackmore: {??}<br /> ** Clearwater Port: {??}<br /> ** Southbay: {??}<br /> * Notable land features:<br /> ** None. (see Wesfolk land)<br /> <br /> == See Also ==<br /> <br /> * [[WesnothHistory]]</div>

Placid https://wiki.wesnoth.org/index.php?title=Create&diff=8378 2006-03-22T01:28:11Z

<p>Placid: float TOC right</p> <hr /> <div>{| style=&quot;float:right&quot;<br /> |<br /> __TOC__<br /> |}<br /> Interested in creating your own scenarios and campaigns? One of Wesnoth's best features is its extensibility. Players can create new maps, units, races, scenarios, art, music, and even entire campaigns. Access to the &quot;guts&quot; of the game is both simple and difficult; if you have an ASCII text editor you have everything you need to build your own world. However, learning the Wesnoth Markup Language (WML) takes some effort. This section will guide you through the process of creating and distributing your own content.<br /> <br /> It should also be noted that '''we need a lot of help creating artwork for the core of the game.''' The current projects we are working on are [http://www.wesnoth.org/forum/viewtopic.php?t=9162 listed here]. We'll happily help you out, if you take a swing at them.<br /> <br /> == Read this first! ==<br /> Before you modify or add anything, it is important to understand how the game stores and organizes its data. This article will explain the game's directory structure and introduce the ''userdata'' directory.<br /> * [[EditingWesnoth]]<br /> <br /> == What can I create, and how? ==<br /> <br /> &lt;div class=&quot;thumb tright&quot;&gt;&lt;div&gt;<br /> [http://www.wesnoth.org/images/sshots/wesnoth_editor-1.jpg http://www.wesnoth.org/images/sshots/wesnoth_editor-1-175.jpg]<br /> &lt;div class=&quot;thumbcaption&quot;&gt;Battle for Wesnoth Map editor&lt;/div&gt;&lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> * [[BuildingMaps|Maps]] - the layout of terrain tiles<br /> * [[BuildingScenarios|Scenarios]] - a scenario makes things happen on a map, making it playable<br /> * [[BuildingCampaigns|Campaigns]] - how to put it all together into a campaign<br /> * [[BuildingMultiplayer|Multiplayer Maps and Scenarios]] - a specialized look at maps and scenarios<br /> * [[BuildingUnits|Units]]<br /> * [[BuildingFactions|Multiplayer factions and eras]]<br /> * '''[[Create Art|Art]]''' - complete with '''tutorials!'''<br /> * [[Create Music|Music]]<br /> * [[Distributing content]] - all about the campaign server<br /> * [[WesnothTranslations|Translations]] - work on translating Wesnoth<br /> <br /> == What have others done? ==<br /> Quick descriptions of the campaigns and scenarios that have been published on the campaign server.<br /> * [[UserScenarios|User contributed campaigns]]<br /> This there are a multitude multiplayer maps and discussion of the campaigns on the [http://www.wesnoth.org/forum Wesnoth forum]<br /> * [http://www.wesnoth.org/forum/viewforum.php?f=15 Multiplayer development forum]<br /> * [http://www.wesnoth.org/forum/viewforum.php?f=8 Scenario and campaign development forum]<br /> * [[Complete Faction List (unfinished)|Complete Faction List]]<br /> <br /> == The world of Wesnoth ==<br /> Many campaigns do not take place in Wesnoth, but many do. There is definitely a certain flavor to campaigns that are intended to take place somewhere in the world of Wesnoth. Stake out a time period or a map locale and tell a story.<br /> * [[WesnothHistory|The history of Wesnoth]]<br /> * [[WesnothGeography|The geography of Wesnoth]]<br /> * [[RaceDescriptions|The races of creatures in Wesnoth]]<br /> * [[WesnothPoetry|Wesnothian poetry]]<br /> <br /> == Miscellaneous ==<br /> * [[ExternalUtilities| External Utilities]] - some extra tools for easier creating stuff<br /> * [[ReferenceWML|WML Reference]] - a quicklink<br /> * [[FAQ#Scenario_and_Campaigns|FAQ]] - if you have a question, post it<br /> * Campaign server [http://wolff.to/campaigns/list.html web interface] - An alternate way to download user campaigns<br /> * [[Status_of_User_Scenarios| Status of User Scenarios]] - Lists which usercampaigns are working and which ones are broken<br /> {{Home}}</div>

Placid https://wiki.wesnoth.org/index.php?title=AbilitiesWML&diff=8377 2006-03-22T01:22:49Z

<p>Placid: /* Normal abilities {{DevFeature}} */ tabularise</p> <hr /> <div>{{WML Tags}}<br /> == Abilities and their effects ==<br /> <br /> There are two types of abilities: ones that apply to units (called ''abilities'') and weapon-based (called<br /> ''specials''). A unit may have multiple abilities,<br /> but each attack can only have at most one special.<br /> <br /> == Normal abilities (for BFW 1.0) ==<br /> {| class=&quot;gallery&quot; style=&quot;text-align:left&quot;<br /> |-<br /> ! ambush<br /> | the unit becomes invisible on forest. Invisible units cannot be seen by enemies and do not possess zone of control, although if an enemy moves next to one, it becomes visible again.<br /> |-<br /> ! cures<br /> | unit will heal ''curer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''cure_amount''. If a neighbour is poisoned, it will cure the poison instead of healing.<br /> |-<br /> ! heals<br /> | unit will heal ''healer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''heal_amount''. If a neighbour is poisoned, it will prevent the poison's effect instead of healing.<br /> |-<br /> ! illuminates<br /> | all neighbouring hex will be &quot;illuminated&quot;, in other words have a different time of day (See [[TimeWML]]). Typically, this will be one step brighter.<br /> |-<br /> ! leadership<br /> | the unit will increase the damage of all neighbouring units by +25% per level difference. (If the neighbouring unit is of a higher level, this effect is negated.)<br /> |-<br /> ! nightstalk<br /> | the unit becomes invisible during night.<br /> |-<br /> ! regenerates<br /> | the unit will heal itself 8 hp per turn. If it is poisoned, it will remove the poison instead of healing.<br /> |-<br /> ! skirmisher<br /> | the unit ignores zone of control when moving, but still cannot move directly through an enemy unit<br /> |-<br /> ! steadfast<br /> | the unit takes half normal damage when it did not initiate the attack.<br /> |-<br /> ! teleport<br /> | the unit can move between any two allied villages for one move point<br /> |}<br /> <br /> == Normal abilities {{DevFeature}} ==<br /> {| class=&quot;gallery&quot; style=&quot;text-align:left&quot;<br /> |-<br /> ! submerge<br /> | the unit becomes invisible in deep water.<br /> |}<br /> <br /> == Attack specials ==<br /> {| class=&quot;gallery&quot; style=&quot;text-align:left&quot;<br /> |-<br /> ! backstab<br /> | doubles damage whenever there is a unit on the opposite side (location) of the defending unit that distracts it. In 1.0.x the distracting unit must be on the same side (player) as the attacker. {{DevFeature}}: the distracting unit must be an enemy of the defending unit and not incapacitated (e.g. turned to stone).<br /> |-<br /> ! berserk<br /> | forces the combat to continue until either the attacker or the defender is killed, or until 30 rounds have passed (whichever comes first.)<br /> |-<br /> ! charge<br /> | when attacking, both this weapon and defender get double damage.<br /> |-<br /> ! drain<br /> | The controller of this weapon gains health equal to half the damage done (rounded down) whenever this attack hits.<br /> |-<br /> ! firststrike<br /> | when this weapon is used to defend, the battle proceeds as if it were the attacker (i.e. it attacks first).<br /> |-<br /> ! magical<br /> | this weapon always has a 70% chance of hitting.<br /> |-<br /> ! marksman<br /> | when attacking, this weapon has a minimum of 60% chance of hitting.<br /> |-<br /> ! plague<br /> | The controller of this weapon is copied onto the tile that any unit this attack killed was on.<br /> |-<br /> ! poison<br /> | when this weapon hits, the defender becomes poisoned (see [status], [[SingleUnitWML]]).<br /> |-<br /> ! slow<br /> | when this weapon hits, the defender becomes slowed (see [status], [[SingleUnitWML]]).<br /> |-<br /> ! stone<br /> | when this weapon hits, the defender turns to stone (see [status], [[SingleUnitWML]]).<br /> |}<br /> <br /> == See Also ==<br /> <br /> * [[UnitWML]]<br /> * [[SingleUnitWML]]<br /> * [[ReferenceWML]]</div>

Placid https://wiki.wesnoth.org/index.php?title=AbilitiesWML&diff=8376 2006-03-22T01:22:13Z

<p>Placid: /* Attack specials */ tabularise</p> <hr /> <div>{{WML Tags}}<br /> == Abilities and their effects ==<br /> <br /> There are two types of abilities: ones that apply to units (called ''abilities'') and weapon-based (called<br /> ''specials''). A unit may have multiple abilities,<br /> but each attack can only have at most one special.<br /> <br /> == Normal abilities (for BFW 1.0) ==<br /> {| class=&quot;gallery&quot; style=&quot;text-align:left&quot;<br /> |-<br /> ! ambush<br /> | the unit becomes invisible on forest. Invisible units cannot be seen by enemies and do not possess zone of control, although if an enemy moves next to one, it becomes visible again.<br /> |-<br /> ! cures<br /> | unit will heal ''curer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''cure_amount''. If a neighbour is poisoned, it will cure the poison instead of healing.<br /> |-<br /> ! heals<br /> | unit will heal ''healer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''heal_amount''. If a neighbour is poisoned, it will prevent the poison's effect instead of healing.<br /> |-<br /> ! illuminates<br /> | all neighbouring hex will be &quot;illuminated&quot;, in other words have a different time of day (See [[TimeWML]]). Typically, this will be one step brighter.<br /> |-<br /> ! leadership<br /> | the unit will increase the damage of all neighbouring units by +25% per level difference. (If the neighbouring unit is of a higher level, this effect is negated.)<br /> |-<br /> ! nightstalk<br /> | the unit becomes invisible during night.<br /> |-<br /> ! regenerates<br /> | the unit will heal itself 8 hp per turn. If it is poisoned, it will remove the poison instead of healing.<br /> |-<br /> ! skirmisher<br /> | the unit ignores zone of control when moving, but still cannot move directly through an enemy unit<br /> |-<br /> ! steadfast<br /> | the unit takes half normal damage when it did not initiate the attack.<br /> |-<br /> ! teleport<br /> | the unit can move between any two allied villages for one move point<br /> |}<br /> <br /> == Normal abilities {{DevFeature}} ==<br /> * 'submerge' the unit becomes invisible in deep water.<br /> <br /> == Attack specials ==<br /> {| class=&quot;gallery&quot; style=&quot;text-align:left&quot;<br /> |-<br /> ! backstab<br /> | doubles damage whenever there is a unit on the opposite side (location) of the defending unit that distracts it. In 1.0.x the distracting unit must be on the same side (player) as the attacker. {{DevFeature}}: the distracting unit must be an enemy of the defending unit and not incapacitated (e.g. turned to stone).<br /> |-<br /> ! berserk<br /> | forces the combat to continue until either the attacker or the defender is killed, or until 30 rounds have passed (whichever comes first.)<br /> |-<br /> ! charge<br /> | when attacking, both this weapon and defender get double damage.<br /> |-<br /> ! drain<br /> | The controller of this weapon gains health equal to half the damage done (rounded down) whenever this attack hits.<br /> |-<br /> ! firststrike<br /> | when this weapon is used to defend, the battle proceeds as if it were the attacker (i.e. it attacks first).<br /> |-<br /> ! magical<br /> | this weapon always has a 70% chance of hitting.<br /> |-<br /> ! marksman<br /> | when attacking, this weapon has a minimum of 60% chance of hitting.<br /> |-<br /> ! plague<br /> | The controller of this weapon is copied onto the tile that any unit this attack killed was on.<br /> |-<br /> ! poison<br /> | when this weapon hits, the defender becomes poisoned (see [status], [[SingleUnitWML]]).<br /> |-<br /> ! slow<br /> | when this weapon hits, the defender becomes slowed (see [status], [[SingleUnitWML]]).<br /> |-<br /> ! stone<br /> | when this weapon hits, the defender turns to stone (see [status], [[SingleUnitWML]]).<br /> |}<br /> <br /> == See Also ==<br /> <br /> * [[UnitWML]]<br /> * [[SingleUnitWML]]<br /> * [[ReferenceWML]]</div>

Placid https://wiki.wesnoth.org/index.php?title=AbilitiesWML&diff=8375 2006-03-22T01:19:21Z

<p>Placid: /* Normal abilities (for BFW 1.0) */ tabularise</p> <hr /> <div>{{WML Tags}}<br /> == Abilities and their effects ==<br /> <br /> There are two types of abilities: ones that apply to units (called ''abilities'') and weapon-based (called<br /> ''specials''). A unit may have multiple abilities,<br /> but each attack can only have at most one special.<br /> <br /> == Normal abilities (for BFW 1.0) ==<br /> {| class=&quot;gallery&quot; style=&quot;text-align:left&quot;<br /> |-<br /> ! ambush<br /> | the unit becomes invisible on forest. Invisible units cannot be seen by enemies and do not possess zone of control, although if an enemy moves next to one, it becomes visible again.<br /> |-<br /> ! cures<br /> | unit will heal ''curer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''cure_amount''. If a neighbour is poisoned, it will cure the poison instead of healing.<br /> |-<br /> ! heals<br /> | unit will heal ''healer_heals_per_turn'' (see [[GameConfigWML]]) hp to all neighbours, up to a total of ''heal_amount''. If a neighbour is poisoned, it will prevent the poison's effect instead of healing.<br /> |-<br /> ! illuminates<br /> | all neighbouring hex will be &quot;illuminated&quot;, in other words have a different time of day (See [[TimeWML]]). Typically, this will be one step brighter.<br /> |-<br /> ! leadership<br /> | the unit will increase the damage of all neighbouring units by +25% per level difference. (If the neighbouring unit is of a higher level, this effect is negated.)<br /> |-<br /> ! nightstalk<br /> | the unit becomes invisible during night.<br /> |-<br /> ! regenerates<br /> | the unit will heal itself 8 hp per turn. If it is poisoned, it will remove the poison instead of healing.<br /> |-<br /> ! skirmisher<br /> | the unit ignores zone of control when moving, but still cannot move directly through an enemy unit<br /> |-<br /> ! steadfast<br /> | the unit takes half normal damage when it did not initiate the attack.<br /> |-<br /> ! teleport<br /> | the unit can move between any two allied villages for one move point<br /> |}<br /> <br /> == Normal abilities {{DevFeature}} ==<br /> * 'submerge' the unit becomes invisible in deep water.<br /> <br /> == Attack specials ==<br /> * 'charge' when attacking, both this weapon and defender get double damage.<br /> * 'poison' when this weapon hits, the defender becomes poisoned (see [status], [[SingleUnitWML]]).<br /> * 'slow' when this weapon hits, the defender becomes slowed (see [status], [[SingleUnitWML]]).<br /> * 'stone' when this weapon hits, the defender turns to stone (see [status], [[SingleUnitWML]]).<br /> * 'magical' this weapon always has a 70% chance of hitting.<br /> * 'marksman' when attacking, this weapon has a minimum of 60% chance of hitting.<br /> * 'drain' The controller of this weapon gains health equal to half the damage done (rounded down) whenever this attack hits.<br /> * 'plague' The controller of this weapon is copied onto the tile that any unit this attack killed was on.<br /> * 'backstab' doubles damage whenever there is a unit on the opposite side (location) of the defending unit that distracts it. In 1.0.x the distracting unit must be on the same side (player) as the attacker. {{DevFeature}}: the distracting unit must be an enemy of the defending unit and not incapacitated (e.g. turned to stone).<br /> * 'firststrike' when this weapon is used to defend, the battle proceeds as if it were the attacker (i.e. it attacks first).<br /> * 'berserk' forces the combat to continue until either the attacker or the defender is killed, or until 30 rounds have passed (whichever comes first.)<br /> <br /> == See Also ==<br /> <br /> * [[UnitWML]]<br /> * [[SingleUnitWML]]<br /> * [[ReferenceWML]]</div>

Placid https://wiki.wesnoth.org/index.php?title=FAQ&diff=8370 2006-03-22T00:42:45Z

<p>Placid: /* There's too much luck in this game! */ grammar</p> <hr /> <div>=Frequently Asked Questions=<br /> <br /> == General ==<br /> <br /> ===What is Battle for Wesnoth?===<br /> Battle for Wesnoth is a fantasy turn-based strategy game.<br /> <br /> ===What license is the game distributed under?===<br /> The project is distributed under the [http://www.fsf.org/copyleft/gpl.html GPL]. All contributors retain copyright on the portions of the project that they contribute.<br /> <br /> ===How to get informed about new releases?===<br /> Subscribe to new releases at [http://freshmeat.net/subscribe/38720/?url=%2Fprojects%2Fwesnoth%2F Freshmeat].<br /> <br /> ===A new version is out, but where is the download for [Windows, Mac OS, etc.]?===<br /> The downloads are NOT part of the official project. The BFW team only releases the game's source code. Binary executables or applications are always contributed by community volunteers. If not for these volunteers, there would never be any downloads for us to enjoy. The volunteers compile the game and upload it on their own time, and sometimes they cannot do this in a timely fashion (or at all, at times) Although there are usual packagers designated for each operating system, there are times when other members of the community are asked to step in and contribute when the usual people cannot.<br /> <br /> Every time a new version is released, the usual volunteers are always notified by the project leaders. '''Please refrain from making forum posts asking where your download is''' because it doesn't help anything - the packagers already know, and they will get to it as soon as they can. In the past, the Windows and Mac communities have come together to produce home-grown unofficial builds for the community to use, and the renewed interest in community and learning how to compile is generally a good thing.<br /> <br /> ===Why doesn't Wesnoth have my favorite feature?===<br /> Because we are building this game for ourselves, to suit our own preferences. We're not building the game for you, in large part because this is our hobby, not our job; whether you like it or not is immaterial to us.<br /> You may wonder, then, what the point is of soliciting ideas, as we do on the forum. We, the developers, have certainly come up with many good ideas on our own, but our players often do as well, and generally ones we don't think of ourselves. If a player comes up with an idea we like, we might implement it. Not because they asked for it, but because of its own merits as an addition to our game.<br /> <br /> The beautiful thing about the license our game is distributed under, as compared to closed-source, commercial games, is that if you want that feature badly enough, you can take the code and art of our game and modify it yourself; you are free to re-use any work in Wesnoth, as long as you follow the rules of the [http://www.fsf.org/copyleft/gpl.html GPL]. From this, you can build a game exactly the way that you like. Just don't expect us to build that game for you. Building this game is our hobby, not our profession, and you did not pay us to make it; rather, we are the ones who have paid for it, in time and labor.<br /> <br /> ===Do you want help making this game? How can I help?===<br /> Yes, we want your help. Whether you're a programmer, artist, musician, writer, translator, level designer, playtester, or just have some great suggestions, you're welcome to contribute. How? You can:<br /> * join the [http://www.wesnoth.org/wiki/Project Project]<br /> * share your point of view at the [http://www.wesnoth.org/forum/ Forum]<br /> * talk with us on [irc://irc.wesnoth.org/wesnoth IRC]<br /> * report bugs you find at [[ReportingBugs]]<br /> * update the wiki<br /> * play against us via the Multiplayer menu<br /> * vote for Wesnoth at your favorite gaming web site<br /> * Spread the word!<br /> <br /> === What are the system requirements? ===<br /> <br /> We are not completely certain, but an x86 running at 600MHz with 128MB RAM should be adequate. Slower machines will have trouble scrolling large maps or processing AI turns with many units. See the [http://www.wesnoth.org/forum/viewtopic.php?t=7384 forum thread] about minimum and recommended system requirements.<br /> <br /> === I'm bored; how do I speed the game up? ===<br /> <br /> There are several preferences you can change to shorten the time that the AI takes to make its moves. &quot;Accelerated Speed&quot; will make units move and fight faster. &quot;Skip AI Moves&quot; will not show the AI's units moving from hex to hex. Finally, you can turn off all combat animations via the &quot;Show Combat&quot; option on the Advanced tab.<br /> <br /> === My computer is too slow; how do I speed the game up? ===<br /> <br /> First, turn off the music and sound effects. Turning off the color cursors will make your cursor respond faster. If scrolling the map is slow, run the game in &quot;Full Screen&quot; mode, not in a window. Turn off combat animations via the &quot;Show Combat&quot; option on the Advanced tab. You can try turning off halos and combat results, but this might make gameplay more difficult.<br /> <br /> == Gameplay and Controls ==<br /> <br /> === How do I learn to play? ===<br /> <br /> If you just want to jump right in, start the game and play the tutorial. If you like reading documentation, see [[WesnothManual]], which is also distributed as a PDF file. At any time while playing, you can select help from the menu button (or hit F1). The online help is quite extensive and provides information on terrains, weapons, traits, abilities, units and a good overview of how to play.<br /> <br /> === My unit leveled up but didn't improve. What happened? ===<br /> <br /> This is called &quot;After Maximum Level Advancement&quot; or AMLA for short. While most level 0, 1, and 2 units can advance, some cannot. However, some level 3 units can advance to level 4, or even 5. You can see whether a unit can advance further by right clicking and selecting &quot;description.&quot;<br /> <br /> After a unit reaches the highest level it can get, every time it gains 100 experience it gains 3 hitpoints. It does not heal when this happens. This is a minor bonus so that experience gained by maxed out units is not altogether wasted. It is generally better to give experience to lower level units, rather than continue to advanced units that have reached their maximum level.<br /> <br /> If the unit in question is the Necrophage, this is not a bug. The Necrophage eats the corpses of the dead, allowing it to periodically completely heal. Leveling into itself is how this is carried out.<br /> <br /> === I tried to trap an enemy with several weak units, but it still escaped. What happened? ===<br /> <br /> Most units exert a zone of control (or ZOC). IF an enemy moves into one of the six adjacent hexes, the zone of control will prevent it from moving any farther. However some weak units are level 0, meaning they are so weak that they do not have a ZOC. You can still surround an enemy unit entirely with level 0 units to keep it from escaping, but if there is any gap in your ranks, it could escape.<br /> <br /> Also, some units have the &quot;skirmish&quot; ability, which allows them to ignore ZOCs.<br /> <br /> === How can I see where an enemy unit can move next turn? ===<br /> <br /> During you turn you can click on an enemy unit. Wesnoth will highlight all the hexes the unit can move to in the next turn. This is useful when trying to arrange your units to block an enemy's movement.<br /> <br /> === There's too much luck in this game! ===<br /> <br /> Sooner or later, you will become frustrated when your archmage with four 70% attacks misses all four times. This does not mean that the AI is cheating or the random number generator is futzed. It means you are noticing random negative events more than positive ones. During the development of the game, many mathematicians have done sophisticated statistical analysis of the combat system. Likewise, programmers have examined the random number generator. Wesnoth has been deliberately designed so that the streaks of &quot;bad&quot; and &quot;good&quot; luck are a part of the gameplay.<br /> <br /> Since Wesnoth is GPLed, it is possible that, after the 1.0 release, a new development team will &quot;fork&quot; the source and produce a version more like Heroes of Might &amp; Magic, with no randomness. Until then, don't charge with your horsemen against rock trolls at night...<br /> <br /> === The (random unit) is overpowered/underpowered! ===<br /> <br /> The development team has spent years tweaking the units in the game. Each unit has had its gold cost, attack types, combat damage, defensive values, resistances, upgrade paths, and other stats carefully scrutinized and loudly discussed in the forum. However, the game code and the units were being modified right up until the 1.0 release, so some unbalanced units may have slipped through.<br /> <br /> If you have evidence to back up your claim, search the forum for past discussions about this unit, and then try posting.<br /> <br /> === The (random scenario) is too hard/easy! ===<br /> <br /> See above answer about random units.<br /> <br /> === What do the different difficulty levels do? ===<br /> <br /> That depends on the scenario. Usually, the opponent will get more money and be able to recruit higher-level units at higher difficulty levels, and you will have fewer turns available.<br /> <br /> == Maps, Scenarios and Campaigns ==<br /> <br /> === How do I beat scenario _______ ? ===<br /> <br /> If you are stuck on a scenario in a campaign, you'll probably find a walkthrough at [[MainlineScenarios]]. Or check out the &quot;Strategies and Tips&quot; forum at http://www.wesnoth.org/forum/viewforum.php?f=3<br /> <br /> === Are there any tools to help me create maps and scenarios? ===<br /> Yes, there is a tool called wesnoth_editor. It is a normal map-editor that should be a good help for creating the plain maps. For creating the scenarios there already is a scenario-editor included in the mac build. But this editor is rather outdated and it exists only for MacOS X. At the moment some community members are working on creating a nice and working scenario editor. You can have a look at the [http://www.wesnoth.org/forum/viewtopic.php?t=6925 forum post] about this tool. You will also find more info at [[CampGen]].<br /> <br /> === How do I download user campaigns? ===<br /> Choose &quot;Campaigns&quot; in the main Wesnoth menu. Then scroll down to the bottom and choose &quot;Get More Campaigns...&quot;. This connects you to the campaign server. In the campaign server you can view a list of all available campaigns and download them, as well as posting or deleting your own campaigns. If you are behind a firewall you may not be able to connect the the campaign server; in this case try contacting the author of the campaign via the forums to see if there is another way you can get the campaign.<br /> <br /> === I already created a campaign and published it on the campaign server. How can I get translations for the campaign? ===<br /> Just have a look at [[WesCamp]]. This project is the easiest way to get translations for your campaign. All the info you need you can find at [[WesCamp]].<br /> <br /> ===How do I place an object or unit on my map with the map editor?===<br /> You can't. You need to make a multiplayer scenario file. There are more details on the [[BuildingMaps|maps]] page.<br /> <br /> == Multiplayer ==<br /> <br /> ===How to find players for multiplayer game?===<br /> Hang around for a while on multiplayer servers and you might find someone to play with. If you observe other people playing you will get informed when someone joins the servers. Maybe you find someone willing to play in the irc channel dedicated to mp: #wesnoth-mp at irc.freenode.net.<br /> You can also join #wesnoth at irc.freenode.net.<br /> <br /> ===How can I make my computer into a dedicated Wesnoth server?===<br /> <br /> ===Which versions of Wesnoth can play together?===<br /> <br /> == Translations ==<br /> <br /> ===I selected an asian translation and am not able to see the letters correctly. What happened?===<br /> <br /> Since the size of the necessary fonts is too large, you'll need to download them separately (if you don't already have them). After that, simply copy the font to the '''fonts/''' directory in your wesnoth installation.<br /> * Chinese font: [ftp://cle.linux.org.tw/pub/fonts/ttf/unicode/Arphic/gkai00mp.ttf gkai00mp.ttf]<br /> * Japanese font: [http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/sqs-xml/sqs-font/sazanami-gothic.ttf sazanami-gothic.ttf]<br /> <br /> If you have futher questions have a look at [[WesnothAsianLanguages|this]] page.<br /> <br /> == Other Questions You Have ==<br /> <br /> The best way to get answers to less-frequently asked questions is by visiting the [http://www.wesnoth.org/forum BFW forum]. There are plenty of people willing to help. Make sure you read ALL of the forum sticky notes and announcements before posting.</div>

Placid https://wiki.wesnoth.org/index.php?title=User:Placid&diff=8369 2006-03-22T00:34:30Z

<p>Placid: </p> <hr /> <div>Fairly newbie player but have a programming and design background. For now I'm pottering around the Wiki tidying things up and learning as I go. I'll add some relevant examples where they are lacking.</div>

Placid https://wiki.wesnoth.org/index.php?title=TimeWML&diff=8366 2006-03-22T00:32:23Z

<p>Placid: /* The [time] and [illuminated_time] tags */</p> <hr /> <div>{{WML Tags}}<br /> == The [time] and [illuminated_time] tags ==<br /> <br /> The [time] tag is a subtag of the [scenario] tag. However, most scenarios do not use these directly, but usually use the ready macros ''{DAWN}, {MORNING}, {AFTERNOON}, {DUSK}, {FIRST_WATCH}, {SECOND_WATCH}'' and ''{UNDERGROUND}'' to specify the day-night cycle.<br /> See '''data/schedules.cfg''' for the definitions of these IDs.<br /> <br /> The [time] tag describes a single turn of a day/night sequence. When a scenario is played, the first turn is described by the first [time] tag; the second described by the second, until there are no more. After all the tags have described a turn, the next turn is described by the first tag again.<br /> <br /> The [illuminated_time] tag is like the [time] tag, but it describes spaces that have been illuminated (see ''illuminates'', [[AbilitiesWML]]). {{DevFeature}}: this tag is no longer used, since the new illuminates ability automatically determines illuminated time<br /> <br /> The [time] tag recognizes the following keys:<br /> <br /> * ''name'' (translatable) the name displayed when the cursor is over the day/night image.<br /> * ''image'' the image displayed at the top of the Status Table during turns of this type.<br /> * ''mask'' the image displayed over all hexes during turns of this type.<br /> * ''lawful_bonus'' units with '''alignment=lawful''' do +//lawful_bonus'' % damage during turns of this type.<br /> Units with '''alignment=chaotic''' do -''lawful_bonus'' % damage. Units with '''alignment=neutral''' are unaffected by this key. ''lawful_bonus'' can be a negative number. This is useful if you want to give Chaotic units an advantage instead of Lawful ones.<br /> * ''red//, ''green//, ''blue'' describe the tint of the screen during the time period. Appears to be an integer value from -255 to 255. See schedules.cfg<br /> for examples.<br /> <br /> == See Also ==<br /> <br /> * [[ScenarioWML]]<br /> * [[ReferenceWML]]<br /> <br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=TerrainWML&diff=8365 2006-03-22T00:32:01Z

<p>Placid: /* the toplevel [terrain] tag */</p> <hr /> <div>{{WML Tags}}<br /> == the toplevel [terrain] tag ==<br /> <br /> the [terrain] tag describes a terrain in WML.<br /> Terrains are usually described in the terrain.cfg file<br /> <br /> the [terrain] tag has the following keys and subtags<br /> * ''image'' an image used for this terrain in the map editor<br /> * ''symbol_image'' appears to work the same as ''image'' - clarification is needed<br /> * ''adjacent_image'' a prefix for adjacent terrain images. they will be postfixed with the orientation of the border to give the image name that will be used for the border terrain<br /> * ''name'' the name of the terrain<br /> * ''char'' the character used to represent this terrain in maps and scenarios<br /> * ''aliasof'' characters representing terrains that this terrain will be an alias of. {{DevFeature}}this is a list of characters, with the + and - signs having special meanings. the string is read left to right taking the best value. when a minus sign is encountered, it starts taking the worst instead. the plus sign reverts it back to the best<br /> * ''def_alias'' {{DevFeature}}like ''aliasof'' but overides it for defense calculation only<br /> * ''mvt_alias'' {{DevFeature}}like ''aliasof'' but overides it for movement calculation only<br /> * ''unit_height_adjust'' how much the unit graphic should be moved up or down when on that terrain<br /> * ''submerge'' float, between 0 and 1: stems how much of the unit graphic should be submerged by the terrain<br /> * ''no_overlay'' whether this terrain should be overwritten by other terrain's borders; 'no_overlay=true' terrains are not overwritten.<br /> * ''light'' {{DevFeature}}signed value. this will modified local light level on that hex by that amount for gameplay<br /> * ''heals'' if set to true a unit on that terrain will be healed at the start of every turn<br /> * ''gives_income'' if set to true, this terrain will give income every turn when flagged as if it were a village<br /> * ''recruit_onto'' if set to true, it is possible to recruit or recall on that terrain<br /> * ''recruit_from'' if set to true it is possible to recruit when a unit that can recruit is on that terrain<br /> <br /> == See Also ==<br /> <br /> * [[ReferenceWML]]<br /> * [[TerrainLettersWML]]<br /> <br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=TerrainCodesWML&diff=8364 2006-03-22T00:31:41Z

<p>Placid: /* Values of terrain letters */</p> <hr /> <div>{{WML Tags}}<br /> == Values of terrain letters ==<br /> <br /> What each letter represents in Wesnoth maps,<br /> and the possible values of the ''letter'' key.<br /> <br /> Any letters can be used for a terrain except for newline.<br /> See [[TerrainWML]] for information on how to define a terrain.<br /> <br /> These are terrains defined in data/terrain.cfg of 1.0<br /> (or later versions as noted):<br /> <br /> * '''A''' human (snow) hill village<br /> * '''a''' human hill village<br /> * '''B''' desert village (adobe)<br /> * '''b''' human mountain village<br /> * '''C''' castle<br /> * '''c''' shallow water, &quot;coast&quot;<br /> * '''D''' underground village (cave, village), &quot;dungeon village&quot;<br /> * '''d''' sand, (old desert)<br /> * '''E''' desert road<br /> * '''e''' elven (snow) village<br /> * '''F''' forest (snow)<br /> * '''f''' forest<br /> * '''G''' savanna (grass)<br /> * '''g''' grass<br /> * '''H''' hills (snow)<br /> * '''h''' hills<br /> * '''I''' desert<br /> * '''i''' ice (tundra)<br /> * '''J''' desert hills<br /> * '''j''' -nothing- (will be snowy mountains)<br /> * '''K''' keep (castle)<br /> * '''k''' river ford (grass, shallow water)<br /> * '''L''' tropical forest village (savanna, village)<br /> * '''l''' lava (canyon)<br /> * '''M''' desert mountains<br /> * '''m''' mountain<br /> * '''N''' ruined castle<br /> * '''n''' encampment (castle)<br /> * '''O''' -nothing- ( will probably be an Orc Castle one day )<br /> * '''o''' dwarven castle (castle)<br /> * '''P''' desert oasis<br /> * '''p''' dwarven village {{DevFeature}}<br /> * '''Q''' sunken ruin<br /> * '''q''' ruin (swamp)<br /> * '''R''' road (grass)<br /> * '''r''' dirt (grass)<br /> * '''S''' tundra<br /> * '''s''' deep water<br /> * '''T''' forest (tropical)<br /> * '''t''' village<br /> * '''U''' desert village (tent)<br /> * '''u''' cave<br /> * '''V''' snow village (tundra, village)<br /> * '''v''' human village (village)<br /> * '''W''' cavewall<br /> * '''w''' swamp<br /> * '''X''' canyon (replaced by chasm in trunk)<br /> * '''x''' reserved for UMCs<br /> * '''Y''' swamp village (swamp, village)<br /> * '''y''' reserved for UMCs<br /> * '''Z''' mermen village (shallow water)<br /> * '''z''' reserved for UMCs<br /> * '''/''','''|''','''\''' bridge (grass, shallow water)<br /> * '''~''' fog<br /> * ' ' void/shroud (it uses the &quot;space&quot; character)<br /> * '''*''' reserved for UMCs<br /> * '''^''' reserved for UMCs<br /> * '''%''' reserved for UMCs<br /> * '''@''' reserved for UMCs<br /> * '''[''' rockbound cave {{DevFeature}}<br /> * ''']''' mushroom grove {{DevFeature}}<br /> * ''' ' ''' illuminated cave {{DevFeature}}<br /> * ''' ? ''' great Elven tree {{DevFeature}}<br /> * ''' &amp; ''' impassable moutains (reserved)<br /> * ''' &quot; ''' ???<br /> * ''' $ ''' ???<br /> * ''' . ''' ???<br /> * ''' ; ''' ???<br /> * ''' : ''' ???<br /> * ''' &lt; ''' ???<br /> * ''' &gt; ''' ???<br /> * ''' _ ''' ???<br /> * ''' ` ''' ???<br /> <br /> ==Reserved letters and non-letter Characters==<br /> Reserved letters are for custom terrains in user-made campaigns. In addition to these it is currently also possible to use other characters not on the above list to represent custom terrain, such as ½ § @ % [ ] etc., but new &quot;official&quot; terrain may be assigned for these characters in the future. So when creating custom terrain, the letters marked as reserved on the above list should be used first.<br /> Use campaign definitions (see [[CampaignWML]])<br /> to prevent your custom terrains from interfering with other campaigns.<br /> <br /> Note: <br /> * UtBS uses: @ ^ &amp; *<br /> * FtF uses: @ ^ % '<br /> * Wesvoid uses: % *<br /> * Seed of Evil: ^<br /> * no other UMCs above version 0.3 uses non-letter character for custom terrains.<br /> <br /> == See Also ==<br /> * [[TerrainWML]]<br /> * [[ReferenceWML]]<br /> * [http://www.idi.ntnu.no/~haskjold/wesnoth/map_letters.html Freim's List of Terrain Letters] <br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=SyntaxWML&diff=8363 2006-03-22T00:31:14Z

<p>Placid: </p> <hr /> <div>{{WML Tags}}<br /> Wesnoth syntax has two basic elements: ''tags'' and ''attributes''.<br /> Further, ''attributes'' consist of ''keys'' and ''values''.<br /> Tag names and keys cannot contain whitespace.<br /> Any line beginning with a pound ('''#''') sign is considered by<br /> WML as a comment, except for preprocessor declarations beginning<br /> with #.<br /> * '''[tag-name] ''data'' [/tag-name]''' is a tag. Tags are used to partition information. A ''top level'' tag is one that is not inside any other tag. Each top level tag describes something about the game. Different tags work differently. For information about how a certain tag works, see [[ReferenceWML]].<br /> * '''[+tag-name] ''data'' [/tag-name]''' means that ''data'' will be considered as part of the data for the most recent [''tag-name''] tag. The ''data'' of '''[+tag-name]''' will be considered as coming after all data in '''[tag-name]''', so attributes of '''[+tag-name]''' will replace attributes of the original '''[tag-name]'''.<br /> * '''''key=value newline''''' is an ''attribute'', or an assignment of a value to a key. When this line is processed, the value of ''key'' for the tag that the attribute is in is set or changed to ''value''. All text from '=' until the end of the line is considered to be part of ''value''. Note that ''key'' is not a WML variable (with the exception of [[VariablesWML]]); the value it is set to has a use which is determined by C++ code, not WML code. In order to change the value of a WML variable, you need to use '''[set_variable]''' (see [[InternalActionsWML]]). '''There should be no space between the key and the '=' symbol!''' If there is whitespace, the attribute assignment is ignored. Note that ''key'' should contain only alphanumerics or underscores (''a-zA-Z0-9_''); no ''+'' or ''-'' characters are allowed.<br /> * '''''key1,key2,key3=value1,value2,value3 newline''''' is a multiple assignment. If there are extra keys, they will be set to an empty value. If there are extra values the last key will be set to the comma separated list of all remaining values. It is the same as<br /> key1=value1<br /> key2=value2<br /> key3=value3<br /> <br /> Although a value can be just text corresponding to a function of<br /> its key (these values are displayed in quotes (') in<br /> [[ReferenceWML]]), a value can also be encoded:<br /> * '''&quot;''multiple-line-value''&quot;''' a multiple-line value must be enclosed in quotes, to prevent it being interpreted as a single-line value. Note that ''multiple-line-value'' doesn't have to have multiple lines; it can simply be a single-line value enclosed in quotes for clarity.<br /> * '''''_ &quot;text&quot;''''' is a ''translatable'' value. ''text'' is English (US) text that will be displayed in-game at some point. Gettext (see [[GetText]]) is used to determine what to display if English (US) is not the current language.<br /> * '''''value-1 + value-2''''' can be used to concatenate two different strings. If you want to have a value that actually has a plus sign ('''+''') in it, you need to enclose the string containing the '''+''' character in quotes (see '''''&quot;multiple-line-value&quot;''''' above).<br /> * '''''$variable-name''''' a ''variable'' value depends on the value of the WML variable ''variable-name''. See [[VariablesWML]] for more information on WML-variable based values.<br /> <br /> Example:<br /> [scenario]<br /> id=Elves Besieged<br /> [side]<br /> side,gold=1,100<br /> [/side]<br /> [+side]<br /> recruit=Elvish Fighter,Elvish Archer<br /> [/side]<br /> [/scenario]<br /> In this example, [scenario] is a top level tag. When these<br /> lines are read, WML will know that there is a scenario with<br /> the ID &quot;Elves Besieged&quot;. Later, when WML is told to play<br /> that scenario, it will read the [side] tag and give 100 gold<br /> to side 1. Then it will read the [+side] tag.<br /> It interprets this tag as belonging to side 1, since the<br /> most recent [side] belonged to side 1. So the [+side] tag<br /> allows side 1 to recruit Elvish Fighters and Elvish Archers.<br /> (Then it will crash, as the leader of side 1 has no unit type.<br /> But this isn't really important.)<br /> <br /> Notes: Normally the order and indentation of attributes and tags<br /> does not matter, as long as the levels within tags are not changed.<br /> So the above example could have been written:<br /> [scenario]<br /> [side]<br /> gold=100<br /> side=1<br /> [/side]<br /> id=Elves Besieged<br /> [/scenario]<br /> Data inside tags should be separated with tabbing; see [[ConventionsWML]].<br /> <br /> <br /> == See Also ==<br /> <br /> * [[PreprocessorRef]]<br /> * [[ReferenceWML]]<br /> <br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=ReplayWML&diff=8362 2006-03-22T00:30:17Z

<p>Placid: /* The [command] tag */</p> <hr /> <div>{{WML Tags}}<br /> == The [command] tag ==<br /> <br /> The '''[command]''' tag is used to specify an action in a replay.<br /> <br /> The following tags are recognized:<br /> * '''[start]''' is used to initialize the replay so that generated random numbers can be saved.<br /> * '''[move]''' the player moved a unit.<br /> ** '''[source]''' the location the unit moved to.<br /> ** '''[destination]''' the location the unit moved from.<br /> * '''[recruit]''' the player recruited a unit.<br /> ** ''value'' the index number of the recruited unit. (Index numbers start at 0 and include all recruitable units in alphabetical order.)<br /> ** ''x'' and ''y'' the castle tile the unit is recruited on.<br /> * '''[recall]''' the player recalled a unit. Same keys as [recruit], except that the index is in order of level, followed by required XP to advance.<br /> * '''[attack]''' the player attacked.<br /> ** ''weapon'' the index number of the weapon. Weapons are indexed by the unit designer.<br /> ** '''[source]''' the location of the attacking unit.<br /> ** '''[destination]''' the location of the defending unit.<br /> * '''[end_turn]''' the player ended his turn.<br /> * '''[choose]''' the player was given an option by the scenario.<br /> ** ''value'' the index number of the option chosen. Index numbers are given by the scenario designer.<br /> * '''[random]''' if the action required a random number, this describes the random number that was generated. In 1.0.x, nested '''[random]''' tags are used and only one is allowed at this level. In 1.1.x, a '''[random]''' tag is used at this level for each value.<br /> ** ''value'' list of generated random values. In 1.1.x only a single value can be used.<br /> ** '''[results]''' used for '''[attack]''' commands. Describes the results of the battle.<br /> *** ''chance'' the percent chance that the attack had to hit.<br /> *** ''damage'' the amount of damage that the attack would do if it hits.<br /> *** ''dies'' whether the defender dies from the hit.<br /> *** ''hits'' whether the attack hits.<br /> ** '''[random]''' additional lists of generated random values. '''[random]''' has the same format as the first '''[random]''' and describes the other numbers that were generated. In 1.1.x, '''[random]''' tags at this level are not used.<br /> <br /> == See Also ==<br /> * [[SavefileWML]]<br /> * [[ReferenceWML]]<br /> <br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=ReferenceWMLSyntax&diff=8361 2006-03-22T00:30:04Z

<p>Placid: /* Wiki Syntax */</p> <hr /> <div>{{WML Tags}}<br /> == Wiki Syntax ==<br /> <br /> ==== Formatting ====<br /> <br /> This page is an example of how these wikis should be formatted:<br /> <br /> Description of the page<br /> <br /> * '''[tag]''' description of [tag]<br /> ** ''key'' description of ''key''.<br /> &quot;''key''&quot; can refer either to the key ''key'' or the value of ''key''<br /> * ''key2'' description of ''key2''<br /> ** 'value' what happens when the attribute '''key2=value''' is set<br /> <br /> Example:<br /> [tag]<br /> key=0<br /> [/tag]<br /> key2=value<br /> <br /> ==== Version Control ====<br /> <br /> For WML features not present in the 1.0 branch, please precede the reference text with the template &lt;nowiki&gt;{{DevFeature}}&lt;/nowiki&gt;. Doing this will use the standardized &quot;development version only WML&quot; flag.<br /> <br /> Please do not delete WML reference text that is valid for version 1.0 if a new feature obsoletes, deprecates, or replaces it. Just put the new reference text beneath it and mark it with &lt;nowiki&gt;{{DevFeature}}&lt;/nowiki&gt;.<br /> <br /> The &lt;nowiki&gt;{{DevFeature}}&lt;/nowiki&gt; code turns into this: {{DevFeature}} (dynamically updated from the template page [[Template:DevFeature]])<br /> <br /> Example of what you type when editing:<br /> &lt;nowiki&gt;'''[tag]''' - specifies something or other &lt;/nowiki&gt;<br /> &lt;nowiki&gt;* ''original_key'' the item you want to specify &lt;/nowiki&gt;<br /> &lt;nowiki&gt;* ''better_key'' {{DevFeature}} a list of possible values, one of which is chosen at random &lt;/nowiki&gt;<br /> <br /> ==== Categorization ====<br /> <br /> WML reference pages should be placed into the category &quot;WML reference.&quot; This allows someone to easily bring up all the WML-related pages at once.<br /> <br /> To do this, add the text &lt;nowiki&gt;[[Category: WML Reference]]&lt;/nowiki&gt; at the bottom of the page under the &quot;See Also&quot; section.<br /> <br /> == See Also ==<br /> <br /> * [[ReferenceWML]]<br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=PreprocessorRef&diff=8360 2006-03-22T00:29:42Z

<p>Placid: /* The WML preprocessor */</p> <hr /> <div>{{WML Tags}}<br /> == The WML preprocessor ==<br /> <br /> Wesnoth loads just one configuration file directly: '''data/game.cfg'''.<br /> However the WML preprocessor allows game.cfg to load in more files.<br /> Whenever a WML file is read by Wesnoth, it is passed through the preprocessor.<br /> <br /> The preprocessor is applied recursively, so included files will<br /> be parsed for macros, and after macro expansion will be parsed for macros<br /> again, and so on. As a result, you should not write a recursive macro,<br /> because it will cause an infinite loop.<br /> [http://www.wesnoth.org/forum/viewtopic.php?t=5838 Changes to the preprocessor in 0.9.2]<br /> allow recursively nested #ifdefs, but recursively nested<br /> macro definitions ('#define') will still cause errors<br /> (but not necessarily error messages).<br /> <br /> The following directives are used to create and use ''macros'',<br /> i.e. shortcuts which reduce repetition of information.<br /> See [[UtilWML]], [[UsefulWMLFragments]] for examples.<br /> * '''#define ''symbol'' [''parameters''] ''newline'' ''substitution'' #enddef''' all subsequent occurences of '''{''symbol'' [''arguments'']}''' (see below) will be replaced by ''substitution'' with all occurences of any parameter {''parameter''} within ''substitution'' replaced by the parameter's corresponding value in ''arguments''. For example, the UNIT macro used below would be defined:<br /> <br /> #define UNIT TYPE X Y## the ordering is important here;<br /> ## since WML does not distinguish<br /> ## data into different types, only<br /> ## the ordering is used to determine which<br /> ## arguments apply to which parameters.<br /> [unit]<br /> type={TYPE}## the unit will be of type TYPE, so different<br /> ## instantiations<br /> ## of this macro can create different units.<br /> x={X}<br /> y={Y}<br /> side=2## the unit will be an enemy, regardless of the parameter<br /> ## values. This reduces &quot;repetition of information&quot;,<br /> ## since it is no longer necessary to specify<br /> ## each created unit as an enemy.<br /> [/unit]<br /> #enddef<br /> (See [[SingleUnitWML]] for information on creating units using WML.)<br /> * '''{''symbol'' [''arguments'']}''' if ''symbol'' is defined, the preprocessor will replace this instruction by the expression ''symbol'' is defined as, using ''arguments'' as parameters. You can create multiple word arguments by using parentheses to restrain the argument. For example, while '''{UNIT Wolf Rider 18 24}''' will attempt to create a &quot;Wolf&quot; at (Rider,18), causing Wesnoth to crash, the macro '''{UNIT (Wolf Rider) 18 24}''' will create a &quot;Wolf Rider&quot; at (18,24) as it should. ('''UNIT''' is defined above). See the ''#define'' preprocessor instruction above for information on defining symbols, including symbols with arguments. Several symbols are defined in the normal game code; for reference they are listed in [[UtilWML]].<br /> <br /> Unlike the other preprocessor directives, #ifdef is not<br /> used for convenience.<br /> It is necessary to distinguish between different modes of play.<br /> * '''#ifdef ''symbol'' ''substitution-if-stored'' [#else ''substitution-if-not-stored''] #endif''' If ''symbol'' has been stored, the whole block will be replaced by ''substitution-if-stored''. If not, it will be replaced by ''substitution-if-not-stored'' if it is available. ''symbol'' can take the following values:<br /> ** a campaign difficulty level. Usually '''EASY''', '''NORMAL''', or '''HARD''', it is decided by the key ''difficulties'' (see [[CampaignWML]]).<br /> ** a campaign ID. Each campaign stores a preprocessor ID. See ''define'', [[CampaignWML]].<br /> ** '''MULTIPLAYER''' is stored when the player is playing or setting up a multiplayer game (i.e. a game with '''scenario_type=multiplayer''').<br /> ** '''TUTORIAL''' is stored when the player is playing the tutorial.<br /> ** '''APPLE''' is stored if the computer Wesnoth is being run on is an Apple.<br /> ''#undef'' can be useful too if ''#ifdef'' is not enough.<br /> * '''#undef ''symbol'' ''' erases ''symbol'' (v1.1.1+svn)<br /> <br /> These directives expand a file by including other files:<br /> * '''{''filename''}''' if ''filename'' isn't a predefined symbol (see above), Wesnoth will assume it's a path to a file in the main '''data/''' subdirectory of Wesnoth and include the file it points to here &quot;as is&quot;. Forward slashes('''/''') should be used to separate directories from their elements, even if your platform uses a different symbol such as colon (''':''') or backslash ('''\'''). If ''filename'' points to a directory, the preprocessor will include all files in the directory ''filename'', non-recursively and in alphabetical order.<br /> * '''{~''filename''}''' similar to above, but the preprocessor assumes that the filename is relative to the user data directory. The ''user data directory'' varies depending on platform:<br /> <br /> Platform | User Data Directory<br /> -------------------------<br /> UNIX | ~/.wesnoth/data/<br /> Mac OS X | ~/Library/Preferences/Wesnoth or ~/.wesnoth/data<br /> Windows | &quot;main Wesnoth folder&quot;\userdata<br /> <br /> * '''{@''filename''}''' is a convenient way to make Wesnoth look for a file by that name in both the main and the user data directory. It is equivalent to writing '''{''filename''}{~''filename''}'''.<br /> * '''{./''filename''}''' is similar to the '''{''filename''}''' directive, but is assumed to be relative to the directory which contains the file in which this appears. For example, if used in game.cfg, it is equivalent to '''{''filename''}'''.<br /> <br /> Note that the parser was changed various times, so don't expect older Wesnoth version to behave exactly the same.<br /> <br /> == See Also ==<br /> * [[SyntaxWML]]<br /> * [[ReferenceWML]]<br /> <br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=PblWML&diff=8359 2006-03-22T00:29:18Z

<p>Placid: /* .pbl files */</p> <hr /> <div>{{WML Tags}}<br /> == .pbl files ==<br /> <br /> To upload a campaign you have made, you need a .pbl file.<br /> This is a file with name '''data/campaigns/''campaign-name''.pbl'''.<br /> When you upload a campaign, the file '''data/campaigns/''campaign-name''.cfg'''<br /> and the directory '''data/campaigns/''campaign-name''/''' will be published.<br /> Your campaign must be based entirely on these files.<br /> This may cause your campaign not to upload properly,<br /> for example, if you have custom campaign units in '''data/units/'''.<br /> <br /> The following keys are recognized for .pbl files:<br /> * ''icon'' an image, displayed leftmost on the &quot;download campaigns&quot; screen. It must be a standard Wesnoth graphic and not a custom one. (Note that the icon used to display your campaign for when it is played can be custom; for more information see [[CampaignWML]].)<br /> * ''title'' displayed to the right of the icon, it is just text. It should usually be the same as the name of your campaign when it is played.<br /> * ''version'' displayed to the right of the title, it is also just text. However the prefered format is x.y.z where x, y and z are numbers and x &gt; 0 implies the campaign is complete and balanced.<br /> * ''author'' displayed to the right of the version, it is also text. Put your name or nickname here. If several people have contributed significantly to the campaign you should list all of their names and perhaps describe what each person was responsible for.<br /> * ''passphrase'' not displayed, it prevents others from modifying the version of your campaign on the campaign server. You do not need to input a passphrase when initially publishind a campaign; if you do not, one will be randomly generated for you.<br /> * ''description'' is not displayed in the client. However it is visible on the web interface to the campaign server. It can be used to give a brief description of your campaign and for pre 1.0 versions let people know how playable it is.<br /> <br /> Example:<br /> <br /> title=&quot;My Campaign&quot;<br /> icon=&quot;misc/ball.png&quot;<br /> version=&quot;0.1.2&quot;<br /> author=&quot;Me, artwork by myself&quot;<br /> passphrase=&quot;This is like a password&quot;<br /> description=&quot;You get to kill a lot of bad guys. But only the first map is done.&quot;<br /> <br /> The campaign server keeps track of some other information about uploaded campaigns, including when they were uploaded, what languages they have been at least partly translated into, how large they are on the server and the number of times they have been downloaded. For more information about this you can read [[CampaignServerWML]].<br /> <br /> == See Also ==<br /> <br /> * [[ReferenceWML]]<br /> * [[BuildingCampaignsThePBLFile]]<br /> * [[CampaignServerWML]]<br /> <br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=MusicListWML&diff=8358 2006-03-22T00:28:56Z

<p>Placid: /* the [music] tag */</p> <hr /> <div>{{WML Tags}}<br /> == the [music] tag ==<br /> {{DevFeature}}<br /> <br /> This tag is a subtag of [scenario] and [event] which is used to describe a music track to play. You can repeat this tag as many times as you like; if you set the ''append'' tag to ''yes'' they will form a playlist from which tracks will be selected at random.<br /> <br /> Tags describe the music track:<br /> * ''name'' specifies the music file, relative to '&quot;music/&quot;'. This is compulsory.<br /> * ''append=yes'' specifies this is to be added to the current playlist. Without this, the current playlist is replaced by this track.<br /> * ''play_once=yes'' immediately switch to playing this track, but then return to the play list, which is unchanged.<br /> * ''immediate=yes'' immediately switch to playing this track. Without this, the song will play when the entire [event] is over or the current song ends. This exists to force music changes '''during''' dialog exchange or other [event] which take significant time.<br /> * ''ms_before'' (optional) specifies how many milliseconds to delay before playing this track. Currently this does not apply when the scenario first starts, or with ''play_once'' or ''immediate''.<br /> * ''ms_after'' (optional) specifies how many milliseconds to delay after playing this track.<br /> <br /> === Example ===<br /> This creates a new playlist with three entries in it. The second track is always preceeded by 1/2 a second of silence.<br /> [music]<br /> name=background-music-1.ogg<br /> [/music]<br /> [music]<br /> name=background-music-2.ogg<br /> ms_before=500<br /> append=yes<br /> [/music]<br /> [music]<br /> name=background-music-3.ogg<br /> append=yes<br /> [/music]<br /> <br /> <br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=MapGeneratorWML&diff=8357 2006-03-22T00:28:34Z

<p>Placid: /* the [generator] tag] */</p> <hr /> <div>{{WML Tags}}<br /> == the [generator] tag] ==<br /> <br /> The [generator] tag replaces a scenario's map data;<br /> in fact it's whole purpose is to generate the map data given a set of configuration parameters.<br /> <br /> The map generator function is not very well documented.<br /> The data on this page are taken from<br /> <br /> == scenarios/multiplayer/Random_Map.cfg ==<br /> and '''scenarios/Heir_To_The_Throne/Sceptre.cfg'''.<br /> <br /> The following key/tags are recognized for [generator]:<br /> * '''[scenario]||/||[settings]''' See [[ScenarioWML]]<br /> * ''name''<br /> ** 'default'<br /> * ''map_width//,//map_height'' size of the map to generate<br /> * ''iterations''<br /> * ''hill_size''<br /> * ''max_lakes''<br /> * ''min_lake_height''<br /> * ''lake_size''<br /> * ''river_frequency''<br /> * ''flipx_chance'' for scenario generation.<br /> Percentage chance to flip map across X axis ???<br /> * ''villages''<br /> * ''village_density'' tiles per village ???<br /> * ''players''<br /> * ''temperature_iterations''<br /> * ''temperature_size''<br /> * ''default_convert''<br /> * ''roads''<br /> * ''road_windiness''<br /> * '''[height]''' list of common terrain types<br /> which come in at different heights, from highest to lowest<br /> ** ''height''<br /> ** ''terrain''<br /> * '''[convert]''' used to make terrain conversions.<br /> For example water becomes ice at low temperatures, grass snow, etc.<br /> ** ''min_height''<br /> ** ''max_height''<br /> ** ''min_temperature''<br /> ** ''max_temperature''<br /> ** ''from''<br /> ** ''to''<br /> * '''[road_cost]'''<br /> ** ''terrain''<br /> ** ''cost''<br /> ** ''convert_to_bridge'' a list of terrains;<br /> N/S, then NE/SW, then NW/SE.<br /> ** ''convert_to'' a terrain<br /> * '''[village]'''<br /> ** ''terrain''<br /> ** ''convert_to''<br /> ** ''adjacent_liked'' an unseparated terrain list<br /> ** ''rating'' chance of appearing<br /> * '''[castle]'''<br /> ** ''valid_terrain''<br /> ** ''min_distance''<br /> * '''[naming]'''<br /> ** ''male_names''<br /> * '''[village_naming]'''<br /> ** ''male_names''<br /> * '''[chamber]''' for underground maps<br /> ** ''id''<br /> ** ''x//,//y'' approximate location of the chamber<br /> ** ''size''<br /> ** ''jagged''<br /> ** '''[items]''' See [[ScenarioWML]].<br /> Locations of items will be generated randomly.<br /> The attribute '''same_location_as_previous=yes'''<br /> means that the filter for a moveto event (see [[EventWML]]) is the same as the location of the previous item.<br /> ** '''[passage]'''<br /> <br /> == See Also ==<br /> <br /> * [[ScenarioWML]]<br /> * [[ReferenceWML]]<br /> <br /> <br /> [[Category: WML Reference]]</div>

Placid https://wiki.wesnoth.org/index.php?title=LanguageWML&diff=8356 2006-03-22T00:28:19Z

<p>Placid: /* the toplevel [language] tag */</p> <hr /> <div>{{WML Tags}}<br /> == the toplevel [language] tag ==<br /> <br /> Each [language] tag represents one language.<br /> Languages are selected by pressing the &quot;Language&quot; button in-game.<br /> <br /> If you are just trying to make a language, then open the file '''data/sample-translation.cfg''', then translate all the<br /> pink text into another language<br /> (See [[WesnothTranslations]] for information on how to submit your translation).<br /> The purpose of this wiki, however, is to explain how the internationalization system works.<br /> (Note: this wiki is currently incomplete)<br /> <br /> == the Wesnoth internationalization system ==<br /> <br /> In the Wesnoth internationanization system, each tag that has keys with displayed text values is given an<br /> internationalization key, or an ''ID''.<br /> For example, the [scenario] tag has the key ''name'' which is a text value, and this value is displayed in the game.<br /> So each [scenario] tag is given an ID, which is used to translate this text in different languages.<br /> Most internationalized tags have the key ''id//; the value of ''id'' is the tag's ID.<br /> However, the tag [unit] (see [[UnitWML]]) uses the key ''name'' in place of ''id''.<br /> Important: since keys are not allowed to have spaces, all spaces should be removed when entering a key.<br /> However, several IDs use underbars instead of spaces; underbars should not be removed.<br /> <br /> <br /> == Internationalization attributes ==<br /> <br /> One type of internationalization attribute is the attribute '''''id//=//translation'''''.<br /> This attribute is interpreted as meaning that all tags with ID ''id'' should have their main text interpreted as<br /> ''translation''.<br /> For example, the attribute '''Elves_Besieged=&quot;Elves Besieged&quot;|| means that the scenario with ||id=Elves_Besieged''' should<br /> use the name &quot;Elves Besieged&quot; in the translation.<br /> <br /> However, some internationalized tags have multiple text attributes.<br /> An example is [scenario], which has the name of the scenario, and the scenario objectives.<br /> If the key ''key'' is not the main text of its tag, it is interpreted using the attribute<br /> == ''id//_//key//=//translation'' ==.<br /> For example the key '''Crossroads_objectives''' describes the scenario objectives for Crossroads.<br /> <br /> A list of tags which have IDs:<br /> * [campaign] main text: ''name//. Also, ''difficulty_descriptions//, which is written as ''difficulties''. See [[CampaignWML]]<br /> * [scenario] main text: ''name//. Also, ''objectives''. See [[ScenarioWML]]<br /> * [unit] main text: ''name//. Also, ''description''. See [[UnitWML]]<br /> * [message] main text: ''message''. See [message], [[InterfaceActionsWML]]<br /> * [object] main text: ''message''. See [object], [[DirectActionsWML]]<br /> * [terrain] main text: ''name''. See [[TerrainWML]]<br /> <br /> Another type of internationalization attribute: '''''type//_//specific//=//translation'''''.<br /> ''type'' is a type of text; ''specific'' is which text.<br /> For example the attribute '''ability_cures=&quot;cures&quot;''' would translate the ability &quot;cures&quot; as &quot;cures&quot;.<br /> <br /> The following are values for ''type'':<br /> * &quot;ability&quot; ''specific'' is the name of an ability (See [[AbilitiesWML]]).<br /> The translation will be displayed on the Status Table.<br /> * &quot;action&quot; ''specific'' is a UI action, for example &quot;Recruit&quot;.<br /> The translation will be displayed as an option on a menu.<br /> See [[ThemeWML]] for a list of UI actions, and for information on menus.<br /> * &quot;weapon_name&quot; ''specific'' is the name of a unit's weapon.<br /> All weapons with '''name=''specific//''' (see [[AttackWML]]) will be displayed on the Status Table as ''translation''.<br /> * &quot;weapon_special&quot; a weapon specialty, displayed in the Status Table under the weapon's name. See [[AbilitiesWML]]<br /> <br /> Another type: '''''tooltip//_description=//translation'''''.<br /> Whenever the player's cursor is over the word ''tooltip//, ''translation'' will be displayed as a tooltip.<br /> <br /> The following types of text can have tooltips:<br /> * (non-weapon) abilities. See [[AbilitiesWML]]<br /> * alignments. See [[TimeWML]]<br /> * status modifications. See [[StatusWML]]<br /> * '''weapon_special_''weapon-special'''''. See [[AbilitiesWML]]<br /> <br /> In addition to internationalization attributes, the following keys are recognized:<br /> * ''language'' the name of the language (in the language).<br /> This is displayed when selecting a translation.<br /> * ''id'' the internationalization key of the language<br /> <br /> == See Also ==<br /> * [[ReferenceWML]]<br /> <br /> <br /> [[Category: WML Reference]]</div>

Placid