Objectives, triggering - Revision history

Obsttorte at 14:19, 11 June 2017

2017-06-11T14:19:07Z

← Older revision		Revision as of 14:19, 11 June 2017
Line 1:		Line 1:
			[[Category:Editing]]
	== Description ==		== Description ==

RJFerret: /* Basics */ wikilink Triggers

2014-03-03T04:11:49Z

Basics: wikilink Triggers

← Older revision		Revision as of 04:11, 3 March 2014
Line 6:		Line 6:
	== Basics ==		== Basics ==

	The first thing to understand is what the objectives editor (OE) offers. There are four fields in the OE that are interesting here. They are the '''success/failure target/script''' fields. These are the targets triggered or the script functions called when an objective succeeds or fails. Normally you won't use them very often, but they are quite useful.		The first thing to understand is what the objectives editor (OE) offers. There are four fields in the OE that are interesting here. They are the '''success/failure target/script''' fields. These are the targets [[Triggers\|triggered]] or the script functions called when an objective succeeds or fails. Normally you won't use them very often, but they are quite useful.

	== Example: Let an object appear when an objective is completed ==		== Example: Let an object appear when an objective is completed ==

Obsttorte: /* Making things more complex */

2013-01-12T00:02:09Z

Making things more complex

← Older revision		Revision as of 00:02, 12 January 2013
Line 31:		Line 31:
	Once an objective is complete, it will trigger the ''trigger_count'' entity. That entity's counter goes up by 1 and gets compared with the spawnarg "count". Once the count reaches N, it will trigger the ''target_callscriptfunction'', which then calls the script function to let the object appear in-game.		Once an objective is complete, it will trigger the ''trigger_count'' entity. That entity's counter goes up by 1 and gets compared with the spawnarg "count". Once the count reaches N, it will trigger the ''target_callscriptfunction'', which then calls the script function to let the object appear in-game.

	''Hint: As all the '''success script''' fields are empty, the function is '''NOT''' called by any objective directly. This is done by the target.''		''Hint: As all the '''success script''' fields are empty, the function is '''NOT''' called by any objective directly. This is done by the target entity.''

	--[[User:Obsttorte\|Obsttorte]] ([[User talk:Obsttorte\|talk]]) 08:41, 2 January 2013 (EST)		--[[User:Obsttorte\|Obsttorte]] ([[User talk:Obsttorte\|talk]]) 08:41, 2 January 2013 (EST)

Obsttorte: /* Making things more complex */

2013-01-12T00:01:55Z

Making things more complex

← Older revision		Revision as of 00:01, 12 January 2013
Line 31:		Line 31:
	Once an objective is complete, it will trigger the ''trigger_count'' entity. That entity's counter goes up by 1 and gets compared with the spawnarg "count". Once the count reaches N, it will trigger the ''target_callscriptfunction'', which then calls the script function to let the object appear in-game.		Once an objective is complete, it will trigger the ''trigger_count'' entity. That entity's counter goes up by 1 and gets compared with the spawnarg "count". Once the count reaches N, it will trigger the ''target_callscriptfunction'', which then calls the script function to let the object appear in-game.

	''Hint: As all the '''success script''' fields are empty, the function is '''NOT''' called by any objective directly.''		''Hint: As all the '''success script''' fields are empty, the function is '''NOT''' called by any objective directly. This is done by the target.''

	--[[User:Obsttorte\|Obsttorte]] ([[User talk:Obsttorte\|talk]]) 08:41, 2 January 2013 (EST)		--[[User:Obsttorte\|Obsttorte]] ([[User talk:Obsttorte\|talk]]) 08:41, 2 January 2013 (EST)

Obsttorte: /* Making things more complex */

2013-01-12T00:01:01Z

Making things more complex

← Older revision		Revision as of 00:01, 12 January 2013
Line 31:		Line 31:
	Once an objective is complete, it will trigger the ''trigger_count'' entity. That entity's counter goes up by 1 and gets compared with the spawnarg "count". Once the count reaches N, it will trigger the ''target_callscriptfunction'', which then calls the script function to let the object appear in-game.		Once an objective is complete, it will trigger the ''trigger_count'' entity. That entity's counter goes up by 1 and gets compared with the spawnarg "count". Once the count reaches N, it will trigger the ''target_callscriptfunction'', which then calls the script function to let the object appear in-game.

	''Hint: If all the '''success script''' fields are empty, the function is '''NOT''' called by any objective directly.''		''Hint: As all the '''success script''' fields are empty, the function is '''NOT''' called by any objective directly.''

	--[[User:Obsttorte\|Obsttorte]] ([[User talk:Obsttorte\|talk]]) 08:41, 2 January 2013 (EST)		--[[User:Obsttorte\|Obsttorte]] ([[User talk:Obsttorte\|talk]]) 08:41, 2 January 2013 (EST)

Grayman: /* Making things more complex */

2013-01-02T19:20:36Z

Making things more complex

← Older revision		Revision as of 19:20, 2 January 2013
Line 25:		Line 25:
	== Making things more complex ==		== Making things more complex ==

	Of course you can use a more complex setup if needed. Let's assume you want the object to appear after a certain number of objectives have been completed. To achieve this, create ''trigger_count'' and ''target_callscriptfunction'' entities. Fill the '''success target''' fields of all the possible or required objectives with the name of the ''trigger_count'' entity. On this entity set the spawnarg "count" "N", where N is the number of objectives that must be completed and let it target the ''target_callscriptfunction'' entity. On the latter, set the spawnarg "call" "showObject". That's it.		Of course, you can use a more complex setup if needed. Let's assume you want the object to appear after a certain number of objectives have been completed. To achieve this, create ''trigger_count'' and ''target_callscriptfunction'' entities. Fill the '''success target''' fields of all the possible or required objectives with the name of the ''trigger_count'' entity. On this entity set the spawnarg "count" "N", where N is the number of objectives that must be completed and let it target the ''target_callscriptfunction'' entity. On the latter, set the spawnarg "call" "showObject". That's it.

	How does it work?		How does it work?

Grayman: /* Making things more complex */

2013-01-02T19:20:21Z

Making things more complex

← Older revision		Revision as of 19:20, 2 January 2013
Line 25:		Line 25:
	== Making things more complex ==		== Making things more complex ==

	Of course you can use a more complex setup if needed. Let's assume you want the object to appear after a certain ~~amount~~ of objectives ~~has~~ been completed. To achieve this, create a ''trigger_count'' and a ''target_callscriptfunction'' ~~entity~~. Fill the '''success target''' ~~field~~ of all the possible or required objectives with the name of the ''trigger_count''. On this entity set the spawnarg "count" "N", where N is the number of objectives that must be completed and let it target the ''target_callscriptfunction'' entity. On the latter, set the spawnarg "call" "showObject". That's it.		Of course you can use a more complex setup if needed. Let's assume you want the object to appear after a certain number of objectives have been completed. To achieve this, create ''trigger_count'' and ''target_callscriptfunction'' entities. Fill the '''success target''' fields of all the possible or required objectives with the name of the ''trigger_count'' entity. On this entity set the spawnarg "count" "N", where N is the number of objectives that must be completed and let it target the ''target_callscriptfunction'' entity. On the latter, set the spawnarg "call" "showObject". That's it.

	How does it work?		How does it work?

	Once an objective is complete, it will trigger the ''trigger_count'' entity. ~~The~~ counter goes up and gets compared with the spawnarg "count". Once it reaches ~~this~~, it will trigger the ''target_callscriptfunction'', which ~~than~~ calls the function to let the object appear in-game.		Once an objective is complete, it will trigger the ''trigger_count'' entity. That entity's counter goes up by 1 and gets compared with the spawnarg "count". Once the count reaches N, it will trigger the ''target_callscriptfunction'', which then calls the script function to let the object appear in-game.

	''Hint: ~~All~~ the '''success script''' fields ~~stay~~ empty, the function is '''NOT''' called by any objective directly''		''Hint: If all the '''success script''' fields are empty, the function is '''NOT''' called by any objective directly.''

	--[[User:Obsttorte\|Obsttorte]] ([[User talk:Obsttorte\|talk]]) 08:41, 2 January 2013 (EST)		--[[User:Obsttorte\|Obsttorte]] ([[User talk:Obsttorte\|talk]]) 08:41, 2 January 2013 (EST)

Grayman: /* Example: Let an object appear when an objective is completed */

2013-01-02T19:16:05Z

Example: Let an object appear when an objective is completed

← Older revision		Revision as of 19:16, 2 January 2013
Line 10:		Line 10:
	== Example: Let an object appear when an objective is completed ==		== Example: Let an object appear when an objective is completed ==

	The first thing you have to do is to set up the object you want to appear once the player has finished an objective. ~~After you~~'~~ve done so, set its~~ name to ''object''~~, than~~ go to the specific objective in the OE, and ~~typ~~ in the '''success script''' field ''showObject''.		The first thing you have to do is to set up the object you want to appear once the player has finished an objective. For our example, we'll give it the name ''object''. Then go to the specific objective in the OE, and type in the '''success script''' field ''showObject''. This will be the name of a script function.

	Now create a script file in your maps folder called ''mymapname''.script, where ''mymapname~~.map~~'' is the name of your map. Type in the following code:		Now create a script file in your maps folder called ''mymapname''.script, where ''mymapname'' is the name of your map. Type in the following code:

	void showObject() {		void showObject() {
Line 21:		Line 21:
	}		}

	That's it. The ''main'' method is called upon map start and ~~let~~ the object ~~dissapear~~ from game. When your desired objective is completed, the method ''showObject'' is called, ~~what let~~ the object appear again.		That's it. The ''main'' method is called upon map start and causes the object to disappear from the game. It's not really gone; it's just hidden. When your desired objective is completed, the method ''showObject'' is called, which causes the object to appear again.

	== Making things more complex ==		== Making things more complex ==

Grayman: /* Basics */

2013-01-02T19:13:01Z

Basics

← Older revision		Revision as of 19:13, 2 January 2013
Line 6:		Line 6:
	== Basics ==		== Basics ==

	The first thing to ~~know~~ is what ~~possibilities you get with~~ the objectives editor (OE). There are four fields in ~~there~~ that are interesting here. They are the '''success/failure target/script''' fields. These are the targets ~~that get~~ triggered or the script functions ~~that get~~ called~~, once the~~ objective ~~was successful~~ or ~~failed~~. Normally you ~~wont~~ use them very often~~, if even~~, but they are ~~quiete~~ useful.		The first thing to understand is what the objectives editor (OE) offers. There are four fields in the OE that are interesting here. They are the '''success/failure target/script''' fields. These are the targets triggered or the script functions called when an objective succeeds or fails. Normally you won't use them very often, but they are quite useful.

	== Example: Let an object appear when an objective is completed ==		== Example: Let an object appear when an objective is completed ==

Grayman: /* Description */

2013-01-02T19:10:31Z

Description

← Older revision		Revision as of 19:10, 2 January 2013
Line 2:		Line 2:
	== Description ==		== Description ==

	Sometimes a map requires it, ~~that~~ after the completion of one or more objectives something in the map changes. The example I'll use here is the ~~appearing~~ of an entity~~/model~~ in the map. ~~Anyway, this~~ method can be used for other things, too.		Sometimes a map requires that, after the completion of one or more objectives, something in the map changes. The example I'll use here is the appearance of an entity in the map. This method can be used for other things, too.

	== Basics ==		== Basics ==