The Battle for Wesnoth Wiki - User contributions [en]

Two Brothers story

2010-05-15T09:07:29Z

Szymek: Redirected page to A Tale Of Two Brothers Story

#REDIRECT [[A Tale Of Two Brothers Story]]

User:Szymek

2010-05-15T09:04:19Z

Szymek: start

I am just a regular user.

WesnothPhilosophy

2009-09-25T17:57:23Z

Szymek: rv

== 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-09-25T17:56:59Z

Szymek:

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

BulgarianTranslation

2009-09-25T17:56:39Z

Szymek: rv

TheEasternInvasion

2009-09-22T06:48:36Z

Szymek: Undo revision 32397 by BooloEltvi (Talk)

This is a discussion of The Eastern Invasion, the campaign featuring Gweddry General of Wesnoth.

''Note by Crus4a7E: I played this campaing in V 1.4.5 (medium difficulty) using this walkthrough. As most parts did not quite seem to reflect the current state of the campain anymore, I felt obliged to contribute a number of updates to most scenarios' walkthroughs. Nevertheless, please feel free to further improve this walkthrough in particular for those scenarios I have not played and thus not updated. Overall the campain now seems well-balanced and is fun to play.''

The following descriptions are aimed at the "medium" difficulty level (as "easy" lets you get away with sloppiness and "hard" is for people who are comfortable with Advanced Tactics). Please improve these and add your own for later levels.

'''Warning: spoilers ahead!'''

==Scenarios==
=== The Outpost ===

It is probably best to recruit 5 heavy infantry and 1 mage on this scenario. The heavy infantry can flag the villages surrounding you by turn 3, turn 2 if they're quick, and the mage can flag the northern forest village on turn 2 if quick.

Sending 2 HI(heavy infantry) south, to the revenants, is a good idea because you can usually get both of them a 2nd level kill without having either die. The other ones should stand and fight against the enemies coming at you from the north and east. Use the HI most of time, and use the mage when they are in forest and it can get a killing blow. By the end of the scenario, you should have 2-3 shock troopers and 1 half-advanced mage.

It is sometimes a good idea to recruit another mage on turn 10 or so, since you will probably end the scenario with less than 100 gold anyway, so you save money by buying in advance. (mathematically this does make sense). Also, you can get them about 10 experience along the way.

==== Alternative Strategy ====
The above strategy did not work for me despite of several attempts. Whenever I recruited only 5 HI or tried to send 2 HI southwards to capture villages I got slaughtered around turns 10 to 12 by the latest. (Played with V 1.4.5 on medium difficulty) Thus below I describe an alternative strategy which worked rather painlessly for me.

Remark: In V 1.4.5 all of the villages surrounding the player's keep are already flagged at the start. Only in the very south (south of the river) are a couple of unflagged villages.

Recruit one keep full of HI in turn 1 (no mage, as there is little use in it in this scenario and we are short of money). In turn 2, move the HI to build a straight line northeast and east of your castle (the line should be inside the castle walls whereever possible to use its high defence rating but other than that as straight as possible to only allow two enemy units at a time to attack any of your HI). Then wait about 2 to 3 turns until the enemy forces start to attack and you have enough money to recruit about another 3 HI. Use them to reinforce your line.

Then just hold out the enemy attack during night time; only rotate wounded units if possible, but do not counter-attack. At dawn start your counter-attack without worrying to much about keeping the original line intact. Instead try to level 2 or 3 HI to Shock Troopers. The enemy forces quickly cease to be any danger to your forces.

Also around turn 12 the white mage re-arrives and points out a trap door you should use. The trap door is located near your castle and clearly visible unless any unit stands on it. So if you do not see it right away, just move your units around a little.

Position your leader near the trap door so he can reach it in one turn. As it is almost impossible to finish with more than 100 gold (which is the minimum starting gold of the next level), use the remaining turns to level as many units as possible and only move your leader onto the trap door in the very last turn.

Using this strategy I finished with 2 shock troopers and several well-levelled HI. Also your leader and the white mage should have gained a little experience.

==== Alternative Strategy #2 ====
An alternative strategy to consider is to recruit as late as possible and to start fighting when the sun is up. Somehow you will be able to decide when to engage in the battle, as the enemy will let you stay in your castle without bothering you.

At turn #4, recruit 1 Mage and 5 Heavy Infantrymen (HI). The trick is not to move a single unit and somehow, no one attacks you. I did the test multiple times and I always started the first fight when I decided it was time (i.e. during the day light). A variation of the strategy that does not work is to start recruiting only when the sun is up; somehow the enemy attacks your leader.

Turn #7, this is dawn and now you can start attacking. My goal is to finish any fight with my Mage or the Leader to get them to level 2 and 3 as soon as possible. White Mages always make my life easier during Campaigns. I also recruit 2 HI, 1 Cavalryman to go get some villages, and 1 Mage.

You will end up with 1 HI or your Leader at level 2 and your Mages should be half way to Level 2.

==== Alternative Strategy... #3 ====
None of the above tactics work when playing under the "challenging" difficulty level(since you are given only 80 coins at the beginning of the scenario).

My advice when playing this on the hardest level is to spend your starting money on two HI units and two cavalry units. Don't buy any mages -- they are too fragile and expensive. Your main goal is to keep away as much enemy forces as possible from your keep (ESPECIALLY during night). Use the cavalry to divert at least a small portion of the undead by making them chase your horsemen. Remember to always "taunt" them -- capture the villages near their keeps and run away from there the next turn. This way you can keep your fortress not owerwhelmed for some time. Spend every coin possible on heavy infantry and don't let skeletons/bats occupy tiles in your keep. If you do let them, this may be fatal to your leader. ;) You may even recruit a spearman or two to "block" a keep tile if this may save your main character.

NOTE: I did use this exact same tactic to beat the scenario on challenging, however, it did require some luck and re-loading. Remember -- when things seem dire, leveling up is the best healing. I saved my leader(why do I always forget his name?) by letting him kill a second-level skeleton archer, but that only happened by miracle - he hit all three times on 40% and didn't get killed by counter-attacks although he had only 3 HP left! I must be lucky :P

Euclid

=== Escape Tunnel ===
Remark: The following applies to V 1.4.5 medium difficulty.

Don't bother recalling HI, they go too slow in caves. Go for a group of mostly mages, and a couple of spearmen. (One keep of units in total should easily be enough.)

Move your units to the east until you encounter trolls and reach a crossroads. A couple of dwarfts will kindly become your allies and keep off the trolls for a few turns. Send a quick spearman to the north where he can pick up a holy amulet (unlike in other campaigns this holy amulet is permanent!). As soon as you have got the holy amulet start to move all your units south without bothering about the trolls or the undead which appear after a number of turns from the direction of your keep.

The undead, trolls and dwarves will all fight each other, so after having moved all your units south position one healthy spearman at the end of the cave leading south (so only one unit a turn can attack him) and position the white mage right behind him to heal it every turn. These two units should easily keep of the enemies following you until the end of the scenario. Move Gweddry to the northeast accompanied by a mage and a spearman (to fight individual trolls coming your way).

Before moving Gweddry to the end of the cave (which ends the level) send the mage to the east past the funny signpost warning you of the troll hole. In the cave the mages discovers a chest containing a troll treasure amounting to 200 gold.

Following this strategy you should earn a decent early finish bonus plus the 200 extra gold, so you finish with well over 300 gold.

Remark: Giving Gweddry the holy amulet (instead of a spearman) allows him to level very quickly, which is important, since he can advance to Grand Marshal. This gives benefits in other ways on a number of later scenarios as well, such as the River Crossing, where you can get an easy 1st turn kill against the undead leader and take his castle. Note that the leader is very hard to kill anyway.

=== An Unexpected Appearance ===

What you do in this scenario depends on which way you want to go. Going east is harder, but brings you more reward, such as the chance to go to Mal-Ravanal's Capital, which gives you the opportunity to get extra experience (a lot for whoever survives) and a free Paladin and several Knights.

Obviously, first kill Mal-Tar. To do this, shoot him with Dacyn and attack him with Gweddry's melee. It probably won't kill him the first turn, so second turn kill the vampire bat he recruits with Dacyn and finish Mal-Tar off with Gweddry.

Then, recall 2 shock troopers and 1 half-advanced heavy infantry on the side of the castle you are going (so if you are attacking eastward, recall them on the 3 eastern castle hexes). This gives them a headstart in that direction.
Dacyn might be wounded, so send him to a village. Don't worry, he can fend for himself, since the bats usually arrive one at a time and he can kill one per turn.

Recall any mages with a lot of XP and the spearman you gave the holy amulet in the previous scenario, then go whichever way you are going. You might want to recruit one throw-away cavalryman to go north, since he gives you income and draws away enemies that otherwise would attack your main force from behind.

===Diverging Campaign Path===
==== Elven Alliance ====

The Orc's warning about the assassin is overrated; Volas can probably take care of it himself, although you might want to leave ONE unit near him to make sure.

Recruit / recall a wide assortment of units, mostly mages, spearmen and cavalry. Send mages and spearmen up to fight the opponent, send cavalry down as scouts. Any heavy infantry should go up to fight also; they will probably arrive late, and be good for reinforcements when the first troops are wounded.

Align the troops in the forest, so that the enemy will be on grass; this gives you a tactical advantage. Use Dacyn to heal those who need it most - those on the corners, and any mages who are on the front lines.

There is a village at {20,8} that can prove tactically very useful, because the elves usually fight somewhere near it.
The elves are defeated most of the time, and the orcs claim this village; it is crucial to kill the orc on this village and take it over with a resilient spearman, or a HI.

Once you have gotten past turn 6, it will be day, and the orcs will be very easy to defeat. When the assassin appears on turn 7, ignore it unless you have a cavalryman still down there. In that case, use it to fight the assassin. Keep pressing up. By turn 9, the orcish leader should be dead.

==== The Undead Border Patrol ====

This scenario also depends on which way you want to go. If going NW, it is fairly straightforward. The enemy is relatively weak. Do the same as in Unexpected Appearance - recruit 2 suicide cavalrymen to distract the bats. One will probably get enough XP to be worth recalling.

I would use mostly heavy infantry and spearmen with the holy amulet on this level, because mages will only get a +10% to hit from magical. However, as in most scenarios against undead, white mages are very useful.

Try to get the opponent to fight you from the sand. This gives you something like a 70% CTH. >)

(CTH = Chance To Hit).

===== Mal-Ravanal's Capital =====

Only reachable from ''The Undead Border Patrol'' scenario, but you might also skip it and go directly to ''Northern Outpost''.

This is a very challenging scenario. I started with only 100 gold, so I recalled one Mage, two Shock Troopers, one Heavy Infantry, and my holy Halberdier. I defended the starting castle for about 10 turns until the Revenants had made their way over to me. Upon killing several of them, I freed some imprisoned Knights and a Paladin. I moved my forces to kill the Death Knight, and then split my forces. I sent one group to attack Mal-Ravanal and the other to kill the Necromancer in the NW corner.

By turn 30, my Eastern assault force was in postion to attack Mal-Ravanal. However, when I attacked him, he teleported my troops back to the starting castle, so I wasn't able to defeat him. When I was ready, I killed the NW Necromancer and progressed to <i>The Northern Outpost</i>.

The reason to go here is to acquire a cavalry force of one Paladin and five Knights. To do this kill six of the Death Knight's troops. The first kill gets you a Paladin. Each succeeding kill gets you one more Knight. They all appear in or around the village southeast of your castle. To end the scenario, have your cavalry force kill the southwest Necromancer while holding your castle from the assault. This can be done by turn 14 giving you a sizeable bonus. You might send expendable cavalrymen north and southeast to distract the enemies, but it won't do much.

As of 1.0.2 it's the Bone Shooters that must be killed to release knights. On the first kill you will get a Paladin as well as the Knight. These seem to all appear around the same village. Maybe they group around the Paladin. Each unit pops in with full moves. If you can use some of them to kill other Bone Shooters, you end up with a substantial cavalry force very quickly.

On easy at least, in 1.0.2, my opponents summoned no Bone Shooters, only Revenants. It took a while for them to arrive, and I could have killed the NW Necromancer, but I waited it out. I still got paladins and knights for killing Revenants. (vfb)

As of version 1.5.4 the cavalry (not apparently loyal) are earned by killing the Death Knight's troops. There are a total of one Paladin and five Knights available, but the number of Knights available is reduced by one for each of your troops that die *after you get the Paladin*. You might want to make sure any expendable troops are "expended" by the time the Death Knight's troops reach your line--units on their own won't last too long with all the ghosts flying around.

=== The Northern Outpost ===

Reachable both from ''The Undead Border Patrol'' and the ''Elven Alliance'' scenarios.

There are two enemies in this scenario that you must defeat - the undead and the outlaws. The undead are fairly straightforward to defeat, and in any case Owaec usually does a good part of the work. Recall a number of shock troopers, a white mage and the spearman who picked up the holy amulet in one of the previous scenarios. I addition recruit one mage.

Then send Gweddry to the holy amulet in the south west accompanied by the mage. The spearman and the white mage go straight southwards and help Owaec with the undead. Your shock troopers go to the east and surround one of the villages over there without flagging it. (As they are quite slow-moving, having them already over there saves you time later on.) Once Gweddry picked up the holy amulet, send him and the mage to finish off the undead leader together with your spearman. (Note: Your spearman is very effective against the undead and will likely level up.) That was the easy part.

The main challenge is the criminals. They appear randomly in the villages you flag (one of the villages has assasin that is outlaw leader), but not in those Owaec flags. So don't worry about him uncovering enemies for you. Since when you capture a village the outlaws surround it, you should surround each village before you capture it, so the enemy surrounds you. This makes it so they can't gang up on one of your units with more than 3 people. Also, when you capture a village, try to kill as many enemies as you can before they get a turn.

Send your your entire force up on the eastern side of the map flagging one village a turn and fighting the bandits. Once you come across the village where the bandid leader hides, concentrate your attacks on him as the bandits are quite strong.

Note: A Cavalry force (such as the one acquired in Mal-Ravanal's Capital) makes short work of the bandits. Lower level units have trouble against the Bandits, especially at night. Slower moving units also have a disadvantage in searching the villages.

Also note, that from this scenario on you can recruit horsemen. You might want to level up a paladin or two, for fast mobile undead removal services (and quick leader assasination).

/* governor */ Just a note: I had the misfortune of taking a group of men to a village where 5or6 enemies appeared. After taking heavy damage, I retreated my char (low on hitpoints) out of the village. When I recaptured the village the same group of enemies reappeared. Since AI enemies seem to prefer recapturing villages this can allow you to obtain easy experience for weak units a few times.

=== Two Paths ===
This is a fairly tough level (played in V 1.4.5 on medium difficulty) which took several attempts to get through. In V 1.4.5 you have 16 turns (unlike 12 as in earlier versions) and can choose between going north to attack the orc leader or going north-east to attack the undead leader.

One option is going north on the very east side of the map trying to fight your enemies from solid ground and mountains while they stand on sand ground with weak defense. As your troops move very slowly on this terrain, you will likely take some heavy losses however, as your enemies keep surrounding you. Also this will presumably take too many turns to reach the orc leader in time.

Thus the preferred choice is to recall a couple of shock troopers and white mages and move them on the path to the north-east in a thigh formation towards the undead leader. Once you survived the first enemy onslaught without loosing units, the rest of this scenario becomes rather easy as the remaining enemies come one by one. Make sure to keep on moving fast to the north-east to reach the undead leader before turns run out.

=== Diverging Campaign Path===
==== Undead Crossing ====
Fighting the undead in this scenario is not the actual problem as they are quite weak. Recall a keep full of shock troopers, white mages and the spearman with the holy amulet (who has likely levelled up by now). Use your faster units to capture the villages in the south-east and move your shock troopers directly to the river crossing.

Once you fought of the bats and skeletons (which the above units should handle quite easily), the undead leader summons two cuttlefish which appear in the water between the two crossings. Be very careful where to position your troops as the cuttlefish have a very nasty melee attack. Fight them with a pair of shock troopers accompanied by Gweddry (to give them leadership) and a white mage for healing.

Make sure you leave your units enough time to cross the river and kill the undead leader before turns run out.

==== The Crossing ====

I had only 100 gold, so recruited some units and went straight north from turn one on. The fighting in the water was quite hard, with some orcs coming down from the north. The un-dead only appeared when I was in the middle of the river, so no encounter with them, and the ogre's helped get rid of the orcs on the north side. (Allefant)

If you have Holy Gweddry, you can (sometimes) get a 1st turn kill on the 1st undead leader, scarf up all the villages, and return to kill the 2nd undead forces before their leader can recruit anything. If you don't, the second undead leader will recruit lots of level two units. The orcs will start out across the river, but usually most of them turn back to fight the ogre reinforcements. Waiting till their first wave hits your shore and wiping them out in the water will probably leave you just enough time to cross the river and find there are only 2 or 3 enemy units left besides the leaders.

Make sure to cover your rear flank with some expendable troops (such as Heavy Infantry) as the undead can move more quickly through the water than your units.

Another strategy is to go straight into the water after killing the first undead leader using the deep water in the middle of the path to seperate the orc forces. You go to the right with Gweddry and Owaec and some support troops while letting the ogres kill many of the orcs in your way. Knights and a Paladin can hold off the orcs enough to get across while the undead behind you are not an issue.

Note: Owaec can move only one hex a turn in the water.

=== Training the Ogres ===

This can be a confusing scenario to understand. Basically, you are fighting the ogres while also trying not to let them reach the rocky borders where they will "escape" (or disappear). Understand how the AI works and that units will attack the weakest units who are closest to leveling.

Whenever I tried to attack the ogres or surround them or using any other intuitive strategy, I always ended up getting my white mage killed by turn 3 at the latest.

Thus try the following which makes keeping all 4 ogres on the green very easy (although I still do not understand why the AI behaves as it does...): Move the white mage and the horseman to the very north outside the moving range of the ogres. Position Gweddry on one of the hills in the west just inside their moving range. For the first two turns the ogres hardly move. Then they start to attack Gweddry which he should be able to withstand. By turn 5 when Gweddry's health starts to wear down, the scenario is over already with all four ogres still on the green and all of your units alive.

(It's a bit of a digression, but the AI in this case is failing to realize that, though each Ogre has an individually unfavorable attack on Gweddry, all four attacking together would be rather more favorable. So, the AI decides to form a defensive line and wait for the sun to set, when Gweddry's 25% bonus disappears and their attacks are more favorable. Note that this technique generally only works for units with full health on defensible terrain, and may disappear entirely if the AI is improved to consider joint attacks.)

It is unclear to me however, what the benefit of all four ogres surviving is though.

Note: Whether or not to use ogres is a matter of playing style. Once they level up, Ogres are quite a tough unit that deals middling damage, but unfortunately can't advance beyond level 2. Their upside is that they move at normal speed on hills and cave floor, which makes them your most mobile unit in at least one scenario (''Captured''). And as they are of neutral alignment, they can sometimes be handy to have around at nighttime.

=== Xenophobia ===

In V 1.4.5 on medium difficulty is a very easy and fun level as all parties in the scenario (i.e. elves, orcs, drawves, and yourself) decide to fight each other instead of forming aliances. Thus you can use this level to gain some experience for your units, pick up another permanent holy amulet (in the north, roughly in the middle between the dwarf and the orc keep) e.g. by a shock trooper, and as the actual ogre training camp (see below).

Recall a keep full of shock troopers and send them straight to the north as they are very slow moving. Then recall one or two white mages and recruit about two to four young ogres. Send all of your units straight north to kill the dwarf leader who unwisely sends all his troops for the orcs right at the start and then misses the money to recruit any more troops to defend his keep.

By the time I reached the dwarf leader, the orcs had already killed the elvish leader, so there was two down and only one to go. Use the young ogres on the mountains in the north to fight the remaining dwarves whilst levelling up to ogres.

By the time you killed the dwarf leader, there should be hardly any enemy troops left, so go straight towards the orc leader and earn a decent early finish bonus. And don't forget to pick up the holy amulet on the way.

The main strategy in this scenario is staying out of the fighting as much as possible, picking off the weaker sides, and in general letting your enemies kill themselves. One successful strategy is to delay moving from your keep for 5-6 turns. Let the other factions weaken each other before you move off. (Although that reduces your early finish bonus, so do not do this if your troops are strong enough.)

By the end of the scenario you should have one or two ogres which comes in quite handy in the next scenarios.

=== Lake Vrug ===
This is a very confusing hide and seek sceario which is not actually hard, but likely takes you several pointless restarts until you have finally discovered the enemy leaders. (Spoiler: there are three enemy keeps, all north of the river. One is to the very north west (go to the right into the mounts directly after crossing the bridge), one is between the path leading east and the river bank just before the path turns northwards, and one is in the very north at the end of the path. The orc leader resides in the first keep, the gryphon leader in the second, and the third is empty.

Recall two or three shock troopers, two white mages and then recall/recruit as many ogres as possible. (Most of the enemy keeps are surrounded by high mountains which most of your troops cannot pass, but which the ogres handle quite easily.) You might also want to recruit a horseman to scout ahead.

The only challenge in this scenario (apart from finding the keeps) is surviving the first onslaught of gryphoons which starts around turn 4 with quite a number of gryphoons appearing from the north-east. Position your heavy units like shock troopers and ogres very tighly around wounded units as the gryphons and dragons really have quite a large moving range and ignore zones of control and thus mercilessly slay away unprotected injured units. To fight them use heavy melee troops like shock troopers.

As you start to cross the bridge a couple of trolls attack. They are really no match for your shock troopers, however, who happy troll-crack away.

When taking the enemy keeps, use the ogres who can move on the high mountains unlike most of your other units.

=== Captured ===

You start out by running up a tunnel to find some of your companions. If you go back down that way or you will have to face some extremely mean trolls in the narrow tunnel. Instead, follow the tunnel to the north and west and face a few bats as you proceed. At the end of that tunnel, you will enter a throne room where there is a leader and some enemy troops.

Upon entering the throne room, a group of your wounded troops will appear in a cavern called the "Torture Room" to the east. They will face a number of assassins and trolls as they leave the Torture Room moving west. (Hint: Try to get through the prison "door" of the torture room quickly as otherwise the enemy units have an easy time keeping your entire army locked away with only one unit at a time, i.e. the unit standing at the door, being able to take part in the fighting.)

Victory occurs when Gweddry moves through the exit in the southwest corner. There is quite a comfortable early finish bonus, so you might want to move him there quickly in order to put some money on savings for later scenarios. It should be possible to finish with over 500 gold without making haste, however. You should also flag the numerous villages in a cavern called "The City", a cavern southwest of the Torture Room.

There is a holy necklace on this level, at coordinates x=12, y=2. Preferrably grab it with a horseman or someting similar. He will come in very hand in later scenarios.

Note: Most of the orcs are level two and three units.

=== Evacuation ===
This scenario is a little frusting. Not so much because of its difficulty (it is hard but managable with enough high-level recalls and lots of money), but because you ''will'' take some heavy losses of high-level troops.

Note: You should have over 400 gold and a large number of level 2 and 3 units to recall to start this scenario.

There are two options in this scenario: you can either defeat all enemy leaders or blow up the bridge in the south. In the former case, you will have to accept quite some casualties in fighting the enemy; In the latter case, all your units which are not on the south side of the river by the time you blow up the bridge (including not recalled units, meanly!) are killed by the explosion. In both cases you have to watch out for the very tight time limit of 12 turns.

I went for option 2 (killing all leaders). First recruit two to tree keeps full of your typical experienced troops like iron maulers, white mages, and so on. Ogres are also helpful, if you have some left, as they are strong and you will have no use for them in later scnearios. After that recall a keep full of young ogres as cannon fodder.

Start to move you units south and attack the central enemy right away (i.e. do not wait until you have recruited all units). The last recalls before the young ogres split and send half of them to the north-east and the other half to the south-west (otherwise you might not make it to all three leaders in time). Finally, send some young ogres to the north-east and south-west to distract the enemies there for two or three turns.

With all three groops of your units try to focus on attacking the enemy leaders as soon as possible so you do not run out of time. Apart from that, watch out for the level 2 trolls, particularly, as they can (and frequently will...) instantly kill almost any of your units. Best fight them with two white mages or a white mage accompanied by some other unit.

With a bit of luck and probably some nasty casualties you will have killed all three leaders around turns 10 to 12.

[Garion] In 1.0, I recruited a lot of Cavalry for fodder, spacing them 1 hex apart to establish a ZOC corridor from my castle to the bridge. They got chewed up very quickly, but they bought me enough time to get out. Use a few Shock Troopers to guard your rear against the Blue enemy; they're too slow to escape anyway. Remember to recall your slowest units closest to the bridge, to minimize the time they spend in transit. I was able to evacuate 2 Holy Cavaliers, 2 Paladins, a Great Mage, the three heroes, a quick Iron Mauler, 2 White Mages, and a Mage of Light.

[Vladevil] In 1.2.6 what worked best for me was recruiting only fodder for 2 turns, then running away with all the main characters. I let Owaec and the mage first and Gweddry last since he can take some hits. All in all I was finished on the 6th turn without losing any valuable troops.

=== The Drowned Plains ===
The Skeletal Dragon will be found in or near the castle (located on an island in the south-east). In getting there, there is a chance the undead (three units mostly level two and an occasional level three) will spring out of the ground near the unit you just moved. Therefore less units are better. Advanced mages, paladins, and other fast-moving units with arcane weapons work well here. To withstand the initial dragon attack you will need very strong units (with more than 50 HP). In order to discover the dragon despite the fog units with a large moving range (and thus large visible area) like horseman are helpful.

The dragon wanders around near the castle but only attacks units which he can kill instantly. If only strong units come near him, he tries to flee. Because of the fog the major challenge of this scenario is finding him and then getting him surrounded so he cannot just move away again. Once you have him trapped like this, slaying him should be easy using your stronger units (preferrably impact weapons because the dragon has a low resistance there).

=== Approaching Weldyn ===
This scenario is fairly easy, but also fun to play. The essence to success is being very fast.

Recall 6 to 8 fast-moving units with arcane attacks. This should be any fast unit who has picked up a holy amulet in earlier scenarios like horsemen or spearmen plus some level 2 or level 3 mages. Completely forget about heavy infantry or other slow-moving troops of similar kind. Move all your units to the eastern enemy and try to kill him by turn 3 or 4 by the latest. This should be easy, as he is still very weak.

Then rush over to the western enemy. It will be night by now so not a good time for attacking. If you have a very strong and fast unit (like a dragoon) try to position it on the enemies keep. This trick stops the enemy leader from recruiting more troops despite having plenty of money left. Once your other troops arrive and daylight breaks you should have an easy time finishing of this enemy leader and those of his troops which you ally has not yet killed.

Then attack the third leader in the south-west in the same manner. If you hurry, you should be able to finish by turn 9 and gain a good early finish bonus.

=== The Council ===

Only plot in this. You see the inside of the castle.

=== Weldyn Under Attack ===
This is an interesting scenario where once again choosing the right strategy is the key to success. Also watch out for the time, as you have only 18 turns to finish.

You find your keep in the center of an island. Three allied leaders also have their keeps on the island around yours. There are three enemy leaders: a weak one in the very north, and two equally strong ones in the south-east and south-west, respectively. It stays nighttime (first and second watch) during the entire scenario which is somewhat uncomfortable, but not a big problem.

Start by recalling all high-level units with arcane attacks (6-8 units max). Then recruit two keeps full of mages. Send your troops straight north and finish of the enemy leader. He is quite weak and even moves onto your island so this should be painlessly accomplished by turn 3.

Then split your troops: one half moves onto the western shore (along the very border of the map), the other half onto the eastern shore (same). To get across the river use the bridges in the north-west and the north-east, respectively. Let some of the mages stay behind and capture the villages on the island so you do not loose money. The may also assist you allies so they do not fall so quickly and keep the enemy busy.

The rest of the scenario is straight-forward: move both your troops southwards straight towards the enemy keeps and kill the leaders. As they have sent most of their troops onto the island where they are busy happily slaying away your allies, this should be no challenge for your troops. Watch out for the nightgaunts, though, which tend to ambush you or rush for weak units without you seeing them coming.

If all goes right you should have killed the remaining two enemy leaders around turns 14 or 15.

Hint: If you have one or two silver mages available (e.g. the engineer unit you joined you in the Escape scneario, if he has levelled by now) this is quite useful in this scenario. The map is rather large so have some fast-moving units like horseman run through enemy territory and capture individual villages. Then use the teleport ability of your silver mage to perform hit-and-run (or rather: hit-and-teleport) attacks to weaken your enemy before attacking with your main force. Make sure you do not get him killed, though, by holding out too long after attacking.

After killing all enemy leaders, an enemy messenger appears telling you that you have only fought some delegates of the ancient lich Mal-Ravenal. It challenges you to have a duel with Mal-Ravenal instead of letting the armies meet for a final battle. If you accept the challenge, you get to scenario "The Duel". Otherwise you get to "Weldyn Besieged".

===Diverging Campaign Path===
==== The Duel ====
This is a somewhat strange scenario: you and Mal-Ravanal get to recall/recruit exactly six units each and then have to fight each other. Mal-Ravenal will recruit mostly level 3 units so this looks difficult. In fact, it is quite managable, however.

Recall mostly mages of light and other high-level arcance troops. Set them up in a line of 4 units backed up by 2 units at the edge of one of the forsts near your keep. (Your leader should stand in the back up line so he does not accidentaly get killed.)

Then wait for his troops to reach you, but make sure you are the first to attack. By the time you meet it will be close to nightfall. Do not hesitate to attack, however, as Mal-Ravanal plays unfair and recruits another 3 units on every first watch.

In your first attack you should be able to kill two enemy units. Try to have at least 5 of your units survive the first round of enemy attacks. Then kill the remaining enemy units near you and move over to Mal-Ravenal straight away who hides by himself on the very border of the map in the mountains. Again, do not wait for daylight, as you can reach him before his reinforcements get to you, so you should have an easy time killing him with your remaining units.

Spoiler: After killing Mal-Ravanal the campaign ends with a final scene of Gweddry and his companions being honoured by the king.

==== Weldyn Besieged ====

On versions prior to 1.5.6 the siege is laughably easy to break; just recall a keep full of your best troops and rush Mal-Ravanal in the south.

As of 1.5.6 this battle should prove a more substantial challenge. Now the liches' names aren't revealed until they are attacked, and Mal-Ravanal is more likely to be revealed later in the scenario. Sending fast scouts to attack all the liches is not advisable since each lich receives a boost of gold for another round of recruitment after its name is revealed.

A workable strategy is to recall a group of cavalry with holy amulets and paladins to circle behind the undead horde and terminate the liches. You can draw the liches out of their keeps by positioning a sacrificial horseman within their attack radius. Once the lich is out in the open, your arcane damage cavalry should have no trouble finishing the lich off in a single turn.

Meanwhile you'll need the rest of your troops to hold the central keep against the undead onslaught. If you can spare the funds, a few sacrificial troops can delay the incoming enemies on one side, giving you the opportunity to focus your firepower on the undead approaching from the other side(s). If things turn grim, retreat to the castle and make your final stand.

[[Category:Campaigns]]

Description

2009-09-22T06:48:26Z

Szymek: Undo revision 32396 by DroneLtcna (Talk)

== 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.2-b.jpg http://www.wesnoth.org/images/sshots/wesnoth-1.2-b-175.jpg]
<div class="thumbcaption">A magical lightning strike</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.2-e.jpg http://www.wesnoth.org/images/sshots/wesnoth-1.2-e-175.jpg]
<div class="thumbcaption">The '''Heir to The Throne''' campaign</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.
* GNU/Linux, Windows, MacOSX, RISC OS, BeOS, Solaris, FreeBSD, OpenBSD, NetBSD, DragonFly BSD, AmigaOS4, OS/2 & eComStation compatible.

{{Play}}

TheEasternInvasion

2009-09-19T14:56:23Z

Szymek: Undo revision 32345 by BooloEltvi (Talk)

CampaignBurningSuns:RussianTranslation

2009-09-12T16:21:12Z

Szymek: Undo revision 32242 by TreraLdomt (Talk)

WesnothPhilosophy

2009-09-12T16:21:04Z

Szymek:

TheEasternInvasion

2009-09-12T16:20:47Z

Szymek: Undo revision 32239 by BooloEltvi (Talk)

GettingStarted

2009-09-12T16:20:25Z

Szymek: Undo revision 32236 by AcellImona (Talk)

{| 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://exong.net/wesnoth-attach/files/splash111_1152_744.jpg http://exong.net/wesnoth-attach/files/splash111_300_159.jpg]
<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>

CampaignBurningSuns:RussianTranslation

2009-09-07T10:00:13Z

Szymek: Undo revision 32210 by TreraLdomt (Talk)

TheEasternInvasion

2009-09-06T06:56:47Z

Szymek: Undo revision 32204 by BooloEltvi (Talk), spam

Description

2009-09-06T06:56:32Z

Szymek: Undo revision 32203 by DroneLtcna (Talk), spam

SoC People to bug on IRC

2009-09-06T06:56:17Z

Szymek: Undo revision 32200 by OrlimOnace (Talk), spam

== People to bug on IRC ==
We have prepared a list of people with their "area of competence". This is to give you an idea on which areas those people can be of help for you. Of course you should always just ask in the IRC chan, but those are the most likely ones to answer questions in the respective area. And here is the list:

=== boucman ===
As our "patch monkey" he accustomed to critiquing patches of every kind. Beside this, he knows many areas of the game due to working on applying patches. He is particularly used to answering question from new coders, and doesn't mind explaining trivial stuff. He was the one who started the "two patches, you're in" policy and the ReferenceWML part of the project.

=== Daniel Franke (dfranke) ===
Daniel is the devteam's most recent addition, and has been primarily concerned with security auditing. Bug him <i>privately</i> if you think you've found a security issue.

=== Dave alias Sirp ===
Sirp started Wesnoth and is our lead developer. He is currently our C++ expert and is also the one that is working on the new Formula AI. Any questions regarding the formula AI should be directed to him.

=== Dragonking ===

He is one of our best Wesnoth players, and understands the various strategies well. He has also programmed much of the Wesnoth Formula AI system and understands it well.

=== Elias Pscherning (elias) ===
He wrote the original version of campgen and as such will know a lot about what is needed to to make such an editor work correctly. The work on a scenario editor might be based upon campgen and as such his knowledge will be really helpful.

=== Eric S. Raymond (ESR) ===
ESR is our project toolsmith; he has written several tools that semi-automate various aspects of WML maintenance. While most of our developers/designers concentrate on either the C++ core or WML but not both, he has a balanced understanding of both levels and may be helpful in helping students develop a grasp of the overall architecture. Finally, he did the last overhaul of the Wesnoth UI and understands UI design principles; he is well-equipped to guide students working in that area.

=== Happygrue/Wintermute ===

A recent addition to the development team, Winter has recently been helping to test the AI and is a useful person to ask about behavioral problems in this area.

=== ilor ===
2008 GSoC student, worked on and maintains the new map editor in Wesnoth 1.5/1.6. Has some fairly recent experience with getting "in" the Wesnoth codebase.

=== Karol Nowak (grzywacz) ===
Two years he participated at GSoC as a student, so he will understand the situation of GSoC students. Beside this he is our top expert on Wesnoth for embedded devices as he worked on the gp2x support.

=== loonycyborg ===
Maintainer of Wesnoth's SCons build system and windows packager. Might also help out with other buildsystems.

=== Mordante ===
Many of the possible projects involve the code for which he is an area expert. Also, many of the possible projects currently listed on the ideas page require GUI parts to work. Mordante is currently busy rewriting the old gui engine, he will be our expert there as well as already being our area expert for the terrain engine.

=== Nils Kneuper (Ivanovic) ===
He is doing nothing special, he just does some "administrative work" like packaging fresh tarballs when it is time for them and works on setting up any kind of deadlines and timetables related to releasing. He has administrative powers in most areas, no matter if website, forum or IRC. Beside this he uploads translation updates, tries to communicate with the translation teams when it is required and translates a little bit himself every now and then. But in general he is not a real expert in anything, just has a look at things that come up and redirects people to the correct contacts.

=== Noy ===
Noy is an oddity among developers; he's got no coding skills whatsoever and possesses a limited understanding of computers, which is illustrated by his difficulty operating a Mac. Instead, Noy makes his contribution in gameplay and multiplayer design, drawing upon his background in social sciences research, military strategy and playing games online, to understand the effects of development on the playing community behavior. Along with Soliton, Noy is a useful conduit to discuss any issues in this area.

=== Noyga ===
Another versatile developer, on the C++ side he doesn't concentrate on a particular area, did some tweaks to improve translations in some languages (like enabling the female forms for names in various place) but know quite well the C++ side of units, abilities and WML. On the WML side he's an expert.

=== Sapient ===
This developer started working on the GUI and widgets, but recently he focused more on improving the internal mechanics of the WML engine such as variable look-ups and filtering. Sapient is not as active anymore but he does come one IRC in the evenings (U.S.A.). He has touched-up many areas of the code in small ways over time, thus he has a good general knowledge of the C++ code and also has worked a little on some python maintenance scripts.

=== Shadow Master/ShikadiLord ===
He has been around since late 2007, and has worked in many areas of the engine, including the game events handler, the image path functors and the add-on management engine. As an add-on developer, he knows a lot about the WML language itself (preprocessor, basic structure) and its various single-player oriented dialects. He may also answer different kinds of questions about C++ as long as you don't start cursing the language.

=== Soliton ===
He knows our MP server setup best. Beside this he has already done a lot of work on the MP server himself. So he probably has most knowledge about it and, being one of our MP-developers, might provide important help from the perspective of the MP player community and what is needed there.

=== YogiHH or Piotr Cychowski (cycholka) ===
Since they are the two developers who know most about building under Windows, they will probably be really helpful. Either if the student comes from the Windows side, or to help test resulting work to make sure that it does work on Windows and, for the case that it does not, to show them where problems are.
YogiHH also knows quite a bit about the game engine and everything that has to do with replays and savegames.

=== zookeeper or Mythological or Rhuvaen ===
As our leading WML experts those are to be contacted when it comes to anything related WML problems since they know this stuff best. They do maintain most of the campaigns and improve them whenever they have a good idea for changes.

=== See also ===
[[SummerOfCodeIdeas|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.

[[Category:Summer of Code]]

CampaignBurningSuns:RussianTranslation

2009-09-02T10:37:30Z

Szymek:

BulgarianTranslation

2009-09-01T18:41:21Z

Szymek: Undo revision 32118 by CnacoBooud (Talk), spam

SoC People to bug on IRC

2009-09-01T18:40:21Z

Szymek: Undo revision 32113 by OrlimOnace (Talk), spam

GettingStarted

2009-09-01T18:40:09Z

Szymek: Undo revision 32112 by AcellImona (Talk), spam

Description

2009-09-01T18:39:23Z

Szymek: Undo revision 32117 by DroneLtcna (Talk), spam

TheEasternInvasion

2009-09-01T18:37:32Z

Szymek: Undo revision 32119 by BooloEltvi (Talk), spam