Clock-Triggered Game Events - Revision history

Grayman: /* Starting the Clock at Mission Start */

2018-10-16T14:17:13Z

Starting the Clock at Mission Start

← Older revision		Revision as of 14:17, 16 October 2018
Line 87:		Line 87:
	* If you have any other function calls in 'main' you should consider and test placement; I put one below the clock line and it failed to work yet above the clock line both worked synchronistically. Another option is to start the clock or any other function during the mission (even if immediately) see next section.		* If you have any other function calls in 'main' you should consider and test placement; I put one below the clock line and it failed to work yet above the clock line both worked synchronistically. Another option is to start the clock or any other function during the mission (even if immediately) see next section.

	NOTE: The reason for the failure is that, as described, the runClock() routine will run endlessly, never returning to the main() routine so it can run further things.		NOTE: (by grayman) The reason for the failure is that, as described, the runClock() routine will run endlessly, never returning to the main() routine so it can run further things.

	The correct way to do this is to change the following line in the main() routine:		The correct way to do this is to change the following line in the main() routine:

2018-10-16T14:15:29Z

Starting the Clock at Mission Start

← Older revision		Revision as of 14:15, 16 October 2018
Line 87:		Line 87:
	* If you have any other function calls in 'main' you should consider and test placement; I put one below the clock line and it failed to work yet above the clock line both worked synchronistically. Another option is to start the clock or any other function during the mission (even if immediately) see next section.		* If you have any other function calls in 'main' you should consider and test placement; I put one below the clock line and it failed to work yet above the clock line both worked synchronistically. Another option is to start the clock or any other function during the mission (even if immediately) see next section.

			NOTE: The reason for the failure is that, as described, the runClock() routine will run endlessly, never returning to the main() routine so it can run further things.

			The correct way to do this is to change the following line in the main() routine:

			thread runClock($clock_hand_big, $clock_hand_small);

			Now runClock will execute in its own thread, and control will return to the main() routine for it to do further work.

	== Starting the Clock during the Mission ==		== Starting the Clock during the Mission ==

2008-12-17T11:13:18Z

Timed Objectives and Mission Fail 'Out of Time'

← Older revision		Revision as of 11:13, 17 December 2008
Line 150:		Line 150:
	* Change the mins and hours values to the time you want the mission to end.		* Change the mins and hours values to the time you want the mission to end.

	~~{{editing-scripting}}~~		[[Category:Editing]]
			[[Category:Scripting]]

2008-12-17T11:07:47Z

Timed Objectives and Mission Fail 'Out of Time'

← Older revision		Revision as of 11:07, 17 December 2008
Line 141:		Line 141:
	If you want to set up a timed objective, eg, "Escape the dungeon before your execution at 3:00am" or "Survive within the crypt until 3:00am" then:		If you want to set up a timed objective, eg, "Escape the dungeon before your execution at 3:00am" or "Survive within the crypt until 3:00am" then:

	* Set up the objective as a custom objective (see [[Objectives Editor]].		* Set up the objective as a custom objective (see [[Objectives Editor]].)
	* Create a target_tdm_setobjectivestate.		* Create a target_tdm_setobjectivestate.
	* Give it a name, eg, TimeObjective		* Give it a name, eg, TimeObjective

2008-12-17T11:06:42Z

Triggering Entities on Time

← Older revision		Revision as of 11:06, 17 December 2008
Line 128:		Line 128:
	To trigger an entity refer to these lines in the runClock script...		To trigger an entity refer to these lines in the runClock script...

	if (mins == 99 && hours == 99) ~~// set hours & mins to trigger any entity~~		if (mins == 99 && hours == 99)
	{		{
	$yourEntity.activate($player1); ~~//replace 'yourEntity' with any entity to be triggered~~		$yourEntity.activate($player1);
	}		}

	* Change the mins and hours values to the time you want the trigger.		* Change the mins and hours values to the time you want the trigger.

2008-12-17T11:00:41Z

How to Set Up the Script & Clock

← Older revision		Revision as of 11:00, 17 December 2008
Line 70:		Line 70:

	* Import one of the clock prefabs (see [[Prefab Comments]] or make your own.		* Import one of the clock prefabs (see [[Prefab Comments]] or make your own.
	* ~~First~~ position and turn the entire clock prefab to face the way you want it in-game. (Dark Radiant's 'rotate models independently' button should be UNset.		* Firstly, position and turn the entire clock prefab to face the way you want it in-game. (Dark Radiant's 'rotate models independently' button should be UNset.
	* Rotate the clock hands around the clockface to the same time as you set in the script above.		* Rotate the clock hands around the clockface to the same time as you set in the script above.
	* The clock is now ready to keep and show time in your Dark Mod mission (without special events or striking the hours yet.)		* The clock is now ready to keep and show time in your Dark Mod mission (without special events or striking the hours yet.)

2008-12-17T11:00:14Z

How to Set Up the Script & Clock

← Older revision		Revision as of 11:00, 17 December 2008
Line 66:		Line 66:
	* If you already have a script file for your map then paste the runClock script into it or....		* If you already have a script file for your map then paste the runClock script into it or....
	* If you haven't already got a script file then paste it into your plain text editor and save it in the same folder as your map with the same name but suffix .script. Example :<br>mymapname.map<br>mymapname.script		* If you haven't already got a script file then paste it into your plain text editor and save it in the same folder as your map with the same name but suffix .script. Example :<br>mymapname.map<br>mymapname.script
	* Edit the lines float hours, float mins, float secs values to the time you want to start.		* Edit the lines float hours, float mins, float secs values to the time you want the clock to show at the start.
	* Resave the file.		* Resave the file.

Line 73:		Line 73:
	* Rotate the clock hands around the clockface to the same time as you set in the script above.		* Rotate the clock hands around the clockface to the same time as you set in the script above.
	* The clock is now ready to keep and show time in your Dark Mod mission (without special events or striking the hours yet.)		* The clock is now ready to keep and show time in your Dark Mod mission (without special events or striking the hours yet.)


	== Starting the Clock at Mission Start ==		== Starting the Clock at Mission Start ==

2008-12-17T10:57:40Z

2008-12-17T10:55:00Z

New page: placeholder

New page

placeholder