SoC2013 thunderstruck MP Campaign Support - Revision history

Thunderstruck at 16:16, 4 July 2013

2013-07-04T16:16:12Z

Thunderstruck: options window

2013-05-22T12:48:16Z

options window

Thunderstruck: update future aspects

2013-05-22T10:23:29Z

update future aspects

Thunderstruck: Create window and demo update.

2013-05-21T14:11:01Z

Create window and demo update.

Thunderstruck: demo update

2013-05-20T13:31:43Z

demo update

Thunderstruck: New syntax support, formatting and other changes.

2013-05-19T18:33:24Z

New syntax support, formatting and other changes.

Show changes

Thunderstruck at 17:59, 10 May 2013

2013-05-10T17:59:35Z

Thunderstruck: Goals, engine and wml syntax changes

2013-05-10T16:05:39Z

Goals, engine and wml syntax changes

Show changes

Thunderstruck: formatting

2013-05-04T20:37:52Z

formatting

Thunderstruck: timeline and game engine adjustments

2013-05-04T20:21:09Z

timeline and game engine adjustments

Show changes

@@ Line 218: / Line 218: @@
 ==Goals==
+''N.B. The progress is not currently marked here, because the expected goals, which are here, do not necessarily match the current goals I'm working on.''
 {| border="1"
 ! ID

@@ Line 42: / Line 42: @@
       # Optional. The value of 'min_players' or 1 will be used as a default value.
       max_players=3
       # details omitted..
@@ Line 158: / Line 162: @@
 ;Connect window
 :The current connect window would need to be modified so that it would be possible to disable/enable options for a non-host player. In this way, the window could be used not for only host player. After those modifications, wait window would no longer be necessary.
 ----
@@ Line 266: / Line 278: @@
 |<p style="color:red">MANDATORY</p>
 |Implement a new dialog or tweak the existing one for chapter/scenario selection for multiplayer campaigns.
+|
 |-
@@ Line 274: / Line 292: @@
 |n/a
 |-
-|10
+|11
 |Save and restore 1
 |<p style="color:red">MANDATORY</p>
@@ Line 280: / Line 298: @@
+|
 |-
-|11
+|12
 |Save and restore 2
 |<p style="color:blue">OPTIONAL</p>
@@ Line 293: / Line 311: @@
 |n/a
 |-
-|12
+|13
 |Multiplayer screens 1
 |<p style="color:red">MANDATORY</p>
@@ Line 299: / Line 317: @@
+|
 |-
-|13
+|14
 |Multiplayer screens 2
 |<p style="color:blue">OPTIONAL</p>
@@ Line 305: / Line 323: @@
+|
 |-
-|14
+|15
 |Multiplayer screens 3
 |<p style="color:blue">OPTIONAL</p>
@@ Line 311: / Line 329: @@
+|
 |-
-|15
+|16
 |Multiplayer screens 4
 |<p style="color:blue">OPTIONAL</p>

@@ Line 154: / Line 154: @@
 :The current window which lets user to create a new multiplayer game mix the all multiplayer campaigns and scenarios into one list. What is more, it won't display campaign's name in that list, but the first scenario of the campaign instead (or more scenarios in some cases).
-:To make it convenient for the users to easily differentiate between campaigns and scenarios a new button would be implemented which would change "maps menu" from scenarios to campaigns and vice-versa. The difficulties and chapter/scenario selection dialogs would be displayed after campaign is selected and launched. These changes would have a little effect on the visual UI part and would not interfere with lipkab's [http://forums.wesnoth.org/viewtopic.php?f=12&t=38748 plans].
+:To make it convenient for the users to easily differentiate between campaigns and scenarios a new button would be implemented which would change "maps menu" from maps/scenarios to campaigns and vice-versa. The difficulties and chapter/scenario selection dialogs would be displayed after campaign is selected and launched. These changes would have a little effect on the visual UI part and would not interfere with lipkab's [http://forums.wesnoth.org/viewtopic.php?f=12&t=38748 plans].
 ;Connect window
@@ Line 329: / Line 329: @@
 * Allow 2 or more players to play the same side by splitting units among them. Suggested [http://forums.wesnoth.org/viewtopic.php?f=15&t=38683#p551723 here].
 * Enable communal choices. Suggested in the same post as above.
-<!--* Improve multiplayer loading time. The problem was described [https://gna.org/bugs/?11503 here].-->
+* Make it possible to change difficulty level between scenarios in multiplayer campaign.
 ==Questionnaire==

@@ Line 152: / Line 152: @@
 ----
 ;Create game window
-TODO: edit after GUI prototypes for new mp campaign create window are confirmed. Should not interfere with [http://forums.wesnoth.org/viewtopic.php?f=12&t=38748 lipkab's plans]
+:The current window which lets user to create a new multiplayer game mix the all multiplayer campaigns and scenarios into one list. What is more, it won't display campaign's name in that list, but the first scenario of the campaign instead (or more scenarios in some cases).
-:The current window which lets user to create a new multiplayer game mix the all multiplayer campaigns and scenarios into one list. What is more, it won't display campaign's name in that list, but the first scenario of the campaign instead (or more scenarios in some cases). It could be fixed by displaying campaign as a single list item. For the cases when there are multiple starting points (scenarios with 'entry_points' has more than one attribute), all the scenarios should be displayed in the additional dialog if campaign is chose to be played. In addition, there should be two separate lists for campaigns and scenarios and the "Load game" option should be moved from the maps list and be represented as a button. Furthermore, additional option for difficulties should be added along other game options as a drop-down box.
 ;Connect window
@@ Line 176: / Line 177: @@
 :* Do a further research on project's implementation and make notes on that.
 :* Exam period at the University.
-:* [https://github.com/thunders/wesnoth-old/commit/ab739ab550b8ce391a9988f062ec2076f52bfcee Demo] to play SP campaigns as MP with no extra WML tweaking (works only partially). [https://github.com/thunders/wesnoth-old/commit/6ca07a094796dafe4e1a4cd58f1f4b7b70680021 Update].
+:* [https://github.com/thunders/wesnoth-old/commit/ab739ab550b8ce391a9988f062ec2076f52bfcee Demo] to play SP campaigns as MP with no extra WML tweaking (works only partially). [https://github.com/thunders/wesnoth-old/commit/6ca07a094796dafe4e1a4cd58f1f4b7b70680021 Update]. [https://github.com/thunders/wesnoth-old/commit/ca32fb7a50b3212d0707c0cb3434f0c2440a4eeb Another update].
 ;May 27 - June 17 (community bonding period):
@@ Line 252: / Line 253: @@
 |Multiplayer WML upgrade 2
 |<p style="color:red">MANDATORY</p>
-|Use upgrader class to upgrade all relevant configs at a loading time.
+|Use upgrader class to upgrade all relevant configs at a loading time and implement checking mechanism to determine if upgraded add-on was updated.
+|
 |-
 |8
 |Create window 1
 |<p style="color:red">MANDATORY</p>
-|TODO: edit after GUI prototypes. Add a new list for games to play and move campaigns to it, leaving scenarios in the previous one.
+|Implement "Switch to" button to quickly switch between multiplayer maps/scenarios to campaigns and vice-versa.
+|
 |-
-|10
+|9
 |Create window 2
 |<p style="color:red">MANDATORY</p>
-|TODO: edit after GUI prototypes. Remove "Load game" option from the scenarios list and place it in the same window as a button. Add drop-down box or dialog for choosing difficulties. Connect GUI changes with relevant code.
+|Implement a new dialog or tweak the existing one for chapter/scenario selection for multiplayer campaigns.
+|
 |-
@@ Line 285: / Line 274: @@
 |n/a
 |-
-|12
+|10
 |Save and restore 1
 |<p style="color:red">MANDATORY</p>
@@ Line 291: / Line 280: @@
+|
 |-
-|13
+|11
 |Save and restore 2
 |<p style="color:blue">OPTIONAL</p>
@@ Line 304: / Line 293: @@
 |n/a
 |-
-|14
+|12
 |Multiplayer screens 1
 |<p style="color:red">MANDATORY</p>
@@ Line 310: / Line 299: @@
+|
 |-
-|15
+|13
 |Multiplayer screens 2
 |<p style="color:blue">OPTIONAL</p>
@@ Line 316: / Line 305: @@
+|
 |-
-|16
+|14
 |Multiplayer screens 3
 |<p style="color:blue">OPTIONAL</p>
@@ Line 322: / Line 311: @@
+|
 |-
-|17
+|15
 |Multiplayer screens 4
 |<p style="color:blue">OPTIONAL</p>

@@ Line 176: / Line 176: @@
 :* Do a further research on project's implementation and make notes on that.
 :* Exam period at the University.
-:* [https://github.com/thunders/wesnoth-old/commit/ab739ab550b8ce391a9988f062ec2076f52bfcee Demo] to play SP campaigns as MP with no extra WML tweaking (works only partially).
+:* [https://github.com/thunders/wesnoth-old/commit/ab739ab550b8ce391a9988f062ec2076f52bfcee Demo] to play SP campaigns as MP with no extra WML tweaking (works only partially). [https://github.com/thunders/wesnoth-old/commit/6ca07a094796dafe4e1a4cd58f1f4b7b70680021 Update].
 ;May 27 - June 17 (community bonding period):

@@ Line 96: / Line 96: @@
 ;Configs loading
-:The game configs for all multiplayer games are currently loaded when "Multiplayer" option is chosen from the main menu. The proposed solution would allow to avoid that, because multiplayer campaigns would have their own campaign define and would be loaded with appropriate difficulty only once game is created. The stand-alone multiplayer games would still be fully parsed with every other multiplayer, but that would not drastically affect loading times, since scenarios contain far less data than campaigns. However, since game loading speed is still an important aspect, some adjustments would might have to be made. When creating a game, instead of loading all WML again, we would have to load only a particular campaign we are interested. This would be done by keeping track of path to '_main.cfg' for every add-on and using that path to load everything under that directory. Additionally, if it would appear that big campaigns would cause time-outs while they are parsed, the thread responsible for answering ping requests from the server could be created in order to avoid that.
+:The game configs for all multiplayer games are currently loaded when "Multiplayer" option is chosen from the main menu. The proposed solution would allow to avoid that, because multiplayer campaigns would have their own campaign define and would be loaded with appropriate difficulty only once game is created. The stand-alone multiplayer games would still be fully parsed with every other multiplayer game, but that would not drastically affect loading times, since scenarios contain far less data than campaigns. However, since game loading speed is still an important aspect, some adjustments would might have to be made; When creating a game, instead of loading all WML again, we would have to load only a particular campaign we are interested. This would be done by keeping track of path to '_main.cfg' for every add-on and using that path to load everything under that directory. Additionally, if it would appear that big campaigns would cause time-outs while they are parsed, the thread responsible for answering ping requests from the server could be created in order to avoid that.
 ;Saving and restoring

@@ Line 123: / Line 123: @@
   lobby <------------> connect_player <-> (game)
 </pre>
-<dl/>
+</dl>
 ----