Difficulty Levels - Revision history

Geep: Add small section "Determining the Current Level From a Script"

2021-01-08T22:31:29Z

Add small section "Determining the Current Level From a Script"

← Older revision		Revision as of 22:31, 8 January 2021
Line 115:		Line 115:
	tdm_difficulty 2		tdm_difficulty 2
	in the console before starting the map and it will always be using this level. Set the CVAR back to -1 (default) to disable the override. This setting is not saved between sessions to prevent it from unintentionally overriding your settings.		in the console before starting the map and it will always be using this level. Set the CVAR back to -1 (default) to disable the override. This setting is not saved between sessions to prevent it from unintentionally overriding your settings.

			==Determining the Current Level From a Script==
			Function getDifficultyLevel returns a float of 0, 1, or 2, e.g.:
			if(sys.getDifficultyLevel() == 2)
			{...}

	==An Example==		==An Example==

2020-03-13T22:16:33Z

Added Example section link to a video demonstrating techniques

← Older revision		Revision as of 22:16, 13 March 2020
Line 115:		Line 115:
	tdm_difficulty 2		tdm_difficulty 2
	in the console before starting the map and it will always be using this level. Set the CVAR back to -1 (default) to disable the override. This setting is not saved between sessions to prevent it from unintentionally overriding your settings.		in the console before starting the map and it will always be using this level. Set the CVAR back to -1 (default) to disable the override. This setting is not saved between sessions to prevent it from unintentionally overriding your settings.

			==An Example==

			A number of these techniques are shown in [https://www.youtube.com/watch?v=Lg2NCpyN4rw Springheel's Speed Build Challenge - Part 8], starting in the video's second half, around 14:25. This includes the difficulty-dependent variation of:
			* AI paths
			* radius of a torch, and range and angles of lights
			* whether AI will relight an extinguished flame
			* overall lightgem level (using the Difficulty Editor), to affect the ability of AI to see the player throughout the game.


	{{tutorial-editing}} {{darkradiant}}		{{tutorial-editing}} {{darkradiant}}

2013-11-08T00:31:26Z

Changing the Difficulty Level Names

← Older revision		Revision as of 00:31, 8 November 2013
Line 95:		Line 95:
	* Select any worldspawn brush or patch		* Select any worldspawn brush or patch
	* Add the following properties and values:		* Add the following properties and values:
	** ~~diff0default~~ Extra Clues		** difficulty0Name Extra Clues
	** ~~diff1default~~ Warrior		** difficulty1Name Warrior
	** ~~diff2default~~ Stealthy		** difficulty2Name Stealthy

	Other suggested styles :"Assassin", "Ninja", "Key Hunt" and so on.		Other suggested styles :"Assassin", "Ninja", "Key Hunt" and so on.

2011-07-03T21:22:37Z

← Older revision		Revision as of 21:22, 3 July 2011
Line 85:		Line 85:
	"diff_1_arg_1" "+8"		"diff_1_arg_1" "+8"
	The above two spawnargs will be activated on difficulty level 1 (Hard) and will set the CVARs '''tdm_player_default_health''' to '''40''' and increase '''tdm_player_default_height''' by 8.		The above two spawnargs will be activated on difficulty level 1 (Hard) and will set the CVARs '''tdm_player_default_health''' to '''40''' and increase '''tdm_player_default_height''' by 8.

			== Changing Global Variables ==

			You can change cvars across the entire map (for example, all AI HP, rather than just one) easily. See [[Difficulty Editor]] for more info.

	==Changing the Difficulty Level Names==		==Changing the Difficulty Level Names==

2010-12-19T15:35:24Z

Excluding & Restricting Entities from/to Difficulty Levels

← Older revision		Revision as of 15:35, 19 December 2010
Line 1:		Line 1:
			==General information==

			You can change what is in your FM and the way it plays on the different difficulty levels.

			It is highly recommended that you do not use these methods to exclude entire sections or interesting features unless you declare this somewhere in the objectives text or in the readme. It's also a good idea to declare if the player will ''not'' miss anything whichever difficulty setting he/she chooses.


	==Excluding & Restricting Entities from/to Difficulty Levels==		==Excluding & Restricting Entities from/to Difficulty Levels==

2010-10-27T20:07:19Z

Placing Entities at Different Locations on Different Difficulty Settings

← Older revision		Revision as of 20:07, 27 October 2010
Line 31:		Line 31:
	... where N is the difficulty 0, 1, or 2		... where N is the difficulty 0, 1, or 2

			(note that the number "x" in "change_x" must correspond to the "arg_x" value in the example above)

2010-10-27T20:04:31Z

Placing Entities at Different Locations on Different Difficulty Settings

2010-10-27T20:03:33Z

Placing Entities at Different Locations on Different Difficulty Settings

2010-10-27T19:42:47Z

Placing Entities at Different Locations on Different Difficulty Settings

2009-05-06T20:31:47Z

Changing Properties on Entity Instances based on Difficulty Settings

← Older revision		Revision as of 20:31, 6 May 2009
Line 54:		Line 54:

	The properties of individual entities can be controlled with difficulty level in this manner, in contrast to the Difficulty Editor, which changes classes instead of instances.		The properties of individual entities can be controlled with difficulty level in this manner, in contrast to the Difficulty Editor, which changes classes instead of instances.

			== Relative Changes ==
			You can either assign new values to spawnargs (like the "angle" "90" example above) or change spawnargs relatively to the existing values. Both additive and multiplicative changes are possible:

			Add 45 degrees to the "angle" property like this:
			"diff_1_change_0" "angle"
			"diff_1_arg_0" "+45"
			Double the "health" property with this:
			"diff_1_change_0" "health"
			"diff_1_arg_0" "*2"
			The important part is to use the asterisk *, plus + or minus - sign to indicate relative changes.

	== Changing CVARs ==		== Changing CVARs ==