The Battle for Wesnoth Wiki - User contributions [en]

Fosdem2010

2009-12-16T20:13:26Z

Yogi Bear: /* Schedule/Plans */

== General information ==
This page is meant to somehow coordinate the small Wesconf taking place at FOSDEM 2010. That is everyone attending should please list him/herself in the list of arrivals and stuff like this. FOSDEM 2010 will take place at the first weekend in Febuary 2010, on Saturday 6th and Sunday 7th.

* Fosdem - http://fosdem.org/2010/
* [http://www.wesnoth.org/forum/viewtopic.php?p=283311#283311 List with phone numbers] (forum moderators only)

== Schedule/Plans ==
{| border="1" width="100%"
|-
! (nick)name(s)
! Arrival
! Departure
! Accomodation
|-
| AI
| Fri, 5th
| Sun, 7th
| 2go4, booked by Ivanovic
|-
| Boucman
| Fri, 5th
| Mon, 8th
| 2go4, booked by Boucman
|-
| Crab
| Fri, 5th
| Sun, 7th
| 2go4, booked by Boucman
|-
| Fendrin
| Fri, 5th
| Sun, 7th
| 2go4, booked by Ivanovic
|-
| grzywacz & deekay
| Fri, 5th (?)
| Mon, 8th (?)
| unknown
|-
| Ivanovic & chrber
| Fri, 5th
| Sun, 7th
| 2go4, booked by Ivanovic
|-
| mordante
| Fri, 5th
| Sun, 7th
| 2go4, booked by Ivanovic
|-
| Noyga
| Fri, 5th
| Sun, 7th
| 2go4, booked by Boucman
|-
| Yogibear
| Fri, 5th
| Sun, 7th
| Thon Hotel Brussels City Centre
|-
|}

For accomodations please keep in mind that parking in the center of Brussels is really problematic. It might make sense to drive to the University where FOSDEM takes place, park there and take the bus into the town center (where some of the hotels/hostels are).

Possible hostels that we at least contacted over the last years (some of them might already be booked out by now!):
* [http://www.chab.be/ CHAB]
* [http://www.2go4.be/ 2go4] Note: groups bigger 6 are not allowed, so we can (officially) not form a complete Wesnoth group at this hostel, got to meet somewhere in town/at the university...
* [http://www.jeugdherbergen.be/brusselE.htm Bruegel YH]

On the official FOSDEM page [http://fosdem.org/2010/practical/accomodation some more possible hotels/hostels] are listed.

== Maps ==
* [http://tinyurl.com/3a65gr Bruegel YH]
* [http://tinyurl.com/35br9c Brussels Central (Train Station) → Bruegel YH]
* [http://tinyurl.com/37d9v4 Bruegel YH → Brussels Central (Train Station) → Novotel Grand Place]
* [http://tinyurl.com/2mzns6 Novotel Grand Place]
* [http://tinyurl.com/3dggg3 CrownePlaza (Europa)]
* [http://tinyurl.com/36epxj FOSDEM]
* [http://tinyurl.com/2w4bms Novotel Grand Place -> FOSDEM]

== Transportation ==
Information about how to reach the FOSDEM is listed at the [http://fosdem.org/2010/practical/transportation official transportation subpage].

Short version of how to get there for those that reside in Bruegel YH and Novotel Grand Place (basically town center):

* Enter Bus 71 (Debrouckere - Central Station ("Gare Centrale") - Delta) somewhere at 'Central Station'
* Leave the bus at "ULB" (crossroads Ave. Adolphe Buyl - Sq. Deveze)
* Walk down Ave. Paul Heger on your right hand.

== Wesnoth Hacking Room ==

Wesnoth will not have a room of its own. Instead we will use one of the "general hacking rooms". So far it is not sure which room it will be, if we do it like the last two years, it will be room number 115 in the building AW1. Last year this was the smaller of the two hacking rooms and we had no real problem with conquering (and holding) the first row in this room. There were not too many power outlets, so this year at least Ivanovic will bring one multi-outlet power strip plus some extension cable (5m or something like this). There is no wired network, everything wireless (and sometimes rather/very unstable!). Beside this you should bring laptops since there are no computers available for hacking.

Short version:
AW1 - Room 115

== Planned discussion ==
We usually discuss all sorts of things at FOSDEM, this section is here to have a small bullet list of things that we actively want to discuss at FOSDEM.
* GSOC 2010: finding mentors, organizing the submission etc..
* FOSDEM 2011 : trying to get a dev room with other games ?
* [wanted: discussion topics!]

== FOSDEM 2009 ==
We were already at FOSDEM 2009, here something as reference:

* [http://www.wesnoth.org/wiki/Fosdem2009 FOSDEM 2009 wiki page]

== FOSDEM 2008 ==
We were already at FOSDEM 2008, here something as reference:

* [http://www.wesnoth.org/forum/viewtopic.php?p=283649#p283649 Forum topic (with group photo)]
* [http://www.wesnoth.org/wiki/Fosdem2008 2008 wiki page]
* [https://mail.gna.org/public/wesnoth-dev/2008-02/msg00078.html Summary of FOSDEM 2008 results]

[[Category:Development]]
[[Category:Wesconf]]

EasyCoding

2009-09-05T14:25:58Z

Yogi Bear: /* * Savegame dialog */

== Foreword ==
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

--[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)

Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).

--Yogi Bear, 28 February 2008

== MP related features ==

=== Use different font for in-game chat ===
Since commas and dots are apparently hard to tell apart. As per FR #7470 [https://gna.org/bugs/?7470]

== WML related features ==

=== WML configurable village income / upkeep ===
Preferably as a [scenario], [side] or [campaign] keys. As per FR #6301 [https://gna.org/bugs/?6301]. Patch submitted: [https://gna.org/patch/index.php?1162] (gabba)

=== Add support of [if] for [scenario] ===
As per FR #4539 [https://gna.org/bugs/?4539]

=== Make [have_unit] optionaly use full SUF ===
[have_unit] by default uses SUF but does not apply it to recall list. Introduce an optional key that will allow to lift that limitation.

=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960]) -- [[User:dlr365|dlr365]] -- patch submitted [https://gna.org/bugs/index.php?4960]

=== Support for leaderless multiplayergames ===
Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])

=== Support for standalone multiplayer scenarios ===
There used to be support for standalone scenarios in the userdata tree, in reorganising the trees this feature got lost and an add-on is now required to add a scenario.
Re-add this feature. It is probably a good idea to mirror the mainline multiplayer tree.

=== Other Ideas ===
See [[FutureWML]]; some ideas there are easier than others.

== Improvements to AI ==

Fix some todos, add new formula functions, or do minor improvements to the formula language. Make it easier to debug the formula language, add more ai components.

Please discuss these with Crab, Dragonking, Sirp or Boucman

=== VERY easy tasks ===

==== Relocate code ====
find a new home for config_value_translator and
variant_value_translator template classes. (currently they are in src/ai/composite/aspect.hpp)
They should be in the separate file.

==== A small rename ====
rename paths::step::move_left to paths::step::move_cost
See r34430 for more details

==== Terrain Filter ====
add a const static terrain_filter::match_nothing_terrain_filter which matches nothing (constructor parameter is 'config cfg("not")' )
replace all places which construct that match_nothing_terrain_filter on the fly to use the new static filter.

=== AI Batch testing ===

Finish patch #1169 [https://gna.org/patch/?1169]

=== Add new generic observers to ai::manager ===

add an observer of 'time of day has changed' event

add an observer of 'minor gamestate changed' event
=== Allow ai to use teleports ===
to do that, add needed parameter to a_star_search in move_result::test_route (src/ai/actions.cpp )

=== Add more ai actions ===

Add an ai action (and add formula_ai function to do that) to set a goto on a unit

Add an ai action (and add formula_ai function to do that) to send a chat message to a player

Add an ai action to set formula ai variable (convert existing code from formula_ai)

Add an ai action to set formula ai unit variable (convert existing code from formula_ai)

=== write a (fai or c++) candidate action for leader control ===

=== write a (fai or c++) candidate action for using leadership/illuminate ===
special handling of units with leadership to have them support units. Only do it if it actually is useful (less hits needed to kill the unit) and ability to help multiple units in a single turn (assuming enough MP)

=== write a (fai or c++) candidate action for healer control ===
Handle units with healing power, moving them at places where they can provide the most healing

=== berserker improvement ===
The default AI's strategy of attacking as much as possible is very bad with berserker... A simple AI that would prevent the berserker from attacking (and keeping him close to fight without being exposed) and attack when the chance to kill is high enough would be an interesting addition

=== power projection improvement ===
AI sometimes wants to calculate 'how much firepower can enemy bring on location X'. in doing so, it considers enemy possible moves, time of day, attacks, enemy defense, etc.
There is specific problem with 'time_of_day' used in that calculation -sometimes, it's really needed to check 'time of day for NEXT turn', not time of day for THIS turn.(since the time of day might change next turn).

power_projection must be fixed to account for the possibility of time_of_day being different.

Note that some enemies might go after us (so, still on THIS turn), and some - before us (so, their next turn will be on NEXT turn).

== GUI related features ==
-------------------

Note at the moment Mordante is working on a new GUI system, these
changes will probably affect the way these items need to be implemented.
Contact Mordante on IRC before starting to work on these.

--[[User:SkeletonCrew|SkeletonCrew]] 14:04, 9 March 2008 (EDT)

=== Theme Changes ===

* allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])
* hide the hourglass item from the statusbar when there is no timer

=== Widget Changes ===
* show side number, name and team association information in the status table
* make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
* input history (chat, commands, ..) - note: rujasu is working on this feature

== GUI2 related features ==
GUI2 is the new gui engine Mordante/SkeletonCrew is working on.
* Information on the wiki can be found here http://www.wesnoth.org/wiki/GUIToolkit
* The source code is under src/gui/
* The configuration config files are under data/gui/default

Some tasks need the --new-widgets since the code is only shown in the experimental mode. Tasks which need this switch have the * in the title.

=== Arrow keys for the slider ===
There's a new slider widget, but it doesn't support the keyboard yet.
gui/widgets/slider.[c|h]pp

Clicking on the widget should capture the keyboard and then arrow left/right should move one step even if not all steps are visible.

=== Slider sizing ===
There are some issues with the sizing of a slider.
gui/widgets/slider.[c|h]pp

In a layout step it needs to try to shrink itself, not entirely sure where or how yet, best ask mordante on irc.

<del>

== Miscellaneous ==

=== More powerful village naming ===
'''Adding mountain names and other features to village names, having a second random name in village names'''

Currently the village naming engine has a very good structure that could allow
more powerfull names to be generated.
Understanding how it works should be quite easy, and a few usefull improvements could be added.

* Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
* It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
* Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice

Euschn 24/03/2009

=== Debug Mode ===
* New debug command functionality (setting additional status.variables, possibly terrain)

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

[[Category:Development]]
[[Category:Future]]

EasyCoding

2009-09-05T14:25:30Z

Yogi Bear: /* Savegame related stuff */

== Foreword ==
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

--[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)

Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).

--Yogi Bear, 28 February 2008

== MP related features ==

=== Use different font for in-game chat ===
Since commas and dots are apparently hard to tell apart. As per FR #7470 [https://gna.org/bugs/?7470]

== WML related features ==

=== WML configurable village income / upkeep ===
Preferably as a [scenario], [side] or [campaign] keys. As per FR #6301 [https://gna.org/bugs/?6301]. Patch submitted: [https://gna.org/patch/index.php?1162] (gabba)

=== Add support of [if] for [scenario] ===
As per FR #4539 [https://gna.org/bugs/?4539]

=== Make [have_unit] optionaly use full SUF ===
[have_unit] by default uses SUF but does not apply it to recall list. Introduce an optional key that will allow to lift that limitation.

=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960]) -- [[User:dlr365|dlr365]] -- patch submitted [https://gna.org/bugs/index.php?4960]

=== Support for leaderless multiplayergames ===
Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])

=== Support for standalone multiplayer scenarios ===
There used to be support for standalone scenarios in the userdata tree, in reorganising the trees this feature got lost and an add-on is now required to add a scenario.
Re-add this feature. It is probably a good idea to mirror the mainline multiplayer tree.

=== Other Ideas ===
See [[FutureWML]]; some ideas there are easier than others.

== Improvements to AI ==

Fix some todos, add new formula functions, or do minor improvements to the formula language. Make it easier to debug the formula language, add more ai components.

Please discuss these with Crab, Dragonking, Sirp or Boucman

=== VERY easy tasks ===

==== Relocate code ====
find a new home for config_value_translator and
variant_value_translator template classes. (currently they are in src/ai/composite/aspect.hpp)
They should be in the separate file.

==== A small rename ====
rename paths::step::move_left to paths::step::move_cost
See r34430 for more details

==== Terrain Filter ====
add a const static terrain_filter::match_nothing_terrain_filter which matches nothing (constructor parameter is 'config cfg("not")' )
replace all places which construct that match_nothing_terrain_filter on the fly to use the new static filter.

=== AI Batch testing ===

Finish patch #1169 [https://gna.org/patch/?1169]

=== Add new generic observers to ai::manager ===

add an observer of 'time of day has changed' event

add an observer of 'minor gamestate changed' event
=== Allow ai to use teleports ===
to do that, add needed parameter to a_star_search in move_result::test_route (src/ai/actions.cpp )

=== Add more ai actions ===

Add an ai action (and add formula_ai function to do that) to set a goto on a unit

Add an ai action (and add formula_ai function to do that) to send a chat message to a player

Add an ai action to set formula ai variable (convert existing code from formula_ai)

Add an ai action to set formula ai unit variable (convert existing code from formula_ai)

=== write a (fai or c++) candidate action for leader control ===

=== write a (fai or c++) candidate action for using leadership/illuminate ===
special handling of units with leadership to have them support units. Only do it if it actually is useful (less hits needed to kill the unit) and ability to help multiple units in a single turn (assuming enough MP)

=== write a (fai or c++) candidate action for healer control ===
Handle units with healing power, moving them at places where they can provide the most healing

=== berserker improvement ===
The default AI's strategy of attacking as much as possible is very bad with berserker... A simple AI that would prevent the berserker from attacking (and keeping him close to fight without being exposed) and attack when the chance to kill is high enough would be an interesting addition

=== power projection improvement ===
AI sometimes wants to calculate 'how much firepower can enemy bring on location X'. in doing so, it considers enemy possible moves, time of day, attacks, enemy defense, etc.
There is specific problem with 'time_of_day' used in that calculation -sometimes, it's really needed to check 'time of day for NEXT turn', not time of day for THIS turn.(since the time of day might change next turn).

power_projection must be fixed to account for the possibility of time_of_day being different.

Note that some enemies might go after us (so, still on THIS turn), and some - before us (so, their next turn will be on NEXT turn).

== GUI related features ==
-------------------

Note at the moment Mordante is working on a new GUI system, these
changes will probably affect the way these items need to be implemented.
Contact Mordante on IRC before starting to work on these.

--[[User:SkeletonCrew|SkeletonCrew]] 14:04, 9 March 2008 (EDT)

=== Theme Changes ===

* allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])
* hide the hourglass item from the statusbar when there is no timer

=== Widget Changes ===
* show side number, name and team association information in the status table
* make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
* input history (chat, commands, ..) - note: rujasu is working on this feature

== GUI2 related features ==
GUI2 is the new gui engine Mordante/SkeletonCrew is working on.
* Information on the wiki can be found here http://www.wesnoth.org/wiki/GUIToolkit
* The source code is under src/gui/
* The configuration config files are under data/gui/default

Some tasks need the --new-widgets since the code is only shown in the experimental mode. Tasks which need this switch have the * in the title.

=== * Savegame dialog ===
This is a new dialog to write and requires the minimap code to be fixed first. The dialog should mimic the current dialog. Sorting of a listbox and the proper alignment of the columns is not important (the engine doesn't support this yet). The code should only be used when --new-widgets is used as start switch since we're in a feature freeze at the moment.

=== Arrow keys for the slider ===
There's a new slider widget, but it doesn't support the keyboard yet.
gui/widgets/slider.[c|h]pp

Clicking on the widget should capture the keyboard and then arrow left/right should move one step even if not all steps are visible.

=== Slider sizing ===
There are some issues with the sizing of a slider.
gui/widgets/slider.[c|h]pp

In a layout step it needs to try to shrink itself, not entirely sure where or how yet, best ask mordante on irc.

<del>

== Miscellaneous ==

=== More powerful village naming ===
'''Adding mountain names and other features to village names, having a second random name in village names'''

Currently the village naming engine has a very good structure that could allow
more powerfull names to be generated.
Understanding how it works should be quite easy, and a few usefull improvements could be added.

* Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
* It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
* Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice

Euschn 24/03/2009

=== Debug Mode ===
* New debug command functionality (setting additional status.variables, possibly terrain)

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

[[Category:Development]]
[[Category:Future]]

DevelopersHome

2009-05-06T19:58:21Z

Yogi Bear: /* Miscellaneous */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling and Building
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
** [[SCons]]
** [[UsingAutotools]]
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can I do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them
* [[GettingStarted]]
* [[FrequentlyProposedIdeas]] - summary of past often-repeated forum discussions
* [[Wesnoth_Acronyms_and_Slang]]

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
* AI
** [[AI_Module]] - guide to AI module (src/ai)
** [[FormulaAI]] - Guide to the experimental formula AI branch
* Themes
** [[ThemeSystem]] - customizing the screen layout for the game and the editor
* Multiplayer
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.
* Gui2 - The new Gui-Framework
** [[GUIToolkit]]
** [[GUILayout]]
** [[GUIVariable]]
** Gui2 WML
*** [[GUICanvasWML]]
*** [[GUIToolkitWML]]
*** [[GUIWidgetDefinitionWML]]
*** [[GUIWidgetInstanceWML]]
*** [[GUIWindowDefinitionWML]]
* Savegames
** [[SavegameClassHierarchy]]

= Communication, Feedback, Events =
* Gna! links
** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
** http://patches.wesnoth.org/ - Gna! - patches

* Mailing lists
** https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
** https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

* IRC
** [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
** http://irclog.wesnoth.org/ - IRC logs

* Forum - http://forum.wesnoth.org

* This wiki - http://www.wesnoth.org/wiki/Main_Page

* FOSDEM
** [[Fosdem2008]]
** [[Fosdem2009]]

* Google Summer of Code
** [[SummerOfCodeIdeas]] - Ideas for GSoC
** [[SoC_Information_for_Google]] - Our organization profile for Google
** [[SoC_People_to_bug_on_IRC]] - Who GSoC students can ask for help

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* http://units.wesnoth.org/ - Unit reference

[[Category:Development]]

DevelopersHome

2009-05-02T20:48:28Z

Yogi Bear: /* Code documentation */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling and Building
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
** [[SCons]]
** [[UsingAutotools]]
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can I do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
* AI
** [[WritingYourOwnAI]] - write a C++ plugin
** [[FormulaAI]] - Guide to the experimental formula AI branch
* Themes
** [[ThemeSystem]] - customizing the screen layout for the game and the editor
* Multiplayer
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.
* Gui2 - The new Gui-Framework
** [[GUIToolkit]]
** [[GUILayout]]
** [[GUIVariable]]
** Gui2 WML
*** [[GUICanvasWML]]
*** [[GUIToolkitWML]]
*** [[GUIWidgetDefinitionWML]]
*** [[GUIWidgetInstanceWML]]
*** [[GUIWindowDefinitionWML]]
* Savegames
** [[SavegameClassHierarchy]]

= Communication, Feedback, Events =
* Gna! links
** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
** http://patches.wesnoth.org/ - Gna! - patches

* Mailing lists
** https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
** https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

* IRC
** [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
** http://irclog.wesnoth.org/ - IRC logs

* FOSDEM
** [[Fosdem2008]]
** [[Fosdem2009]]

* Google Summer of Code
** [[SummerOfCodeIdeas]] - Ideas for GSoC
** [[SoC_Information_for_Google]] - Our organization profile for Google
** [[SoC_People_to_bug_on_IRC]] - Who GSoC students can ask for help

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

[[Category:Development]]

DevelopersHome

2009-05-01T21:14:48Z

Yogi Bear: /* Code documentation */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling and Building
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
** [[SCons]]
** [[UsingAutotools]]
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
* AI
** [[WritingYourOwnAI]] - write a C++ plugin
** [[FormulaAI]] - Guide to the experimental formula AI branch
* Themes
** [[ThemeSystem]] - customizing the screen layout for the game and the editor
* Multiplayer
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.
* Gui2 - The new Gui-Framework
** [[GUIToolkit]]
** [[GUILayout]]
** [[GUIVariable]]
** Gui2 WML
*** [[GUICanvasWML]]
*** [[GUIToolkitWML]]
*** [[GUIWidgetDefinitionWML]]
*** [[GUIWidgetInstanceWML]]
*** [[GUIWindowDefinitionWML]]

= Communication, Feedback, Events =
* Gna! links
** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
** http://patches.wesnoth.org/ - Gna! - patches

* Mailing lists
** https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
** https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

* IRC
** [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
** http://irclog.wesnoth.org/ - IRC logs

* FOSDEM
** [[Fosdem2008]]
** [[Fosdem2009]]

* Google Summer of Code
** [[SummerOfCodeIdeas]] - Ideas for GSoC
** [[SoC_Information_for_Google]] - Our organization profile for Google
** [[SoC_People_to_bug_on_IRC]] - Who GSoC students can ask for help

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T21:09:56Z

Yogi Bear: /* Tools and Packaging */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling and Building
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
** [[SCons]]
** [[UsingAutotools]]
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
* AI
** [[WritingYourOwnAI]] - write a C++ plugin
** [[FormulaAI]] - Guide to the experimental formula AI branch
* Themes
** [[ThemeSystem]] - customizing the screen layout for the game and the editor
* Multiplayer
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
* Gna! links
** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
** http://patches.wesnoth.org/ - Gna! - patches

* Mailing lists
** https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
** https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

* IRC
** [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
** http://irclog.wesnoth.org/ - IRC logs

* FOSDEM
** [[Fosdem2008]]
** [[Fosdem2009]]

* Google Summer of Code
** [[SummerOfCodeIdeas]] - Ideas for GSoC
** [[SoC_Information_for_Google]] - Our organization profile for Google
** [[SoC_People_to_bug_on_IRC]] - Who GSoC students can ask for help

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T21:07:49Z

Yogi Bear: /* Communication, Feedback, Events */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
* AI
** [[WritingYourOwnAI]] - write a C++ plugin
** [[FormulaAI]] - Guide to the experimental formula AI branch
* Themes
** [[ThemeSystem]] - customizing the screen layout for the game and the editor
* Multiplayer
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
* Gna! links
** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
** http://patches.wesnoth.org/ - Gna! - patches

* Mailing lists
** https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
** https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

* IRC
** [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
** http://irclog.wesnoth.org/ - IRC logs

* FOSDEM
** [[Fosdem2008]]
** [[Fosdem2009]]

* Google Summer of Code
** [[SummerOfCodeIdeas]] - Ideas for GSoC
** [[SoC_Information_for_Google]] - Our organization profile for Google
** [[SoC_People_to_bug_on_IRC]] - Who GSoC students can ask for help

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:57:29Z

Yogi Bear: /* Communication, Feedback, Events */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
* AI
** [[WritingYourOwnAI]] - write a C++ plugin
** [[FormulaAI]] - Guide to the experimental formula AI branch
* Themes
** [[ThemeSystem]] - customizing the screen layout for the game and the editor
* Multiplayer
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
* Gna! links
** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
** http://patches.wesnoth.org/ - Gna! - patches

* Mailing lists
** https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
** https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

* IRC
** [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
** http://irclog.wesnoth.org/ - IRC logs

* FOSDEM
** [[Fosdem2008]]
** [[Fosdem2009]]

* Google Summer of Code
** [SummerOfCodeIdeas Ideas for GSoC]

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:54:17Z

Yogi Bear: /* Communication, Feedback, Events */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
* AI
** [[WritingYourOwnAI]] - write a C++ plugin
** [[FormulaAI]] - Guide to the experimental formula AI branch
* Themes
** [[ThemeSystem]] - customizing the screen layout for the game and the editor
* Multiplayer
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
* Gna! links
** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
** http://patches.wesnoth.org/ - Gna! - patches

* Mailing lists
** https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
** https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

* IRC
** [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
** http://irclog.wesnoth.org/ - IRC logs

* FOSDEM
** [[Fosdem2008]]
** [[Fosdem2009]]

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:52:29Z

Yogi Bear: /* Communication, Feedback, Events */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
* AI
** [[WritingYourOwnAI]] - write a C++ plugin
** [[FormulaAI]] - Guide to the experimental formula AI branch
* Themes
** [[ThemeSystem]] - customizing the screen layout for the game and the editor
* Multiplayer
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
* Gna! links
** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
** http://patches.wesnoth.org/ - Gna! - patches

* Mailing lists
** https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
** https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

* IRC
** [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
** http://irclog.wesnoth.org/ - IRC logs

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:51:58Z

Yogi Bear: /* Code documentation */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
* AI
** [[WritingYourOwnAI]] - write a C++ plugin
** [[FormulaAI]] - Guide to the experimental formula AI branch
* Themes
** [[ThemeSystem]] - customizing the screen layout for the game and the editor
* Multiplayer
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
== Gna! links ==
* http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
* http://patches.wesnoth.org/ - Gna! - patches

== Mailing lists ==
* https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
* https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

== IRC ==
* [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
* http://irclog.wesnoth.org/ - IRC logs

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:51:08Z

Yogi Bear: /* Tools and Packaging */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
* Supporting Websites
** [[WesnothSVN]] - accessing the source code
** http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
** http://gettext.wesnoth.org/ - gettext status
* Compiling
** [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* Packaging and Releasing
** [[ReleasingWesnoth]] - steps to follow to release a new version
** [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation
** [[Doxygen]] - Documentation generator
* More stuff
** [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
** [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
== Gna! links ==
* http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
* http://patches.wesnoth.org/ - Gna! - patches

== Mailing lists ==
* https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
* https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

== IRC ==
* [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
* http://irclog.wesnoth.org/ - IRC logs

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:50:01Z

Yogi Bear: /* General Information */

= General Information =
* Links
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
** [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

* Coding Guidelines
** [[HackingWesnoth]] - guide for programmers
** [[CodingStandards]] - for programmers
** [[DeveloperGuide]] - for those who received SVN commit rights

* Library documentation
** http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
== Supporting Websites ==
* [[WesnothSVN]] - accessing the source code
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* http://gettext.wesnoth.org/ - gettext status
== Compiling ==
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
== Packaging and Releasing ==
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
== Documentation ==
* [[Doxygen]] - Documentation generator
== More stuff ==
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
* [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
== Gna! links ==
* http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
* http://patches.wesnoth.org/ - Gna! - patches

== Mailing lists ==
* https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
* https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

== IRC ==
* [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
* http://irclog.wesnoth.org/ - IRC logs

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:48:28Z

Yogi Bear:

= General Information =
== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== Coding Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== STL documentation ==
* http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
== Supporting Websites ==
* [[WesnothSVN]] - accessing the source code
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* http://gettext.wesnoth.org/ - gettext status
== Compiling ==
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
== Packaging and Releasing ==
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
== Documentation ==
* [[Doxygen]] - Documentation generator
== More stuff ==
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
* [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Game - Create content =
* [[BuildingScenarios]] and related useful forum discussions:
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development]
** [http://www.wesnoth.org/forum/viewtopic.php?t=4301 A Balancing Act]
* [[ReferenceWML]]

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
== Gna! links ==
* http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
* http://patches.wesnoth.org/ - Gna! - patches

== Mailing lists ==
* https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
* https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

== IRC ==
* [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
* http://irclog.wesnoth.org/ - IRC logs

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:45:46Z

Yogi Bear: /* IRC */

= General Information =
== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== Coding Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== STL documentation ==
* http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
== Supporting Websites ==
* [[WesnothSVN]] - accessing the source code
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* http://gettext.wesnoth.org/ - gettext status
== Compiling ==
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
== Packaging and Releasing ==
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
== Documentation ==
* [[Doxygen]] - Documentation generator
== More stuff ==
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
* [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
== Gna! links ==
* http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
* http://patches.wesnoth.org/ - Gna! - patches

== Mailing lists ==
* https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
* https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

== IRC ==
* [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] - IRC (alias to irc.freenode.net)
* http://irclog.wesnoth.org/ - IRC logs

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:45:12Z

Yogi Bear: /* Mailing lists */

= General Information =
== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== Coding Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== STL documentation ==
* http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
== Supporting Websites ==
* [[WesnothSVN]] - accessing the source code
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* http://gettext.wesnoth.org/ - gettext status
== Compiling ==
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
== Packaging and Releasing ==
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
== Documentation ==
* [[Doxygen]] - Documentation generator
== More stuff ==
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
* [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
== Gna! links ==
* http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
* http://patches.wesnoth.org/ - Gna! - patches

== Mailing lists ==
* https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
* https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits

== IRC ==
* IRC: [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] (alias to irc.freenode.net)
* IRC logs - http://irclog.wesnoth.org/

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:44:51Z

Yogi Bear: /* Gna! links */

= General Information =
== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== Coding Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== STL documentation ==
* http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
== Supporting Websites ==
* [[WesnothSVN]] - accessing the source code
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* http://gettext.wesnoth.org/ - gettext status
== Compiling ==
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
== Packaging and Releasing ==
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
== Documentation ==
* [[Doxygen]] - Documentation generator
== More stuff ==
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
* [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
== Gna! links ==
* http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
* http://patches.wesnoth.org/ - Gna! - patches

== Mailing lists ==
* wesnoth-dev - https://mail.gna.org/listinfo/wesnoth-dev/
* wesnoth-commits - https://mail.gna.org/listinfo/wesnoth-commits/

== IRC ==
* IRC: [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] (alias to irc.freenode.net)
* IRC logs - http://irclog.wesnoth.org/

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:43:55Z

Yogi Bear: /* Communication, Feedback */

= General Information =
== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== Coding Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== STL documentation ==
* http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
== Supporting Websites ==
* [[WesnothSVN]] - accessing the source code
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* http://gettext.wesnoth.org/ - gettext status
== Compiling ==
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
== Packaging and Releasing ==
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
== Documentation ==
* [[Doxygen]] - Documentation generator
== More stuff ==
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
* [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback, Events =
== Gna! links ==
* Gna! - bugs and feature requests - http://bugs.wesnoth.org/
* Gna! - patches - http://patches.wesnoth.org/

== Mailing lists ==
* wesnoth-dev - https://mail.gna.org/listinfo/wesnoth-dev/
* wesnoth-commits - https://mail.gna.org/listinfo/wesnoth-commits/

== IRC ==
* IRC: [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] (alias to irc.freenode.net)
* IRC logs - http://irclog.wesnoth.org/

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:43:20Z

Yogi Bear:

= General Information =
== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== Coding Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== STL documentation ==
* http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
== Supporting Websites ==
* [[WesnothSVN]] - accessing the source code
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* http://gettext.wesnoth.org/ - gettext status
== Compiling ==
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
== Packaging and Releasing ==
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
== Documentation ==
* [[Doxygen]] - Documentation generator
== More stuff ==
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
* [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

= Communication, Feedback =
== Gna! links ==
* Gna! - bugs and feature requests - http://bugs.wesnoth.org/
* Gna! - patches - http://patches.wesnoth.org/

== Mailing lists ==
* wesnoth-dev - https://mail.gna.org/listinfo/wesnoth-dev/
* wesnoth-commits - https://mail.gna.org/listinfo/wesnoth-commits/

== IRC ==
* IRC: [irc://irc.wesnoth.org/#wesnoth-dev freenode/#wesnoth-dev] (alias to irc.freenode.net)
* IRC logs - http://irclog.wesnoth.org/

= Miscellaneous =
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:41:09Z

Yogi Bear: /* More stuff */

= General Information =
== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== Coding Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== STL documentation ==
* http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
== Supporting Websites ==
* [[WesnothSVN]] - accessing the source code
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* http://gettext.wesnoth.org/ - gettext status
== Compiling ==
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
== Packaging and Releasing ==
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
== Documentation ==
* [[Doxygen]] - Documentation generator
== More stuff ==
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)
* [[MaintenanceTools]] WMLLint, WMLIndent and WMLScope

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

== Miscellaneous ==
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:39:02Z

Yogi Bear: /* Code documentation */

= General Information =
== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== Coding Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== STL documentation ==
* http://www.sgi.com/tech/stl/ - Standard Template Library

= Tools and Packaging =
== Supporting Websites ==
* [[WesnothSVN]] - accessing the source code
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* http://gettext.wesnoth.org/ - gettext status
== Compiling ==
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
== Packaging and Releasing ==
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
== Documentation ==
* [[Doxygen]] - Documentation generator
== More stuff ==
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)

= I want to start coding, what can i do? =
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

= Code documentation =
* http://devdocs.wesnoth.org - generated code documentation
== AI ==
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
== Themes ==
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
== Multiplayer ==
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

== Miscellaneous ==
* [[DebugMode]] and [[CommandMode]] - in game debugging commands
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing

DevelopersHome

2009-05-01T20:36:27Z

Yogi Bear:

DevelopersHome

2009-05-01T20:31:28Z

Yogi Bear: /* Tools and Packaging */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights
* http://www.sgi.com/tech/stl/ - Standard Template Library

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[Doxygen]] - Documentation generator
* http://gettext.wesnoth.org/ - gettext status
* [[ExternalUtilities]] (Wercator, CampGen, wmllint, etc.)

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* http://devdocs.wesnoth.org - generated code documentation
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

== Miscellaneous ==
* [[DebugMode]] and [[CommandMode]] - in game debugging commands

DevelopersHome

2009-05-01T20:30:24Z

Yogi Bear: /* Tools and Packaging */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights
* http://www.sgi.com/tech/stl/ - Standard Template Library

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[Doxygen]] - Documentation generator
* http://gettext.wesnoth.org/ - gettext status

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* http://devdocs.wesnoth.org - generated code documentation
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

== Miscellaneous ==
* [[DebugMode]] and [[CommandMode]] - in game debugging commands

DevelopersHome

2009-05-01T20:29:33Z

Yogi Bear:

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights
* http://www.sgi.com/tech/stl/ - Standard Template Library

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[Doxygen]] - Documentation generator
* http://gettext.wesnoth.org/ - gettext status

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* http://devdocs.wesnoth.org - generated code documentation
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

== Miscellaneous ==
* [[DebugMode]] and [[CommandMode]] - in game debugging commands

DevelopersHome

2009-05-01T20:28:13Z

Yogi Bear: /* General Guidelines */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights
* http://www.sgi.com/tech/stl/ - Standard Template Library

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[Doxygen]] - Documentation generator
* http://gettext.wesnoth.org/ - gettext status

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* http://devdocs.wesnoth.org - generated code documentation
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:27:20Z

Yogi Bear: /* Tools and Packaging */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[CompilingWesnoth]] - how to compile Battle for Wesnoth (it's not hard)
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[Doxygen]] - Documentation generator
* http://gettext.wesnoth.org/ - gettext status

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* http://devdocs.wesnoth.org - generated code documentation
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:26:30Z

Yogi Bear: /* Tools and Packaging */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[Doxygen]] - Documentation generator
* http://gettext.wesnoth.org/ - gettext status

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* http://devdocs.wesnoth.org - generated code documentation
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:24:14Z

Yogi Bear:

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[Doxygen]] - Documentation generator

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* http://devdocs.wesnoth.org - generated code documentation
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:23:54Z

Yogi Bear: /* Code documentation */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[Doxygen]] - Documentation generator

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* generated code documentation - http://devdocs.wesnoth.org
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:23:00Z

Yogi Bear: /* Tools and Packaging */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* [[Doxygen]] - Documentation generator

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:22:29Z

Yogi Bear: /* Tools and Packaging */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms
* Documentation generator [[Doxygen]]

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:21:45Z

Yogi Bear: /* Links */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth Latest commits] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:20:51Z

Yogi Bear: /* Links */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* [http://cia.vc/stats/project/wesnoth] - Up-to-date commit messages

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:20:18Z

Yogi Bear: /* Links */

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game
* Up-to-date commit messages : http://cia.vc/stats/project/wesnoth

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

DevelopersHome

2009-05-01T20:18:59Z

Yogi Bear: New page: <h1>Developers Home</h1> If you want to program for wesnoth, this is the page to look at. == Links == * DeveloperResources - useful links * [http://changelog.wesnoth.org Changelog] - ...

<h1>Developers Home</h1>
If you want to program for wesnoth, this is the page to look at.

== Links ==
* [[DeveloperResources]] - useful links
* [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game

== General Guidelines ==
* [[HackingWesnoth]] - guide for programmers
* [[CodingStandards]] - for programmers
* [[DeveloperGuide]] - for those who received SVN commit rights

== Tools and Packaging ==
* [[WesnothSVN]] - accessing the source code
* [[ReleasingWesnoth]] - steps to follow to release a new version
* [[WesnothPackagersGuide]] - guidelines for packaging Wesnoth for different platforms

== I want to start coding, what can i do? ==
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them

== Code documentation ==
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing
* [[WritingYourOwnAI]] - write a C++ plugin
* [[FormulaAI]] - Guide to the experimental formula AI branch
* [[ThemeSystem]] - customizing the screen layout for the game and the editor
* [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server.

EasyCoding

2009-04-29T21:15:48Z

Yogi Bear: /* Savegame related stuff */

== Foreword ==
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

--[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)

Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).

--Yogi Bear, 28 February 2008

== MP related features ==

=== Use different font for in-game chat ===
Since commas and dots are apparently hard to tell apart. As per FR #7470 [https://gna.org/bugs/?7470]

== WML related features ==

=== WML configurable village income / upkeep ===
Preferably as a [scenario], [side] or [campaign] keys. As per FR #6301 [https://gna.org/bugs/?6301]. Patch submitted: [https://gna.org/patch/index.php?1162] (gabba)

=== Add support of [if] for [scenario] ===
As per FR #4539 [https://gna.org/bugs/?4539]

=== Make [have_unit] optionaly use full SUF ===
[have_unit] by default uses SUF but does not apply it to recall list. Introduce an optional key that will allow to lift that limitation.

=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960]) -- [[User:dlr365|dlr365]] -- patch submitted [https://gna.org/bugs/index.php?4960]

=== Support for leaderless multiplayergames ===
Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])

=== Support for standalone multiplayer scenarios ===
There used to be support for standalone scenarios in the userdata tree, in reorganising the trees this feature got lost and an add-on is now required to add a scenario.
Re-add this feature. It is probably a good idea to mirror the mainline multiplayer tree.

=== Other Ideas ===
See [[FutureWML]]; some ideas there are easier than others.

== Improvements to FormulaAI ==

Add new formula functions, or minor improvements to the formula language. Make it easier to debug the formula language.

Please discuss these with Dragonking, Sirp or Boucman

Use [[AI_Arena]] for testing custom formulas.

=== Poisoning Improvement ===

Writing a formula that will make units with poison attacks prioritize their targets to spead poison as much as possible, avoiding already poisoned units and other useless targets

=== About to level formula ===

Writing a formula that would handle units with only a few XP left to level and have them fight accordingly (most likely to kill or hit depending on XP needed, taking into account target's level)

=== Healer improvements ===

Handle units with healing power, moving them at places where they can provide the most healing

=== Leader improvements ===

A bit more complicated : special handling of units with leadership to have them support units. Only do it if it actually is usefull (less hits needed to kill the unit) and ability to help multiple units in a single turn (assuming enough MP)

=== Berserker improvements ===

The default AI's strategy of attacking as much as possible is very bad with berserker... A simple AI that would prevent the berserker from attacking (and keeping him close to fight without being exposed) and attack when the chance to kill is high enough would be an interesting addition

=== Debugging help ===

<s>* provide a way for a formula to have a text float over hex (for debugging purpose).</s> done by [[SummerOfCodeProposal_AI_Improvement_Crab|Crab]], patch submitted [https://gna.org/bugs/?13230]
* in debug mode, have all AI move print their name in the log

=== New type of candidate moves : Global ===

to be called only once with no implicit variable

== GUI related features ==
-------------------

Note at the moment Mordante is working on a new GUI system, these
changes will probably affect the way these items need to be implemented.
Contact Mordante on IRC before starting to work on these.

--[[User:SkeletonCrew|SkeletonCrew]] 14:04, 9 March 2008 (EDT)

=== Theme Changes ===

* allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])
* hide the hourglass item from the statusbar when there is no timer

=== Widget Changes ===
* show side number, name and team association information in the status table
* make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
* input history (chat, commands, ..) - note: rujasu is working on this feature

== GUI2 related features ==
GUI2 is the new gui engine Mordante/SkeletonCrew is working on.
* Information on the wiki can be found here http://www.wesnoth.org/wiki/GUIToolkit
* The source code is under src/gui/
* The configuration config files are under data/gui/default

Some tasks need the --new-widgets since the code is only shown in the experimental mode. Tasks which need this switch have the * in the title.

=== Generic yes/no ok/cancel dialog ===
There's already a generic OK dialog
* src/gui/dialogs/message.[h|c]pp
* data/gui/default/window/message.cfg

This dialog should have the option to show a cancel button as well and also let the caller of the dialog determine the text of the button. Maybe more buttons (4 in total) can be added to make the dialog more flexible.

=== * Minimap ===
The minimap widget has already been made but is broken.
* src/gui/widgets/minimap.[c|h]pp

The drawing code has been rewritten, but this widget hasn't been updated it's used in the MP connection dialog (which needs more work).

=== * Savegame dialog ===
This is a new dialog to write and requires the minimap code to be fixed first. The dialog should mimic the current dialog. Sorting of a listbox and the proper alignment of the columns is not important (the engine doesn't support this yet). The code should only be used when --new-widgets is used as start switch since we're in a feature freeze at the moment.

=== * Title screen ===
A start has been made for the new titlescreen
* src/gui/dialogs/title_screen.[c|h]pp
* data/gui/default/window/title_screen.cfg
This should be improved to include the buttons and alignment of the current title screen. The 'roll-over' image is not part of this task.

=== Arrow keys for the slider ===
There's a new slider widget, but it doesn't support the keyboard yet.
gui/widgets/slider.[c|h]pp

Clicking on the widget should capture the keyboard and then arrow left/right should move one step even if not all steps are visible.

=== Slider sizing ===
There are some issues with the sizing of a slider.
gui/widgets/slider.[c|h]pp

In a layout step it needs to try to shrink itself, not entirely sure where or how yet, best ask mordante on irc.

<del>
== Savegame related stuff ==

=== consistent player information ===
At the moment, the [player]-section for a campaign savegame will appear in two places: The root level of the savegame and the [replay_start]-section. This was due to a last-minute fix for 1.6 that was designed to be the least intrusive. The [player]-section should only be written to [replay_start] (and of course read from there as well). Patch submitted: [https://gna.org/patch/index.php?1150] -grantwu

=== fix bug #13268 (save corruption through undo/redo of recalls [https://gna.org/bugs/?13268] ===
</del>

== Miscellaneous ==

=== More powerful village naming ===
'''Adding mountain names and other features to village names, having a second random name in village names'''

Currently the village naming engine has a very good structure that could allow
more powerfull names to be generated.
Understanding how it works should be quite easy, and a few usefull improvements could be added.

* Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
* It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
* Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice

Euschn 24/03/2009

=== Debug Mode ===
* New debug command functionality (setting additional status.variables, possibly terrain)

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

[[Category:Development]]
[[Category:Future]]

SummerOfCodeProposal lmg

2009-03-27T23:01:11Z

Yogi Bear:

'''In progress...'''

==User Information==
gna: lmg<br>
wesnoth forums: lmg<br>
irc: lgraham<br>
preferred email: <br>

==Basics==

===Introduction===
''Write a small introduction to yourself. )''<br>
I'm just finishing up my second year of software engineering. I have been a Linux user for two years, and I was looking into contributing to an open source project when I ran across Google Summer of Code. I thought this would be a great way for me to learn about contributing to open source projects.

===Education===
''What are you studying, subject, level and school''<br>
In April 2009, I will have completed my second year of Software Engineering at the University of Calgary in Calgary, Alberta, Canada.

===Why Google Summer of Code?===
''Why do you want to participate in summer of code?''<br>
I would like to participate in the summer of code to enhance my programming skills and apply the software design techniques I am learning in classes. I feel that participating in this program will enhance my educational experience and give me something practical to which I can relate when doing classwork. In addition to this, I use a lot of open source software at home, and I am interested in learning more about open source development.

===Patches Submitted to Wesnoth===
''(If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for Wesnoth. If you have gained commit access to our SVN (during the evaluation period or earlier) please state so. ''<br>
<here>

==Experience==

===Previous Projects===
''What programs/software have you worked on before? ''<br>
I have done both procedural and object oriented programming to learn the structure of the languages I have studied. Most of the programs I have worked on have been done to complete class requirements.

===Team Software Development Experience===
''Have you developed software in a team environment before? (As opposed to hacking on something on your own)''<br>
I have done a significant amount of work developing with another person, but I don't have experience developing with larger groups.

===Previous Google Summer of Code Participation===
''Have you participated to the Google Summer of Code before? As a mentor or a student? In what project? Were you successful? If not, why?''<br>
I have never participated in Google Summer of Code.

===Open Source===
''Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.''<br>
I am not currently involved with any open source development projects.

===Gaming Experience===
''Are you a gamer? What type of gamer are you?What type of games? What type of opponents do you prefer? Are you more interested in story or gameplay?Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.
We do not plan to favor Wesnoth players as such, but some particular projects require a good feeling for the game which is hard to get without having played intensively.''<br>
I enjoy gaming, but can only do it on a casual basis. I like fantasy/scifi-based games with a good story and gameplay, and I believe both the story and gameplay are essential to making a great game. I don't have experience in playing against other players. I have played Wesnoth for only a few days in single player mode, but I look forward to learning more about Wesnoth and branching into the multiplayer mode. Most of the games I have played are single-player games, and I look forward to exploring the multiplayer side of things.

==Communication Skills==

===English Fluency===
''Though most of our developers are not native English speakers, English is the project's working language. Describe your fluency level in written English.''<br>
English is my first language.

===Player Interaction===
''Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough''<br>
I think I will be good at interacting with other players. I was a forum moderator last summer, and I feel I am pretty well equipped to handle most things.

===Advice and Criticism===
''Do you give constructive advice?Do you receive advice well? Are you good at sorting useful criticisms from useless ones?''<br>
I only give advice if I think it will be constructive. When someone gives me advice, I take it into consideration and try to use it if I can. I have done a lot of group work in which there are useful and useless criticisms, and I think I am fairly proficient at determining what is useful.

==Project==

===Selection and Reasons for Choosing===
''Did you select a project from our list? If that is the case, what project did you select? What do you want to especially concentrate on? Why did you choose this project?''<br>
Savegame Reorganization. For this particular project, I would like to focus on the software development process and seeing how it works in a real project. I chose this project because many of the software engineering concepts I am currently learning can be applied to this project (UML, software design process)

===Estimated Timeline===
''Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".''<br>
<estimated timeline>

===Technical Details===
''Include as much technical detail about your implementation as you can''<br>
<technical details>

===Expected Outcome===
''What do you expect to gain from this project? What would make you stay in the Wesnoth community after the conclusion of SOC?''<br>
I would like to gain a good understanding of how open source projects work and how to contribute in a meaningful way. I would stay in the Wesnoth community after the conclusion of SOC if I have good support from my mentor and the development community and I can use my skills to make Wesnoth better.

==Practical Considerations==

===Tool and Languages===
''Are you familiar with any of the following tools or languages?''

* Subversion (used for all commits)
* C++ (language used for all the normal source code)
** I have been using C++ for almost a year (I have taken two courses using C++ as the programming language)
* Python (optional, mainly used for tools)
** I have never used Pythong
* build environments (eg cmake/autotools/scons)

''What programming languages are you fluent in?''<br>
C, C++, Java

===Development Tools===
''Which tools do you normally use for development? Why do you use them?''<br>
vim - offers many features in a simple, easy to use command line text editor
<br>Eclipse - it shows compilation errors in real time
<br>junit - for unit testing of Java programs
<br>javadoc - create nicely formatted inline documentation

===Spoken Languages===
''What spoken languages are you fluent in?)''<br>
I am fluent in English and have limited knowledge of French.

===Availability and Alternate Contact===
''At what hours are you awake and when will you be able to be in IRC (please specify in UTC) Would you mind talking with your mentor on telephone / internet phone? We would like to have a backup way for communications for the case that somehow emails and IRC do fail.''<br>
I am generally awake 1400 - 0400 UTC. I will be able to be in IRC between the hours of 2300 - 0400 UTC during the week although the actual hours may vary (I don't have summer plans yet). On weekends, I am awake 1500 - 0500 UTC and can be on IRC anytime. I don't mind talking with my mentor on the phone - either regular or internet phone is good for me.

[[Category:Summer of Code]]

SummerOfCodeProposal Euschn

2009-03-27T23:00:28Z

Yogi Bear:

==Euschn's SoC Proposal: Savegame Reorganization==

hi, I'm euschn and I would like to contribute to wesnoth via GSoC

real name: Eugen

age: 26

location: Vienna, Austria

occupation: phd student for computer science, Vienna University of Technology

==Questionaire==

====1) Basics====

'''1.1) Write a small introduction to yourself.'''

My name is Eugen Jiresch, I live in Vienna, Austria, and I am 26 years old. I am a phd student in computer science at the Vienna University of Technology. My phd project is about formal models of computation and theory of programming languages.
Despite the theoretic focus of my phd, I like coding a lot, which is one of my reasons for applying for GSoC.

'''1.2) State your preferred email address.'''

jiresch_(atsign)_logic_(dot)_at

'''1.3) If you have chosen a nick for IRC and Wesnoth forums, what is it?'''

euschn (same as my gna.org account)

'''1.4) Why do you want to participate in summer of code?'''

There are several reasons. First, I would like to take part in an interesting software development project.
By doing so, I want to improve my skills and learn new things about programming. Then, being a gamer myself, I am very interested
in contributing to the development a computer game, especially one that seems cool and fun to me (Wesnoth falls in that category). I have often dreamed about a job in game development in the future, and this could be a good opportunity to get started.
Additionally, if I want a job for the summer, I want it to be something that is meaningful to me and needed/appreciated by others - like adding desired feature to a game.
Finally, being a poor student, 4500$ is a lot of money to me.

'''1.5) What are you studying, subject, level and school?'''

As mentioned above, I am a phd student in computer science, at Vienna University of Technology

'''1.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for Wesnoth. If you have gained commit access to our SVN (during the evaluation period or earlier) please state so.'''
Not yet, but I plan to do so in the course of my application.

====2) Experience====

'''2.1) What programs/software have you worked on before?'''

Most of the software I have done was for university courses. I have done a bit of programming in games that support modding/custom maps like Starcraft of World of Warcraft, but nothing too fancy.
Recently, I became a contributor to the inets project (see 2.4.1)

'''2.2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)'''

Yes, in university courses and the inets project (see 2.4.1)

'''2.3) Have you participated to the Google Summer of Code before? As a mentor or a student? In what project? Were you successful? If not, why?'''

No.

====2.4) Open Source====

'''2.4.1) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.'''

Yes, I recently became contributor to the inets project ( https://gna.org/projects/inets/ ). inets is a compiler from an interaction nets based language to C (for more information, see http://www.interaction-nets.org/)
Interaction nets is an innovative formal model of computation, which is also a focus of my phd project.
My involvement so far has been the implementation of extended pattern matching for the computational rules of the inets language, and some bug fixing.

====2.5) Gaming experience - Are you a gamer?====
Yes, since early childhood!

'''2.5.1) What type of gamer are you?'''

I am a passionate gamer, maybe even hardcore - allthough the definition of hardcore is quite fuzzy depending on game and community :).
In short, I spend a *lot* of my free time playing computer games and checking out their respective communities.

'''2.5.2) What type of games?'''

My favorite genres and games include:

Role playing games: Final Fantasy series, Zelda series, Baldurs Gate series, Diablo series,...

Strategy games: Warcraft series, Starcraft, Spellforce, and just recently Wesnoth

Platforming: the usual old school nintendo stuff

Action: Quake series, Metroid series, Portal

singleplayer vs multiplayer:

I enjoy a good singleplayer game a lot. But I also like multiplayer, and I am doing a lot of online multiplayer gaming.
For example, a few years ago I was playing Warcraft 3 online a lot, and got to know the online community pretty well.
So while I have not played Wesnoth a lot, I have a good feeling for online gaming communities. (if they are comparable at all!)

'''2.5.3) What type of opponents do you prefer?'''

I like opponents that can teach me something and help me improve my skills in a game, or just generally make a game fun.
To me, playing against a good and fun oponent in a multiplayer game makes winning or losing of secondary importance.
Generally, I do not like oponents who are sore losers, and I am doing my best not to be one, either.

'''2.5.4) Are you more interested in story or gameplay?'''

I would say it depends on the game. Awesome gameplay can make a great game even with a lackluster story (or none at all).
In my opinion, this is often true for multiplayer games, where most of the fun comes from human oponents (or allies). But singleplayer games
with a weak story can be great, too (everyone who has ever enjoyed a Super Mario game has to agree).
Then again, I remember many cool games especially for their story (RPGs mostly, but also some strategy games).
So all in all, either can make a great game and I am interested in both.

'''2.5.5) Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.'''

I only recently got to know Wesnoth. I have played some of the singleplayer campaigns, and I like it a lot so far. It is a nice mix of strategy and roleplaying, and I plan to continue playing it
(apart from getting to know it for GSoC!). I understand that being an experienced wesnoth player helps with some projects, I hope this is not so mandatory for savegame reorganization.

//We do not plan to favor Wesnoth players as such, but some particular projects require a good feeling for the game which is hard to get without having played intensively.

====3) Communication skills====

'''3.1) Though most of our developers are not native English speakers, English is the project's working language. Describe your fluency level in written English.'''

I am a German native speaker, but I feel I can fully express myself in English.

'''3.2) Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.'''

Yes, I am fine with interacting with other players, even if it is going to be rough. As mentioned in 2.5.2), I have experience with online gaming communities (especially Blizzard games),
so I am used to their not so friendly aspects.

'''3.3) Do you give constructive advice?'''

Absolutely, I try to keep my advice as constructive as possible.

'''3.4) Do you receive advice well?'''

Yes, constructive advice is a chance to improve myself, and I always give my best to take that chance.

'''3.5) Are you good at sorting useful criticisms from useless ones?'''

Yes.

====4) Project====

'''4.1) Did you select a project from our list? If that is the case, what project did you select? What do you want to especially concentrate on?'''

Yes, I selected Savegame reorganization.

4.2) If you have invented your own project, please describe the project and the scope.

'''4.3) Why did you choose this project?'''

There are several reasons. First, I want to work on a project that is deemed necessary or desired by the wesnoth community. I think redesigning savegames is such a project.
I do not want to work on some feature that noone really wants.
Second, I like the concept of multiplayer campaigns. Cooperative multiplayer games are good fun (I like them a lot myself), but they are rare. Only few games have coop modes, especially in combination with
story-driven game types like a campaign in wesnoth. So if I can help to promote cooperative game types by improving wesnoth's savegame design, I will be very glad to do so.
In general, it seems to me that studying a "messy" design (Im quoting the wiki here) and trying to come up with a better one is a good challenge that I would like to take. Also, I am
curious how this component works in a project of this size, as I have not yet worked on such a big program and I would like to learn what makes it tick.
Finally, I think I have the required skills to succeed at this project (with help from my mentor of course!). I have good C++ skills and I feel up to
study the current implementation and develop a deliberate design in cooperation with my mentor.

'''4.4) Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".'''

My estimated timeline is affected by both "special things" mentioned in the question.
First, I will have to spend some time on university stuff up to mid June. In this period, I can of course still work on the GSoC project, just not full time.
I think that I will be able to work 20-25h a week on wesnoth during that time. To tackle this problem, some people at #wesnoth-dev have suggested that I start early, which is generally possible.
I could start on the actual work as soon as May 16th, which is a week earlier than the official date. This could help me to regain the lost time.
Note that this estimation is more on the worst-case side. Things may turn out better and I might have more time in June anyways (I will manage 20h a week in any case).
Still, if you think this is not feasible, please tell me so I can reconsider my options.
Second, I will most likely be on vacation from July 12th to July 19th. I hope this would not be too much of a problem.

as for a tentative timeline: (this will be edited after further discussion with the developers)

april 20th - may 15th: "bonding peroid:" I get accepted and start to read documentation, get familiar with the code.

may 16th - june 15th: the actual start of work: (note: the above mentioned part time period)

* I start on the documentation of the current implementation of savegames
* investigation of WML
* play with different scenarios and their savegames
* start to evaluate the problems with/needs for multiplayer campaigns

june 15th - june 30th:

* finish evaluation of problems
* develop a new design of "unified" savegames
* deliver UML model

july 1st - july 11th:

* start of implementation
* goal: get a part of the implementation done before mid-term evaluation

july 12th - july 19th:

* vacation

july 20th - august 10th:

* finish implementation

august 11th - august 17th:

* testing, bug fixing, documentation

'''4.5) Include as much technical detail about your implementation as you can'''

The description of the Savegame project in the wiki suggests that several technical details will be unclear until the design, which is a rather large milestone itself, is fleshed out.
Concerning the design milestone, I plan to deliver a UML model describing the new savegame organization.

'''4.6) What do you expect to gain from this project?'''

I would like to:
* gain insight on the development of large open source projects
* learn more about game design
* improve my coding skills
* last but not least, I want to gain the satisfaction of contributing something worthy to such a big project

'''4.7) What would make you stay in the Wesnoth community after the conclusion of SOC?'''

The success of my project and/or the feeling that I have not completely made a fool of myself :).

====5) Practical considerations====

'''5.1) Are you familiar with any of the following tools or languages?'''

* Subversion (used for all commits)
Yes, I have used SVN for university projects and my master thesis.
* C++ (language used for all the normal source code)
Yes, I think I have good C++ skills. To elaborate with the C++ quiz on http://www.wesnoth.org/wiki/Hackingwesnoth : I fit in the "can answer most questions" category (I looked up the ones I did not know of course).
* Python (optional, mainly used for tools)
Sorry, I do not have Python skills.
* build environments (eg cmake/autotools/scons)
I used autotools in a university project.

'''5.2) Which tools do you normally use for development? Why do you use them?'''

For larger projects: Eclipse, Netbeans. I use them for their debugging capabilities and for convenience features like code completion
for smaller stuff: vi, sometimes jEdit, gdb. I use them for their simplicity and their wide availability.

'''5.3) What programming languages are you fluent in?'''

Java, C++, Haskell. I have mostly used them in university courses. Additionally, I have been a tutor for undergraduate Java courses and used Haskell for my masters project.

'''5.4) What spoken languages are you fluent in?'''

I am a German native speaker and I am fluent in English. I also speak a bit French and Russian

'''5.5) At what hours are you awake and when will you be able to be in IRC (please specify in UTC)'''

Austria is UTC+1, so my usual working/availability hours would be UTC: 8am - 4pm, but its flexible to some degree. On some days, I will most likely be available longer into the evening.

'''5.6) Would you mind talking with your mentor on telephone / internet phone? We would like to have a backup way for communications for the case that somehow emails and IRC do fail.'''

I would mind not at all. I am fine with both phone and voice chat if you can bear with my german accent :).

==Ideas on Savegame Reorganization==

===WML Mapping Redundancies===

In general, we can distinguish between two types of redundancies:

'''A:''' information is stored in two or more places in a savegame file (WML), but is mapped to the '''same c++ object.'''

'''B:''' information is stored in two or more places in WML, and is mapped to '''more than one c++ object'''.

Both types are worth fixing.

As mentioned on [[SoC_Ideas_Savegame]], WML events can change a lot of information of a scenario, which makes some redundancies, e.g., between [snapshot] and root/[replay_start], necessary. I will list some info in WML that I think is unnecessarily redundant. (and verify my thoughts with a WML expert).

'''root vs [snapshot] (type A)'''

serveral fields appear on the root and again under [snapshot]. The following are candidates for redundancy elimination:

* abbrev
* version
* campaign (SP only)
* campaign_type
* campaign_define
* random_seed
* difficulty
* random_calls
* underlying_unit_id (task?)

I think these need to be stored twice:
* label (different in root and [snapshot])
* completion
* end_text_duration (different endings possible)

'''[player] vs [snapshot.side] (type B)'''

[player] (SP only) only holds a few items, most of which occur in [snapshot.side]. Additionally, both map to different c++ objects, player_info and team.info_ .

==Milestones and Timeline==

back to: [[SummerOfCodeIdeas| GSoC Ideas]]

[[Category:Summer of Code]]

SummerOfCodeProposal grantwu

2009-03-27T22:59:49Z

Yogi Bear:

==Basics==

===Introduction===
My name is Grant Wu and I hope to work with the Wesnoth developers over the summer as part of Google's Summer of Code.

===Preferred E-mail Address===
grantwu at umich dot edu

===Handles===
My handle on the IRC channels is 'grantwu' while my name on the forums is 'zenneth'.

===Why GSoC?===
I want to participate in Google's Summer of Code in order to gain experience working with veteran coders on a project that interests me. I plan on entering the video game industry after I graduate so the Wesnoth project looks like the best fit to me.

===School===
I am currently enrolled at the University of Michigan in Ann Arbor. I am in my second year of studying Computer Science through the College of Engineering.

===Patches for Wesnoth===
I have not yet submitted anything to the Wesnoth project but I plan on doing my best to change that.

==Experience==

===Projects===
My current experience is largely through assignments from my classes. One of my classes is entirely project based so I know how to handle larger tasks. The biggest programming project I've worked on so far was actually a video game. I made a 2D platformer with some physics twists to it. Not the most complicated but it gave me valuable experience.

===Groups===
My very first programming class at the University focused on pair programming. All of our projects were done with a partner. This taught me a lot of valuable lessons when it comes to just how fallible every programmer is. The video game project I described in the previous section was also done in a team of 4. The people I worked with were all passionate about video games and programming. I learned to appreciate being in such an environment and I'm well aware that some groups won't be as ideal.

===Previous GSoCs===
I have never participated in Google's Summer of Code before.

===Open Source===
I have very limited experience working with open source projects. By limited I mean I use Ubuntu as my standard operating system for my netbook. I hope to remedy this unfortunate situation.

===Am I a Gamer===
Am I a gamer? Hell yeah. Gaming is my passion. I play everything and anything. Unusually enough I was looking for a turn-based strategy RPG to play before I found Wesnoth. Convenient.

====Type of Gamer====
I'm a hardcore gamer. There's no other way to describe my relationship with video games.

====Types of Games====
Like I said before, I play pretty much anything. My favorites right now include Left 4 Dead, Civilization IV, Team Fortress 2, and Dawn of War II. I also play a lot of FIFA 09 and I still play Mass Effect now and then. I plan on getting more into Wesnoth too.

====Types of Opponents====
My ideal human opponent is a mythical beast that does not exist. Someone who is respectful but not afraid to do a little trash talking to put an edge on things. My ideal AI opponent also probably doesn't exist but I'm pretty sure devs fake it. The one thing that I feel an AI opponent has to do is be adaptable and challenging while remaining fair. I hope that gone are the days where computer bots could see through walls in shooters and have laser vision to pierce through fog of war in strategy games.

====Story or Gameplay====
I'd love to have both, but sadly its usually only one. If a game has poor story and good gameplay just the experience of playing the game will push it through. I feel like this is usually the case with games, not ideal at all. There has been the rare game where the story was what kept me playing. For example, when I'm in the right mood I like to burn through Japanese RPGs. Japanese RPGs so often fall into the same trappings when it comes to gameplay but the story keeps me mashing the attack command for hours and hours.

====Played Wesnoth====
I have played a little bit. I didn't know about it until I saw it on GSoC's list of projects. I plan on sinking my teeth into it more and if worse comes to worst at least I was introduced to a good game. For the moment I'm going to try to get better at the game through single player and eventually make the dive into multiplayer.

==Communication Skills==

===English===
English is my native tongue and I think I'm pretty good at communicating with it.

===Player Community===
Being a pretty competitive gamer myself I'm well aware of how nasty the player community can get (NERF PALADINS! NERF THE DEMOMAN!). I'm more than prepared to handle that.

===Constructive Advice===
In my opinion, if it isn't constructive then really is no reason to give it. When I give feedback I try to form it in a way that is most useful to the recipient.

===How Well Do I Receive Advice===
One of the positions I hold at my University is the Publications Chair for a student organization. I create flyers and basically mold the image of the org. Because of this I receive constant feedback from the other members about my work and I'm experienced with taking in a wide variety of suggestions. My group programming projects also had a lot of back and forth communication. After implementing a new feature we'd all sit down and discuss what's good, what's bad, and the person in charge of that feature would go back and make whatever changes we decided on.

===Filter Feedback===
Again my previous experiences have taught me a lot of about taking in and digesting feedback. You can't take every piece of advice as gospel. I've burned a lot of time sitting down and mulling over the feedback I've gotten on my work.

==Project==

===Which Project I Picked===
I picked the save game project. I hope to make the multiplayer and single player experience of Wesnoth indistinguishable, at least when it comes to saving.

===Why This Project===
If there's one thing that I love about games, its working together with another player. Getting a multiplayer campaign option working for Wesnoth would be a huge step for it and add a hugely valuable feature. In addition to this, I feel that this project is very doable with my current experience with C++. Finally, the class where I created my first game emphasized the important of UML and language-independent representation of code. I feel like I can use what I learned from that class on this project.

===Timeline===
{| border="1"
|align="right" width="125"|March 25th - April 29th
|align="left"|These are the remaining days of the school semester. I plan on using this time to familiarize myself with everything Wesnoth. Code, the community, everything.
|-
|align="right" width="125"|April 29th - May 23rd
|align="left"|Begin working with my mentor on the overall design of how to change the save file structure. I should be familiar enough with how everything works by this point to keep things moving, however, this is the most important part of the process so I a significant amount of time should be devoted to design. UML diagrams and such will be drawn up during this time.
|-
|align="right" width="125"|May 24rd - June 14th
|align="left"|Prototyping should begin now. This is also the prescribed "start coding!" time from Google. Hopefully with the early start on the project this will give me time to come up with more than one prospective implementation idea to work with. This way I can start prototyping and see if there are any unforeseen shortcomings to the proposed solutions.
|-
|align="right" width="125"|June 14th - June 16th
|align="left"|After a few weeks of rapid prototyping I hope to discuss the results of all the test runs with my mentor. We'll weigh the options and hopefully quickly come to a conclusion on what the ideal solution candidate.
|-
|align="right" width="125"|June 16th - July 10th
|align="left"|At this point I'll begin the final implementation of the code. Of course I'm still far from being done. I'll work closely with my mentor to get the final product up and running by when Google requests us to turn in midterm reviews.
|-
|align="right" width="125"|July 10th - August 10th
|align="left" width="125"|So while my experience with open source is limited, from what I can see the success of any open source project is the community. At this time I would like to release the final product to the community and try to use whatever good feedback I get. I'll continue to polish it until the Google's given deadline and probably work on it beyond then.
|}

===Technical Details===
I'm going to leave this section unpopulated for now until I become more familiar with Wesnoth's source code.

===My Own Personal Gain===
I hope to become involved in an active open source project and community while gaining experience on working with a video game. I'm pretty sure Wesnoth will provide both.

===Continued Involvement===
I feel as though after reading the documentation and just lurking around the IRC channel and forums that the Wesnoth community is a very healthy one. My continued involvement with the project is directly related to the activity of the community as a whole.

==Practical Considerations==
===Languages===
All the required Computer Science courses taught through the College of Engineering here use C++. I'm very familiar and comfortable with writing code in it and learning with C++. I don't know very much Python and I'm not familiar with build environments. Build environments are number one on my list of things to learn though.

===Tools===
I write my code in either gedit or emacs. I use gedit because its a convenient and modern editor while I use emacs when working on my schools remote computing environments. I use g++ to compile my C++ code and I haven't needed to use anything else as of yet.

===Fluent Programming Languages===
I am most familiar with C++. I've spent two years working with it pretty extensively now. I also feel that one of the courses I'm taking now is covering some of the most vital aspects of the language and object oriented programming in general. The first part of the course was review but now we're going over abstract data types and the very important features that OO programming provides (from what I read, Wesnoth's lead dev is very passionate about encapsulation).

===Fluent Spoken Languages===
I am fluent in English and spoken Mandarin Chinese. I also know a bit of German.

===Waking Hours===
I'm usually up from late morning to early morning. 10AM - 3AM are most likely. During the summer I can be on IRC at almost all times though I like to keep an active and healthy lifestyle so I'll have to stray away from the keyboard at times.

===Phone Calls===
I'd actually prefer to communicate on the phone. Makes for a stronger relationship. Unfortunately, computer science lends itself to digital communication due to the technical nature of the subject.

[[Category:Summer of Code]]

EasyCoding

2009-03-26T23:57:43Z

Yogi Bear: /* Savegame related stuff */

== Foreword ==
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

--[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)

Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).

--Yogi Bear, 28 February 2008

== MP related features ==

=== Use different font for in-game chat ===
Since commas and dots are apparently hard to tell apart. As per FR #7470 [https://gna.org/bugs/?7470]

== WML related features ==

=== WML configurable village income / upkeep ===
Preferably as a [scenario], [side] or [campaign] keys. As per FR #6301 [https://gna.org/bugs/?6301]

=== Add support of [if] for [scenario] ===
As per FR #4539 [https://gna.org/bugs/?4539]

=== Make [have_unit] optionaly use full SUF ===
[have_unit] by default uses SUF but does not apply it to recall list. Introduce an optional key that will allow to lift that limitation.

=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960]) -- [[User:dlr365|dlr365]] -- patch submitted [https://gna.org/bugs/index.php?4960]

=== Support for leaderless multiplayergames ===
Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])

=== Support for standalone multiplayer scenarios ===
There used to be support for standalone scenarios in the userdata tree, in reorganising the trees this feature got lost and an add-on is now required to add a scenario.
Re-add this feature. It is probably a good idea to mirror the mainline multiplayer tree.

=== Other Ideas ===
See [[FutureWML]]; some ideas there are easier than others.

== Improvements to FormulaAI ==

Add new formula functions, or minor improvements to the formula language. Make it easier to debug the formula language.

Please discuss these with Dragonking, Sirp or Boucman

=== Poisoning Improvement ===

Writing a formula that will make units with poison attacks prioritize their targets to spead poison as much as possible, avoiding already poisoned units and other useless targets

=== About to level formula ===

Writing a formula that would handle units with only a few XP left to level and have them fight accordingly (most likely to kill or hit depending on XP needed, taking into account target's level)

=== Healer improvements ===

Handle units with healing power, moving them at places where they can provide the most healing

=== Leader improvements ===

A bit more complicated : special handling of units with leadership to have them support units. Only do it if it actually is usefull (less hits needed to kill the unit) and ability to help multiple units in a single turn (assuming enough MP)

=== Berserker improvements ===

The default AI's strategy of attacking as much as possible is very bad with berserker... A simple AI that would prevent the berserker from attacking (and keeping him close to fight without being exposed) and attack when the chance to kill is high enough would be an interesting addition

=== Debugging help ===

<s>* provide a way for a formula to have a text float over hex (for debugging purpose).</s> done by [[SummerOfCodeProposal_AI_Improvement_Crab|Crab]], patch submitted [https://gna.org/bugs/?13230]
* in debug mode, have all AI move print their name in the log

=== New type of candidate moves : Global ===

to be called only once with no implicit variable

== GUI related features ==
-------------------

Note at the moment Mordante is working on a new GUI system, these
changes will probably affect the way these items need to be implemented.
Contact Mordante on IRC before starting to work on these.

--[[User:SkeletonCrew|SkeletonCrew]] 14:04, 9 March 2008 (EDT)

=== Theme Changes ===

* allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])
* hide the hourglass item from the statusbar when there is no timer

=== Widget Changes ===
* show side number, name and team association information in the status table
* make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
* input history (chat, commands, ..) - note: rujasu is working on this feature

== GUI2 related features ==
GUI2 is the new gui engine Mordante/SkeletonCrew is working on.
* Information on the wiki can be found here http://www.wesnoth.org/wiki/GUIToolkit
* The source code is under src/gui/
* The configuration config files are under data/gui/default

Some tasks need the --new-widgets since the code is only shown in the experimental mode. Tasks which need this switch have the * in the title.

=== Generic yes/no ok/cancel dialog ===
There's already a generic OK dialog
* src/gui/dialogs/message.[h|c]pp
* data/gui/default/window/message.cfg

This dialog should have the option to show a cancel button as well and also let the caller of the dialog determine the text of the button. Maybe more buttons (4 in total) can be added to make the dialog more flexible.

=== * Minimap ===
The minimap widget has already been made but is broken.
* src/gui/widgets/minimap.[c|h]pp

The drawing code has been rewritten, but this widget hasn't been updated it's used in the MP connection dialog (which needs more work).

=== * Savegame dialog ===
This is a new dialog to write and requires the minimap code to be fixed first. The dialog should mimic the current dialog. Sorting of a listbox and the proper alignment of the columns is not important (the engine doesn't support this yet). The code should only be used when --new-widgets is used as start switch since we're in a feature freeze at the moment.

=== * Title screen ===
A start has been made for the new titlescreen
* src/gui/dialogs/title_screen.[c|h]pp
* data/gui/default/window/title_screen.cfg
This should be improved to include the buttons and alignment of the current title screen. The 'roll-over' image is not part of this task.

=== Arrow keys for the slider ===
There's a new slider widget, but it doesn't support the keyboard yet.
gui/widgets/slider.[c|h]pp

Clicking on the widget should capture the keyboard and then arrow left/right should move one step even if not all steps are visible.

=== Slider sizing ===
There are some issues with the sizing of a slider.
gui/widgets/slider.[c|h]pp

In a layout step it needs to try to shrink itself, not entirely sure where or how yet, best ask mordante on irc.

== Savegame related stuff ==

=== consistent player information ===
At the moment, the [player]-section for a campaign savegame will appear in two places: The root level of the savegame and the [replay_start]-section. This was due to a last-minute fix for 1.6 that was designed to be the least intrusive. The [player]-section should only be written to [replay_start] (and of course read from there as well).

=== fix bug #13268 (save corruption through undo/redo of recalls [https://gna.org/bugs/?13268] ===

== Miscellaneous ==

=== More powerful village naming ===
'''Adding mountain names and other features to village names, having a second random name in village names'''

Currently the village naming engine has a very good structure that could allow
more powerfull names to be generated.
Understanding how it works should be quite easy, and a few usefull improvements could be added.

* Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
* It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
* Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice

Euschn 24/03/2009

=== Debug Mode ===
* New debug command functionality (setting additional status.variables, possibly terrain)

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

[[Category:Development]]
[[Category:Future]]

EasyCoding

2009-03-26T23:56:38Z

Yogi Bear: /* Savegame related stuff */

== Foreword ==
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

--[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)

Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).

--Yogi Bear, 28 February 2008

== MP related features ==

=== Use different font for in-game chat ===
Since commas and dots are apparently hard to tell apart. As per FR #7470 [https://gna.org/bugs/?7470]

== WML related features ==

=== WML configurable village income / upkeep ===
Preferably as a [scenario], [side] or [campaign] keys. As per FR #6301 [https://gna.org/bugs/?6301]

=== Add support of [if] for [scenario] ===
As per FR #4539 [https://gna.org/bugs/?4539]

=== Make [have_unit] optionaly use full SUF ===
[have_unit] by default uses SUF but does not apply it to recall list. Introduce an optional key that will allow to lift that limitation.

=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960]) -- [[User:dlr365|dlr365]] -- patch submitted [https://gna.org/bugs/index.php?4960]

=== Support for leaderless multiplayergames ===
Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])

=== Support for standalone multiplayer scenarios ===
There used to be support for standalone scenarios in the userdata tree, in reorganising the trees this feature got lost and an add-on is now required to add a scenario.
Re-add this feature. It is probably a good idea to mirror the mainline multiplayer tree.

=== Other Ideas ===
See [[FutureWML]]; some ideas there are easier than others.

== Improvements to FormulaAI ==

Add new formula functions, or minor improvements to the formula language. Make it easier to debug the formula language.

Please discuss these with Dragonking, Sirp or Boucman

=== Poisoning Improvement ===

Writing a formula that will make units with poison attacks prioritize their targets to spead poison as much as possible, avoiding already poisoned units and other useless targets

=== About to level formula ===

Writing a formula that would handle units with only a few XP left to level and have them fight accordingly (most likely to kill or hit depending on XP needed, taking into account target's level)

=== Healer improvements ===

Handle units with healing power, moving them at places where they can provide the most healing

=== Leader improvements ===

A bit more complicated : special handling of units with leadership to have them support units. Only do it if it actually is usefull (less hits needed to kill the unit) and ability to help multiple units in a single turn (assuming enough MP)

=== Berserker improvements ===

The default AI's strategy of attacking as much as possible is very bad with berserker... A simple AI that would prevent the berserker from attacking (and keeping him close to fight without being exposed) and attack when the chance to kill is high enough would be an interesting addition

=== Debugging help ===

<s>* provide a way for a formula to have a text float over hex (for debugging purpose).</s> done by [[SummerOfCodeProposal_AI_Improvement_Crab|Crab]], patch submitted [https://gna.org/bugs/?13230]
* in debug mode, have all AI move print their name in the log

=== New type of candidate moves : Global ===

to be called only once with no implicit variable

== GUI related features ==
-------------------

Note at the moment Mordante is working on a new GUI system, these
changes will probably affect the way these items need to be implemented.
Contact Mordante on IRC before starting to work on these.

--[[User:SkeletonCrew|SkeletonCrew]] 14:04, 9 March 2008 (EDT)

=== Theme Changes ===

* allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])
* hide the hourglass item from the statusbar when there is no timer

=== Widget Changes ===
* show side number, name and team association information in the status table
* make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
* input history (chat, commands, ..) - note: rujasu is working on this feature

== GUI2 related features ==
GUI2 is the new gui engine Mordante/SkeletonCrew is working on.
* Information on the wiki can be found here http://www.wesnoth.org/wiki/GUIToolkit
* The source code is under src/gui/
* The configuration config files are under data/gui/default

Some tasks need the --new-widgets since the code is only shown in the experimental mode. Tasks which need this switch have the * in the title.

=== Generic yes/no ok/cancel dialog ===
There's already a generic OK dialog
* src/gui/dialogs/message.[h|c]pp
* data/gui/default/window/message.cfg

This dialog should have the option to show a cancel button as well and also let the caller of the dialog determine the text of the button. Maybe more buttons (4 in total) can be added to make the dialog more flexible.

=== * Minimap ===
The minimap widget has already been made but is broken.
* src/gui/widgets/minimap.[c|h]pp

The drawing code has been rewritten, but this widget hasn't been updated it's used in the MP connection dialog (which needs more work).

=== * Savegame dialog ===
This is a new dialog to write and requires the minimap code to be fixed first. The dialog should mimic the current dialog. Sorting of a listbox and the proper alignment of the columns is not important (the engine doesn't support this yet). The code should only be used when --new-widgets is used as start switch since we're in a feature freeze at the moment.

=== * Title screen ===
A start has been made for the new titlescreen
* src/gui/dialogs/title_screen.[c|h]pp
* data/gui/default/window/title_screen.cfg
This should be improved to include the buttons and alignment of the current title screen. The 'roll-over' image is not part of this task.

=== Arrow keys for the slider ===
There's a new slider widget, but it doesn't support the keyboard yet.
gui/widgets/slider.[c|h]pp

Clicking on the widget should capture the keyboard and then arrow left/right should move one step even if not all steps are visible.

=== Slider sizing ===
There are some issues with the sizing of a slider.
gui/widgets/slider.[c|h]pp

In a layout step it needs to try to shrink itself, not entirely sure where or how yet, best ask mordante on irc.

== Savegame related stuff ==

=== consistent player information ===
At the moment, the [player]-section for a campaign savegame will appear in two places: The root level of the savegame and the [replay_start]-section. This was due to a last-minute fix for 1.6 that was designed to be the least intrusive. The [player]-section should only be written to [replay_start] (and of course read from there as well).

=== fix bug #13268 (save corruption through undo/redo [https://gna.org/bugs/?13268]

== Miscellaneous ==

=== More powerful village naming ===
'''Adding mountain names and other features to village names, having a second random name in village names'''

Currently the village naming engine has a very good structure that could allow
more powerfull names to be generated.
Understanding how it works should be quite easy, and a few usefull improvements could be added.

* Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
* It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
* Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice

Euschn 24/03/2009

=== Debug Mode ===
* New debug command functionality (setting additional status.variables, possibly terrain)

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

[[Category:Development]]
[[Category:Future]]

EasyCoding

2009-03-26T22:24:56Z

Yogi Bear:

== Foreword ==
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

--[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)

Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).

--Yogi Bear, 28 February 2008

== MP related features ==

=== Use different font for in-game chat ===
Since commas and dots are apparently hard to tell apart. As per FR #7470 [https://gna.org/bugs/?7470]

== WML related features ==

=== WML configurable village income / upkeep ===
Preferably as a [scenario], [side] or [campaign] keys. As per FR #6301 [https://gna.org/bugs/?6301]

=== Add support of [if] for [scenario] ===
As per FR #4539 [https://gna.org/bugs/?4539]

=== Make [have_unit] optionaly use full SUF ===
[have_unit] by default uses SUF but does not apply it to recall list. Introduce an optional key that will allow to lift that limitation.

=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960]) -- [[User:dlr365|dlr365]] -- patch submitted [https://gna.org/bugs/index.php?4960]

=== Support for leaderless multiplayergames ===
Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])

=== Support for standalone multiplayer scenarios ===
There used to be support for standalone scenarios in the userdata tree, in reorganising the trees this feature got lost and an add-on is now required to add a scenario.
Re-add this feature. It is probably a good idea to mirror the mainline multiplayer tree.

=== Other Ideas ===
See [[FutureWML]]; some ideas there are easier than others.

== Improvements to FormulaAI ==

Add new formula functions, or minor improvements to the formula language. Make it easier to debug the formula language.

Please discuss these with Dragonking, Sirp or Boucman

=== Poisoning Improvement ===

Writing a formula that will make units with poison attacks prioritize their targets to spead poison as much as possible, avoiding already poisoned units and other useless targets

=== About to level formula ===

Writing a formula that would handle units with only a few XP left to level and have them fight accordingly (most likely to kill or hit depending on XP needed, taking into account target's level)

=== Healer improvements ===

Handle units with healing power, moving them at places where they can provide the most healing

=== Leader improvements ===

A bit more complicated : special handling of units with leadership to have them support units. Only do it if it actually is usefull (less hits needed to kill the unit) and ability to help multiple units in a single turn (assuming enough MP)

=== Berserker improvements ===

The default AI's strategy of attacking as much as possible is very bad with berserker... A simple AI that would prevent the berserker from attacking (and keeping him close to fight without being exposed) and attack when the chance to kill is high enough would be an interesting addition

=== Debugging help ===

<s>* provide a way for a formula to have a text float over hex (for debugging purpose).</s> done by [[SummerOfCodeProposal_AI_Improvement_Crab|Crab]], patch submitted [https://gna.org/bugs/?13230]
* in debug mode, have all AI move print their name in the log

=== New type of candidate moves : Global ===

to be called only once with no implicit variable

== GUI related features ==
-------------------

Note at the moment Mordante is working on a new GUI system, these
changes will probably affect the way these items need to be implemented.
Contact Mordante on IRC before starting to work on these.

--[[User:SkeletonCrew|SkeletonCrew]] 14:04, 9 March 2008 (EDT)

=== Theme Changes ===

* allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])
* hide the hourglass item from the statusbar when there is no timer

=== Widget Changes ===
* show side number, name and team association information in the status table
* make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
* input history (chat, commands, ..) - note: rujasu is working on this feature

== GUI2 related features ==
GUI2 is the new gui engine Mordante/SkeletonCrew is working on.
* Information on the wiki can be found here http://www.wesnoth.org/wiki/GUIToolkit
* The source code is under src/gui/
* The configuration config files are under data/gui/default

Some tasks need the --new-widgets since the code is only shown in the experimental mode. Tasks which need this switch have the * in the title.

=== Generic yes/no ok/cancel dialog ===
There's already a generic OK dialog
* src/gui/dialogs/message.[h|c]pp
* data/gui/default/window/message.cfg

This dialog should have the option to show a cancel button as well and also let the caller of the dialog determine the text of the button. Maybe more buttons (4 in total) can be added to make the dialog more flexible.

=== * Minimap ===
The minimap widget has already been made but is broken.
* src/gui/widgets/minimap.[c|h]pp

The drawing code has been rewritten, but this widget hasn't been updated it's used in the MP connection dialog (which needs more work).

=== * Savegame dialog ===
This is a new dialog to write and requires the minimap code to be fixed first. The dialog should mimic the current dialog. Sorting of a listbox and the proper alignment of the columns is not important (the engine doesn't support this yet). The code should only be used when --new-widgets is used as start switch since we're in a feature freeze at the moment.

=== * Title screen ===
A start has been made for the new titlescreen
* src/gui/dialogs/title_screen.[c|h]pp
* data/gui/default/window/title_screen.cfg
This should be improved to include the buttons and alignment of the current title screen. The 'roll-over' image is not part of this task.

=== Arrow keys for the slider ===
There's a new slider widget, but it doesn't support the keyboard yet.
gui/widgets/slider.[c|h]pp

Clicking on the widget should capture the keyboard and then arrow left/right should move one step even if not all steps are visible.

=== Slider sizing ===
There are some issues with the sizing of a slider.
gui/widgets/slider.[c|h]pp

In a layout step it needs to try to shrink itself, not entirely sure where or how yet, best ask mordante on irc.

== Savegame related stuff ==

=== consistent player information ===
At the moment, the [player]-section for a campaign savegame will appear in two places: The root level of the savegame and the [replay_start]-section. This was due to a last-minute fix for 1.6 that was designed to be the least intrusive. The [player]-section should only be written to [replay_start] (and of course read from there as well).

== Miscellaneous ==

=== More powerful village naming ===
'''Adding mountain names and other features to village names, having a second random name in village names'''

Currently the village naming engine has a very good structure that could allow
more powerfull names to be generated.
Understanding how it works should be quite easy, and a few usefull improvements could be added.

* Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
* It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
* Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice

Euschn 24/03/2009

=== Debug Mode ===
* New debug command functionality (setting additional status.variables, possibly terrain)

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

[[Category:Development]]
[[Category:Future]]

SoC People to bug on IRC

2009-03-25T22:07:28Z

Yogi Bear: /* YogiHH or Piotr Cychowski (cycholka) */

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

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

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

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

=== Dragonking ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Summer of Code]]

SoC Ideas Savegame

2009-03-25T22:02:37Z

Yogi Bear: /* Proposal contents */

=== Reorganizing the savegame format ===

Wesnoth basically supports two types of scenarios: Single player campaign (one campaign consists of several scenarios) and multiplayer (one isolated scenario). The savegame information for both share a lot of stuff, but there are also differences, information which is unique to each of them.

Lately, there is another development showing up, which wasn't really considered in the beginning of wesnoth: Multiplayer campaigns. Those kind of work at the moment, but they are a little uncomfortable, because the savegame format does not support them good enough.

Your task will be to develop a uniform savegame format, that allows to store all information needed for any kind of scenario and to write the code supporting this format.

==== General description ====

The idea behind this project is that there won't be any significant differences (at least regarding the savegame format) between single player and multiplayer anymore. Rather, multiplayer is seen as an enhancement to single player with the main difference being that multiple player information will have to be stored.

From the coding side of perspective, you might think that you will be able to reuse lots of existing code. In a way this will be true, but there are also some specialties about it:

* At the moment, the code for processing savegames is spread along several files and it is full of workarounds to serve the three main 'consumers': Single player scenarios, multiplayer scenarios and replays. In other words: It is a mess, one of the worst you will be able to find within the wesnoth codebase. Every new coder has to struggle just to ''find'' the functionality he is looking for and senior developers desperately try to avoid any changes to it.
* Although you will be able to reuse some of the code, you also will have to think of a new design, that combines the current still separated approaches to the different types of scenarios. It might turn out, that starting your code from scratch is a better idea than rewriting the existing stuff.
* Basically, the challenge of this project won't be writing the code in the first place, but rather figuring out what is the best way to rework it: How do i minimize impact? How can i design the code so that it is easy to understand and maintainable? What information is needed upfront to achieve that?. These are the important questions that you will tackle in close teamwork with your mentor.
* The intent of this project is to adapt the content of savegames, not the format that content is stored in. WML has been proven to be an efficient format and we don't want to change it.

==== Required knowledge and talent ====

* ''A minimal knowledge of C++ is required, a good knowledge of C++ is desired :'' The main challenge will be to become familiar with the common style of wesnoth coding, since we widely use some advanced C++ features like STL and rely on a couple of libraries. However, the savegame processing code is relatively straightforward and not as complex as many other areas.
* ''Design capabilities: '' Because your code will have to integrate into the current wesnoth architecture, you can't just grab the keyboard and start hacking (well, you shouldn't do that anyway but that's another topic for another day ;-). So a very important part of this project will be to provide a good design and put some thought into that. It is also essential, that this won't happen solely inside your head but that you also provide some visible results (see the list of milestones and deliverables below). Static (or maybe even dynamic) UML models would be really cool, but they are not required. Any other technique, be it a diagram or simple text will do as well, as long as it contains the needed information. ''Depending on your experience and skills, your mentor will closely interact with you throughout this work and give you the support you need.''
* ''Good social interaction with the multiplayer community :'' As mentioned before, multiplayer campaigns are one of the triggers for this task. There are some multiplayer campaigns and part of your work will be to get in contact with the maintainers and get an understanding of the current problems in order to decide how to support needed features with savegame information.

==== Milestones and deliverables ====

Some of the milestones will become obvious after the design phase is finished, but here are some ideas of what needs to be done:

* ''Being familiar with the code :'' To get a better understanding, you will have to examine the currently available code, find all the places that deal with savegame information and roughly understand what their specific task is about. This should be documented. You will also have to learn the text representation of savegame information which is done by WML, a markup language that is widely used within wesnoth. Play a little with the different kind of scenarios and see what savegames get out of that and what the code is doing with them.
* ''Design :'' Evaluating the current problems with multiplayer campaigns will be needed for this phase. After you have done this, you will have to develop a new savegame format and a design for the code that is processing it. The delivery will be at least some kind of static model (preferably UML but other techniques will do as well) and a roadmap of steps to get from the current code to the new one.
* ''Implementing :'' It is hard to give detailed information about the content of this phase. But basically it will be implementing the roadmap steps one by one.

=== Proposal contents ===
Here are some questions and ideas to help you dive into the topic. They are meant to help you get a better idea of what this project is going to be about. They are also meant to show us, how much you made yourself familiar with wesnoth's code, as this is very important to us. We are mostly ambitious and passionate ourselves, and we seek for students that are alike. Other (wesnoth) projects provide the opportunity to present prototypes, which won't be working here. Therefore it is even more important, that you implement some patches to show us your coding skills.<br>
However, there is some preparation you can do by now already. You should also add your thoughts about this to the proposal you are giving us. If you get accepted, this will serve as a starting point for further fleshing out things.

Don't hesitate to seek for help, if you have difficulties with some of the questions. I (YogiHH) will be on IRC most of the time in the evening (GMT+1) hours. You can also reach me by mail (joerg.hinrichs@alice-dsl.de) if that is not sufficient. Also keep in mind, that this is not a typical test with "right and wrong". It is clear that being new you won't be able to provide the "perfect proposal" right out of the box. We are more interested in how you approach this task, how you communicate and if you can focus on the relevant stuff without losing yourself into details. So know what you are talking about, be innovative and take initiative.

The following two links are meant to give you further information for that:<br>
[[SavegameCode|savegame code]] - Contains the pieces of codes that deal with savegames and where to find them<br>
[[Summer of Code:SavegameWMLMapping|WML - object mapping]] - A mapping table to show you which objects hold the information of the savegame WML content<br>

1.
<p>If you take a closer look at the code, you will find, that there are different architectures of design to implement persistence. One is a more layered approach, which separates the creation and population of objects from persistent information (a savegame file, represented by a config object) from the rest. Config_adapter.cpp is an example of that idea. The other passes the raw persistence information (=config object) to the object to be created and lets it do the work. An example for this is the game_state constructor that takes a config object as argument.</p>
Which are the pro's and con's of those approaches with regard to encapsulation and maintenance? What would you choose for wesnoth's savegame processing?

2.
If your task is to remove config_adapter.cpp, how would you do that? Where would you put the code instead? And what are your reasons for that?

3.
The <i>player_info</i> struct and the <i>team</i> class share some information (for example units that belong to a certain side). Do you think it is feasible to mold those two into one? And what are your reasons?

4.
The same question is to be asked for the <i>game_state</i> class and the <i>gamestatus</i> class.

5.
The second link above contains a mapping table, that matches savegame WML tags to C++ objects. Identify candidates for redundancies. Warning: Keep in mind, that WML is a mighty beast! Just one example: Through WML events, a map can change throughout a scenario. Therefore it makes a lot of sense to put that map into the [snapshot] and [replay_start] tags respectively, although at first glance it looks like we could put it into some central place. After you identified candidates for redundant information, you might want to talk to one of the WML experts to make sure those information is really redundant.

6.
Based on the thoughts you layed out in 1-5, what would the new savegame structure you propose be like? A level of detail like it is outlined in the mapping table will suffice here. Please also make sure, that your proposal is consistent with the idea of multiplayer campaigns.

=== See also ===
[[SummerOfCodeIdeas|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.<br>
[[User:SkeletonCrew#Savegame_format|savegame contents]] - Some ideas about the current and future content of savegames.<br>
[[SavefileWML|Savegame WML]] - Information about the format used for storing savegame information.
[[Category:Summer of Code]]

SoC Ideas Savegame

2009-03-25T21:57:08Z

Yogi Bear: /* Proposal contents */

=== Reorganizing the savegame format ===

Wesnoth basically supports two types of scenarios: Single player campaign (one campaign consists of several scenarios) and multiplayer (one isolated scenario). The savegame information for both share a lot of stuff, but there are also differences, information which is unique to each of them.

Lately, there is another development showing up, which wasn't really considered in the beginning of wesnoth: Multiplayer campaigns. Those kind of work at the moment, but they are a little uncomfortable, because the savegame format does not support them good enough.

Your task will be to develop a uniform savegame format, that allows to store all information needed for any kind of scenario and to write the code supporting this format.

==== General description ====

The idea behind this project is that there won't be any significant differences (at least regarding the savegame format) between single player and multiplayer anymore. Rather, multiplayer is seen as an enhancement to single player with the main difference being that multiple player information will have to be stored.

From the coding side of perspective, you might think that you will be able to reuse lots of existing code. In a way this will be true, but there are also some specialties about it:

* At the moment, the code for processing savegames is spread along several files and it is full of workarounds to serve the three main 'consumers': Single player scenarios, multiplayer scenarios and replays. In other words: It is a mess, one of the worst you will be able to find within the wesnoth codebase. Every new coder has to struggle just to ''find'' the functionality he is looking for and senior developers desperately try to avoid any changes to it.
* Although you will be able to reuse some of the code, you also will have to think of a new design, that combines the current still separated approaches to the different types of scenarios. It might turn out, that starting your code from scratch is a better idea than rewriting the existing stuff.
* Basically, the challenge of this project won't be writing the code in the first place, but rather figuring out what is the best way to rework it: How do i minimize impact? How can i design the code so that it is easy to understand and maintainable? What information is needed upfront to achieve that?. These are the important questions that you will tackle in close teamwork with your mentor.
* The intent of this project is to adapt the content of savegames, not the format that content is stored in. WML has been proven to be an efficient format and we don't want to change it.

==== Required knowledge and talent ====

* ''A minimal knowledge of C++ is required, a good knowledge of C++ is desired :'' The main challenge will be to become familiar with the common style of wesnoth coding, since we widely use some advanced C++ features like STL and rely on a couple of libraries. However, the savegame processing code is relatively straightforward and not as complex as many other areas.
* ''Design capabilities: '' Because your code will have to integrate into the current wesnoth architecture, you can't just grab the keyboard and start hacking (well, you shouldn't do that anyway but that's another topic for another day ;-). So a very important part of this project will be to provide a good design and put some thought into that. It is also essential, that this won't happen solely inside your head but that you also provide some visible results (see the list of milestones and deliverables below). Static (or maybe even dynamic) UML models would be really cool, but they are not required. Any other technique, be it a diagram or simple text will do as well, as long as it contains the needed information. ''Depending on your experience and skills, your mentor will closely interact with you throughout this work and give you the support you need.''
* ''Good social interaction with the multiplayer community :'' As mentioned before, multiplayer campaigns are one of the triggers for this task. There are some multiplayer campaigns and part of your work will be to get in contact with the maintainers and get an understanding of the current problems in order to decide how to support needed features with savegame information.

==== Milestones and deliverables ====

Some of the milestones will become obvious after the design phase is finished, but here are some ideas of what needs to be done:

* ''Being familiar with the code :'' To get a better understanding, you will have to examine the currently available code, find all the places that deal with savegame information and roughly understand what their specific task is about. This should be documented. You will also have to learn the text representation of savegame information which is done by WML, a markup language that is widely used within wesnoth. Play a little with the different kind of scenarios and see what savegames get out of that and what the code is doing with them.
* ''Design :'' Evaluating the current problems with multiplayer campaigns will be needed for this phase. After you have done this, you will have to develop a new savegame format and a design for the code that is processing it. The delivery will be at least some kind of static model (preferably UML but other techniques will do as well) and a roadmap of steps to get from the current code to the new one.
* ''Implementing :'' It is hard to give detailed information about the content of this phase. But basically it will be implementing the roadmap steps one by one.

=== Proposal contents ===
Here are some questions and ideas to help you dive into the topic. They are meant to help you get a better idea of what this project is going to be about. They are also meant to show us, how much you made yourself familiar with wesnoth's code, as this is very important to us. We are mostly ambitious and passionate ourselves, and we seek for students that are alike. Other (wesnoth) projects provide the opportunity to present prototypes, which won't be working here. Therefore it is even more important, that you implement some patches to show us your coding skills.<br>
However, there is some preparation you can do by now already. You should also add your thoughts about this to the proposal you are giving us. If you get accepted, this will serve as a starting point for further fleshing out things.

Don't hesitate to seek for help, if you have difficulties with some of the questions. I (YogiHH) will be on IRC most of the time in the evening (GMT+1) hours. You can also reach me by mail (joerg.hinrichs@alice-dsl.de) if that is not sufficient. Also keep in mind, that this is not a typical test with "right and wrong". It is clear that being new you won't be able to provide the "perfect proposal" right out of the box. We are more interested in how you approach this task, how you communicate and if you can focus on the relevant stuff without losing yourself into details. So know what you are talking about, be innovative and take initiative.

The following two links are meant to give you further information for that:<br>
[[SavegameCode|savegame code]] - Contains the pieces of codes that deal with savegames and where to find them<br>
[[Summer of Code:SavegameWMLMapping|WML - object mapping]] - A mapping table to show you which objects hold the information of the savegame WML content<br>

1.
<p>If you take a closer look at the code, you will find, that there are different architectures of design to implement persistence. One is a more layered approach, which separates the creation and population of objects from persistent information (a savegame file, represented by a config object) from the rest. Config_adapter.cpp is an example of that idea. The other passes the raw persistence information (=config object) to the object to be created and lets it do the work. An example for this is the game_state constructor that takes a config object as argument.</p>
Which are the pro's and con's of those approaches with regard to encapsulation and maintenance? What would you choose for wesnoth's savegame processing?

2.
If your task is to remove config_adapter.cpp, how would you do that? Where would you put the code instead? And what are your reasons for that?

3.
The <i>player_info</i> struct and the <i>team</i> class share some information (for example units that belong to a certain side). Do you think it is a feasible idea to mold those two into one? And what are your reasons?

4.
The same question is to be asked for the <i>game_state</i> class and the <i>gamestatus</i> class.

5.
The second link above contains a mapping table, that matches savegame WML tags to C++ objects. Identify candidates for redundancies. Warning: Keep in mind, that WML is a mighty beast! Just one example: Through WML events, a map can change throughout a scenario. Therefore it makes a lot of sense to put that map into the [snapshot] and [replay_start] tags respectively, although at first glance it looks like we could put it into some central place. After you identified candidates for redundant information, you might want to talk to one of the WML experts to make sure those information is really redundant.

6.
Based on the thoughts you layed out in 1-5, what would the new savegame structure you propose be like? A level of detail like it is outlined in the mapping table will suffice here. Please also make sure, that your proposal is consistent with the idea of multiplayer campaigns.

=== See also ===
[[SummerOfCodeIdeas|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.<br>
[[User:SkeletonCrew#Savegame_format|savegame contents]] - Some ideas about the current and future content of savegames.<br>
[[SavefileWML|Savegame WML]] - Information about the format used for storing savegame information.
[[Category:Summer of Code]]

SoC Ideas Savegame

2009-03-25T21:56:22Z

Yogi Bear: /* Proposal contents */

=== Reorganizing the savegame format ===

Wesnoth basically supports two types of scenarios: Single player campaign (one campaign consists of several scenarios) and multiplayer (one isolated scenario). The savegame information for both share a lot of stuff, but there are also differences, information which is unique to each of them.

Lately, there is another development showing up, which wasn't really considered in the beginning of wesnoth: Multiplayer campaigns. Those kind of work at the moment, but they are a little uncomfortable, because the savegame format does not support them good enough.

Your task will be to develop a uniform savegame format, that allows to store all information needed for any kind of scenario and to write the code supporting this format.

==== General description ====

The idea behind this project is that there won't be any significant differences (at least regarding the savegame format) between single player and multiplayer anymore. Rather, multiplayer is seen as an enhancement to single player with the main difference being that multiple player information will have to be stored.

From the coding side of perspective, you might think that you will be able to reuse lots of existing code. In a way this will be true, but there are also some specialties about it:

* At the moment, the code for processing savegames is spread along several files and it is full of workarounds to serve the three main 'consumers': Single player scenarios, multiplayer scenarios and replays. In other words: It is a mess, one of the worst you will be able to find within the wesnoth codebase. Every new coder has to struggle just to ''find'' the functionality he is looking for and senior developers desperately try to avoid any changes to it.
* Although you will be able to reuse some of the code, you also will have to think of a new design, that combines the current still separated approaches to the different types of scenarios. It might turn out, that starting your code from scratch is a better idea than rewriting the existing stuff.
* Basically, the challenge of this project won't be writing the code in the first place, but rather figuring out what is the best way to rework it: How do i minimize impact? How can i design the code so that it is easy to understand and maintainable? What information is needed upfront to achieve that?. These are the important questions that you will tackle in close teamwork with your mentor.
* The intent of this project is to adapt the content of savegames, not the format that content is stored in. WML has been proven to be an efficient format and we don't want to change it.

==== Required knowledge and talent ====

* ''A minimal knowledge of C++ is required, a good knowledge of C++ is desired :'' The main challenge will be to become familiar with the common style of wesnoth coding, since we widely use some advanced C++ features like STL and rely on a couple of libraries. However, the savegame processing code is relatively straightforward and not as complex as many other areas.
* ''Design capabilities: '' Because your code will have to integrate into the current wesnoth architecture, you can't just grab the keyboard and start hacking (well, you shouldn't do that anyway but that's another topic for another day ;-). So a very important part of this project will be to provide a good design and put some thought into that. It is also essential, that this won't happen solely inside your head but that you also provide some visible results (see the list of milestones and deliverables below). Static (or maybe even dynamic) UML models would be really cool, but they are not required. Any other technique, be it a diagram or simple text will do as well, as long as it contains the needed information. ''Depending on your experience and skills, your mentor will closely interact with you throughout this work and give you the support you need.''
* ''Good social interaction with the multiplayer community :'' As mentioned before, multiplayer campaigns are one of the triggers for this task. There are some multiplayer campaigns and part of your work will be to get in contact with the maintainers and get an understanding of the current problems in order to decide how to support needed features with savegame information.

==== Milestones and deliverables ====

Some of the milestones will become obvious after the design phase is finished, but here are some ideas of what needs to be done:

* ''Being familiar with the code :'' To get a better understanding, you will have to examine the currently available code, find all the places that deal with savegame information and roughly understand what their specific task is about. This should be documented. You will also have to learn the text representation of savegame information which is done by WML, a markup language that is widely used within wesnoth. Play a little with the different kind of scenarios and see what savegames get out of that and what the code is doing with them.
* ''Design :'' Evaluating the current problems with multiplayer campaigns will be needed for this phase. After you have done this, you will have to develop a new savegame format and a design for the code that is processing it. The delivery will be at least some kind of static model (preferably UML but other techniques will do as well) and a roadmap of steps to get from the current code to the new one.
* ''Implementing :'' It is hard to give detailed information about the content of this phase. But basically it will be implementing the roadmap steps one by one.

=== Proposal contents ===
Here are some questions and ideas to help you dive into the topic. They are meant to help you get a better idea of what this project is going to be about. They are also meant to show us, how much you made yourself familiar with wesnoth's code, as this is very important to us. We are mostly ambitious and passionate ourselves, and we seek for students that are alike. Other (wesnoth) projects provide the opportunity to present prototypes, which won't be working here. Therefore it is even more important, that you implement some patches to show us your coding skills.<br>
However, there is some preparation you can do by now already. You should also add your thoughts about this to the proposal you are giving us. If you get accepted, this will serve as a starting point for further fleshing out things.

Don't hesitate to seek for help, if you have difficulties with some of the questions. I (YogiHH) will be on IRC most of the time in the evening (GMT+1) hours. You can also reach me by mail (joerg.hinrichs@alice-dsl.de) if that is not sufficient. Also keep in mind, that this is not a typical test with "right and wrong". It is clear that being new you won't be able to make the "perfect proposal" right out of the box. We are more interested in how you approach this task, how you communicate and if you can focus on the relevant stuff without losing yourself into details. So know what you are talking about, be innovative and take initiative.

The following two links are meant to give you further information for that:<br>
[[SavegameCode|savegame code]] - Contains the pieces of codes that deal with savegames and where to find them<br>
[[Summer of Code:SavegameWMLMapping|WML - object mapping]] - A mapping table to show you which objects hold the information of the savegame WML content<br>

1.
<p>If you take a closer look at the code, you will find, that there are different architectures of design to implement persistence. One is a more layered approach, which separates the creation and population of objects from persistent information (a savegame file, represented by a config object) from the rest. Config_adapter.cpp is an example of that idea. The other passes the raw persistence information (=config object) to the object to be created and lets it do the work. An example for this is the game_state constructor that takes a config object as argument.</p>
Which are the pro's and con's of those approaches with regard to encapsulation and maintenance? What would you choose for wesnoth's savegame processing?

2.
If your task is to remove config_adapter.cpp, how would you do that? Where would you put the code instead? And what are your reasons for that?

3.
The <i>player_info</i> struct and the <i>team</i> class share some information (for example units that belong to a certain side). Do you think it is a feasible idea to mold those two into one? And what are your reasons?

4.
The same question is to be asked for the <i>game_state</i> class and the <i>gamestatus</i> class.

5.
The second link above contains a mapping table, that matches savegame WML tags to C++ objects. Identify candidates for redundancies. Warning: Keep in mind, that WML is a mighty beast! Just one example: Through WML events, a map can change throughout a scenario. Therefore it makes a lot of sense to put that map into the [snapshot] and [replay_start] tags respectively, although at first glance it looks like we could put it into some central place. After you identified candidates for redundant information, you might want to talk to one of the WML experts to make sure those information is really redundant.

6.
Based on the thoughts you layed out in 1-5, what would the new savegame structure you propose be like? A level of detail like it is outlined in the mapping table will suffice here. Please also make sure, that your proposal is consistent with the idea of multiplayer campaigns.

=== See also ===
[[SummerOfCodeIdeas|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.<br>
[[User:SkeletonCrew#Savegame_format|savegame contents]] - Some ideas about the current and future content of savegames.<br>
[[SavefileWML|Savegame WML]] - Information about the format used for storing savegame information.
[[Category:Summer of Code]]

SoC Ideas Savegame

2009-03-25T21:29:31Z

Yogi Bear: /* Proposal contents (under construction) */

=== Reorganizing the savegame format ===

Wesnoth basically supports two types of scenarios: Single player campaign (one campaign consists of several scenarios) and multiplayer (one isolated scenario). The savegame information for both share a lot of stuff, but there are also differences, information which is unique to each of them.

Lately, there is another development showing up, which wasn't really considered in the beginning of wesnoth: Multiplayer campaigns. Those kind of work at the moment, but they are a little uncomfortable, because the savegame format does not support them good enough.

Your task will be to develop a uniform savegame format, that allows to store all information needed for any kind of scenario and to write the code supporting this format.

==== General description ====

The idea behind this project is that there won't be any significant differences (at least regarding the savegame format) between single player and multiplayer anymore. Rather, multiplayer is seen as an enhancement to single player with the main difference being that multiple player information will have to be stored.

From the coding side of perspective, you might think that you will be able to reuse lots of existing code. In a way this will be true, but there are also some specialties about it:

* At the moment, the code for processing savegames is spread along several files and it is full of workarounds to serve the three main 'consumers': Single player scenarios, multiplayer scenarios and replays. In other words: It is a mess, one of the worst you will be able to find within the wesnoth codebase. Every new coder has to struggle just to ''find'' the functionality he is looking for and senior developers desperately try to avoid any changes to it.
* Although you will be able to reuse some of the code, you also will have to think of a new design, that combines the current still separated approaches to the different types of scenarios. It might turn out, that starting your code from scratch is a better idea than rewriting the existing stuff.
* Basically, the challenge of this project won't be writing the code in the first place, but rather figuring out what is the best way to rework it: How do i minimize impact? How can i design the code so that it is easy to understand and maintainable? What information is needed upfront to achieve that?. These are the important questions that you will tackle in close teamwork with your mentor.
* The intent of this project is to adapt the content of savegames, not the format that content is stored in. WML has been proven to be an efficient format and we don't want to change it.

==== Required knowledge and talent ====

* ''A minimal knowledge of C++ is required, a good knowledge of C++ is desired :'' The main challenge will be to become familiar with the common style of wesnoth coding, since we widely use some advanced C++ features like STL and rely on a couple of libraries. However, the savegame processing code is relatively straightforward and not as complex as many other areas.
* ''Design capabilities: '' Because your code will have to integrate into the current wesnoth architecture, you can't just grab the keyboard and start hacking (well, you shouldn't do that anyway but that's another topic for another day ;-). So a very important part of this project will be to provide a good design and put some thought into that. It is also essential, that this won't happen solely inside your head but that you also provide some visible results (see the list of milestones and deliverables below). Static (or maybe even dynamic) UML models would be really cool, but they are not required. Any other technique, be it a diagram or simple text will do as well, as long as it contains the needed information. ''Depending on your experience and skills, your mentor will closely interact with you throughout this work and give you the support you need.''
* ''Good social interaction with the multiplayer community :'' As mentioned before, multiplayer campaigns are one of the triggers for this task. There are some multiplayer campaigns and part of your work will be to get in contact with the maintainers and get an understanding of the current problems in order to decide how to support needed features with savegame information.

==== Milestones and deliverables ====

Some of the milestones will become obvious after the design phase is finished, but here are some ideas of what needs to be done:

* ''Being familiar with the code :'' To get a better understanding, you will have to examine the currently available code, find all the places that deal with savegame information and roughly understand what their specific task is about. This should be documented. You will also have to learn the text representation of savegame information which is done by WML, a markup language that is widely used within wesnoth. Play a little with the different kind of scenarios and see what savegames get out of that and what the code is doing with them.
* ''Design :'' Evaluating the current problems with multiplayer campaigns will be needed for this phase. After you have done this, you will have to develop a new savegame format and a design for the code that is processing it. The delivery will be at least some kind of static model (preferably UML but other techniques will do as well) and a roadmap of steps to get from the current code to the new one.
* ''Implementing :'' It is hard to give detailed information about the content of this phase. But basically it will be implementing the roadmap steps one by one.

=== Proposal contents ===
Here are some questions and ideas to help you dive into the topic. They are meant to help you get a better idea of what this project is going to be about. They are also meant to show us, how much you made yourself familiar with wesnoth's code, as this is very important to us. We are mostly ambitious and passionate ourselves, and we seek for students that are alike. Other (wesnoth) projects provide the opportunity to present prototypes, which won't be working here. Therefore it is even more important, that you implement some patches to show us your coding skills.<br>
However, there is some preparation you can do by now already. You should also add your thoughts about this to the proposal you are giving us. If you get accepted, this will surve as a starting point for further fleshing out things.

Don't hesitate to seek for help, if you have difficulties with some of the questions. I (YogiHH) will be on IRC most of the time in the evening (GMT+1) hours. You can also reach me by mail (joerg.hinrichs@alice-dsl.de) if that is not sufficient. Also keep in mind, that this is not a typical test with "right and wrong". It is clear that being new you won't be able to make the "perfect proposal" right out of the box. We are more interested in how you approach this task, how you communicate and if you can focus on the relevant stuff without losing yourself into details. So know what you are talking about, be innovative and take initiative.

The following two links are meant to give you further information for that:<br>
[[SavegameCode|savegame code]] - Contains the pieces of codes that deal with savegames and where to find them<br>
[[Summer of Code:SavegameWMLMapping|WML - object mapping]] - A mapping table to show you which objects hold the information of the savegame WML content<br>

1.
<p>If you take a closer look at the code, you will find, that there are different architectures of design to implement persistence. One is a more layered approach, which separates the creation and population of objects from persistent information (a savegame file, represented by a config object) from the rest. Config_adapter.cpp is an example of that idea. The other passes the raw persistence information (=config object) to the object to be created and lets it do the work. An example for this is the game_state constructor that takes a config object as argument.</p>
Which are the pro's and con's of those approaches with regard to encapsulation and maintenance? What would you choose for wesnoth's savegame processing?

2.
If your task is to remove config_adapter.cpp, how would you do that? Where would you put the code instead? And what are your reasons for that?

3.
The <i>player_info</i> struct and the <i>team</i> class share some information (for example units that belong to a certain side). Do you think it is a feasible idea to mold those two into one? And what are your reasons?

4.
The same question is to be asked for the <i>game_state</i> class and the <i>gamestatus</i> class.

5.
The second link above contains a mapping table, that matches savegame WML tags to C++ objects. Identify candidates for redundancies. Warning: Keep in mind, that WML is a mighty beast! Just one example: Through WML events, a map can change throughout a scenario. Therefore it makes a lot of sense to put that map into the [snapshot] and [replay_start] tags respectively, although at first glance it looks like we could put it into some central place. After you identified candidates for redundant information, you might want to talk to one of the WML experts to make sure those information is really redundant.

6.
Based on the thoughts you layed out in 1-5, what would the new savegame structure you propose be like? A level of detail like it is outlined in the mapping table will suffice here. Please also make sure, that your proposal is consistent with the idea of multiplayer campaigns.

=== See also ===
[[SummerOfCodeIdeas|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.<br>
[[User:SkeletonCrew#Savegame_format|savegame contents]] - Some ideas about the current and future content of savegames.<br>
[[SavefileWML|Savegame WML]] - Information about the format used for storing savegame information.
[[Category:Summer of Code]]

Summer of Code:SavegameWMLMapping

2009-03-25T20:11:57Z

Yogi Bear: New page: <table border=1> <tr> <td bgcolor="#dcdcdc">config tag</td> <td bgcolor="#dcdcdc">attribute</td> <td bgcolor="#dcdcdc">C++ object</td> <td bgcolor="#dcdcdc">task</td> <td bgcolo...

<table border=1>
<tr>
<td bgcolor="#dcdcdc">config tag</td>
<td bgcolor="#dcdcdc">attribute</td>
<td bgcolor="#dcdcdc">C++ object</td>
<td bgcolor="#dcdcdc">task</td>
<td bgcolor="#dcdcdc">multiplayer</td>
<td bgcolor="#dcdcdc">campaign</td>
</tr>
<tr>
<td>root</td>
<td>label</td>
<td>game_state.label</td>
<td>name of the savefile</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>abbrev</td>
<td>game_state.abbrev</td>
<td>info, not used</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>version</td>
<td>game_state.version</td>
<td>wesnoth version</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>scenario</td>
<td>game_state.scenario</td>
<td>name of the scenario</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>completion</td>
<td>game_state.completion</td>
<td>control linger mode</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>campaign</td>
<td>game_state.campaign</td>
<td>objectives message
game_config ID</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>campaign_type</td>
<td>game_state.campaign_type</td>
<td>process control</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>difficulty</td>
<td>game_state.difficulty</td>
<td>process control (scenario WML)
cache loading</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>campaign_define</td>
<td>game_state.campaign_define</td>
<td>cache loading</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>random_seed</td>
<td>game_state.random_seed</td>
<td>initialize rng</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>random_calls</td>
<td>game_state.random_calls</td>
<td>initialize rng</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>next_underlying_unit_id</td>
<td>nunit.id_manager.instance().save_id</td>
<td>nunit support</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>root</td>
<td>end_text_duration</td>
<td>game_state.end_text_duration</td>
<td>control display of campaigns ending text</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>variables</td>
<td>various</td>
<td>game_state.variables</td>
<td>store game variables</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>player</td>
<td></td>
<td>game_state.players</td>
<td>store player information</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>player</td>
<td>save_id</td>
<td>game_state.players</td>
<td>map key</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>player</td>
<td>gold</td>
<td>player_info.gold</td>
<td></td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>player</td>
<td>gold_add</td>
<td>player_info.gold_add</td>
<td></td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>player</td>
<td>name</td>
<td>player_info.name</td>
<td></td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>player</td>
<td>can_recruit</td>
<td>player_info.can_recruit</td>
<td>units available for recruiting</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>player.unit</td>
<td></td>
<td>player_info.available_units</td>
<td>recall list</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>replay</td>
<td></td>
<td>game_state.replay_data</td>
<td>replay information</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td></td>
<td>game_state.snapshot</td>
<td>current gamestate information</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>abbrev</td>
<td>game_state.abbrev</td>
<td>info, not used</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>campaign</td>
<td>game_state.campaign</td>
<td>objectives message
game_config ID</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>campaign_define</td>
<td>game_state.campaign_define</td>
<td>cache loading</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>campaign_type</td>
<td>game_state.campaign_type</td>
<td>process control</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>completion</td>
<td>game_state.completion</td>
<td>control linger mode</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>current_tod</td>
<td>gamestatus.areas_</td>
<td>current time of day</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>difficulty</td>
<td>game_state.difficulty</td>
<td>process control (scenario WML)
cache loading</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>#textdomain</td>
<td>preprocessor</td>
<td>translation support</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>description</td>
<td>tooltips</td>
<td>minimap description</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>end_text_duration</td>
<td>game_state.end_text_duration</td>
<td>control display of campaigns ending text</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>experience_modifier</td>
<td>play_controller.xp_mod_
unit_type::experience_accelerator</td>
<td>experience modifier</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot</td>
<td>hash</td>
<td>config</td>
<td>mp game verification</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot</td>
<td>id</td>
<td>?</td>
<td>?</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>label</td>
<td>game_state.label</td>
<td>savefile name (without specification)</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>map_data</td>
<td>game_state.snapshot
game_state.starting_pos
cfg_summary
play_controller.map_</td>
<td>map information</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>mp***</td>
<td>play_controller.level_ (config)</td>
<td>mp game parameter</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot</td>
<td>name</td>
<td>?</td>
<td>scenario name</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>next_scenario</td>
<td>game_state.next_scenario</td>
<td>id of the next scenario of a campaign</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>next_underlying_unit_id</td>
<td>nunit.id_manager.instance().save_id</td>
<td>nunit support</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>objectives</td>
<td>team.info_.objectives</td>
<td>objective string</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot</td>
<td>observer</td>
<td>game_item.observers
level (config)</td>
<td>allow / disallow observers</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot</td>
<td>playing_team</td>
<td>play_controller.first_player_</td>
<td>first team to continue playing</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>random_seed</td>
<td>game_state.random_seed</td>
<td>initialize rng</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>random_calls</td>
<td>game_state.random_calls</td>
<td>initialize rng</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>random_start_time</td>
<td>level_ (config)</td>
<td>activate random start time for scenario</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot</td>
<td>scenario</td>
<td>game_state.scenario</td>
<td>name of the scenario</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>snapshot</td>
<td>game_state.snapshot
play_controller.snapshot_</td>
<td>snapshot yes / no</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>turn_at</td>
<td>gamestatus ?</td>
<td>current turn</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>turns</td>
<td>gamestatus ?</td>
<td>max number of turns</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>unit_wml_ids</td>
<td>manager (game_events)</td>
<td>used unit_type ID's</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>version</td>
<td>game_state.version</td>
<td>wesnoth version</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot</td>
<td>side</td>
<td>level_ (config)</td>
<td>player information</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>action_bonus_count</td>
<td>team.action_bonus_count_</td>
<td>timer support</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot.side</td>
<td>aggression</td>
<td>team.info_.aggresion_</td>
<td>AI behaviour</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>allow_player</td>
<td>team.info_.allow_player</td>
<td>multiplayer game setup</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>caution</td>
<td>team.info_.caution_</td>
<td>AI behaviour</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>colour</td>
<td>team.info_.colour</td>
<td>Team display</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>controller</td>
<td>team.info_.controller</td>
<td>type of controller for this side</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>countdown_time</td>
<td>team.countdown_time_</td>
<td>time remaining for the current / next turn</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>current_player</td>
<td>team.info_.current_player</td>
<td>name of the current player (name of leader?)</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>disallow_observers</td>
<td>team.info_.disallow_observers</td>
<td>prohibits observing this side</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>fog</td>
<td>team.fog_</td>
<td>turns fog on / off</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>global_recruitment_pattern</td>
<td>team.info_.global_recruitment_pattern</td>
<td>AI recruitment behaviour</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>gold</td>
<td>team.gold_</td>
<td>available gold</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>hidden</td>
<td>team.info_.hidden</td>
<td>display control (status table)</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>id</td>
<td>?</td>
<td>?</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot.side</td>
<td>income</td>
<td>team.info_.income</td>
<td>gold income</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot.side</td>
<td>leader_value</td>
<td>team.info_.leader_value</td>
<td>AI target parameter</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>name</td>
<td>team.info_.name</td>
<td>team name</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>snapshot.side</td>
<td>no_leader</td>
<td>team.info_.no_leader</td>
<td>side has (not) a leader</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>number_of_possible_recruits_to_force_recruit</td>
<td>team.info_.number_of_possible_recruits_to_force_recruit</td>
<td>AI recruitment behaviour</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>objectives</td>
<td>team.info_.objectives</td>
<td>team objectives</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>objectives_changed</td>
<td>team.info_.objectives_changed</td>
<td>objectives changed mid scenario</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>recruit</td>
<td>team.info_.can_recruit</td>
<td>unit types to recruit</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>recruitment_pattern</td>
<td>team.info_.recruitment_pattern</td>
<td>AI recruitment behaviour</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>save_id</td>
<td>team.info_.save_id</td>
<td>identification information</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>share_maps</td>
<td>team.info_.share_maps</td>
<td>display control</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>share_view</td>
<td>team.info_.share_view</td>
<td>display control</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>shroud</td>
<td>team.shroud_</td>
<td>turns shroud on /off</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>side</td>
<td>team vector index?</td>
<td>side number (identification)</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>start_gold</td>
<td>team.info_.start_gold</td>
<td>starting gold for this team / scenario</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>team_name</td>
<td>team.info_.team_name</td>
<td>team name</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>user_team_name</td>
<td>team.info_.user_team_name</td>
<td>translatable team name</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>village_gold</td>
<td>team.info_.income_per_village</td>
<td>village income</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>village_value</td>
<td>team.info_.village_value</td>
<td>AI rating parameter</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side</td>
<td>villages_per_scout</td>
<td>team.info_.villages_per_scout</td>
<td>AI recruitment behaviour</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side.unit</td>
<td></td>
<td>player_info.available_units</td>
<td>recall list</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side.ai</td>
<td></td>
<td>team.aiparams_</td>
<td>AI parameter</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.side.villages</td>
<td></td>
<td>team.villages_</td>
<td>villages owned by the team</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.time</td>
<td></td>
<td>gamestatus.times_</td>
<td>time cycle definition</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.music</td>
<td></td>
<td>sound.cpp::current_track_list</td>
<td>music playlist</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.variables</td>
<td></td>
<td>game_state.variables</td>
<td>variables</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.player</td>
<td></td>
<td>game_state.players</td>
<td>player information</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>snapshot.event</td>
<td></td>
<td>game_events, event_handler?</td>
<td>event handler definition</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>current_tod</td>
<td>gamestatus.areas_</td>
<td>current time of day</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>description</td>
<td>tooltips</td>
<td>minimap description</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>experience_modifier</td>
<td>play_controller.xp_mod_
unit_type::experience_accelerator</td>
<td>experience modifier</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>replay_start</td>
<td>hash</td>
<td>config</td>
<td>mp game verification</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>replay_start</td>
<td>id</td>
<td>?</td>
<td>?</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>map_data</td>
<td>game_state.snapshot
game_state.starting_pos
cfg_summary
play_controller.map_</td>
<td>map information</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>mp***</td>
<td>play_controller.level_ (config)</td>
<td>mp game parameter</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>replay_start</td>
<td>name</td>
<td>?</td>
<td>scenario name</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>next_scenario</td>
<td>game_state.next_scenario</td>
<td>id of the next scenario of a campaign</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>next_underlying_unit_id</td>
<td>nunit.id_manager.instance().save_id</td>
<td>nunit support</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>objectives</td>
<td>team.info_.objectives</td>
<td>objective string</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>replay_start</td>
<td>observer</td>
<td>game_item.observers
level (config)</td>
<td>allow / disallow observers</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>replay_start</td>
<td>random_seed</td>
<td>game_state.random_seed</td>
<td>initialize rng</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>random_start_time</td>
<td>level_ (config)</td>
<td>activate random start time for scenario</td>
<td>x</td>
<td></td>
</tr>
<tr>
<td>replay_start</td>
<td>scenario</td>
<td>game_state.scenario</td>
<td>name of the scenario</td>
<td></td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>turns</td>
<td>gamestatus ?</td>
<td>max number of turns</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start</td>
<td>version</td>
<td>game_state.version</td>
<td>wesnoth version</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start.time</td>
<td></td>
<td>gamestatus.times_</td>
<td>time cycle definition</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start.music</td>
<td></td>
<td>sound.cpp::current_track_list</td>
<td>music playlist</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start.event</td>
<td></td>
<td>game_events, event_handler?</td>
<td>event handler definition</td>
<td>x</td>
<td>x</td>
</tr>
<tr>
<td>replay_start.era</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>replay_start.story</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>replay_start.side</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>replay_start.player</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>statistics</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</table>