Difference between revisions of "SoC Ideas Unify SP and MP 2014"
(Created page with "{{SoC2014Idea}} =Description= <h2>Game Engine: Unify SP and MP</h2> Page for the idea: SoC_Ideas_Unify_SP_and_MP_2014 Wesnoth has lots of user made content, but some of ...") |
m (MediaWiki discourages using = for first-level headers) |
||
| Line 1: | Line 1: | ||
{{SoC2014Idea}} | {{SoC2014Idea}} | ||
| − | =Description= | + | ==Description== |
| − | + | ===Game Engine: Unify SP and MP=== | |
Page for the idea: [[SoC_Ideas_Unify_SP_and_MP_2014]] | Page for the idea: [[SoC_Ideas_Unify_SP_and_MP_2014]] | ||
| Line 20: | Line 20: | ||
}} | }} | ||
| − | =Additional Information= | + | ==Additional Information== |
Last year's [[SoC2013_thunderstruck_MP_Campaign_Support|GSoC project]] made it possible to use the same configuration files for both singleplayer and multiplayer campaigns. However, there's still some WML content which is not available for both singleplayer and multiplayer due to being handled by different code paths. | Last year's [[SoC2013_thunderstruck_MP_Campaign_Support|GSoC project]] made it possible to use the same configuration files for both singleplayer and multiplayer campaigns. However, there's still some WML content which is not available for both singleplayer and multiplayer due to being handled by different code paths. | ||
| Line 26: | Line 26: | ||
The goal of this project is to unify singleplayer and multiplayer code paths which are responsible for handling configuration files. This would lead to being able to use multiplayer eras and modifications in singleplayer too. As a result of this, some GUI dialogs would have to be created in order for players to be able to use this new functionality. | The goal of this project is to unify singleplayer and multiplayer code paths which are responsible for handling configuration files. This would lead to being able to use multiplayer eras and modifications in singleplayer too. As a result of this, some GUI dialogs would have to be created in order for players to be able to use this new functionality. | ||
| − | =Whom to ask about this= | + | ==Whom to ask about this== |
thunderstruck on irc. | thunderstruck on irc. | ||
Revision as of 22:15, 14 February 2014
| This page is related to Summer of Code 2014 |
| See the list of Summer of Code 2014 Ideas |
| This is a Summer of Code 2014 Idea |
Contents
Description
Game Engine: Unify SP and MP
Page for the idea: SoC_Ideas_Unify_SP_and_MP_2014
Wesnoth has lots of user made content, but some of it works only for either singleplayer or multiplayer. To solve this, some of the engine's singleplayer and multiplayer code paths need to be unified and extended.
There are no submitted student proposals for this idea
Additional Information
Last year's GSoC project made it possible to use the same configuration files for both singleplayer and multiplayer campaigns. However, there's still some WML content which is not available for both singleplayer and multiplayer due to being handled by different code paths.
The goal of this project is to unify singleplayer and multiplayer code paths which are responsible for handling configuration files. This would lead to being able to use multiplayer eras and modifications in singleplayer too. As a result of this, some GUI dialogs would have to be created in order for players to be able to use this new functionality.
Whom to ask about this
thunderstruck on irc.