The Battle for Wesnoth Wiki - User contributions [en]

RujasuScenarioEditor

2008-04-04T15:49:46Z

Rujasu:

==Basics==
My name is Jacob Rudolph. I'm twenty years old and currently reside in Pennsylvania. I'm hoping for a career in software development, though I have not decided my exact ambitions yet. My hobbies include acting, and, well, open source game development.

Email: rujasu@yahoo.com

My nick is "rujasu" on IRC and forums. Generally, if you see "rujasu," it's probably me.

I am hoping that Summer of Code will give me enough income to dedicate more of my time to working on one of my favorite open source games, and less time working at a job that may not relate to my ultimate career path.

I'm a junior (third-year) undergraduate student at York College of Pennsylvania, majoring in Computer Science. I've taken nearly every programming-related course possible.

==Experience==
I have been a developer for Hero of Allacrost (www.allacrost.org) for about a year now, and was recently named lead of the programming team. Hero of Allacrost is an open source project for a single player RPG with 2D graphics; it draws inspiration from games such as Final Fantasy and Chrono Trigger. This would be my first Summer of Code experience.

I believe in using a general agile development model. It is clear that the waterfall model does not work in open source development. Documentation is important, but more important is producing readable and flexible code. Creating full prototypes is unnecessary for this project, but it will be helpful to create some interface mockups. For this project, the best method of testing is having people try using the software; I don't feel that automated testing will be useful for this project.

For the Allacrost project, I have worked on bugfixing and extending the functionality of the game's shopping and game menu interfaces. I have also contributed ideas, tested for bugs, and worked with scripting in Lua. More recently, I have been mentoring new contributing programmers for the project and working on battle mode.

I consider myself a pretty serious strategy/RPG gamer, though I haven't been playing as many games as I'd like lately. I play single-player games almost exclusively. I like games that challenge me; great gameplay is always the important factor, but a fantasy game needs a great story to be a true classic. I first learned of Wesnoth from a friend, a little over a year ago. I play single-player campaigns and have not tried multiplayer.

==Communication skills==
I am a native English speaker. I am an effective communicator and have taken academic writing classes through college. I do my best to help anyone who has questions or problems. I am very patient, and I should be able to interact with players easily. Whenever possible, I give constructive advice. I do not give negative or demeaning feedback. I am always willing to listen to advice and constructive criticisms. I am able to recognize when a criticism is accurate and useful.

==Project==
I chose the scenario editor project from the list. I chose this project because I would like to create an editor that is more usable and flexible than the out-of-date campgen, and one that will ultimately be more powerful. The editor will be written in C++. This is my most proficient language, and it allows better integration with other aspects of Wesnoth.

The editor will be using Wesnoth's own GUI toolkit (currently in development), with any necessary extensions being added as needed. I plan to use this toolkit because it would allow the editor to be distributed with Wesnoth, without any added dependencies. Since it is supposed to be easy-to-use, we don't want the user to have to install additional libraries. It would also keep the general feel of the game. Map viewing code from the map editor and/or main game could be re-used.

The interface will allow:

- Modification of basic scenario infomation
- Modification of sides/unit types
- Adding/removing/editing WML events by clicking on specific units, locations, or list of turns
- Saving to WML, loading from WML

On the back end, the editor will work using a simple process:

- Load and parse the scenario's CFG file.
- Modify the components of the WML as directed by the user/interface.
- Output the WML components to a CFG file.

This will also allow significant re-use and coordination with the main game's code. Much of the WML parser will be re-used, or at least used as a guide. Other things to worry about on the WML side:

Events will have to be dealt with. The system will have to be able to create events, remove events, and modify existing events. Removing events will be simple enough; just delete the event code. My plan to deal with creating events is to use small templates for common types of events. For modifying events, the editor can essentially list everything that happens as a part of that event, allowing the user to add to the event, remove from the event, or change parts of the event. To change the condition for an event, the user will probably have to create new events in most cases.

Preferably, comments written in WML would be preserved, though exact formatting will not be. This is a feature that may be difficult to implement during a summer project. However, comments could be preserved by keeping a record of all comments loaded from a data file and the information directly below them.

Macros would be very possible to deal with, however it would require a fundamental change to the editor's internal representation, so it would probably not be a feasible goal for this project to preserve macros.

==Practical considerations==
I am very familiar with SVN, mainly from my work on Allacrost. Also, I have been using C++ for about six years. Though I have no experience with Python, I am confident in my ability to learn programming languages quickly when needed.

As a Linux user, my work is mostly done on KDE development tools such as KWrite and KDevelop. I believe these are the most easily usable and visually appealing tools available for Linux. I am fluent in C++, Java, and C, with a working knowledge in Lua and a few others. Unfortunately, I am also fluent in BASIC, though I haven't touched it in years.

My only fluent language is English. My knowledge of Spanish is passable at best. Generally, I am awake from 14:00 to 6:00 UTC. I am able to talk over the phone; haven't really done anything with VOIP before.

==Tenative Timeline==

Now - May 25:

Learn more about Wesnoth: read documentation, talk to developers, etc.
Play through as many currently-available campaigns as possible.
Refine ideas.
Talk to scenario developers and get an idea of most requested features, etc.

May 26 - June 8:

Begin coding
Implement loading from WML, using (derivative of) current Wesnoth parser
Begin implementing the interface

June 9 - June 22:

Implement saving to WML
Implement basic modification support: static scenario information

June 23 - July 6:

Implement support for creating events
Implement support for modifying events
Implement support for creating new scenarios (default CFG files)

July 7 - July 20:

Clean up loose ends
Continue to work on implementing more events
Implement "export to WML" and test basic scenario

July 21 - August 3:

Put out version to community for testing/feedback
Implement an interface that will allow the user to tie scenarios together into a full campaign
Continue to work on implementing more events
Begin implementing additional features, such as:
- preserving comments
- events that affect AI?

August 4 - August 18:

Respond to feedback/bug reports
Finish anything not already completed
Work on additional features/events

[[Category:Summer of Code]]

RujasuScenarioEditor

2008-03-30T18:26:14Z

Rujasu: /* Tenative Timeline */

==Basics==
My name is Jacob Rudolph. I'm twenty years old and currently reside in Pennsylvania. I'm hoping for a career in software development, though I have not decided my exact ambitions yet. My hobbies include acting, and, well, open source game development.

Email: rujasu@yahoo.com

My nick is "rujasu" on IRC and forums. Generally, if you see "rujasu," it's probably me.

I am hoping that Summer of Code will give me enough income to dedicate more of my time to working on one of my favorite open source games, and less time working at a job that may not relate to my ultimate career path.

I'm a junior (third-year) undergraduate student at York College of Pennsylvania, majoring in Computer Science. I've taken nearly every programming-related course possible.

==Experience==
I have been a developer for Hero of Allacrost (www.allacrost.org) for about a year now, and was recently named lead of the programming team. Hero of Allacrost is an open source project for a single player RPG with 2D graphics; it draws inspiration from games such as Final Fantasy and Chrono Trigger. This would be my first Summer of Code experience.

I believe in using a general agile development model. It is clear that the waterfall model does not work in open source development. Documentation is important, but more important is producing readable and flexible code. Creating full prototypes is unnecessary for this project, but it will be helpful to create some interface mockups. For this project, the best method of testing is having people try using the software; I don't feel that automated testing will be useful for this project.

For the Allacrost project, I have worked on bugfixing and extending the functionality of the game's shopping and game menu interfaces. I have also contributed ideas, tested for bugs, and worked with scripting in Lua. More recently, I have been mentoring new contributing programmers for the project and working on battle mode.

I consider myself a pretty serious strategy/RPG gamer, though I haven't been playing as many games as I'd like lately. I play single-player games almost exclusively. I like games that challenge me; great gameplay is always the important factor, but a fantasy game needs a great story to be a true classic. I first learned of Wesnoth from a friend, a little over a year ago. I play single-player campaigns and have not tried multiplayer.

==Communication skills==
I am a native English speaker. I am an effective communicator and have taken academic writing classes through college. I do my best to help anyone who has questions or problems. I am very patient, and I should be able to interact with players easily. Whenever possible, I give constructive advice. I do not give negative or demeaning feedback. I am always willing to listen to advice and constructive criticisms. I am able to recognize when a criticism is accurate and useful.

==Project==
I chose the scenario editor project from the list. I chose this project because I would like to create an editor that is more usable and flexible than the out-of-date campgen, and one that will ultimately be more powerful.

During the summer, I expect to build an editor that can produce playable scenarios to be used in full campaigns. The editor will be flexible enough to, at some point, include additional features such as importing scenarios from WML. Additional tools can be developed for unit modification and any other possible campaign considerations; this will not be in the scope of my summer project.

The editor will be written in C++. This is my most proficient language, and it allows better integration with other aspects of Wesnoth. (For one thing, map-viewing code could potentially be re-used.) The editor will use Wesnoth's own GUI toolkit, which Mordante is currently developing. This will help to give the editor a united feel with the game itself.

I believe this project will help me to improve my practical software development abilities while doing something I enjoy. I fully intend to continue improving the editor, and possibly contributing to other areas of Wesnoth, once the SoC period is complete.

==Practical considerations==
I am very familiar with SVN, mainly from my work on Allacrost. Also, I have been using C++ for about six years. Though I have no experience with Python, I am confident in my ability to learn programming languages quickly when needed.

As a Linux user, my work is mostly done on KDE development tools such as KWrite and KDevelop. I believe these are the most easily usable and visually appealing tools available for Linux. I am fluent in C++, Java, and C, with a working knowledge in Lua and a few others. Unfortunately, I am also fluent in BASIC, though I haven't touched it in years.

My only fluent language is English. My knowledge of Spanish is passable at best. Generally, I am awake from 14:00 to 6:00 UTC. I am able to talk over the phone; haven't really done anything with VOIP before.

==Tenative Timeline==

Now - May 25:

Learn more about Wesnoth: read documentation, talk to developers, etc.
Play through as many currently-available campaigns as possible.
Refine ideas.
Talk to scenario developers and get an idea of most requested features, etc.

May 26 - June 8:

Begin coding.
Begin implementing the interface.
Implement support for global campaign data (name, difficulties, description, etc.)
Implement support for editing general scenario information (name, description, map data, etc.)
Implement editing of sides (available units).

June 9 - June 22:

Implement creation of events for basic victory conditions.
Implement pre-scenario events.
Implement placement of default units on map.

June 23 - July 6:

Implement in-game events.
- One view for events specific to units (if unit attacks, if unit is attacked, if unit moves to a location).
- One view for events specific to time (turns finished, specific event happens on turn 2).
- Map view for events specific to location (any unit from a specific side reaches a certain point.

July 7 - July 20:

Clean up loose ends.
Implement "export to WML" and test basic scenario.

July 21 - August 3:

Put out version to community for testing/feedback.
Possibly implement "import from WML."
Work on additional features?

August 4 - August 18:

Respond to feedback/bug reports.
Finish anything not already completed.
Work on additional features?

[[Category:Summer of Code]]

RujasuScenarioEditor

2008-03-30T17:10:27Z

Rujasu: Added timeline

==Basics==
My name is Jacob Rudolph. I'm twenty years old and currently reside in Pennsylvania. I'm hoping for a career in software development, though I have not decided my exact ambitions yet. My hobbies include acting, and, well, open source game development.

Email: rujasu@yahoo.com

My nick is "rujasu" on IRC and forums. Generally, if you see "rujasu," it's probably me.

I am hoping that Summer of Code will give me enough income to dedicate more of my time to working on one of my favorite open source games, and less time working at a job that may not relate to my ultimate career path.

I'm a junior (third-year) undergraduate student at York College of Pennsylvania, majoring in Computer Science. I've taken nearly every programming-related course possible.

==Experience==
I have been a developer for Hero of Allacrost (www.allacrost.org) for about a year now, and was recently named lead of the programming team. Hero of Allacrost is an open source project for a single player RPG with 2D graphics; it draws inspiration from games such as Final Fantasy and Chrono Trigger. This would be my first Summer of Code experience.

I believe in using a general agile development model. It is clear that the waterfall model does not work in open source development. Documentation is important, but more important is producing readable and flexible code. Creating full prototypes is unnecessary for this project, but it will be helpful to create some interface mockups. For this project, the best method of testing is having people try using the software; I don't feel that automated testing will be useful for this project.

For the Allacrost project, I have worked on bugfixing and extending the functionality of the game's shopping and game menu interfaces. I have also contributed ideas, tested for bugs, and worked with scripting in Lua. More recently, I have been mentoring new contributing programmers for the project and working on battle mode.

I consider myself a pretty serious strategy/RPG gamer, though I haven't been playing as many games as I'd like lately. I play single-player games almost exclusively. I like games that challenge me; great gameplay is always the important factor, but a fantasy game needs a great story to be a true classic. I first learned of Wesnoth from a friend, a little over a year ago. I play single-player campaigns and have not tried multiplayer.

==Communication skills==
I am a native English speaker. I am an effective communicator and have taken academic writing classes through college. I do my best to help anyone who has questions or problems. I am very patient, and I should be able to interact with players easily. Whenever possible, I give constructive advice. I do not give negative or demeaning feedback. I am always willing to listen to advice and constructive criticisms. I am able to recognize when a criticism is accurate and useful.

==Project==
I chose the scenario editor project from the list. I chose this project because I would like to create an editor that is more usable and flexible than the out-of-date campgen, and one that will ultimately be more powerful.

During the summer, I expect to build an editor that can produce playable scenarios to be used in full campaigns. The editor will be flexible enough to, at some point, include additional features such as importing scenarios from WML. Additional tools can be developed for unit modification and any other possible campaign considerations; this will not be in the scope of my summer project.

The editor will be written in C++. This is my most proficient language, and it allows better integration with other aspects of Wesnoth. (For one thing, map-viewing code could potentially be re-used.) The editor will use Wesnoth's own GUI toolkit, which Mordante is currently developing. This will help to give the editor a united feel with the game itself.

I believe this project will help me to improve my practical software development abilities while doing something I enjoy. I fully intend to continue improving the editor, and possibly contributing to other areas of Wesnoth, once the SoC period is complete.

==Practical considerations==
I am very familiar with SVN, mainly from my work on Allacrost. Also, I have been using C++ for about six years. Though I have no experience with Python, I am confident in my ability to learn programming languages quickly when needed.

As a Linux user, my work is mostly done on KDE development tools such as KWrite and KDevelop. I believe these are the most easily usable and visually appealing tools available for Linux. I am fluent in C++, Java, and C, with a working knowledge in Lua and a few others. Unfortunately, I am also fluent in BASIC, though I haven't touched it in years.

My only fluent language is English. My knowledge of Spanish is passable at best. Generally, I am awake from 14:00 to 6:00 UTC. I am able to talk over the phone; haven't really done anything with VOIP before.

==Tenative Timeline==

May 26 - June 8:

Begin coding.
Begin implementing the interface.
Implement support for global campaign data (name, difficulties, description, etc.)
Implement support for editing general scenario information (name, description, map data, etc.)
Implement editing of sides (available units).

June 9 - June 22:

Implement creation of events for basic victory conditions.
Implement pre-scenario events.
Implement placement of default units on map.

June 23 - July 6:

Implement in-game events.
- One view for events specific to units (if unit attacks, if unit is attacked, if unit moves to a location).
- One view for events specific to time (turns finished, specific event happens on turn 2).
- Map view for events specific to location (any unit from a specific side reaches a certain point.

July 7 - July 20:

Clean up loose ends.
Implement "export to WML" and test basic scenario.

July 21 - August 3:

Put out version to community for testing/feedback.
Possibly implement "import from WML."
Work on additional features?

August 4 - August 18:

Respond to feedback/bug reports.
Finish anything not already completed.
Work on additional features?

[[Category:Summer of Code]]

EasyCoding

2008-03-30T16:38:27Z

Rujasu:

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

== WML related features ==
=== 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.
=== Introducing consistent invocation of SUF ===
Some tags using SUF do not use [filter] to describe it. This should be changed to achieve some consistency, but backwards compatibility should be preserved for now. Probably exhaustive list of tags to work on includes :
*[kill]
*[recall]
*[role]
*[scroll_to_unit]
=== 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]
=== Recall Event ===
WML event trigger for recalling (the current one triggers on both recalls and recruits) ([http://gna.org/bugs/index.php?3622 FR #3622]) (please read the comments of the report for a proper description of how this should work)
=== Enabling checking of damage dealt in WML ===
A WML variable should be set when triggering some combat-related events, allowing WML to know the amount of damage being dealt. ([http://gna.org/bugs/index.php?7673 FR #7673])
=== 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])
=== 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.

== 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 ===
* show number of owned villages/total villages (FR: #3135) (--[[User:Alink|alink]] done but must update help, doc, tooltip...)
* 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

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

ACardboardRobot 2/2/07

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

=== Additional Commandline Options ===
'''Done''' by lao, actually in trunk, revision 25325.

It would be nice if one could start Wesnoth from commandline specifying whether one wants to connect to a mp-server, load the last savegame or wants to start a campaign. More detailed information and examples are given in the [http://www.wesnoth.org/forum/viewtopic.php?f=12&t=20243 idea forum].

=== Add minimal regexp to friend list ===

Lots of people use multiple nicks, usually postfixed with a number... it would be nice to have minimal regexp support in friend list to easily get who's there...

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

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

SummerOfCodeIdeas

2008-03-22T07:14:01Z

Rujasu: Added link to my SoC page

This is a compilation of ideas from ML. Needs to be refined (more detailed description, deliverables, workload estimation?):

== I want to be one of your Google Summer of Code students, what should I do... ==

Here is a quick list of things to do to get you started
* Create an account on gna.org
* Create an account on the wesnoth forum
* Join the irc channel (#wesnoth-dev on irc.freenode.net) and introduce yourself. We will not give formal interviews, but we will clearly favor people we have learnt to know during the selection process
* Contact one of our SummerOfCode people (Ivanovic, Sirp, Boucman, Mordante) to have your forum nick marked as a Summer of code student

* Start a wiki page about your idea, add a link on the bottom of this page and add this information on it:
** List your account names (gna, forum, irc nick) so that we can recognize you
** Fill the questionnaire on this page: [[SoC_Information_for_Google#Does_your_organization_have_an_application_template_you_would_like_to_see_students_use.3F_If_so.2C_please_provide_it_now.| List of questions to answer]]
** Detail your idea as much as possible, look at other students pages, and please give milestones and studies you've done

* Though not mandatory, it is highly advisable to go to the [[EasyCoding]] and [[NotSoEasyCoding]] pages and implement one of these ideas (or any idea of similar scope) so we have an idea how you work. Be sure to use your gna account when submitting these patches so we know who it is coming from. You can also implement some features from our feature request database at gna. When you implement something, also list it on your own page with a reference to the patch.

== List of Ideas for the Project (Suggestions from the wesnoth developers) ==

Here is only a short description of possible Ideas we have, each has a page of its own with a more detailed version on it.

=== Writing an AI based on the formula AI ===

Wesnoth has always had a simple C++ based AI. David (our lead developer) has been working on a simple language to write AI in Wesnoth: [[FormulaAI]]

The Wesnoth AI is used as an opponent in most campaigns, and as such is an important piece of code for the Wesnoth project. Unfortunately, because the skills required to understand and modify it are rather arcane, it is also one of the most neglected parts of the Wesnoth code. This is a place where a lot of research and useful work could be done. But keep in mind that [[WhyWritingAWesnothAIIsHard|writing an AI for Wesnoth is difficult]].

[[SoC Ideas FormulaAI]] - Full version of the idea, with detailed information

=== Extending the Multiplayer server ===

Our multiplayer community is generally strong and healthy, but we believe its growth is limited by some problems in the interface of the multiplayer lobby.

[[SoC Ideas Multiplayer server]] - Full version of the idea, with detailed information

=== Scenario/Campaign editor ===

Currently, in order to create campaign or multiplayer scenarios, it is necessary to manually edit WML files - XML-like configuration files. The goal of this project would be to create a graphical editor to make the creative process easier.

[[SoC Ideas Scenario and Campaign Editor]] - Full version of the idea, with detailed information

=== Addon server ===
Wesnoth has an addon server which offers users to upload user
made content (UMC). This allows all other users of Wesnoth
to easily download and install this content. The server was
originally written for user-made campaigns but contains a lot
more types of addons nowadays. Both the server side and the
client side need to be improved.

[[SoC Ideas Addon Server]] - Full version of the idea, with detailed information

=== Map editor ===
The map editor in Wesnoth serves two goals, making it easy to create
a new map and helping the terrain artists to test their new terrains.

[[SoC_Ideas_Map_Editor]] - Full version of the idea, with detailed information

=== Other possible ideas to be fleshed out ===
A MapGenerator rewrite - better scalable for outdoor maps, plus the possibility to define areas (similar to the caverns in the cave generator) etc.

=== Make your own ideas ===
If you have your own idea the best thing is to join IRC wesnoth-dev at irc.freenode.net and discuss the idea with the developers there. If the developers think your idea is interesting and like the feature you can start to turn it into a full proposal. Once done discuss it again on IRC so the developers can accept your idea.

== Information about our Project ==
The information we provided google with about our project can be looked up at the site [[SoC Information for Google]].

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

[[SoC People to bug on IRC]]

== GSoC Student Applicant Ideas ==

Every student interested to work on Wesnoth as part of Summer of Code should create a page of his own where several things should be listed. Here is a short list of what should be mentioned on the list (the more info for us, the better...):

* Who are you? Please list your IRC and forum nickname in here and describe yourself so that we get you to know.
* What do you want to work on? Please flesh out your personal ideas, so that we get to know what you plan to work on.
* If you already submitted patches, please list those so that we have a reference.

=== [[FormulaAIandDynamicScripting]] (barbarianhero) ===
This project idea uses Formula AI and Dynamic Scripting to create a tunable and adaptive AI.

===[[FormulaAIandAdaptation]] (Alesis-Novik) ===
The new idea and aproach using strategic and inside game knowledge

===[[FormulaAIBaseAI]] (Dragonking) ===
Developing smart and pluggable AI, which would be really easy tweakable by Scenario and Campaign Developers

===[[ExtensibleScenarioEditor]] (david.hilton) ===
On a conceptual level, this idea combines a finite state machine editor with a code generator to create scenarios.

===[[pyQTScenarioEditor]] (Malle) ===
That's me!

===[[EvolutionaryMapEditor]] (xonev) ===
Under Construction

===[[RandomCampaignGenerator]] (kartik thakore, refining idea) ===
Procedural map generation that will hope to give writers better control over the random map generator using an interface.

===[[LaoSoCIdeas]] by lao ===
Under Construction...

===[[AddonServer]] (giebfried) ===
This project is to improve the server and client sides of the addon server, as suggested above.

===[[RujasuScenarioEditor]] (rujasu) ===
Scenario editor that will coordinate with the look and feel of the Wesnoth game.

[[Category:Summer of Code|*]]

RujasuScenarioEditor

2008-03-22T07:03:54Z

Rujasu:

RujasuScenarioEditor

2008-03-22T07:02:34Z

Rujasu: New page: ==Basics== My name is Jacob Rudolph. I'm twenty years old and currently reside in Pennsylvania. I'm hoping for a career in software development, though I have not decided my exact ambit...

EasyCoding

2008-03-21T03:24:34Z

Rujasu: Updated Debug Mode todo list.

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

== WML related features ==

=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960])
=== Recall Event ===
WML event trigger for recalling (the current one triggers on both recalls and recruits) ([http://gna.org/bugs/index.php?3622 FR #3622]) (please read the comments of the report for a proper description of how this should work)
=== Enabling checking of damage dealt in WML ===
A WML variable should be set when triggering some combat-related events, allowing WML to know the amount of damage being dealt. ([http://gna.org/bugs/index.php?7673 FR #7673])
=== 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])
=== 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.

== 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 ===
* show number of owned villages/total villages (FR: #3135) (--[[User:Alink|alink]] done but must update help, doc, tooltip...)
* 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, ..), seek Sapient for more info and tips

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

ACardboardRobot 2/2/07

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

=== Additional Commandline Options ===

It would be nice if one could start Wesnoth from commandline specifying whether one wants to connect to a mp-server, load the last savegame or wants to start a campaign. More detailed information and examples are given in the [http://www.wesnoth.org/forum/viewtopic.php?f=12&t=20243 idea forum].

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

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