AI stats - Revision history

Frost Salamander: /* Stealth Combat */

2024-01-30T20:23:47Z

Stealth Combat

← Older revision		Revision as of 20:23, 30 January 2024
Line 129:		Line 129:
	\|-		\|-
	\|canclosedoors		\|canclosedoors
	\|AI ability to close doors. canoperatedoors must be ~~set~~ for this to work. Added in TDM 2.12.		\|AI ability to close doors. canoperatedoors must be enabled for this to work. Added in TDM 2.12.
	\|-		\|-
	\|canoperateelevators		\|canoperateelevators

Frost Salamander: add canclosedoors spawnarg

2024-01-30T20:18:53Z

add canclosedoors spawnarg

← Older revision		Revision as of 20:18, 30 January 2024
Line 127:		Line 127:
	\|canoperatedoors		\|canoperatedoors
	\|AI ability to handle doors		\|AI ability to handle doors
			\|-
			\|canclosedoors
			\|AI ability to close doors. canoperatedoors must be set for this to work. Added in TDM 2.12.
	\|-		\|-
	\|canoperateelevators		\|canoperateelevators
Line 198:		Line 201:
	\|-		\|-
	\|}		\|}

	=== Open Combat ===		=== Open Combat ===
	When stealth fails, the player always has the option to openly fight AIs instead of fleeing. However, combat in TDM is meant as a last resort and will ruin any stealth scores and will most likely kill you, when you face more than one guard. Also, common settings prohibit killing civilians (AI with the spawnarg "is_civilian" set to 1) and even guards on higher difficulties. The difficulty of a melee fight is influenced by three factors (not counting the player's skills): The combat difficulty setting in the menu (which can be set by the player), the melee skills of the AI (novice, trained, skilled, see Melee sets, are usually set for specific AI, but can be changed by the map author), and the difficulty setting of the current map (also chosen by the player). For a more detailed description on what to keep in mind while fighting, see [[The Dark Mod Gameplay#Combat\|Combat]]. A hit by the player will deal damage. The damage reduces the amount of health of the AI by the base damage, scaled by the "damage_scale" of the zone hit. When the dealt damage surpasses the pain_threshold, the pain animation of the AI will be played. As soon as the health of the AI reaches the health_critical value, the AI will flee. Each successful hit or parry by the player will render an AI "flatfooted", which means it will not move for an amount of time defined as flatfooted_time (it can still attack, though). This time can be used to flee from the AI instead of continuing fighting. If the player gets outside the melee reange of an AI (e.g. by climbing somewhere the AI cannot reach), the AI will start throwing stones at the player if "outofreach_projectile_enabled" is set to "1". It will wait a random amount of time between "outofreach_projectile_delay_min" and "outofreach_projectile_delay_max" before doing so. The "attack_cone" determines in which region the AI can throw (or shoot in case of bowmen). Additionally, each shot will be offset by a random amount of up to "attack_accuracy" degrees, so not each shot will hit the player.		When stealth fails, the player always has the option to openly fight AIs instead of fleeing. However, combat in TDM is meant as a last resort and will ruin any stealth scores and will most likely kill you, when you face more than one guard. Also, common settings prohibit killing civilians (AI with the spawnarg "is_civilian" set to 1) and even guards on higher difficulties. The difficulty of a melee fight is influenced by three factors (not counting the player's skills): The combat difficulty setting in the menu (which can be set by the player), the melee skills of the AI (novice, trained, skilled, see Melee sets, are usually set for specific AI, but can be changed by the map author), and the difficulty setting of the current map (also chosen by the player). For a more detailed description on what to keep in mind while fighting, see [[The Dark Mod Gameplay#Combat\|Combat]]. A hit by the player will deal damage. The damage reduces the amount of health of the AI by the base damage, scaled by the "damage_scale" of the zone hit. When the dealt damage surpasses the pain_threshold, the pain animation of the AI will be played. As soon as the health of the AI reaches the health_critical value, the AI will flee. Each successful hit or parry by the player will render an AI "flatfooted", which means it will not move for an amount of time defined as flatfooted_time (it can still attack, though). This time can be used to flee from the AI instead of continuing fighting. If the player gets outside the melee reange of an AI (e.g. by climbing somewhere the AI cannot reach), the AI will start throwing stones at the player if "outofreach_projectile_enabled" is set to "1". It will wait a random amount of time between "outofreach_projectile_delay_min" and "outofreach_projectile_delay_max" before doing so. The "attack_cone" determines in which region the AI can throw (or shoot in case of bowmen). Additionally, each shot will be offset by a random amount of up to "attack_accuracy" degrees, so not each shot will hit the player.

Petike: adding category tag

2018-10-20T05:07:48Z

adding category tag

← Older revision		Revision as of 05:07, 20 October 2018
Line 714:		Line 714:
	=== Steambots ===		=== Steambots ===
	=== Undead ===		=== Undead ===

			[[Category:AI]]

Destined at 09:20, 4 May 2018

2018-05-04T09:20:50Z

← Older revision		Revision as of 09:20, 4 May 2018
Line 11:		Line 11:
	Tactile perception gets triggered, when the AI collision model touches the player's collision model.		Tactile perception gets triggered, when the AI collision model touches the player's collision model.
	==== Perception and Alarms ====		==== Perception and Alarms ====
	When an AI perceives anything suspicious, it adds to the AI's alert level. When this counter exceeds a certain amount (alert_thresh#), the AI will reach the next alert stage. In order to prevent the alert level to ramp up too quickly there is a grace period (alert_gracetime#) during which a new suspicious stim will not further alert the AI. This period can be ~~termintaed~~ if the new stim during the grace period is too strong (exceeds the former addition to the alert level multiplied with the "alert_gracefrac#" value) or if there are too many stims in quick succession (exceeding the ~~alert_gracvecount~~#). Above the "idle" state (0) there are five alert stages:		When an AI perceives anything suspicious, it adds to the AI's alert level. When this counter exceeds a certain amount (alert_thresh#), the AI will reach the next alert stage. In order to prevent the alert level to ramp up too quickly there is a grace period (alert_gracetime#) during which a new suspicious stim will not further alert the AI. This period can be terminated if the new stim during the grace period is too strong (exceeds the former addition to the alert level multiplied with the "alert_gracefrac#" value) or if there are too many stims in quick succession (exceeding the alert_gracecount#). Above the "idle" state (0) there are five alert stages:
	*1: Observant (bark, but otherwise no reaction)		*1: Observant (bark, but otherwise no reaction)
	*2: Suspicious (bark, look, may stop and turn)		*2: Suspicious (bark, look, may stop and turn)

Destined at 12:35, 21 April 2017

2017-04-21T12:35:46Z

Show changes

Destined at 07:45, 6 March 2017

2017-03-06T07:45:34Z

← Older revision		Revision as of 07:45, 6 March 2017
Line 1:		Line 1:
	<pre style="color: red">THIS PAGE IS A WORK IN PROGRESS</pre>		<pre style="color: red">THIS PAGE IS A WORK IN PROGRESS</pre>
	== Spawnargs and Game Mechanics ==		== Spawnargs and Game Mechanics ==
	In order to understand the influence of the spawnargs on game mechanics, I want to give a ~~simplified~~ insight into the mechanics. For this I have decided to categorise them into four subgroups: AI perception, Combat, Interaction between AIs and player out of combat~~, and others~~.		In order to understand the influence of the spawnargs on game mechanics, I want to give a simple insight into the mechanics. For this I have decided to categorise them into four subgroups: AI perception, Combat, and Interaction between AIs and player out of combat.
	=== AI perception ===		=== AI perception ===
	In the centre of each stealth game lies the perception of the AIs. This includes the ability of AIs to see, hear, and touch its environment. The chance to percieve anything with the respective sense is multiplied with the respective acuity_* spawnarg at some point. If the AI is drunk all these factors are multiplied with the drunk_acuity_factor (default 0.5), which reduces the chance of the AI to notice the player.		In the centre of each stealth game lies the perception of the AIs. This includes the ability of AIs to see, hear, and touch its environment. The chance to percieve anything with the respective sense is multiplied with the respective acuity_* spawnarg at some point. If the AI is drunk all these factors are multiplied with the drunk_acuity_factor (default 0.5), which reduces the chance of the AI to notice the player.
Line 110:		Line 110:
	\|}		\|}
	=== Combat ===		=== Combat ===
	When stealth fails, the player always has the option to fight AIs instead of fleeing. However, combat in TDM is meant as a last resort and will ruin any stealth scores and will most likely kill you, when you face more than on guard. Also, common settings prohibit killing civilians (AI with the spawnarg "is_civilian" set to 1) and even guards on higher difficulties. The difficulty of a melee fight is influenced by two factors (not counting the player's skills): The difficulty setting in the menu and the difficulty setting of the AI (novice, trained, skilled, see Melee sets). For a more detailed description on what to keep in mind while fighting, see [[The Dark Mod Gameplay#Combat\|Combat]]. A hit on or ~~successful~~ parry will render an AI "flatfooted", which means it will not move for an amount of time defined as flatfooted_time. This time can be used to flee from the AI instead of continuing fighting.		When stealth fails, the player always has the option to fight AIs instead of fleeing. However, combat in TDM is meant as a last resort and will ruin any stealth scores and will most likely kill you, when you face more than on guard. Also, common settings prohibit killing civilians (AI with the spawnarg "is_civilian" set to 1) and even guards on higher difficulties. The difficulty of a melee fight is influenced by two factors (not counting the player's skills): The difficulty setting in the menu (which can be set by the player) and the difficulty setting of the AI (novice, trained, skilled, see Melee sets, can be set by the map author). For a more detailed description on what to keep in mind while fighting, see [[The Dark Mod Gameplay#Combat\|Combat]]. A hit by the player will deal damage. The damage reduces the amount of health of the AI by the base damage, scaled by the "damage_scale" of the zone hit. When the dealt damage surpasses the pain_threshold, the pain animation of the AI will be played. As soon as the health of the AI reaches the health_critical value, the AI will flee. Each successful hit or parry by the player will render an AI "flatfooted", which means it will not move for an amount of time defined as flatfooted_time (it can still attack, though). This time can be used to flee from the AI instead of continuing fighting. If the player gets outside the melee reange of an AI (e.g. by climbing somewhere the AI cannot reach), the AI will start throwing stones at the player if "outofreach_projectile_enabled" is set to "1". It will wait a random amount of time between "outofreach_projectile_delay_min" and "outofreach_projectile_delay_max" before doing so. The "attack_cone" determines in which region the AI can throw (or shoot in case of bowmen). Additionally, each shot will be offset by a random amount of up to "attack_accuracy" degrees, so not each shot will hit the player.
	{\| class="wikitable"		{\| class="wikitable"
	\|+Spawnargs realted to combat		\|+Spawnargs realted to combat
Line 128:		Line 128:
	\|bleed		\|bleed
	\|If set to true, this entity will bleed, e.g. spawn blood particles and decals when hurt.		\|If set to true, this entity will bleed, e.g. spawn blood particles and decals when hurt.
			\|-
			\|can_be_flatfooted
			\|If set to true, the AI becomes flat-footed in certain combat situations. This means they're unable to run at the player, but can still turn to face the player.
	\|-		\|-
	\|damage		\|damage
Line 152:		Line 155:
	\|is_civilian		\|is_civilian
	\|If true, the AI is a civilian. Defaults to 0.		\|If true, the AI is a civilian. Defaults to 0.
	\|-
	~~\|melee_damage_mod~~
	~~\|When the AI hits with a melee weapon, this multiplies the default damage done by the weapon. Is depending on difficulty and is replaced by melee_sets. Ranges from 0.8 to 1.4.~~
	\|-
	~~\|melee_range~~
	~~\|do melee attack when within 3x this range~~
	\|-		\|-
	\|move_speed		\|move_speed
Line 187:		Line 184:
	\|blind_time		\|blind_time
	\|The time span in seconds the AI is staying in 'blinded' state when hit by a flashbomb or -mine.		\|The time span in seconds the AI is staying in 'blinded' state when hit by a flashbomb or -mine.
	\|-
	~~\|can_be_flatfooted~~
	~~\|If set to true, the AI becomes flat-footed in certain combat situations. This means they're unable to run at the player, but can still turn to face the player.~~
	\|-		\|-
	\|can_drown		\|can_drown

Destined at 05:12, 28 February 2017

2017-02-28T05:12:42Z

← Older revision		Revision as of 05:12, 28 February 2017
Line 152:		Line 152:
	\|is_civilian		\|is_civilian
	\|If true, the AI is a civilian. Defaults to 0.		\|If true, the AI is a civilian. Defaults to 0.
	\|-
	~~\|melee_damage~~
	~~\|Damage dealt with a melee weapon.~~
	\|-		\|-
	\|melee_damage_mod		\|melee_damage_mod
	\|When the AI hits with a melee weapon, this multiplies the default damage done by the weapon. Is depending on difficulty and is replaced by melee_sets. Ranges from 0.8 to 1.4.		\|When the AI hits with a melee weapon, this multiplies the default damage done by the weapon. Is depending on difficulty and is replaced by melee_sets. Ranges from 0.8 to 1.4.
	\|-
	~~\|melee_predicts_proximity~~
	\|If true, AI takes the current velocity of itself and its enemy into account to predict whether it will hit the enemy in the future if it starts a melee attack now. All but the stupidest AI should do this.
	\|-
	~~\|melee_predicted_attack_time~~
	\|The amount of time in milliseconds that the AI uses to predict whether it will hit its enemy if it starts its attack now. Should roughly correspond to the time it takes before the attack animation is threatening to an enemy in front of them. This baseline can be set on an AI for empty-hand attacks, then may be overwritten by individual weapons if their attack animations are slower/faster than this baseline.
	\|-		\|-
	\|melee_range		\|melee_range
	\|do melee attack when within 3x this range		\|do melee attack when within 3x this range
	\|-
	~~\|melee_rep_attack_time~~
	\|
	\|-		\|-
	\|move_speed		\|move_speed

Destined at 05:08, 28 February 2017

2017-02-28T05:08:18Z

← Older revision		Revision as of 05:08, 28 February 2017
Line 17:		Line 17:
	*4: Agitated Searching (Investigation, Weapon out, AI is quite sure that there is someone around)		*4: Agitated Searching (Investigation, Weapon out, AI is quite sure that there is someone around)
	*5: Combat.		*5: Combat.
	The AI will stay in this alert state for a time determined by "alert_time#". Please note, that as soon as an AI has drawn its weapon it will not recede to the regular idle state, but instead to the "alert idle" state, in which ~~the AI will not put away its weapon. This state may result~~ in a different behaviour of the AI ~~as before~~ (e.g. a former stationary AI starts patroling).		The AI will stay in this alert state for a time determined by "alert_time#". Please note, that as soon as an AI has drawn its weapon it will not recede to the regular idle state, but instead to the "alert idle" state, which results in a hightened senses and possibly different behaviour of the AI (e.g. a former stationary AI starts patroling).
	{\| class="wikitable"		{\| class="wikitable"
	\|+Spawnargs related to AI perception		\|+Spawnargs related to AI perception
Line 110:		Line 110:
	\|}		\|}
	=== Combat ===		=== Combat ===
	When stealth fails, the player always has the option to fight AIs instead of fleeing. However, combat in TDM is meant as a last resort and will ruin any stealth scores. Also, a common ~~setting prohibits~~ killing civilians (AI with the spawnarg "is_civilian" set to 1) and even ~~any AIs~~ on higher difficulties. The difficulty of a fight is influenced by two factors (not counting the player's skills): The difficulty setting in the menu and the difficulty setting of the AI (novice, trained, skilled, see Melee sets).		When stealth fails, the player always has the option to fight AIs instead of fleeing. However, combat in TDM is meant as a last resort and will ruin any stealth scores and will most likely kill you, when you face more than on guard. Also, common settings prohibit killing civilians (AI with the spawnarg "is_civilian" set to 1) and even guards on higher difficulties. The difficulty of a melee fight is influenced by two factors (not counting the player's skills): The difficulty setting in the menu and the difficulty setting of the AI (novice, trained, skilled, see Melee sets). For a more detailed description on what to keep in mind while fighting, see [[The Dark Mod Gameplay#Combat\|Combat]]. A hit on or successful parry will render an AI "flatfooted", which means it will not move for an amount of time defined as flatfooted_time. This time can be used to flee from the AI instead of continuing fighting.
	~~==== Melee~~ Combat ~~====~~
	~~Melee~~ Combat ~~difficulty is mainly dependent~~ on ~~two factors: How well and often can the AI~~ parry ~~and how well and often does the~~ AI ~~attack. These two factors are~~ not ~~only influenced by the general skill~~ of the AI~~, but also by the actions of the player and thus require a couple~~ of ~~spawnargs~~.
	~~==== Ranged Combat ====~~
	{\| class="wikitable"		{\| class="wikitable"
	\|+Spawnargs realted to combat		\|+Spawnargs realted to combat
Line 136:		Line 133:
	\|-		\|-
	\|damage_zones		\|damage_zones
	\|There are different hit zones for AI that ~~variy~~ the damage recieved from the player.		\|There are different hit zones for AI that vary the damage recieved from the player.
	\|-		\|-
	\|damage_scale "zone"		\|damage_scale "zone"
Line 143:		Line 140:
	\|def_melee_set		\|def_melee_set
	\|The defined melee set that describes the fighting skills. The levels are "novice", "trained", and "skilled" and are further modiefied by the difficulty of the game.		\|The defined melee set that describes the fighting skills. The levels are "novice", "trained", and "skilled" and are further modiefied by the difficulty of the game.
			\|-
			\|flatfooted_time
			\|The duration in milliseconds that this AI remains flat footed after a combat action triggers this state.
	\|-		\|-
	\|health		\|health
Line 223:		Line 223:
	\|cansearchcooperatively		\|cansearchcooperatively
	\|ability to participate in a coordinated search		\|ability to participate in a coordinated search
	\|-
	~~\|flatfooted_time~~
	~~\|The duration in milliseconds that this AI remains flat footed after a combat action triggers this state.~~
	\|-		\|-
	\|gas_immune		\|gas_immune

Destined at 19:32, 17 February 2017

2017-02-17T19:32:41Z

← Older revision		Revision as of 19:32, 17 February 2017
Line 8:		Line 8:
	==== Aural perception ====		==== Aural perception ====
	Noises made by the player as well as thrown objects or noise arrows produce a propagated sound of a specified volume. The propagated sound's volume decreases linearly with increasing distance from the source. When it reaches an AI the alert_aud_thresh value is subtracted and the remaining volume (if it is greater than 0) is added to the alert level of an AI.		Noises made by the player as well as thrown objects or noise arrows produce a propagated sound of a specified volume. The propagated sound's volume decreases linearly with increasing distance from the source. When it reaches an AI the alert_aud_thresh value is subtracted and the remaining volume (if it is greater than 0) is added to the alert level of an AI.
	==== ~~Aural~~ perception ====		==== Tactile perception ====
	Tactile perception gets triggered, when the AI collision model touches the player's collision model.		Tactile perception gets triggered, when the AI collision model touches the player's collision model.
	==== Perception and Alarms ====		==== Perception and Alarms ====

Destined at 19:32, 17 February 2017

2017-02-17T19:32:02Z

← Older revision		Revision as of 19:32, 17 February 2017
Line 8:		Line 8:
	==== Aural perception ====		==== Aural perception ====
	Noises made by the player as well as thrown objects or noise arrows produce a propagated sound of a specified volume. The propagated sound's volume decreases linearly with increasing distance from the source. When it reaches an AI the alert_aud_thresh value is subtracted and the remaining volume (if it is greater than 0) is added to the alert level of an AI.		Noises made by the player as well as thrown objects or noise arrows produce a propagated sound of a specified volume. The propagated sound's volume decreases linearly with increasing distance from the source. When it reaches an AI the alert_aud_thresh value is subtracted and the remaining volume (if it is greater than 0) is added to the alert level of an AI.
	~~<pre style~~=~~"color: red">Here will follow an explanation on~~ the ~~missing mechanics</pre>~~		==== Aural perception ====
			Tactile perception gets triggered, when the AI collision model touches the player's collision model.
	==== Perception and Alarms ====		==== Perception and Alarms ====
	When an AI perceives anything suspicious, it adds to the AI's alert level. When this counter exceeds a certain amount (alert_thresh#), the AI will reach the next alert stage. In order to prevent the alert level to ramp up too quickly there is a grace period (alert_gracetime#) during which a new suspicious stim will not further alert the AI. This period can be termintaed if the new stim during the grace period is too strong (exceeds the former addition to the alert level multiplied with the "alert_gracefrac#" value) or if there are too many stims in quick succession (exceeding the alert_gracvecount#). Above the "idle" state (0) there are five alert stages:		When an AI perceives anything suspicious, it adds to the AI's alert level. When this counter exceeds a certain amount (alert_thresh#), the AI will reach the next alert stage. In order to prevent the alert level to ramp up too quickly there is a grace period (alert_gracetime#) during which a new suspicious stim will not further alert the AI. This period can be termintaed if the new stim during the grace period is too strong (exceeds the former addition to the alert level multiplied with the "alert_gracefrac#" value) or if there are too many stims in quick succession (exceeding the alert_gracvecount#). Above the "idle" state (0) there are five alert stages:
Line 110:		Line 111:
	=== Combat ===		=== Combat ===
	When stealth fails, the player always has the option to fight AIs instead of fleeing. However, combat in TDM is meant as a last resort and will ruin any stealth scores. Also, a common setting prohibits killing civilians (AI with the spawnarg "is_civilian" set to 1) and even any AIs on higher difficulties. The difficulty of a fight is influenced by two factors (not counting the player's skills): The difficulty setting in the menu and the difficulty setting of the AI (novice, trained, skilled, see Melee sets).		When stealth fails, the player always has the option to fight AIs instead of fleeing. However, combat in TDM is meant as a last resort and will ruin any stealth scores. Also, a common setting prohibits killing civilians (AI with the spawnarg "is_civilian" set to 1) and even any AIs on higher difficulties. The difficulty of a fight is influenced by two factors (not counting the player's skills): The difficulty setting in the menu and the difficulty setting of the AI (novice, trained, skilled, see Melee sets).
			==== Melee Combat ====
			Melee Combat difficulty is mainly dependent on two factors: How well and often can the AI parry and how well and often does the AI attack. These two factors are not only influenced by the general skill of the AI, but also by the actions of the player and thus require a couple of spawnargs.
			==== Ranged Combat ====
	{\| class="wikitable"		{\| class="wikitable"
	\|+Spawnargs realted to combat		\|+Spawnargs realted to combat