SoC Ideas Multiplayer Engine Refactoring 2012: Difference between revisions

From The Battle for Wesnoth Wiki
Crab (talk | contribs)
Crab (talk | contribs)
 
(4 intermediate revisions by the same user not shown)
Line 3: Line 3:


=Description=
=Description=
<h2>MULTIPLAYER: Improve wesnoth's engine to allow better transitions between scenarios</h2>
<h2>Improve wesnoth's engine to allow better transitions between scenarios [1]</h2>


More info at [[SoC_Ideas Multiplayer Engine Refactoring 2012]]
Page for the idea: [[SoC_Ideas Multiplayer Engine Refactoring 2012]]


We have a piece of code which links scenarios together. We need to improve the quality of that code (the code is rather messy at the moment) and we need to allow fun things to happen between scenarios, - like 'changing from singleplayer to multiplayer or back again, changes of difficulty level, changes to recall lists and player sides, etc). This code would interact with the new GUI2 dialogs which would allow the players to select 'what to do next' in a better way. An example of usage: after completing a campaign scenario, a 'big interactive map' might appear on a user screen and the player (or players) would select who plays next. This would replace the current 'assign players to sides' dialog, as well, allowing other parameters of 'next scenario' to be customizable.
We have a piece of code which links scenarios together. We need to improve the quality of that code (the code is rather messy at the moment) and we need to allow fun things to happen between scenarios, - like 'changing from singleplayer to multiplayer or back again, changes of difficulty level, changes to recall lists and player sides, etc). This code would interact with the new GUI2 dialogs which would allow the players to select 'what to do next' in a better way. An example of usage: after completing a campaign scenario, a 'big interactive map' might appear on a user screen and the player (or players) would select who plays next. This would replace the current 'assign players to sides' dialog, as well, allowing other parameters of 'next scenario' to be customizable.
Line 23: Line 23:


=Additional Information=
=Additional Information=
The main file related to scenario transitions is http://svn.gna.org/viewcvs/wesnoth/trunk/src/playcampaign.cpp?view=markup
During the project, there would be need to change:
# method of constructing scenario config.
# method of determining the next scenario.
# method of changing the config between scenario.
# method of changing the type of game between scenario.


=Whom to ask about this=
=Whom to ask about this=
Crab_ on irc
Crab_ on irc

Latest revision as of 12:05, 5 April 2012


This page is related to Summer of Code 2012
See the list of Summer of Code 2012 Ideas



This is a Summer of Code 2012 Idea


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

Description

Improve wesnoth's engine to allow better transitions between scenarios [1]

Page for the idea: SoC_Ideas Multiplayer Engine Refactoring 2012

We have a piece of code which links scenarios together. We need to improve the quality of that code (the code is rather messy at the moment) and we need to allow fun things to happen between scenarios, - like 'changing from singleplayer to multiplayer or back again, changes of difficulty level, changes to recall lists and player sides, etc). This code would interact with the new GUI2 dialogs which would allow the players to select 'what to do next' in a better way. An example of usage: after completing a campaign scenario, a 'big interactive map' might appear on a user screen and the player (or players) would select who plays next. This would replace the current 'assign players to sides' dialog, as well, allowing other parameters of 'next scenario' to be customizable.

There are no submitted student proposals for this idea

Additional Information

The main file related to scenario transitions is http://svn.gna.org/viewcvs/wesnoth/trunk/src/playcampaign.cpp?view=markup

During the project, there would be need to change:

  1. method of constructing scenario config.
  2. method of determining the next scenario.
  3. method of changing the config between scenario.
  4. method of changing the type of game between scenario.

Whom to ask about this

Crab_ on irc

This page was last edited on 5 April 2012, at 12:05.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.