https://wiki.wesnoth.org/api.php?action=feedcontributions&feedformat=atom&user=Dlr365 2026-06-02T15:34:53Z User contributions MediaWiki 1.31.16 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=27696 2008-12-23T05:53:39Z

<p>Dlr365: </p> <hr /> <div>== Info ==<br /> *Name - Doug Rosvick<br /> *Location - Calgary, Canada<br /> *Profession - Software Engineering student at University of Calgary<br /> <br /> == Works in Progress ==<br /> === Current ===<br /> * bug #12747 [https://gna.org/bugs/index.php?12747] - holding escape quits titlescreen<br /> <br /> === Previous ===<br /> ==== [endlevel] giving different results to different sides ====<br /> (info below is out of date)<br /> <br /> Allows specific sides to be issued specific results in multiplayer, instead of everyone getting the same result. See [http://gna.org/bugs/index.php?4960 bug#4960], [https://gna.org/patch/?1032 patch#1032].<br /> <br /> If [result] tags are found within an [endlevel] tag, the normal ''result='' key will be ignored. If ''summary=yes'' is specified in the [endlevel] tag, then instead of specific victory/defeat messages for only local players, each player is shown the victory/defeat status of all sides. Any sides who are not given a specific [result] are either shown a summary or nothing, and their result is defaulted to ''continue''. Observers are shown a &quot;game over&quot; dialog if ''summary=no'', and the summary if ''summary=yes''.<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> <br /> next_scenario=<br /> <br /> bonus= {these are the defaults for all [result] tags}<br /> carryover_percentage=<br /> carryover_add=<br /> <br /> summary= {controls whether players are shown a summary of all sides, or just their local victory/defeat messages}<br /> <br /> [result]<br /> side=1<br /> outcome=victory {may be victory, defeat, continue, continue_no_save}<br /> fire_events= {yes/no, controls whether victory/defeat events are fired}<br /> [/result]<br /> <br /> [result]<br /> side=4<br /> outcome=victory<br /> fire_events=<br /> carryover_percentage= {can override the defaults}<br /> carryover_add=<br /> bonus=<br /> [/result]<br /> <br /> [result]<br /> outcome=defeat<br /> side=2,3<br /> fire_events=<br /> [/result]<br /> <br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3. Side 1 and 4 will have different carryover amounts.<br /> <br /> Further discussion needed:<br /> * Handling of ''name=victory'' and ''name=defeat'' events<br /> * could the default for ''summary'' be controlled by a menu option / preference? to allow players to always see a summary...<br /> <br /> <br /> Another possible format would be as follows: (thanks Sapient for ideas)<br /> [endlevel]<br /> <br /> next_scenario=<br /> <br /> bonus=<br /> carryover_percentage=<br /> carryover_add=<br /> <br /> summary=<br /> <br /> [victory]<br /> side=1<br /> fire_events=<br /> [/victory]<br /> <br /> [victory]<br /> side=4<br /> carryover_percentage=<br /> carryover_add=<br /> bonus=<br /> fire_events=<br /> [/victory]<br /> <br /> [defeat]<br /> side=2,3<br /> fire_events=<br /> [/defeat]<br /> <br /> [/endlevel]<br /> This will produce the same result as the above format, but involves less WML typing and is clearer what is going on. For ''continue'' and ''continue_no_save'' results, there is a ''[continue]'' tag in addition to [victory] and [defeat] tags, which takes a ''save='' key.<br /> [continue]<br /> side=<br /> save= {yes/no}<br /> [/continue]<br /> <br /> ==== 2008 SoC application ====<br /> [[MapEditorRewrite]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=27695 2008-12-23T05:50:17Z

<p>Dlr365: /* Works in Progress */</p> <hr /> <div>== Works in Progress ==<br /> === Current ===<br /> * bug #12747 [https://gna.org/bugs/index.php?12747] - holding escape quits titlescreen<br /> <br /> === Previous ===<br /> ==== [endlevel] giving different results to different sides ====<br /> (info below is out of date)<br /> <br /> Allows specific sides to be issued specific results in multiplayer, instead of everyone getting the same result. See [http://gna.org/bugs/index.php?4960 bug#4960], [https://gna.org/patch/?1032 patch#1032].<br /> <br /> If [result] tags are found within an [endlevel] tag, the normal ''result='' key will be ignored. If ''summary=yes'' is specified in the [endlevel] tag, then instead of specific victory/defeat messages for only local players, each player is shown the victory/defeat status of all sides. Any sides who are not given a specific [result] are either shown a summary or nothing, and their result is defaulted to ''continue''. Observers are shown a &quot;game over&quot; dialog if ''summary=no'', and the summary if ''summary=yes''.<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> <br /> next_scenario=<br /> <br /> bonus= {these are the defaults for all [result] tags}<br /> carryover_percentage=<br /> carryover_add=<br /> <br /> summary= {controls whether players are shown a summary of all sides, or just their local victory/defeat messages}<br /> <br /> [result]<br /> side=1<br /> outcome=victory {may be victory, defeat, continue, continue_no_save}<br /> fire_events= {yes/no, controls whether victory/defeat events are fired}<br /> [/result]<br /> <br /> [result]<br /> side=4<br /> outcome=victory<br /> fire_events=<br /> carryover_percentage= {can override the defaults}<br /> carryover_add=<br /> bonus=<br /> [/result]<br /> <br /> [result]<br /> outcome=defeat<br /> side=2,3<br /> fire_events=<br /> [/result]<br /> <br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3. Side 1 and 4 will have different carryover amounts.<br /> <br /> Further discussion needed:<br /> * Handling of ''name=victory'' and ''name=defeat'' events<br /> * could the default for ''summary'' be controlled by a menu option / preference? to allow players to always see a summary...<br /> <br /> <br /> Another possible format would be as follows: (thanks Sapient for ideas)<br /> [endlevel]<br /> <br /> next_scenario=<br /> <br /> bonus=<br /> carryover_percentage=<br /> carryover_add=<br /> <br /> summary=<br /> <br /> [victory]<br /> side=1<br /> fire_events=<br /> [/victory]<br /> <br /> [victory]<br /> side=4<br /> carryover_percentage=<br /> carryover_add=<br /> bonus=<br /> fire_events=<br /> [/victory]<br /> <br /> [defeat]<br /> side=2,3<br /> fire_events=<br /> [/defeat]<br /> <br /> [/endlevel]<br /> This will produce the same result as the above format, but involves less WML typing and is clearer what is going on. For ''continue'' and ''continue_no_save'' results, there is a ''[continue]'' tag in addition to [victory] and [defeat] tags, which takes a ''save='' key.<br /> [continue]<br /> side=<br /> save= {yes/no}<br /> [/continue]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=25161 2008-04-08T08:09:59Z

<p>Dlr365: /* Current */</p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite|Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] giving different results to different sides ====<br /> Allows specific sides to be issued specific results in multiplayer, instead of everyone getting the same result. See [http://gna.org/bugs/index.php?4960 bug#4960], [https://gna.org/patch/?1032 patch#1032].<br /> <br /> If [result] tags are found within an [endlevel] tag, the normal ''result='' key will be ignored. If ''summary=yes'' is specified in the [endlevel] tag, then instead of specific victory/defeat messages for only local players, each player is shown the victory/defeat status of all sides. Any sides who are not given a specific [result] are either shown a summary or nothing, and their result is defaulted to ''continue''. Observers are shown a &quot;game over&quot; dialog if ''summary=no'', and the summary if ''summary=yes''.<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> <br /> next_scenario=<br /> <br /> bonus= {these are the defaults for all [result] tags}<br /> carryover_percentage=<br /> carryover_add=<br /> <br /> summary= {controls whether players are shown a summary of all sides, or just their local victory/defeat messages}<br /> <br /> [result]<br /> side=1<br /> outcome=victory {may be victory, defeat, continue, continue_no_save}<br /> fire_events= {yes/no, controls whether victory/defeat events are fired}<br /> [/result]<br /> <br /> [result]<br /> side=4<br /> outcome=victory<br /> fire_events=<br /> carryover_percentage= {can override the defaults}<br /> carryover_add=<br /> bonus=<br /> [/result]<br /> <br /> [result]<br /> outcome=defeat<br /> side=2,3<br /> fire_events=<br /> [/result]<br /> <br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3. Side 1 and 4 will have different carryover amounts.<br /> <br /> Further discussion needed:<br /> * Handling of ''name=victory'' and ''name=defeat'' events<br /> * could the default for ''summary'' be controlled by a menu option / preference? to allow players to always see a summary...<br /> <br /> <br /> Another possible format would be as follows: (thanks Sapient for ideas)<br /> [endlevel]<br /> <br /> next_scenario=<br /> <br /> bonus=<br /> carryover_percentage=<br /> carryover_add=<br /> <br /> summary=<br /> <br /> [victory]<br /> side=1<br /> fire_events=<br /> [/victory]<br /> <br /> [victory]<br /> side=4<br /> carryover_percentage=<br /> carryover_add=<br /> bonus=<br /> fire_events=<br /> [/victory]<br /> <br /> [defeat]<br /> side=2,3<br /> fire_events=<br /> [/defeat]<br /> <br /> [/endlevel]<br /> This will produce the same result as the above format, but involves less WML typing and is clearer what is going on. For ''continue'' and ''continue_no_save'' results, there is a ''[continue]'' tag in addition to [victory] and [defeat] tags, which takes a ''save='' key.<br /> [continue]<br /> side=<br /> save= {yes/no}<br /> [/continue]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=25115 2008-04-06T09:28:26Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite|Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] giving different results to different sides ====<br /> Allows specific sides to be issued specific results in multiplayer, instead of everyone getting the same result. See [http://gna.org/bugs/index.php?4960 bug#4960], [https://gna.org/patch/?1032 patch#1032].<br /> <br /> If [result] tags are found within an [endlevel] tag, the normal ''result='' key will be ignored. If ''summary=yes'' is specified in the [endlevel] tag, then instead of specific victory/defeat messages for only local players, each player is shown the victory/defeat status of all sides. Any sides who are not given a specific [result] are either shown a summary or nothing, and their result is defaulted to ''continue''. Observers are shown a &quot;game over&quot; dialog if ''summary=no'', and the summary if ''summary=yes''.<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> <br /> next_scenario=<br /> <br /> bonus= {these are the defaults for all [result] tags}<br /> carryover_percentage=<br /> carryover_add=<br /> <br /> summary= {controls whether players are shown a summary of all sides, or just their local victory/defeat messages}<br /> <br /> [result]<br /> side=1<br /> outcome=victory {may be victory, defeat, continue, continue_no_save}<br /> [/result]<br /> <br /> [result]<br /> side=4<br /> outcome=victory<br /> carryover_percentage= {can override the defaults}<br /> carryover_add=<br /> [/result]<br /> <br /> [result]<br /> outcome=defeat<br /> side=2,3<br /> [/result]<br /> <br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3. Side 1 and 4 will have different carryover amounts.<br /> <br /> Further discussion needed:<br /> * ''name=victory'' and ''name=defeat'' events are currently ignored when using [result] tags (possibly need to re-structure the way these events are handled...)<br /> * could the default for ''summary'' be controlled by a menu option / preference? to allow players to always see a summary...</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=25114 2008-04-06T09:03:48Z

<p>Dlr365: /* Works in Progress */</p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite|Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] giving different results to different sides ====<br /> Allows specific sides to be issued specific results in multiplayer, instead of everyone getting the same result. See [http://gna.org/bugs/index.php?4960 bug#4960], [https://gna.org/patch/?1032 patch#1032].<br /> <br /> If [result] tags are found within an [endlevel] tag, the normal ''result='' key will be ignored. If ''summary=yes'' is specified in the [endlevel] tag, then instead of specific victory/defeat messages for only local players, each player is shown the victory/defeat status of all sides. Any sides who are not given a specific [result] (including observers) are either shown a summary or nothing, and their result is defaulted to ''continue''.<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> <br /> next_scenario=<br /> <br /> bonus= {these are the defaults for all [result] tags}<br /> carryover_percentage=<br /> carryover_add=<br /> <br /> summary= {controls whether players are shown a summary of all sides, or just their local victory/defeat messages}<br /> <br /> [result]<br /> side=1<br /> outcome=victory {may be victory, defeat, continue, continue_no_save}<br /> [/result]<br /> <br /> [result]<br /> side=4<br /> outcome=victory<br /> carryover_percentage= {can override the defaults}<br /> carryover_add=<br /> [/result]<br /> <br /> [result]<br /> outcome=defeat<br /> side=2,3<br /> [/result]<br /> <br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3. Side 1 and 4 will have different carryover amounts.<br /> <br /> Further discussion needed:<br /> * ''name=victory'' and ''name=defeat'' events are currently ignored when using [result] tags (possibly need to re-structure the way these events are handled...)<br /> * could the default for ''summary'' be controlled by a menu option / preference? to allow players to always see a summary...</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=25113 2008-04-06T09:02:59Z

<p>Dlr365: /* [endlevel] giving different results to different sides */</p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite|Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] giving different results to different sides ====<br /> Allows specific sides to be issued specific results in multiplayer, instead of everyone getting the same result. See [http://gna.org/bugs/index.php?4960 bug#4960], [https://gna.org/patch/?1032 patch#1032].<br /> <br /> If [result] tags are found within an [endlevel] tag, the normal ''result='' key will be ignored. If ''summary=yes'' is specified in the [endlevel] tag, then instead of specific victory/defeat messages for only local players, each player is shown the victory/defeat status of all sides. Any sides who are not given a specific [result] (including observers) are either shown a summary or nothing, and their result is defaulted to ''continue''.<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> <br /> next_scenario=<br /> <br /> bonus= {these are the defaults for all [result] tags}<br /> carryover_percentage=<br /> carryover_add=<br /> <br /> summary= {controls whether players are shown a summary of all sides, or just their local victory/defeat messages}<br /> <br /> [result]<br /> side=1<br /> outcome=victory {may be victory, defeat, continue, continue_no_save}<br /> [/result]<br /> <br /> [result]<br /> side=4<br /> outcome=victory<br /> carryover_percentage= {can override the defaults}<br /> carryover_add=<br /> [/result]<br /> <br /> [result]<br /> outcome=defeat<br /> side=2,3<br /> [/result]<br /> <br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3. Side 1 and 4 will have different carryover amounts.<br /> <br /> Further discussion needed:<br /> * ''name=victory'' and ''name=defeat'' events are currently ignored when using [result] tags (possibly need to re-structure the way these events are handled...)<br /> * could the default for ''summary'' be controlled by a menu option / preference? to allow players to always see a summary...<br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Possible Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24948 2008-03-31T02:25:40Z

<p>Dlr365: /* [endlevel] giving different results to different sides */</p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite|Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] giving different results to different sides ====<br /> Allows specific sides to be issued victory/defeat in multiplayer, instead of everyone getting the same. See [http://gna.org/bugs/index.php?4960 bug#4960], [https://gna.org/patch/?1032 patch#1032].<br /> <br /> If either [victory] or [defeat] tags are found within an [endlevel] tag, the normal ''result='' key will be ignored. Any sides who are not given a specific [victory] or [defeat] are given a &quot;Game Over&quot; message(includes observers) ''(future: give a summary of the victories/defeats)''.<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> next_scenario=<br /> bonus=<br /> carryover_percentage= {this acts as the default for all [victory] tags}<br /> carryover_add= {also default for [victory] tags}<br /> [victory]<br /> side=1<br /> [/victory]<br /> [victory]<br /> side=4<br /> carryover_percentage= {can override the defaults}<br /> carryover_add=<br /> [defeat]<br /> side=2,3<br /> [/defeat]<br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3. Side 1 and 4 will have different carryover amounts.<br /> <br /> Issues with current implementation:<br /> * ''name=victory'' and ''name=defeat'' events are currently ignored<br /> * only supports [victory] and [defeat]... not sure if [continue] or [continue_no_save] tags would make sense....<br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Possible Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24947 2008-03-31T02:24:42Z

<p>Dlr365: /* [endlevel] [result] tag */</p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite|Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] giving different results to different sides ====<br /> Allows specific sides to be issued victory/defeat in multiplayer, instead of everyone getting the same. See [http://gna.org/bugs/index.php?4960 bug#4960], [https://gna.org/patch/?1032 patch#1032].<br /> <br /> If either [victory] or [defeat] tags are found within an [endlevel] tag, the normal ''result='' key will be ignored. Any sides who are not given a specific [victory] or [defeat] are given a summary (includes observers).<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> next_scenario=<br /> bonus=<br /> carryover_percentage= {this acts as the default for all [victory] tags}<br /> carryover_add= {also default for [victory] tags}<br /> [victory]<br /> side=1<br /> [/victory]<br /> [victory]<br /> side=4<br /> carryover_percentage= {can override the defaults}<br /> carryover_add=<br /> [defeat]<br /> side=2,3<br /> [/defeat]<br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3. Side 1 and 4 will have different carryover amounts.<br /> <br /> Issues with current implementation:<br /> * ''name=victory'' and ''name=defeat'' events are currently ignored<br /> * only supports [victory] and [defeat]... not sure if [continue] or [continue_no_save] tags would make sense....<br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Possible Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24857 2008-03-29T21:32:18Z

<p>Dlr365: /* Programming */</p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is dlr365 {at} gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP. The only spoken language I know is English.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...). Pretty much all my programming knowledge has been self-taught, besides small nuances that I have gleaned from my programming classes.<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into Eclipse or NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if you're interested... most code was written in 2006)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> * I'm working on a patch to add support to [endlevel] such that different sides can be given different results. [https://gna.org/patch/?1032 Patch#1032]<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level/scenario editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (Warcraft 3 DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I just recently started playing Wesnoth.<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. This past week I have been familiarizing myself with the Wesnoth code by working on a patch to the [endlevel] tag.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner, fully-commented C++ code, and an improved interface (using the new GUI toolkit that Mordante is working on, if it is ready). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code. Specific ideas for improvement to the map editor itself:<br /> * opening multiple maps<br /> * copy-paste of regions of the map<br /> * terrain changes from holding down the mouse button are considered as one undo step<br /> * scroll bars<br /> * custom brushes, with custom shapes and terrain patterns (savable, thus default templates could be created such as a standard castle)<br /> * random placement functions for terrain elements<br /> * full-map export to *.png<br /> * expanded preferences dialog, allowing changes to many nuances of the interface<br /> * custom terrain import &amp; support<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended (time-permitting) by merging scenario/campaign-editing functionality into it (possibly working together with another SoC project?), which would be much easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * commonly used WML templates<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> * tree-view based WML editing for larger scenarios<br /> <br /> === Goal/Rough Timeline ===<br /> I intend to have a rewritten map editor, with all current functionality, by the end of June. The remainder of the summer would be spent expanding the featureset, and moving towards an integrated map/scenario editor.<br /> More specific dates:<br /> * end of May, possibly earlier : prototype of rewritten map editor, allowing basic map editing<br /> * June : many prototypes of the editor as features are expanded<br /> * end of June : rewritten map editor replicates all current functionality<br /> * July/August : addition of new features and scenario-editing capabilities, and rigorous testing and polishing<br /> <br /> After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am already getting involved with Wesnoth development (whether or not I'm accepted for SoC).<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24856 2008-03-29T21:31:39Z

<p>Dlr365: /* Programming */</p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is dlr365 {at} gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP. The only spoken language I know is English.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...). Pretty much all my programming knowledge has been self-taught, besides small nuances that I have gleaned from my programming classes.<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into Eclipse or NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if you're interested... most code was written in 2006)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> * I'm working on a patch to add support to [endlevel] such that different sides can be given different results. [https://gna.org/patch/?1032|Patch#1032]<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level/scenario editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (Warcraft 3 DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I just recently started playing Wesnoth.<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. This past week I have been familiarizing myself with the Wesnoth code by working on a patch to the [endlevel] tag.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner, fully-commented C++ code, and an improved interface (using the new GUI toolkit that Mordante is working on, if it is ready). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code. Specific ideas for improvement to the map editor itself:<br /> * opening multiple maps<br /> * copy-paste of regions of the map<br /> * terrain changes from holding down the mouse button are considered as one undo step<br /> * scroll bars<br /> * custom brushes, with custom shapes and terrain patterns (savable, thus default templates could be created such as a standard castle)<br /> * random placement functions for terrain elements<br /> * full-map export to *.png<br /> * expanded preferences dialog, allowing changes to many nuances of the interface<br /> * custom terrain import &amp; support<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended (time-permitting) by merging scenario/campaign-editing functionality into it (possibly working together with another SoC project?), which would be much easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * commonly used WML templates<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> * tree-view based WML editing for larger scenarios<br /> <br /> === Goal/Rough Timeline ===<br /> I intend to have a rewritten map editor, with all current functionality, by the end of June. The remainder of the summer would be spent expanding the featureset, and moving towards an integrated map/scenario editor.<br /> More specific dates:<br /> * end of May, possibly earlier : prototype of rewritten map editor, allowing basic map editing<br /> * June : many prototypes of the editor as features are expanded<br /> * end of June : rewritten map editor replicates all current functionality<br /> * July/August : addition of new features and scenario-editing capabilities, and rigorous testing and polishing<br /> <br /> After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am already getting involved with Wesnoth development (whether or not I'm accepted for SoC).<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24855 2008-03-29T21:31:21Z

<p>Dlr365: /* Programming */</p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is dlr365 {at} gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP. The only spoken language I know is English.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...). Pretty much all my programming knowledge has been self-taught, besides small nuances that I have gleaned from my programming classes.<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into Eclipse or NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if you're interested... most code was written in 2006)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> * I'm working on a patch to add support to [endlevel] such that different sides can be given different results. [[https://gna.org/patch/?1032|Patch#1032]]<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level/scenario editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (Warcraft 3 DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I just recently started playing Wesnoth.<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. This past week I have been familiarizing myself with the Wesnoth code by working on a patch to the [endlevel] tag.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner, fully-commented C++ code, and an improved interface (using the new GUI toolkit that Mordante is working on, if it is ready). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code. Specific ideas for improvement to the map editor itself:<br /> * opening multiple maps<br /> * copy-paste of regions of the map<br /> * terrain changes from holding down the mouse button are considered as one undo step<br /> * scroll bars<br /> * custom brushes, with custom shapes and terrain patterns (savable, thus default templates could be created such as a standard castle)<br /> * random placement functions for terrain elements<br /> * full-map export to *.png<br /> * expanded preferences dialog, allowing changes to many nuances of the interface<br /> * custom terrain import &amp; support<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended (time-permitting) by merging scenario/campaign-editing functionality into it (possibly working together with another SoC project?), which would be much easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * commonly used WML templates<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> * tree-view based WML editing for larger scenarios<br /> <br /> === Goal/Rough Timeline ===<br /> I intend to have a rewritten map editor, with all current functionality, by the end of June. The remainder of the summer would be spent expanding the featureset, and moving towards an integrated map/scenario editor.<br /> More specific dates:<br /> * end of May, possibly earlier : prototype of rewritten map editor, allowing basic map editing<br /> * June : many prototypes of the editor as features are expanded<br /> * end of June : rewritten map editor replicates all current functionality<br /> * July/August : addition of new features and scenario-editing capabilities, and rigorous testing and polishing<br /> <br /> After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am already getting involved with Wesnoth development (whether or not I'm accepted for SoC).<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24822 2008-03-29T02:54:38Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite|Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] [result] tag ====<br /> Allows specific sides to be issued victory/defeat in multiplayer, instead of everyone getting the same. See [https://gna.org/bugs/index.php?4960 bug#4960].<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> [result]<br /> [victory]<br /> side=1,4<br /> [/victory]<br /> [defeat]<br /> side=2,3<br /> [/defeat]<br /> [/result]<br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3.<br /> <br /> Problems with current implementation:<br /> * uses ''result=continue'' to suppress regular victory/defeat dialogs, thus bonus gold is never applied to anyone, and ''name=victory'' events are always called regardless of any specific outcomes<br /> ** possible fix -- a new LEVEL_RESULT type that doesn't show dialogs, but gives bonus gold properly and calls the proper ''[event]''s? Needs more discussion.<br /> * does not notify the network immediatly that the game has ended, because the dialog for the current player is shown ''before'' the end_level_exception is thrown<br /> ** this could also possibly be fixed by adding a new LEVEL_RESULT type for when end_level_exception is thrown<br /> * only supports [victory] and [defeat]... not sure if [continue] or [continue_no_save] tags would make sense....<br /> <br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Possible Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24821 2008-03-29T02:53:51Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite|Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] [result] tag ====<br /> Allows specific sides to be issued victory/defeat in multiplayer, instead of everyone getting the same. See [https://gna.org/bugs/index.php?4960 bug#4960].<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> [result]<br /> [victory]<br /> side=1,4<br /> [/victory]<br /> [defeat]<br /> side=2,3<br /> [/defeat]<br /> [/result]<br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3.<br /> <br /> Problems with current implementation:<br /> * uses ''result=continue'' to suppress regular victory/defeat dialogs, thus bonus gold is never applied to anyone, and ''name=victory'' events are always called regardless of any specific outcomes<br /> ** possible fix -- a new LEVEL_RESULT type that doesn't show dialogs, but gives bonus gold properly and calls the proper ''[event]''s? Needs more discussion.<br /> * does not notify the network immediatly that the game has ended, because the dialog for the current player is shown ''before'' the end_level_exception is thrown<br /> ** this could also possibly be fixed by adding a new LEVEL_RESULT type for when end_level_exception is thrown<br /> * only supports [victory] and [defeat]... not sure if [continue] or [continue_no_save] tags would make sense....<br /> <br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Possible Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** --&gt;(not implemented, see note#1)&lt;-- '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24820 2008-03-29T02:53:18Z

<p>Dlr365: /* GSoC Application */</p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite|Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] [result] tag ====<br /> Allows specific sides to be issued victory/defeat in multiplayer, instead of everyone getting the same. See [https://gna.org/bugs/index.php?4960 bug#4960].<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> [result]<br /> [victory]<br /> side=1,4<br /> [/victory]<br /> [defeat]<br /> side=2,3<br /> [/defeat]<br /> [/result]<br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3.<br /> <br /> Problems with current implementation:<br /> * uses ''result=continue'' to suppress regular victory/defeat dialogs, thus bonus gold is never applied to anyone, and ''name=victory'' events are always called regardless of any specific outcomes<br /> ** possible fix -- a new LEVEL_RESULT type that doesn't show dialogs, but gives bonus gold properly and calls the proper ''[event]''s? Needs more discussion.<br /> * does not notify the network immediatly that the game has ended, because the dialog for the current player is shown ''before'' the end_level_exception is thrown<br /> ** this could also possibly be fixed by adding a new LEVEL_RESULT type for when end_level_exception is thrown<br /> * only supports [victory] and [defeat]... not sure if [continue] or [continue_no_save] tags would make sense....<br /> <br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** --&gt;(not implemented, see note#1)&lt;-- '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24819 2008-03-29T02:52:57Z

<p>Dlr365: /* GSoC Application */</p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([[MapEditorRewrite Application Wiki Page]])<br /> <br /> === Current ===<br /> ==== [endlevel] [result] tag ====<br /> Allows specific sides to be issued victory/defeat in multiplayer, instead of everyone getting the same. See [https://gna.org/bugs/index.php?4960 bug#4960].<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> [result]<br /> [victory]<br /> side=1,4<br /> [/victory]<br /> [defeat]<br /> side=2,3<br /> [/defeat]<br /> [/result]<br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3.<br /> <br /> Problems with current implementation:<br /> * uses ''result=continue'' to suppress regular victory/defeat dialogs, thus bonus gold is never applied to anyone, and ''name=victory'' events are always called regardless of any specific outcomes<br /> ** possible fix -- a new LEVEL_RESULT type that doesn't show dialogs, but gives bonus gold properly and calls the proper ''[event]''s? Needs more discussion.<br /> * does not notify the network immediatly that the game has ended, because the dialog for the current player is shown ''before'' the end_level_exception is thrown<br /> ** this could also possibly be fixed by adding a new LEVEL_RESULT type for when end_level_exception is thrown<br /> * only supports [victory] and [defeat]... not sure if [continue] or [continue_no_save] tags would make sense....<br /> <br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** --&gt;(not implemented, see note#1)&lt;-- '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=EasyCoding&diff=24818 2008-03-29T02:52:40Z

<p>Dlr365: </p> <hr /> <div>== Foreword ==<br /> This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task. <br /> <br /> If you are such a person, you should feel free to edit this page.<br /> <br /> If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.<br /> <br /> Anybody should feel free to add &quot;clues&quot; to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.<br /> <br /> If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll &quot;free&quot; it back (that is if you're not working on it. If you have problems implementing it, just tell us....)<br /> <br /> <br /> --[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)<br /> <br /> <br /> Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).<br /> <br /> --Yogi Bear, 28 February 2008<br /> <br /> <br /> <br /> == WML related features ==<br /> <br /> === Side-specific results ===<br /> Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960]) -- [[User:dlr365|dlr365]] -- patch submitted [https://gna.org/bugs/index.php?4960]<br /> === Recall Event ===<br /> WML event trigger for recalling (the current one triggers on both recalls and recruits) ([http://gna.org/bugs/index.php?3622 FR #3622]) (please read the comments of the report for a proper description of how this should work)<br /> === Enabling checking of damage dealt in WML ===<br /> A WML variable should be set when triggering some combat-related events, allowing WML to know the amount of damage being dealt. ([http://gna.org/bugs/index.php?7673 FR #7673])<br /> === Support for leaderless multiplayergames ===<br /> Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])<br /> === Other Ideas ===<br /> See [[FutureWML]]; some ideas there are easier than others.<br /> == Improvements to FormulaAI ==<br /> <br /> Add new formula functions, or minor improvements to the formula language. Make it easier to debug the formula language.<br /> <br /> == GUI related features ==<br /> Note at the moment Mordante is working on a new GUI system, these <br /> changes will probably affect the way these items need to be implemented.<br /> Contact Mordante on IRC before starting to work on these.<br /> <br /> --[[User:SkeletonCrew|SkeletonCrew]] 14:04, 9 March 2008 (EDT)<br /> <br /> === Theme Changes ===<br /> * show number of owned villages/total villages (FR: #3135) (--[[User:Alink|alink]] done but must update help, doc, tooltip...)<br /> * allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])<br /> * hide the hourglass item from the statusbar when there is no timer<br /> <br /> === Widget Changes ===<br /> * show side number, name and team association information in the status table <br /> * make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud) <br /> * input history (chat, commands, ..), seek Sapient for more info and tips<br /> <br /> == Miscellaneous ==<br /> === More powerful village naming ===<br /> '''Adding mountain names and other features to village names, having a second random name in village names'''<br /> <br /> Currently the village naming engine has a very good structure that could allow <br /> more powerfull names to be generated. <br /> Understanding how it works should be quite easy, and a few usefull improvements could be added.<br /> <br /> * Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...<br /> * It would be nice to have a separate list of &quot;first sylabus&quot; and &quot;last sylabus&quot; for naming. That's not really needed in english, but some translations could use it<br /> * Again, it is common to have villages with more than one &quot;random&quot; word in them. having a $name2 variable would be nice<br /> <br /> ACardboardRobot 2/2/07<br /> <br /> === Debug Mode ===<br /> * New debug command functionality (setting additional status.variables, possibly terrain)<br /> <br /> === Additional Commandline Options ===<br /> <br /> It would be nice if one could start Wesnoth from commandline specifying whether one wants to connect to a mp-server, load the last savegame or wants to start a campaign. More detailed information and examples are given in the [http://www.wesnoth.org/forum/viewtopic.php?f=12&amp;t=20243 idea forum].<br /> <br /> == Bugs ==<br /> <br /> <br /> <br /> == See Also ==<br /> <br /> [[NotSoEasyCoding]]<br /> <br /> [[Category:Development]]<br /> [[Category:Future]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24817 2008-03-29T02:45:34Z

<p>Dlr365: /* GSoC Application */</p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. ([http://www.wesnoth.org/wiki/MapEditorRewrite Application Wiki Page])<br /> <br /> === Current ===<br /> ==== [endlevel] [result] tag ====<br /> Allows specific sides to be issued victory/defeat in multiplayer, instead of everyone getting the same. See [https://gna.org/bugs/index.php?4960 bug#4960].<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> [result]<br /> [victory]<br /> side=1,4<br /> [/victory]<br /> [defeat]<br /> side=2,3<br /> [/defeat]<br /> [/result]<br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3.<br /> <br /> Problems with current implementation:<br /> * uses ''result=continue'' to suppress regular victory/defeat dialogs, thus bonus gold is never applied to anyone, and ''name=victory'' events are always called regardless of any specific outcomes<br /> ** possible fix -- a new LEVEL_RESULT type that doesn't show dialogs, but gives bonus gold properly and calls the proper ''[event]''s? Needs more discussion.<br /> * does not notify the network immediatly that the game has ended, because the dialog for the current player is shown ''before'' the end_level_exception is thrown<br /> ** this could also possibly be fixed by adding a new LEVEL_RESULT type for when end_level_exception is thrown<br /> * only supports [victory] and [defeat]... not sure if [continue] or [continue_no_save] tags would make sense....<br /> <br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** --&gt;(not implemented, see note#1)&lt;-- '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24816 2008-03-29T02:44:58Z

<p>Dlr365: /* Works in Progress */</p> <hr /> <div>== Works in Progress ==<br /> === GSoC Application ===<br /> I plan to re-write the map editor. [http://www.wesnoth.org/wiki/MapEditorRewrite]<br /> <br /> === Current ===<br /> ==== [endlevel] [result] tag ====<br /> Allows specific sides to be issued victory/defeat in multiplayer, instead of everyone getting the same. See [https://gna.org/bugs/index.php?4960 bug#4960].<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> [result]<br /> [victory]<br /> side=1,4<br /> [/victory]<br /> [defeat]<br /> side=2,3<br /> [/defeat]<br /> [/result]<br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3.<br /> <br /> Problems with current implementation:<br /> * uses ''result=continue'' to suppress regular victory/defeat dialogs, thus bonus gold is never applied to anyone, and ''name=victory'' events are always called regardless of any specific outcomes<br /> ** possible fix -- a new LEVEL_RESULT type that doesn't show dialogs, but gives bonus gold properly and calls the proper ''[event]''s? Needs more discussion.<br /> * does not notify the network immediatly that the game has ended, because the dialog for the current player is shown ''before'' the end_level_exception is thrown<br /> ** this could also possibly be fixed by adding a new LEVEL_RESULT type for when end_level_exception is thrown<br /> * only supports [victory] and [defeat]... not sure if [continue] or [continue_no_save] tags would make sense....<br /> <br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** --&gt;(not implemented, see note#1)&lt;-- '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24815 2008-03-29T02:14:20Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === Current ===<br /> ==== [endlevel] [result] tag ====<br /> Allows specific sides to be issued victory/defeat in multiplayer, instead of everyone getting the same. See [https://gna.org/bugs/index.php?4960 bug#4960].<br /> <br /> Example WML syntax:<br /> [endlevel]<br /> [result]<br /> [victory]<br /> side=1,4<br /> [/victory]<br /> [defeat]<br /> side=2,3<br /> [/defeat]<br /> [/result]<br /> [/endlevel]<br /> This will issue a victory message for sides 1 and 4, and a defeat message for sides 2 and 3.<br /> <br /> Problems with current implementation:<br /> * uses ''result=continue'' to suppress regular victory/defeat dialogs, thus bonus gold is never applied to anyone, and ''name=victory'' events are always called regardless of any specific outcomes<br /> ** possible fix -- a new LEVEL_RESULT type that doesn't show dialogs, but gives bonus gold properly and calls the proper ''[event]''s? Needs more discussion.<br /> * does not notify the network immediatly that the game has ended, because the dialog for the current player is shown ''before'' the end_level_exception is thrown<br /> ** this could also possibly be fixed by adding a new LEVEL_RESULT type for when end_level_exception is thrown<br /> * only supports [victory] and [defeat]... not sure if [continue] or [continue_no_save] tags would make sense....<br /> <br /> <br /> === Need More Thought/Discussion ===<br /> ==== [endlevel] [result] tag ====<br /> * The current implementation has a few key issues still... see above for problems/fix ideas... further ideas/discussion will go here.<br /> * Want to add support for a [summary] tag that simply shows the results of the [victory] and [defeat] tags to observers (or specific sides).<br /> <br /> ==== [result] -- new DirectActionWML ====<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ===== Implementation =====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** --&gt;(not implemented, see note#1)&lt;-- '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ===== Notes =====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24786 2008-03-28T01:17:18Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is dlr365 {at} gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP. The only spoken language I know is English.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...). Pretty much all my programming knowledge has been self-taught, besides small nuances that I have gleaned from my programming classes.<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into Eclipse or NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if you're interested... most code was written in 2006)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level/scenario editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (Warcraft 3 DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I just recently started playing Wesnoth.<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. This past week I have been familiarizing myself with the Wesnoth code by working on a patch to the [endlevel] tag.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner, fully-commented C++ code, and an improved interface (using the new GUI toolkit that Mordante is working on, if it is ready). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code. Specific ideas for improvement to the map editor itself:<br /> * opening multiple maps<br /> * copy-paste of regions of the map<br /> * terrain changes from holding down the mouse button are considered as one undo step<br /> * scroll bars<br /> * custom brushes, with custom shapes and terrain patterns (savable, thus default templates could be created such as a standard castle)<br /> * random placement functions for terrain elements<br /> * full-map export to *.png<br /> * expanded preferences dialog, allowing changes to many nuances of the interface<br /> * custom terrain import &amp; support<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended (time-permitting) by merging scenario/campaign-editing functionality into it (possibly working together with another SoC project?), which would be much easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * commonly used WML templates<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> * tree-view based WML editing for larger scenarios<br /> <br /> === Goal/Rough Timeline ===<br /> I intend to have a rewritten map editor, with all current functionality, by the end of June. The remainder of the summer would be spent expanding the featureset, and moving towards an integrated map/scenario editor.<br /> More specific dates:<br /> * end of May, possibly earlier : prototype of rewritten map editor, allowing basic map editing<br /> * June : many prototypes of the editor as features are expanded<br /> * end of June : rewritten map editor replicates all current functionality<br /> * July/August : addition of new features and scenario-editing capabilities, and rigorous testing and polishing<br /> <br /> After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am already getting involved with Wesnoth development (whether or not I'm accepted for SoC).<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24783 2008-03-28T00:54:37Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is dlr365 {at} gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP. The only spoken language I know is English.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...). Pretty much all my programming knowledge has been self-taught, besides small nuances that I have gleaned from my programming classes.<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into Eclipse or NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if anyone is interested)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level/scenario editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (Warcraft 3 DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I just recently started playing Wesnoth.<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. This past week I have been familiarizing myself with the Wesnoth code by working on a patch to the [endlevel] tag.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner, fully-commented C++ code, and an improved interface (using the new GUI toolkit that Mordante is working on, if it is ready). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code. Specific ideas for improvement to the map editor itself:<br /> * opening multiple maps<br /> * copy-paste of regions of the map<br /> * terrain changes from holding down the mouse button are considered as one undo step<br /> * scroll bars<br /> * custom brushes, with custom shapes and terrain patterns (savable, thus default templates could be created such as a standard castle)<br /> * random placement functions for terrain elements<br /> * full-map export to *.png<br /> * expanded preferences dialog, allowing changes to many nuances of the interface<br /> * custom terrain import &amp; support<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended (time-permitting) by merging scenerio/campaign-editing functionality into it (possibly working together with another SoC project?), which would be much easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * commonly used WML templates<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> * tree-view based WML editing for larger scenarios<br /> <br /> === Goal/Rough Timeline ===<br /> I intend to have a rewritten map editor, with all current functionality, by the end of June. The remainder of the summer would be spent expanding the featureset, and moving towards an integrated map/scenario editor.<br /> More specific dates:<br /> * end of May, possibly earlier : prototype of rewritten map editor, allowing basic map editing<br /> * June : many prototypes of the editor as features are expanded<br /> * end of June : rewritten map editor replicates all current functionality<br /> * July/August : addition of new features and scenario-editing capabilities, and rigorous testing and polishing<br /> <br /> After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am already getting involved with Wesnoth development (whether or not I'm accepted for SoC).<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24782 2008-03-28T00:53:15Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is dlr365 {at} gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...). Pretty much all my programming knowledge has been self-taught, besides small nuances that I have gleaned from my programming classes.<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into Eclipse or NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if anyone is interested)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level/scenario editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (Warcraft 3 DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I just recently started playing Wesnoth.<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. This past week I have been familiarizing myself with the Wesnoth code by working on a patch to the [endlevel] tag.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner, fully-commented C++ code, and an improved interface (using the new GUI toolkit that Mordante is working on, if it is ready). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code. Specific ideas for improvement to the map editor itself:<br /> * opening multiple maps<br /> * copy-paste of regions of the map<br /> * terrain changes from holding down the mouse button are considered as one undo step<br /> * scroll bars<br /> * custom brushes, with custom shapes and terrain patterns (savable, thus default templates could be created such as a standard castle)<br /> * random placement functions for terrain elements<br /> * full-map export to *.png<br /> * expanded preferences dialog, allowing changes to many nuances of the interface<br /> * custom terrain import<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended (time-permitting) by merging scenerio/campaign-editing functionality into it (possibly working together with another SoC project?), which would be much easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * commonly used WML templates<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> * tree-view based WML editing for larger scenarios<br /> <br /> === Goal/Rough Timeline ===<br /> I intend to have a rewritten map editor, with all current functionality, by the end of June. The remainder of the summer would be spent expanding the featureset, and moving towards an integrated map/scenario editor.<br /> More specific dates:<br /> * end of May, possibly earlier : prototype of rewritten map editor, allowing basic map editing<br /> * June : many prototypes of the editor as features are expanded<br /> * end of June : rewritten map editor replicates all current functionality<br /> * July/August : addition of new features and scenario-editing capabilities, and rigorous testing and polishing<br /> <br /> After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am already getting involved with Wesnoth development (whether or not I'm accepted for SoC).<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24781 2008-03-28T00:51:52Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is the same username, @gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...). Pretty much all my programming knowledge has been self-taught, besides small nuances that I have gleaned from my programming classes.<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into Eclipse or NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if anyone is interested)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level/scenario editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (Warcraft 3 DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I just recently started playing Wesnoth.<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. This past week I have been familiarizing myself with the Wesnoth code by working on a patch to the [endlevel] tag.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner, fully-commented C++ code, and an improved interface (using the new GUI toolkit that Mordante is working on, if it is ready). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code. Specific ideas for improvement to the map editor itself:<br /> * opening multiple maps<br /> * copy-paste of regions of the map<br /> * terrain changes from holding down the mouse button are considered as one undo step<br /> * scroll bars<br /> * custom brushes, with custom shapes and terrain patterns (savable, thus default templates could be created such as a standard castle)<br /> * random placement functions for terrain elements<br /> * full-map export to *.png<br /> * expanded preferences dialog, allowing changes to many nuances of the interface<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended (time-permitting) by merging scenerio/campaign-editing functionality into it (possibly working together with another SoC project?), which would be much easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * commonly used WML templates<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> * tree-view based WML editing for larger scenarios<br /> <br /> === Goal/Rough Timeline ===<br /> I intend to have a rewritten map editor, with all current functionality, by the end of June. The remainder of the summer would be spent expanding the featureset, and moving towards an integrated map/scenario editor.<br /> More specific dates:<br /> * end of May, possibly earlier : prototype of rewritten map editor, allowing basic map editing<br /> * June : many prototypes of the editor as features are expanded<br /> * end of June : rewritten map editor replicates all current functionality<br /> * July/August : addition of new features and scenario-editing capabilities, and rigorous testing and polishing<br /> <br /> After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am already getting involved with Wesnoth development (whether or not I'm accepted for SoC).<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24780 2008-03-28T00:50:36Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is the same username, @gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...). Pretty much all my programming knowledge has been self-taught, besides small nuances that I have gleaned from my programming classes.<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into Eclipse or NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if anyone is interested)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level/scenario editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (Warcraft 3 DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I just recently started playing Wesnoth.<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. This past week I have been familiarizing myself with the Wesnoth code by working on a patch to the [endlevel] tag.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner, fully-commented C++ code, and an improved interface (using the new GUI toolkit that Mordante is working on, if it is ready). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code. Specific ideas for improvement to the map editor itself:<br /> * opening multiple maps<br /> * copy-paste of regions of the map<br /> * terrain changes from holding down the mouse button are considered as one undo step<br /> * scroll bars<br /> * custom brushes, with custom shapes and terrain patterns (savable, thus default templates could be created such as a standard castle)<br /> * random placement functions for terrain elements<br /> * full-map export to *.png<br /> * expanded preferences dialog, allowing changes to many nuances of the interface<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended (time-permitting) by merging scenerio/campaign-editing functionality into it (possibly working together with another SoC project?), which would be much easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * commonly used WML templates<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> <br /> === Goal/Rough Timeline ===<br /> I intend to have a rewritten map editor, with all current functionality, by the end of June. The remainder of the summer would be spent expanding the featureset, and moving towards an integrated map/scenario editor.<br /> More specific dates:<br /> * end of May, possibly earlier : prototype of rewritten map editor, allowing basic map editing<br /> * June : many prototypes of the editor as features are expanded<br /> * end of June : rewritten map editor replicates all current functionality<br /> * July/August : addition of new features and scenario-editing capabilities, and rigorous testing and polishing<br /> <br /> After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am already getting involved with Wesnoth development (whether or not I'm accepted for SoC).<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24755 2008-03-27T06:58:26Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === [result] -- new DirectActionWML ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ==== Implementation ====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** --&gt;(not implemented, see note#1)&lt;-- '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored. ''(see note#1)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given defeat. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ==== Notes ====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24754 2008-03-27T06:25:57Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === [result] -- new DirectActionWML ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ==== Implementation ====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** --&gt;(not implemented, see note#1)&lt;-- '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : comma-delimited list of the sides to be given victory. If not included, the ''[victory]'' tag is ignored.<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : the side to be given defeat. Each ''[defeat]'' tag may include multiple ''side'' keys. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ==== Notes ====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24753 2008-03-27T06:21:14Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === [result] -- new DirectActionWML ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ==== Implementation ====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** --&gt;(not implemented, see note#1)&lt;-- '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : the side to be given victory. All teammates of the given side will also be given victory. If not included, the ''[victory]'' tag is ignored.<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : the side to be given defeat. Each ''[defeat]'' tag may include multiple ''side'' keys. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ==== Notes ====<br /> # does having multiple opposing sides with victory make sense??<br /> # out of sync problems in MP with bonus gold?<br /> # TODO : allow comma-delimited lists for ''side'' in ''[defeat]'' tags<br /> # TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> #* when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24752 2008-03-27T06:13:26Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === [result] -- new DirectActionWML ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ==== Implementation ====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : the side to be given victory. All teammates of the given side will also be given victory. If not included, the ''[victory]'' tag is ignored.<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''yes''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : the side to be given defeat. Each ''[defeat]'' tag may include multiple ''side'' keys. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ==== Notes ====<br /> * out of sync problems in MP with bonus gold?<br /> * TODO : allow comma-delimited lists for ''side'' in ''[defeat]'' tags<br /> * TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> ** when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24748 2008-03-27T05:31:08Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === [result] -- new DirectActionWML ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ==== Implementation ====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. '''CURRENT IMPLEMENTATION DOES NOT ALLOW ''endlevel=no''!''' The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Can have either zero or one ''[victory]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : the side to be given victory. All teammates of the given side will also be given victory. If not included, the ''[victory]'' tag is ignored.<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''no''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Can have either zero or one ''[defeat]'' tag per ''[results]'' tag. Valid keys:<br /> *** '''side''' : the side to be given defeat. Each ''[defeat]'' tag may include multiple ''side'' keys. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> * If neither a ''[victory]'' nor ''[defeat]'' tag is specified, then all sides are issued ''default_result''.<br /> <br /> ==== Notes ====<br /> * out of sync problems in MP with bonus gold?<br /> * TODO : allow comma-delimited lists for ''side'' in ''[defeat]'' tags<br /> * TODO : allow ''endlevel=no'' (may require server-side changes...)<br /> ** when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer?</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24737 2008-03-27T04:25:51Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === [result] -- new DirectActionWML ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides from within events, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ==== Implementation ====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given victory. All teammates of the given side will also be given victory. If not included, the ''[victory]'' tag is ignored.<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''no''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given defeat. Each ''[defeat]'' tag may include multiple ''side'' keys. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> ==== Notes ====<br /> * out of sync problems in MP with bonus gold?<br /> * when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer? or just get dropped &amp; then have to rejoin?<br /> * TODO : allow comma-delimited lists for '''side'''</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24736 2008-03-27T04:23:13Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === [result] event tag ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ==== Implementation ====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given victory. All teammates of the given side will also be given victory. If not included, the ''[victory]'' tag is ignored.<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''no''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given defeat. Each ''[defeat]'' tag may include multiple ''side'' keys. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> ==== Notes ====<br /> * out of sync problems in MP with bonus gold?<br /> * when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer? or just get dropped &amp; then have to rejoin?<br /> * TODO : allow comma-delimited lists for '''side'''</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24734 2008-03-27T04:17:17Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === [result] event tag ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> ==== Implementation ====<br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given victory. Each ''[victory]'' tag may include multiple ''side'' keys. If not included, the ''[victory]'' tag is ignored.<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''no''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given defeat. Each ''[defeat]'' tag may include multiple ''side'' keys. If not included, the ''[defeat]'' tag is ignored.<br /> <br /> ==== Notes ====<br /> * out of sync problems in MP with bonus gold?<br /> * when someone is issued defeat in MP (when there is 3 or more teams), could they become an observer? or just get dropped &amp; then have to rejoin?<br /> * TODO : allow comma-delimited lists for '''side'''</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24722 2008-03-27T03:33:59Z

<p>Dlr365: </p> <hr /> <div>== Works in Progress ==<br /> === [result] event tag ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given victory. Each ''[victory]'' tag may include multiple ''side'' keys. If not included, the ''[victory]'' tag is ignored. ''(Todo: allow side to be a comma-delimited list of sides)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''no''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> ** '''[defeat]''' : issues defeat to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given defeat. Each ''[defeat]'' tag may include multiple ''side'' keys. If not included, the ''[defeat]'' tag is ignored. ''(Todo: allow side to be a comma-delimited list of sides)''</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=User:Dlr365&diff=24721 2008-03-27T03:33:35Z

<p>Dlr365: New page: == Works in Progress == === [result] event tag === This tag would allow scenario authors to issue victory/defeat to specific sides, without the scenario necessarily ending (if it makes sen...</p> <hr /> <div>== Works in Progress ==<br /> === [result] event tag ===<br /> This tag would allow scenario authors to issue victory/defeat to specific sides, without the scenario necessarily ending (if it makes sense for it to continue).<br /> <br /> * The following keys are valid:<br /> ** '''endlevel''' : this key specifies if the level should be ended. Can be either ''yes'' or ''no''. Defaults to ''yes''. The following keys may be used if ''endlevel=yes'':<br /> *** '''next_scenario''' : the ID of the next scenario that is to be played. Default specified in ''[scenario]'' tag.<br /> *** '''default_result''' : sides who are not given specific results are issued this result. Defaults to ''defeat''.<br /> <br /> * The following tags are valid:<br /> ** '''[victory]''' : issues victory to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given victory. Each ''[victory]'' tag may include multiple ''side'' keys. If not included, the ''[victory]'' tag is ignored. ''(Todo: allow side to be a comma-delimited list of sides)''<br /> *** '''bonus''' : whether the sides specified in this ''[victory]'' tag should get bonus gold. Can be either ''yes'' or ''no''. Defaults to ''no''.<br /> *** '''carryover_percentage''' : Amount of gold carried over into the next scenario. Defaults to 80%.<br /> *** '''carryover_add''' : if ''true'' the gold will be added to the starting gold the next scenario, if ''false'' the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is ''false''.<br /> <br /> ** '''[defeat]''' : issues defeat to the specified sides. Valid keys:<br /> *** '''side''' : the side to be given defeat. Each ''[defeat]'' tag may include multiple ''side'' keys. If not included, the ''[defeat]'' tag is ignored. ''(Todo: allow side to be a comma-delimited list of sides)''</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=SummerOfCodeIdeas&diff=24546 2008-03-25T04:40:29Z

<p>Dlr365: </p> <hr /> <div>This is a compilation of ideas from ML. Needs to be refined (more detailed description, deliverables, workload estimation?):<br /> <br /> == I want to be one of your Google Summer of Code students, what should I do... ==<br /> <br /> Here is a quick list of things to do to get you started<br /> * Create an account on gna.org<br /> * Create an account on the wesnoth forum<br /> * Join the irc channel (#wesnoth-dev on irc.freenode.net) and introduce yourself. We will not give formal interviews, but we will clearly favor people we have learnt to know during the selection process<br /> * Contact one of our SummerOfCode people (Ivanovic, Sirp, Boucman, Mordante) to have your forum nick marked as a Summer of code student<br /> <br /> * Start a wiki page about your idea, add a link on the bottom of this page and add this information on it:<br /> ** List your account names (gna, forum, irc nick) so that we can recognize you<br /> ** Fill the questionnaire on this page: [[SoC_Information_for_Google#Does_your_organization_have_an_application_template_you_would_like_to_see_students_use.3F_If_so.2C_please_provide_it_now.| List of questions to answer]]<br /> ** Detail your idea as much as possible, look at other students pages, and please give milestones and studies you've done<br /> <br /> * Though not mandatory, it is highly advisable to go to the [[EasyCoding]] and [[NotSoEasyCoding]] pages and implement one of these ideas (or any idea of similar scope) so we have an idea how you work. Be sure to use your gna account when submitting these patches so we know who it is coming from. You can also implement some features from our feature request database at gna. When you implement something, also list it on your own page with a reference to the patch.<br /> <br /> * Once you have everything done here and think your idea is okay, go to [http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants to page at google] to submit your application. You have to submit it before '''Monday, March 31, 2008''' or you have no chance to get in!<br /> <br /> == List of Ideas for the Project (Suggestions from the wesnoth developers) ==<br /> <br /> Here is only a short description of possible Ideas we have, each has a page of its own with a more detailed version on it.<br /> <br /> === Writing an AI based on the formula AI ===<br /> <br /> 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: [[FormulaAI]]<br /> <br /> The Wesnoth AI is used as an opponent in most campaigns, and as such is an important piece of code for the Wesnoth project. Unfortunately, because the skills required to understand and modify it are rather arcane, it is also one of the most neglected parts of the Wesnoth code. This is a place where a lot of research and useful work could be done. But keep in mind that [[WhyWritingAWesnothAIIsHard|writing an AI for Wesnoth is difficult]].<br /> <br /> [[SoC Ideas FormulaAI]] - Full version of the idea, with detailed information<br /> <br /> === Extending the Multiplayer server ===<br /> <br /> Our multiplayer community is generally strong and healthy, but we believe its growth is limited by some problems in the interface of the multiplayer lobby.<br /> <br /> [[SoC Ideas Multiplayer server]] - Full version of the idea, with detailed information<br /> <br /> === Scenario/Campaign editor ===<br /> <br /> Currently, in order to create campaign or multiplayer scenarios, it is necessary to manually edit WML files - XML-like configuration files. The goal of this project would be to create a graphical editor to make the creative process easier.<br /> <br /> [[SoC Ideas Scenario and Campaign Editor]] - Full version of the idea, with detailed information<br /> <br /> === Addon server ===<br /> Wesnoth has an addon server which offers users to upload user <br /> made content (UMC). This allows all other users of Wesnoth<br /> to easily download and install this content. The server was <br /> originally written for user-made campaigns but contains a lot<br /> more types of addons nowadays. Both the server side and the <br /> client side need to be improved.<br /> <br /> [[SoC Ideas Addon Server]] - Full version of the idea, with detailed information<br /> <br /> === Map editor ===<br /> The map editor in Wesnoth serves two goals, making it easy to create<br /> a new map and helping the terrain artists to test their new terrains.<br /> <br /> [[SoC_Ideas_Map_Editor]] - Full version of the idea, with detailed information<br /> <br /> === Other possible ideas to be fleshed out ===<br /> A MapGenerator rewrite - better scalable for outdoor maps, plus the possibility to define areas (similar to the caverns in the cave generator) etc.<br /> <br /> === Make your own ideas ===<br /> If you have your own idea the best thing is to join IRC wesnoth-dev at irc.freenode.net and discuss the idea with the developers there. If the developers think your idea is interesting and like the feature you can start to turn it into a full proposal. Once done discuss it again on IRC so the developers can accept your idea.<br /> <br /> == Information about our Project ==<br /> The information we provided google with about our project can be looked up at the site [[SoC Information for Google]].<br /> <br /> Also see the [[DeveloperResources]] link (from the [[Project]] page).<br /> <br /> == People to bug on IRC ==<br /> We have prepared a list of people with their &quot;area of competence&quot;. This is to give you an idea on which areas those people can be of help for you. Of course you should always just ask in the IRC chan, but those are the most likely ones to answer questions in the respective area. And here is the list:<br /> <br /> [[SoC People to bug on IRC]]<br /> <br /> == GSoC Student Applicant Ideas == <br /> <br /> Every student interested to work on Wesnoth as part of Summer of Code should create a page of his own where several things should be listed. Here is a short list of what should be mentioned on the list (the more info for us, the better...):<br /> <br /> * Who are you? Please list your IRC and forum nickname in here and describe yourself so that we get you to know.<br /> * What do you want to work on? Please flesh out your personal ideas, so that we get to know what you plan to work on.<br /> * If you already submitted patches, please list those so that we have a reference.<br /> <br /> ===[[SoC Ideas FormulaAI|Formula AI]]===<br /> ====[[FormulaAIandAdaptation]] (Alesis-Novik) ====<br /> The new idea and aproach using strategic and inside game knowledge<br /> <br /> ==== [[FormulaAIandDynamicScripting]] (barbarianhero) ====<br /> This project idea uses Formula AI and Dynamic Scripting to create a tunable and adaptive AI.<br /> <br /> ====[[FormulaAIBaseAI]] (Dragonking) ====<br /> Developing smart and pluggable AI, which would be really easy tweakable by Scenario and Campaign Developers <br /> <br /> ====[[Building A Strategic Planner with Formula AI|FormulaAI Planner]] (TVincent) ====<br /> This project idea uses (and maybe extends) Formula AI to create a strategic, responsive AI of the Planner model.<br /> <br /> ===[[SoC Ideas Multiplayer server|Multiplayer Server]]===<br /> ====[[ExtendingMultiplayerServer]] (dudegaurav) ====<br /> Under Construction ... <br /> <br /> ===[[SoC Ideas Scenario and Campaign Editor|Scenario/Campaign Editor]]===<br /> ====[[ExtensibleScenarioEditor]] (david.hilton) ====<br /> On a conceptual level, this idea combines a finite state machine editor with a code generator to create scenarios.<br /> <br /> ====[[pyQTScenarioEditor]] (Malle) ====<br /> That's me!<br /> <br /> ====[[RujasuScenarioEditor]] (rujasu) ====<br /> Scenario editor that will coordinate with the look and feel of the Wesnoth game.<br /> <br /> ===[[SoC Ideas Addon Server|Addon Server]]===<br /> ====[[AddonServerSocial]] (lao) ====<br /> Improving addon Server/Client by adding some social content.<br /> <br /> ====[[AddonServer]] (giebfried) ====<br /> This project is to improve the server and client sides of the addon server, as suggested above.<br /> <br /> ===[[SoC Ideas Map Editor|Map Editor]]===<br /> ====[[EvolutionaryMapEditor]] (xonev) ====<br /> An evolutionary approach to improving the map editor.<br /> <br /> ====[[VimzardMapEditor]] (vimzard) ====<br /> A better random map generator, some essential features and a tie-in with the Scenario Editor.<br /> <br /> ====[[NewMapEditor]] (Cecen) ====<br /> This is basically a rewrite of the current map editor with various added features and tweaks to both increase the versatility of the editor and make it easier for the user to create maps with.<br /> <br /> ====[[MapEditorRewrite]] (dlr365)====<br /> A rewrite of the map editor, then taking it in the direction of a combined map/scenario editor for both quick scenarios and more complex ones.<br /> <br /> ===Map Generator===<br /> ====[[RandomCampaignGenerator]] (kartik thakore, refining idea) ====<br /> Procedural map generation that will hope to give writers better control over the random map generator using an interface.<br /> <br /> ===Other===<br /> ====[[WesnothStatistics]] (radx) ====<br /> Project related to Wesnoth statistics (campaign) submission, gathering and presentation.<br /> <br /> [[Category:Summer of Code|*]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24544 2008-03-25T04:37:25Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is the same username, @gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...) and it got lost when I installed a different distro on my computer<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if anyone is interested)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (Warcraft 3 DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I have not played Wesnoth before 2 weeks ago... :(<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. Also these last few weeks have been crunch time with my coursework, so I have had little time to come up with a thorough concept/timeline.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner code and a possibly improved interface (using the new GUI toolkit that Mordante is working on). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code.<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended by merging scenerio/campaign-editing functionality into it (possibly working together with another SoC project?), which would be made easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> <br /> === Goal/Rough Timeline ===<br /> Over the summer I would aim to get a fully rewritten map editor running, adding as many extras as time allows. After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am planning to get involved with Wesnoth development whether or not I'm accepted for SoC.<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24542 2008-03-25T04:37:01Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is the same username, @gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...) and it got lost when I installed a different distro on my computer<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if anyone is interested)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I have not played Wesnoth before 2 weeks ago... :(<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> I would like to work on Wesnoth for SoC since I love gaming, I enjoy strategy games, and I like the developer atmosphere and community (from what I have seen on IRC &amp; forums).<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. Also these last few weeks have been crunch time with my coursework, so I have had little time to come up with a thorough concept/timeline.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner code and a possibly improved interface (using the new GUI toolkit that Mordante is working on). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code.<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended by merging scenerio/campaign-editing functionality into it (possibly working together with another SoC project?), which would be made easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> <br /> === Goal/Rough Timeline ===<br /> Over the summer I would aim to get a fully rewritten map editor running, adding as many extras as time allows. After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am planning to get involved with Wesnoth development whether or not I'm accepted for SoC.<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=24538 2008-03-25T04:35:09Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, and I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/email/etc my username is dlr365. Email is the same username, @gmail.com<br /> <br /> I am usually awake from 1500 to 0500 UTC, and would be fine with communicating over IRC/forums/MSN/email/VoIP.<br /> <br /> === Experience ===<br /> ==== Programming ====<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had.<br /> * I'm very comfortable working in C++ and Java. I have never used Python before. I set up my own SVN server a while back, but I didn't end up using it for very long (school got in the way of my hobby project...) and it got lost when I installed a different distro on my computer<br /> * When coding I currently use [http://www.jedit.org jEdit], but I have been looking into NetBeans (I used to use VB6's IDE extensively)<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game (Minotaur) I had poked around in, complete with a graphical interface.<br /> * I have (some) experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Windows' GDI if anyone is interested)<br /> * I have worked on software in a team environment through school projects (very small team size though)<br /> * I have never been involved in GSoC<br /> <br /> ==== Gaming ====<br /> * I created many custom Starcraft maps/scenarios in highschool, so I have experience with a commercial level editor.<br /> * I love most kinds of games, specifically strategy, first person shooters, and (slightly less so) RPG's.<br /> * Story vs. gameplay.... very tough question... both are important, but if I had to choose I'd say that good gameplay is needed no matter how good your story is. Any game that excels in both will likely make me lose all track of time :P (examples-- Deus Ex, God of War 1 &amp; 2, Final Fantasy 7, Golden Sun 1 &amp; 2, Warcraft 3)<br /> * I enjoy playing with highly competitive opponents (DotA leagues), but I also enjoy playing games just for fun/relaxing as well (Unreal Tournament at LAN parties)<br /> * I have not played Wesnoth before 2 weeks ago... :(<br /> <br /> <br /> == Interest in Summer of Code ==<br /> I would love to participate in the Summer of Code, as I have been wanting to get involved with an open source project for some time now. Since the Summer of Code is paid, it would allow me to dedicate much more time towards it than if I was trying to develop the map editor in my spare time.<br /> <br /> <br /> == GSoC Idea ==<br /> Rewrite the map editor, and add additional features that are requested by the community. I would eventually like to take the map editor in the direction of a full-fledged scenario editor (likely to be completed after SoC).<br /> I admit that since I am new to Wesnoth, I don't know a whole bunch of things that may be useful, but I am motivated and willing to learn the codebase, WML, and talk to the users of the map editor (both serious scenario authors and casual map creators) in order to determine what features should be added. Also these last few weeks have been crunch time with my coursework, so I have had little time to come up with a thorough concept/timeline.<br /> <br /> === Details ===<br /> The current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner code and a possibly improved interface (using the new GUI toolkit that Mordante is working on). I would modularize the code such that any further improvements would be relatively easy to implement as compared to the current code.<br /> <br /> === Further Ideas ===<br /> The map editor would be further extended by merging scenerio/campaign-editing functionality into it (possibly working together with another SoC project?), which would be made easier if the code were made cleaner. Possible ideas on this front could include:<br /> * unit placement with custom properties<br /> * event creation dialogs for simple, commonly used events<br /> * side-by-side WML editing functionality, for more complex scenarios, and with positions/units/etc in WML linked to a graphical icon in the terrain view<br /> <br /> === Goal/Rough Timeline ===<br /> Over the summer I would aim to get a fully rewritten map editor running, adding as many extras as time allows. After the summer I would continue working on the map editor (and Wesnoth in general) as my spare time allows, as I am planning to get involved with Wesnoth development whether or not I'm accepted for SoC.<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=23837 2008-03-19T19:23:56Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/etc my username is dlr365.<br /> === Experience ===<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had. I'm very comfortable working in C++ and Java.<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game I had poked around in, complete with a graphical interface.<br /> * I have experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Window's GDI if anyone is interested)<br /> * I was heavily into creating custom Starcraft maps in highschool as well, so I have experience with commercial level editors.<br /> * I love strategy games, although I've only recently started playing Wesnoth.<br /> <br /> == GSoC Idea ==<br /> <br /> Rewrite the map editor, and add additional features that are requested by the community.<br /> <br /> === Details ===<br /> As I understand it, the current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner code and a possibly improved interface ((more research needed for the interface)). I would try to structure the code so that any further improvements would be relatively easy to implement as compared to the current code.<br /> <br /> === Further Ideas ===<br /> The map editor could be further extended by merging some scenerio/campaign-editing functionality into it (possibly through [[ExtensibleScenarioEditor|david hilton's GSoC proposal]]), which would be easier if the code were made cleaner.<br /> <br /> === Goal ===<br /> Over the summer I would aim to get a fully rewritten map editor running, adding as many extras as time allows. After the summer I would be very willing to continue working on the map editor as my spare time allows.<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=23836 2008-03-19T19:23:10Z

<p>Dlr365: </p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/etc my username is dlr365.<br /> === Experience ===<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had. I'm very comfortable working in C++ and Java.<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game I had poked around in, complete with a graphical interface.<br /> * I have experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Window's GDI if anyone is interested)<br /> * I was heavily into creating custom Starcraft maps in highschool as well, so I have experience with commercial level editors.<br /> * I love strategy games, although I've only recently started playing Wesnoth.<br /> <br /> == GSoC Idea ==<br /> <br /> Rewrite the map editor, and add additional features that are requested by the community.<br /> <br /> === Details ===<br /> As I understand it, the current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner code and a possibly improved interface ((more research needed for the interface)). I would try to structure the code so that any further improvements would be relatively easy to implement as compared to the current code.<br /> <br /> === Further Ideas ===<br /> The map editor could be further extended by merging some scenerio/campaign-editing functionality into it (see also: [[ExtensibleScenarioEditor|david hilton's GSoC proposal]]), which would be easier if the code were made cleaner.<br /> <br /> === Goal ===<br /> Over the summer I would aim to get a fully rewritten map editor running, adding as many extras as time allows. After the summer I would be very willing to continue working on the map editor as my spare time allows.<br /> <br /> [[Category:Summer of Code]]</div>

Dlr365 https://wiki.wesnoth.org/index.php?title=MapEditorRewrite&diff=23835 2008-03-19T19:22:50Z

<p>Dlr365: New page: == Personal == My name is Doug Rosvick, I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/etc my username is dlr365. === Experie...</p> <hr /> <div>== Personal ==<br /> My name is Doug Rosvick, I'm currently in my second year of Software Engineering at the University of Calgary (Canada). On IRC/forums/etc my username is dlr365.<br /> === Experience ===<br /> * I've been into programming as a hobby since 2001, before that I just poked around some QBasic programs on an old 286 my family had. I'm very comfortable working in C++ and Java.<br /> * Back in my QBasic days I extended a game called Hunt the Wumpus to support custom level files, and Nibbles to support up to 4 players simultaneously (it originally only allowed 2).<br /> * I created a few turn-based games on my TI-83 in high school, one of which was a conversion of an old QBasic game I had poked around in, complete with a graphical interface.<br /> * I have experience with SDL through a platformer/RTS concept that I've been working on the last few summers, although it hasn't gotten very far due to schoolwork and previous summer jobs that did not allow much free time. (I have a prototype VB6 version using Window's GDI if anyone is interested)<br /> * I was heavily into creating custom Starcraft maps in highschool as well, so I have experience with commercial level editors.<br /> * I love strategy games, although I've only recently started playing Wesnoth.<br /> <br /> == GSoC Idea ==<br /> <br /> Rewrite the map editor, and add additional features that are requested by the community.<br /> <br /> === Details ===<br /> As I understand it, the current map editor is sufficient, but the code is in a sorry state. I would rewrite the map editor so that it still performs its current functions, but with cleaner code and a possibly improved interface ((more research needed for the interface)). I would try to structure the code so that any further improvements would be relatively easy to implement as compared to the current code.<br /> <br /> === Further Ideas ===<br /> The map editor could be further extended by merging some scenerio/campaign-editing functionality into it (see also: [[ExtensibleScenarioEditor|david hilton's GSoC proposal]]), which would be easier if the code were made cleaner.<br /> <br /> === Goal ===<br /> Over the summer I would aim to get a fully rewritten map editor running, adding as many extras as time allows. After the summer I would be very willing to continue working on the map editor as my spare time allows.</div>

Dlr365