SummerOfCodeIdeas

Ideas for Google Summer of Code projects

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

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 link to formula AI page here

The wesnoth AI is used as an oponent in most campaigns, and as such is an important piece of code for the wesnoth project. Unfortunately it is also one of the most neglected piece of code and a place where a lot of research and work could be done

General description

The aim of this project is to develop a new AI that would replace the original C++ AI. The main criterias we would want for this new AI are

• Plugability : It should be trivial for any content maker to change the behavior of the AI in specific case. The exact cases are still to be defined but should typically include
  • hardwiring the first few turns of the AI
  • changing the recruitment pattern
  • completely controlling a given unit (sceneario unit)
  • taking control then giving back control of a given unit
• tunability : It should be easy for a scenario author to specify the general behaviour of the ennemy on a given scenario (agressivity, intrepidity...)
• specific behaviours : there are some typical behaviours that are not smart to win the scenario but are needed, such as guarding a given unit, a given position, wandering aimlessly, attacking randomly, always fleeing. The AI should implement such behaviours, and allow easy addition of new behaviours

Required knowledge and talent

• A minimal knowledge of C++ is required, a good knowledge of C++ is desired : The formula AI framework is a work in progress and chances are high that some changes in the wesnoth code base will be needed. The wesnoth developper community is used to handle people that are familiar with coding but not C++, however the Forumla AI framework uses advanced C++ features and a good knowledge of the language would avoid a major hurdle when plugging in new entries or functionalities for the AI
• Good social interaction with a large player community : A preliminary phase to coding any AI is to know the strategies and game pattern used by human players. This requires huge interaction with the player community. Our Gameplay Developpers are open and can give some good starting points, but a big game experience and good interaction with the player community will greatly help in the study of the design

Milestones and deliverables

It is hard to give milestones at this point, but here are some ideas of what could be done

• AI design description, and basic function library : This first deliverable aims to conclude the study and analysis part of the project : becoming familiar with the formula language, study of the Multiplayer strategies and of the need of scenario writers with regard to AI. We would like to have a description of the code structure of the AI, some basis of the play strategies it would use and how external scenario writers could configure it for the particular behaviour they need
• Main AI delivery : This milestone's aim is to deliver a working AI implementing the strategies described in the first phase. It would not have to systematically beat the standard C++ AI at this point, but should be able to play the game correctly (recruit, early deployment on villages, grouping units to attack, holding its ground, protecting weak/important units). Moreover most plug-in entries should be available and a test-case for these entries should be provided.
• Fine tunning and behaviour library : The third phase would validate the actual strategy of the AI. The AI should consistently beat the default C++ AI, and do fairly well against an average human player. At that stage a library of scenario behaviours should also be delivered. The AI does not need to be as efficiant with all scenario tweaking, but should act correctly with regard to the particular behaviour desired.

Extending the Multiplayer server

When the developement team met at FOSDEM, we had our multiplayer commuinty, though it is strong and healthy, had its growth restrained by the interface of the multiplayer lobby.

General Description

The general idea of this project would be

• To study the current lobby,
• To present some ideas of evolutions both in interface and functionalities of our multiplayer interface to allow it to scale to a much larger community
• To present some well constructed thought on our MP community and how that interface would develop it
• Of course to implement those changes :)

Some ideas that we had (but that are in no way mandatory)

• Having a simple way to register and authentificate nicknames, similar to what IRC offers. The point is not to have cryptographically safe logins, but to have something simple that gets the job done
• Having a simple room system? again inspired on IRC
• Having some way to find the type of games you are interested in.
  • game type
  • number of free slots/players
  • any other criterias you might find interesting

Other ideas we are not convinced are good, but that are certainly worth studying (especially how the communities based around these concepts are different from ours)

• ranking players
• guilds
• official tournaments
• titles for players
• metaservers

The scalablity of the project, both in term of number of players, and in term of the possibility for players and developpers to extend the concept will be a valued criteria

Administration/moderation problems and techniques should also be studied

interaction with the Add-On server/forum might be an interseting field to expand to

Required knowledge and talent

• A fair amount of experience on C++ is required. Wesnoth uses some advanced C++ features and is heavily based on BOOST and STL. We can train you in some of the libraries used, but learning all of them would be a big hurdle
• Various experience with multiplayer games, in order to have a good idea of what multiplayer lobbies of other game look like, and (more importantly) a good idea of the social behaviours of multiple MP communities, how teams are formed in games and things like that

Milestones and deliverables

• A first milestone would be a presentation summarizing the different studies, and the proposed interface. preliminary unformal stages would probably be desirable, to make sure the proposed idea is already a consensus within devs
  • Study of other MP game-matching interfaces and functionalities
  • Study of other MP communities
  • Study of other MP moderation practices
  • Study of the Wesnoth MP community, including needs, various opinons from different developers and players
• A second milestone would be the main code delivery. Code should be functional for it will be delivered in the next Wesnoth developement release

Other ideas to be fleshed out

• Working on the GUI engine (needs to be defined more precisely)
• Extend the multiplayer server to provide accounts and room
• Rewrite of the campaign (add-on) server
• The editor can use quite a revamp
• A good scenario editor. We have campgen but it hasn't been updated for a while.