User talk:Maikel - Revision history

Maikel: Blanked the page

2010-11-09T21:32:18Z

Blanked the page

← Older revision		Revision as of 21:32, 9 November 2010
Line 1:		Line 1:
	~~Test for Tutorial: Creating a parkour~~


	This tutorial provides a basis for scenario designers wanting to create a parkour. It explains the basics and some extended features of the parkour goal. Furthermore some elementary design issues for parkours will be addressed.

	~~== Parkour ==~~
	~~[[File:ParkourGoal.png\|thumb\|Parkour goal]]~~
	A parkour is basically an extended race, players have to get from start to finish but have to pass checkpoints in between. The parkour goal gives the scenario designer options to adjust the path, thereby increasing the challenge for the players. Other features would be creating team parkours, where team members need to split up and complete different paths to join forces later. On the player's side rounds get less frustrating since they would only have to redo parts of a parkour after having died, as you respawn at the latest passed checkpoint.

	~~== Scenario script ==~~
	The parkour goal can not be created through a Scenario.txt entry, since the checkpoints have to be created manually. Thus the obvious location to create the parkour goal is in the scenario script, an example of such a script is given here.

	~~/-- ''Parkour'' --/~~

	~~protected func Initialize()~~
	{
	~~// ''First create the goal and store it.''~~
	~~var goal = CreateObject(Goal_Parkour);~~

	~~// ''Place the start at the left of the map.''~~
	~~goal->SetStartpoint(50, LandscapeHeight() / 2);~~

	~~// ''Place some checkpoints from left to right at random height in between.''~~
	~~var cp_count = 10;~~
	~~for (var cp_num = 1; cp_num <= cp_count; cp_num++)~~
	{
	~~var x = cp_num * LandscapeWidth() / (cp_count + 1);~~
	~~var y = Random(LandscapeHeight());~~
	~~var cp_mode = PARKOUR_CP_Check \| PARKOUR_CP_Respawn \| PARKOUR_CP_Ordered;~~
	~~goal->AddCheckpoint(x, y, cp_mode);~~
	}

	~~// ''Place the finish at the right of the map.''~~
	~~goal->SetFinishPoint(LandscapeWidth() - 50, LandscapeHeight() / 2);~~

	~~return;~~
	}

	~~// ''Callback from parkour goal to the scenario script.''~~
	~~protected func PlrHasRespawned(int plr, object cp)~~
	{
	~~// ''Give the player a shovel when he respawns.''~~
	~~var clonk = GetCrew(plr);~~
	~~clonk->CreateContents(Shovel);~~
	}

	This of course cries for an explanation. First note that for a static map, i.e. those created from a Map.bmp, you can look for decent places for your checkpoints and create them. For dynamic maps you need to let a script search a decent location, in this example script we do not worry about such issues. So in the first line the parkour goal is created and stored in the variable <nowiki>goal</nowiki>, cause we need that later. The second line creates the parkour start, only create one start checkpoint. The function
	~~public func SetStartpoint(int x, int y)~~
	creates a start checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> and returns the checkpoint just created. After that 10 checkpoints are created ordered along the x direction at random height, for this the function
	~~public func AddCheckpoint(int x, int y, int mode)~~
	is used. This creates a checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> with the specified mode and returns the checkpoint just created. Checkpoint modes will be explained later, just note here that the checkpoints created in the example have to be passed in order and respawn the player at the latest passed checkpoint. In the last line the the parkour finish is created, also here only one finish should be created. The function
	~~public func SetFinishpoint(int x, int y)~~
	creates a finish checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> and returns the checkpoint just created. The parkour goal also provides a callback to the scenario script
	~~PlrHasRespawned(int plr, object cp)~~
	when the player is (re)spawned at a checkpoint. The player number and the checkpoint are passed as parameters. With this callback you can give the player necessary equipment to overcome the challenges provided.

	~~== Checkpoints ==~~

	~~A checkpoint can have various modes, these can be assigned using a bit mask. The different modes are~~
	* <nowiki>PARKOUR_CP_Start</nowiki>: Marks the start of a parkour, players spawn at this checkpoint. This mode is not compatible with other modes, and only one can be placed.
	* <nowiki>PARKOUR_CP_Finish</nowiki>: Marks the finish of a parkour. This mode is compatible with <nowiki>PARKOUR_CP_Team</nowiki> and only one can be placed.
	* <nowiki>PARKOUR_CP_Check</nowiki>: This mode has to be set for the basic checkpoint functionality, meaning that a player must have passed this in order to be able to finish the parkour.
	* <nowiki>PARKOUR_CP_Respawn</nowiki>: If this mode is set, the checkpoint will respawn players. The checkpoint at which will be respawned is the last checkpoint of this mode passed by the player or the start.
	* <nowiki>PARKOUR_CP_Ordered</nowiki>: This checkpoint has to be completed in logic order. If you have multiple ordered checkpoints, an ordered checkpoint can only be completed if the previous ordered checkpoint has been passed.
	* <nowiki>PARKOUR_CP_Team</nowiki>: Normally only one team member needs to pass a checkpoint. With this mode all team members must have passed this checkpoint.

	~~== Parkour Design ==~~

	~~=== Landscape ===~~
	~~When designing scenario's for clonk the designer has the choice between static and dynamic landscapes. This section will elaborate a bit on the influence of the landscape on a parkour.~~
	* Static landscape:
	* Dynamic landscape:



	~~Test for Tutorial: Creating a scenario~~

	~~Explain how to create a scenario.~~

Maikel at 18:13, 9 November 2010

2010-11-09T18:13:23Z

← Older revision		Revision as of 18:13, 9 November 2010
Line 5:		Line 5:

	== Parkour ==		== Parkour ==
	A parkour is basically an extended race, players have to get from start to finish but have to pass checkpoints in between. The parkour goal gives the scenario designer options to adjust the path, thereby increasing the challenge for the players. Other features would be creating team parkours, where ~~players~~ need to split up and complete different paths to join forces later. On the player's side rounds get less frustrating since ~~you~~ would only have to redo parts of a parkour after having died, as you respawn at the latest passed checkpoint.		[[File:ParkourGoal.png\|thumb\|Parkour goal]]
			A parkour is basically an extended race, players have to get from start to finish but have to pass checkpoints in between. The parkour goal gives the scenario designer options to adjust the path, thereby increasing the challenge for the players. Other features would be creating team parkours, where team members need to split up and complete different paths to join forces later. On the player's side rounds get less frustrating since they would only have to redo parts of a parkour after having died, as you respawn at the latest passed checkpoint.

	== Scenario script ==		== Scenario script ==
Line 64:		Line 65:
	* <nowiki>PARKOUR_CP_Team</nowiki>: Normally only one team member needs to pass a checkpoint. With this mode all team members must have passed this checkpoint.		* <nowiki>PARKOUR_CP_Team</nowiki>: Normally only one team member needs to pass a checkpoint. With this mode all team members must have passed this checkpoint.

	== Landscape ==		== Parkour Design ==

			=== Landscape ===
			When designing scenario's for clonk the designer has the choice between static and dynamic landscapes. This section will elaborate a bit on the influence of the landscape on a parkour.
			* Static landscape:
			* Dynamic landscape:

	~~Dynamic vs. static.~~

Maikel: /* Checkpoints */

2010-11-08T18:53:44Z

Checkpoints

← Older revision		Revision as of 18:53, 8 November 2010
Line 57:		Line 57:

	A checkpoint can have various modes, these can be assigned using a bit mask. The different modes are		A checkpoint can have various modes, these can be assigned using a bit mask. The different modes are
	* <nowiki>PARKOUR_CP_Start</nowiki>: Marks the start of a parkour, players spawn at this checkpoint. This mode is not ~~compitable~~ with other modes, and only one can be placed.		* <nowiki>PARKOUR_CP_Start</nowiki>: Marks the start of a parkour, players spawn at this checkpoint. This mode is not compatible with other modes, and only one can be placed.
	* <nowiki>PARKOUR_CP_Finish</nowiki>		* <nowiki>PARKOUR_CP_Finish</nowiki>: Marks the finish of a parkour. This mode is compatible with <nowiki>PARKOUR_CP_Team</nowiki> and only one can be placed.
	* <nowiki>PARKOUR_CP_Check</nowiki>		* <nowiki>PARKOUR_CP_Check</nowiki>: This mode has to be set for the basic checkpoint functionality, meaning that a player must have passed this in order to be able to finish the parkour.
	* <nowiki>PARKOUR_CP_Respawn</nowiki>		* <nowiki>PARKOUR_CP_Respawn</nowiki>: If this mode is set, the checkpoint will respawn players. The checkpoint at which will be respawned is the last checkpoint of this mode passed by the player or the start.
	* <nowiki>PARKOUR_CP_Ordered</nowiki>		* <nowiki>PARKOUR_CP_Ordered</nowiki>: This checkpoint has to be completed in logic order. If you have multiple ordered checkpoints, an ordered checkpoint can only be completed if the previous ordered checkpoint has been passed.
	* <nowiki>PARKOUR_CP_Team</nowiki>		* <nowiki>PARKOUR_CP_Team</nowiki>: Normally only one team member needs to pass a checkpoint. With this mode all team members must have passed this checkpoint.

	== Landscape ==		== Landscape ==

Maikel at 18:31, 8 November 2010

2010-11-08T18:31:48Z

← Older revision		Revision as of 18:31, 8 November 2010
Line 57:		Line 57:

	A checkpoint can have various modes, these can be assigned using a bit mask. The different modes are		A checkpoint can have various modes, these can be assigned using a bit mask. The different modes are
	PARKOUR_CP_Start		* <nowiki>PARKOUR_CP_Start</nowiki>: Marks the start of a parkour, players spawn at this checkpoint. This mode is not compitable with other modes, and only one can be placed.
	PARKOUR_CP_Finish		* <nowiki>PARKOUR_CP_Finish</nowiki>
	PARKOUR_CP_Check		* <nowiki>PARKOUR_CP_Check</nowiki>
	PARKOUR_CP_Respawn		* <nowiki>PARKOUR_CP_Respawn</nowiki>
	PARKOUR_CP_Ordered		* <nowiki>PARKOUR_CP_Ordered</nowiki>
	PARKOUR_CP_Team		* <nowiki>PARKOUR_CP_Team</nowiki>

	== Landscape ==		== Landscape ==

	Dynamic vs. static.		Dynamic vs. static.


			Test for Tutorial: Creating a scenario

			Explain how to create a scenario.

Maikel: /* Scenario script */

2010-11-08T16:18:48Z

Scenario script

← Older revision		Revision as of 16:18, 8 November 2010
Line 44:		Line 44:
	}		}

	This of course cries for an explanation. First note that for a static map, i.e. those created from a Map.bmp, you can look for decent places for your checkpoints and create them. For dynamic maps you need to let a script search a decent location, in this example script we do not worry about such issues. So in the first line the parkour goal is created and stored in <nowiki>goal</nowiki>, cause we need that later. The second line creates the parkour start, only create one start checkpoint. The function		This of course cries for an explanation. First note that for a static map, i.e. those created from a Map.bmp, you can look for decent places for your checkpoints and create them. For dynamic maps you need to let a script search a decent location, in this example script we do not worry about such issues. So in the first line the parkour goal is created and stored in the variable <nowiki>goal</nowiki>, cause we need that later. The second line creates the parkour start, only create one start checkpoint. The function
	public func SetStartpoint(int x, int y)		public func SetStartpoint(int x, int y)
	creates a start checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> and returns the checkpoint just created. After that 10 checkpoints are created ordered along the x direction at random height, for this the function		creates a start checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> and returns the checkpoint just created. After that 10 checkpoints are created ordered along the x direction at random height, for this the function

Maikel: /* Scenario script */

2010-11-02T17:55:50Z

Scenario script

← Older revision		Revision as of 17:55, 2 November 2010
Line 10:		Line 10:
	The parkour goal can not be created through a Scenario.txt entry, since the checkpoints have to be created manually. Thus the obvious location to create the parkour goal is in the scenario script, an example of such a script is given here.		The parkour goal can not be created through a Scenario.txt entry, since the checkpoints have to be created manually. Thus the obvious location to create the parkour goal is in the scenario script, an example of such a script is given here.

			/-- ''Parkour'' --/

	protected func Initialize()		protected func Initialize()
	{		{
Line 32:		Line 34:

	return;		return;
			}

			// ''Callback from parkour goal to the scenario script.''
			protected func PlrHasRespawned(int plr, object cp)
			{
			// ''Give the player a shovel when he respawns.''
			var clonk = GetCrew(plr);
			clonk->CreateContents(Shovel);
	}		}

Line 38:		Line 48:
	creates a start checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> and returns the checkpoint just created. After that 10 checkpoints are created ordered along the x direction at random height, for this the function		creates a start checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> and returns the checkpoint just created. After that 10 checkpoints are created ordered along the x direction at random height, for this the function
	public func AddCheckpoint(int x, int y, int mode)		public func AddCheckpoint(int x, int y, int mode)
	is used. This creates a checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> with the specified mode and returns the checkpoint just created. Checkpoint modes will be explained later, just note here that the checkpoints created in the example have to be passed in order and respawn the player at the latest passed checkpoint. In the last line the the parkour finish is created, also here only one finish should be created.		is used. This creates a checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> with the specified mode and returns the checkpoint just created. Checkpoint modes will be explained later, just note here that the checkpoints created in the example have to be passed in order and respawn the player at the latest passed checkpoint. In the last line the the parkour finish is created, also here only one finish should be created. The function
			public func SetFinishpoint(int x, int y)
			creates a finish checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> and returns the checkpoint just created. The parkour goal also provides a callback to the scenario script
			PlrHasRespawned(int plr, object cp)
			when the player is (re)spawned at a checkpoint. The player number and the checkpoint are passed as parameters. With this callback you can give the player necessary equipment to overcome the challenges provided.

	== Checkpoints ==		== Checkpoints ==

Maikel: /* Scenario script */

2010-11-02T17:17:00Z

Scenario script

← Older revision		Revision as of 17:17, 2 November 2010
Line 22:		Line 22:
	for (var cp_num = 1; cp_num <= cp_count; cp_num++)		for (var cp_num = 1; cp_num <= cp_count; cp_num++)
	{		{
	var x = cp_num * LandscapeWidth() / cp_count;		var x = cp_num * LandscapeWidth() / (cp_count + 1);
	var y = Random(LandscapeHeight());		var y = Random(LandscapeHeight());
	var cp_mode = PARKOUR_CP_Check \| PARKOUR_CP_Respawn \| PARKOUR_CP_Ordered;		var cp_mode = PARKOUR_CP_Check \| PARKOUR_CP_Respawn \| PARKOUR_CP_Ordered;
Line 34:		Line 34:
	}		}

	This of course cries for an explanation.		This of course cries for an explanation. First note that for a static map, i.e. those created from a Map.bmp, you can look for decent places for your checkpoints and create them. For dynamic maps you need to let a script search a decent location, in this example script we do not worry about such issues. So in the first line the parkour goal is created and stored in <nowiki>goal</nowiki>, cause we need that later. The second line creates the parkour start, only create one start checkpoint. The function
			public func SetStartpoint(int x, int y)
			creates a start checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> and returns the checkpoint just created. After that 10 checkpoints are created ordered along the x direction at random height, for this the function
			public func AddCheckpoint(int x, int y, int mode)
			is used. This creates a checkpoint at the global coordinates <nowiki>x</nowiki> and <nowiki>y</nowiki> with the specified mode and returns the checkpoint just created. Checkpoint modes will be explained later, just note here that the checkpoints created in the example have to be passed in order and respawn the player at the latest passed checkpoint. In the last line the the parkour finish is created, also here only one finish should be created.

	== Checkpoints ==		== Checkpoints ==

Maikel: /* Parkour */

2010-11-02T16:28:59Z

Parkour

← Older revision		Revision as of 16:28, 2 November 2010
Line 5:		Line 5:

	== Parkour ==		== Parkour ==
	A parkour is basically an extended race, players have to get from start to finish but have to pass checkpoints in between. The parkour goal gives the scenario designer options to adjust the path, thereby increasing the challenge for the players. Other features would be creating team parkours, where players need to split up and complete different paths to join forces later. On the player's side rounds get less frustrating since you would only have to redo parts of a parkour, as you respawn at the latest passed checkpoint.		A parkour is basically an extended race, players have to get from start to finish but have to pass checkpoints in between. The parkour goal gives the scenario designer options to adjust the path, thereby increasing the challenge for the players. Other features would be creating team parkours, where players need to split up and complete different paths to join forces later. On the player's side rounds get less frustrating since you would only have to redo parts of a parkour after having died, as you respawn at the latest passed checkpoint.

	== Scenario script ==		== Scenario script ==

Maikel at 16:25, 2 November 2010

2010-11-02T16:25:48Z

@@ Line 1: / Line 1: @@
 Test for Tutorial: Creating a parkour
 == Scenario script ==
+The parkour goal can not be created through a Scenario.txt entry, since the checkpoints have to be created manually. Thus the obvious location to create the parkour goal is in the scenario script, an example of such a script is given here.
   protected func Initialize()
+  {
-  	var goal = CreateObject(Goal_Parkour);
+ 	// ''First create the goal and store it.''
    	return;
+  }
 == Landscape ==
 Dynamic vs. static.

Maikel at 14:10, 2 November 2010

2010-11-02T14:10:31Z

← Older revision		Revision as of 14:10, 2 November 2010
Line 1:		Line 1:
	Test for Tutorial: Creating a parkour		Test for Tutorial: Creating a parkour

	=== Scenario ~~script~~ ===		== Scenario script ==

			The parkour goal can not be created through a Scenario.txt entry, since the checkpoints have to be created manually.

			protected func Initialize()
			{
			var goal = CreateObject(Goal_Parkour);

			return;
			}


			== Landscape ==

			Dynamic vs. static.

			=== Example ===