The Battle for Wesnoth Wiki - User contributions [en]

GSoC sachith500 Proposal

2014-03-17T15:09:52Z

Happygrue:

{{SoC2014Student}}
[[Category:SoC_Ideas_Multiplayer_Data_Analysis]]

==Description==
<h4> <span class="mw-headline" id="Sachith_Seneviratne_-_Multiplayer_Data_Analysis_Proposal">Sachith Seneviratne - Multiplayer Data Analysis Proposal </span></h4>
<p>Although Multiplayer games are being archived currently, no data is saved regarding the winner(s). Recording and presenting this information would allow for easier balancing and feedback for content creators. Specifically, this project will add a means by which players can indicate who won, as well as parse the saved data and store in a database as much useful information regarding the games as possible.
</p>

==Deliverables==
Priorities are divided among
<br><font style="color: blue">Optional</font> - may not get implemented, but can be a future use of having this project implemented.
<br><font style="color: purple">High Priority</font> - will most probably be implemented.
<br><font style="color: red">Critical</font> - Will definitely be implemented.

Provide winner of game whenever possible <br>
*<font style="color: red">[Critical]</font> A button for players to resign with. On click, it will print "GG" in chat, and auto-quit the game.
Provide a database with easy extensibility to support different future types that may need to be entered.
*<font style="color: red">[Critical]</font> A MySQL / SQLite database with a connector which can store generated stats.
Stats and a way for players/content creators to gain access to them.
*<font style="color: purple">High Priority</font> Set up the data webpage.

==Implementation Details==

This section will describe the major components as well as the design decisions and implementations which are a part of this project.
The components will also be developed with maximum extensibility in mind (So that changes to WML, such as new tags etc, can be easily supported in the future).
The implementation will feature a top-down approach to

===Winner Detection===
This deliverable shall deliver a means of identifying winners in multiplayer games. This would additionally involve ensuring that the replay would contain the part leading upto the players resigning and immediately after that as well.
*Step 1 : Identify winners by having players declare a winner at the end of the game.
*Step 2 : Implement advanced winner detection, specially with respect to custom games. (this will be implemented on the parser, most probably)

===Data Analysis===
====Core Components====
*WML Parser
*Database to store results of analysis
This mainly involves implementing a parser (Currently decided language is C++) as well as a database (MySQL) that stores parsed information.

=====Parser=====
The parser will target WML and attempt to derive useful information. This will involve mostly standard string processing within the tags. Certain tags like the end-level tag will be of particular interest with regards to winner detection especially for custom scenarios.
The parser will be designed so as to support future tags as well as easy changes to the nature of tagging.
Certain data may not need to be parsed due to already being available in-game (such as unit recruit/advancement/death information). Modules that currently do such processing could send that information to the parser.

=====Database=====
Since the database is going to be used for a lot of lookup, the current plan is to keep it sufficiently denormalised to optimize performance, while at the same time allow for enough normalisation to reduce needless redundancy.
<br>
The idea is to save as much basic data about a game as possible so as to allow a wide variety of statistical techniques to be applied on them.
<u> Important: </u> Note that columns with a "!" at the end may require further decisions as it relates to certain things like collecting player stats.
======Schema======
The schema is a work in progress and is subject to change over the course of the project. Below is a list of the main tables and a short description listing the expected structure and logic behind it.

*Game Table
**Stores overall information about games (<u>game_id</u>,num_turns,num_players,winning_team,duration, ...)

*Player Entry table
**Stores information regarding the performance of each individual side in a game. Note that a single player may control 2 sides of the same race,leader combination, so (Game, player, race, leader) need not necessarily form a candidate key.
**Will include data such as game_num,player_num(!),faction,leader,gold_gathered,gold_spent,damage_dealt,damage_taken,healing_done, ...)

*Unit Table
**This table will contain details such as, unit_name,num_recruited,num_died,num_advanced,xp,damage_dealt,healing_done, ...
**It might also be interesting to store details on an individual unit basis (could allow for unit trait analysis), but this would probably be too much data.
Note- if the Leader Table is implemented as below, leader details would not be included in the unit table.

*Leader Table
**Stores data about the performance by leaders in various games. This will give valuable stats about how different leaders perform on different maps,against different other factions and even other leaders.
**This table will provide interesting insights into how leaders affect the game as a whole.

=====Data Visualisation=====
The idea is to expose the stats that are generated by the 2 other components, to players and content creators. Due to the collection of data being on the most basic level possible, it should be possible to support a large amount of customization to the queries that can be run at the user's request. <br>Note that this component has lower priority overall compared to the above components. However, the project will attempt it's best to make at least a basic presentation of the collected stats available to everyone.

Some interesting stats that maybe provided:

==Timeline==
The timeline has been devised to get working components as soon as possible, and then to iteratively improve them to the desired level. This ensures that the deliverable are guaranteed, and the iterations allow for easier management of the work required on each individual component.
{| class="wikitable centre" width="80%"
|+
|-
! scope=col | Week
! scope=col | Major Tasks
! scope=col | Subtasks
|-
| width="10%" |
Week 1 <br> ( May 19-26 )
| width="34%" |
Implement Resign Button
| width="10%" |
*Implement Button for players to Press
*Include the player resign data in the stream to the server
|-
| width="10%" |
Week 2 <br> (26 May-02 June)
| width="34%" |
Basic Replay Parser
| width="10%" |
*Implement support for checking for resigned players
*Collect some of the data that will be added to persistent storage later.
*Test basic functionality
|-
| width="10%" |
Week 3 <br>
(June 2 – 9)

| width="34%" |
Set-up basic database controller, and add data generated so far into database.
| width="10%" |
*Implement Database (SQL)
*Implement extensible design to allow for future data
|-
| width="10%" |
Week 4 <br>
(June 9 – 16)
| width="34%" |
Set-up connectivity between all new components, test implemented functionality.
| width="10%" |
*Test extensibility of the database/dbcontroller design by adding new datatypes to the parser
*Write a few unit tests.
|-
| width="10%" |
Week 5 <br>
(June 16 – 23)
| width="34%" |
Implement Additional parser functionality
| width="10%" |
*Add several more fields to the database and implement corresponding query mining on the server stream.
|-
| width="10%" |
Week 6 <br>
(June 23 – 30)
| width="34%" |
Implement advanced victory detection<br>Prepare for Mid Evaluations
| width="10%" |
*Implement better victory detection in addition to the resign button.
*Scrub code and complete documentation in expectation of mid evaluations.
|-
| width="10%" |
Week 7 <br>
(June 30 – July 7)
| width="34%" |
Optimize Communication between server and parser.
| width="10%" |
*Provide parser with only relevant data from the server data stream
*Implement basic aggregation views etc in preparation of providing presentable data.
|-
| width="10%" |
Week 8 <br>
(July 7 – 14)
| width="34%" |
Scrub Code and improve parser functionality.
| width="10%" |
*Implement some additional data gathering functionality in parser.
*Get up-to-date on documentation and tests.
|-
| width="10%" |
Week 9 <br>
(July 14 – 21)
| width="34%" |
Start work on presenting generated results/analysis
| width="10%" |
*Provide complete set of aggregation methods/ statistical analysis
*Provide access to stats a few stats on a webpage (basic victory stats)
|-
| width="10%" |
Week 10 <br>
(July 21 – 28)
| width="34%" |
Provide more details on webpage
| width="10%" |
*Add era-wise,race-wise analysis of results
*Add capabilities for custom queries
|-
| width="10%" |
Week 11 <br>
(July 28 – August 4)
| width="34%" |
Add additional features to parser/database to check extensibility
| width="10%" |
*Add a few more fields to check how extensible system is
*Improve extensibility further
|-
| width="10%" |
Week 12 <br>
(August 4 – 11)
| width="34%" |
Scrub all code and complete testing/documentation
| width="10%" |
*Add a few more fields to check how extensible system is
*Improve extensibility further
|}

<h1><span class="mw-headline" id="About_Me">About Me</span></h1>
Hello everyone! I'm a 22 year old guy studying Computer Science and Engineering at the University of Moratuwa, Sri Lanka. This is my first year taking part in GSoC and I definitely intend to take part in it next year as well. If you wish to contact me I hope the following details will be sufficient. Please feel free to leave me any feedback regarding this proposal, or anything else! :D

===IRC===
sachith500

===Email===
sachith500@gmail.com

===Github===
https://github.com/sachith500

==Experience==
I've worked on a number of projects in various languages. I've compiled a small collection of them that is relevant to this project here.

===Programming Contests===
Language used: C++
<br>I have about 5 years of experience with programming contests. I've listed links to my profiles below.

====[//community.topcoder.com/tc?module=MemberProfile&cr=23014314 Topcoder ]====
Language : C++
====[//codeforces.com/profile/sachith500 Codeforces]====
Language : C++
====[//projecteuler.net/country=Sri_Lanka Project Euler]====
Language : C++
====[//robotgame.net/user/7601 Robotgame AI game]====
Language : Python
====[//planetwars.aichallenge.org/profile.php?user_id=9900 Google AI Challenge 2010]====
Language : Java

===Decision Support System for [http://soiltechltd.com/ SoilTech]===
*PHP
*MySQL

===Customer Managing DBMS===
Database Management System that uses MySQL for storing as well as controlling access to customer information.
*PHP
*MySQL
*Symfony2
*Doctrine

===DiscoverLanka -Maching Learning, Query Mining Android App ===
A Location based, context aware app that employs query mining using an ontology database in order to learn about users as well as the places they are interested in visiting.

Technologies used:
*Android

==Contribution to Wesnoth==
=== Patches ===
I started work on Wesnoth even before it got officially selected for GSoC :D
Description is colour coded by acceptance status.<br>
<font style="color: green">
GREEN</font> indicates the patch was accepted.
<br>
<font style="color: red">
RED
</font> indicates the patch is pending approval.
{| class="wikitable centre" width="80%"
|+
|-
! scope=col | Bug#
! scope=col | Description
! scope=col | Submission Date
|-
| width="10%" |
[//gna.org/bugs/index.php?21358 #21358]
| width="34%" |
<font style="color: green">'''''Help link for special ability plague was not linking back to the units'''''</font>
| width="10%" |
2014.02.15
|-
| width="10%" |
[//gna.org/bugs/index.php?21486 #21486]
| width="34%" |
<font style="color: green">'''''Team labels were clearing non-team labels on the map'''''</font>
| width="10%" |
2014.02.14
|}

==Brainstorm==
THIS SECTION WILL BE REMOVED FOR THE FINAL PROPOSAL.
This section is just used for brainstorming various half formed ideas, so they can be iterated upon.

#Add this information to archive.
*Possible Cases to consider
*#Everyone disconnects : no clear winner.
*#All leaders on all sides except one are dead : Side with leaders remaining win.
*#All players except 1 disconnect : TODO- Decide if game is still multiplayer

*At the end of the game, attempt to identify the winner using available information.
*Current work plan :
*#Implement very basic winner detection.
*#Implement some basic database features.
*#Repeat until satisfactory.
<br>
A suitable database connector would be incorporated into the wml parser to allow for saving of collected data into a database (MySQL perhaps?).
A separate class could then be used in conjunction with the connector to provide an extensible design for the database.
<font style="color: purple">[High Priority]</font> Provide stats regarding game, (units used, advancements made etc) <br>
<font style="color: blue">[Optional]</font> Provide stats on the pages of units.wesnoth.org. eg:- http://units.wesnoth.org/1.10/mainline/en_US/Vampire%20Bat.html could have stats on vampire bats,
% appearing in games, of those offer a breakdown of how many (1,2,3 bats etc). How many advancements etc.

==Feedback==
THIS SECTION WILL BE REMOVED FOR THE FINAL PROPOSAL.
*[Critical] A button for players to resign with. On click, it will print "GG" in chat, and auto-quit the game. Provide a database with easy extensibility to support different future types that may need to be entered.

And save a replay of the game including the the outcome message. If possible, outcome message would be better as "Good Game! Winners: <playername>, <playername>,...

*This deliverable shall deliver a means of identifying

Redundant, perhaps "Delivers a means of..." or "Implement a means of..."

*Unit Table

I agree, it might be interesting to store stuff on a per-unit basis. That said, it may end up as too much data that rarely gets used. Is it possible to remove later easily if that turns out to be the case? If we can scrap it later than I would be in favor of trying it to start, assuming it does not add to the complexity of the implementation. It's a low priority, but possibly interesting idea.

One other thing regarding units, some UMC does a LOT with units and WML. For example:
http://forums.wesnoth.org/viewtopic.php?f=15&t=18919
or
http://forums.wesnoth.org/viewtopic.php?f=15&t=40073
or
http://forums.wesnoth.org/viewtopic.php?f=15&t=21234

So we can't really expect to design something that is going to handle every case perfectly. The priority should be on taking what useful info we can and not breaking under "crazy" conditions. Documenting how things work will also be useful and some of these authors might be REALLY interested in seeing unit stats and willing to work toward complying with guidelines for how to handle their units and WML so that they can be parsed usefully or helping improve how this works in the future. Food for thought.

*Leader Table

I would like to see leader stats, that could be interesting. One thought: if the unit table above is implemented, perhaps just tagging leaders as units and keeping them in there (to be filtered out later by queries) is an option? As you have it outlined is fine too. This is another lower priority but fun idea.

*Brainstorm
*Everyone disconnects : no clear winner.

I think we have to treat this case as an unfinished game and throw it out. Many times MP games are saved to continue later.

* All leaders on all sides except one are dead : Side with leaders remaining win.

In a regular MP game, yes. In a survival style perhaps there are no leaders on the other side but some other WML yet to happen or a turn limit? I forget if this is possible or not these days.

*All players except 1 disconnect : TODO- Decide if game is still multiplayer

This is a tricky case. Usually this would be a game over situation but sometimes not. Every once in a while one side surrenders but the winning or losing player wants to play on a bit to see if it's REALLY lost. I would guess we have to throw these out because it's really hard to tell what should happen if one player continues on in a game.

OTHER NOTES:

Not everything is going to work as nicely as default. As I continue to think about this, it is clear that some UMC will be broken or may not parse well for some reason. There are guidelines to prevent such problems, but it is fair to assume that mistakes will be made and not everyone is going to follow the guidelines perfectly. We should be careful to handle stuff in a way that broken or crazy content doesn't creep in and pollute regular data or cause unforeseen problems.

What happens when two different eras made by different authors have created a WML ability that has different outcomes? For example, two authors implement an ability called improved_magic, but one gives hits 80% of the time and one gives hits 90% of the time. How this is stored and retrieved should be done so as not to gloss over any problems as an apples to apples comparison. Since we would rarely, if ever, want to take data from ALL eras for any given map but we might want to take data from the default era and perhaps a few others to look at them together, this might be best addressed on the storage side or the query side ("duplicate ability/unit, are you sure you wish to continue?" Or even just a warning somewhere for the user to be careful not to combine eras that could produce such results), I'm not really sure.

MultiplayerServers

2014-03-06T13:43:49Z

Happygrue: /* Public Official servers */

The game server runs on TCP port 15000 by default.

== Public Official servers ==
; server.wesnoth.org : accepts up-to-date trunk repository versions and redirects other clients to the appropriate server according to their version, runs on the default port 15000

*Connecting on port 14997 gives the current development version.
*Connecting on port 14998 gives the current stable version.
*Connecting on port 14999 gives the previous stable version.

To connect to a specific port choose "Connect to Server" in the multi-player options list and enter "server.wesnoth.org:#####" where the number signs are the port number.

'''Alternate servers:'''
; server2.wesnoth.org aka gonzo.dicp.de : accepts up-to-date trunk repository versions and redirects other clients to the appropriate server according to their version, runs on the default port 15000

; server3.wesnoth.org aka basilic.tuxfamily.org : accepts up-to-date trunk repository versions and redirects other clients to the appropriate server according to their version, runs on the default port 15000

Usually supported versions include: the current stable release, the old stable release, the current development release, the previous development release (runs only periodically in the transition phase between releases)

== Alternate servers setup by users ==
; wesnoth.geeknode.org : v1.2 dedicated server ([irc://irc.geeknode.org#wesnoth #wesnoth])
; icestation.homeunix.org : Yet another mirror of the official server, located in Russia. Accepts latest development version on port 15000.
; <nowiki>alliance25.hd.free.fr:15000</nowiki> : Another server, located in France. Accepts latest development version of the game on port 15000.
; <nowiki>games.kingshomeworld.com:15000</nowiki> : Server hosted by K.I.M CHAT in Canada. We welcome beginners. Accepts latest stable Current Version release on default port 15000
; <nowiki>allfex.org:15000</nowiki> : Just another server, located in germany. Everyone is welcome. All versions are accepted.
; <nowiki>game.chillat.net:15000</nowiki> : Server hosted by Chillat.net in Sweden, running v1.6. ([http://forums.chillat.net/forum/wesnoth Chillat.net Wesnoth Forum])
; <nowiki>foss.uoa.gr:15000</nowiki> : Server hosted by the Greek FOSS community at the University of Athens, running v1.6.5 (FreeBSD). ([http://foss.uoa.gr/forum/ FOSS-UoA Forum])
; <nowiki>vending-machine.game-server.cc:15000</nowiki> : U.S. West - Any and all players welcome.
; <nowiki>laltromondo.dynalias.net:15000</nowiki> : Debian <del>Lenny Squeeze</del> Wheezy Server located in Italy. Accepts 1.10.x versions of the game on default port 15000.
; <nowiki>thecakeisalie.biz:15000</nowiki> : Debian Lenny x86_64 server in Cairo Egypt. Accepts 1.6.* and 1.8.*, will redirect accordingly based on version (1.8 runs on port 14999). Name registration at http://thecakeisalie.biz/wesnoth
; <nowiki>play.royaldev.org:15000</nowiki> : Debian Wheezy x86_64 server in Portland, Oregon, United States. We accept all players of all versions. ([irc://irc.royaldev.org/#wesnoth #wesnoth])
; vesnod.ceata.org : Trisquel 6 server located in Romania, maintained by Fundația Ceata. Accepts 1.10.x versions of the game on default port 15000.

== Debian Servers ==
Please note that the terms ''Stable'' and ''Testing version'' refers to the Debian distribution, not wesnoth itself. Please check http://packages.debian.org/wesnoth if you are unsure what wesnoth versions they currently refer to.

=== Stable version ===
; <nowiki>www.salokine.org</nowiki> : Lenny version (Contact [[User:Salokine|Salokine]])

[[Category:Playing Wesnoth]]

SoC Ideas Multiplayer Data Analysis

2014-03-03T16:03:41Z

Happygrue: /* Additional Information */

{{SoC2014Idea}}

==Description==
===Improve the automated collection and display of multiplayer game data===
Page for the idea: [[SoC_Ideas_Multiplayer_Data_Analysis]]

Multiplayer games are currently [http://replays.wesnoth.org/ archived]. This includes lots of interesting and potentially useful data, including recruits, deaths, number of turns and other things. The only way to access this information currently is parsing the WML one save file at a time. Additionally, which side(s) won the game is only recorded in some cases. We would like to record which side(s) won or lost (for as many games as possible) and then display useful information about these games for balancing and feedback purposes.

{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
|notcategory=SoC 2014 Not Submitted To Google
|include=#Description
|nottitlematch=SoC2014_Template_of_Student_page
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}

==Additional Information==

The primary use for this would be for multiplayer balancing, both for developers and for authors of UMC. This breaks down into 3 parts.

# '''Implement some way in the Wesnoth client to select a winning side (when it is not otherwise obvious).'''
#*Alter how multiplayer games end in such a way that they must either declare a winning side or have the players select a "continue later" option. Thought needs to be put into how to handle this to include different types of games (regular duels as well as custom scenarios that might end with special conditions). This will allow much of the game data that is already collected to be used more directly for analysis. Many games will no doubt never finish "successfully" due to network disconnections or savegames that are never reloaded, but if most players simply declare a winning side via some interface at the end of the game we should get many good data points. User Made Content (UMC) would also provide good data if the [end_level] tag is correctly implemented.
# '''Implement a replay data analyzation tool that processes replays and save what it finds out in a database.'''
#*Store in a database as much data useful to analysis as is currently possible. Savegames are stored in [[SavefileWML|WML]], which can be parsed by C++, Python and Perl. Some highlights of very useful things:
#** By era, which factions win the most and on which maps.
#** Which side(s) win the most on which maps.
#** Which eras and/or maps see the most games, and their various full-game completion rate.
#** If possible, what difficulty (if applicable to MP campaign or UMC) was selected for the game.
# '''Implement some frontend to query/visualize the data in the database.'''
#*While the first two parts are most important, if time allows it would be great to create a medium to display and filter the data (preferably web-based). Allow for filtering of many different variable with an eye toward being able to expend and add display variables in the future.

'''FAQ'''

'''''Q: Where in the code the data saving takes place?'''''

A: src/server/game.cpp: game::save_replay()

'''''Q: How will I open up the archived replays for data analysis?'''''

A: Using a WML parser you'd go through the replay like the game proper and collect data you think is useful (storing it in the database).

'''''Q: Where would the data analyzation tool live?'''''

A: The analyzation tool would probably be run on the server where also wesnothd runs but it's an independent process, since wesnothd just saves the replay data it has no real idea what's in it.

==Whom to ask about this==

Soliton, happygrue (IRC is preferable)

SoC Ideas Multiplayer Data Analysis

2014-03-03T15:42:31Z

Happygrue: /* Additional Information */

{{SoC2014Idea}}

==Description==
===Improve the automated collection and display of multiplayer game data===
Page for the idea: [[SoC_Ideas_Multiplayer_Data_Analysis]]

Multiplayer games are currently [http://replays.wesnoth.org/ archived]. This includes lots of interesting and potentially useful data, including recruits, deaths, number of turns and other things. The only way to access this information currently is parsing the WML one save file at a time. Additionally, which side(s) won the game is only recorded in some cases. We would like to record which side(s) won or lost (for as many games as possible) and then display useful information about these games for balancing and feedback purposes.

{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
|notcategory=SoC 2014 Not Submitted To Google
|include=#Description
|nottitlematch=SoC2014_Template_of_Student_page
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}

==Additional Information==

The primary use for this would be for multiplayer balancing, both for developers and for authors of UMC. This breaks down into 3 parts.

# '''Implement some way in the Wesnoth client to select a winning side (when it is not otherwise obvious).'''
#*Alter how multiplayer games end in such a way that they must either declare a winning side or have the players select a "continue later" option. Thought needs to be put into how to handle this to include different types of games (regular duels as well as custom scenarios that might end with special conditions). This will allow much of the game data that is already collected to be used more directly for analysis. Many games will no doubt never finish "successfully" due to network disconnections or savegames that are never reloaded, but if most players simply declare a winning side via some interface at the end of the game we should get many good data points. User Made Content (UMC) would also provide good data if the [end_level] tag is correctly implemented.
# '''Implement a replay data analyzation tool that processes replays and save what it finds out in a database.'''
#*Store in a database as much data useful to analysis as is currently possible. Savegames are stored in [[SavefileWML|WML]], which can be parsed by C++, Python and Perl. Some highlights of very useful things:
#** By era, which factions win the most and on which maps.
#** Which side(s) win the most on which maps.
#** Which eras and/or maps see the most games, and their various full-game completion rate.
#** If possible, what difficulty (if applicable to MP campaign or UMC) was selected for the game.
# '''Implement some frontend to query/visualize the data in the database.'''
#*While the first two parts are most important, if time allows it would be great to create a medium to display and filter the data (preferably web-based). Allow for filtering of many different variable with an eye toward being able to expend and add display variables in the future.

FAQ:
Q: Where in the code the data saving takes place?
A: src/server/game.cpp: game::save_replay()

==Whom to ask about this==

Soliton, happygrue (IRC is preferable)

SoC Ideas Multiplayer Data Analysis

2014-03-03T15:23:24Z

Happygrue: /* Improve the automated collection and display of multiplayer game data */

{{SoC2014Idea}}

==Description==
===Improve the automated collection and display of multiplayer game data===
Page for the idea: [[SoC_Ideas_Multiplayer_Data_Analysis]]

Multiplayer games are currently [http://replays.wesnoth.org/ archived]. This includes lots of interesting and potentially useful data, including recruits, deaths, number of turns and other things. The only way to access this information currently is parsing the WML one save file at a time. Additionally, which side(s) won the game is only recorded in some cases. We would like to record which side(s) won or lost (for as many games as possible) and then display useful information about these games for balancing and feedback purposes.

{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
|notcategory=SoC 2014 Not Submitted To Google
|include=#Description
|nottitlematch=SoC2014_Template_of_Student_page
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}

==Additional Information==

The primary use for this would be for multiplayer balancing, both for developers and for authors of UMC. This breaks down into 3 parts that I can see.

# Alter how multiplayer games end in such a way that they must either declare a winning side or have the players select a "continue later" option. This will allow much of the game data that is already collected to be used more directly for analysis. Many games will no doubt never finish "successfully" due to network disconnections or savegames that are never reloaded, but if most players simply declare a winning side via some interface at the end of the game we should get many good data points.
# Store in a database as much data useful to analysis as is currently possible. Savegames are stored in [[SavefileWML|WML]], which can be parsed by C++, Python and Perl. Some highlights of very useful things:
#* By era, which factions win the most and on which maps.
#* Which side(s) win the most on which maps.
#* Which eras and/or maps see the most games, and their various full-game completion rate.
#* If possible, what difficulty (if applicable to MP campaign or UMC) was selected for the game.
# While the first two parts are most important, if time allows it would be great to create a medium to display and filter the data (preferably web-based). Allow for filtering of many different variable with an eye toward being able to expend and add display variables in the future.

==Whom to ask about this==

Soliton, happygrue (IRC is preferable)

SoC Ideas Multiplayer Data Analysis

2014-02-14T18:19:42Z

Happygrue: /* Additional Information */

{{SoC2014Idea}}
A template for the Summer of Code 2014 Idea Page. Copy this to the new idea page, and edit it accordingly.

=Description=
<h2>Improve the automated collection and display of multiplayer game data</h2>
Page for the idea: [[SoC_Multiplayer_Data_Analysis]]

Multiplayer games are currently archived [http://replays.wesnoth.org/] but there is no data stored regarding who won the game. We would like to record which team won (for as many games as possible) and then display information about these games for balancing and feedback purposes.

{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
|notcategory=SoC 2014 Not Submitted To Google
|include=#Description
|nottitlematch=SoC2014_Template_of_Student_page
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}

=Additional Information=

The primary use for this would be for multiplayer balancing both for developers and for authors of UMC. This breaks down into 3 parts that I can see.

1) Alter how multiplayer games end in such a way that they must either declare a winning side or have the players select a "continue later" option. This will allow much of the game data that is already collected to be used more directly for analysis. Many games will no doubt never finish "successfully" due to network disconnections or savegames that are never reloaded, but if most players simply declare a winning side via some interface at the end of the game we should get many good data points.

2) Store in a database as much data useful to analysis as is currently possible. Savegames are stored in WML [http://wiki.wesnoth.org/SavefileWML], which can be parsed by C++, Python and Perl. Some highlights of very useful things:
i) By era, which races win the most and on which maps.
ii) Which side(s) win the most on which maps.
iii) Which eras and/or maps see the most games, and their various full-game completion rate.
iv) If possible, what difficulty (if applicable to MP campaign or UMC) was selected for the game.

3) While the first two parts are most important, if time allows it would be great to create a medium to display and filter the data (preferably web-based). Allow for filtering of many different variable with an eye toward being able to expend and add display variables in the future.

=Whom to ask about this=

Soliton, happygrue (IRC is preferable)

SoC Ideas Multiplayer Data Analysis

2014-02-14T17:53:54Z

Happygrue: /* Description */

{{SoC2014Idea}}
A template for the Summer of Code 2014 Idea Page. Copy this to the new idea page, and edit it accordingly.

=Description=
<h2>Improve the automated collection and display of multiplayer game data</h2>
Page for the idea: [[SoC_Multiplayer_Data_Analysis]]

Multiplayer games are currently archived [http://replays.wesnoth.org/] but there is no data stored regarding who won the game. We would like to record which team won (for as many games as possible) and then display information about these games for balancing and feedback purposes.

{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
|notcategory=SoC 2014 Not Submitted To Google
|include=#Description
|nottitlematch=SoC2014_Template_of_Student_page
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}

=Additional Information=

The primary use for this would be for multiplayer balancing both for developers and for authors of UMC. This breaks down into 3 parts that I can see.

1) Alter how multiplayer games end in such a way that they must either declare a winning side or have the players select a "continue later" option. This will allow much of the game data that is already collected to be used more directly for analysis. Many games will no doubt never finish "successfully", but if most players simply declare a winning side via some interface at the end of the game we should get many good data points.

2) Render as much data useful to analysis as is currently possible. Some highlights of very useful things:
i) By era, which races win the most and on which maps.
ii) Which side(s) win the most on which maps.
iii) Which eras and/or maps see the most games, and their various full-game completion rate.
iv) If possible, what difficulty (if applicable to MP campaign or UMC) was selected for the game.

3) Create a medium to display and filter the data (preferably web-based). Allow for filtering of many different variable with an eye toward being able to expend and add display variables in the future.

=Whom to ask about this=

Soliton, happygrue (IRC is preferable)

SoC Ideas Multiplayer Data Analysis

2014-02-14T17:53:04Z

Happygrue: /* Description */

{{SoC2014Idea}}
A template for the Summer of Code 2014 Idea Page. Copy this to the new idea page, and edit it accordingly.

=Description=
<h2>Improve the automated collection and display of multiplayer game data</h2>
Page for the idea: [[SoC_Multiplayer_Data_Analysis]]

Multiplayer games are currently [[#http://replays.wesnoth.org/|archived]] but there is no data stored regarding who won the game. We would like to record which team won (for as many games as possible) and then display information about these games for balancing and feedback purposes.

{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
|notcategory=SoC 2014 Not Submitted To Google
|include=#Description
|nottitlematch=SoC2014_Template_of_Student_page
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}

=Additional Information=

The primary use for this would be for multiplayer balancing both for developers and for authors of UMC. This breaks down into 3 parts that I can see.

1) Alter how multiplayer games end in such a way that they must either declare a winning side or have the players select a "continue later" option. This will allow much of the game data that is already collected to be used more directly for analysis. Many games will no doubt never finish "successfully", but if most players simply declare a winning side via some interface at the end of the game we should get many good data points.

2) Render as much data useful to analysis as is currently possible. Some highlights of very useful things:
i) By era, which races win the most and on which maps.
ii) Which side(s) win the most on which maps.
iii) Which eras and/or maps see the most games, and their various full-game completion rate.
iv) If possible, what difficulty (if applicable to MP campaign or UMC) was selected for the game.

3) Create a medium to display and filter the data (preferably web-based). Allow for filtering of many different variable with an eye toward being able to expend and add display variables in the future.

=Whom to ask about this=

Soliton, happygrue (IRC is preferable)

SoC Ideas Multiplayer Data Analysis

2014-02-14T17:47:22Z

Happygrue: Created page with "{{SoC2014Idea}} A template for the Summer of Code 2014 Idea Page. Copy this to the new idea page, and edit it accordingly. =Description= <h2>Improve the automated collection ..."

{{SoC2014Idea}}
A template for the Summer of Code 2014 Idea Page. Copy this to the new idea page, and edit it accordingly.

=Description=
<h2>Improve the automated collection and display of multiplayer game data</h2>
Page for the idea: [[SoC_Multiplayer_Data_Analysis]]

Multiplayer games are currently archived but there is no data stored regarding who won the game. We would like to record which team won (for as many games as possible) and then display information about these games for balancing and feedback purposes.

{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
|notcategory=SoC 2014 Not Submitted To Google
|include=#Description
|nottitlematch=SoC2014_Template_of_Student_page
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}

=Additional Information=

The primary use for this would be for multiplayer balancing both for developers and for authors of UMC. This breaks down into 3 parts that I can see.

1) Alter how multiplayer games end in such a way that they must either declare a winning side or have the players select a "continue later" option. This will allow much of the game data that is already collected to be used more directly for analysis. Many games will no doubt never finish "successfully", but if most players simply declare a winning side via some interface at the end of the game we should get many good data points.

2) Render as much data useful to analysis as is currently possible. Some highlights of very useful things:
i) By era, which races win the most and on which maps.
ii) Which side(s) win the most on which maps.
iii) Which eras and/or maps see the most games, and their various full-game completion rate.
iv) If possible, what difficulty (if applicable to MP campaign or UMC) was selected for the game.

3) Create a medium to display and filter the data (preferably web-based). Allow for filtering of many different variable with an eye toward being able to expend and add display variables in the future.

=Whom to ask about this=

Soliton, happygrue (IRC is preferable)

SoC Ideas2014 Template

2014-02-14T17:38:55Z

Happygrue: Undo revision 53087 by Happygrue (talk)

{{SoC2014Idea}}
A template for the Summer of Code 2014 Idea Page. Copy this to the new idea page, and edit it accordingly.

=Description=
<h2>New idea template title</h2>
Page for the idea: [[SoC_Ideas2014_Template]]

Info that will appear on Summer of Code ideas list.

{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
|notcategory=SoC 2014 Not Submitted To Google
|include=#Description
|nottitlematch=SoC2014_Template_of_Student_page
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}

=Additional Information=

=Whom to ask about this=

SoC Ideas2014 Template

2014-02-14T17:37:11Z

Happygrue: Undo revision 53088 by Happygrue (talk)

SoC Ideas2014 Template

2014-02-14T17:35:13Z

Happygrue: /* Whom to ask about this */

SoC Ideas2014 Template

2014-02-14T17:15:55Z

Happygrue: /* Description */

SoC People to bug on IRC

2014-02-07T16:42:48Z

Happygrue: /* Happygrue/Wintermute */

{{SoC2014}}

== 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.

=== Crab_ ===
iurii chernyi (Crab) has joined the team in 2009. He restructured Wesnoth AI as part of GSoC-2009, and is an expert on all aspects of current Wesnoth AI codebase. So, he's the person to ask about anything in '''src/ai'''. He also knows much about campaign units/leaders persistence.

=== 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.

=== 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.

=== Gabriel Morin (gabba) ===

gabba joined the team in 2010 where he participated in GSoC, and is the conceptor and maintainer of Wesnoth's planning system, codenamed "Whiteboard".

=== happygrue/Wintermute ===

Has been involved with multiplayer balance and testing for a number of years. Currently working on balancing the default+khalifate era, but interested in, and often available for, testing various aspects game play or mechanics. A good person to bug about getting feedback from the multiplayer community about any relevant issue.

=== ilor ===
2008 GSoC student, worked on and maintains the new map editor in Wesnoth 1.5/1.6/1.7. 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. He also has limited experience with boost asio.

=== 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.

=== 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.

=== shadowm ===
He has been around since late 2007, and has worked in many areas of the game, including WML event commands handling, image path functions, and the add-ons client code. As an add-on content developer, he also knows a lot about the WML language itself (preprocessor, syntax) and the functionality available in single-player campaigns.

=== 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 ===
Since he is the developer who know most about building under Windows, he 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.

ServerAdministration

2010-04-17T00:19:34Z

Happygrue: /* Links */

== Overview ==

The Wesnoth server, [[wesnothd]] provides a simple interface for administering the server from within the game itself.

To issue an administrative command to the server, you must be connected to the server using Wesnoth, and in the lobby. Any text you type into the chat box that begins with '/query ' will be considered an administrative command instead of a normal chat message. It will not be relayed to other users, but instead treated as a command by the server.

Most commands are not accessible to normal users. They are only accessible once you have authenticated yourself to the server as an administrator. The way to authenticate yourself as an administrator is to use the command,

'''/query admin <password>'''

where <password> is the administrative password to the server. The administrative password is specified as the passwd attribute in wesnothd.cfg. Naturally the password for a server should be kept a secret. One danger is that if you forget to type '/query ' at the start of a command you may accidentally type the password in a chat message, and let all users on the server know it. If you do this, then notify an administrator who has access to the box as soon as possible, so they can reset the password in wesnothd.cfg. We may provide features to prevent this kind of accident in future versions.

A message from the server should tell you that you have successfully authenticated yourself as an administrator. The server will recognize you as an administrator until the next time you log out of the server. If the server has support for accounts it may also remember and authenticate you automatically as an administrator next time.

== Available commands ==

Note: Moderators of the official Wesnoth servers can utilize these commands [[ServerAdministration_FromIRC|via IRC]].

'''/query adminmsg <message>''': sends a message to all administrators and also gets logged in case none is on. You can use this to report abuse, rule violations, etc. (available to non-administrators, duh)

'''/query games''': shows how many games have ended in various ways. (available to non-administrators)

'''/query metrics''': shows a simple metrics report of how the server has been performing. (available to non-administrators)

'''/query netstats''': shows some network stats. (available to non-administrators)

'''/query stats''': shows the current number of users and games. (available to non-administrators)

'''/query wml''': shows stats about WML documents and their current memory consumption. (available to non-administrators)

'''/query status [<nickmask>]''': this command will show you a list of users (matching the nickmask) connected to the server, with IP addresses, and how long they have been connected. Note that IP addresses of users are not available to non-administrators, and should be treated as confidential. When used as a non-administrator it just returns the entry of the user.

'''/query motd [<message>]''': this command sets the message of the day that appears as the first message users get when they log on to the server. You can prefix the message with color formatting as described in [[InterfaceActionsWML#.5Bmessage.5D]]. Without argument it returns the current motd. (available to non-administrators)

'''/query msg <message>''': this command will relay the message 'message' to all users on the server, even if they are in a game. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix the message with color formatting as described in [[InterfaceActionsWML#.5Bmessage.5D]].

'''/query lobbymsg <message>''': this command will relay the message 'message' to all users in the lobby of the server. The message will appear to come from 'server', so you should write your name as part of the message if it is necessary to show who it comes from. You can prefix the message with color formatting as described in [[InterfaceActionsWML#.5Bmessage.5D]].

'''/green <message>''': this command executes the lobbymsg command with green font (alias for '/query lobbymsg @<message>').

'''/red <message>''': this command executes the lobbymsg command with red font (alias for '/query lobbymsg #<message>').

'''/yellow <message>''': this command executes the lobbymsg command with yellow font (alias for '/query lobbymsg <255,255,0><message>').

'''/query clones''': shows a list of all users that have the same IP address as another one.

'''/query kick <mask> [<reason>]''': this command will disconnect the user matching the given nick or ip mask from the server.

'''/query ban <mask> <time> <reason>''': this command will make the server refuse connections from users matching the given IP mask or the IPs of users matching the nick mask. Existing bans (and their reason!) will be overwritten so you can change the reason for a ban by adding it again.

'''/query gban <mask> <group> <time> <reason>''': this command will make a ban that belongs to a group. They function just like ordinary bans but only the group name is mentioned in the ban listing.

'''/query bans''': shows a list of currently banned IP masks and the reasons for the bans.

'''/query kban <mask> <time> <reason>''': this command is equivalent to 'kick <mask>' 'ban <mask> <time> <reason>' -- i.e. bans the users matching the IP mask or the IPs of users matching the nick mask and disconnects them all in one go. The most common way to ban someone from the server.

'''/query unban <ipmask>''': this command removes the specified IP mask from the ban list.

'''/query ungban <group>''': this command removes all bans in the group.

'''/query searchlog <mask>''': this returns the IP a nick matching the mask has used or the nicks that used a matching IP. Unlike status this searches the IP log.

'''/query deny_unregistered_login [yes|no]''': If set to yes the server will refuse to let unregistered users log in. Without an argument the current setting is displayed. There is an alias 'dul' for convenience.

Masks are arguments that can contain wildcards ('*' and '?'). '*' matches any number of characters (including none), and '?' any one character. IP masks are masks that contain at least one '.'.

The time parameter is used to set the time when a ban expires. A simple example is 2D12h which means after 2 days and 12 hours the ban gets removed. Modifiers are: s=seconds, m=minutes, h=hours, D=days, M=months and Y=years (case doesn't actually matter except for minutes (m) and months (M); also you can write the modifiers (partially) out as in 2days12hours). Permanent bans can be set with 'permanent' or '0' as the time argument. We can also set shortcuts like LONG, MEDIUM and SHORT for common ban lengths but none is set yet.

== Future extensions ==

The current administrative interface is fairly primitive. We plan to provide some further extensions in the future, such as,

'''/query mute <nick>''': makes it so that any messages sent by the user with the given nick will not be received by any other user on the server unless they share an IP address with 'nick'. Any games created by 'nick' will likewise not be seen by other users. 'nick' may observe games but will not appear in the observer list, and players of the game will not see any messages they type.

== Links ==
* [[ServerAdministration_FromIRC|Server Administration via IRC]]
* [[MP_CodeOfConduct|Multiplayer Information]]

[[Category:Troubleshooting and Bugs]]

ServerAdministration FromIRC

2010-03-30T18:23:45Z

Happygrue: /* Administration via IRC */

== Overview ==

The official Wesnoth servers can be moderated via IRC from the moderator IRC channel - which you know the location of if you are a moderator.

Lobby chat, games, and other statistics are echoed at [irc://irc.freenode.net/wesnoth-mp-lobby-stable #wesnoth-mp-lobby-stable] and [irc://irc.freenode.net/wesnoth-mp-lobby-dev #wesnoth-mp-lobby-dev].

== Administration via IRC ==

Server administration commands are accessed via IRC by directing them to the lobby bot rather than using "/query" as is done on the server. For an action on the stable server direct commands to "lobby: ", and for the development server "lobby !dev: "

For example:
lobby: kick <mask> [<reason>]
kicks a user from the stable server.

Since knowing where a message is going is important, here is a list of message commands available in the moderation channel, all prefixed by "lobby: " or "lobby: !dev: "

<text> sends a message to all server admins on the server (instead of the adminmsg command).

/msg <text> sends a message to all users on the server, even if they are in a game.

/lobbymsg <text> sends a message to all users in the lobby.

/pm <mask> <text> sends a private message to a user.

== Links ==

* [[ServerAdministration]] for admin commands

ServerAdministration FromIRC

2010-03-30T18:23:29Z

Happygrue: /* Administration via IRC */

== Overview ==

The official Wesnoth servers can be moderated via IRC from the moderator IRC channel - which you know the location of if you are a moderator.

Lobby chat, games, and other statistics are echoed at [irc://irc.freenode.net/wesnoth-mp-lobby-stable #wesnoth-mp-lobby-stable] and [irc://irc.freenode.net/wesnoth-mp-lobby-dev #wesnoth-mp-lobby-dev].

== Administration via IRC ==

Server administration commands are accessed via IRC by directing them to the lobby bot rather than using "/query" as is done on the server. For an action on the stable server direct commands to "lobby: ", and for the development server "lobby !dev: "

For example:
lobby: kick <mask> [<reason>]
kicks a user from the stable server.

Since knowing where a message is going is important, here is a list of message commands available in the moderation channel, all prefixed by "lobby: " or "lobby: !dev: "

<text> sends a message to all server admins on the server (instead of the adminmsg command).

/msg <text> sends a message to all users on the server, even if they are in a game.

/lobbymsg <text> sends a message to all users in the lobby.
/pm <mask> <text> sends a private message to a user.

== Links ==

* [[ServerAdministration]] for admin commands

ServerAdministration FromIRC

2010-03-30T18:23:01Z

Happygrue: /* Administration via IRC */

== Overview ==

The official Wesnoth servers can be moderated via IRC from the moderator IRC channel - which you know the location of if you are a moderator.

Lobby chat, games, and other statistics are echoed at [irc://irc.freenode.net/wesnoth-mp-lobby-stable #wesnoth-mp-lobby-stable] and [irc://irc.freenode.net/wesnoth-mp-lobby-dev #wesnoth-mp-lobby-dev].

== Administration via IRC ==

Server administration commands are accessed via IRC by directing them to the lobby bot rather than using "/query" as is done on the server. For an action on the stable server direct commands to "lobby: ", and for the development server "lobby !dev: "

For example:
lobby: kick <mask> [<reason>]
kicks a user from the stable server.

Since knowing where a message is going is important, here is a list of message commands available in the moderation channel, all prefixed by "lobby: " or "lobby: !dev: "

<text> sends a message to all server admins on the server (instead of the adminmsg command).

/msg <text> sends a message to all users on the server, even if they are in a game.

/lobbymsg <text> sends a message to all users in the lobby.

/pm <mask> <tect> sends a private message to a user.

== Links ==

* [[ServerAdministration]] for admin commands

ServerAdministration FromIRC

2010-03-30T17:36:55Z

Happygrue: /* Overview */

ServerAdministration FromIRC

2010-03-30T17:29:44Z

Happygrue: /* Overview */

== Overview ==

The official Wesnoth servers can be moderated via IRC from the moderator IRC channel, [irc://irc.freenode.net/wesnoth-mp-mod #wesnoth-mp-mod].

Lobby chat, games, and other statistics are echoed at [irc://irc.freenode.net/wesnoth-mp-lobby-stable #wesnoth-mp-lobby-stable] and [irc://irc.freenode.net/wesnoth-mp-lobby-dev #wesnoth-mp-lobby-dev].

== Administration via IRC ==

== Links ==

* [[ServerAdministration]] for admin commands

ServerAdministration FromIRC

2010-03-30T17:27:42Z

Happygrue: /* Overview */

== Overview ==

The official Wesnoth servers can be moderated via IRC from the moderator IRC channel, #wesnoth-mp-mod.

Lobby chat, games, and other statistics are echoed at #wesnoth-mp-lobby-stable and #wesnoth-mp-lobby-dev.

== Administration via IRC ==

== Links ==

* [[ServerAdministration]] for admin commands

ServerAdministration FromIRC

2010-03-30T17:19:53Z

Happygrue: /* Links */

== Overview ==

== Administration via IRC ==

== Links ==

* [[ServerAdministration]] for admin commands

ServerAdministration

2010-03-30T17:15:20Z

Happygrue: /* Available commands */

ServerAdministration

2010-03-30T17:14:52Z

Happygrue:

ServerAdministration FromIRC

2010-03-30T17:11:00Z

Happygrue: Created page with '== Overview == == Administration via IRC == == Links =='

== Overview ==

== Administration via IRC ==

== Links ==

Support

2008-11-10T20:47:22Z

Happygrue: /* Wiki Resources */

__NOTOC__
There are many ways to get help. From online documentation to support from the community on IRC or forums.

== Wiki Resources ==
* [[Play|Online Players Guide]] - Game manual, walkthroughs, strategy guides, and more.
* [[Create|Content-Creation Guide]] - Manual showing how to create new campaigns for Wesnoth.
* [[StartingPoints|Starting Points]] - List of pages to serve as starting point for diving deeply into the wiki...
* [[MP_CodeOfConduct | Multiplayer Information ]] - Info about server moderators, useful MP commands, and our online Code of Conduct.

== Reporting Bugs ==
If you are experiencing problems, you should consider [[ReportingBugs|reporting a bug]].

== Community ==

When asking for help with some technical problem in the game forums, please provide the following information:
* which operating system do you use (e.g. Windows, Linux, Mac OSX)
* which version of Wesnoth do you use (it is displayed in the bottom left corner of title screen)
* contents of file "stderr.txt"
** on MS Windows, it is here: "C:\Program Files\Wesnoth\stderr.txt"

=== Forums ===
* [http://www.wesnoth.org/forum/ Official Wesnoth forums]
* [[Wesnoth_Acronyms_and_Slang|Wesnoth Acronyms]] - forum lingo
* [http://www.wesnoth.cn Chinese wesnoth forums]
* [http://wif.altervista.org/index.php Wesnoth Italian Forums (W.I.F)]

=== IRC ===
If you don't know what IRC is, check out [http://www.irchelp.org/ irchelp].

* [irc://irc.freenode.net/wesnoth #wesnoth]
* [irc://irc.freenode.net/wesnoth-dev #wesnoth-dev]
* [irc://irc.freenode.net/wesnoth-mp #wesnoth-mp]
* [irc://irc.freenode.net/wesnoth-music #wesnoth-music]
* [irc://irc.freenode.net/wesnoth-umc-dev #wesnoth-umc-dev]
* [irc://irc.tweakers.net/wesnoth #wesnoth (Dutch channel)]
* [irc://irc.freenode.net/wesnoth-de #wesnoth-de (German channel)]
* [irc://irc.syrolnet.org/WIF #WIF (Italian channel)]
You can also see the [http://irclog.wesnoth.org/ logs].

=== Mailing Lists ===
* [https://mail.gna.org/listinfo/wesnoth-dev/ wesnoth-dev] ([https://mail.gna.org/public/wesnoth-dev/ archives])
* [https://mail.gna.org/listinfo/wesnoth-commits/ wesnoth-commits] ([https://mail.gna.org/public/wesnoth-commits/ archives])
* [https://mail.gna.org/listinfo/wesnoth-i18n/ wesnoth-i18n] ([https://mail.gna.org/public/wesnoth-i18n/ archives])

=== Other Servers List ===
see [http://www.wesnoth.org/wiki/MultiplayerServers here]

[[Category:Troubleshooting and Bugs]]

Play

2008-11-10T20:44:56Z

Happygrue: /* Playing Battle for Wesnoth */

== Getting Battle for Wesnoth ==
* [[Description|About the project]]
* [[Download|Downloads and Source Code Page]]
* [[CompilingWesnoth| Compiling Wesnoth]]
* [[WesnothBinariesLinux| Binary Installation -- the easy way]]

== Playing Battle for Wesnoth ==
<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-1.4-8.jpg http://www.wesnoth.org/images/sshots/wesnoth-1.4-8-175.jpg]
<div class="thumbcaption">The Elves Besieged</div></div>
</div>

* [[GettingStarted|Get Started]]
* [[WesnothManual|Game Manual]]
* [[BasicStrategy|Basic Tactics]]
* [[MainlineCampaigns|Walkthroughs of Official Campaigns]]
* [[UserScenarios | User-made Add-On Campaigns]]
* [[Competitive_Gaming | Competitive Gaming]]
* [[MP_CodeOfConduct | Multiplayer Information ]]

* [[FAQ]]

== Advanced Players ==
* [[CommandMode|Debugging and Multiplayer Command Reference]]
* [[AdvancedTactics|Advanced Tactics]]
* [http://units.wesnoth.org/ Units Reference]
* [[MultiplayerServers|Multiplayer Servers]]
* [[How to play...|The "How to play" Series]]

== The world of Wesnoth ==
<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-map-1.jpg http://www.wesnoth.org/images/sshots/wesnoth-map-1-175.jpg]
<div class="thumbcaption">Wesnoth and Surrounding Lands</div></div>
</div>

* [[History of Wesnoth|The history of Wesnoth]]
* [[Geography of Wesnoth|The geography of Wesnoth]]
* [[WesnothFigures|Notable figures of Wesnoth]]
* [[Races|The races of creatures in Wesnoth]]
* [[Poetry of Wesnoth|Wesnothian poetry]]

== Miscellaneous ==
* [[WhatArePlayersSaying|Comments from Wesnoth Players]]
* [[WesnothReviews|Third party Wesnoth reviews]]
* [[Screenshots]]
* [[FAQ#Do_you_want_help_making_this_game.3F_How_can_I_help.3F|Help to improve the game]]
* A Wesnoth [[Glossary]]
* [[The Observer|The Observer]] -- The Unofficial Wesnoth Newspaper
* [http://wesnoth.dbzer0.com/blog/ The Wesnoth Journals] -- A collaborative Wesnoth blog.
* [[RelatedTools|Related Tools]]
__NOTOC__

[[Category:Playing Wesnoth]]

Wesnoth Acronyms and Slang

2008-09-06T03:53:00Z

Happygrue: /* Unit Names */

Use the following list to demystify the various (mostly wesnoth specific) acronyms you may run into at the forum.



== Names of Mainline Campaigns and Scenarios ==

*AoI - "An Orcish Incursion"
*DiD - "Descent into Darkness"
*EI - "The Eastern Invasion"
*HttT - "Heir to the Throne"
** BoP - "Bay of Pearls"
** DD - "Dwarven Doors"
** HotNE - "Home of the North Elves"
** IotD - "Isle of the Damned"
** RtW - "Return to Wesnoth"
** SoE - "Siege of Elensefar"
** SoF - "Scepter of Fire"
** TotC - "Test of the Clans"
** VoD - "Valley of Death"
*NR - "Northern Rebirth"
*SoF - "Sceptre of Fire"
*SotBE - "Son of the Black Eye"
*TB - "A Tale of Two Brothers"
*THoT - "The Hammer of Thurgasan"
*TRoW - "The Rise of Wesnoth"
*TSG - "The South Guard"
*UtBS - "Under the Burning Suns"

== Unofficial Campaigns ==

*FtF - "Flight to Freedom" (campaign name)
*IftU - "Invasion from the Unknown" (campaign name)
*LoW - "Legend of Wesmere" (campaign name)
*SE - "Saving Elensefar" (campaign name)

== Unit Names ==

*bird - usually Gryphon Rider/Master (knaglans), or occasionally a Falcon or Eagle Rider from the [[Extended Era]] Aragwaith and Kalifa factions.
*DA - Dark Adept (undead)
*fish - Merman (loyalists or rebels) or Naga Fighter (northerners)
*gobo - An affectionate, if somewhat derogatory term for the Goblin Spearman
*gunner - Dwarvish Thunderer/Thunderguard/Dragonguard (knaglans)
*HI - Heavy Infantryman (loyalists)
*MoL - Mage of Light (loyalists or rebels)
*Ulf - Dwarvish Ulfserker (knaglans)
*WC - Walking Corpse (undead)
*zombie - Walking Corpse

== Other, Wesnoth-specific ==

*AMLA - After Maximum Level Advancement
*AoH - Age of Heroes
*BfW - Battle for Wesnoth (the name of the game)
*BWH - Been suggested before. We think it's a good idea. Hope to add it eventually.
*CABD - Can Already Be Done, e.g., you can already create custom unit abilities via WML.
*CtH - Chance to Hit (also C2H)
*CtBH - Chance to Be Hit (also C2BH)
*CtK - Chance to Kill (also C2K)
*CtBK - Chance to Be Killed (also C2BK)
*EP - Elvish Pillager, moderator and great man :) at forum
*FoW - Fog of War (i.e. fog)
*FFA - Free For All (playing a map with >2 players without teams)
*FPI - Frequently Posted Idea (read the [http://www.wesnoth.org/forum/viewtopic.php?t=1158|FPI Post] from the Ideas Forum)
*HANE—EtH - Hexes Are Not Evil - Embrace the Hex
*HAPMA - Hexes Are Possibly Miles Across - http://www.wesnoth.org/forum/viewtopic.php?t=1882
*HP - Hit points
*IIRWIIR - It Is Ready When It Is Ready
*KISS - Keep It Simple, Stupid: Applies to coding, not game rules (although indirectly it does): see [[WesnothPhilosophy]]
*MP - Multiplayer or Movement Points
*N3T - No 3-Teams; A belief stating that contests between three equal and opposing forces are inherently unbalanced
*OAB - Options Are Bad; In reference to gameplay, not user interface options. Mostly used by Turin. See also [[FrequentlyProposedIdeas]] (idea #1)
*OFWRA - Old Flame War Revival Alert; In other words, we have discussed this before and have no interest in discussing it again, especially if it got ugly
* OOS - Out Of Synch - an error generated by Wesnoth. OOS errors occur when game data for one player is different/incompatible from the others
* PoD - Paths of Daggers, the name of a 2v2 multiplayer map.
*RiPLIB - Reduction in Power when Levelling Is Bad: means that when a unit upgrades, at least one of its options should be strictly superior to the original unit. [http://www.wesnoth.org/forum/viewtopic.php?t=1423 Reference 1] / [http://www.wesnoth.org/forum/viewtopic.php?t=7205 Reference 2]
*RPG - Role Playing Game - [http://www.wesnoth.org/forum/viewtopic.php?t=4385 1)] Wesnoth's experience system. <nowiki>2)</nowiki> An "RPG-style" game on the MP server means the primary focus will be walking your leader-units through a scripted storyline involving map exploration and lots of WML.
*SLF - [[StandardLocationFilter]]
*SP - Single Player (Campaigns)
*SUF - [[StandardUnitFilter]]
*ToD - Time of Day
*TWP - The Wesnoth Philosophy: [[WesnothPhilosophy]]
*UMC - User Made Campaign or User Made Content (any add-on not packaged with Wesnoth)
*WICOT - WML is capable of this (the requested feature is already possible to script, so no need to hard-code it in C++)
*WINR - Wesnoth Is Not Realistic
*WIN_ - Wesnoth Is Not... (Warcraft, Lord of the Rings, medieval Europe, an RPG, a wargame, a war simulation, etc.)
*WML - Wesnoth Markup Language: [[ReferenceWML]]
*XP - Experience
*ZoC - Zone of Control

== General Acronyms ==

*AFaICT - As Far as I Can Tell (A statement with a disclaimer on truthfulness)
*AFaIK - As Far as I Know (A statement with a disclaimer on truthfulness)
*AfK - Away from the Keyboard
*ASaP - As Soon as Possible
*BRB - Be Right Back
*BtW - By the Way (A statement with a disclaimer on relevance)
*EV - Expected Value
*FYI - For Your Information
*GtG - Got to Go
*IIRC - If I Recall Correctly (A statement with a disclaimer on truthfulness)
*IMHO - In My Humble Opinion (A statement with a disclaimer on objectiveness)
*IMO - In My Opinion
*LTNS - Long Time No See
*OMG - Oh My God
*OT - Off Topic: can refer either to the forum category (http://www.wesnoth.org/forum/viewforum.php?f=11) or to spam
*OtOH - On the Other Hand (A contrast)
*RotFL - Rolling on the Floor Laughing; also RoFL
*RNG - Random Number Generator
*RtFM - Read the F***ing Manual
*RTS - Real Time Strategy Game - as opposed to a turn-based game like Wesnoth
*SVN - Subversion -- the bleeding-edge up-to-the-minute current version of Wesnoth [[WesnothSVN]] ([[What_Is_SVN]])
*TBS - Turn Based Strategy Game, like Wesnoth

[[Category:World of Wesnoth]]

Wesnoth Acronyms and Slang

2008-06-08T03:03:03Z

Happygrue: /* Other, Wesnoth-specific */

Use the following list to demystify the various (mostly wesnoth specific) acronyms you may run into at the forum.



== Names of Mainline Campaigns and Scenarios ==

*AoI - "An Orcish Incursion"
*DiD - "Descent into Darkness"
*EI - "The Eastern Invasion"
*HttT - "Heir to the Throne"
** BoP - "Bay of Pearls"
** DD - "Dwarven Doors"
** HotNE - "Home of the North Elves"
** IotD - "Isle of the Damned"
** RtW - "Return to Wesnoth"
** SoE - "Siege of Elensefar"
** SoF - "Scepter of Fire"
** TotC - "Test of the Clans"
** VoD - "Valley of Death"
*NR - "Northern Rebirth"
*SoF - "Sceptre of Fire"
*SotBE - "Son of the Black Eye"
*TB - "A Tale of Two Brothers"
*THoT - "The Hammer of Thurgasan"
*TRoW - "The Rise of Wesnoth"
*TSG - "The South Guard"
*UtBS - "Under the Burning Suns"

== Unofficial Campaigns ==

*FtF - "Flight to Freedom" (campaign name)
*IftU - "Invasion from the Unknown" (campaign name)
*LoW - "Legend of Wesmere" (campaign name)
*SE - "Saving Elensefar" (campaign name)

== Unit Names ==

*bird - usually Gryphon Rider/Master (knaglans), or occasionally a Falcon or Eagle Rider from the [[Extended Era]] Aragwaith and Kalifa factions.
*DA - Dark Adept (undead)
*fish - Merman (loyalists or rebels) or Naga Fighter (northerners)
*gunner - Dwarvish Thunderer/Thunderguard/Dragonguard (knaglans)
*HI - Heavy Infantryman (loyalists)
*MoL - Mage of Light (loyalists or rebels)
*Ulf - Dwarvish Ulfserker (knaglans)
*WC - Walking Corpse (undead)
*zombie - Walking Corpse

== Other, Wesnoth-specific ==

*AMLA - After Maximum Level Advancement
*AoH - Age of Heroes
*BfW - Battle for Wesnoth (the name of the game)
*BWH - Been suggested before. We think it's a good idea. Hope to add it eventually.
*CABD - Can Already Be Done, e.g., you can already create custom unit abilities via WML.
*CtH - Chance to Hit (also C2H)
*CtBH - Chance to Be Hit (also C2BH)
*CtK - Chance to Kill (also C2K)
*CtBK - Chance to Be Killed (also C2BK)
*EP - Elvish Pillager, moderator and great man :) at forum
*FoW - Fog of War (i.e. fog)
*FFA - Free For All (playing a map with >2 players without teams)
*FPI - Frequently Posted Idea (read the [http://www.wesnoth.org/forum/viewtopic.php?t=1158|FPI Post] from the Ideas Forum)
*HANE—EtH - Hexes Are Not Evil - Embrace the Hex
*HAPMA - Hexes Are Possibly Miles Across - http://www.wesnoth.org/forum/viewtopic.php?t=1882
*HP - Hit points
*IIRWIIR - It Is Ready When It Is Ready
*KISS - Keep It Simple, Stupid: Applies to coding, not game rules (although indirectly it does): see [[WesnothPhilosophy]]
*MP - Multiplayer or Movement Points
*N3T - No 3-Teams; A belief stating that contests between three equal and opposing forces are inherently unbalanced
*OAB - Options Are Bad; In reference to gameplay, not user interface options. Mostly used by Turin. See also [[FrequentlyProposedIdeas]] (idea #1)
*OFWRA - Old Flame War Revival Alert; In other words, we have discussed this before and have no interest in discussing it again, especially if it got ugly
* OOS - Out Of Synch - an error generated by Wesnoth. OOS errors occur when game data for one player is different/incompatible from the others
* PoD - Paths of Daggers, the name of a 2v2 multiplayer map.
*RiPLIB - Reduction in Power when Levelling Is Bad: means that when a unit upgrades, at least one of its options should be strictly superior to the original unit. [http://www.wesnoth.org/forum/viewtopic.php?t=1423 Reference 1] / [http://www.wesnoth.org/forum/viewtopic.php?t=7205 Reference 2]
*RPG - Role Playing Game - [http://www.wesnoth.org/forum/viewtopic.php?t=4385 1)] Wesnoth's experience system. <nowiki>2)</nowiki> An "RPG-style" game on the MP server means the primary focus will be walking your leader-units through a scripted storyline involving map exploration and lots of WML.
*SLF - [[StandardLocationFilter]]
*SP - Single Player (Campaigns)
*SUF - [[StandardUnitFilter]]
*ToD - Time of Day
*TWP - The Wesnoth Philosophy: [[WesnothPhilosophy]]
*UMC - User Made Campaign or User Made Content (any add-on not packaged with Wesnoth)
*WICOT - WML is capable of this (the requested feature is already possible to script, so no need to hard-code it in C++)
*WINR - Wesnoth Is Not Realistic
*WIN_ - Wesnoth Is Not... (Warcraft, Lord of the Rings, medieval Europe, an RPG, a wargame, a war simulation, etc.)
*WML - Wesnoth Markup Language: [[ReferenceWML]]
*XP - Experience
*ZoC - Zone of Control

== General Acronyms ==

*AFaICT - As Far as I Can Tell (A statement with a disclaimer on truthfulness)
*AFaIK - As Far as I Know (A statement with a disclaimer on truthfulness)
*AfK - Away from the Keyboard
*ASaP - As Soon as Possible
*BRB - Be Right Back
*BtW - By the Way (A statement with a disclaimer on relevance)
*EV - Expected Value
*FYI - For Your Information
*GtG - Got to Go
*IIRC - If I Recall Correctly (A statement with a disclaimer on truthfulness)
*IMHO - In My Humble Opinion (A statement with a disclaimer on objectiveness)
*IMO - In My Opinion
*LTNS - Long Time No See
*OMG - Oh My God
*OT - Off Topic: can refer either to the forum category (http://www.wesnoth.org/forum/viewforum.php?f=11) or to spam
*OtOH - On the Other Hand (A contrast)
*RotFL - Rolling on the Floor Laughing; also RoFL
*RNG - Random Number Generator
*RtFM - Read the F***ing Manual
*RTS - Real Time Strategy Game - as opposed to a turn-based game like Wesnoth
*SVN - Subversion -- the bleeding-edge up-to-the-minute current version of Wesnoth [[WesnothSVN]] ([[What_Is_SVN]])
*TBS - Turn Based Strategy Game, like Wesnoth

[[Category:World of Wesnoth]]

FAQ

2008-05-14T18:57:43Z

Happygrue: /* There's too much luck in this game! */

=Frequently Asked Questions=

== General ==

===What is Battle for Wesnoth?===
Battle for Wesnoth is a fantasy turn-based strategy game.

===What license is the game distributed under?===
The project is distributed under the [http://www.fsf.org/copyleft/gpl.html GPL]. All contributors retain copyright on the portions of the project that they contribute. For more information, see [[Wesnoth:Copyrights]].

===How to get informed about new releases?===
Subscribe to new releases at [http://freshmeat.net/subscribe/38720/?url=%2Fprojects%2Fwesnoth%2F Freshmeat].

===A new version is out, but where is the download for [Windows, Mac OS, etc.]?===
The downloads are NOT part of the official project. The BFW team only releases the game's source code. Binary executables or applications are always contributed by community volunteers. If not for these volunteers, there would never be any downloads for us to enjoy. The volunteers compile the game and upload it on their own time, and sometimes they cannot do this in a timely fashion (or at all, at times) Although there are usual packagers designated for each operating system, there are times when other members of the community are asked to step in and contribute when the usual people cannot.

Every time a new version is released, the usual volunteers are always notified by the project leaders. '''Please refrain from making forum posts asking where your download is''' because it doesn't help anything - the packagers already know, and they will get to it as soon as they can. In the past, the Windows and Mac communities have come together to produce home-grown unofficial builds for the community to use, and the renewed interest in community and learning how to compile is generally a good thing.

===Why doesn't Wesnoth have my favorite feature?===
Because we are building this game for ourselves, to suit our own preferences. We're not building the game for you, in large part because this is our hobby, not our job; whether you like it or not is immaterial to us.
You may wonder, then, what the point is of soliciting ideas, as we do on the forum. We, the developers, have certainly come up with many good ideas on our own, but our players often do as well, and generally ones we don't think of ourselves. If a player comes up with an idea we like, we might implement it. Not because they asked for it, but because of its own merits as an addition to our game.

The beautiful thing about the license our game is distributed under, as compared to closed-source, commercial games, is that if you want that feature badly enough, you can take the code and art of our game and modify it yourself; you are free to re-use any work in Wesnoth, as long as you follow the rules of the [http://www.fsf.org/copyleft/gpl.html GPL]. From this, you can build a game exactly the way that you like. Just don't expect us to build that game for you. Building this game is our hobby, not our profession, and you did not pay us to make it; rather, we are the ones who have paid for it, in time and labor.

===Do you want help making this game? How can I help?===
Yes, we want your help. Whether you're a programmer, artist, musician, writer, translator, level designer, playtester, or just have some great suggestions, you're welcome to contribute. How? You can:
* join the [http://www.wesnoth.org/wiki/Project Project]
* share your point of view at the [http://www.wesnoth.org/forum/ Forum]
* talk with us on [irc://irc.wesnoth.org/wesnoth IRC]
* report bugs you find at [[ReportingBugs]]
* update the wiki
* play against us via the Multiplayer menu
* vote for Wesnoth at your favorite gaming web site
* Spread the word!

=== What are the system requirements? ===

We are not completely certain, but an x86 running at 400 MHz with 128MB RAM should be adequate for versions 1.02 and below. For versions 1.1 and up we recommend a computer with at least 1 GHz and 512 MB RAM if you run KDE or Gnome as Windowmanager (The game itself needs about 100 MB RAM). Slower machines will have trouble scrolling large maps or processing AI turns with many units. See the [http://www.wesnoth.org/forum/viewtopic.php?t=7384 forum thread] about minimum and recommended system requirements.

=== I'm bored; how do I speed the game up? ===

There are several preferences you can change to shorten the time that the AI takes to make its moves. "Accelerated Speed" will make units move and fight faster. "Skip AI Moves" will not show the AI's units moving from hex to hex. Finally, you can turn off all combat animations via the "Show Combat" option on the Advanced tab.

=== My computer is too slow; how do I speed the game up? ===

First, turn off the music and sound effects. Turning off the color cursors will make your cursor respond faster. If scrolling the map is slow, run the game in "Full Screen" mode, not in a window. Turn off combat animations via the "Show Combat" option on the Advanced tab. You can try turning off halos and combat results, but this might make gameplay more difficult.
For some tips on tweaking the startup, see [[CustomizingStartup]].

== Gameplay and Controls ==

=== How do I learn to play? ===

If you just want to jump right in, start the game and play the tutorial. If you like reading documentation, see [[WesnothManual]], which is also distributed as a PDF file. At any time while playing, you can select help from the menu button (or hit F1). The online help is quite extensive and provides information on terrains, weapons, traits, abilities, units and a good overview of how to play.

=== My unit leveled up but didn't improve. What happened? ===

This is called "After Maximum Level Advancement" or AMLA for short. While most level 0, 1, and 2 units can advance, some cannot. However, some level 3 units can advance to level 4, or even 5. You can see whether a unit can advance further by right clicking and selecting "description."

After a unit reaches the highest level it can get, every time it gains 150 experience points (gets progressively more) it gains 3 hitpoints. This is a minor bonus so that experience gained by maxed out units is not altogether wasted. It is generally better to give experience to lower level units, rather than continue to advance units that have reached their maximum level.

=== I tried to trap an enemy with several weak units, but it still escaped. What happened? ===

Most units exert a zone of control (or ZOC). IF an enemy moves into one of the six adjacent hexes, the zone of control will prevent it from moving any farther. However some weak units are level 0, meaning they are so weak that they do not have a ZOC. You can still surround an enemy unit entirely with level 0 units to keep it from escaping, but if there is any gap in your ranks, it could escape.

Also, some units have the "skirmish" ability, which allows them to ignore ZOCs.

=== How can I see where an enemy unit can move next turn? ===

During your turn you can click on an enemy unit. Wesnoth will highlight all the hexes the unit can move to in the next turn. This is useful when trying to arrange your units to block an enemy's movement.

=== There's too much luck in this game! ===

Sooner or later, you will become frustrated when your archmage with four 70% attacks misses all four times. This does not mean that the AI is cheating or the random number generator is futzed. It means you are noticing random negative events more than positive ones. During the development of the game, many mathematicians have done sophisticated statistical analysis of the combat system. Likewise, programmers have examined the random number generator. No flaws have been found, so streaks of "bad" and "good" luck should just be accepted as part of having randomness in Wesnoth. A more detailed rational and discussion of the role that randomness plays in Wesnoth can be found [http://www.wesnoth.org/forum/viewtopic.php?f=6&t=21317&start=0&st=0&sk=t&sd=a here].

Since Wesnoth is GPLed, it is possible that a new development team will someday "fork" the source and produce a version more like Heroes of Might & Magic, with less or no randomness. Until then, don't charge with your horsemen against troll rocklobbers at night...

=== The (random unit) is overpowered/underpowered! ===

The development team has spent years tweaking the units in the game. Each unit has had its gold cost, attack types, combat damage, defensive values, resistances, upgrade paths, and other stats carefully scrutinized and loudly discussed in the forum. However, the game code and the units were being modified right up until the 1.0 release, so some unbalanced units may have slipped through.

If you have evidence to back up your claim, search the forum for past discussions about this unit, and then try posting.

=== The (random scenario) is too hard/easy! ===

See above answer about random units.

=== What do the different difficulty levels do? ===

That depends on the scenario. Usually, the opponent will get more money and be able to recruit higher-level units at higher difficulty levels, and you will have fewer turns available.

== Maps, Scenarios and Campaigns ==

=== How do I beat scenario _______ ? ===

If you are stuck on a scenario in a campaign, you'll probably find a walkthrough at [[MainlineCampaigns]]. Or check out the "Strategies and Tips" forum at http://www.wesnoth.org/forum/viewforum.php?f=3

=== How do I download user campaigns? ===
Choose "Campaigns" in the main Wesnoth menu. Then scroll down to the bottom and choose "Get More Campaigns..." or since 1.1.5 there is a "Get add-ons" button in the main menu. This connects you to the campaign server. In the campaign server you can view a list of all available campaigns and download them, as well as posting or deleting your own campaigns.

If you are behind a firewall you may not be able to connect to the campaign server. In this case try to download the campaign directly from the campaign server through the web interface at http://wolff.to/campaigns/list.html. If you know how to change your firewall settings, then you should open port 15003 (version 1.1.1 and up) or port 15002 (versions 1.1.0 and lower). For added security, you can restrict traffic over those ports to the campaign server's IP address (currently 88.191.12.200).

=== Are there any tools to help me create maps and scenarios? ===
Yes, there is a tool called wesnoth_editor. It is a normal map-editor that should be a good help for creating the plain maps. For creating the scenarios there already is a scenario-editor included in the mac build. But this editor is rather outdated and it exists only for MacOS X. At the moment some community members are working on creating a nice and working scenario editor. You can have a look at the [http://www.wesnoth.org/forum/viewtopic.php?t=6925 forum post] about this tool. You will also find more info at [[CampGen]].

=== What are the .cfg files and how can I edit them? ===

The .cfg files are plain text files, just saved with a file extension ".cfg". You can create and edit them using normal text editors; just save the files in correct format.

Please note that some Windows programs like to add a ".txt" extension, so the file is instead of "my_scenario.cfg" saved as "my_scenario.cfg.txt". And then the Windows Explorer will hide the ".txt" extension, so you may not notice it.

'''Notepad''': After you create a document, click "File", "Save as..." and select "Save as type: All files". To open the document, click "File", "Open..." and select "Files of type: All files (*.*)". If you open someone else's document, and the end-of-line symbols are displayed as small rectangles, you have to use another editor.

'''WordPad''': After you create a document, click "File", "Save as..." and select "Save as type: Text Document". After the document is saved, close WordPad and remove the ".txt" extension from file. To open the document, click "File", "Open..." and select "Files of type: All documents (*.*)".

=== I already created a campaign and published it on the campaign server. How can I get translations for the campaign? ===
Just have a look at [[WesCamp]]. This project is the easiest way to get translations for your campaign. All the info you need you can find at [[WesCamp]].

===How do I place an object or unit on my map with the map editor?===
You can't. You need to make a multiplayer scenario file. There are more details on the [[BuildingMaps|maps]] page.

== Multiplayer ==

===How do i connect to a multiplayer server, when i sit behind a restrictive Firewall?===

You have to open for TCP on port 14999 to play multiplayer games over the internet. For added security, you can restrict access to the server's IP address (currently 84.207.24.9 for the official server).

===How to find players for multiplayer game?===
Hang around for a while on multiplayer servers and you might find someone to play with. If you observe other people playing you will get informed when someone joins the servers. Maybe you find someone willing to play in the irc channel dedicated to mp: #wesnoth-mp at irc.freenode.net.
You can also join #wesnoth at irc.freenode.net.

===How to save and load a multiplayer game===

Save the game. Give it a good name, so that you can find it among the other saved games.

Create new game. (Give it a name like "private game for X and Y", so that other players will not try joining it, and you do not have to explain or kick them.) The first item in the map/scenario list is "Saved games", select this. Choose the saved game. Wait for the other player(s) to connect. Start the game.

===How can I make my computer into a dedicated Wesnoth server?===

To setup a dedicated Wesnoth server, you have to compile the game with the "--enable-server" flag, and after you install, simply run wesnothd from the console. This will start the server, listening on TCP port 15000. To compile the server only you can use the flags "--disable-game --enable-server". If you aren't using a linux or mac operating system, there are a few ways you can compile on Windows...here is one way http://www.wesnoth.org/wiki/CompilingWesnoth/CrossCompiling

===Which versions of Wesnoth can play together?===

I'm on a MAC, and my friends are on XP. I would like to play together with them. Is this currently possible?

YES! All you need is to have the same version number.

For a list of Mac-XP-compatible games (including BfW) see: http://www.insidemacgames.com/forum/index.php?showtopic=21818

== Translations ==

===I selected an asian translation and am not able to see the letters correctly. What happened?===

Since the size of the necessary fonts is too large, you'll need to download them separately (if you don't already have them). After that, simply copy the font to the '''fonts/''' directory in your wesnoth installation.
* Chinese font: [http://ftp.debian.org/debian/pool/main/t/ttf-arphic-gkai00mp/ttf-arphic-gkai00mp_2.11.orig.tar.gz gkai00mp_2.11.orig.tar.gz (2.6 MB)]

Untar it into your home directory, and move this file ''gkai00mp.ttf'' into the '''wesnoth/fonts''' folder.

* Japanese font: [http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/*checkout*/sqs-xml/sqs-font/sazanami-gothic.ttf sazanami-gothic.ttf (7.3 MB)]

If you have further questions have a look at [[WesnothAsianLanguages|this]] page.

== Other Questions You Have ==

The best way to get answers to less-frequently asked questions is by visiting the [http://www.wesnoth.org/forum BFW forum]. There are plenty of people willing to help. Make sure you read ALL of the forum sticky notes and announcements before posting.

[[Category:Troubleshooting and Bugs]]

DeveloperGuide

2007-08-09T15:48:34Z

Happygrue: /* See also */

* setting up developer SVN access: https://gna.org/svn/?group=wesnoth
* Keep the commit easy to revert if need be
* no huge commit (hard to review), so when possible maybe split it in working part with info about where you are going
* be on #wesnoth-dev IRC channel and coordinate with other developers
* code should compile and work after commit
* Don't mess with the art or music without approval from one of the art and music people.
* clear commit message (can be several lines)
* mention "bug #1234" in the commit message for automatic cc to that gna bug number
* don't forget changelog
* change status of fixed bugs to "Fixed" when committed
* change status of fixed bugs to "Closed" when released (as stable or devel version)
** if the bug is svn only (something that was existing as bug in svn but in no release) you can directly close the bug after fixing it
* register to commit mailing list: https://mail.gna.org/listinfo/wesnoth-commits
** or get the list moderator to approve commit messages from you otherwise
* don't forget http://www.wesnoth.org/wiki/EasyCoding if you're ever out of ideas :)

* threading model: SDL threads via src/thread.hpp
** synchronization model
*** avoid multi-threading code as much as possible
*** if you don't see threading code you probably don't need to learn about it

== See also ==
* [[Project#Developers]]
* [[WesnothSVN]]

[[Category:Committers]]

Project

2007-05-27T14:53:02Z

Happygrue: /* Developers */

The Battle for Wesnoth is a [http://gna.org/projects/wesnoth/ Gna! project]. See also the [http://freshmeat.net/projects/wesnoth/ project] and [http://freshmeat.net/project-stats/view/38720/ stats] at [http://www.freshmeat.net/ freshmeat].

There are also Wesnoth pages in other languages:
French ([http://tournoiswesnoth.frbb.net/ 1], [http://wesnothfr.ww7.be/ 2]),
[http://wesnoth.fw.hu/ Hungarian],
[http://wikiwiki.jp/wesnoth/ Japanese],
[http://www.wesnoth.pl/ Polish],
[http://perso.wanadoo.es/wesnoth/ Spanish].

== Artists ==
Graphic artists and musicians usually meet on the [http://www.wesnoth.org/forum/ forum].
* [http://www.wesnoth.org/forum/viewforum.php?f=9 Artwork development forum]
* [http://www.wesnoth.org/forum/viewforum.php?f=14 Music development forum]

== Developers ==
Coders can help fixing [http://bugs.wesnoth.org bugs], adding new features...
* [[CodingStandards]]
* [[Roadmap]]
* [http://devdocs.wesnoth.org/ Documentation] - generated and uploaded two times every day (05:05 and 17:05 GMT+2).
* [[WesnothSVN]]

== Translators ==
* [[WesnothTranslations]]
* [http://gettext.wesnoth.org Statistics]
* [[WesCamp|Translating User made Campaigns (featuring wescamp-i18n)]]

{{Home}}

WesnothRepository

2007-05-27T11:18:45Z

Happygrue: added link to SVN on Windows

{{Compiling Wesnoth}}
== SVN ==

Wesnoth development currently uses the Subversion
software tool to keep developers in sync with each other. See the
[http://svnbook.org SVN book] for
more on how to use Subversion.

== Browse the code ==

There are currently two main streams of development: trunk (1.3.x) and branch (1.2.x). Most other branches are only used for a short time to do some testing without disturbing the main development. You can use your web browser to navigate through the source code:

http://svn.gna.org/viewcvs/wesnoth/

== Download ==

To check out trunk (About 266 MB at october 2006) into a directory ''wesnoth'':
svn co http://svn.gna.org/svn/wesnoth/trunk wesnoth

or to check out the 1.2 branch (About 263 MB at december 2006) into a directory ''wesnoth-1.2'':
svn co http://svn.gna.org/svn/wesnoth/branches/1.2 wesnoth-1.2

More info on the repository: https://gna.org/svn/?group=wesnoth

== Update ==

Do this from inside the ''wesnoth'' or ''wesnoth-1.2'' directory where you checked out the repository:
svn update

Note that when you update from Subversion, you should always run 'autogen.sh' if ''configure.ac'' or any of the ''Makefile.am'' files were changed. It is safest to 'make clean' before updating, then update and finally run 'autogen.sh', 'configure' and 'make'.

You may be able to skip the 'autogen.sh' and the 'make clean' if the makefiles and ''configure.ac'' have not changed. If only minor changes were made then even the 'configure' step is optional.

== See Also ==

* [[CompilingWesnoth]]
* [[UsingAutotools]]
* [[What_Is_SVN]]
* [[SVN_on_Windows]]