The Battle for Wesnoth Wiki - User contributions [en]

Contrib:CaÃ§ada Selvagem

2006-01-21T18:13:33Z

GrabberBot: automated change of forum links take 2

== Caçada Selvagem ==

http://exong.net/wesnoth-attach/files/centaur-chieftain.png
http://exong.net/wesnoth-attach/files/centaur-chieftain-attack.png
http://exong.net/wesnoth-attach/files/centaur-chieftain_198.png
http://exong.net/wesnoth-attach/files/centaur-chieftain-hair2.png
http://exong.net/wesnoth-attach/files/centaur-spearman-alt_176.png
http://exong.net/wesnoth-attach/files/elvish_centaur_179.png
http://exong.net/wesnoth-attach/files/centaur_overview_001.png
http://exong.net/wesnoth-attach/files/centaur_overview_002.png

Contrib:Archenemy

2006-01-21T18:12:38Z

GrabberBot: automated change of forum links take 2

== Archenemy ==

http://exong.net/wesnoth-attach/files/undead-bat.png

Team Color Shifting

2006-01-21T18:03:50Z

GrabberBot: automated change of forum links take 2

by Richard Kettering (Jetryl)

===How to make units which conform to the system that lets us shift team colors.===

Any team color shifting system needs a way of indicating which areas of the graphic are to be changed in color. Ours solves this by selecting a certain range of colors, and shifting the pixels whenever they are that source color in the unit image. In our system, this can be done with any set of colors that you choose, on a per-unit basis. There are other ways that this could have been done, but this one was chosen for several reasons. For one thing, if we had used special grayscale image maps to indicate what to change, they would have basically doubled the number of images used by the game. The notable disadvantages of our system are that the colors which get shifted away are inaccessible for use, which is a minor issue, and that we only have a binary choice of a pixel getting shifted, which is a somewhat more major limitation, albeit one which is worth working around.

These colors are defined in the unit .cfg file. They are defined as follows, for an example in which we shift the colors black and white:
flag_rgb=0,0,0,255,255,255
Note that these shift ONLY the precise RGB values given - do not confuse color with hue, because every specific shade - every specific instance with a different luminosity and saturation value - must be specified separately.

The game will shift the color set to one of the team colors; in doing so it will completely overrun the saturation of the original color (E- not sure about that). It will change the hue to that of the team, and shift the luminosity as well. The coloration you give is set in terms of relative luminosity - the entire patch may be bright or dark depending on which team the unit is on.

Also note that the first color specified is special, because it is treated as the median value, and will be assigned the precise luminosity value of the team color. Anything brighter than it will be brighter than the team color, anything darker will be darker.

==WorkFlow:==
There are two general ways to do things. No matter what, you need a patch of color on the target unit which is separate from other colors, and is contiguous. It is best if this is only on specific sections, and does not have any stray pixels lying around in other areas of the image.

This can, on very rare occasions, be done to existing graphics with no changes in the target image; however it is almost always best to redesign the unit around use of the team color system. In this, you often go so far as to change the costuming, and to include props showing the team color which would not have been included before.

Possibly the easiest way to do this, to a reworked image, is to define a new layer in a capable program (photoshop, gimp, etc), overlaid on the rest of the image, in which you draw with a color that will stick out like a sore thumb. Magenta has often been used for this because it largely has no use as a normal color for general unit graphics.

http://exong.net/wesnoth-attach/files/colorswatch_200.png

We've actually defined a WML macro to specify a set of magenta colors, as seen in the previous palette. To use this, you simply sample the color with your graphics program's eyedropper tool, and then draw with it. The macro is used just like the flag_rgb business - you simply insert the following in your unit .cfg file (for reference, the macro itself is defined in utils.cfg):

{MAGENTA_IS_THE_TEAM_COLOR}

==Time-Saving Tips:==
If units are drawn with a small color set, as used in traditional sprite art, you can use a properly-set paint-bucket tool to replace all instances of a given color. You'll want to set it to be non-contiguous, non-antialiased and to have a tolerance of 0 (presumably, you also want it to fill based on "all layers" - these settings are based on Photoshop, and the Gimp is likely similar).

If someone used a "non-traditional" spriting technique (such as jetryl or wayfarer, using a paintbrush instead of a pencil tool), you're not out of luck at all. Simply take the same paint-bucket tool with the same settings, and crank the tolerance up to about 20-30. The paint-bucket will then affect all of those similar, subtle gradations in shade which were achieved with the paintbrush tool, replacing them all with a single color. Use this with progressively lighter shades, and you'll fill in 90% of the target area, after which it is trivial to fill the holes left behind with a pencil tool.

Also, if you'd like a sane representation of what the final colors will look like, you can shift this separate team-color layer in your graphics application by using a '''temporary''' hue/saturation filter on that layer (I use +40 to the hue on the magenta colors to give a red hue similar but '''not''' identical to the one which the game uses).

Finally, to keep things intuitive, if you are using the magenta swatch, which you should, it is often easiest to simply sample the colors from a unit to which this has already been applied.

==Screenshots==
This is a screenshot of what a unit looks like with his team color layer turned off - this is the graphic before the edit, essentially:

http://exong.net/wesnoth-attach/files/tcpatch_off_140.png

This is a screenshot of the team color layer itself. Note that it is only what is changed:

http://exong.net/wesnoth-attach/files/tcpatch_alone_654.png

And this is what the combined image looks like, which will get mixed-down into a single PNG file:

http://exong.net/wesnoth-attach/files/tcpatch_on_180.png

== See Also ==
* [[Create]]
* [[Art Tutorials]]

[[Category: Art Tutorials]]

Give Your Hero A Personality

2006-01-21T17:50:49Z

GrabberBot: automated change of forum links take 2

by Francisco Muñoz (fmunoz)

This tutorial details techniques for modifying existing wesnoth sprites in order to generate new, more unique images. This is especially useful when creating a "hero" character for a campaign, who behaves similarly to an existing unit type, such as the swordsman, thus needing to suggest the unit it is derived from, and yet look unique at the same time. Several of the techniques described herein, such as color transformations, are very useful for general work.

All instructions are given according to how one would use them in The Gimp, I'm sure that Photoshop users can easily translate them to equivalent commands. Attached to this message is a zip archive with the gimp file described in the tutorial.

'''1st Image, Edgar, the mercenary sword: Swapping heads'''

We want a variation of the swordman as our hero, thus we are going to use the easiest method, giving him a new head. We save the image file with a new name (to avoid accidentally overwriting the original one, one good way is to change the file format to the .xcf gimp original file format, rather than saving as a png). We open the swordsman image and change its mode to use more colours (Image->Mode->RGB). We delete the original head of the image by either selecting it and deleting the pixels in the selection (R and later Ctrl+K), or by using the eraser (Shift+E, but make sure to change the size to 1 pixel). We select the head from the head template, copy, and paste it over the body image, move (M) it to pick a place where it looks right. Then, we can just click again to merge it with the body layer or create a new layer for it (which is a better option) by clicking in the menu option under layer or in the layer palette. Now we have the 1st image of our new hero ready.

'''2nd Image, Harold of the horned helm : Layers'''

Lets do another one, this time we select the horned helmet head, and repeat the same steps again. If we used the multilayer approach we can reuse the body layer, after hiding the first face (click on the eye icon in the layer palette, if you don't have that palette, you can open it from the Dialogues mmenu). Looking at the image, we notice the horn is overlapping the sword. That doesn't look good. This time we are going to use another layer to fix it. We select the sword, copy, and paste it. This time we need to put it in another layer (not absolutely necessary, but a very helpful technique). We may need to change the ordering of the layers, to make sure that the new sword layer is placed over the head layer.

'''3rd Image, Victor, the Pirate Marine : Adding bits'''

This time we want more. We are going to use all the steps from the previous edit (and the same file too), but we are going to add minor extra bits here and there, a new sword point, a red gem in the shield, and extra shoulder padding.
After adding the new head and our new sword copy (to lay over the red bandanna end), we change its point a bit to make it into a kind of boarding sabre. We create another layer, where we draw a bigger set of shoulder pads using the armour colours. You can copy a few bits of armour into this new layer to get the colours more easily later; just paste them at one side and delete them when you are done. Using the pencil (N) with a size of 1 pixel, we draw the new shoulder armour. Remember that you can use the CONTROL key to pick colours fast from the samples we pasted before. We paste a red bit over the centre of the shield too (again in another layer).

'''4th Image, Rufus, the Breathdrainer: Colourize and change hue.'''

We want an evil swordsman variation, and we have an evil looking hooded head (kudos to artist Neoriceisgood) but the armour and weapon don't look evil enough.

We create a copy of the body, hide all the unused layers, and add the head using the same method as before. We go to the new body layer, which we want to look like a dark metal, so we start selecting the blue bits using either the Rectangle selection (R, later we can use CONTROL to remove parts and SHIFT to add them), or the Select by Colour tool (SHIFT+O, later we can use CONTROL to remove colours and SHIFT to add them). We can mix the two methods of selection; the end result of our "target" being selected is the same. We remove the pixels of the sword, because we are going to change them later.

From the menu Layer->Colours->Hue-Saturation, we change the saturation (to something less) and brightness (also less), until we have a darker, more sinister armour. We deselect the pixels (SHIFT+CTRL+A), and try to select the yellowish bits of the armour. As the pixels have a really soft colour, the former method doesn't work really well now, so we have to use Layer->Colours->Colourize to add more Saturation. We change mostly the hue until we have a dark purple. Now we repeat these things with the sword blade and the its handle to make it look like a wraith's sword (We can also easily do things by hand with the pencil tool).

Take note of the colour settings used if you plan to edit all the other unit frames. An easy way to do this is to use special layers that store and perform those color changes (which photoshop calls "adjustment layers"), rather than applying the changes directly to the picture data. Another way is simply to scribble down the few settings (hue, saturation, brightness) which were changed for each part of the unit, onto a piece of paper.

'''5th image, Karina, the Firemaiden: All at the same time'''

In this last image we add a new head, edit the sword to look like it is on fire, and change the armour colour until it looks like it is made of brass. The sword has been done using 3 layers, the original one, a flames one done using the fire colours from the Wesnoth item-firesword.png image and another copy of the original, placed above the others, with a 50% transparency (change it in the upper part of the Layer palette). As a last touch we add the same red bit we used in the Victor shield as a gem in the breastplate.

http://exong.net/wesnoth-attach/files/faces_166.png http://exong.net/wesnoth-attach/files/human-swordman-variations_127.png

The following is a [[http://www.wesnoth.org/forum/download.php?id=4919, zip file]] containing all the images.

== See Also ==
* [[Create]]
* [[Art Tutorials]]

[[Category: Art Tutorials]]

Editing Castles

2006-01-21T17:47:28Z

GrabberBot: automated change of forum links take 2

This tutorial is based on a gimp-python script, and as such is aimed squarely at users of The GIMP.

It will show you how to edit the existing castle tiles while making sure they continue to line up properly in game. The same technique can be used for any tiles which work on the same principle (such as Eleazar's new canyons, or Scott's indoor walls).

'''You will need to download both [http://www.wesnoth.org/forum/download.php?id=5197 this overlay template], and [http://www.wesnoth.org/forum/download.php?id=5196 this gimp-python script]. ''Extract the python script to your GIMP "plug-ins" directory'', and you're ready to go.'''

== Editing the Existing Castles ==

=== Step 1: Open ===

Open the overlay template in The GIMP.

http://exong.net/wesnoth-attach/files/shot1_568.jpg

Find the castle tiles you want to modify and drag them onto your image. This should add each castle image as a separate layer. In this case I'm modifying the "castle-convex" parts of pekka's castles.
Press 'M' and move the layers around so that the images line up around the central white hex. The layers should snap to the guides in the overlay template, so this should be easy to get exactly right.

http://exong.net/wesnoth-attach/files/shot2_531.jpg

You can hide the guides (as I've done here) by pressing shift-control-T, or deselecting "show guides" in the "View" menu.

=== Step 2: Edit ===

Edit the castle to your heart's content. Here I'm just going to put some annoying little flags on top. Make sure you edit one corner at a time, and that you keep each corner on a separate layer. It's useful to turn "Snap to Guides" off (in the "View" menu) if you're doing any freehand drawing.

http://exong.net/wesnoth-attach/files/shot3_178.jpg

=== Step 3: Save ===

Now to save the edited castle. First, make everything except for one corner invisible.

http://exong.net/wesnoth-attach/files/shot4_494.jpg

Then run the "WesCutter" script. If you've extracted the plugin to the right place, it should be found under "Wesnoth" in the Gimp "Python-Fu" menu. You'll be doing this again, so click the dotted line to detach the Wesnoth menu and save yourself a few clicks.

The script lets you choose a directory to save the file in (I'm saving to my desktop), the base filename (in this case, "castle"), whether it's a concave or convex image (added to the filename) and which corner it is (in this case, NW).

http://exong.net/wesnoth-attach/files/shot5_193.jpg

After clicking on "OK", I have a shiny new image called "castle-convex-nw.png" on my desktop, just the right size to work in Wesnoth. After doing this with all 6 corners, you can put them in the "images/terrain" subdirectory of your userdata directory (see [[EditingWesnoth]]). If you've put them in the right place, your new castles will automatically replace the old ones next time you run wesnoth http://www.wesnoth.org/forum/images/smiles/icon_smile.gif.

http://exong.net/wesnoth-attach/files/shot6_273.jpg

hooray!

== Making other Corner-Based Terrains ==

The same technique can also be used to make other corner-based terrains (for examples of other corner-based terrains, see [http://www.wesnoth.org/forum/viewtopic.php?t=7936 Eleazar's Canyons] and [http://www.wesnoth.org/forum/viewtopic.php?t=8274 Scott's Indoor Walls]).

== See Also ==

* [[Create]]
* [[Create Art]]
* [[CastleTutorial]]
* [[EditingWesnoth]]

Creating Shadows Under Units

2006-01-21T17:44:59Z

GrabberBot: automated change of forum links take 2

by Richard Kettering (Jetryl)

Wesnoth's shadows have evolved through several different iterations of "how they are drawn". This tutorial covers both a quick history of what was done in the past to draw shadows, and what the current "official" method is. As a general note, it should be mentioned that the shadows are part of the same image file as the unit graphics.

===History:===

Wesnoth, at first, used a binary transparency system - a pixel was either completely opaque, or completely see-through (transparent). This is not unlike what .gif images use, in terms of the final effect. The first system actually assigned one color (pure black, for those who are interested) as the transparent color, and anywhere where such a pixel was found in a game image, the engine would not draw it.

The next step was fairly obvious - wesnoth uses the PNG image format, which allows a special part of the image to be built-in to the file. This is essentially another image which tells the computer how transparent each pixel in the image is, and it is called an Alpha Channel. This "alpha channel" is a grayscale image, meaning that each pixel can be set to be not only either completely opaque or completely transparent, but also anywhere in-between. At first, we converted all of our images to PNG, but used only binary transparency. Our shadows were jet black, and obscured the ground completely.

As code support came, we switched to our next system, in which many of our images are in at the time of this writing. This set the shadow of a unit to be 60% opaque, allowing the ground beneath to show through, and looked rather good.

As our terrain improved, however, this began to show its limitations. The shadows had hard edges which were forced to lie on pixel boundaries. This looks unnatural for some of the situations in which we use it, and as such, we moved to our current system. This is simple, has a clear procedure which can be followed to generate it rapidly and correctly, and looks good in all situations. In the following image, compare the dwarf done with the old method, and the elven sylph done with the new method. It's a subtle, but potent difference, and is especially evident when the colored rings are drawn under our units to signify which team they're on:

http://exong.net/wesnoth-attach/files/unitshadows1_148.png

The obvious complaint about the current system is that it might be hard to edit, compared with the previous system. The solution is simple - just delete the previous shadow and recreate one from scratch. Because of how these shadows are made, it is relatively clear which pixels had been opaque in the source layer before blurring, and if a few pixels are different in a new frame, it is often unnoticeable. At most, the process of creating a new shadow will take a few minutes, and for animations, it has the benefit of forcing someone to draw a shadow from scratch (which should be done anyways).

===The Current Method:===

The first two steps in this method are for converting old shadows to the new system. To adapt it to creating a shadow from scratch, start with a new empty layer in your graphics program, and begin at step three. In this tutorial, I'll be using the process I used to create shadows for Neoriceisgood's Saurian Flanker as an example:

1] Select all of the pixels which make up the old shadow:

http://exong.net/wesnoth-attach/files/unitshadows2_123.png

2] "Cut" these into another layer in your graphics program. In photoshop, a wonderful tool for this is in the following menu: '''Layer -> New -> Layer via Cut'''. This acts like cutting the selection from one layer and pasting it as another in the exact same position it was in before.

3] Take this new layer, and draw over all of it in solid black with the pencil tool. When doing this, if you are converting an old shadow, you can use the old one as a guide for where the new shadow should fall. Regardless of what you're creating, however, there is an unusual thing to do in this step, and that is to draw in the entire area that a shadow would fall - not merely the area that is unobscured by the unit, but also in the area that you cannot see. This is important for a later step.

Note that this layer should be moved below all the other layers in the file. It's also very helpful to temporarily make the other layers mostly transparent, as this can guide you in intuiting where the shadow should fall on an imaginary ground:

http://exong.net/wesnoth-attach/files/unitshadows3_202.png

4] I generally duplicate this layer, when finished, and hide the duplicate "backup" layer.

5] Apply a gaussian blur to this layer, with a width of 0.5 pixels:

http://exong.net/wesnoth-attach/files/unitshadows4_193.png

6] Change the opacity of this layer to precisely 60%. If your graphics editor speaks in transparency instead, then set it to 40%, which is the same thing. Either one of these means that 40% of what is underneath will shine through the black. '''It's very important, however, not to deviate from using solid black, and not to deviate from using 60% opacity unless you have a good reason.''' Using these makes our unit imagery consistent.

http://exong.net/wesnoth-attach/files/unitshadows5_481.png

This, then, is what the final result of the example images in this tutorial looks like:

http://exong.net/wesnoth-attach/files/unitshadows6_182.png

== See Also ==
* [[Create]]
* [[Art Tutorials]]

[[Category: Art Tutorials]]

Basic Animation Tutorial

2006-01-21T17:39:53Z

GrabberBot: automated change of forum links take 2

by Jetryl

== Introduction ==

Animation works by fooling the mind into thinking that a series of still images are one continuously moving object. Certain things have to happen for the illusion to work. The basic principles are as follows, though keep in mind that these are interrelated:

* A moving object can only travel below a certain ratio of "screen space travelled" to "number of frames". If an object travels too far in too few frames, it will not look like it is moving, rather, it will look like it is disappearing from one location, and suddenly appearing in another.

* If the frames iterate too slowly - eg, less that 5 frames per second, the illusion of motion fails, and the whole thing looks more like a slideshow than an animation. Many 3d videogamers demand a framerate of 30fps from their hardware, or else they find the game to be too "jerky" and frustrating to play - some, even, demand 60fps. As a priciple, though, animation tends to fall apart somewhere between 5-10 fps.

Wesnoth is able to get away with a lot because we can programmatically create motion, some of the time. When a unit attacks, the code slides the attack image around. This allows us to use single images where we would be better served by multiple images. We can only get away with this in certain situations, however, and part of this is because the code-driven movement is both done at the maximum framerate of the running copy of wesnoth (often in the ballpark of a 3d game; some 30-60fps), and the code-driven movement is out-of-synch with the procedural animation, seemingly giving us additional frames of animation.

== Common mistakes: ==

All of these mistakes are ''absolutely unacceptable'' in an official in-game image. Some are very easy to correct, such as alignment, others, such as redrawing hidden surfaces, can make an animation much harder to do, but this is the price you ''must'' pay to make something look right. They're the laws of the real world, and fortunately, no one can use "style" as a cop-out for not following them - if you ignore these, your animation will look ''terrible''.

As a general principle, whenever you are tempted to use a shortcut to finish something, don't. It will look bad, and in the long run, it won't save any time, because if we end up using the animation, someone will have to pay the time to correct it. We will not use broken, half-hearted attempts at animations.

===Moving only the active element===
An animator thinks, "Hey, I'm animating a man swinging a sword. That means all I have to do is move the sword down in his hand." The animator then wonders why on earth his animation looks so poorly done.

Even the most subtle human motions will result in adjustments of the entire body, for balance. Human beings occupy what is known in physics as an "unstable" equilibrium point. If you set a pen on its point, it will fall over - amusingly enough, human beings are built, balance-wise, much like a pen. If we make any movement, we need to make an appropriate counter-movement, or we will fall on our face. Because of the way the human body is constructed, this generally means a rotation or movement of the entire torso, which makes anything connected (which is, the entire body) move with it.

In order to understand how something is supposed to move, you may need to look in the mirror, or look at a movie. There are many examples of good, medieval action films - titles such as Braveheart, or Lord of the Rings come to mind. Watch one of those movies, find a point where a character swings a sword, and watch what happens to the rest of the body. It's not subtle at all.
* Wrong: http://exong.net/wesnoth-attach/files/dark_queen_577.gif
* Right: http://exong.net/wesnoth-attach/files/orc_grunt-westattack0_213.gif (ignore the dithering (dots))

===Hidden surfaces must be redrawn===
When an object turns, in an animation, and shows a side that wasn't visble before, it ''must'' be drawn from scratch. If a man has his back to you, and turns around, his now-visible face will look a whole heck of a lot different from the back of his head, which was visible before. This is obvious! However, this is an often-repeated mistake, because people are afraid of having to draw parts from scratch. Cutting and pasting body parts, and moving them around can only be used for the tiniest motions, or motions in which there is NO rotation. The good news is, this is a great way for people to practice drawing parts of sprites, because here, they only have to draw a part of the unit's body, rather than the whole thing.

===Turned surfaces must be redrawn===
After about a 30-45 degree turn of any part of a sprite, the surface of that part has to be redrawn to account for the rotation. If a man is facing you, and turns sideways, his appearance will change considerably - for one thing, there will only be one eye visible where there were two visible before. Like I said above, '''DO NOT CUT AND PASTE'''. It simply will _ not look right.
* Wrong: http://exong.net/wesnoth-attach/files/elvish-rider-die_272.gif

===Misaligned Frames===
Each image in a series must line up correctly with the image before it. If they don't, the image shakes around inside the animation.
* Wrong: http://exong.net/wesnoth-attach/files/elfherb_170.gif

== Exaggeration techniques: ==

Traditional animation studios discovered several techniques along the way to "procedurally" liven up a strict representation of movement - that is, techniques that are probably correct to use even if you're not "drawing from life" and witnessing them firsthand. These were especially powerful in the first days of animation, because the drawings made were so simple, and left out a lot of the detail of the natural world - these are some of the first details to put back in. All of these are based vaguely on movement in the real world. If you exaggerate these too much, which you can certainly get away with, it will result in the animation looking cartoony, which is not necessarily a bad thing. These were developed in the first days of animation - in fact, fellows like Walt Disney were likely those who pioneered them.

* '''Wind-Up/Anticipation''' - When human beings prepare for a big move, such as swinging a baseball bat, or sword, they tend to give themselves some space to gain momentum. When a pitcher winds up for a throw, he curls back so that the ball will spend more time in his hand, thus spending more time accelerating, and thus have a higher speed. For wesnoth images, this is a great technique to use on big swords and clubs. If a man is going to throw a punch, he reels back with the arm that is preparing to deliver it. If a cobra is going to strike, it first rears back its head. Think of what "Popeye the Sailor Man" does when he's about to clobber someone, and you'll have good example of the "cartoony" range of things.

* '''Inertia and Air Resistance''' - Different things are affected by physics in different ways. When a person makes a motion, certain muscles drive the motion, and the rest of the body is pulled by this force acting on it. The most important thing is that different parts of the body will move at different speeds - this is related to my mantra of ''"move the whole body"'' - if you do it, things will look a ''lot'' more realistic.

* '''Non-rigid Objects''' - Most objects in the real world flex in extraordinary ways when they move, ways that you would never guess, but which are clearly percieved by the "subconcious," and thus look right when animated. For a stunning example, if you look at a slow-motion recording of baseball being hit by a bat, the baseball gets flattened like a pancake! This happens only for the tiniest moment, after which it oscillates back and forth (like a spring) returning to it's normal shape. In wesnoth animation, using such a thing only for a single frame can make for a much livelier animation.

* '''Follow Through''' - often taught to beginning boxers, a strike given with enough force to damage will often be targeted not at the surface of the opponent, but deep inside and even behind him. This is also related to many situations in which the person performing an action doesn't care where the moving object stops - a baseball player is not concerned with where the bat stops in his swing, rather he just wants to hit the ball as hard as he can, which is why the bat will often swing a full half-circle beyond home plate. In animating wesnoth images, this is why it looks better if really strong sword strokes go ''clean through'' the point where the opponent is standing. As an example, this is why the Elvish Hero's attack looks stronger than that of the Elvish Fighter.

* '''Cycling/Looping''' - In the real world, points of view do not remain fixed like they do in animations or videogames, but certain motions often get repeated, sometimes almost identically. One of the first tricks that animators used was to make animations of people doing something like walking. Instead of imitating the real world, wherein each step taken is subtly different from the next, as the mind carefully coordinates changing balance and the uneven conditions of the ground "plane", the animators simply drew a single step of the person walking, and lined up the images so that the final frame lined up with the first frame. Though one could not change the point of view on the subject, the animation could be looped indefinitely, and would look convincingly like viewing a person walking from a specific angle. For our purposes, this can be used to link together any repeating animations (such as walking animations).

== Some examples ==

Taken from Zhukov's edit of the orcish grunt
<table>
<tr><td>
http://exong.net/wesnoth-attach/files/orc-grunt-westbase_146.png
</td><td>
The base frame for an Orcish Grunt
</td></tr>
<tr><td>
http://exong.net/wesnoth-attach/files/orc_grunt-westattack_f1_203.png
</td><td>
Wind up - note the exaggerated pullback
</td></tr>
<tr><td>
http://exong.net/wesnoth-attach/files/orc_grunt-westattack_f3_123.png
</td><td>
Strike - note the whole body has moved, and most (but not all) of it has had to be redrawn.
</td></tr>
</table>

== See Also ==

* [[Art Tutorials]]
* [[Create Art]]
* [[Create]]

[[Category: Art Tutorials]]

DescriptionWML

2006-01-21T16:35:54Z

GrabberBot: automated change of forum links

== Description texts ==

A description is a part of the value of a menu attribute.
It is used to represent a single option in the menu which consists of an image(called the ''icon'') followed by text.

A description has the format

* ''';''' if another description precedes it

* '''*''' if it should be the default selection

* '''&''image''=''text''''' image with text description

* '''&''image''=''text''=''text2''''' image with two text descriptions

Single text items are always enclosed in '''"''', and concatenated with '''+'''. This is useful so the text can contain translateable items (the '''_''' before a text), and so it can span multiple lines.

for example:

difficulty_descriptions="&" + "elvish-fighter.png" + "=" + _"Fighter" + "=" + _"(easiest)" +
";*" + "&" + "elvish-hero.png" + "=" + _"Hero" +
";" + "&" + "elvish-champion.png" + "=" + _"Champion" + "=" + _"(hardest)"

The utility macros (see [[UtilWML]]) '''{MENU_IMG_TXT ''icon'' ''text''}'''
and '''{MENU_IMG_TXT2 ''icon'' ''text'' ''text-2''}'''
can be used to create descriptions more easily. The above example would become:

difficulty_descriptions={MENU_IMG_TXT2 "elvish-fighter.png" _"Fighter" _"(easiest)"} +
";*" + {MENU_IMG_TXT "elvish-hero.png" _"Hero"} + ";" +
{MENU_IMG_TXT2 "elvish-champion.png" _"Champion" _"(hardest)"}

== See Also ==

* [[CampaignWML]]
* [[EraWML]]
* [[ReferenceWML]]

Description

2006-01-21T16:35:46Z

GrabberBot: automated change of forum links

== What is Battle for Wesnoth? ==

The Battle for Wesnoth is a turn-based strategy game with a fantasy theme.

<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-0.8.4-halo.jpg http://www.wesnoth.org/images/sshots/wesnoth-0.8.4-halo-175.jpg]
<div class="thumbcaption">Silver Mage in action</div></div>
</div>

''Build up a great army'', gradually turning raw recruits into hardened veterans. In later games, recall your toughest warriors and form a deadly host against whom none can stand! Choose units from a large pool of specialists, and hand-pick a force with the right strengths to fight well on different terrains against all manner of opposition.

Fight to regain the throne of Wesnoth, of which you are the legitimate heir, or use your dread power over the Undead to dominate the land of mortals, or lead your glorious Orcish tribe to victory against the humans who dared despoil your lands … Wesnoth has many different sagas waiting to be played out. You can create your own custom units, and write your own scenarios – or even full-blown campaigns. You can also challenge your friends – or strangers – and fight ''multi-player'' epic fantasy battles.

== Features ==

<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-0.8.4-burningsuns.png http://www.wesnoth.org/images/sshots/wesnoth-0.8.4-burningsuns-175.jpg]
<div class="thumbcaption">Under the Burning Suns</div></div>
</div>

* Build up a formidable fighting force, starting from a single leader and a small amount of gold.
* Over 200 unit types in six major factions, all with distinctive abilities, weapons and spells.
* Experienced units gain powerful new abilities as they advance.
* Several multi-player options available, including internet play.
* Scores of different custom-designed maps, and unlimited random maps.
* Hundreds of campaign scenarios available for download via a simple in-game procedure.
* 'Fog of war' feature available for a true test of generalship.
* Sophisticated mark-up language lets advanced users make their own maps, factions or campaigns.
* Excellent language support &ndash; 20 different languages currently available.
* GNU/Linux, Windows, MacOSX, BeOS, Solaris, FreeBSD, OpenBSD and NetBSD compatible.

{{Play}}

DelfadorsMemoirs

2006-01-21T16:35:46Z

GrabberBot: automated change of forum links

This campaign follows the adventures of Delfador, beginning from him leaving home as a newly qualified journeyman mage,
and leading up to him helping to bring peace to Wesnoth. It is set a couple of generations earlier than "Heir to the
Throne".

Comments: email to Josh Parsons, jp30 AT st-and.ac.uk.
Thread is at http://www.wesnoth.org/forum/viewtopic.php?t=1293.

== Installation notes ==

Delfador's Memoirs is distributed as a tarball (.tar.gz), containing all sources for the campaign.
The tarball is built with automake. To install, unpack it, change into the directory delfadors-memoirs-(version) and
run (as root) "./configure && make && make install"

If you can't install DM this way, then you may install download and install it from the campaign server (you will need
wesnoth 0.8.5 or a current CVS version to do this).

== Download ==

Version 0.1: (3 playable scenarios) requires wesnoth = 0.7.7
* http://www.st-and.ac.uk/~jp30/memoirs-0.1.tar.gz

Version 0.2: (7 playable scenarios) requires wesnoth = 0.7.9
* http://www.st-and.ac.uk/~jp30/delfadors_memoirs-0.2.tar.gz
* http://www.st-and.ac.uk/~jp30/delfadors_memoirs-0.2.zip

Version 0.3: (9 playable scenarios) requires wesnoth >= 0.7.11 (=0.7.11 for the tarball)
* http://www.st-and.ac.uk/~jp30/delfadors_memoirs-0.3.tar.gz
* http://www.st-and.ac.uk/~jp30/delfadors_memoirs-0.3.zip

Version 0.4: (10 playable scenarios) requires wesnoth >= 0.7.11, <= 0.8.3
* http://www.st-and.ac.uk/~jp30/delfadors_memoirs-0.4.tar.gz
* http://www.st-and.ac.uk/~jp30/delfadors_memoirs-0.4.zip

Version 0.5: (10 playable scenarios) requires wesnoth >= 0.8.4, <= 0.8.7
* http://weka.ucdavis.edu/~jp30/delfadors_memoirs-0.5.tar.gz

Version 0.5.1: (10 playable scenarios) requires wesnoth >= 0.8.4, <= 0.8.7
* http://weka.ucdavis.edu/~jp30/delfadors_memoirs-0.5.1.tar.gz

Version 0.5.2: (10 playable scenarios) requires wesnoth >= 0.8.9
* http://weka.ucdavis.edu/~jp30/delfadors_memoirs-0.5.2.tar.gz

== See Also ==

* [[UserScenarios]]

DebuggingWesnoth

2006-01-21T16:35:42Z

GrabberBot: automated change of forum links

A common problem is that a user of Wesnoth has Wesnoth crash on them, but no developers can reproduce the problem, and so that makes it very difficult for us to fix it.

Fortunately, if you are using GNU/Linux or another Unix-like system, have compiled Wesnoth yourself, and you have debugging symbols in (the default when compiling), or your packager has left debugging symbols in, you can do a little debugging yourself to send to a developer. Even a non-programmer can do enough to give a developer alot of clues about where Wesnoth is crashing.

When a program crashes, if the system is configured correctly it will leave behind a 'core' file. A 'core' file contains the contents of memory [1] at the time the program crashed. However, many systems by default have the maximum size of cores set very low, or to 0, meaning that the system won't dump cores. So, before running Wesnoth, use the following command in the same terminal you plan to run Wesnoth from to make it so that cores will be always dumped, no matter how large they are.

'''ulimit -c unlimited'''

Then, run Wesnoth, and do whatever you have to do to make it crash. The last line of output should be something like,

'''Segmentation Fault (core dumped)'''

or perhaps,

'''Aborted (core dumped)'''

or something similiar. The core file will then be in the current working directory, and will either be called 'core' or 'core.<pid>' where <pid> is the process ID of Wesnoth before it crashed. You can of course list all cores in the current directory using,

'''ls core*'''

Now that you have your core, you can open it and see where Wesnoth crashed. To open it, you run gdb giving it the path to the Wesnoth binary as its first argument, and the core file as its second. The most common usage is,

'''gdb ./wesnoth ./core'''

This should run gdb, and print out alot of information which is generally of no consequence (unless there is an error message). gdb should give you a prompt, at which you can type the command,

'''bt full'''

This should make gdb print out what is known as a 'backtrace' -- a list of all the functions Wesnoth was in when it crashed. Copy everything that gdb printed out below where you typed bt full, and send it to a developer. It's a good idea if you keep the core file around, because the developer may need you to open it again with gdb to run some more commands.

[1] 'core' is an old-fashioned Unix term for memory.

DanishTranslation

2006-01-21T16:35:33Z

GrabberBot: automated change of forum links

= Danish Translation =
As of Aug 10 2005 the Danish translations has been brought to life again. Contact Anders K. Madsen
(mailto:madsen@lillesvin.net) if you want to help out. If you need to get in touch with the entire Danish translation team, try: [mailto:wesnoth-daATlillesvinDOTnet]

= Status =
This is the status of the development versions of the translations. If you want to see the stats for the ones actually included in the CVS version of Wesnoth, goto: http://gettext.wesnoth.org ([http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.lang.php?lang=da stats for danish]).

'''Note:''' The percentage of fuzzy translations are counted as a sub-part of the translated strings, so if you calculate the total percentage it may look a bit weird at times.

<center>

<table border="1">



<tr><th colspan="5" style="background-color: #ddd">Revision 49 (64% done)</th></tr>
<tr><th>Fil</th><th>I alt</th><th>Oversat</th><th>Fuzzy</th><th>Mangler</th></tr>
<tr><td>./wesnoth/da.po</td><td align="right">1572</td><td align="right">(57%) 906</td><td align="right">(3%) 53</td><td align="right">(42%) 666</td></tr>
<tr><td>./wesnoth-httt/da.po</td><td align="right">840</td><td align="right">(71%) 602</td><td align="right">(1%) 13</td><td align="right">(28%) 238</td></tr>
<tr><td>'''./wesnoth-lib/da.po'''</td><td align="right">129</td><td align="right">(100%) 129</td><td align="right">(0%) 0</td><td align="right">(0%) 0</td></tr>

</table>

</center>

= Overblik =
Vi er startet helt forfra med oversættelsen, da kvaliteten af de tidligere oversættelser ikke var acceptabel. (Noget lignede mistænkelig meget maskinoversættelse...)

Oversættelserne ligger i et subversion repository på http://svn.lillesvin.net/wesnoth_da - der kan du hente de nyeste versioner af filerne. Du kan også surfe rundt mellem filerne i et mere brugervenligt (og avanceret) miljø på http://lillesvin.net/viewcvs/wesnoth_da

== Faste termer ==
Har du forslag til rettelser, så kør dem omkring oversætterholdet ([mailto:wesnoth-daATlillesvinDOTnet]). Alle forslag (og forbedringer) er meget velkomne.

<center>
=== Generelt ===
<table border="1">
<tr>
<td align="center">'''Original'''</td>
<td align="center">'''Oversættelse'''</td>
</tr>
<tr>
<td>Battle for Wesnoth</td>
<td>Kampen om Wesnoth</td>
</tr>
<tr>
<td>Abilities</td>
<td>Evner</td>
</tr>
<tr>
<td>Units</td>
<td>Enheder</td>
</tr>
<tr>
<td>Experience</td>
<td>Erfaring</td>
</tr>
<tr>
<td>Hitpoints / HP</td>
<td>Hitpoints / HP</td>
</tr>
<tr>
<td>Experience points / XP</td>
<td>Erfaringspoint / XP</td>
</tr>
<tr>
<td>Advance(ment)</td>
<td>Forfremme(lse)</td>
</tr>
<tr>
<td>Zone-of-Control</td>
<td>Kontrolzone</td>
</tr>
<tr>
<td>Traits</td>
<td>Karaktertræk</td>
</tr>
<tr>
<td>objectives</td>
<td>mål</td>
</tr>
<tr>
<td>time of day</td>
<td>tid på dagen/døgnet</td>
</tr>
<tr>
<td>Village</td>
<td>Landsby</td>
</tr>
<tr>
<td>castle</td>
<td>borg</td>
</tr>
<tr>
<td>keep (på en borg)</td>
<td>tårn</td>
</tr>
<tr>
<td>blade (skadestype)</td>
<td>klinge</td>
</tr>
<tr>
<td>pierce (skadestype)</td>
<td>stik</td>
</tr>
<tr>
<td>impact (skadestype)</td>
<td>slag</td>
</tr>
<tr>
<td>upkeep</td>
<td>vedligeholdelse</td>
</tr>
<tr>
<td>alignment</td>
<td>sindelag</td>
</tr>
<tr>
<td>lawful</td>
<td>hæderlig</td>
</tr>
<tr>
<td>neutral</td>
<td>neutral</td>
</tr>
<tr>
<td>chaotic</td>
<td>lyssky</td>
</tr>
</table>
<br />

=== Racer og professioner ===
<table border="1">
<tr>
<th>Original</th>
<th>Oversættelse</th>
</tr>
<tr>
<td>Saurian</td>
<td>Øgle</td>
</tr>
<tr>
<td>Undead</td>
<td>Udød</td>
</tr>
<tr>
<td>Elvish</td>
<td>Elver</td>
</tr>
<tr>
<td>Merman</td>
<td>Havmand</td>
</tr>
<tr>
<td>Orc(s)</td>
<td>Ork(er)</td>
</tr>
<tr>
<th colspan="2">Professioner</th>
</tr>
<tr>
<td>Skirmisher</td>
<td>Stifinder</td>
</tr>
</table>
</center>

==== BEMÆRK ====
Når man oversætter mange af racerne til dansk, så kan det være praktisk at sammensætte racenavnet med enhedens profession, så f.eks. ''Elvish Fighter'' bliver til ''Elverkriger''. Dette gælder selvfølgelig ikke for racer som f.eks. Undeads/Udøde, hvor ''Undead Fighter'' ville blive noget i stil med ''Udød kriger''.

== Svært-oversættelige termer ==
Du er meget velkommen til at foreslå oversættelser til især termerne listet her!
<dl>
<dt>ancient</dt>
<dd>som i "Ancient Guard". Kan nogle gange oversættes til noget i stil med ''gammeldags'' eller ''traditionel'', ellers er det måske muligt at slippe afsted med ''... af de Gamle Tider'', hvis pladsen tillader det.</dd>
</dl>

= Oversættere / Translators =
== Aktive / Active ==
* Anders K. Madsen (madsen) - mailto:madsen@lillesvin.net
* Jesper Fuglsang Wolff (ulven) - [mailto:ulvenATdibidutDOTdk]
* Bjarke Sørensen (basher) - [mailto:bsATwasdDOTdk]

== Inaktive / Inactive ==
* Mark Michelsen (skovbaer) - [mailto:skovbaerATfemgramskovbaerteDOTdk]
* Mathias Bundgaard Svensson (freaken) - [mailto:freakenATfreakenDOTdk]

CzechTranslationANewOrderCampaign

2006-01-21T16:35:26Z

GrabberBot: automated change of forum links

== Translators ==
* [[User:Tapik]]
== ChangeLog ==
* The campaign translation is still under heavy translation.

== Remarks in Czech ==
* Skřeti a Trolové mají ořezaný slovník, takže neskloňují. Navíc hodně komolí: "Já zabýt to. To být úžasný písňa o já."
* Akladians jsou Akladijci. Je snaha je překládat tak, aby byla patrná podoba mezi Akladijci a Áríjci, neb se chovají úplně stejně. Navíc vznikli jako kříženci skřetů a lidí, takže musí být jejich řeč také nechutná. Jedinou výjimku je zatím Reme Carremnoe. Jeho věrnost je neakladijská, tak proto.
* Underling překládám jako porobenec. Lepší překlad neznám. Kdyby někdo věděl, jak Němci nazývali podrobené slovanské národy (hlavně Poláky a Rusy), asi by to bylo ono.

Creating Unit Art

2006-01-21T16:34:57Z

GrabberBot: automated change of forum links

Here's the information needed to start doing units art for Wesnoth. Please update the wiki with links to examples and other tips and tricks realted to unit art. This page started from [http://www.wesnoth.org/forum/viewtopic.php?p=104809#104809 this forum thread].

=== Basic unit image specifications ===
*Final format is PNG, 72 x 72 pixels
*the units should be contained in the hex (the white in the attached template)
*Normal Units (humans and elves) are about 40px tall
*Small Units (dwarves and goblins) are a bit over 30px tall
*Tall Units (drakes and great trolls) are a bit under 50px tall
*Light comes from a specific direction (for shadings and highlights)
*Unit must look in the lower right direction
*Units are centered horizontally
*Units feets are positioned around 55 pixel from the top, lower for taller units
*Shadows at 60 opacity, black color.
*Outlines should be used, made with a darker, but similar colour to what they're surrounding, this makes the unit feel bigger then the amount of pixels you'd use for the same with a black outline.
*Use consistent names for your files, beginning with the unit name, so that they are kept together when browsing the files.

=== Unit animation specifications ===
*You can have as many frames for animations as you like. It depends on what you want to get accross
*Images and animations must be done for:
*normal image (1 frame)
*attack for each type (at least one frame - 2 is good)
*directional attacks (spear and ranged)
*defense
*death frame
*magical attacks should have 'special effects'

You can also have multiple defense animations (like the thief.)
Defense can be split into ranged and melee animations.

It is important that the unit moves its feet when doing a melee attack. During the attack the unit will move from its own hex to the hex it is attacking. If you don't have feet movement in your animation, the unit will be "sliding" toward it's target, which looks bad.

=== Additional Notes and examples ===

*Test early with different backgrounds. Go to your game terrain files, pick, say, 3 terrains, preferably with different colours, and have a look what they look like against the background, because that way if you have used alpha channels, it may look better in game than as the average standard sprite.

*Test your unit early in the game. Replacing an existing unit graphic with yours is the fastest way (be sure to make a copy of the originals so you don't lose them.)

*If you are animating a horse, you should base it on this [http://www.wesnoth.org/forum/viewtopic.php?t=7592&sid=eb882602a04b48cf8fcce9ca77fbeae0 example of an horse animation]

*The thief is a very good example of what can be done. It has basically all possible animations. It doesn't use the multidirectional ranged images, though, since it's not a ranged unit.

== See Also ==
* [[BuildingUnits]]
* [[Create]]
* [[Create Art and Music]]
* [[Art Tutorials]]

Creating Shadows Under Units

2006-01-21T16:34:51Z

GrabberBot: automated change of forum links

DebuggingCampaigns

2006-01-21T16:34:42Z

GrabberBot: automated change of forum links

"Debugging" means to fix by removing errors. Here are some ideas to help you when you are building a campaign and need to fix it.

== Things to check when your scenario doesn't load ==

*Do the id tags match exactly? Does the id in the caller script have the same case (lowercase/uppercase) as the scenario's id?

*Is the ".cfg" extension appended to the script filename?

*Is the script in the right location (usually campaigns/YOUR_MODULE/scenarios)

*Is it really a scenario load problem? Maybe the main CFG file isn't being loaded correctly.

*Are all the linking tags spelled correctly?("first_scenario=???", "next_scenario=???", "id=???")

*If you're using the template, did you remember to change the script in the utils directory to load your module? Otherwise you might get a recursion error that may prevent your scenarios from loading (remember, scenarios are loaded last)

*Is a downloaded module breaking you version of the game?

*Do you have read permissions on your scripts?

== See Also: ==

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

Create Art

2006-01-21T16:34:26Z

GrabberBot: automated change of forum links

== Getting Started ==

=== General Information ===

Graphic artists usually meet on the [http://www.wesnoth.org/forum/viewforum.php?f=9 artwork development forum]. This is a great place to discuss new and current Wesnoth art and graphics, and to see what other people are contributing.

Unit and terrain art is stored in the portable network graphics (PNG) format. Each frame of a unit animation, and each variation of a terrain is stored as a separate .png file in the "images" subdirectory of wesnoth, and generally these files will be 72 x 72 pixels (the size of Wesnoth's basic hexagonal tile) with an alpha channel (a part of the file that indicates how transparent each pixel is). When creating your own images, you can test them without overwriting any game data by putting them in your userdata directory (see [[EditingWesnoth]] for details on Wesnoth's directory structure). The game also supports JPEG images, though these are better suited for story art.

To edit these graphics, you'll need some program capable of creating PNGs - some of the programs in the following list are free, open-source software, and will do the job nicely: [[Art Programs]]

If you need some inspiration, we have a [[GraphicLibrary|Graphics Library]] which collects art posted on the forum. You can use this for ideas, and as a scrap heap for different parts of unit images (a technique described [[Give Your Hero A Personality|here]]). One of the best examples of the library's content came from the project artist "Neoriceisgood," which can be seen in the following [http://www.wesnoth.org/forum/viewtopic.php?t=4466 forum thread].

=== Roadmap ===
A list of what's being done and what needs doing:
* '''[[Tiles Status]]''' - a roadmap/plan of sorts for future work on terrain tiles
* [http://www.wesnoth.org/forum/viewtopic.php?t=9162&sid=21cf168d2b077d06bb0017c059b4add6 A list] of current work that needs to be done with sprites.

== Art Tutorials ==

These are a work-in-progress, and describe both how to make art fit into wesnoth's style, as well as giving some considerable tips on drawing in general. Especially useful is the [[External Tutorials]] page which lists some very good art tutorials available on the web.

=== Terrain Graphics ===

The following is information specific to drawing terrain for Wesnoth. Read Frame's "Tiles Tutorial" for a good overview of how terrain graphics work.

* [[Tiles Tutorial]] - Frame's tutorial describing the process of making terrain tiles in wesnoth, and how they interact with adjacent tiles.
* [[How To Make Seamless Tiles]] - Eleazar's tutorial on making your terrain tiles seamless. The tutorial is aimed at Photoshop users, but the technique is similar with The GIMP.
* [[CastleTutorial|Castle Tutorial]] - A description of how Wesnoth's castle tiles work (needs updating, but useful nonetheless)
* [[MultiHexTutorial|Multi-Hex Tiling Tutorial]] - A description of how multi-hex tiles work.
* [[Editing Castles]] - Instructions for how to make/edit castles (and other corner-based terrains) using yobbo's GIMP script.

These describe the system used to specify how terrains behave in game:
* [[TerrainLettersWML]] - A list of the letters used to represent terrain types.
* [[TerrainGraphicsWML]] - If you really need to get technical, start here.
* [http://www.anathas.org/ayin/wesnoth/doc/terrain_graphics_wml Ayin's Terrain Graphics document] - If you really, ''really'' need to get technical, this describes the terrain graphics WML system in depth.

=== Sprite Art ===
The following are different tutorials about sprite work compiled by various wesnoth sprite artists. These will give you the most specific-to-wesnoth information about making sprites, and are well worth a read.

* [[Creating Unit Art]] - a list of specifications you will need to match.
* [[Give Your Hero A Personality]] - tricks for editing existing images, including some clip art.
* [[Basic Animation Tutorial]] - or "How to Animate Sprites for Dummies," covering the basic theory, and all of the mistakes to avoid.
* [[Team Color Shifting]] - how to use our new team color system (only for wesnoth 1.1 or greater).
* [[Creating Shadows Under Units]] - how we create the shadows for the units in-game
* [[Making Bow Animations]] - the current standard for how we want bow animations to work

=== External Tutorials ===
The following page contains dozens of links to tutorials covering all manner of artwork, including sprite art. These were not made by wesnoth artists, but should prove very useful for general instruction.

* [[External Tutorials]]

== See Also ==
* [[Create]]
* [[EditingWesnoth]]
* [[GraphicLibrary]] - Lot's of usercontributed graphics (most should be GPL'ed)
* [[Project]]

ConventionsWML

2006-01-21T16:34:23Z

GrabberBot: automated change of forum links

The purpose of this page is to list conventions of WML --
that is, things that make WML more readable and flexible.
Note that this page is not official;
in fact most mainline campaigns do not follow this.

== Macros ==

Using macros is useful for decreasing the size of a file,
and for making it clear
that you are doing the same thing several times.
A good rule for when to use macros
is to use them whenever information is being repeated.
For information on how to create and use macros, see [[PreprocessorRef]].

Also, if you are writing a campaign,
you should use campaign macros.
These are macros in the main .cfg file of your campaign;
i.e. the one with the [campaign] tag.
They can be used in any scenario of your campaign.
One useful campaign macro is a "deaths" macro, which describes events
that should occur in all scenarios of your campaign;
for example an event causing you to lose when your hero dies.
Refer to this macro in each of your scenarios.

Put campaign macros after the #ifdef of your campaign;
that way they will not conflict with other campaign's macros.

== Indentation ==

In indentation, every subtag is indented 1 level outward of its parent tag.
Toplevel tags are not indented;
neither are the direct subtags of macros and files.
For example, in unit files [unit] is not indented,
and every macro should have at least 1 unindented tag or attribute.
A macro references should be indented
as though it were the contents of the macro it refers to.
Some macros require the use of another macro later;
in this case the macro should be considered as a tag,
with its counterpart as the closing tag.

Example:

[scenario]
[event]
#define START_STORE_UNIT
[store_unit]
[unit]
#enddef
#define END_STORE_UNIT
[/unit]
variable=temp
[/store_unit]
#enddef
{START_STORE_UNIT}
type=Elvish Fighter
[not]
x,y=$x1,$y1
[/not]
{END_STORE_UNIT}
[/event]
[/scenario]

Although spaces can substitute for tabs (as done in this wiki),
it is generally not advisable to use a series of spaces
to substitute for a single tab - one is enough.

Some writers don't indent subtags of [if]
because of the way these tags are used recursively;
indenting these tags fully could cause line wraps
to make the code incomprehensible.

There are two ways to indent keys:
normal indentation, and savefile indentation.
In normal indentation, a key is indented
on the same level as the tag containing it,
and in savefile indentation a key is indented
1 level outward of that.

Examples:

Normal indentation:
[scenario]
turns=16
[side]
side=1
[/side]
[/scenario]

Savefile indenatation:
[scenario]
turns=16
[side]
side=1
[/side]
[/scenario]

It doesn't matter what indentation format you use,
but if a file is not indented
then it is harder to tell what is going on;
for example it is difficult to catch errors in tag matchups.

== Naming files ==

First of all, don't put spaces in filenames;
this causes errors on some systems.
Use underscores('''_''') instead.

If the IDs of your scenarios are different from their names,
name the files after the IDs, not the names.
That way it is easier to tell which scenario is next.

If files are named in a numerical order,
put 0 at the beginning of single-digit numbers.
This makes the alphabetical sorting also a numerical sorting.
For example if you have 20 different maps, you can name them
'MAP_01', 'MAP_02'...., 'MAP_20'.

== WML variables ==

(For information about what WML variables are, see [[VariablesWML]].)
These shouldn't be used except when necessary.
[have_unit] tags can often be used instead.
Also, make sure that your scenarios
clear meaningless variables using [clear_variable].

For variable values, use 'yes' and 'no' for boolean values
rather than 1 and 0.
It's clearer to people who don't know programming.

== See Also ==
* [[ReferenceWML]]

Create

2006-01-21T16:34:22Z

GrabberBot: automated change of forum links

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 "guts" 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.

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.

== Read this first! ==
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.
* [[EditingWesnoth]]

== What can I create, and how? ==

<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth_editor-1.jpg http://www.wesnoth.org/images/sshots/wesnoth_editor-1-175.jpg]
<div class="thumbcaption">Battle for Wesnoth Map editor</div></div>
</div>

* [[BuildingMaps|Maps]] - the layout of terrain tiles
* [[BuildingScenarios|Scenarios]] - a scenario makes things happen on a map, making it playable
* [[BuildingCampaigns|Campaigns]] - how to put it all together into a campaign
* [[BuildingMultiplayer|Multiplayer Maps and Scenarios]] - a specialized look at maps and scenarios
* [[BuildingUnits|Units]]
* [[BuildingFactions|Multiplayer factions and eras]]
* [[Create Art|Art]] - complete with ''tutorials!''
* [[Create Music|Music]]
* [[Distributing content]] - all about the campaign server
* [[WesnothTranslations|Translations]] - work on translating Wesnoth

== What have others done? ==
Quick descriptions of the campaigns and scenarios that have been published on the campaign server.
* [[UserScenarios|User contributed campaigns]]
This there are a multitude multiplayer maps and discussion of the campaigns on the [http://www.wesnoth.org/forum Wesnoth forum]
* [http://www.wesnoth.org/forum/viewforum.php?f=15 Multiplayer development forum]
* [http://www.wesnoth.org/forum/viewforum.php?f=8 Scenario and campaign development forum]
* [[Complete Faction List (unfinished)|Complete Faction List]]

== The world of Wesnoth ==
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.
* [[WesnothHistory|The history of Wesnoth]]
* [[WesnothGeography|The geography of Wesnoth]]
* [[RaceDescriptions|The races of creatures in Wesnoth]]
* [[Custom_RaceDescriptions|User made races for Wesnoth]]
* [[WesnothPoetry|Wesnothian poetry]]

== Miscellaneous ==
* [[ExternalUtilities| External Utilities]] - some extra tools for easier creating stuff
* [[ReferenceWML|WML Reference]] - a quicklink
* [[FAQ#Scenario_and_Campaigns|FAQ]] - if you have a question, post it
* Campaign server [http://wolff.to/campaigns/list.html web interface] - An alternate way to download user campaigns
* [[Status_of_User_Scenarios| Status of User Scenarios]] - Lists which usercampaigns are working and which ones are broken
{{Home}}

CommandMode

2006-01-21T16:33:42Z

GrabberBot: automated change of forum links

== Command Mode ==

You can access command mode by typing ' ''':''' ' in a single player or multiplayer scenario.
More accurately, you need to type shift - semicolon( ''';''' ). However this isn't possible on all keyboards; if your keyboard doesn't have ':' above ';' you can change the hotkey in the Preferences, or you could edit '''game.cfg''' by hand.'

Several vi-like commands are available in command mode. They are defined in ''playturn.cpp'' in the ''turn_info::do_command()'' function:
;<nowiki>:q or :q!</nowiki>
:quit the scenario (without prompting)
;<nowiki>:w</nowiki>
:save the game (without prompting)
;<nowiki>:wq</nowiki>
:save the game and quit the scenario (without prompting)
;<nowiki>:refresh</nowiki>
:redraw the screen
;<nowiki>:droid</nowiki> ''side''
:toggle player on side between human and AI players. If a human controls the side, the player himself has to issue this command.
;<nowiki>:kick</nowiki> ''username''
:kick a user in multiplayer. They will be able to rejoin the game. Generally a friendly way to remove someone who is having connection or other difficulties.
;<nowiki>:ban</nowiki> ''username''
:kick and ban a user in multiplayer, and the IP address used by that username
;<nowiki>:control</nowiki> ''side'' ''username''
:change the controller for ''side'' (write here number of the side) to ''username'' (write here nick of player or observer)
;<nowiki>:clear</nowiki>
:clear chat messages
;<nowiki>:debug</nowiki>
:switch debug mode on (does not work in multiplayer). Debug mode is turned off by quitting the game.
;<nowiki>:theme</nowiki>
:bring up theme selection menu

===Extra Debugging Commands===
[[DebugMode]] enables additional commands in command mode:

;<nowiki>:n</nowiki>
:skip to next scenario by triggering a win event
;<nowiki>:gold</nowiki> ''amount''
:add ''amount'' gold to the current player's side
;<nowiki>:create</nowiki> ''unit_type''
:create a unit of type specified at last selected hex
;<nowiki>:unit</nowiki> ''attribute=value''
:when a unit is selected, this will set the unit's ''attribute'' to ''value''. See [[SingleUnitWML]] for possible values.

== See Also ==

* [[DebugMode]]
* [[DeveloperResources]]

CodingStandards

2006-01-21T16:33:37Z

GrabberBot: automated change of forum links

Wesnoth uses modern/advanced C++ that is portable to Visual C++ 6 and GNU G++ 3.0+

== End Non-Public Members of Classes with an Underscore ==

All non-public data members of classes should have their names terminated with an underscore, to show that they are a
class member. This makes for more readable code, once one is familiar with the convention.

== Use References when a value may not be NULL ==

If a value passed to a function can never be NULL, use a reference instead of a pointer. I.e.

void myfunction(Object& obj);

rather than

void myfunction(Object* obj);

This more clearly shows the user of the function that obj may never be NULL, without them having to consult
documentation or the implementation of the function.

== Use Const ==

The 'const' feature of C++ allows interfaces to more clearly specify how they treat objects. Always use const when you
are not going to modify an object.

I.e.

void myfunction(const Object& obj);

demonstrates to the caller of myfunction() that obj will not be modified. If myfunction may modify obj, then use

void myfunction(Object& obj);

likewise, if a variable is not changed after initialization, make it const.

== Write Exception-Safe Code ==

Wesnoth code should be exception-safe, even if you do not use exceptions directly. That is, you should be able to assume that an exception is thrown almost anywhere from within the code, with well-defined results (i.e. no resource leaks).

Code that uses a pattern like,

{
SDL_Surface* image = IMG_Load("image.bmp");
...some code, which uses 'image'...
SDL_FreeSurface(image);
}

is bad, because the code may throw an exception, and 'image' will never be freed. Instead, use wrapper objects which free the object in their destructor.

For SDL_Surface objects, use the <tt>surface</tt> class. So you could rewrite the above code,

{
surface image(IMG_Load("image.bmp"));
...some code, which uses 'image'...
} ''the image is automatically freed here when 'image' is destroyed

Instead of allocating memory directly using new[] or malloc(), use language-provided containers, such as vector.

== Respect for loop scoping of different platforms ==

In the code,

for(int i = 0; i != 100; ++i) {...}

the variable 'i' is scoped within the for loop according to ISO/ANSI C++ and GNU G++. However it is scoped within the
surrounding scope according to Visual C++ 6.

This means that the code,

for(int i = 0; i != 100; ++i) {}
for(int i = 0; i != 100; ++i) {}

is illegal on VC++6, because i is defined twice, although it is legal according to the standard, and GNU G++.

On VC++6, the legal way to write it would be,

for(int i = 0; i != 100; ++i) {}
for(i = 0; i != 100; ++i) {}

But this is illegal according to the standard, because 'i' is not defined in the second loop. The correct way to write
this code to conform to the standard and work on all platforms is to simply abandon declaring variables in the
initialization statement of a for loop when the variable must be reused in the same scope,

int i;
for(i = 0; i != 100; ++i) {}
for(i = 0; i != 100; ++i) {}

== Use the function templates minimum and maximum ==

Standard C++ offers the function templates min and max to find the minimum and maximum of two values on which operator
<
is defined. Unfortunately, many hoops must be leapt through to get this working on VC++. So, we do not use standard
min
and max. Instead, we use minimum and maximum, defined in utils.hpp.

Usage is fairly natural:

int i = minimum(x,y);

Note that in the above example, if x is an unsigned integer, and y is a signed integer, VC++ will have problems. You
must explicitly specify the version of minimum being called in such cases:

int i = minimum<int>(x,y);

== Do not use wstring ==

The standard C++ wstring class, defined as a basic_string< wchar_t >, does not exist in some platforms supported
by
Wesnoth. Use wide_string, defined in language.hpp, instead. wide_string is actually defined as a vector< wchar_t >

== Use util::array instead of C-style Arrays ==

C-style arrays are very efficient, but their interface is ugly. Use util::array defined in array.hpp. It is a wrapper
for an array which has a C++ container-style interface. If you need to, extend it to make it fit your needs.

== Do not use sprintf ==

Sprintf does not check whether or not it is writing passed the end of the space allocated. This is a security problem if someone other than the person running the game can cause sprintf to write very long strings. In Wesnoth this untrusted data could come potentially from other players in a multiplayer game or from downloaded campaigns. Instead you should use snprintf with the second argument being sizeof of the buffer that will hold the result.

ChineseTranslation

2006-01-21T16:33:32Z

GrabberBot: automated change of forum links

== ''' Wesnoth的中文翻译工作正在进行当中。''' ==

如你喜欢这个游戏，并且愿意为翻译工作尽一份力，请联系firen.china@gmail.com

对于如何开展翻译工作有疑问的也可以发邮件和我联系。

====目前参与翻译的人员有：====

<pre>Firen
Luyang Han
Solkarnar
</pre>

====翻译进度: ====

<pre>游戏主模块文件：翻译中 (50%)
游戏编辑器文件：未开始翻译
主模块和编辑器共享文件：翻译已完成（By Luyang Han)
战役文件：翻译中（Solkarnar）
</pre>

====名词确认：====
以下是一些已经被确认的名词翻译方式，请翻译者注意。同时，如果你遇到新的名词觉得有必要在翻译中进行统一，请发邮件到 firen.china@gmail.com 进行讨论
<pre>
Battle for Wesnoth : 韦诺之战
Recruiting and Recalling : 征兵和召回
Keep : 要塞
Orcish Grunt : 咕哝兽
Terrain Modifiers : 地形影响
Leader : 领袖
Traits : 特质
Ability : 技能
Skirmisher : 刺客

人名（黑眼之子）
Albert : 阿尔伯特
Ar Dant : 亚单
Blemaker : 别马克
Etheliel : 伊特立尔
Filiel : 飞立尔
Gork : 古洛
Grüü : 库鲁
Howgarth III:豪伽施
Inarix : 依娜丽丝
Jetto : 杰图
Kapou'e ：卡破尔
Karun : 卡伦
Kult : 苦熬
Kwili : 魁里
Lanbec'h : 兰贝契
Lucile : 路西尔
Ma-rana ：玛·拉纳
Mkel : 科尔
Na-Mana ：纳·马那
Oumph : 欧汉
Pe : 披
Pirk : 辟克
Plonk : 普隆克
Plouf : 普劳夫
Raceme : 瑞斯密
Rugh : 如克
Rahul I:拉乎尔
Shan Taum : 善同
Slowhand : 史洛汉德（暂用，不知意译或音译比较妥当）
Toughkon : 陶亢
Vraurk : 福莱克

地名（黑眼之子）
Barag Gór : 八拉·格
Bork river : 伯克河
Desert of Death : 死亡沙漠
Haag Mountains : 海格山区
Mourned Hills : 哀悼山峦
Prestim : 普莱斯亭
Silent Forest : 幽静森林
Tirigaz : 提里加斯

其他
Council : 元老会
Shaman : 萨满祭司（据魔兽世界所译）
Saurian : 蜥蜴人
Troll : 巨魔（据魔兽世界所译）
</pre>

CatalanTranslation

2006-01-21T16:33:29Z

GrabberBot: automated change of forum links

Aquesta és la pàgina del wiki dedicada a la traducció del Wesnoth al català.

== Estat de la traducció ==
<table border="1" style="width:80%">
<tr><th>Element</th><th>Traducció</th><th>Revisió</th><th>Estat</th></tr>
<tr><th colspan="4" style="text-align:left">Campanyes</th></tr>
<tr><td>Hereu al tron</td><td>focks, tin, paurullan, ettin</td><td>-</td><td>Pendent revisió</td></tr>
<tr><td>Les Hordes Obscures</td><td>paurullan</td><td>-</td><td>Fet</td></tr>
<tr><td>Fill d'Ull Negre</td><td>brrr</td><td>-</td><td>Fet</td></tr>
<tr><td>La Invasió de l'Est</td><td>Linuv</td><td>-</td><td>Pendent revisió</td></tr>
<tr><td>El Despertar de Wesnoth</td><td>Azazelo, paurullan</td><td>-</td><td>Pendent revisió</td></tr>
<tr><th colspan="4" style="text-align:left">Interfície</th></tr>
<tr><td>Wesnoth</td><td>focks, ettin</td><td>-</td><td>Pendent revisió</td></tr>
<tr><td>Lib</td><td>ettin</td><td>-</td><td>Fet</td></tr>
<tr><td>Editor</td><td>ettin</td><td>-</td><td>Fet</td></tr>
<tr><th colspan="4" style="text-align:left">Altres</th></tr>
<tr><td>MANUAL.catalan</td><td>Mark Recasens</td><td>-</td><td>Pendent revisió</td></tr>
<tr><td>Pàgina <code>man</code></td><td>-</td><td>-</td><td>-</td></tr>
<tr><th colspan="4" style="text-align:left">Campanyes addicionals - [[WesCamp]]</th></tr>
<tr><td>Les memòries de Delfador</td><td>Azazelo</td><td>-</td><td>En curs</td></tr>
<tr><td>Terra lliure</td><td>kilder</td><td>-</td><td>Fet/Revisió</td></tr>
<tr><td>Disturbis a terres elfes</td><td>kilder</td><td>-</td><td>Fet/Revisió</td></tr>
<tr><td><em>A New Order</em></td><td>kilder</td><td>-</td><td>En curs</td></tr>
<tr><td><em>Orcish Incursion</em></td><td>?</td><td>-</td><td>En curs</td></tr>
</table>

== Equip ==
* Carles Company (brrr)
* Dan Rosàs Garcia (focks)
* Daniel López (Azazelo)
* Jonatan Alamà (tin)
* Jordà Polo (ettin) - [mailto:jordaAettinPUNTorg] [coordinador]
* Jose Gordillo (kilder)
* Pau Rul·lan Ferragut
* Equip traducció Linuv

== Enllaços ==
* [http://ettin.org/vault/wesnoth/ca/unitats.html Noms de les unitats]
* Al fòrum: [http://www.wesnoth.org/forum/viewtopic.php?t=1115 Wesnoth en català]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/ Estadístiques de les traduccions]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.lang.php?lang=ca Estadístiques de la traducció al català]

== Recursos ==
* [http://www.softcatala.org/projectes/eines/guiaestil/guiaestil.htm Guia d'estil de Softcatalà]
* [http://dcvb.iecat.net/ Diccionari català-valencià-balear]
* [http://www.grec.net/home/cel/dicc.htm Gran Diccionari de la Llengua]

== On trobar-nos ==
* Llista de correu: [http://ettin.org/mailman/listinfo/wesnoth-ca_ettin.org wesnoth-ca] ([http://ettin.org/pipermail/wesnoth-ca_ettin.org/ arxius])
* IRC: Canals #wesnoth i #wesnoth-ca a irc.freenode.net
* Correu: jorda AT ettin DOT org

CastleTutorial

2006-01-21T16:33:21Z

GrabberBot: automated change of forum links

== Building tileable castles - A tutorial ==

== Introduction To Castles ==

===Overview===

Wesnoth terrain graphics system allows the WML designer to create various
terrain graphics "models": rules that allow to determine how the different
terrain tiles will be displayed by the game. Those allow the terrain designer
to specify renderings that go beyond the simple "one terrain type = one image"
representation.

One of those terrain models is the Castle (it will be called like that,
"Castle", all along this document, although this model can be used for many
other terrain types, like, for example, caves.) Castles are created from two
type of elements: a castle floor, and a castle wall. Castle floors are normal,
basic tiles that are placed on each corresponding tile. As those really have
nothing special, they will not be detailed in this document. What we will
detail is how to build castle _walls_.

===The Simple Castle Model===

The Simple Castle Model is used to build castle walls, without keeps. Castle
walls are special transitions, that are drawn between Castle tiles, and
Non-Castle tiles. For example, imagine some castle tiles are disposed as shown
in figure (1); castle walls will then be drawn as shown in figure (2)

''(figure 1)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure1.png

''(figure 2)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure2.png

Castle Walls are composed of 12 different images (as show in figure 3), that
tile together. Those are positioned at the corners of the castle border, as
shown in figure 4.
"convex" images are positioned at convex borders, "concave" images are
positioned at concave borders (as it hopefully might be expected.) When we talk
about "concave", or "convex" borders, we always take the castle's interior
point of view.

''(figure 3)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure3.png

''(figure 4)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure4.png

===The Keep Model===

The Keep Model is created to build the special transitions that are used to
build a wall around the Keep of a Castle. Keeps are assumed to be always
composed of one tile (isolated from any other keep tile.)
Keeps are a little more complex than castles walls: they are built from 24
different images (see figure 5,) thus setting to 36 the number of images
required for a complete castle.

''(figure 5)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure5.png

There are 4 kinds of keep images: those representing keeps corners that are
outside of a castle, those representing keep corners that are inside of a
castle, and thos representing keep corners which are in the border; the last
one being divided in 2 categories, depending on the castle-keep tiles going
clockwise, or counter-clockwise (see figures 5 and 6.) Interior keep tiles are
supposed to tile with other interior keep tiles, and with corresponding
transition tiles; same for exterior keep tiles. Figure 6 illustrates the
different types of transitions for keep tiles.

''(figure 6)''

== The Wall ==

===Tile drawing problematics===

To draw tileable castles, one should start with drawing the wall. Some tileable
castles may only consist on a wall, without a keep (Think here that what we
call "Castles" in this document may apply to a lot of other terrains, built
with the same rules. Also think that some castle may have keeps that are normal
tiles.)
The 12 tiles that compose a wall are made from 2 groups of tiles, as stated
above: convex wall tiles, and concave wall tiles. Tiles for each one of those 2
groups are drawn together, then automatically cut out using a specialized
software. That way, only 2 graphics are necessary to generate those 2 tiles.

The main problem, as that should be inferred from reading the tile model
description, is making convex graphics tiling with concave graphics: as concave
graphics are drawn together, there is no problem making them tile together;
same with convex graphics. See figure 7 for an illustration of this problem: ||A and
B are drawn together, so they tile perfectly. However, we must make sure A will
correctly tile with C!||

''(figure 7)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure7.png

Geometry, and a good methodology, may be used to make those tile correctly.
This is possible, but, trust me, this is tedious. And hard to maintain. And
even harder to explain. And, the more complex the graphics are, the harder it
is. That is why ia helper tool was developed, to help in the process.
The helper tool we are talking about is called the Castle Exploder. We will
describe how to used it to build a complete castle.

===Preparing the work environment===

Before using the Exploder, you must prepare a work environment. The Exploder,
must be provided with files named according to a correct pattern in order to be
able to work.
Exploder files are named according to the type of image they represent. The
"type" of the image corresponds to the position of the different tiles that
compose the image. For example, the exploder recognizes any image that is
called foobar-convex.png as containing the 6 convex castle walls, disposed
around an hex.

There currently are 7 different image types; all of which are used to build a
complete castle with keep. Those are named:

* convex
* concave
* exploded-convex
* exploded-concave
* keep (not yet available)
* keep-walls (not yet available)
* keep-flower (not yet available)

''(figure 8)''

Forget about the last 3 ones for now; the 4 first ones are used to build
castles.

Download the castle project here:

http://www.anathas.org/ayin/wesnoth/castle-tutorial/files/castle_project.zip

To prepare your work environment, unpack the castle_project.zip file in a
directory of your choice.

===Drawing The Convex Wall===

Open, using your favourite bitmap editor the file "castle-convex.png" (if your
favourite bitmap editor cannot open png files, I can't help you.) You will see
the following:

''(figure 10)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure10.png

Do not be afraid with all those coloured polygons! Those just are guides, that
will help you to position your image. If your bitmap editor handles layers, I
suggest you make the actual drawing on another layer, keeping this one to
provide guidelines. If it does not, you should just delete all this coloured
stuff.
The different hexes, corresponding to the position of the actual terrain hexes
in the game, are represented with a value change. The 6 different corners, that
will be cut into tileable pictures, are represented with a hue change.

This image is supposed to represent a convex castle tile: that is, a single
castle hex, followed by non-castle hexes all around. Draw the corresponding
graphics on it. You do not have to bother about them tiling together: they
will, as they were drawn together.

Some guidelines on drawing the wall: when drawing a wall, the TOP of the wall
(not the bottom) should be around the hex border (TODO: confirm this: this is
good for the positioning of units, but not so for villages near castles)
Ideally, a wall should not be higher than 1/4 of a tile (that is: 18 pixels).
Try to make the castle appear to be viewed under the same angle as other
castles, and villages.

Let's draw the wall (figure 11).

''(figure 11)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure11.png

===Exploding The Wall=== http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/castle-exploder.png

Now, we must draw the concave version of the wall. To make sure it will
correctly tile with the convex version, we will not directly draw it in the
castle_concave.png image: we will draw it in an exploded version of the
castle_convex.png image. That is where the Exploder Tool comes into play.

Just open a terminal window, and type the following command:

exploder castle-convex.png castle-exploded-convex.png

The exploder will open the first file, extract from it the tiles it
recognizes, then put those on the second file, if there is a place to put
them (For example, exploding castle_concave.png to castle_convex.png is a
no-op, as those two pictures do not have any tile in common.)

''After the program finishing merging the tiles'', the castle-exploded-convex.png
file will then look like figure 12

''(figure 12)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure12.png

===Drawing The Concave Wall===

Draw the castle graphics on the 6 concave tiles, so that they tile correctly
with the convex tiles. It is useless to modify the concave tiles; if you have
inadvertently done so, you may explode back the castle_convex.png file on the
file you are working on. Do not worry: your work will not be lost; as the
exploder tool does only overwrite the portions of the image it actually
replaces.

''After you have drawn the missing castle corners'', the castle-exploded-convex.png
file should look like figure 13

''(figure 13)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure13.png

===Imploding Back the Concave Wall===

The concave tiles you drew should, magically, tile together. However, you may
want to ensure they actually do, and, if they don't, to correct them so they
do. Just implode back the castle_exploded-convex.png file into the
castle_concave.png file, using the command

exploder castle-exploded-convex.png castle-concave.png

It should look like as in figure 14.

''(figure 14)'' http://www.anathas.org/ayin/wesnoth/castle-tutorial/images/figure14.png

===Further manipulations===

===Cutting The Tiles For Use In The Game===

Once you have up-to-date castle_convex.png and castle_concave.png files, you
must cut them, so they are usable by Wesnoth. To do this, create a directory
where you want the cut tiles to be output (or you may just use the "output"
directory which already was created), and use the commands:

cutter castle-concave.png output
cutter castle-convex.png output

== Keeps ==

As it was said above, keeps are a little bit more complicated than castles.
Keep always being composed of one isolated tile, keep tiles always are convex,
however, they may have several different relationships with nerby castle tiles:
they may be inside of a castle, outside from a castle, or in a border.

===The keep views===

===Drawing interior and exterior keeps===

Keeps inside of a castle, and keeps outside of a castle, may be strictly
identical. However, for your graphics to be more "realistic," you may decide they
are different. For example, keep tiles located outside of a castle may have no
doors, less windows, they even may have a stronger wall, etc. Interior keep and
Exterior keep tiles do not need to tile together, as there always will be an
intermediate Border tile to make transition. They may be made separately;
however, keep in mind that you will have to make each transition between those.
If they are too different, transitions may be clunky.

===Making keep transitions===

===Flower Power===

CampaignWML

2006-01-21T16:33:07Z

GrabberBot: automated change of forum links

== the [campaign] tag ==



This tag describes a campaign, and is used for the "Campaign" menu
in the title screen.

The '''[campaign]''' tag has the following attibutes:
* ''icon'' the image displayed in the campaign selection menu
* ''name'' (translatable) name displayed in the campaign selection menu
* ''image'' the image shown in the information pane when this campaign is selected in the campaign selection menu
* ''description'' (translatable) text shown in the information pane when this campaign is selected in the campaign selection menu
* ''define''='''''CAMPAIGN_SYMBOL''''' when this campaign is started, the preprocessor symbol '''''CAMPAIGN_SYMBOL''''' will be defined. See '''#ifdef''' in [[PreprocessorRef]] for how this can be used to isolate parts of the campaign file from other campaigns. Only the tags '''[campaign]''' and '''[binary_path]''' (see [[BinaryPathWML]]) should go outside of '''#ifdef ''CAMPAIGN_SYMBOL'''''.
* ''difficulties'' a comma(''',''') separated list of preprocessor symbols, exactly one of which will be stored depending on the difficulty setting chosen when the campaign is started. The symbols '''EASY''', '''NORMAL''', and '''HARD''' are usually used, and there are several macros in utils.cfg (see [[UtilWML]]) which check for these values to set WML keys to different values depending on difficulty. If you use different difficulty symbols, you may need to define your own versions of these macros.
* ''difficulty_descriptions'' the menu of difficulties; this is a list of descriptions (see [[DescriptionWML]]) that correspond to different difficulty levels. Since each description is a menu option for a difficulty level, this must provide the same number of descriptions as there are levels in the ''difficulties'' list.
* ''first_scenario'' the ID of the first scenario in the campaign; see ''id'' in [[ScenarioWML]]
* ''rank'' a number that determines the order of campaigns in the campaign selection menu. Lower ''rank'' campaigns appear earlier, with unranked campaigns at the end. Currently the mainline campaigns use multiples of 10 from 10 to 50; if you specify this, it should not be less than 51.

The following keys of '''[campaign]''' are obsolete and have no effect:
* ''id'' the internationalization key for the campaign

== See Also ==

* [[PreprocessorRef]]
* [[ScenarioWML]]
* [[ReferenceWML]]
* [[PblWML]]

[[Category: WML Reference]]

CampaignUnrest

2006-01-21T16:33:04Z

GrabberBot: automated change of forum links

== Translation of Unrest in Elfland ==
This is a list of the people currently translating Unrest in Elfland into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>kilder</td><td>completed</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>Ivanovic</td><td>completed</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>[[HungarianTranslation|Műhelyben]]</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>RokStar</td><td>completed</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>tephlon</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Unrest&order=trans Translation stats for Unrest in Elfland]

CampaignTwoBrothers

2006-01-21T16:32:56Z

GrabberBot: automated change of forum links

== Translation of Two Brothers ==
This is a list of the people currently translating Two Brothers into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>Ivanovic</td><td>completed</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>[[HungarianTranslation|Műhelyben]]</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>RokStar</td><td>completed</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>Sanna, Lugo Moll</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Two_Brothers&order=trans Translation stats for Two Brothers]

CampaignServerWML

2006-01-21T16:32:44Z

GrabberBot: automated change of forum links

= Campaign Server WML =

This page describes the WML commands exchanged between campaign download clients and a campaign server. Note that this WML is not used in the game engine. Note that this page describes functions of the 1.1 campaign server, because that is what is used by the official campaign server.

== Listing Available Campaigns ==

This request is used to retrieve a list of campaigns available on the server and some overview information about them.

* Request
** '''[request_campaign_list]'''
*** ''after'' - only select campaigns last updated after the indicated time. ''after'' is in seconds relative to either the time when the command is processed or the [http://wikipedia.org/wiki/Unix_epoch Unix epoch]. As an example, to select campaigns last updated after Mon Oct 10 21:42:41 2005 GMT, you could not specify a value for ''times_relative_to'' (to use the default of relative to the [http://wikipedia.org/wiki/Unix_epoch Unix epoch]) and specify ''after'' = "1128980561".
*** ''before'' - only select campaigns last updated before the indicated time. ''before'' is in seconds relative to either the time when the command is processed or the [http://wikipedia.org/wiki/Unix_epoch Unix epoch]. As an example, to select campaigns last updated over a day ago, you could specify ''times_relative_to'' = "now" and ''before'' = "-86400".
*** ''language'' - return information only about campaigns that appear to be translated into this language. These names will normally be posix locale names. Typically you will want to either use a two letter language code (e.g. "de") or a two letter language code followed by a two character region code (e.g. "pt_BR"). Note that "pt" will not match "pt_BR".
*** ''name'' - return information for this campaign. If the name is specified and not the empty string then only information about campaigns with matching names (unless something changes there will be at most one such campaign) will be returned.
*** ''times_relative_to'' - "now" means that ''before'' and ''after'' are in seconds relative to the time when the request is processed by the campaign server. Any other value, or if it is not set, indicates that ''before'' and ''after'' are in seconds relative to the [http://wikipedia.org/wiki/Unix_epoch Unix epoch].
* Response
** ''timestamp'' - what time the campaign server thought it was when this response was generated. You shouldn't count on this as a guaranty that no new campaigns will appear with previous update times. This could be used to detect significant clock skew or possibly used as an approximate time for how far you need to look back for updated campaigns.
** '''[campaigns]'''
*** '''[campaign]'''
**** ''author'' - author(s) of the campaign.
**** ''description'' - description of the campaign. For pre 1.0 campaigns this should also describe the playability.
**** ''downloads'' - the number times the campaign (including previous versions) has been downloaded directly from the campaign server.
**** ''filename'' - filename campaign is stored in (currently the same as ''name'').
**** ''icon'' - path to an image in the standard image directory for Wesnoth. This path must use forward slashes (/). It cannot refer to custom images included with the campaign. This image is displayed as an icon by the campaign client built into Wesnoth.
**** ''name'' - the name of the campaign. Note this is not the title and shouldn't have spaces in it.
**** ''size'' - the size of the campaign in bytes on the campaign server.
**** ''timestamp'' - when this version of the campaign was uploaded.
**** ''title'' - campaign title. This is not a translatable string.
**** ''version'' - version of the campaign. The recommended format is x.y.z where x, y and z are decimal strings. x should be 0 for campaigns that are not yet complete.
**** '''[translation]'''
***** ''language'' - a language that this campaign has appeared to have been at least partially translated into. The following hueristic is used when a campaign is uploaded to extract a list of languages. The list of directories in the uploaded campaign is recursively searched. If a directory named 'LC_MESSAGES' is found then the name of the object containing this '''[dir]''' (normally the parent directory, but could be the campaign name if someone did something silly) is added to the list of translations. Directories named "LC_MESSAGES" are not searched for further matches. The normal naming convention is to use Posix locale names. This will usually be a two letter language code (e.g. "de") or a two letter language code followed by a two letter region code (e.g. "pt_BR"). Since "en_US" is the base language, this language will not be listed as an available translation.

== Downloading a Campaign ==

This command is used to download a specified campaign from the campaign server.

* Request
** '''[request_campaign]'''
*** ''name'' - the name of the campaign. Note this is not the title and shouldn't have spaces in it.
* Response
** ''author'' - author(s) of the campaign.
** ''campaign_name'' - the name of the campaign. Note this is not the title and shouldn't have spaces in it.
** ''description'' - description of the campaign. For pre 1.0 campaigns this should also describe the playability.
** ''icon'' - path to an image in the standard image directory for Wesnoth. This path must use forward slashes (/). It cannot refer to custom images included with the campaign. This image is displayed as an icon by the campaign client built into Wesnoth.
** ''name'' - this field will always be empty. Client code would treat it as a directory name if it was not empty.
** ''passphrase'' - this is used to control updates to campaigns on the server. For existing campaigns, if the passphrase doesn't match the update will be rejected. You can't change the passphrase yourself. If you lose or need to change the passphrase you need to contact the server administrator.
** ''timestamp'' - the time the campaign was last uploaded to the campaign server. This is a decimal string containing the number of seconds since the unix epoch.
** ''title'' - the title of the campaign. This is not a translatable string.
** ''version'' - version of the campaign. The recommended format is x.y.z where x, y and z are decimal strings. x should be 0 for campaigns that are not yet complete.
** '''[file]'''
*** ''name'' - the name of the file. This does not include any path information.
*** ''contents'' - the content of the file (binary data). This data should have no zero bytes. A byte with the code of 1 is an escape byte. The next byte will be data, but its value should be reduced by 1. Normally only byte codes of 0 and 1 are escaped.
** '''[dir]'''
*** ''name'' - the name of the directory. This does not include any path information.
*** This tag may contain '''[file]''' or '''[dir]''' subtags (the latter are recursive).

== Uploading a Campaign ==

This command is used to upload a new or updated version of an add on campaign to the campaign server.

* Request
** '''[upload]'''
*** ''author'' - author(s) of the campaign.
*** ''description'' - description of the campaign. For pre 1.0 campaigns this should also describe the playability.
*** ''icon'' - path to an image in the standard image directory for Wesnoth. This path must use forward slashes (/). It cannot refer to custom images included with the campaign. This image is displayed as an icon by the campaign client built into Wesnoth.
*** ''name'' - the name of the campaign. Note this is not the title and shouldn't have spaces in it.
*** ''passphrase'' - this is used to control updates to campaigns on the server. For existing campaigns, if the passphrase doesn't match the update will be rejected. You can't change the passphrase yourself. If you lose or need to change the passphrase you need to contact the server administrator.
*** ''title'' - the title of the campaign. This is not a translatable string.
*** ''version'' - version of the campaign. The recommended format is x.y.z where x, y and z are decimal strings. x should be 0 for campaigns that are not yet complete.
*** '''[data]'''
**** '''[file]'''
***** ''name'' - the name of the file. This does not include any path information.
***** ''contents'' - the content of the file (binary data). This data should have no zero bytes. A byte with the code of 1 is an escape byte. The next byte will be data, but its value should be reduced by 1. Normally only byte codes of 0 and 1 are escaped.
**** '''[dir]'''
***** ''name'' - the name of the directory. This does not include any path information.
***** This tag may contain '''[file]''' or '''[dir]''' subtags (the latter are recursive).
* Response
** '''[message]'''
*** ''message'' - translatable string that indicates that the campaign upload was successful.

== Changing the Passphrase for a Campaign ==

This command is used to change the passphrase for a campaign. Currently the normal client doesn't have a way to use this. However, you can use the perl script campaign_passphrase.pl to do it, if you have a copy of the source tree.

* Request
** '''[change_passphrase]'''
*** ''name'' - The name of campaign.
*** ''passphrase'' - The old passphrase.
*** ''new_passphrase'' - The new passphrase.
* Respose
** '''[message]'''
*** ''message'' - Translatable string that says that the passphrase was changed.

== Deleting a Campaign ==

This command is used to delete an existing campaign from the campaign server.

* Request
** '''[delete]'''
*** ''name'' - The name of the campaign to delete.
*** ''passphrase'' - This must match the passphrase on record for the campaign in order for the campaign to be deleted.
* Response
** '''[message]'''
*** ''message'' - Translatable string that says that the campaign was deleted.

== Request License Information ==

Retrieve the terms of the license used for any uploaded campaigns. You may not upload a campaign if you don't (or can't) aggree to the license. Wesnoth requires campaigns (including images and sound) to be licensed under the GPL.

* Request
** '''[request_terms]'''
* Response
** '''[message]'''
*** ''message'' - translatable string containing the text of the license.

== See Also ==

* [[UserScenarios#Campaign_Server_Web_Access]]
* [[PblWML]]
* [[BuildingCampaignsThePBLFile]]

CampaignSouthGuard

2006-01-21T16:32:42Z

GrabberBot: automated change of forum links

== Translation of The South Guard ==

This is a list of the people currently translating The South Guard into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>gdou</td><td>complete</td></tr>
<tr><td>German (de)</td><td>?</td><td>unknown</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>?</td><td>unknown</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>grzywacz</td><td>in progress</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>?</td><td>unknown</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-The_South_Guard&order=trans Translation stats for The South Guard]

CampaignSeptreOfFire

2006-01-21T16:32:36Z

GrabberBot: automated change of forum links

== Translation of Sceptre of Fire ==
This is a list of the people currently translating Sceptre of Fire into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>Ivanovic</td><td>completed</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>?</td><td>unknown</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>Sanna</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Sceptre_of_Fire&order=trans Translation stats for Sceptre of Fire]

CampaignSavingElensefar

2006-01-21T16:32:23Z

GrabberBot: automated change of forum links

== Translation of Saving Elensefar ==

This is a list of the people currently translating Saving Elensefar into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>Schattenstephan</td><td>work in progress</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>?</td><td>unknown</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>capitol</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Saving_Elensefar&order=trans Translation stats for Saving Elensefar]

CampaignOrcishIncursion

2006-01-21T16:32:18Z

GrabberBot: automated change of forum links

== Translation of Orcish Incursion ==

This is a list of the people currently translating Orcish Incursion into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>work in progress</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>Torangan</td><td>completed</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>RokStar</td><td>completed</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>capitol</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>Pınar</td><td>completed</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Orcish_Incursion&order=trans Translation stats for Orcish Incursion]

CampaignNewThreat

2006-01-21T16:32:09Z

GrabberBot: automated change of forum links

== Translation of A New Threat ==

This is a list of the people currently translating Mage Republic into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>Tux2B</td><td>work in progress</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>Tux2B</td><td>work in progress</td></tr>
<tr><td>German (de)</td><td>?</td><td>unknown</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>?</td><td>unknown</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>Nikita(ILikeProgramming)</td><td>work in progress</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>Unassigned</td><td>stalled</td></tr>
<tr><td>Turkish (tr)</td><td>Pınar</td><td>work in progress</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Dark_Elves&order=trans Translation stats for A New Threat]

CampaignMysteryCampaign

2006-01-21T16:31:57Z

GrabberBot: automated change of forum links

== Translation of Mystery Campaign ==

This is a list of the people currently translating Mystery Campaign into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>Torangan</td><td>completed</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>RokStar</td><td>completed</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>tephlon</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Mystery_Campaign&order=trans Translation stats for Mystery Campaign]

CampaignMageRepublic

2006-01-21T16:31:53Z

GrabberBot: automated change of forum links

== Translation of Mage Republic ==

This is a list of the people currently translating Mage Republic into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>Allefant</td><td>completed</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>RokStar</td><td>completed</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>Nikita(ILikeProgramming)</td><td>completed</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>Sanna</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Mage_Republic&order=trans Translation stats for Mage Republic]

CampaignLiberty

2006-01-21T16:31:51Z

GrabberBot: automated change of forum links

== Translation of Liberty ==

This is a list of the people currently translating Liberty into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>kilder</td><td>completed</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>Maarten</td><td>correction</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>Bertram</td><td>work in progress</td></tr>
<tr><td>German (de)</td><td>Torangan</td><td>completed</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>Americo Iacovizzi (Dark Amex)</td><td>work in progress</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>capitol</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Liberty&order=trans Translation stats for Liberty]

CampaignLegendOfWesmere

2006-01-21T16:31:43Z

GrabberBot: automated change of forum links

== Translation of Legend of Wesmere ==

This is a list of the people currently translating Legend of Wesmere into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>Tux2b</td><td>completed</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>Tux2B</td><td>pause</td></tr>
<tr><td>German (de)</td><td>Torangan</td><td>work in progress</td></tr>
<tr><td>Greek (el_GR)</td><td>santi</td><td>completed</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>?</td><td>unknown</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>Sanna, capitol, tephlon</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Legend_of_Wesmere&order=trans Translation stats for Legend of Wesmere]

CampaignEliador

2006-01-21T16:31:40Z

GrabberBot: automated change of forum links

== Translation of Invasion of Eliador ==

This is a list of the people currently translating Invasion of Eliador into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>?</td><td>unknown</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>?</td><td>unknown</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>capitol</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Eliador&order=trans Translation stats for Invasion of Eliador]

CampaignFlightFreedom

2006-01-21T16:31:38Z

GrabberBot: automated change of forum links

== Translation of Flight to Freedom ==

This is a list of the people currently translating Flight to Freedom into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>The Very Uhu </td><td>completed</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>luciano</td><td>work in progress</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>capitol</td><td>completed</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==

* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Flight_Freedom&order=trans Translation stats for Flight to Freedom]

CampaignBurningSuns

2006-01-21T16:31:17Z

GrabberBot: automated change of forum links

== Translation of Under the Burning Suns ==
This is a list of the people currently translating Under the Burning Suns into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>breversa</td><td>work in progress</td></tr>
<tr><td>German (de)</td><td>Allefant</td><td>work in progress</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>luciano</td><td>work in progress</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>Unassigned</td><td>stalled</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Under_the_Burning_Suns&order=trans Translation stats for Under the Burning Suns]

CampaignNorthernRebirth

2006-01-21T16:31:16Z

GrabberBot: automated change of forum links

== Translation of Northern Rebirth ==

This is a list of the people currently translating Northern Rebirth into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>?</td><td>unknown</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>?</td><td>unknown</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>Belchion</td><td>work in progress</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>?</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>?</td><td>unknown</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>?</td><td>unknown</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>Unassigned</td><td>stalled</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Northern_Rebirth&order=trans Translation stats for Northern Rebirth]

CampaignANewOrder:RussianTranslation

2006-01-21T16:30:57Z

GrabberBot: automated change of forum links

<table style="width: 100%; border: 0; padding: 1em">
<tr>
<td>
This page is created to coordinate work on the russian translation of the campaign [[CampaignANewOrder|"A New Order"]].
</td>
<td>
Страница создана для координации работы над русским переводом кампании [[CampaignANewOrder|"A New Order"]].
</td>
</tr>
</table>

----

== Имена собственные ==

=== Нации и расы ===

; Akladians (нация) : акладианы, акладиан, акладианам, акладиан, акладианами, акладианах. [+] переведено ([[Talk:CampaignANewOrder:RussianTranslation|см. также дискуссию]])
; Akladian (отдельный представитель) : акладиан, акладиана, акладиану, акладиана, акладианом, акладиане. [+] переведено
; Wesnothians (нация) : веснотцы, веснотцев, веснотцам, веснотцев, веснотцами, веснотцах. [+] переведено
; Wesnothian (отдельный представитель) : веснотец, веснотца, веснотцу, веснотца, веснотцем, веснотце. [+] переведено
; Aragwaithi (нация) : арагвейты, арагвейтов, арагвейтам, арагвейтов, арагвейтами, арагвейтах. [?] подстрочник
; Aragwaith (отдельный представитель) : арагвейт, арагвейта, арагвейту, арагвейта, арагвейтом, арагвейте. [?] подстрочник
; Saorduc Saurians : Ящеры Заурдака/Заурдакские ящеры [?] обдумать

=== Имена персонажей ===

; Heinric the Redbeard : Хейнрик Рыжебородый [+] переведено
; Gawen Hagarthen : Гэвен Хагартен [+] переведено
; Haldric : Хальдрик [+] переведено
; Gaumhaldric : Гемхальдрик [+] переведено
; Lady Lorin : Леди Лорин, леди Лорин [+] переведено ([[Talk:CampaignANewOrder:RussianTranslation|см. дискуссию]])
; Reme Carrenemoe : Реме Карренемо [+] переведено
; Raul O Gaeltin : Рауль О'Гэлтин [+] переведено
; Uri van Roe : Ури ван Роэ [+] переведено
; Bor Cryne : Бор Крайн [+] переведено
; Graeme O Borrain : Грэм О'Боррейн [+] переведено
; O-Barnon : О'Барнон [+] переведено
; Hoyre O Barnon : Ойре О'Барнон [+] переведено
; Uruk Maluf : Урук Малуф [+] переведено
; Arlgor Maunarr : Арлгор Маунарр [+] переведено
; Ruvio : Рувио [+] переведено
; Karen : Карен [+] переведено
; Rob Roe : Роб Ро [+] переведено
; Andrey Yaranov : Андрей Яранов [+] переведено
; Reumario : Ромарио [+] переведено
; Oyre Mathauri : Ойре Матаури [+] переведено
; Erart : Эрарт [+] переведено
; Raole Mathauri : Рауль Матаури [+] переведено
; Yarl Urluf : Ярл Урлуф [+] переведено
; Gwidle Turlin : Гвидл Турлин [+] переведено
; Huon Ryedric : Хуон Райдрик [?] выяснить произношение
; Mithrandil : Митрандил [+] переведено
; Elorain : Элорайн [+] переведено
; Baruk Gar : Барук Гар [+] переведено
; Grekulak : Грекулак [+] переведено
; Hans the Ripper : Ганс Потрошитель [+] переведено
; Leif Thrall : Лейф Тралл [+] переведено
; Rouke Rebarnon : Рук Ребарнон [*] вычитывается
; Burass : Бурасс [+] переведено
; Ussuh : Уссух [+] переведено
; Rassum : Рассум [+] переведено
; Bussur : Буссур [+] переведено
; Mal-Ravanal : Мал-Раванал [+] переведено
; Deorien : Деориен [+] переведено

=== Географические названия ===

; Vakladia : Вакладия [+] переведено
; Outlaw Place : Логово разбойников/Лагерь разбойников [*] выбрать вариант
; Vattin : Ваттин [+] переведено
; Gaeltin Hyer : Гэлтин Хаер [+] переведено
; Saoren Duc : Заурин Дак [*] вычитывается
; Freetown : Фритаун [+] переведено
; Raumair : Ромейр [+] переведено
; Forest of Raedwood : Редвудский лес [+] переведено
; Bontom : Бонтом [+] переведено
; Haeltin : Хэлтин [+] переведено
; Ruen : Руэн [+] переведено

== Соединения ==

=== Общие соединения ===

; Akladian Clanmember : Член клана Акладиан
:* название: [?] подстрочник
:* описание: [?] подстрочник
; Akladian Homeguard : Ополченец Акладиан
:* название: [+] переведено
:* описание: [?] подстрочник
; Akladian Shieldguard : Щитоносец Акладиан
:* название: [?] подстрочник
:* описание: [?] подстрочник
; Akladian Protector : Защитник клана Акладиан
:* название: [?] подстрочник
:* описание: [?] подстрочник
; Akladian Chieftain : Глава клана Акладиан
:* название: [+] переведено
:* описание: [?] подстрочник
; Akladian Fastfoot : Адьютант Акладиан ''(Следует из смысла описания соединения. Возможно лучше заменить на "Гвардеец" или "Личная гвардия". По смыслу ближе всего "вестовой" или "денщик", но как-то несолидно для элитного соединения третьего уровня :) )''
:* название: [?] подстрочник
:* описание: [?] подстрочник
; Akladian Wiseman : Знахарь Акладиан
:* название: [+] переведено
:* описание: [?] подстрочник
; Akladian Leader : Командир Акладиан ''(возможно всё-таки "лидер", но пока логичней кажется "командир")''
:* название: [?] подстрочник
:* описание: [?] подстрочник
; Akladian Sturmknight : Штурмовик Акладиан ''(кажется кривоватым, но альтернативы пока в голову не приходят)''
:* название: [?] подстрочник
:* описание: [?] подстрочник
; Akladian Raider : Охотник за добычей Акладиан (жутко криво, но "рейдер" очень не хочется)
:* название: [?] подстрочник
:* описание: [?] подстрочник
; Henchman : Шестёрка (потому что так и есть :) )
:* название: [+] переведено
:* описание: [?] подстрочник
; Akladian Princess : Принцесса Акладиан
:* название: [+] переведено
:* описание: [+] отсутствует в оригинале

=== Уникальные персонажи ===

; Young Hagarthen : Юный Хагартен
:* название: [+] переведено
:* описание: [?] подстрочник
; Hagarthen : Хагартен
:* название: [+] переведено
:* описание: [+] переведено
; Lord Hagarthen : Лорд Хагартен
:* название: [+] переведено
:* описание: [-] не переведено
; Akladian Lady : Акладианская леди/Леди Акладиан/Дама Акладиан
:* название: [?] подстрочник
:* описание: [?] подстрочник
; Akladian Queen : Королева Акладиан
:* название: [+] переведено
:* описание: [?] подстрочник
; Ruvio : Рувио
:* название: [+] переведено
:* описание: [?] подстрочник
; Ruvious Daughter : Дочь Рувио
:* название: [+] переведено
:* описание: [?] подстрочник
; City Militia : Городской стражник ''(Уникальный или нет, не знаю. Ещё не доиграл :) )''
:* название: [+] переведено
:* описание: [?] подстрочник

== Сценарии ==

=== A New Order ===

Новый порядок

* название: [+] переведено
* описание: [+] переведено

=== Breaking the Circle ===

Прорыв кольца

* название: [+] переведено
* вступление: [+] переведено
* диалоги: [+] переведены

=== Fighting for pass ===

Проход с боем

* название: [+] переведено
* вступление: [*] вычитывается
* диалоги: [*] вычитываются

=== Conversation ===

Переговоры

* название: [+] переведено
* вступление: [*] вычитывается
* диалоги: [*] вычитываются

=== Battle of Barnon ===

Битва при Барноне

* название: [+] переведено
* вступление: [*] вычитывается
* диалоги: [*] вычитываются

=== Unexpected guests ===

Незваные гости

* название: [+] переведено
* вступление: [+] переведено
* диалоги: [*] вычитываются

=== The swamp things ===

Болотные создания/Болотные жители/Болотные твари

* название: [?] подстрочник
* вступление: [?] подстрочник
* диалоги: [?] подстрочник

=== Separation ===

Расставание

* название: [+] переведено
* вступление: [*] вычитывается
* диалоги: [*] вычитываются

=== Ally from the past ===

Союзник из прошлого/Забытый союзник

* название: [?] подстрочник
* вступление: [+] переведено
* диалоги: [*] вычитываются

=== Outlow Base ===

Логово разбойников

* название: [+] переведено
* вступление: [+] переведено
* диалоги: [*] вычитываются

=== Hired swords ===

Наёмные мечи/Наёмное оружие/Купленные мечи/Оплаченное оружие/Клинки по найму/Оружие по найму (зависит от перевода финала вступления)

* название: [?] подстрочник
* вступление: [?] подстрочник
* диалоги: [-] частично - подстрочник

=== Siege of Haeltin ===

Осада Хэлтина

* название: [+] переведено
* вступление: [?] подстрочник
* диалоги: [?] подстрочник

=== Council in Freetown ===

Совет во Фритауне/Фритаунский совет

* название: [?] подстрочник
* вступление: [?] подстрочник
* диалоги: [-] не переведены

=== Leaving Raedwood ===

Покидая Редвуд/Уход из Редвуда/Выход из Редвуда

* название: [?] подумаю
* вступление: [+] переведено
* диалоги: [*] вычитываются

=== Scouting ===

Разведка

* название: [+] переведено
* вступление:
** из Фритауна [?] подстрочник
** из Руэна [?] подстрочник
** из Хэлтина [?] подстрочник
** из Барнона [?] подстрочник; уточнить финал
** из Заурдака [-] не переведено
* диалоги: [?] подстрочник

=== Avenging Ruen ===

Месть за Руэн

* название: [+] переведено
* вступление: [?] подстрочник
* диалоги: [?] подстрочник

=== She-wolf of Haeltin ===

Хэлтинская Волчица

* название: [+] переведено
* вступление: [?] подстрочник
* диалоги: [?] подстрочник

=== Bontom ===

Бонтом

* название: [+] переведено
* вступление: [*] вычитывается
* диалоги: [-] не переведены

=== Saorduc Swamps ===

Заурдакские болота

* название: [?] подстрочник
* вступление: [?] подстрочник
* диалоги: [-] не переведены

=== Back in Freetown ===

Возвращение во Фритаун

* название: [*] вычитывается
* вступление: [?] подстрочник
* диалоги: [-] не переведены

=== The Preparations ===

Приготовления

* название: [?] подстрочник
* вступление: [-] не переведено
* диалоги: [-] не переведены

=== Repelling the Orcs ===

Отпор оркам

* название: [?] подстрочник
* вступление: [-] не переведено
* диалоги: [-] не переведены

== Замечания о переводе ==

# "My lord" в обращениях - "Милорд"

== Спорные переводы ==

Обсуждение вариантов &mdash; на [[Talk:CampaignANewOrder:RussianTranslation#.D0.A2.D1.80.D1.83.D0.B4.D0.BD.D0.BE.D1.81.D1.82.D0.B8_.D0.BF.D0.B5.D1.80.D0.B5.D0.B2.D0.BE.D0.B4.D0.B0_:.3E|странице дискуссии]]

; Underlings : Дикари
; recoinessance : рекогносцировка
; ... You know, da bosses. : ... Ну, к боссам. Понимаешь?
; sietches : шатры
; Мy lady : Моя госпожа/Миледи ???

== Вероятные ошибки в движке кампании ==

# Был креш во время призыва капитана в начале Leaving Raedwood. Разобраться.
# В допросе пропускаются реплики потрошителя.
#* Пофиксил. Отправить баг-репорт.

== Ссылки по теме ==

* [[CampaignANewOrder|Страница кампании "A New Order"]]
* [http://www.wesnoth.org/forum/viewtopic.php?t=6486 Обсуждение кампании в форуме]
* [[RussianTranslation|Страница команды русского перевода "Битвы за Веснот"]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-A_New_Order&order=trans Статистика переводов кампании "A New Order"]
* [https://developer.berlios.de/projects/wescamp-i18n Проект перевода кампаний "Битвы за Веснот" на berlios.de]

== Переводчики ==

[[User:Alxrem|Alexey Remizov]]

CampaignDelfadorsMemoirs

2006-01-21T16:30:32Z

GrabberBot: automated change of forum links

== New maintainer ==
Josh Parsons hasn't active for a long time, so I've been nominated (by myself) to be a new maintainer of the campaign. Currently I'm working on internationalized version, so, translators, you are welcome now. In few days a i18n version will be on the server.

Oto '[[User:Tapik|tapik]]' Buchta

== Translation of Delfador's Memoirs ==

This is a list of the people currently translating Delfador's Memoirs into different languages:

<table border="1" style="width:65%">
<tr><th>Language</th><th>Translator</th><th>Status</th></tr>
<tr><td>Afrikaans (af)</td><td>?</td><td>unknown</td></tr>
<tr><td>Brazilian Portuguese (pt_BR)</td><td>?</td><td>unknown</td></tr>
<tr><td>British English (en_GB)</td><td>?</td><td>unknown</td></tr>
<tr><td>Bulgarian (bg)</td><td>?</td><td>unknown</td></tr>
<tr><td>Catalan (ca)</td><td>Azazelo</td><td>work in progress</td></tr>
<tr><td>Chinese (zh_CN)</td><td>?</td><td>unknown</td></tr>
<tr><td>Czech (cs)</td><td>[[User:Tapik|tapik]]</td><td>completed</td></tr>
<tr><td>Danish (da)</td><td>?</td><td>unknown</td></tr>
<tr><td>Dutch (nl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Estonian (et)</td><td>?</td><td>unknown</td></tr>
<tr><td>Finnish (fi)</td><td>?</td><td>unknown</td></tr>
<tr><td>French (fr)</td><td>?</td><td>unknown</td></tr>
<tr><td>German (de)</td><td>schmidta</td><td>correction</td></tr>
<tr><td>Greek (el_GR)</td><td>?</td><td>unknown</td></tr>
<tr><td>Hungarian (hu)</td><td>[[HungarianTranslation|Műhelyben]]</td><td>unknown</td></tr>
<tr><td>Italian (it)</td><td>RokStar</td><td>work in progress</td></tr>
<tr><td>Japanese (ja)</td><td>?</td><td>unknown</td></tr>
<tr><td>Latin (la)</td><td>?</td><td>unknown</td></tr>
<tr><td>Norwegian (no)</td><td>?</td><td>unknown</td></tr>
<tr><td>Polish (pl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Russian (ru)</td><td>Nikita(I[[LikeProgramming]])</td><td>in progress</td></tr>
<tr><td>Serbian (sr)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovak (sk)</td><td>?</td><td>unknown</td></tr>
<tr><td>Slovenian (sl)</td><td>?</td><td>unknown</td></tr>
<tr><td>Spanish (es)</td><td>?</td><td>unknown</td></tr>
<tr><td>Swedish (sv)</td><td>Sanna</td><td>work in progress</td></tr>
<tr><td>Turkish (tr)</td><td>?</td><td>unknown</td></tr>
</table>

== Status Descriptions ==
* '''unknown'''

It is not known if someone is actually translating this campaign.
* '''work in progress'''

Someone is working on it, but it is not done, yet.
* '''correction'''

Translation is already completed, but it is being corrected at the moment.
* '''completed'''

It is already completed and updated when there are changes.
* '''completed (not active)'''

It is already completed and but not updated when there are changes.

== See Also ==

* [[WesCamp]]
* [http://pulsar.unizar.es/~isaac/wesnoth-gettext/westats/index.php?package=wesnoth-Delfardors_Memoirs&order=trans Translation stats for Delfaldors Memoirs]

BuildingUnits

2006-01-21T16:30:12Z

GrabberBot: automated change of forum links

Making new units is fairly easy. Unit configuration files are plain text files that you can edit with any editor such as Notepad, TextEdit, gedit, pico, vi, emacs, etc. You will need to become familiar with [[UnitWML|WML]] in order to make a new unit. This page contains a more in-depth discussion of Unit WML syntax and will walk you through the creation of a new unit and discuss how you can use it in-game.

== Recommended procedure ==
The easiest way to make a new unit is to copy and paste an existing unit, then modify it. Navigate to the game's data/units directory and copy any unit. When you are editing the unit, attention to detail is key. If you forget to modify each key (for example, the unique id key), problems will result.

== Using your new unit ==
Any unit in the game's ./data/units directory or ''userdata''/data/units will be recognized by the game. However, just because you made a new unit does NOT mean you can use it in game yet. Each scenario and multiplayer era has a specific recruit list. If your unit is not on the list, you can't use it. This means you need to modify the ''recruit='' key in the appropriate configuration file. [[BuildingMultiplayer]] describes different ways you do this for multiplayer. To add a unit to a campaign, read about scenarios, sides, and recruit lists in [[BuildingScenarios]].

== Distributing your unit ==
If you made a single unit, post it on the [http://www.wesnoth.org/forum forum]. If you made a whole group of units, you can make them into a multiplayer faction or you can upload a unit pack.

If you want to make a faction, follow the instructions in the [[BuildingFactions]] article. You should create a new era and add your units as one of the factions. You will not be able to add your units to any era that ships with the game.

If you want to make a unit pack, the procedure is easier. Unit packs are distributed for campaign writers who want to use your units in their campaigns/eras. They download your unit pack and copy/paste the units and images into their campaign/era.
* Navigate to the ''userdata''/data/campaigns directory. Everything from now on will occur relative to here. The era we'll use as an example will be called MyUnitPack
* Create a text file called MyUnitPack.cfg. Add the following lines:
# #define USE_MYUNITS #<- replace MYUNITS with something descriptive
# #enddef
# #ifdef USE_MYUNITS #<- replace MYUNITS with something descriptive
# {@campaigns/MyUnitPack/}
# #endif
:* These lines are commented out (with the #). That way when the unit pack ships it won't affect the game. If someone wants the game to be able to see these units, he can uncomment those lines and it will work. However, this usually causes problems in multiplayer (you will be using units no one else has), but it can be fun for campaigns.
:* NOTE: the commenting/uncommenting trick will only work if the units branch off of an existing unit. Custom L1 units will NOT show up in game automatically without editing another configuration file somewhere (scenario config file or multiplayer.cfg)
* Create another text file called MyUnitPack.pbl. (See [[PblWML]] for more details about *.pbl files.) Add the following lines to it:
author="''your name''"
icon="''any image file in the game's ./images directory''"
version="1.0"
title="My Awesome Unit Pack"
description="New race of lizard men."
* Create a folder called MyUnitPack. Navigate to it.
* Create two subdirectories: units and images. Place your unit cfg files and artwork into those subdirectories
* Create a text file called MyUnitPack.cfg (or another name of your choosing). Add the following lines:
[binary_path]
path=data/campaigns/MyUnitPack
[/binary_path]
[+units]
{@campaigns/MyUnitPack/units}
[/units]
* You should be ready to distribute your unit pack on the campaign server now
* PLEASE change the names to something unique before you publish

== Unit WML discussion ==
Units are enclosed in '''[unit]''' tags.
The first attribute of a unit is the ''id'' key, which is a unique identifier for the unit. As value of the ''type'' attribute for these units, the ''id'' key is used. (See [[BuildingScenarios]]).
It also has a ''name'' key, which is the (translatable) name of the unit, and is displayed on the Status Table when a unit of this type is selected.

The ''race'' and ''gender'' keys indicate what kind of names and traits units of this type should have.
Races are specified by the '''[race]''' tag, and the common set is found in '''data/game.cfg'''.
Values for ''gender'' are ''male'' and ''female'' (Default is ''male'').

The next attributes are ''image'', ''image_defensive'', and ''profile''.
These are the images of the unit when it is resting, defending, and talking, respectively.
The default for the keys ''image_defensive'' and ''profile'' is the value for ''image''.

Next is the ''ability'' key.
This is a list of strings which are listed as the abilities of the unit.
The following strings give the unit an ability:

* illuminates: Units surrounding this unit recieve 25% lawful bonus.
* leadership: Units surrounding this unit recieve a 25% times the level difference between them and the highest level adjacent leader on the same side, bonus to damage. Only units that are higher level than the unit involved in combat provide a bonus.
* heals: Units surrounding this unit regenerate 4 HP per turn.
* cures: Units surrounding this unit regenerate as if they were on a villages.
* regenerates: The unit regenerates each turn as if it were on a village.
* teleport: Whenever it is on a village, the unit can use 1 move point to move to any allied village.
* skirmisher: The unit is unaffected by ZoC.
* ambush: The unit becomes invisible on forest.
* nightstalk: The unit becomes invisible during night.

The ''hitpoints'' and ''movement'' keys input numbers.
''hitpoints'' is the amount of HP the unit has, and ''movement'' is the number of move points it receives each turn.

The ''movement_type'' key is a shortcut to information found in game.cfg.
After (or replacing) the ''movement_type'' key, tags can be used to modify the unit's movement.

The '''[movement costs]''' tag has keys equal to the name of the various terrains, and values equal to the number of move points it takes to move onto a tile of that terrain type.

Terrains:

* village
* castle
* grassland
* forest
* tundra
* hills
* mountains
* cave
* cavewall
* sand
* swamp water
* shallow water
* deep water

The '''[defense]''' tag also has keys equal to the name of the various terrains, and values equal to the percent chance the unit has of being hit while on a tile of that terrain type.

The '''[resistance]''' tag has keys equal to attack types, and values equal to the percent damage that the unit takes from attacks of that type. The attack types are:

* blade
* pierce
* impact
* fire
* cold
* holy

The next keys are ''experience'' and ''advanceto''.
''experience'' is the amount of experience the unit needs to advance to the unit with the id specified as value of the ''advanceto'' key.
If ''advanceto'' has multiple entries, the player will choose which unit to advance to.
If ''advanceto=null'', then the unit cannot advance.

The next keys are ''cost'' and ''level''.
''cost'' is how much gold the unit costs to recruit, and ''level'' is the upkeep cost of the unit.
''level'' is also the amount of XP another unit gets for fighting this one, and the multiplier for the amount of XP the other unit gets for killing this one (multiplied with the ''kill_experience'' value set in '''game.cfg''').

The next keys are ''alignment'' and ''usage''.
''alignment'' tells how the unit's damage should be affected by the current time of day (lawful: <better during day>, chaotic: <better during night>, neutral: unaffected by time of day changes).
''usage'' is the AI's interpretation of this unit.
Values are 'fighter', 'scout', 'archer', 'mixed fighter', and 'null' (Default is null).

The last keys are ''unit_description'' and ''get_hit_sound''.
''unit_description'' is the (translatable) text that is displayed in the unit description box.
''get_hit_sound'' is a .wav file in '''sounds/ ''' that is played when the unit is hit.

The '''[death]''' tag is used to specify an animation of the unit dying, and consists of a set of '''[frame]''' tags, which are similar to all animation '''[frame]''' tags (see description of how these are used below), but is used outside an '''[attack]''' tag.

Next are the '''[attack]''' tags.
The ''name'' key is the displayed name of the attack. (Is this not now divided up into ''id'' and ''name'' ??)
The ''name'' key also affects the ''has_weapon'' filter
(See [[BuildingScenariosIntermediate]]).

Next are the ''type'' and ''range'' keys.
''type'' is an attack type.
''range'' is either '''short''' or '''long'''.
'range=short' means melee, 'range=long' means ranged.

The ''special'' key is similar to the ''ability'' key.
The values are:

* backstab: Whenever there is a unit allied with this unit "behind" the unit that this attack attacks, then this attack does +100% damage.
* charge: Whenever the unit attacks with this attack, both it and the unit it attacks do +100% damage.
* drain: The unit gains health (?)% of the time whenever this attack hits.
* first-strike: This attack always strikes first, even if defending
* magical: This attack is guaranteed a 70% chance of hitting.
* marksman: This attack is guaranteed a 60% chance of hitting.
* plague: The unit is copied onto the tile that any unit this attack killed was on.
* poison: All units this attack hits become poisoned.
* slows: All units this attack hits become slowed for 1 turn.
* steadfast: Unit takes half damage when defending.
* stone: Units this attack hits turn into stone (the stoned unit is lost)
* berserk: Combat continues until either the attacked or the defender is killed.

The last keys are ''damage'' and ''number''.
''damage'' is the amount of damage the attack does;
''number'' is the number of times it can try to hit with each attack.

Next are the animation tags (Note: these are inside the '''[attack]''' tags) (Has the set of keys not been extended?).
The '''[frame]''' tag contains the keys ''begin'', ''end'', and ''image''.
''begin'' and ''end'' specify in what period of time the frame should exist.
These times are in milliseconds. 0 is when the attack hits.
The ''image'' key is the unit image to switch to during this time.

The '''[missile_frame]''' tag is like the '''[frame]''' tag,
but ''image'' represents the image of the projectile.
Also ''image_diagonal'' is the image when the attack is not north-south aligned.

The '''[sound]''' tag takes the keys ''time'' (the time to play the sound) and ''sound'' (the sound to play).

== See Also ==

* [[Create]]
* [[EditingWesnoth]]
* [[Creating Unit Art]]
* [[CampaignServerWML]]
* [[PblWML]]
* [[BuildingCampaignsThePBLFile]]
* [[Team_Color_Shifting]]

{{Create}}

BuildingScenariosSamples

2006-01-21T16:29:51Z

GrabberBot: automated change of forum links

This page contains basic examples of WML.
For more examples, you can look at the data of Wesnoth using a text editor.

to flash the screen red for a moment, we might go,

[colour_adjust]
red=200
[/colour_adjust]
[delay]
time=20
[/delay]
[colour_adjust]
red=0
[/colour_adjust]

A unit remarking what a tough fight it was when they kill an Ogre:

[event]
name=die
[filter]
type=Ogre
[/filter]
[message]
id=tough_fight_ogre
speaker=second_unit
message= _ "Whew! That was a tough fight!"
[/message]
[/event]

Konrad remarks that he is scared at the start of a scenario: (Note the difference between the speaker= and the
description= attributes in the two examples).

[event]
name=start
[message]
id=konrad_scared
description=Konrad
message= _ "I feel uneasy about this place"
[/message]
[/event]

A selection of which way they should go at the end of a scenario:

[event]
name=victory
[message]
id=which_way
speaker=narrator
message= _ "Which way do you wish to go?"
[option]
id=go_north
message= _ "North"
[command]
[endlevel]
result=victory
next_scenario="Northern Advance"
[/endlevel]
[/command]
[/option]
[option]
id=go_south
message= _ "South"
[command]
[endlevel]
result=victory
next_scenario="Southern Citadel"
[/endlevel]
[/command]
[/option]
[/message]
[/event]

Suppose you want to make it so that if a certain character, we will call him Fred the Peasant, survives in a certain
scenario, he will leave,
but return in a later scenario. We can do this in the first scenario:

[event]
name=victory
[if]
[have_unit]
description=Fred
[/have_unit]
[then]
[message]
description=Fred
message= _ "I must go now, friends, but will return later!"
[/message]
[kill]
description=Fred
[/kill]
[set_variable]
name=fred_is_alive
value=yes
[/set_variable]
[/then]
[/if]
[/event]

This makes it so that if Fred is alive, he says something, then is removed from the game, and the variable
'fred_is_alive' is set to yes.

In a later scenario, we can use the following code:

[event]
name=turn 7
[if]
[variable]
name=fred_is_alive
equals=yes
[/variable]
[then]
[unit]
type=Peasant
description=Fred
side=1
x=8
y=1
[/unit]
[message]
description=Fred
message= _ "I have returned to aid you friends!"
[/message]
[/then]
[else]
[message]
description=Konrad
message= _ "I wish Fred were still alive. He would know what to do!"
[/message]
[/else]
[/if]
[/event]

If the variable 'fred_is_alive' equals 'yes' then this will create a unit, Fred, a Peasant, at (8,1), and he will give a
greeting message. Otherwise, Konrad will lament Fred being dead.

Suppose the player has just come across some undead, you might like to find if the player has a unit that would truly
hate the undead, and if so, and get it to say something:

[role]
role=undead_hater
type=Mage of Light,Paladin,White Mage
[/role]
[message]
role=undead_hater
message= _ "The foul hordes of the undead approach, this battle will surely be tough!"
[/message]

[teleport]
[filter]
name=Garcimore
[/filter]
x=10
y=20
[/teleport]

== See Also ==
* [[BuildingScenarios]]
* [[UsefulWMLFragments]]

BuildingScenariosSimple

2006-01-21T16:29:50Z

GrabberBot: automated change of forum links

I will show you a very simple scenario file,
then explain each line of it.
This file is not fully functional, but it shows you
the basics needed to describe what this scenario is all about.

[scenario]

id=test-1
next_scenario=test-2

name=A Simple Test Scenario
map_data="{campaigns/Test_Campaign/testmap}{~campaigns/Test_Campaign/testmap}"
turns=20

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

music=wesnoth-1.ogg

[event]
name=prestart
[objectives]
side=1
[objective]
description= _ "Defeat Enemy Leader"
condition=win
[/objective]
[objective]
description= _ "Death of Konrad"
condition=lose
[/objective]
[/objectives]
[/event]

First, every scenario must be enclosed in a tag;
the '''[scenario]''' tag is used for campaign scenarios.
The first set of keys in the scenario tag
describe the very basics of this scenario.
The ''id'' is the computer's name for your scenario,
and is not displayed during the game.
It is neccesary to put this name somewhere else,
such as a campaign tag, as well, in order to actually play the scenario.
Where you put the ID for the scenario
indicates how you would play this scenario in-game.
For example, if your scenario is for a campaign,
you need to list it as the scenario following another scenario in the campaign.

The ''next_scenario'' key lists the scenario
that is played after this one is won,
with units from this scenario available for recall.
The value of this key should be the same
as the value of the '''id''' key in the scenario following it.
If your scenario is not part of a campaign,
putting '''next_scenario=null''' or skipping this line
will cause the "End" screen to be displayed when you win.

The ''name'' key is shown on the introduction screen(which usually contains the
map graphic) before each scenario is played.
It is also the default name for saves on the level.
The next key, ''map_data'', is a link to the map file.
Since we may not know exactly where this campaign will be installed we write
two possible locations of the map data.
The quotes are necessary because Wesnoth map data takes up multiple lines,
so quotes are used instead to determine where the data begins and ends.
The map file must be a valid Wesnoth map file; see [[BuildingMaps]].
Finally, the last key in the top set of keys is ''turns''.
This sets an event on the specified turn causing the player to lose.

The next section is a set of IDs. This section tells the game how a day should
progress. This listing above is the normal day used throughout Wesnoth. If you
want the entire scenario to take place at night, remove all the IDs except for
'''{SECOND_WATCH}'''. This can be useful if you have Konrad
fighting against the Undead and wanted the Undead to have the upper hand the
whole time. Remember though, by setting this to a single ID and not the normal
day listed above, your scenario will effectively be taking place during one day
or night, not many days as the majority currently are.

The ''music'' key is a filename pointing to the music which plays.
This music file must be in the ''music/'' directory and must be in .ogg format.

The next part sets the objectives for the scenario. This is done inside an '''[event]''' tag, and to have the objectives set before the scenario starts, we must specify '''name=prestart'''. Inside the [event] tag, we have an '''[objectives]''' (plural) tag, which contains any number of '''[objective]''' (singular) tags.
For each tag, if ''condition'' is "win", the text of ''description'' will be displayed in green after "Victory" in the Scenario Objectives. If ''condition'' is "lose", the text of ''description'' will be displayed in red after "Defeat" in the Scenario Objectives.

The ' _ ' facilitates translation using Gettext (see [[GetText]]).

Note that ''ANY'' Victory or Defeat objective can be met to win or lose the scenario,
but a single Victory objective may have multiple parts.

So far so good. The last necessary part of a scenario describes what the players (Human and
Computer) start with and can do. Each of the players is described through
the '''[side]''' tag.

.
.
.

[side]
side=1
controller=human
team_name=2

type=Commander
description=Konrad
canrecruit=1

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

{GOLD 100 50 0}
{INCOME 10 5 0}
[/side]

[/scenario]

From the above example above you can see
a sample '''[side]''' for the human player, Konrad.
The first key, ''side'',
is the location where this player starts on the map,
and is also the ID for this side.
It is a number from 1 to 9.
The next key that describes this player is ''controller''.
The possible values are 'human'
and 'ai', with 'ai' as the default.
After this, the ''team_name'' key describes which team the side is on.
In this example Konrad is on team "2", which by default contains side 2.
However, if you change the team_name of side 2,
Konrad will no longer be allied with it.

The next set of keys describe the player's leader.
First we have ''canrecruit''.
This key can be '0' or '1', which is "no" or "yes" respectively.
If you say no, then the player's leader will not be able to recruit.
And if he can't recruit, he's not really a leader, is he?
Any team without a canrecruit=1 unit automatically loses, so be sure to use this key.
The next key, ''type'', is the type of unit the leader will be.
The possible values are listed at [[UnitTables]].
The ''description'' is the name and description of the leader.
All of these keys are ignored for the human player on all campaign scenarios except the first,
since the leader from the previous scenario is used instead.
However, the ''type'' key is still neccesary to prevent the scenario from crashing.

Next we have the '''recruit''' key which is a comma-separated
list of units. The possible values are listed in [[UnitTables]].

The last two things are IDs.
'''{GOLD}''' inputs any 3 positive numbers.
These indicate the amount of money the player will start with.
The first value indicates the value on the EASY difficulty level;
second NORMAL, third HARD.
When this is inside the ''controller=human'' in a campaign file
then the actual gold the player gets will be the maximum of this value,
and the amount of gold the player retained from the previous scenario.
The '''INCOME''' id is similar, but indicates the base income instead of the base gold.
The defaults for each of these values are 100 gold and 2 base income.

Now, to make this scenario playable, we need to make a campaign for it.
This should usually be stored in its own file in '''data/campaigns/'''.
Note: All files, the campaign file and the scenario file, one for each scenario level, must be saved with the ending
.cfg (for example: testcampaign.cfg, level1.cfg).
[campaign]
name= _ "Test Campaign"
first_scenario=test-1
difficulties=EASY,NORMAL,HARD

difficulty_descriptions= _ "&elvish-fighter.png=Easy;*&elvish-hero.png=Medium;&elvish-champion.png=Hard"
icon=elvish-fighter.png
[/campaign]

Campaigns are enclosed in the '''[campaign]''' tag. The first key is ''name'', which is
displayed on the campaign selector box. The second key is ''first_scenario'', which is
the ID of the first scenario of the campaign (Other scenarios are indicated using
''next_scenario'').

The attribute '''difficulties=EASY,NORMAL,HARD'''
tells the computer to give the macro '''EASY''' a value
if the first difficulty choice is chosen,
'''NORMAL''' if the second is chosen, and '''HARD''' if the third is chosen.
The expression '''#ifdef''' can be used later to test these macros.
It is recommended that you do not use any names other than
'''EASY''', '''NORMAL''', and '''HARD''' for your macros,
because if you do then the macros '''{GOLD}''' and '''{INCOME}''' will not work properly.

Two optional keys in '''[campaign]''' are ''difficulty_descriptions'' and ''icon''.
''icon'' has value equal to an image.
''difficulty_descriptions'' must have the same number of inputs as '''difficulties''', most commonly three, separated by
semicolons.
These inputs then map on to the difficulties, so that if you have set difficulties to
"difficulties=EASY,NORMAL,HARD",
the first input will specify the display
on easy, the second on normal and the third (and last) on hard.
Each difficulty display is an '''&''' sign, then the image to display,
then an equals sign, then the text to display.
Place an '''*''' sign before the display which you wish to be default difficulty, and it will be selected when the player
has chosen the campaign.

== See Also ==
* [[BuildingMaps]]
* [[ScenarioWML]]
* [[BuildingScenarios]]

BuildingScenariosIntermediate

2006-01-21T16:29:44Z

GrabberBot: automated change of forum links

<table width=100% border=0>
<tr>
<td>[[BuildingScenarios]]</td>
<td>[[BuildingScenariosWML]]</td>
<td>[[BuildingScenariosSimple]]</td>
<td>[[BuildingScenariosIntermediate]]</td>
<td>[[BuildingScenariosAdvanced]]</td>
</tr><tr>
<td></td>
<td>[[BuildingScenariosComments]]</td>
<td>[[BuildingScenariosSamples]]</td>
<td>[[BuildingScenariosFAQ]]</td>
<td></td>
</tr>
</table>

<<<<<<< [[BuildingScenariosIntermediate]]

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

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

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

Of course, we don't want it to be fired everytime any unit moves anywhere,
so we use the '''[filter]''' tag to filter out the kind of moveto event we want.
Events can be filtered on many different parameters.
Filters are described in [[FilterWML]].

''Special attributes''

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

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

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

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

The event

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

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

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

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

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

[scenario]
.
.
.

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

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

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

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

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

[/scenario]

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

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

[scenario]
.
.
.

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

[/scenario]

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

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

[scenario]
.
.
.

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

[scenario]

FIXME: finish [story]

BuildingScenariosBalancing

2006-01-21T16:29:16Z

GrabberBot: automated change of forum links

I'm writing this wiki article to talk about some things that came up as I was balancing a couple of the scenarios in the
South Guard Campaign. I'm going to
respond to something that PDF wrote but that I think is a pretty common idea. I don't mean to single him out:

PDF wrote:
"Adding a difficulty level does not necessarily requires much balancing;
you can, for example, just add or remove gold."

I'm going to argue that that is fundamentally a flawed way to balance campaigns, and should only be used in conjunction
with other balancing methods.

1. '''Wesnoth scenarios as tactical problems'''

Each scenario in Wesnoth presents a tactical problem. The problem is generally phrased something like this: "Kill the
enemy leader in so much time
while keeping your leader alive." The most common variation is this: "Move your leader to this hex in so much time while
keeping him alive." Of course,
there are subtleties to these tactical problems. Because of the gold bonus you want to finish is less that the stated
time. Because you can recall experienced
and leveled units you want to have units that have gained experience not die. There may be other units that you must
keep alive. There may be certain
units you must kill. At its core, however, each scenario is a relatively simple tactical problem.

2. '''Factors that influence the difficulty of a tactical problem in Wesnoth'''

I am going to briefly list the factors (that I perceive) which affect the difficulty of a tactical problem in Wesnoth.
This list is probably not exhaustive, so if
there's something I've missed, post it and I'll add it to the list. They in no particular order:

a) Terrain
b) Player's starting gold
c) AI's starting gold
d) Player's recriutment list
e) AI's recriutment list
f) Player's recall list
g) Time limitations
h) Size of player's keep
i) Size of AI's keep
j) AI Parameters (more on this in a minute)
k) Distribution of villages
l) Unexpected reinforcements
m) Time of day

Note that the AI's starting gold is one factor among many.

3. '''Varying the difficulty of a tactical problem presented to the player in a scenario'''

Considering the above factors, it is easy (if time consuming for the designer) to present tactical problems of differing
difficulty in a single scenario. For
most of the above factors, I'll give and example and explain in a sentence how if affects the tactical problem:

''a)'' If the map is predominantly a terrain that favors either the player's forces or the ai's forces, it will have a
huge effect on the difficulty of the battle. For example, a player whose units are broadly loyalists will have a
disasterous time trying to root Elves out of woods. The terrain is, however, generally fixed by the nature of the
scenario (i.e. the designer can't really make a whole new map for each difficulty level). I would submit, however, that
80% of the actual
fighting in a typical scenario occurs in less than 10% of the hexes. It is possible to change only one or two hexes and
have a dramatic effect on the outcome of the battle if you can identify those "chokepoint" hexes.

This can either be done my having three different maps (which I suspect is more work) or by using the WML tag [terrain].
For example, the code:

#ifdef EASY
[terrain]
x=4
y=5
letter=n
[/terrain]
#endif

will turn the hex at (4,5) into an encampment.

''b)'' If the player has a lot of gold he can make more tactical mistakes because he can recruit more troops to replace
the ones he's lost. Additionally, quantity has a quality all of its own, so if the player's starting gold is much higher
that the AI's starting gold he can employ a swarm of cheap units. Note that this does not simplify the tactical problem,
it only allows more mistakes to be made.

''c)'' If the AI's starting gold is much higher than the players, the player will be unable to make any tactical
mistakes and still win the scenario. I'll talk more
about this in a moment.

''d)'' If the player can only recruit units that will be effective against the enemy's forces, then the tactical problem
is simplified. If I can only recruit heavy
infantry to face a force of skeleton archers, then I have a less difficult tactical decision to make than if I can
recruit heavy infantry and spearmen. Especially
if I don't know the game well.

''e)'' Restricting the enemy to a certain class of units (i.e. melee-only, ranged-only, impact-attacks-only) can
simplify the tactical problem immensely. Consider an enemy who can only recruit thieves and thugs facing a predominantly
loyalist force, who can recruit Bowmen and Spearmen. Bowmen are very good against thugs and thieves because they have a
strong ranged attack. If the enemy can also recruit poachers and footpads, the tactical problem becomes more difficult
because the player must balance the effectiveness of the Bowmen against the thieves and thugs with their (relative) weakness
against footpads and poachers.

''g)'' The turn limit controls to what extent the player is allowed to waste turns not directly accomplishing his
mission. In the most difficult case scenario, a player must move his leader across the map and only enough turns are
allotted such that if he ever moves in any other direction, time will run out. Elongating the turn limit allows an
inexperienced player to turn-costing make mistakes and still be victorious.

''h&i)'' The size of a player's keep determines at what rate he can recruit troops. The size of the enemy's keep
determines at what rate he can recruit troops. Divide one by the other and you get a relative-recruitment-rate (assuming
both have lots of gold). If the relative recruitment rate favors the player, the tactical problem should be easier
because he can replenish losses more easily than the AI player. If the AI player's keep is larger, then any losses by
the human player will be that much more difficult to replace.

''j)'' The AI parameters are perhaps the best way to alter a tactical problem. [[AiWML]] is a particularly important read
for a scenario designer. I'd draw attention to aggression and [target] in particular. attack_depth is also very nice.
These parameters are especially important for building scenarios with tactical problems that are fundamentally different
from the basic kill-his-leader ones.

''k)'' Using the [terrain] WML tag you can easily alter the distribution of villages in a scenario. Move the
distribution towards the player, and things get easier. Move it towards the enemy, and they get harder.

''l)'' Enemy reinforcements complicate the tactical problem. They are a surprise that you have to figure out how to deal
with after you've deployed your troops. (Which should be possible so the player doesn't just re-play the scenario with
knowledge of the reinforcements.)

''m)'' Time of day is an interesting factor. While you are normally not free to change the cycle, changing when the
cycle starts can be a significant influence, timing when (by ToD) the battle begins. On a large or open battlefield, the
player has more control over that, depending on their skill.

== See Also ==

* [[BuildingScenarios]]
* [[ReferenceWML]]

BuildingScenariosAdvanced

2006-01-21T16:29:09Z

GrabberBot: automated change of forum links

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

.
.
.

[side]
side=2
enemy=1

canrecruit=1

type=Lich
description=Galga

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

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

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

aggression=1.0
village_value=0.0
leader_value=50.0
[/side]

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

If a scenario is meant to be translated, it must have ids
(Editor's Note: For 0.8.3 and later, scenarios no longer need IDs.).
IDs are used to represent text in the scenario.
A translation maps the ID of each text in the scenario to a translation text.

Example:

[message]
message= _ "Where are we? Which way now? I am tired of this darkness!"
description=Konrad
id=hasty_1
[/message]

This is the first message in the scenario "Hasty Alliance". To translate this message into French, we put the key

hasty_1="Où sommes-nous ? Quel chemin devons-nous emprunter maintenant ? Je suis fatigué de cette obscurité !"

in the French translation file and when Wesnoth is played in French this message will be displayed rather than the
original one. The key
== id == should be added to any tag with text that is meant to be translated (remember, the [scenario] tag already has an
id, do not add
another one).

Now you have enough information to make some interesting looking scenarios with tuned AI players.
This is a big step.
Next we are going to learn how to make your newly created scenario fit nicely into a campaign.
This involves making a descriptive intro shown before the scenario is played.
See [[IntroWML]] for a description of the intro screen.

See [[ReferenceWML]] for a more complete description of what WML can do.

== See Also ==
* [[BuildingScenarios]]

BuildingMaps

2006-01-21T16:28:55Z

GrabberBot: automated change of forum links

This is all you need to know about maps:

# A map is just a bunch of letters arranged in a rectangle (the rectangle is known as the "map data")
# There are two ways to save this rectangle in a file

Seriously now, here are the details.

== Wesnoth map data format ==

Map data is used to represent maps in Wesnoth. The encoding for maps has a specific format:

* A map data file consists of any number of lines, each with the same number of characters.
* Each character must be either a letter specified in a ''letter'' key specifying a terrain (see [[TerrainLettersWML]]), or a digit.
* When the file is interpreted, each letter will be replaced by the terrain it refers to.
* Each nonzero digit ''n'' where ''n'' = 1, 2, 3, ... will be replaced by keep, with the leader of side ''n'' placed on the keep.

Since text file tiles are squares while game tiles are hexes, some tiles must be shifted.
Tiles in even-numbered columns are shifted down 1/2 of a tile.
For example, to have a road of connected dirt ('r') tiles, the map data would look like this:

gggrr
grrgg
rgggg

== Creating a map ==

This is not the Matrix. You do not need to look at encoded maps. The source code and most binary distributions come with the official graphical map editor. Using the map editor tends to be straightforward, judging from the feedback received from novice mapmakers. However, if you do encounter problems locating or using the editor, please ask for help on the [http://www.wesnoth.org/forum forum].

After the map is created, you may find it easier to make small tweaks by editing the textual map data directly.

Making good, balanced, interesting maps is another task altogether, and if someone wants to take a stab at sharing insight about this art, please do so.

== Using map data ==

Map data is used in two ways.
# It is used as an input to the key ''map_data'' (see [[ScenarioWML]]).
# Files consisting entirely of map data can be read and edited easily by the [[WesnothMapEditor]].
#* Files in the folder '''''userdata''/editor/maps/''' which consist entirely of map data can be played in multiplayer as user maps.

==== The map_data key ====

The first way is to use the map_data key. A campaign scenario starts with the '''[scenario]''' tag. A multiplayer map scenario starts with the '''[multiplayer]''' tag. Each tag takes the key ''map_data''. The value of the ''map_data'' key is the map data enclosed in quotes. Here is an example:
map_data="rRfRffffffffffffffcgggfffffffhmmhmhmffff
ffRfRffffffffffvfccfgffffmmhffmhXXmmmhff
ffffRRfnngvgffffscfffmfmhmmmmmfmmfmXmhff
gffffn1RgvgggfffscffffmmmfXmmmhXmmmXmhff
gfffnvggRRgfvnffcfffffhmXmmXXXXfXXmmhfff
gffffggggfR2nffccvggfffhmhXfgCgCfmmXmhff
fffffvfgfnnRR\ccffggffffmmXgfC3CgXmfmhff
ffffffvffcc|cfrrccfffffmmmXXfgggfXmhhfff
fffffcfccfcrffgvrrccffffhhmmXXggXmmfmffr
fffccfcffrrggggffrffcfffffmmmhffmfmmfrfr
fccffffrfffffhffrfffccffffffmmfrfmmrrfrf
ccffvffrffffvhhhrhhhffcfffffffffrrrhhfff
fffffffrffffffhhrrhffccffrfffffrrfhfffff
frfffffrrrffffffhrffffwrrfrfrfrfffffffff
rfrrfrffffrrfffffrfffr/wfhffrrfffffgggvf
fvffrffffffrffffffrrrfwwhhfvffrrfffggggf"

==== Standalone map file ====

The second way to store a map is in a text file that consists '''only''' of the map data. The advantage of this method is that it's simple. If you drop one of the map files in '''''userdata''/editor/maps/''', the game will find it automatically in multiplayer. On the other hand, this method also works with more complex scenarios. If there is a scenario file somewhere (campaign or multiplayer) that has a line similar to the following:
map_data="{@editor/''map_filename''}"
then all of the map data in the file is inserted between the quote marks.

== Discussion: Scenario File vs Standalone ==

Campaign writers can't write campaigns without scenarios, so campaigns will always use the ''map_data'' key, either with the raw data in quotes or a preprocessor symbol {} pointing to the standalone file.

Multiplayer mapmakers, however, '''have a choice'''. If you want to place an object or unit on the map, you must create a scenario file starting with the '''[multiplayer]''' tag and containing the ''map_data'' key therein. You lose the simplicity of the standalone map file, but you gain tremendous power. Not only can you add units and objects, you can set allies, experience modifiers, add a map description, and add custom events (among other things). The question, "How do I place an object on the map with the map editor" is such a common question that I am sorry this information is buried so deeply here. But, now that you know you can seek out an example of a multiplayer map scenario file to use as an example. The game comes with many maps of each type.

== See Also ==

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

{{Create}}