Conversations - Revision history

Geep: Add link to Conversation Looping

2021-12-30T21:47:12Z

Add link to Conversation Looping

← Older revision		Revision as of 21:47, 30 December 2021
Line 232:		Line 232:
	volume 1		volume 1
	Regular AI spoken lines have maxDistance 25, yells 30.		Regular AI spoken lines have maxDistance 25, yells 30.

			== Looping a Conversation ==
			See [[Conversation Looping]]

	== Debugging Conversations ==		== Debugging Conversations ==

Geep: Rewrite "AI continues on path" section & adjoining, to add JackFarmer update.

2021-12-29T21:46:37Z

Rewrite "AI continues on path" section & adjoining, to add JackFarmer update.

← Older revision		Revision as of 21:46, 29 December 2021
Line 164:		Line 164:
	:* no arguments		:* no arguments

	== ~~How~~ to ~~get~~ AI ~~to patrol after finishing~~ a ~~conversation ==~~		== A Single-Actor "Conversation" ==
			It's possible to define conversations with only one actor. This can be used to let AI say a single sentence or perform some other actions.

	''Sometimes you want AI to stay put until their conversation is ~~triggered~~, and then start a regular patrol. ~~Here~~'s ~~one~~ way ~~how~~(~~courtesy~~ of ~~grayman)~~, ~~see another below in Notes:'~~'		When only one actor is present in a conversation, the flags <tt>actors_must_be_within_talkdistance</tt> and <tt>actors_always_face_each_other_while_talking</tt> have no effect. The flags are automatically set to 0 in the code.

			== How to Get AI to Patrol after Finishing a Conversation ==
			''Sometimes you want AI to stay put until their conversation is done, and then start a regular patrol.''

			=== Recommended Method ===
			''grayman's method, improved by JackFarmer''

			The trick is to have your conversation, for each actor, trigger an atdm:target_changetarget. In that entity, give it these spawnargs:

			"target" "<name of AI who's leaving>"
			"add" "<name of path_corner you want him to walk to>"

			The traditional advice would be to put that entity at or near the '''end''' of the conversation. However, it turns out it's better to place it at the '''start''' of the conversation. That way, if the conversationalists are interrupted and the conversation aborted, at least they will continue on to pathing.

			Furthermore, for this method to work as expected, you also have to first remove any old unwanted "target" spawnargs from the AI. For instance, if pre-conversation Bob has a spawnarg "target" "path_corner_start", create a separate atdm:target_changetarget with:

			"target" "Bob"
			"remove" "path_corner_start".

			Activate this at or near the start of your conversation.

			(Note: Can one use just one atdm:target_changetarget with '''both''' add and remove? With the traditional placement at the end of the conversation, that didn't work right. Maybe it will work when placed at the beginning.)

			==== An Example ====

	Guards Bob and Sam will have the conversation. Neither is targetted at any path_corners.		Guards Bob and Sam will have the conversation. Neither is targetted at any path_corners.
Line 176:		Line 201:
	A player-activated trigger fires the entity that starts the conversation.		A player-activated trigger fires the entity that starts the conversation.

	In the conversation, have these two steps at or near the ~~end~~:		In the conversation, have these two steps at or near the beginning:

	Trigger the entity StartBobPatrol		* Trigger the entity StartBobPatrol
			* Trigger the entity StartSamPatrol

	~~Trigger the entity StartSamPatrol~~		where "StartBobPatrol" is an atdm:target_changetarget with these spawnargs:

	"~~StartBobPatrol~~" ~~is an atdm:target_changetarget with these spawnargs:~~		"add" "path_corner_1"
			"target" "Bob"

	"~~add" "path_corner_1"~~		and "StartSamPatrol" is an atdm:target_changetarget with these spawnargs:
	~~"target" "Bob~~"

	"~~StartSamPatrol~~" ~~is an atdm:target_changetarget with these spawnargs:~~		"add" "path_corner_2"
			"target" "Sam"

	~~"add" "path_corner_2"~~		When the conversation ends, both guards will go their separate ways.
	~~"target" "Sam"~~

	~~When~~ the conversation ~~ends~~, ~~both guards~~ will ~~go their separate ways~~.		=== Older Alternative Method ===

			Starting with TDM 1.08, an actor who begins a conversation sitting on a path_waitfortrigger can be moved off that trigger at the end of the conversation by having the last step in the conversation activate a trigger_once whose target is the actor, and which has a 'delay' spawnarg set to at least 1 second. Without the delay, the actor will ignore the activation and remain where they are.

			== Run to Actor? ==

	~~== Notes ==~~		Since there are no "RunToActor"-style commands, only "WalkToActor", switching between pathing and conversation as just described is a way to incorporate running.
	* It's possible to define conversations with only one actor. This can be used to let AI talk a single sentence or perform some other actions.
	* The flags <tt>actors_must_be_within_talkdistance</tt> and <tt>actors_always_face_each_other_while_talking</tt> have no effect when only one actor is present in the conversation. The flags are automatically set to 0 in the code.
	* Starting with 1.08, an actor who begins a conversation sitting on a path_waitfortrigger can be moved off that trigger at the end of the conversation by having the last step in the conversation activate a trigger_once whose target is the actor, and which has a 'delay' spawnarg set to at least 1 second. W/o the delay, the actor will ignore the activation and remain where they are.
	* Simpler to walk off might be to have the last command in your conversation trigger an atdm:target_changetarget. In that entity, give it these spawnargs: "target" "<name of AI who's leaving>" and "add" "<name of path_corner you want him to walk to>, as discussed above. However, for this to work as expected, you also have to first remove any old unwanted "target" spawnargs from the AI. For instance, if Bob has a spawnarg "target" "path_corner_start", create a separate atdm:target_changetarget with "target" "Bob", "remove" "path_corner_start". Activate this near the start of your conversation... it won't work right if you try to use just one atdm:target_changetarget with both add and remove at the conversation's end.
	* Since there are no "RunToActor"-style commands, only "WalkToActor", switching between pathing and conversation as just described is a way to incorporate running.

	== Volume of Custom Lines ==		== Volume of Custom Lines ==

Geep: /* Notes */ Discuss changetarget with remove; use with running

2021-03-09T15:40:12Z

Notes: Discuss changetarget with remove; use with running

← Older revision		Revision as of 15:40, 9 March 2021
Line 198:		Line 198:
	* The flags <tt>actors_must_be_within_talkdistance</tt> and <tt>actors_always_face_each_other_while_talking</tt> have no effect when only one actor is present in the conversation. The flags are automatically set to 0 in the code.		* The flags <tt>actors_must_be_within_talkdistance</tt> and <tt>actors_always_face_each_other_while_talking</tt> have no effect when only one actor is present in the conversation. The flags are automatically set to 0 in the code.
	* Starting with 1.08, an actor who begins a conversation sitting on a path_waitfortrigger can be moved off that trigger at the end of the conversation by having the last step in the conversation activate a trigger_once whose target is the actor, and which has a 'delay' spawnarg set to at least 1 second. W/o the delay, the actor will ignore the activation and remain where they are.		* Starting with 1.08, an actor who begins a conversation sitting on a path_waitfortrigger can be moved off that trigger at the end of the conversation by having the last step in the conversation activate a trigger_once whose target is the actor, and which has a 'delay' spawnarg set to at least 1 second. W/o the delay, the actor will ignore the activation and remain where they are.
	* Simpler to walk off might be to have the last command in your conversation trigger an atdm:target_changetarget. In that entity, give it these spawnargs: "target" "<name of AI who's leaving>" and "add" "<name of path_corner you want him to walk to>"		* Simpler to walk off might be to have the last command in your conversation trigger an atdm:target_changetarget. In that entity, give it these spawnargs: "target" "<name of AI who's leaving>" and "add" "<name of path_corner you want him to walk to>, as discussed above. However, for this to work as expected, you also have to first remove any old unwanted "target" spawnargs from the AI. For instance, if Bob has a spawnarg "target" "path_corner_start", create a separate atdm:target_changetarget with "target" "Bob", "remove" "path_corner_start". Activate this near the start of your conversation... it won't work right if you try to use just one atdm:target_changetarget with both add and remove at the conversation's end.
			* Since there are no "RunToActor"-style commands, only "WalkToActor", switching between pathing and conversation as just described is a way to incorporate running.

	== Volume of Custom Lines ==		== Volume of Custom Lines ==

VanishedOne: /* Conversation */ Note on conv_N_actors_must_be_within_talkdistance and seated AI

2015-10-20T18:49:11Z

Conversation: Note on conv_N_actors_must_be_within_talkdistance and seated AI

← Older revision		Revision as of 18:49, 20 October 2015
Line 61:		Line 61:

	;'''conv_N_actors_must_be_within_talkdistance''' (1/0) default is 1		;'''conv_N_actors_must_be_within_talkdistance''' (1/0) default is 1
	: if set to "1", all actors are told to walk towards each other before the conversation actually starts.		: if set to "1", all actors are told to walk towards each other before the conversation actually starts. (Note that this can make seated characters stand up while the conversation plays even if they don't need to walk anywhere.)
	;'''conv_N_talk_distance''' (float) default is 60		;'''conv_N_talk_distance''' (float) default is 60
	: defines the maximum distance AI should be away from each other while talking. When the spawnarg '''actors_must_be_within_talkdistance''' is set to 1, this distance tells the AI when to stop when walking towards each other.		: defines the maximum distance AI should be away from each other while talking. When the spawnarg '''actors_must_be_within_talkdistance''' is set to 1, this distance tells the AI when to stop when walking towards each other.

Springheel: /* Spawnargs */

2015-10-19T19:29:35Z

Spawnargs

← Older revision		Revision as of 19:29, 19 October 2015
Line 65:		Line 65:
	: defines the maximum distance AI should be away from each other while talking. When the spawnarg '''actors_must_be_within_talkdistance''' is set to 1, this distance tells the AI when to stop when walking towards each other.		: defines the maximum distance AI should be away from each other while talking. When the spawnarg '''actors_must_be_within_talkdistance''' is set to 1, this distance tells the AI when to stop when walking towards each other.
	;'''conv_N_actors_always_face_each_other_while_talking''' (1/0) default is 1		;'''conv_N_actors_always_face_each_other_while_talking''' (1/0) default is 1
	: if set to "1", all actors are facing each other while talking. The talker turns towards another actor (usually the actor 0 or 1), and all other actors (the listeners) turn to face the talker.		: if set to "1", all actors are facing each other while talking. The talker turns towards another actor (usually the actor 0 or 1), and all other actors (the listeners) turn to face the talker. ''Note that when this option is selected in the conversation editor, AI will randomly play talk animations while speaking. When it is not selected, they won't. The latter may be desirable when AI are talking to themselves or whistling, for example''
	;'''conv_N_max_play_count''' (int) default is -1		;'''conv_N_max_play_count''' (int) default is -1
	: defines the maximum number of times this conversation is allowed to "play". After this number has been exhausted, the conversation won't be started anymore.		: defines the maximum number of times this conversation is allowed to "play". After this number has been exhausted, the conversation won't be started anymore.

RJFerret: /* Triggering a Conversation */ that's what I get for not previewing

2014-07-07T21:00:20Z

Triggering a Conversation: that's what I get for not previewing

← Older revision		Revision as of 21:00, 7 July 2014
Line 89:		Line 89:
	Now that your conversation is created, you need to trigger it.		Now that your conversation is created, you need to trigger it.

	To trigger a conversation you need to create a ''target_tdm_startconversation'' entity. Give it the spawnarg "conversation" with the name of the conversation you want to start (ex "conversation" "Testcoversation 1") then target that entity from any trigger you like such as a trigger_once entity or [[Path ~~Node~~\|path node]] (as of TDM v2.02).		To trigger a conversation you need to create a ''target_tdm_startconversation'' entity. Give it the spawnarg "conversation" with the name of the conversation you want to start (ex "conversation" "Testcoversation 1") then target that entity from any trigger you like such as a trigger_once entity or [[Path Nodes\|path node]] (as of TDM v2.02).

	== Conversation Commands ==		== Conversation Commands ==

RJFerret: /* Triggering a Conversation */

2014-07-07T20:59:55Z

Triggering a Conversation

← Older revision		Revision as of 20:59, 7 July 2014
Line 89:		Line 89:
	Now that your conversation is created, you need to trigger it.		Now that your conversation is created, you need to trigger it.

	To trigger a conversation you need to create a ''target_tdm_startconversation'' entity. Give it the spawnarg "conversation" with the name of the conversation you want to start (ex "conversation" "Testcoversation 1") then target that entity from any trigger you like such as a trigger_once entity or [path node] (as of TDM v2.02).		To trigger a conversation you need to create a ''target_tdm_startconversation'' entity. Give it the spawnarg "conversation" with the name of the conversation you want to start (ex "conversation" "Testcoversation 1") then target that entity from any trigger you like such as a trigger_once entity or [[Path Node\|path node]] (as of TDM v2.02).

	== Conversation Commands ==		== Conversation Commands ==

RJFerret: /* Triggering a Conversation */ +path node

2014-07-07T20:59:35Z

Triggering a Conversation: +path node

← Older revision		Revision as of 20:59, 7 July 2014
Line 89:		Line 89:
	Now that your conversation is created, you need to trigger it.		Now that your conversation is created, you need to trigger it.

	To trigger a conversation you need to create a ''target_tdm_startconversation'' entity. Give it the spawnarg "conversation" with the name of the conversation you want to start (ex "conversation" "Testcoversation 1") then target that entity from any trigger you like such as a trigger_once entity.		To trigger a conversation you need to create a ''target_tdm_startconversation'' entity. Give it the spawnarg "conversation" with the name of the conversation you want to start (ex "conversation" "Testcoversation 1") then target that entity from any trigger you like such as a trigger_once entity or [path node] (as of TDM v2.02).

	== Conversation Commands ==		== Conversation Commands ==

RJFerret: /* Volume of Custom Lines */

2014-04-28T12:52:08Z

Volume of Custom Lines

← Older revision		Revision as of 12:52, 28 April 2014
Line 202:		Line 202:
	== Volume of Custom Lines ==		== Volume of Custom Lines ==
	The soundshader files for unique lines control how far the sound reaches and volume, it's not set within the editor.		The soundshader files for unique lines control how far the sound reaches and volume, it's not set within the editor.
	* minDistance		minDistance 1
	* maxDistance		maxDistance 25
	* volume		volume 1
	Regular AI spoken lines ~~are~~ 25 dB, yells 30.		Regular AI spoken lines have maxDistance 25, yells 30.

	== Debugging Conversations ==		== Debugging Conversations ==

RJFerret: +volume

2014-04-27T16:26:44Z

+volume

← Older revision		Revision as of 16:26, 27 April 2014
Line 199:		Line 199:
	* Starting with 1.08, an actor who begins a conversation sitting on a path_waitfortrigger can be moved off that trigger at the end of the conversation by having the last step in the conversation activate a trigger_once whose target is the actor, and which has a 'delay' spawnarg set to at least 1 second. W/o the delay, the actor will ignore the activation and remain where they are.		* Starting with 1.08, an actor who begins a conversation sitting on a path_waitfortrigger can be moved off that trigger at the end of the conversation by having the last step in the conversation activate a trigger_once whose target is the actor, and which has a 'delay' spawnarg set to at least 1 second. W/o the delay, the actor will ignore the activation and remain where they are.
	* Simpler to walk off might be to have the last command in your conversation trigger an atdm:target_changetarget. In that entity, give it these spawnargs: "target" "<name of AI who's leaving>" and "add" "<name of path_corner you want him to walk to>"		* Simpler to walk off might be to have the last command in your conversation trigger an atdm:target_changetarget. In that entity, give it these spawnargs: "target" "<name of AI who's leaving>" and "add" "<name of path_corner you want him to walk to>"

			== Volume of Custom Lines ==
			The soundshader files for unique lines control how far the sound reaches and volume, it's not set within the editor.
			* minDistance
			* maxDistance
			* volume
			Regular AI spoken lines are 25 dB, yells 30.

	== Debugging Conversations ==		== Debugging Conversations ==