The Battle for Wesnoth Wiki - User contributions [en]

BuildingMaps

2009-10-11T04:34:07Z

Mabeenot: updated and expanded

A map is just a bunch of terrain strings arranged in a rectangle (the rectangle is known as the "map data"). There are two ways to use this rectangle in a file: as a stand-alone map or within a scenario. The easiest way to create maps is just to use the built-in editor, but if you want to actually understand how maps work, you should read a little about the map data format. This page explains that format, and then has some pointers about the editor, saving files, and how to play on a map once you've made it. For instructions on how to distribute maps, see [[BuildingMapsDistribution]].

== Creating a map ==

Wesnoth has a fully functional map editor, accessible from within the game. The map editor should be fairly straightforward, however some helpful hotkeys can be found in the [[WesnothMapEditor]] article. Making good, balanced, interesting maps is another task altogether. ESR has addressed it in his [http://catb.org/~esr/wesnoth/campaign-design-howto.html Campaign Design How-To]. If you run into trouble with the map editor, go ahead and ask for help on the [http://www.wesnoth.org/forum/viewforum.php?f=15 Multiplayer Development forum].

If you're a programmer, note that while the source code and most binary distributions come with the official graphical map editor, you may have to give the build system a flag or argument to tell it to compile them as well as the main game.

=== Adding units and map descriptions ===

Campaign writers can't write campaigns without scenarios, so campaigns will always use scenario files. 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. The ''map_data'' key can either point to a standalone map file or include the raw map data in quotes inside the scenario file.

Using scenario files for multiplayer maps, you lose the simplicity of the standalone map file, but you gain tremendous power. With a scenario file, you can add units and objects, include a map description, and set default map settings like allies, starting gold, and experience modifiers. You can even create custom events. Check out [[BuildingScenarios]], [[ScenarioWML]], and [[BuildingMultiplayer]] for more information.

=== Map data format ===

This is not the Matrix. You normally don't need to look at encoded maps. However, if you would like to use some advanced terrain features or create scenarios and campaigns, you'll have to dive into the map code. The encoding for maps has a specific format in Wesnoth:

* A map starts with a header with the following keys
** '''usage''', this should be 'map' for a map and 'mask' for an overlay mask
** '''border_size''', the size of the border, should be 1 for map and 0 for mask. When the border_size is 1 the map border is part of the map data, this means the user can define the border instead of the game taking a guess.
* Between the header and the data should be 1 empty line
* A map data file consists of any number of lines, each with the same number of strings.
* Each string must be a string specified in a ''string'' key specifying a terrain (see [[TerrainLettersWML]]).
* Each string may be padded with spaces or tabs and must be separated with a comma, except for the last string on a line this one may not have a comma.
* When the file is interpreted, each string will be replaced by the terrain it refers to.
* Empty lines are allowed before, after and between lines of characters, between lines is not advised.
* Terrains may be prefixed with a number followed by one space, these indicate the starting position for side ''n''. ''n'' = 1, 2, 3, ... 9 (more might work but is untested and unsupported). This is a change from the previous system where a starting position was automatically a keep.

It's advised to use spaces for padding and pad each column to be the same width; the game does this when writing a map file.

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 ('Re') tiles, the map data would look like this:

usage=map
border_size=1

Re, Re, Gg, Gg, Gg, Gg, Gg, Gg
Gg, Gg, Re, Re, Gg, Gg, Gg, Gg
Gg, Gg, Gg, Gg, Re, Re, Gg, Gg
Gg, Gg, Gg, Gg, Gg, Gg, Re, Re

== So now what? ==

You've created an awesome map with the map editor and you're ready to test it out. But how can you do this? It's actually quite simple.

=== Play your map ===

If you just want to play the map, maybe against the computer or with a friend, all you have to do is save it into the map editor's folder (the default location). Then, when you launch the game and host a multiplayer game, the map should appear '''at the top''' of the map choices screen.

When creating a game on the multiplayer server, your map will be described to other players as a "Use Map" and any replays stored on the server will refer to the game as "Use Map."

For the curious: Saving a map file like this creates a stand-alone file that holds the map data. That file is by default saved in '''''userdata''/editor/maps/''', and maps in that location are added to the top of the multiplayer map selection list.

=== Share your map ===

When you're ready to share your map with the world, post it to the [http://www.wesnoth.org/forum/viewforum.php?f=15 Multiplayer Development forum] or package it to be distributed on the in-game add-ons server. For instructions on how to distribute maps, see [[BuildingMapsDistribution]]

== See Also ==

* [[WesnothMapEditor]]
* [[TerrainCodesWML]]
* [[ScenarioWML]]
* [[ReferenceWML]]

{{Create}}

BulgarianTranslation

2009-10-09T04:59:04Z

Mabeenot: undo spam by CnacoBooud

WesnothPhilosophy

2009-10-09T04:57:04Z

Mabeenot: undo spam by Letoc4tdro

== The History of, and Philosophy behind Wesnoth (2003 original) ==

The 18th of December 2003 marked six months since the first version of Battle for Wesnoth, version 0.1, was released.

I feel it is appropriate to respond to something Bazarov said in another thread:

<blockquote>am having a little difficulty understanding the core values of the game in the eyes of the creators. I think having an established, ordered list of these would help a lot in my attempts to help. A white paper of sorts. I don't think this should be done by voting, either; a clear, concise vision would be nice. Where does originality factor in? I, too, felt that the game's focus was on the units rather than the strategy, that the building of my colourful army was more important than the logic of any scenario.</blockquote>

We talk about the 'KISS [1] principle' here a lot, and I think that that is the most core
design principle used in Wesnoth. It was the key principle that enabled Wesnoth
to get off the ground, and it is the principle that has kept it alive since.

First of all, the concept of 'KISS' is a software development principle.
Not a game-design principle. The idea of game rules being simple is not
necessarily a bad one, and can be linked to KISS in that game rules
that are simple to implement are often ones that most players would
consider 'simple'. However simple game rules are not directly related
to KISS, as many people on the forum mistakenly seem to have thought.

When I was a teenager, I attempted to write games several times.
Some of them were playable, even impressive - especially considering
my resources and skill - but none of them were professional, and polished.
When I showed them to people, they would be impressed, and say
"this looks good", but I knew that none of them would actually want to take
the game home and play it for themselves.

My programming skills back then left alot of room for improvement.
I had a basic, self-taught knowledge of C and C++.
Then I went to college, and after that got a job programming,
where my skills improved immensely.

In some of my spare time, I decided to try writing a game again.
What kind of game? Well, I was confident of my skills,
so I would write a complex game, using all the latest programming tools.

I wanted to write a Civilization-like game, but with some major rule changes,
and a better AI. I had thought up sophisticated systems for everything.
The result? It failed before it even got started, collapsing in a mountain of
complexity.

I gave up on writing a game for a long time after that.
I was busy with other things anyhow. But then one day, I played
a game that I had played when I was much younger, a Genesis game:
Master of Monsters. It was fun, lots of fun, yet it was simple.
Simple enough that I was confident I could program a game like it easily enough.

I had analyzed that most Free games fall into one of two categories:
they are either boringly trivial, or they are insanely complex,
and never really get off the ground. I decided I would claim the middle ground:
make it simple enough to write, but substantial enough to be lots of fun.
It wouldn't be as ambitious as some things I wanted to write, but at
least it would work.

But, I don't see the point of writing a Free game which is simply
a copy of a commercial game. My aim would be to write
something new, something better, something which borrows the best ideas
from a number of other games, and which adds new ideas of its own.

The idea of KISS is that the feature must be easy enough to program
that before the programmer starts working on it, they have a very clear
and strong understanding of how they're going to make it work.
Not a 'yes I can do this but it is kinda complicated'.
Rather they should be thinking 'this is so stupid and simple that it's
really really easy for me to do'. So I decided on a simple rule for the
game: a feature would be added only if I knew immediately how to implement it.
I wouldn't make vague promises to myself about features that would be later added,
but which I had no idea how to do.

I started with a few basic units, and two races: Orcs and Elves.
Elves had horsemen, which could advance to knights, archers which
could advance to rangers, and fighters which could advance to heroes.

I considered different systems of advancement. Even considering
something which keeps track of the activity the unit undergoes,
and advances it in that area, but I rejected such a system for
something simple, something similiar to Master
of Monsters with the added choice of letting the player
choose what their unit advances into at some points.

The focus would be around building your own army, and watching
it grow as its members became more experienced.
You would only have basic control over the advancement of
a particular member of the army, but you would decide what units go
into the army.

I also fleshed out a very basic interface. There would be only a few commands:
to move a unit, and to attack with that unit, as well as to recruit and
recall units. I added in unit skills, which was something Master of Monsters
didn't have, but I made the skills occur implicitly -- healing would be
dispensed to all units around a specific unit for instance.

Obviously, Wesnoth is a fantasy game, so it contains some implication of
spells/magic, however I have always disliked games that got deep
into sophisticated systems of spells.

In Wesnoth, wars would be decided with sword and bow.
Mages would be involved too, of course, but warfare was to be
about guiding troops around strategically, not about which spell
to cast and where. So, from the beginning I decided
that all spells would be implicit, or simply a type of attack.

This was a big divergence from Master of Monsters where
one spell could be cast every turn by each master at any place
on the battlefield. That was, in my opinion, one of the game's
worst features - if your enemy had advanced a unit on
the other side of the map, you could try to kill him with a spell.

I also made the combat very simple. An example of this is the
way in which the chance to hit is calculated. I'm
wondering how many people know how the chance to hit is calculated
in Wesnoth? I thought it was alot more complex in
Master of Monsters until I studied how they did it.

What I suspect most people would immediately consider for a
chance-to-hit system would be a formula that relies on the
attacker's skill with the weapon, and the defender's defensiveness,
as well as the terrain the defender is in.

The way Wesnoth does it is in fact so insanely simple that
I suspect many people who did not know how it is done will
think 'what a naive, silly system!' when they read the following:

<blockquote>The chance to hit is taken entirely from the defender's defensive rating in the terrain it is in.</blockquote>

So, there is always 30% chance to hit Elves in forest,
and 60% chance to hit them in grassland. The attacker's skill doesn't come
into the equation.

I decided it would add interesting strategy, though, if just
a very few weapons had a special attribute that would
guarantee them a certain chance to hit. I decided that was
an appropriate thing for magic, to differentiate it: so, I
decided that magic attacks would always have 70% chance to hit.

For all my efforts though, and for all the people who say that
graphics are of little importance or unimportant, I don't
think that Wesnoth would have gotten anywhere if fmunoz hadn't
seen it, and drawn some very good graphics for it. The
graphics I had drawn were pathetic, but he drew some nice ones,
and added the undead and later humans to the game, as
well as doing some scenarios, and adding some very good ideas to the game.

I think it's important for us to remember the KISS principle
as development continues. Remember: Wesnoth has not reached
1.0 yet. It's not a finished work. It could still fail.
Let's make it easy for it to succeed by keeping everything simple.

Oh and how did I come up with the name 'Wesnoth'?
It was late at night, and I wanted to release version 0.1.
I muttered syllables to myself, until I came up with a pair
that sounded halfway reasonable: 'Wesnoth'.

David

[1] Keep It Simple, Stupid

== More on the KISS principle ==

The reason behind the KISS principle is fairly straightforward:
often programmers will be confronted with someone -
perhaps a user, perhaps a designer, perhaps themselves -
who wants them to implement something to work in a certain way.
Oftentimes the programmer can only just work their head around
all the requirements, and when they start implementing the feature,
they don't have a clear idea of how the entire feature
is to be implemented, because it's so complicated.

Such a situation inevitably leads to low-quality and very buggy software.

KISS intentionally has the 'stupid' part, because often
'architecture astronauts' as they're known come up with 'super
elegant generic designs' that to them are simple, and most
importantly, elegant. Elegance is nice, but in a real-world
situation, it doesn't defeat KISS. Without the 'stupid' part
in there, some people would claim that elegance and
simplicity are strongly related, and so their 'elegant'
design should be implemented.

But no, it doesn't matter how elegant it is. If the coder can't
understand exactly how to do it, it's not KISS. A less
elegant design, one that is simple and stupid, should be used instead.

So that's it I guess: if the implementer finds it very very easy
to do, then it's KISS. If they don't, it's not.

This can be related back to game rules somewhat. One of the aims
of Wesnoth was to make a game with a pretty good AI.
One of the things I noticed about other games, was that they added
in alot of game rules that their users wanted, which
were very very difficult for the AIs of those games to use or understand.

So, I decided I'd make a game where the rules were detailed
enough to be fun, but structured in a way that the AI can work with them.

I think that's the best definition of KISS for game rules that
we will find: if it's very easy to implement, including
making the AI use the rules effectively, then it's KISS.

This makes most but not all of our current game rules KISS.
In particular, special abilities involving auras
(leadership, healing, illumination) are not currently used at all
effectively by the AI. It might not be so complicated
for the AI to be able to use them though.

Things like skirmish are very KISS, since the AI immediately
understands how to use it effectively.

You'll note that originally, when Wesnoth consisted of
no multiplayer, and no campaigns other than Heir to the Throne,
it was structured so the AI would only control units that it can
use effectively: it didn't have access to any aura
effects, while it did have access to things like poison.

This is the cornerstone of KISS: what is laughably easy for
a programmer to do is going to result in high quality,
bug-free software. What is 'simple' for users, or 'elegant'
for designers, but not easy for a programmer is not going
to result in high quality software.

David

== Wesnoth Philosophy II: Where Next? (2008) ==

We had a section in here on where to take Wesnoth next, but it was written before 1.0 was released. That would make it rather out of date.

Eric Raymond has pressured me to update this section. Interestingly, much of the above was based on some of Eric Raymond's writings.

So, we are about to release Wesnoth 1.4. 1.4 will be a very solid, stable release, with an impressive list of features. Some people claimed that Wesnoth wasn't really ready for a 1.0 label back when we released 1.0. Any concerns that Wesnoth is not a stable, mature game should have been removed by 1.2 though, and certainly should be crushed by 1.4. The team has done an excellent job of building a very impressive product.

Where to now? Onward and upward, of course! We already have a great game, and around that great game has developed a great community. Using the resources we now have available, we can continue to improve the game to be better and better. To make it more fun, faster, run on more platforms, more reliable, and support a wider variety of game elements.

Of all suggestions to improve -- or perhaps I should say change -- Wesnoth, one of the most common, and certainly the most controversial, is to alter the gameplay in some way. To add a new gameplay feature, to add new unit special abilities, to alter unit stats, and so on and so forth. Are we planning to continue to make gameplay changes, and of what nature? Should we radically alter the game?

We have a great game, that people enjoy. We don't plan to radically alter the core game mechanics. We will continue to tweak things of course -- and our gameplay balance developers have done an excellent job of balancing things out, and will continue to do so. The core game mechanics will remain the same. What we might do, however, is add a wider variety of feature support to the engine, to support more different user made campaigns and scenarios.

A key part of Wesnoth's success is in keeping an open mind. No single developer, least of all me, has been able to consistently and accurately predict what is fun and what isn't. Instead, by developing a flexible platform that allows people to develop scenarios and campaigns on, users can make content which proves to be fun, or not. Our community has done an excellent job of creating fun content that I never imagined possible.

We want to continue doing this. We want to make our engine more and more flexible, little by little. We want to take 'fringe elements' -- dramatically different gameplay styles that were only supportable by bizarre and convoluted WML -- and make the engine support them better.

We have many plans for a variety of features to allow this. A better WML engine. A more flexible AI engine that will allow much greater customization.

However, the core Wesnoth team does not intend to migrate Wesnoth to a fundamentally different play stle. But, that said, I think it would be a great idea for *someone* to. We have an excellent set of resources: great art, a good code base, and so forth. These resources could be re-used to make a 'civilization-style' hex game. Or a 'tactics' game (Wesnoth is already somewhat of a tactics game, but one could take this in different directions). Or more of a 'wargame'. For someone to do this would be excellent. If another great FLOSS game could be created with Wesnoth's resources, that would be great for the FLOSS gaming community. I, personally, would love to play such a game. :)

Something else we want to address going forward is Wesnoth's performance. Wesnoth was originally created using an approach that was easy to develop with, but placed performance, in terms of time and space, as a secondary concern. It is still easily runnable on most desktop machines, but it doesn't run well on smaller devices. We have several developers who are highly committed to making Wesnoth run well on small devices. We plan to work hard on this, and make this happen.

Finally, I think the best thing about Wesnoth is its community. I feel we should continue to foster and grow the community. We have recently had a "Wesnoth Conference" at FOSDEM, which ten Wesnoth developers and contributors attended. It would be excellent if we could organize such a thing again, perhaps on a larger scale.

That said, I personally feel that attempting to raise money to fund such a thing is entirely within the spirit of the FLOSS community. We could, for instance, consider using (unintrusive) ads on our website to raise money, and then organize a conference, funding it with the money (including paying subsidies to anyone wanting to come, to help pay for their expenses).

I must admit, that even after Wesnoth got 'off the ground', I was at times concerned about its chances of reaching a credible 1.0. Later I was concerned about its direction thereafter, especially with me becoming less involved with the project. I have been incredibly impressed by the development team and the community which has done an excellent job in developing Wesnoth. I am now very confident in Wesnoth's future.

== See Also ==
* [[FrequentlyProposedIdeas]]
* [http://www.wesnoth.org/forum/viewtopic.php?t=441 The History of, and Philosophy behind Wesnoth]
* [http://www.wesnoth.org/forum/viewtopic.php?t=2190 Wesnoth Philosophy II: Where Next? (2004)]

[[Category:Historical]]
[[Category:Future]]

CampaignBurningSuns:RussianTranslation

2009-10-09T04:55:33Z

Mabeenot: undo spam by TreraLdomt

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

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

=== Under the Burning Suns ===

Под палящими светилами

* Название: [*] вычитывается
* Описание: [*] вычитывается

=== The morning after ===

На следующее утро

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

=== Across the Harsh Sands ===

По суровым пескам

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

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

; Central Body : Главное тело
:* Название [-] не переведено
:* Описание [-] не переведено
; Weakened Central Body :
:* Название [-] не переведено
:* Описание [-] не переведено
; Crawling Horror : Ползучий ужас
:* Название [*] вычитывается
:* Описание [-] не переведено
; Pulsing Spire : Пульсирующий шпиль
:* Название [-] не переведено
:* Описание [-] не переведено
; Giant Ant : Гигантский муравей
:* Название [*] вычитывается
:* Описание [-] не переведено
; Confused Ant :
:* Название [-] не переведено
:* Описание [-] не переведено
; Corrupted Elf :
:* Название [-] не переведено
:* Описание [-] не переведено
; Crab Man :
:* Название [-] не переведено
:* Описание [-] не переведено
; Dawarf : Даварф
:* Название [-] не переведено
:* Описание [-] не переведено
; Dark Assassin :
:* Название [-] не переведено
:* Описание [-] не переведено
; Uncloaked Assassin :
:* Название [-] не переведено
:* Описание [-] не переведено
; Desert Archer : Пустынный лучник
:* Название [+] переведено
:* Описание [-] не переведено
; Desert Avenger : Пустынный мститель
:* Название [+] переведено
:* Описание [-] не переведено
; Desert Captain : Пустынный капитан
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Champion : Пустынный защитник
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Druid : Пустынный друид
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Fighter : Пустынный боец
:* Название [+] переведено
:* Описание [-] не переведено
; Desert Hero : Пустынный герой
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Horseman : Пустынный конник
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Marksman : Пустынный снайпер
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Marshal : Пустынный маршал
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Outrider : Пустынный наездник
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Ranger : Пустынный странник
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Rider : Пустынный всадник
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Scout : Пустынный разведчик
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Shaman : Пустынный шаман
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Sharpshooter : Пустынный снайпер
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Shyde :
:* Название [-] не переведено
:* Описание [-] не переведено
; Desert Star :
:* Название [-] не переведено
:* Описание [-] не переведено
; Desert Hunter : Пустынный охотник
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Sentinel : Пустынный страж
:* Название [*] вычитывается
:* Описание [-] не переведено
; Desert Prowler : Пустынный бродяга
:* Название [*] вычитывается
:* Описание [-] не переведено
; Deep One : Глубинная тварь
:* Название [*] вычитывается
:* Описание [-] не переведено
; Dread Bat :
:* Название [-] не переведено
:* Описание [-] не переведено
; Dwarvish Explorer : Гном-исследователь
:* Название [-] не переведено
:* Описание [-] не переведено
; Dwarvish Pathfinder : Гном-следопыт
:* Название [-] не переведено
:* Описание [-] не переведено
; Dwarvish Scout : Гном-разведчик
:* Название [-] не переведено
:* Описание [-] не переведено
; Flesh Golem : Голем из плоти
:* Название [-] не переведено
:* Описание [-] не переведено
; Giant Tentacle :
:* Название [-] не переведено
:* Описание [-] не переведено
; Troll : Тролль
:* Название [*] вычитывается
:* Описание [-] не переведено
; Troll Warrior :
:* Название [-] не переведено
:* Описание [-] не переведено
; Haunt :
:* Название [-] не переведено
:* Описание [-] не переведено
; Ixthala Demon :
:* Название [-] не переведено
:* Описание [-] не переведено
; Fire Guardian : Огненный страж
:* Название [-] не переведено
:* Описание [-] не переведено
; Dwarvish Sentinel : Гном-страж
:* Название [-] не переведено
:* Описание [-] не переведено
; Dwarvish Stalwart :
:* Название [-] не переведено
:* Описание [-] не переведено
; Small Mudcrawler : Маленькое грязевое чудище
:* Название [-] не переведено
:* Описание [-] не переведено
; Spider Lich : Паук-лич
:* Название [-] не переведено
:* Описание [-] не переведено
; Troll Shaman : Тролль-шаман
:* Название [-] не переведено
:* Описание [-] не переведено
; Troll Zombie : Тролль-зомби
:* Название [-] не переведено
:* Описание [-] не переведено
; Skeleton Rider : Скелет-всадник
:* Название [-] не переведено
:* Описание [-] не переведено
; Water Serpent :
:* Название [-] не переведено
:* Описание [-] не переведено

=== Вооружение и боевые способности ===

; energy ray : энергетический луч
; cold : холод
; magical : магический
; fangs : клыки
; blade : клинок
; sword : меч
; magic : магия
; claws : когти
; fist : кулак
; impact : толчок
; dagger : кинжал
; darts : дротики
; poison : яд
; tentacle : щупальца
; ink : тушь
; pierce : укол
; bow : лук
; backstab : бьет в спину
; ambush : засада
; leadership : лидерство
; cures : лечение
; staff : посох
; ensnare : ловушка
; slow : замедление
; thorns : колючки
; bola : болас
; longbow : большой лук
; marksman : меткость
; skirmisher : застрельщик
; heals : исцеление
; entangle : запутывание
; faerie touch : волшебное касание
; illuminates,cures : освещение,лечение
; drain : истощение
; axe : топор
; smashing frenzy : сокрушающее безумие
; berserk : берсерк
; regenerates : восстановление
; club : дубина/дубинка
; mace : булава
; touch : касание
; wail : вопль
; flaming sword : пылающий (пламенеющий?/а мне нравится пламенный) меч
; fire : огонь
; fire claws : огненные когти
; fire breath : огненное дыхание
; skash : удар сплеча
; steadfast : устойчивость
; spear : копьё
; mud glob : комок грязи
; plague : чума

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

=== Персонажи ===

; Quenoth : Квенот
; Kaleh : Кале (м)
; Sela : Сэла (ж)
; Naia : Найя (ж)
; Tanuil : Тануил (м)
; Eloh : Эло (ж)
; Nym : Ним (ж)
; Garak : Гарак (м)
; Zhul : Жул (ж)
; Vecnu : Векну
; Uria : Урия
; Eranor : Эранор (м)
; Xanthos : Ксантос (м)
; Nisa : Ниса (ж)
; Yasi : Яси
; Nary : Нару (м)
; Pythos : Пайтос (м)
; Jokli : Джокли
; Thorn : Торн
; Elyssa : Элисса (ж)
; Go-Hag : Го-Хаг (м)
; Vengeful Lord : Мстительный лорд [?] подстрочник

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

; Pinnacle Rock : Каменный Шпиль

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

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

[[Category:Translations]]

Description

2009-10-08T01:07:33Z

Mabeenot: updated pics

== 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-1.6-4.jpg http://www.wesnoth.org/images/sshots/wesnoth-1.6-4-175.jpg]
<div class="thumbcaption">Delfador's magical lightning strike</div></div>
</div>

<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-1.6-5.jpg http://www.wesnoth.org/images/sshots/wesnoth-1.6-5-175.jpg]
<div class="thumbcaption">An ambush in a campaign</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.

Wesnoth has many different sagas waiting to be played out. Fight to regain the throne of Wesnoth, of which you are the legitimate heir... step into the boots of a young officer sent to guard a not-so-sleepy frontier outpost... vanquish a horde of undead warriors unleashed by a foul necromancer, who also happens to have taken your brother hostage... guide a band of elvish survivors in an epic quest to find a new home.

200+ unit types. 16 races. 6 major factions. Hundreds of years of history. The world of Wesnoth is absolutely huge and limited only by your creativity - make your own custom units, compose your own maps, and write your own scenarios or even full-blown campaigns. You can also challenge up to 8 friends - or strangers - and fight in epic ''multi-player'' fantasy battles.

== Features ==

<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-1.6-2.jpg http://www.wesnoth.org/images/sshots/wesnoth-1.6-2-175.jpg]
<div class="thumbcaption">The map editor</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 – 35 different languages currently available.
* Windows, Mac OS X, GNU/Linux, RISC OS, BeOS, Solaris, FreeBSD, OpenBSD, NetBSD, DragonFly BSD, AmigaOS4, OS/2 & eComStation compatible.

{{Play}}

GettingStarted

2009-10-08T00:58:33Z

Mabeenot: updated pic

{| style="float:right;"
|
__TOC__
|}
The Battle for Wesnoth is a turn-based strategy game with a fantasy theme.

''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 in epic ''multi-player'' fantasy battles.

=== Welcome to Wesnoth ===
==== The Land of Wesnoth ====
The Land of Wesnoth is generally divided into three areas: the northlands, which are generally lawless; the kingdom of Wesnoth and its occasional principality, Elensefar; and the domain of the Southwest Elves.

The Kingdom of Wesnoth lies in the center of the land. Its borders are the Great River to the north, the Lower Hills in the east and south, the Green Swamp to the southwest, and the Ocean to the west. Elensefar, a once-province of Wesnoth, is bordered by the Great River to the north, a loosely defined line with Wesnoth to the east, the Bay of Pearls to the south, and the ocean to the west. There is no government of the Northlands. Various groups of orcs, dwarves, barbarians and even elves populate the region. The northern and eastern borders are not defined, the southern border is the Great River, and the western border is the Ocean.

As you travel around the land you will encounter peaceful villages where you can heal your troops and obtain a good income to support your army. You will also have to cross mountains and rivers, either on foot or mounted, push through forests, hills and tundra, or brazenly cross open grassland. In each of these areas different creatures have adapted to live there and can travel more easily and fight better when they are in familiar terrain. In the hills, mountains and underground caves orcs and dwarves are most at home. In the forests the elves reign supreme while in the oceans and rivers mermen and nagas control the waves.

==== The Creatures of Wesnoth ====

The world of Wesnoth contains several [[races]] that have joined forces into different factions. Here, Elves and Dwarves fight side by side against Orcs and Humans. In most campaigns, you will mostly control units from one faction, but often you will have a recruit list with units mixed in from other factions, and will not have some units from a faction available. Basically, your recruit list is determined by the plot of the campaign, not by a predetermined ruleset.

Sometimes factions make alliances with others, so you may face more than one faction in a scenario.

=== Finding Your Way Around Battle For Wesnoth ===
<div class="thumb tright"><div>
[http://upload.wikimedia.org/wikipedia/commons/a/a8/The_Battle_for_Wesnoth-Title_Screen.png http://upload.wikimedia.org/wikipedia/commons/thumb/a/a8/The_Battle_for_Wesnoth-Title_Screen.png/250px-The_Battle_for_Wesnoth-Title_Screen.png]
<div class="thumbcaption"><div align="center">The Main Menu<br>(Click to enlarge)</div></div></div>
</div>
When Wesnoth first starts it displays an initial background and a column of buttons called the Main Menu. The buttons only work with a mouse. For the impatient, we recommend you: click the 'Language' button to set your language; then click the 'Tutorial' button to run the tutorial; and then play the campaign, 'The Two Brothers' by clicking the 'Campaign' button and selecting it from the list provided.

The Main Menu buttons are:

*Tutorial
:The tutorial is a real, but basic, game which teaches you some of the basic controls needed to play the game. Winning or losing is not important here, but learning what to do is. Click the Tutorial button to play. In the Tutorial you are in the role of the young prince Konrad or princess Li'sar, learning from the Elder Mage Delfador - pay attention or he might turn you into a newt.

*Campaign
:Wesnoth was primarily designed to play campaigns. Campaigns are a series of connected scenarios. Click this button to start a new campaign. You will be presented with a list of campaigns available on your computer (more can be downloaded if you wish). Select your campaign and click OK to start or Cancel to quit.

:Each campaign has a difficulty level: easy, medium (normal), and hard. Some have an extra setting, 'nightmare'. We recommend medium as this level is challenging, but not difficult. You may not change the difficulty during the campaign. In case you have serious problems fighting your way through easy difficulty, the guide about [[BasicStrategy]] will surely help you. Once you have selected the difficulty, you will start with the first scenario of the campaign. A good campaign to start with is the Heir to The Throne. It is not too difficult on easy, but gets challenging later on. You can find walkthroughs or descriptions of the available campaigns at:

::* [[MainlineCampaigns]]
::* [[UserCampaigns]]
::* [[BeginnerCampaigns]]

*Multiplayer
:Click this button to play single scenarios against one or more opponents. You can play the games over the internet or at your computer, against computer or human opponents. When you select this button a dialogue will appear and allow you to choose how you want to play the scenario. To learn more, see [[#Multiplayer|Multiplayer]].

*Load
:Click this button to load a previously saved game. You will be shown a dialogue listing saved games. Select the game and click Ok to load and continue, or Cancel to return to the Main Menu.

:If you select a replay game, you can check the Replay check box. The loaded game will make all the moves from the beginning while you watch.

*Language
:Click this button, select your language, and click OK to use it, or Cancel to continue with the current language. The first time Wesnoth starts, it defaults to English, but once you change it, it will start in that language.

*Preferences

:Click here to change default settings. These are explained in more detail in [[PlayingBattleForWesnoth#Preferences|the Manual]].

*About
:Click this button for a list of major Wesnoth contributors. You may find most of them at irc.freenode.org:6667 on #wesnoth. Or visit http://www.wesnoth.org for news, forums, and Wiki updates. The project is hosted on https://gna.org/projects/wesnoth, where you can download the latest production or developer release, review and report problems (bugs).

*Quit
:Click this button to close Wesnoth.

This getting started guide provides a basic introduction to Battle for Wesnoth. You can find more details about playing the game in the [[WesnothManual|Manual]].

=== Play a Game ===
There are two basic ways to play Battle for Wesnoth:
*Play a sequence of connected scenarios, known as a campaign, against the computer (Campaign)
*Play a single scenario against computer or human opponents (Multiplayer)
(Note: The development of multiplayer campaigns is currently underway).

==== Campaigns ====
Campaigns can take a long time to complete. Typical campaigns have about 10-20 scenarios. The main advantage with campaigns is that they allow you to develop your army. As you complete each scenario, the remaining units at the end are saved for you to use in the next scenario. If you choose not to use a unit at all during a scenario it is carried over to the next, so you don't lose units you don't use.

The campaign is the primary form in which Wesnoth is intended to be played, and is the recommended way for new players to learn the game. Some Official campaigns also describe the history of Wesnoth as scenarios are completed.

==== Multiplayer ====
Multiplayer games are played with or against other players, which may be human or AI-controlled. There are 4 major options: 1) Join official server, 2) Connect to host/server, 3) Host networked game, 4) Local game.

By selecting this option, you may play either competitive games or cooperative games. Competitive games include 1 vs 1's , 2 vs 2's or even free-for-alls (FFA's). Cooperative games or scenarios include survivals and other user made scenarios, which may include RPG elements or other elements which are not present in campaigns or competitive games. In general, cooperative scenarios require downloading from the Wesnoth Add-On Server. In all games, you have the option of assigning any sides control by the AI.

Multiplayer games can take anywhere from 1 hour to 10 hours (or more, for very rare map settings), depending on how many players there are (and the size of the map). The average time is between 3 to 7 hours. Games can be saved and loaded as many times as you like. So, it's possible for some games to last 1 or 2 weeks, even though the play time is only a few hours. You cannot carry over units in multiplayer from one scenario to the next, so building up your army's strength is possible only within the scenario.

===== Join Official Server =====
By selecting this option, you will be connected to the official Wesnoth server via the Internet. This option will allow you to play with other players from around the world.

===== Connect to Host/Server =====
This option allows you to connect to other computers or servers, including the official Wesnoth server. You may use this option to join a multiplayer game via a local access network (LAN).

===== Host Networked Game =====
This option allows you to create a game that can be joined by other players via a LAN network.

===== Local Game =====
This option allows you to play a game involving 1 computer only. You may still assign control for other sides to other players/AI.

=== The Game Screen ===

Regardless of whether you are playing a scenario or a campaign, the basic layout of the game screen is the same. The majority of the screen is filled with a map which shows all of the action that takes place in the game. Around the map are various elements which provide useful information about the game and are described in more detail below.

Across the top of the screen from left to right are the following items:
#Menu button
#Actions button
#Turn counter *
#Your gold
#Your total villages
#Your total units
#Your upkeep
#Your income
#Timer or clock
#Current hex type
#Current hex position

Down the right of the screen from top to bottom are:
#Full map, scaled *
#Time of day indicator
#Unit profile for last selected unit*
#End Turn button *

(Items marked with a * are currently undocumented)

*Menu button: Displays a drop-down menu with the following options:

#Scenario Objectives: Lists the victory and defeat conditions.
#Statistics
#Unit List: Lists your active units, including their map position.
#Status Table: Summary list of visible player units, villages, income etc.
#Save Game: Write the current game position to disk.
#Load Game
#Preferences: see [[PlayingBattleForWesnoth#Preferences|the Manual]] for details.
#Back to: Return to previous turns without opening the Load Game dialog. Not available in all games.
#Help
#Quit Game: Close the game, without saving, and return to the Main menu.

*Actions button: Displays a drop-down menu with the following options:
#Next unit
#Recruit: Lists units your commander can recruit from a keep.
#Recall (Campaign only): Lists units your commander can recall from a keep.
#Show enemy moves
#Best possible enemy moves
#End Turn: On your turn, select it to end your turn.

*Your gold, villages, units, upkeep, and income
:Quick way to check how your army is doing. A negative income means you'll lose gold, a positive means you gain gold. Upkeep is the gold you pay your units. Villages shows how many you own, each village will give you Gold.

*Current hex
:Shows the terrain type and position of the hex pointed to by the mouse. If a unit is on the hex, its resistance on that terrain is shown after the position. The position is in column, row order.

*Time of day indicator
:Putting your mouse over the indicator will bring up a tooltip showing the effect of the time of day. Wesnoth has a 6-turn day and different alignments have bonuses depending on the time of day.

==== Recruit and Recall ====
When you first start a scenario or campaign you will only have a few units on the map. One of these will be your commander (identified by a little crown icon). Your commander is usually placed in a castle on a special hex called a keep. Whenever your commander is on a keep (not only your own, but also the keep of any enemy castles you capture) and you have enough gold, you can recruit units for your army. In later scenarios you can recall experienced units that survived earlier scenarios. From here, you can start to build your army to conquer the enemy.

The first thing you will probably want to do is recruit your first unit. Press 'ctrl-r' (or right click on an empty castle hex and select 'recruit') and you will be able to recruit a unit from a list of all the units available to you. Each recruit is placed on an empty castle square. Once you have filled the castle, you cannot recruit any more until units move off. Your opponent's commander is similarly placed on its castle keep and will begin by recruiting its troops -- so don't dilly-dally looking at the scenery, there's a battle to be won.

At the end of each successful scenario, all your remaining troops are
automatically saved. At the start of the next scenario you may
recall them in a similar way to recruiting. Recalled troops are often more
experienced than recruits and usually a better choice.

==== Your Army ====

All game types use the same soldiers, called units. Each unit is identified
by Race, Level, and Class. Each unit has strengths and weaknesses,
based on their Resistance, current Terrain, and Level.
See http://units.wesnoth.org/

==== Life and Death - Experience ====

As your troops gain battle experience, they will learn more skills and
become stronger. They will also die in battle, so you'll need to
recruit and recall more when that happens. But choose wisely, for each has
strengths and weaknesses a cunning opponent will quickly exploit.

==== Money ====
Your army does not fight for free. It costs you money to recruit units and money to maintain them. You start each scenario with money carried over from previous scenarios (although each scenario ensures you have at least a minimum amount of gold to start if you didn't carry over enough from previous scenarios) and can gain more by meeting scenario objectives quickly and, during a scenario, by controlling villages. Each village you control will give you two gold pieces income per turn. When you first start a scenario it is usually worthwhile to gain control of as many villages as you can to ensure you have sufficient income to wage war. You can see your current gold and current income at the top of the screen as described in the section on [[#The_Game_Screen|the Game Screen]]. More information can be found in [[PlayingBattleForWesnoth#Gold|the manual]].

==== Save and Load ====
At the start of each scenario, you have the option to save it.
If you are defeated, you may load it and try again. Once you have succeeded,
you will again be asked to save the next scenario and play that.
If you have to stop playing during a scenario, you can save your turn
and load it again later. Just remember, a good BFW player never needs to
save '''during''' a scenario. However, most beginners tend to do so rather
often. ;)

=== Getting the Most Fun Out of the Game ===

Remember, the idea of a game is to have fun! Here are some recommendations
from the development team on how to get the most fun out of the game:

* Consider playing the campaign on 'Medium' difficulty level, especially if you have prior experience with strategy games. We feel you'll find it much more rewarding.
* Don't sweat it too much when you lose some units. The campaign was designed to accommodate the player losing some units along the way.
* Don't abuse saved games. Long ago, Wesnoth only allowed saving the game at the end of a scenario. Mid-scenario saving was added as a convenience to use if you had to continue the game another day, or to protect against crashes. We do not recommend loading mid-scenario saved games over and over because your White Mage keeps getting killed. Learn to protect your White Mage instead, and balance risks! That is part of the strategy.
* If you must load a saved game, we recommend going back to the start of the scenario, so that you choose a new strategy that works, rather than simply finding random numbers that favor you.
* But remember, the aim is to have fun! You may have different tastes than the developers, so do what you enjoy most! If you enjoy loading the saved game every time you make a mistake, looking for the 'perfect' game where you never lose a unit, by all means, go right ahead!

==== At the start of a scenario ====
* First, read the scenario objectives. Sometimes you do not have to kill enemy leaders; instead it is enough that you survive for a certain number of turns, or pick up a particular object
* Look at the map: the terrain, the position of your leader and the other leader(s).
* Then, begin to recruit units. Cheap units are useful to soak up the first wave of an enemy's attack; advanced units can then be brought in as support. Fast units can be used as scouts, for exploring the map and to quickly conquer villages.

==== During the scenario ====
* Try to capture and keep control of as many villages as possible to keep the gold coming in
* Keep units in packs so the enemy cannot attack from as many sides, and so you can outnumber each enemy unit. Put your units in a line so that the enemy cannot attack any one of your units from more than two sides.
* Different units have different strengths and weaknesses depending on terrain and who they are attacking; right click on units and select "Describe unit" to learn more
* You can use lower level units as cannon fodder, to slow down enemy. e.g. you can use them to block enemy reaching your important units
* You can cause damage to enemies with advanced units and then finish them with lower level units - to give them more experience (and finally make them advance to next level)
* When you have a White Mage (advances from Mage) or Druid (advances from Shaman), put it in the middle of a circle of units to heal them as they move across the map (Shamans can do this too, but not as well)
* Losing units is expected, even advanced units
* Time of day really matters:
** lawful units do more damage at day and less damage at night
** chaotic units do more damage at night and less damage at day
** remember to always check the time of day on the right side of the screen. Plan ahead - think about what it's going to be next turn as well as this turn.
* Some units are resistant or vulnerable to different kind of attacks. Mounted units are weak vs pierce attacks. Fire and holy (arcane) attacks destroy undead. To see how much a unit resists an attack type, right click on the unit, select 'Unit Description', then select 'Resistance'. It will show you how resistant a unit is to different types of attacks.

==== Healing ====
An important part of succeeding at Battle for Wesnoth is keeping your units healthy. When your units take damage you can heal them by moving them onto villages or next to special healing units (e.g. the Elvish Shaman and White Mage). Some other units you will encounter, such as Trolls, have the ability to heal themselves naturally. You can find more detailed information about healing in [[PlayingBattleForWesnoth#Healing|Chapter 2]].

==== Winning a scenario ====
* Advanced units are needed to quickly kill enemy commanders, and to avoid losing lots of units.
* The quicker you win a scenario, the more gold you get; you will get more gold from winning early than from all of the map's villages for the rest of the turns.
* Killing all enemy leaders usually gives instant victory.

==== More general tips ====
* After slaughtering scenarios (where you take lots of punishment) there are usually "breathing room" scenarios where you can rather easily gain some gold and experience (advanced units)
* Advanced units have higher upkeep than lower level units (1 gp per level), loyal units are an exception.

<noinclude>

=== See Also ===
* [[WesnothManual]]
* [[AdvancedTactics]]
* [[MP_Tutorial]] learn how to play multiplayer games.

{{Play}}
</noinclude>

Distributing content

2009-10-08T00:34:16Z

Mabeenot:

== The Forum ==

The [http://www.wesnoth.org/forum/ BFW forum] is a good way to distribute small creations, like single multiplayer maps. Larger creations, like multiplayer eras or campaigns, should be compressed before uploading them. Note that you may encounter a size limit on attachments.

Also, there is a [http://www.wesnoth.org/forum/viewtopic.php?t=2014 legal announcement] that you should read before distributing anything on the forum. Basically, by posting you say that you own the license to what you are posting, and that you are licensing it under the [http://www.gnu.org/copyleft/gpl.html General Public License].

== The Add-on Server ==

The add-on server is the preferred way to distribute your creations, but it is more suited for larger projects. It currently lacks advanced organization features such as filtering and reviewing, so adding hundreds of little things makes it harder to find anything. Basically, the server should not be used to post single maps, units, songs, or artwork, but map packs, campaigns, entire eras, music packs, and unit packs are fine.

Once you are ready to publish, here is how you access the add-on server:
# Open Wesnoth
# Select "Add-ons" from the main menu
# Connect to the default ''campaigns.wesnoth.org'' add-on server
# Select "Publish Add-on: ''Your Add-on Name''" (the last entry in the list of campaigns)

Anything you distribute on the server will be uploaded from and downloaded to the ''userdata''/data/campaigns directory regardless of what it is (units, maps, campaign, etc). For this reason, you need three things in the campaigns directory to distribute via the server:
# A folder, for example MyCampaign
# A .cfg file MyCampaign/_main.cfg
# A .pbl file MyCampaign/_server.pbl
Note that only the contents of your add-on directory (in this case, MyCampaign) will get uploaded, nothing else, so you need to have all the necessary files inside that directory.

==== General Reading ====
* [[BuildingCampaignsThePBLFile|General information about the .pbl file]] - It has a campaign flavor, but it is adaptable to any content
* [[PblWML|Syntax reference for the .pbl file]]

==== Content-specific instructions ====
* Maps - see [[BuildingMaps|Building Maps]]
** [[BuildingMapsDistribution|About distributing map-packs]]
* Campaign - see [[BuildingCampaigns|Building Campaigns]]
** [[BuildingCampaignsDistribution|About distributing campaigns]]
* Multiplayer era - see [[BuildingFactions#Adding_a_whole_new_era_with_its_own_factions_-_modular|Building MP Era]]
* Unit pack - see [[BuildingUnits#Distributing_your_unit|Building Units]]

==== License ====
You should note that by uploading anything to the campaign server, you say that you own the license to all content in your upload and that it is under the GPL. Whenever you upload or update your content pack, you will have to say "OK" to this statement: "All campaigns uploaded to this server must be licensed under the terms of the GNU General Public License (GPL). By uploading content to this server, you certify that you have the right to placethe content under the conditions of the GPL, and choose to do so."

== See Also ==

* [[Create]]
* [[BuildingMapsDistribution]]
* [[BuildingCampaignsDistribution]]
* [[BuildingCampaignsThePBLFile]]
* [[PblWML]]
* [[IGNFileFormat]]
* [[Wesnoth:Copyrights]]

[[Category:Create]]

BuildingMaps

2009-10-07T23:58:48Z

Mabeenot: /* See Also */

A map is just a bunch of terrain strings arranged in a rectangle (the rectangle is known as the "map data"). There are two ways to use this rectangle in a file: as a stand-alone map, or within a scenario. The easiest way to create maps is just to use the built-in editor, but if you want to actually understand how maps work, you should read a little about the map data format. This page explains that format, and then has some pointers about the editor, saving files, and how to play on a map once you've made it.

== Wesnoth map data format ==

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

* A map starts with a header with the following keys
** usage, this is map for a 'map' and 'mask' for an overlay mask
** border_size, the size of the border, should be 1 for map and 0 for mask. When the border_size is 1 the map border is part of the map data, this means the user can define the border instead of the game taking a guess.
* Between the header and the data should be 1 empty line
* A map data file consists of any number of lines, each with the same number of strings.
* Each string must be a string specified in a ''string'' key specifying a terrain (see [[TerrainLettersWML]]).
* Each string may be padded with spaces or tabs and must be separated with a comma, except for the last string on a line this one may not have a comma.
* When the file is interpreted, each string will be replaced by the terrain it refers to.
* Empty lines are allowed before, after and between lines of characters, between lines is not advised.
* Terrains may be prefixed with a number followed by one space, these indicate the starting position for side ''n''. ''n'' = 1, 2, 3, ... 9 (more might work but is untested and unsupported). This is a change from the previous system where a starting position was automatically a keep.

It's advised to use spaces for padding and pad each column to be the same width; the game does this when writing a map file.

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 ('Re') tiles, the map data would look like this:

usage=map
border_size=1

Re, Re, Gg, Gg, Gg, Gg, Gg, Gg
Gg, Gg, Re, Re, Gg, Gg, Gg, Gg
Gg, Gg, Gg, Gg, Re, Re, Gg, Gg
Gg, Gg, Gg, Gg, Gg, Gg, Re, Re

== Creating a map ==

This is not the Matrix. You do not need to look at encoded maps. Wesnoth has a fully functional map editor, accessible from within the game. The map editor should be fairly straightforward, although if you run into trouble, go ahead and ask for help on the [http://www.wesnoth.org/forum forum].

Making good, balanced, interesting maps is another task altogether. ESR has addressed it in his [http://catb.org/~esr/wesnoth/campaign-design-howto.html Campaign Design How-To]

If you're a programmer, note that while the source code and most binary distributions come with the official graphical map editor, you may have to give the build system a flag or argument to tell it to compile them as well as the main game.

== So now what? ==

You've created an awesome map with the [[WesnothMapEditor]] and you're ready to test it out. But how can you do this? It's actually quite simple.

==== Stand-alone maps ====

If you just want to play the map, maybe against the computer or with a friend, all you have to do is save it into your custom maps folder (the default location). Then, when you launch the game and host a multiplayer game, the map should appear at the top of the map choices dialog.

For the curious: Saving a map file like this creates a stand-alone file that holds the map data. That file is by default saved in '''''userdata''/editor/maps/''', and maps in that location are added to the top of the multiplayer map selection list.

==== The map_data key ====

There's another way to use map data. The data for the map can be placed directly inside of a ''map_data'' tag in a '''[scenario]''' tag (see [[ScenarioWML]]). An example of map data encoded directly in a file might look like this:
map_data="border_size=1
usage=map

Gg, Ke, Gg, Gg
Gg, Ce, Ce, Gg"

Keep in mind that it's almost always more useful to have a separate map file that you reference in a scenario than putting the data directly into the scenario (not least because the editor works on such separate map files). To use a saved map file in a campaign, you have to include the map data like this:

map_data="{@editor/''map_filename''}"

Note that @editor here means that the map should be found in the '''''userdata''/editor/maps/''' directory. You need to specify something else if your map is in another location (for example, in a campaign, the maps should go into their own folder). The [[ScenarioWML]], [[BuildingCampaignsTheCampaignFile]] and [[PreprocessorRef]] pages all contain more detailed information about how this works.

==== Share your map ====

When you're ready to share your map with the world, post if to the forum or package it to be distributed on the in-game add-ons server. For instructions on how to distribute maps, see [[BuildingMapsDistribution]]

== 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. Check out [[BuildingMultiplayer]] for more information.

== See Also ==

* [[BuildingMapsDistribution]]
* [[WesnothMapEditor]]
* [[ScenarioWML]]
* [[ReferenceWML]]
* [[BuildingScenariosShroudData]]
* [[TerrainCodesWML]]

{{Create}}

BuildingMaps

2009-10-07T23:56:54Z

Mabeenot: /* So now what? */

A map is just a bunch of terrain strings arranged in a rectangle (the rectangle is known as the "map data"). There are two ways to use this rectangle in a file: as a stand-alone map, or within a scenario. The easiest way to create maps is just to use the built-in editor, but if you want to actually understand how maps work, you should read a little about the map data format. This page explains that format, and then has some pointers about the editor, saving files, and how to play on a map once you've made it.

== Wesnoth map data format ==

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

* A map starts with a header with the following keys
** usage, this is map for a 'map' and 'mask' for an overlay mask
** border_size, the size of the border, should be 1 for map and 0 for mask. When the border_size is 1 the map border is part of the map data, this means the user can define the border instead of the game taking a guess.
* Between the header and the data should be 1 empty line
* A map data file consists of any number of lines, each with the same number of strings.
* Each string must be a string specified in a ''string'' key specifying a terrain (see [[TerrainLettersWML]]).
* Each string may be padded with spaces or tabs and must be separated with a comma, except for the last string on a line this one may not have a comma.
* When the file is interpreted, each string will be replaced by the terrain it refers to.
* Empty lines are allowed before, after and between lines of characters, between lines is not advised.
* Terrains may be prefixed with a number followed by one space, these indicate the starting position for side ''n''. ''n'' = 1, 2, 3, ... 9 (more might work but is untested and unsupported). This is a change from the previous system where a starting position was automatically a keep.

It's advised to use spaces for padding and pad each column to be the same width; the game does this when writing a map file.

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 ('Re') tiles, the map data would look like this:

usage=map
border_size=1

Re, Re, Gg, Gg, Gg, Gg, Gg, Gg
Gg, Gg, Re, Re, Gg, Gg, Gg, Gg
Gg, Gg, Gg, Gg, Re, Re, Gg, Gg
Gg, Gg, Gg, Gg, Gg, Gg, Re, Re

== Creating a map ==

This is not the Matrix. You do not need to look at encoded maps. Wesnoth has a fully functional map editor, accessible from within the game. The map editor should be fairly straightforward, although if you run into trouble, go ahead and ask for help on the [http://www.wesnoth.org/forum forum].

Making good, balanced, interesting maps is another task altogether. ESR has addressed it in his [http://catb.org/~esr/wesnoth/campaign-design-howto.html Campaign Design How-To]

If you're a programmer, note that while the source code and most binary distributions come with the official graphical map editor, you may have to give the build system a flag or argument to tell it to compile them as well as the main game.

== So now what? ==

You've created an awesome map with the [[WesnothMapEditor]] and you're ready to test it out. But how can you do this? It's actually quite simple.

==== Stand-alone maps ====

If you just want to play the map, maybe against the computer or with a friend, all you have to do is save it into your custom maps folder (the default location). Then, when you launch the game and host a multiplayer game, the map should appear at the top of the map choices dialog.

For the curious: Saving a map file like this creates a stand-alone file that holds the map data. That file is by default saved in '''''userdata''/editor/maps/''', and maps in that location are added to the top of the multiplayer map selection list.

==== The map_data key ====

There's another way to use map data. The data for the map can be placed directly inside of a ''map_data'' tag in a '''[scenario]''' tag (see [[ScenarioWML]]). An example of map data encoded directly in a file might look like this:
map_data="border_size=1
usage=map

Gg, Ke, Gg, Gg
Gg, Ce, Ce, Gg"

Keep in mind that it's almost always more useful to have a separate map file that you reference in a scenario than putting the data directly into the scenario (not least because the editor works on such separate map files). To use a saved map file in a campaign, you have to include the map data like this:

map_data="{@editor/''map_filename''}"

Note that @editor here means that the map should be found in the '''''userdata''/editor/maps/''' directory. You need to specify something else if your map is in another location (for example, in a campaign, the maps should go into their own folder). The [[ScenarioWML]], [[BuildingCampaignsTheCampaignFile]] and [[PreprocessorRef]] pages all contain more detailed information about how this works.

==== Share your map ====

When you're ready to share your map with the world, post if to the forum or package it to be distributed on the in-game add-ons server. For instructions on how to distribute maps, see [[BuildingMapsDistribution]]

== 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. Check out [[BuildingMultiplayer]] for more information.

== See Also ==

* [[Create]]
* [[ScenarioWML]]
* [[ReferenceWML]]
* [[BuildingScenariosShroudData]]
* [[TerrainCodesWML]]

{{Create}}

Drakes

2009-08-11T01:46:20Z

Mabeenot: fixed typo

{{Faction |
faction = Drakes |
image=
http://svn.gna.org/viewcvs/*checkout*/wesnoth/trunk/data/core/images/units/drakes/flameheart-lead.png |
era=[[Default Era]] |
race=[[Drakes (race)|Drakes]], [[Saurians]] |
alignment=Lawful, Chaotic |
units=Drake Burner, Drake Clasher, Drake Glider, Drake Fighter, Saurian Skirmisher, Saurian Augur |
tactics=[[How to play Drakes]] |
tree=[http://www.wesnoth.org/units/1.6/C/era_default.html#Default%20/%20Drakes 1.6]
}}

The '''Drakes''' are a faction of dragon-like [[Drakes (race)|Drakes]] and their lizard [[Saurian]] allies. Drakes are descendants of dragons, but smaller in size. Saurians are considerably smaller than Drakes and from different ancestry. Together, the Drake faction has high mobility but low defense, leading to unusual tactics for a [[Default Era]] faction.

==Races==
===Drakes===
''Main article: [[Drakes (race)]]

Drakes are large, winged and fire-breathing creatures, reminiscent of true dragons. On average, an adult drake stands around three meters tall and easily weighs more than a man and a horse combined. Their skin is made up of hard scales, resistant to most physical strikes except piercing and cold damage. Most drakes are capable of true flight and can travel long distances quickly. However, their sheer weight and bulk limits their flight ability somewhat, making them ungainly in the air. Where possible, they make use of terrain features such as hills, mountains and trees as launch points in order to gain greater height and speed. Fortunately for their enemies, they are still quite clumsy creatures and surprisingly slow in combat. This, combined with their large size, renders them easy targets for those who dare attack them.

===Saurians===
Saurians are the smaller, more crafty allies of the Drakes. They often live in swamps or other damp places. Saurians are very small of frame, and though they are somewhat frail because of this, they are very, very agile. In combat, their size allows some of them to dart past defenses that would hold any grown man at bay, making them a tricky foe to deal with. Other saurians have some knowledge of what men call sorcery, but their practice of it reeks of augury and black magic. It is little understood, but rightly regarded with fear by those against whom it is used.

==Tactics==
''Main article: [[How to play Drakes]]

Drakes generally win by dealing the most damage. Their units are big and deadly, but they're also more expensive than most. The best way to play Drakes is to take advantage of having the best mobility in the game by placing the units in hard-to-access places such as behind mountains or across water from their opponent. Drakes have the advantage by being able to decide when and where battles will happen. Their major disadvantage is how easily their units will take damage. Because of this they usually want to be the aggressor in battle to kill a unit or two, get damaged, and then flee to heal. Having a mobile healer helps with this if villages are sparse.

{{Factionbox}}

[[Category:Factions]]