RandomCampaignGenerator - Revision history

Kthakore: /* Rough Project Timeline */

2008-03-21T00:11:49Z

‎Rough Project Timeline

2008-03-21T00:08:00Z

‎Project

2008-03-21T00:05:28Z

‎Overview

2008-03-20T17:25:53Z

‎Project

2008-03-20T17:24:40Z

‎Rough Project Timeline

2008-03-20T17:18:50Z

2008-03-20T17:12:04Z

2008-03-20T16:59:36Z

2008-03-20T16:38:46Z

2008-03-20T16:37:13Z

‎Development Model

← Older revision		Revision as of 00:11, 21 March 2008
Line 51:		Line 51:
	==Rough Project Timeline==		==Rough Project Timeline==

−	~~Summer~~ 08 - ~~Random Map Generator~~, and ~~start Strategy Balancer~~	+	March 31st - hammer out an algorithm for the PMG and start some prototypes. (Also some Doxygen patches will help realize the project)
		+
		+	April - I have finals so no coding for me :{
		+
		+	May 08 - Start first serious development iteration of the PMG, (the tests will be well discussed in IRC and the forums)
		+
		+	- Goals are to create a script parser for the maps
		+

−	~~Fall 08 - Startegy Balancer and start story writer~~

−	~~Winter 09 - Spring 09 - Story Writer and start world creator~~

−	~~More to Come~~

@@ Line 29: / Line 29: @@
 ==Project==
-I have selected this project myself after playing Wesnoth and other strategy games.
+I have selected this project myself after playing Wesnoth and other strategy games. The Project is two part first is the Procedural Map Generator and the second is random unit placement for strategy problems that the player can train on. This two combined will give a better random campaign generator for quick play, however this is not the focus of GCoS 2008.
 ===Scope===
-For the summer of 2008  I will be focusing on the Random Map Generator. The rest of the project will be continued after the GCoS well into 2009. The timeline is showed below.
+For the summer of 2008  I will be focusing on the Procedural Map Generator. The rest of the project will be continued after the GCoS well into 2009. The timeline is showed below.
 ==Overview==

@@ Line 35: / Line 35: @@
 ==Overview==
-I propose to flesh out a procedural world generator (PWG) that consists of generated characters, stories, timelines, and maps. PWG first plans to develop a random map generator using previous efforts. Next PWG will work on startegy balancing to create well balance battles. Finally PWG will create world of characters and stories that they can use to improve their skills, get ideas for writing campaigns, and allow users to experience different units. In the future PWG hopes, to provide players with a back drop world where then they can expand on to create new stories separate from the Wesnoth World.
+I propose to flesh out a procedural map generator (PMG) that consists of preset map generation and terrain strategy control. PWG first plans to improve the random map generator using previous efforts. PWG will provide writers with a simple scripting interface where they can specify features that will be required in the map. Moreover writers can decide who the map should favor in terms of terrain. The PWG will create points of interest beginning with the specifications, then inserting terrains that are favorable to some races then others, and then finally blending the terrains together to give the landscape a natural look.
 ==Development Model==

@@ Line 30: / Line 30: @@
 ==Project==
 I have selected this project myself after playing Wesnoth and other strategy games.
 ==Overview==

@@ Line 48: / Line 48: @@
 ==Rough Project Timeline==
-Summer 08 - Random Map Generator, and start Startegy Balancer
+Summer 08 - Random Map Generator, and start Strategy Balancer
 Fall 08 - Startegy Balancer and start story writer
 Winter 09 - Spring 09 - Story Writer and start world creator

@@ Line 5: / Line 5: @@
 forum: kthakore
 </pre>
-My preferred email address is thakore.kartik@gmail.com.
+My preferred email address is thakore.kartik|ATT|gmail.com.
 I am a software engineering student at the University of Western Ontario. I would like to participate in the Google Summer of Code, because I have had this idea in my head ever since I first started playing Strategy Games and want to see it realized. I am just taking advance of GSoC to get my self to start working on this project.

← Older revision	Revision as of 17:12, 20 March 2008
Line 46:	Line 46:


	+	==Rough Project Timeline==

	+	Summer 08 - Random Map Generator, and start Startegy Balancer
	+	Fall 08 - Startegy Balancer and start story writer
	+	Winter 09 - Spring 09 - Story Writer and start world creator

	+	More to Come

@@ Line 27: / Line 27: @@
 I believe the best development cycle with be iterative (spiral) model because it would ensure that the project will be well documented before design and development begin. Moreover it will reduce some of the time that would occur if the traditional waterfall model was used. Also I think a rigorous testing stage every iteration would be necessary to keep the project on track.
-Basic Development Model:
+===Basic Development Model:===
 - Design tests: this will ensure designs and code developed in this iteration are aimed and organized. The tests will also serve to refactor code by redesigning old tests.

← Older revision		Revision as of 16:37, 20 March 2008
Line 25:		Line 25:

	==Development Model==		==Development Model==
−	I believe the best development cycle with be iterative (spiral) model because it would ensure that the project will be well documented before design and development begin. Moreover it will reduce some of the time that would occur if the traditional waterfall model was used. ~~Moreover~~ I think a rigorous testing stage every iteration would be necessary to keep the project on track.	+	I believe the best development cycle with be iterative (spiral) model because it would ensure that the project will be well documented before design and development begin. Moreover it will reduce some of the time that would occur if the traditional waterfall model was used. Also I think a rigorous testing stage every iteration would be necessary to keep the project on track.
		+
		+	Basic Development Model:
		+
		+	- Design tests: this will ensure designs and code developed in this iteration are aimed and organized. The tests will also serve to refactor code by redesigning old tests.
		+
		+	- Develop to meet tests: This will keep development in scope and relevant
		+
		+	- Testing and update TODO lists
		+
		+
		+