SoC Ideas Whiteboard Multiple CTK 2012 - Revision history

Crab: /* Description */

2012-04-05T12:06:05Z

‎Description

2012-03-30T14:50:00Z

‎Description

2012-03-30T14:48:09Z

‎Chance-to-kill calculations for multiple planned attacks

2012-03-30T14:45:24Z

‎Requirements

2012-03-20T20:49:54Z

Correction of category

2012-03-20T02:15:39Z

‎Whom to ask about this

2012-03-20T01:32:26Z

2012-03-20T01:31:48Z

2012-03-20T01:30:04Z

‎Description

2012-03-20T01:09:49Z

@@ Line 1: / Line 1: @@
 {{Template:SoC2012Idea}}
 = Description =
-<h2>Whiteboard: Multiple Chance-to-kill calculations and interface polish</h2>
+<h2>Whiteboard: Multiple Chance-to-kill calculations and interface polish [3]</h2>
 Page for the idea: [[SoC Ideas Whiteboard Multiple CTK 2012]]

@@ Line 5: / Line 5: @@
 Page for the idea: [[SoC Ideas Whiteboard Multiple CTK 2012]]
-The whiteboard (the wesnoth action-planning system) allows you to plan several attacks on a single unit. Wesnoth already computes your chances to kill an attacked unit in a 1v1 fight in the battle dialog: extend this dialog to compute total kill chances taking into account all successive planned attackers.
+The whiteboard (the wesnoth action-planning system) allows you to plan several attacks on a single unit. Wesnoth already shows the player his chances to kill an attacked unit in a 1v1 fight in the battle dialog: reusing the existing code already used by the AI for this purpose, extend the dialog to present to the player total kill chances taking into account all successive planned attackers.
 In addition, the whiteboard interface still has some outstanding bugs or incomplete features and usability issues. Identify as many of those problems as possible and propose ways to solve them (see details for some ideas).

@@ Line 28: / Line 28: @@
 ==Chance-to-kill calculations for multiple planned attacks==
-The main challenge here besides computing the odds will be to design a good interface to accomodate this new info. You should at the very least submit UI mockups. Be aware that your UI should still work at the lowest resolution Wesnoth supports.
+The main challenge here will be to design a good interface to accomodate this new info. You should at the very least submit UI mockups. Be aware that your UI should still work at the lowest resolution Wesnoth supports.
 Optional addition: When several attacks are planned it can be hard to remember which unit is using which weapon. Try and find a way to display this information. Again, UI mockups are necessary so we can evaluate your idea.

@@ Line 62: / Line 62: @@
 Prior Wesnoth playing experience is required, since you're gonna do interface design, and a multiplayer match versus the whiteboard developer will be part of the acceptance process (don't worry, he sucks at competitive Wesnoth, and you're only expected to show that you have some clue on how to play the game).
-Good C++ skills are recommended, as is at least basic experience in interface design. You should also have a basic grasp of statistics, for the CTK calculations.
+Good C++ skills are recommended, as is at least basic experience in interface design.
 Note that all feature development (i.e. multiple CTK and Suppose Dead) must be finished by the GSoC midterm evaluation, after which all the time will be reserved for playtesting and further polishing.

@@ Line 16: / Line 16: @@
   |suppresserrors=true
   |noresultsheader=''There are no student proposals for this idea''
-  |category=Summer of Code 2012 Student Page&SoC Ideas AI Defense Strategies 2012
+  |category=Summer of Code 2012 Student Page&SoC Ideas Whiteboard Multiple CTK 2012
   |notcategory=SoC 2012 Not Submitted To Google
   |include=#Description

@@ Line 67: / Line 67: @@
 =Whom to ask about this=
 gabba on irc. If I'm hard to reach you can also find my email in the game's source files (if you're gonna make the effort to find it, I can make the effort to read your mail ;) ).
 Crab_ on irc can point you to the existing code for chance-to-kill calculations.

@@ Line 60: / Line 60: @@
 =Requirements=
-Prior Wesnoth playing experience is required, since you're gonna do interface design, and a multiplayer match versus the whiteboard developer will be part of the acceptance process (don't worry, he sucks at Wesnoth, and you're only expected to show that you have some clue on how to play the game).
+Prior Wesnoth playing experience is required, since you're gonna do interface design, and a multiplayer match versus the whiteboard developer will be part of the acceptance process (don't worry, he sucks at competitive Wesnoth, and you're only expected to show that you have some clue on how to play the game).
 Good C++ skills are recommended, as is at least basic experience in interface design. You should also have a basic grasp of statistics, for the CTK calculations.

@@ Line 56: / Line 56: @@
 For proper playtesting you'll need to create several very simple scenarios that allow to quickly test all the possible planned actions, i.e. recruit, recall, move (including over several turns), attack, and eventually the "suppose dead" action if we re-enable it.
-You should at first do exhaustive tests by yourself up to simulating 2v2 matches with 4 local clients, and when you're confident the game is bug-free, organise matches with devs and community members to see how people react, and to find the last, least obvious bugs.
+You should at first do exhaustive tests by yourself up to simulating 2v2 matches with 4 local clients, and when you're confident the game is bug-free, organise matches with devs and community members to put the whiteboard's usability to the test, and to find the last, least obvious bugs.
 =Requirements=