Attaching Props to AI - Revision history

Frost Salamander: /* Belt Objects - Keys */

2025-05-13T19:42:44Z

Belt Objects - Keys

← Older revision		Revision as of 19:42, 13 May 2025
Line 98:		Line 98:
	''Example of key attachment by bikerdude''		''Example of key attachment by bikerdude''

	def_attach6 atdm:~~key_simple~~		def_attach6 atdm:prop_key_simple
	pos_attach6 belt_back_right		pos_attach6 belt_back_right
	name_attach6 gate_key		name_attach6 gate_key
Line 108:		Line 108:
	Other attachable key styles include:		Other attachable key styles include:
	atdm:prop_key_gold		atdm:prop_key_gold
	atdm:~~prop_key_silver~~		atdm:prop_silverkey
	~~atdm:prop_key_simple~~
	atdm:prop_key_fancy01		atdm:prop_key_fancy01
	atdm:prop_key_padlock		atdm:prop_key_padlock

Bikerdude: /* Belt Objects - Keys */

2024-08-19T10:45:31Z

Belt Objects - Keys

← Older revision		Revision as of 10:45, 19 August 2024
Line 98:		Line 98:
	''Example of key attachment by bikerdude''		''Example of key attachment by bikerdude''

	def_attach6 atdm:~~prop_silverkey~~		def_attach6 atdm:key_simple
	pos_attach6 belt_back_right		pos_attach6 belt_back_right
	name_attach6 gate_key		name_attach6 gate_key

Geep: /* Difficulty Levels */

2022-03-09T18:49:06Z

Difficulty Levels

← Older revision		Revision as of 18:49, 9 March 2022
Line 154:		Line 154:
	set name on test_key test_key		set name on test_key test_key

	Now, let's redo it, so the key is only present on the easiest difficulty (diff_0). First, and required to make this work, '''DON'T''' have present (even blank or defaulted) any spawnargs related to the item we want conditional, e.g, all of those spawnargs in our example above. Instead, each line above becomes a pair of spawnargs, of form diff_0_change_n and diff_0_arg_n:		Now, let's redo it, so the key is only present on the easiest difficulty (diff_0). First, and required to make this work, '''DON'T''' have present (even blank or defaulted) any unconditional spawnargs related to the item we want conditional, e.g, all of those spawnargs in our example above. Instead, each line above becomes a pair of spawnargs, of form diff_0_change_n and diff_0_arg_n:

	diff_0_change_0 def_attach6		diff_0_change_0 def_attach6

Geep: /* Difficulty Levels */ Redone with content by Spooks

2022-03-09T18:46:56Z

Difficulty Levels: Redone with content by Spooks

@@ Line 142: / Line 142: @@
 === Difficulty Levels ===
-''From [https://forums.thedarkmod.com/index.php?/topic/9082-newbie-darkradiant-questions/page/264/&tab=comments#comment-387803 this forum discussion:]''
+[https://forums.thedarkmod.com/index.php?/topic/9082-newbie-darkradiant-questions/page/264/&tab=comments#comment-387803 Traditionally], it was thought you cannot directly vary the presence of a def_attached item, like a key, by Difficulty Level. Specifically, using diff_x_nospawn doesn't work, because the def_attached item is automatically spawned when the AI is spawned, and then it is too late for spawn prevention with diff_x_nospawn. (The recommended work-around was to clone your AI, then make them differ in their diff_n_nospawn spawnargs and their attached items.)
-You cannot directly vary the presence of a def_attached item by Difficulty Level. A work-around is to clone your AI, then make them differ in their diff_''n''_nospawn spawnargs and their attached items.
 == Binding ==

Geep: /* Binding */ limitation of bound keys for AI

2021-12-10T21:47:43Z

Binding: limitation of bound keys for AI

← Older revision		Revision as of 21:47, 10 December 2021
Line 150:		Line 150:
	'''Benefits:''' You can bind any object to an AI, so it is a great deal more flexible. You can also see and position the object in DR.		'''Benefits:''' You can bind any object to an AI, so it is a great deal more flexible. You can also see and position the object in DR.

	'''Weaknesses:''' Bound objects cannot affect AI animations. You must adjust each object individually.		'''Weaknesses:''' Bound objects cannot affect AI animations. You must adjust each object individually. An AI can't use a bound key to open locked doors (but see [[Doors]] for a workaround).

	See [[BindToJoint]] and [[Attaching Items]] for more info on using bind.		See [[BindToJoint]] and [[Attaching Items]] for more info on using bind.

Geep: /* Changing the Behavior of Def-Attached Props */ Add frob_distance example

2021-01-29T22:22:13Z

Changing the Behavior of Def-Attached Props: Add frob_distance example

← Older revision		Revision as of 22:22, 29 January 2021
Line 123:		Line 123:

	For instance:		For instance:
	set frob_distance on ~~my_key~~ 100		set frob_distance on gate_key 100

	This can be done not just for props you attach, but for those pre-provisioned with an AI. For example, consider an archer whose quiver comes with 1 frobable arrow. Suppose you wish to override the default frob behavior. If you examine the archer with the Entity Inspector (including inherited items), you will find that there's an arrow on def_attach3, but it is unnamed. Fix that:		This can be done not just for props you attach, but for those pre-provisioned with an AI. For example, consider an archer whose quiver comes with 1 frobable arrow. Suppose you wish to override the default frob behavior. If you examine the archer with the Entity Inspector (including inherited items), you will find that there's an arrow on def_attach3, but it is unnamed. Fix that:

Geep: /* Changing the Behavior of Def-Attached Props */

2021-01-29T22:19:30Z

Changing the Behavior of Def-Attached Props

← Older revision		Revision as of 22:19, 29 January 2021
Line 121:		Line 121:
	Then reference that name:		Then reference that name:
	set [spawnarg] on [my_prop_name] [value]		set [spawnarg] on [my_prop_name] [value]

			For instance:
			set frob_distance on my_key 100

	This can be done not just for props you attach, but for those pre-provisioned with an AI. For example, consider an archer whose quiver comes with 1 frobable arrow. Suppose you wish to override the default frob behavior. If you examine the archer with the Entity Inspector (including inherited items), you will find that there's an arrow on def_attach3, but it is unnamed. Fix that:		This can be done not just for props you attach, but for those pre-provisioned with an AI. For example, consider an archer whose quiver comes with 1 frobable arrow. Suppose you wish to override the default frob behavior. If you examine the archer with the Entity Inspector (including inherited items), you will find that there's an arrow on def_attach3, but it is unnamed. Fix that:

Geep: Add Difficulty Levels section

2021-01-19T05:50:13Z

Add Difficulty Levels section

← Older revision		Revision as of 05:50, 19 January 2021
Line 137:		Line 137:

	This latter alternative is especially useful if you want this response on multiple AI: just set up the S/R spawnargs once, then easily give the special arrow to various AI by changing the def_attach_3 spawnarg.		This latter alternative is especially useful if you want this response on multiple AI: just set up the S/R spawnargs once, then easily give the special arrow to various AI by changing the def_attach_3 spawnarg.

			=== Difficulty Levels ===

			''From [https://forums.thedarkmod.com/index.php?/topic/9082-newbie-darkradiant-questions/page/264/&tab=comments#comment-387803 this forum discussion:]''
			You cannot directly vary the presence of a def_attached item by Difficulty Level. A work-around is to clone your AI, then make them differ in their diff_''n''_nospawn spawnargs and their attached items.

	== Binding ==		== Binding ==

Geep: Add See Also

2020-03-24T18:37:41Z

Add See Also

← Older revision		Revision as of 18:37, 24 March 2020
Line 146:		Line 146:
	See [[BindToJoint]] and [[Attaching Items]] for more info on using bind.		See [[BindToJoint]] and [[Attaching Items]] for more info on using bind.

			== See Also ==
			[[Def attach]] applied to non-AI entities, such as combined light sources.
	{{tutorial-ai}}		{{tutorial-ai}}

Geep: /* Changing the Behavior of Def-Attached Props */

2020-03-23T21:24:49Z

Changing the Behavior of Def-Attached Props

← Older revision		Revision as of 21:24, 23 March 2020
Line 134:		Line 134:
	set [S/R spawnarg] on [my_prop_name] [S/R value] ''where [my_prop_name] might be "quiver_arrow" from above''		set [S/R spawnarg] on [my_prop_name] [S/R value] ''where [my_prop_name] might be "quiver_arrow" from above''

	If there ~~are~~ any problem when overriding a behavior for an existing prop, a safe bet is to write a new definition. Thus, in our arrow example, copy the definition of atdm:prop_quiver_arrow to a new definition file, rename the definition to a unique name (e.g. "atdm:prop_quiver_arrow_special"). Again, use a dummy entity to create the S/R spawnargs. Then add those spawnargs to the definition, and change the spawnarg def_attach_3 on the AI to the new name.		If there is any problem when overriding a behavior for an existing prop, a safe bet is to write a new definition. Thus, in our arrow example, copy the definition of atdm:prop_quiver_arrow to a new definition file, rename the definition to a unique name (e.g. "atdm:prop_quiver_arrow_special"). Again, use a dummy entity to create the S/R spawnargs. Then add those spawnargs to the definition, and change the spawnarg def_attach_3 on the AI to the new name.

	This latter alternative is especially useful if you want this response on multiple AI: just set up the S/R spawnargs once, then easily give the special arrow to various AI by changing the def_attach_3 spawnarg.		This latter alternative is especially useful if you want this response on multiple AI: just set up the S/R spawnargs once, then easily give the special arrow to various AI by changing the def_attach_3 spawnarg.